Recommendations for FX-40 to FX-60 Upgrade

[t-reck]

My first FX-40 site has 2 FX-40 that replaced 2 NCM102s. All devices communicate but memory issues and exceeding the 1000 point count has made the performance very poor. Setpoints don't change on many controllers. It does not perform as well as the NCMs.

Would a single FX-60 with 2 N2 busses perform better than the 2 FX-40s? I assume I would need the 256M memory.

Controllers are a handful of DX9100, VMA and UNTs. Most controllers are Microtech HPs communicating through MIGs (1 MIG per N2 Bus)

Will the station easily convert from the FX-40 to the FX-60? I can abandon the station of the #2 FX-40 since it is just HPs from the MIG and the points can be copied from the others.

[freddy-b]

My first FX-40 site has 2 FX-40 that replaced 2 NCM102s. All devices communicate but memory issues and exceeding the 1000 point count has made the performance very poor. Setpoints don't change on many controllers. It does not perform as well as the NCMs.

Would a single FX-60 with 2 N2 busses perform better than the 2 FX-40s? I assume I would need the 256M memory.

Controllers are a handful of DX9100, VMA and UNTs. Most controllers are Microtech HPs communicating through MIGs (1 MIG per N2 Bus)

Will the station easily convert from the FX-40 to the FX-60? I can abandon the station of the #2 FX-40 since it is just HPs from the MIG and the points can be copied from the others.

The EM60 will take the load and smile at you.

Easy....Pretty much a drag and drop deal.

[t-reck]

The EM60 will take the load and smile at you.

Easy....Pretty much a drag and drop deal.

Nice! Thanks.

[Chris_Worthington]

Setpoints don't change on many controllers.

Are you using "Set" or "Setpoint" ???

The "Set" action will carry a overridden status along with the "Set" action and generally will cause mayhem within the controllers, like not releasing the original command :eek:

I would configure the flags to make that option go away ;)

Like Freddy said the Jace 6 series are unbelievable as to the horse power behind them, you will be pleased :D

[t-reck]

The EM60 will take the load and smile at you.

Easy....Pretty much a drag and drop deal.

Finally got my hands on the hardware and my license renewal.

Wow! Just like you said Freddy, drag and drop for the majority of the programming. The processor putters along at about 30%, the FX40s were maxed out all the time.

That cured my issues and also made the navigation for the customer easier since only one device to browse to (no supervisor).

Some comments/questions:

*When the N2 devices were dropped into the config of the FX60, the devices dropped on the 2nd N2 bus had no issues, the devices dropped onto the standard N2 bus had the addressing all scrambled. I had to re-assign all addresses. I could make out no patterns, some were off by 1, some by 10.

*I tried to enable the 2nd ethernet port, more of a test than anything. It locked up both ports, I had to go into the serial shell to disable the 2nd port to get it back.

*What can the USB do?

*In the device networks portion of the side bar (that is visible while bowsing to the controller), only the devices on the primary N2 bus are available. I can get to all of them from the bound label targets on the graphics which is fine for normal operation, but may impact any programming done from the embedded workbench.

*When I try starting a station from my local host, the stations from the FX40's don't start properly, they are in some type of endless loop. If I exit the program and go back in, the stations are then running just fine. I did a station upgrade before doing this.

*For some reason, the station copier put my new FX60 copies into the C:\JCI\FXSupervisorPro-1.2\stations folder instead of the 2.0 folder. Just copying the folders over does not seem to allow the Application Director to see those stations so I can't run the station offline. How can I make those stations available?

Thanks again for your input Freddy and Chris.

[NINAX]

Finally got my hands on the hardware and my license renewal.

Wow! Just like you said Freddy, drag and drop for the majority of the programming. The processor putters along at about 30%, the FX40s were maxed out all the time.

Yea, 60s sure are great.



*In the device networks portion of the side bar (that is visible while bowsing to the controller), only the devices on the primary N2 bus are available. I can get to all of them from the bound label targets on the graphics which is fine for normal operation, but may impact any programming done from the embedded workbench.
I saw the same thing originally until I radically changed the name of the N2 buses. I think the new jars fix that. The jci FX Super Patch 2.0.1.



*For some reason, the station copier put my new FX60 copies into the C:\JCI\FXSupervisorPro-1.2\stations folder instead of the 2.0 folder. Just copying the folders over does not seem to allow the Application Director to see those stations so I can't run the station offline. How can I make those stations available?
That sounds like your platform daemon hasn't been ran for the 2.0 version.

[freddy-b]

Finally got my hands on the hardware and my license renewal.

Wow! Just like you said Freddy, drag and drop for the majority of the programming. The processor putters along at about 30%, the FX40s were maxed out all the time.

That cured my issues and also made the navigation for the customer easier since only one device to browse to (no supervisor).

Some comments/questions:

*When the N2 devices were dropped into the config of the FX60, the devices dropped on the 2nd N2 bus had no issues, the devices dropped onto the standard N2 bus had the addressing all scrambled. I had to re-assign all addresses. I could make out no patterns, some were off by 1, some by 10.

*I tried to enable the 2nd ethernet port, more of a test than anything. It locked up both ports, I had to go into the serial shell to disable the 2nd port to get it back.

*What can the USB do?

*In the device networks portion of the side bar (that is visible while bowsing to the controller), only the devices on the primary N2 bus are available. I can get to all of them from the bound label targets on the graphics which is fine for normal operation, but may impact any programming done from the embedded workbench.

*When I try starting a station from my local host, the stations from the FX40's don't start properly, they are in some type of endless loop. If I exit the program and go back in, the stations are then running just fine. I did a station upgrade before doing this.

*For some reason, the station copier put my new FX60 copies into the C:\JCI\FXSupervisorPro-1.2\stations folder instead of the 2.0 folder. Just copying the folders over does not seem to allow the Application Director to see those stations so I can't run the station offline. How can I make those stations available?

Thanks again for your input Freddy and Chris.

Cool, yes they are pretty impressive compared to a 40

The second port is not recommended or needed for fox. From what I read it is kind of in the same boat as the USB..I know you can set it up for bacnet IP, or 852 if thats important. but I really see no reason to use it as of yet.

I dont think the USB actually has a purpose yet, its there for future need.. I
guess?

The device networks are part of JCI's aplliance. I subdue it as much as possible and go at it like any other Jace, but I think it was addressed with the new jars.

As Ninax said, Running the platform daemon for 2.0 will take care of your other issues

[t-reck]

I saw the same thing originally until I radically changed the name of the N2 buses. I think the new jars fix that. The jci FX Super Patch 2.0.1.

Can I upload the Super patch from JCI or do I have to get it from my distributor?




That sounds like your platform daemon hasn't been ran for the 2.0 version.
:rolleyes:

Yup, that took care of that.

[hueyman]

Originally Posted by NINAX
That sounds like your platform daemon hasn't been ran for the 2.0 version.

Ninax, do you mean install the platform daemon? If not, can you explain the procedure to run it?

hueyman

[NINAX]

Ninax, do you mean install the platform daemon? If not, can you explain the procedure to run it?

Yes, that it.

Remember that if you're running multiple AX versions, that you have to run/install that version's daemon when you're going to work with it.

[NINAX]

Can I upload the Super patch from JCI or do I have to get it from my distributor?

Yes, you should be able to get it through an email.

[hueyman]

Yes, that it.

Remember that if you're running multiple AX versions, that you have to run/install that version's daemon when you're going to work with it.

Understood,
Thanks

[willf650]

Some comments/questions:



*I tried to enable the 2nd ethernet port, more of a test than anything. It locked up both ports, I had to go into the serial shell to disable the 2nd port to get it back.




I assume the FX60 is pretty much idenical to a Jace 6. You can use the second IP port but it doesn't have all features of port 1. I don't know the specifics off the top of my head but it has to do with some of the different network authenication features and options.

The reason you probably locked up your ethernet ports is because you assigned them in the same address range and subnet. Is this right? This won't work as the IP addresses need to be on a different subnet. I've been setting all my secondary ports to specific addresses to allow you to conect to the Jace with out having to get on the customers network with my computer as some of the IT guys are fine other are funny about it. What address for the secondary port is based on the address of the primary port. So if the the primary port it is set up as 192.168.1.XXX I set the secondary up as 10.10.220.250 or vice versa. I've been trying to get in the habit of doing the secondary port with XXX.XXX.XXX.250 so our company has a standard to connect to the Jace redaurdless of the primary port IP so we all ways have the "backdoor" in.

[t-reck]

I assume the FX60 is pretty much idenical to a Jace 6. You can use the second IP port but it doesn't have all features of port 1. I don't know the specifics off the top of my head but it has to do with some of the different network authenication features and options.

The reason you probably locked up your ethernet ports is because you assigned them in the same address range and subnet. Is this right? This won't work as the IP addresses need to be on a different subnet. I've been setting all my secondary ports to specific addresses to allow you to conect to the Jace with out having to get on the customers network with my computer as some of the IT guys are fine other are funny about it. What address for the secondary port is based on the address of the primary port. So if the the primary port it is set up as 192.168.1.XXX I set the secondary up as 10.10.220.250 or vice versa. I've been trying to get in the habit of doing the secondary port with XXX.XXX.XXX.250 so our company has a standard to connect to the Jace redaurdless of the primary port IP so we all ways have the "backdoor" in.

That's is exactly what I had done, and the backdoor entrance is why I wanted to test the operation. This particular site doesn't have a problem with me connecting my laptop, but some sites do get a little funny.