FX Server Setup

[techno98]

I am messing around with the FX server for the first time. I have my workstation and 2 fx 60s. When I do a search in the niagara driver of each fx60 I pick up the other fx60 but I never pick up my workstation which has the server software. Since I am using the same computer with the server software and workbench trying to set it up, can this be giving me a problem. Also does anybody have a step by step on how to set this up for future reference. Like I said this is my first time with this so maybe Im not explaing my self correct. But any kind of feed back will be greatly appreciated.

[MCP]

I may be confused on how you worded it but the workbench software is essentially the server so once you start a station and set it up to auto-start, it will run, restart after re-boots, etc without re-starting the workbench sofware (that part of it runs in the background as a service). The license file defines what it can and can not do. The difference is going to be that a FX20/40/60 comes with a station in it already and you will not have a station running in the sever when you first set it up.

Just create a new station and then login to the platform on the localhost and set it up to run/auto-start/etc. and start it. From there it will act pretty much just like the station in the FX?0.

We don't really use the FXApp stuff JCI adds into their flavor Jace and setting it up this way does not put it in the server so i'm not sure how to do that but it should be possible (or maybe not but we don't use it so i'm not sure).

[techno98]

This is where I get confused. When I originally set up a station I got to put the ip address of my fx60. Do I have to put the ip address of my workstation when i originally start my station. When I manually start my station on my computer and do a search from my Niagara driver it always fails and doesnt pick up my other fx60.

[justjohnson]

a station in a supervisor is the same type of thing as a station in a jace. Both places need to run a station. You need to setup a new station on the supervisor and then set it up to AutoStart like MCP said. Once the station is running on the supervisor you can then login to the station on the supervisor and doing a search for stations in the NiagaraNetwork should yield both of your FX60s. If they don't automatically pop up in a discovery (sometimes they won't if they are on different subnets), then manually add a new station, enter the IP address of the FX60, username and password. Then it should show online and in the points manager you should be able to do a discover of the points in the FX60 that you want to bring into your supervisor.

[techno98]

Thanks I added them manualy and now I see them. I got 2 questions the Fx server software I had to buy, was this needed so I can see the remote sations from my local stations or this could have been done without it also instead of taking individual points can I create a home page in my local station and hyperlink to individual units in my fx60 because I already have all the graphics set up at each fx60.

[MCP]

I have a few sites with multiple JACEs and no server. The graphics are setup to take you to the applicable jace. They were early AX setups and i could never get the passwords tricks to work so the first time you move from one Jace to the other by clicking a graphic button, you have to login to the 2nd JACE but other than that it is seamless.

The server is really only necessary when you need to to collect a huge amount of trend data for the most part. There are other benefits to having them such as centralizing everything when there are many JACE panels.

[techno98]

I agree with you. This job only has 2 fx60. I am going to make 1 fx60 my main home page and just link my points between the 2 fx60. So you've done this before, anything I need to look out for that might confuse the building operators.

[freddy-b]

I agree with you. This job only has 2 fx60. I am going to make 1 fx60 my main home page and just link my points between the 2 fx60. So you've done this before, anything I need to look out for that might confuse the building operators.

No, No, No.....Graphics/Schedules on server. Subscribe your field points from each jace into niagara folders via niagara network...and graphics will be linked to these suscribed points.
Schedules in Server, then discovered at JACE via niagara scheduling
Alarms and histories in JACE and exported to server...rolling with low counts in jace,..server count can be infinite.

Jaces with Servers dont need any graphics in them whatsoever. Extremely important with FX-40's and good practice with 60's.

[freddy-b]

Thanks I added them manualy and now I see them. I got 2 questions the Fx server software I had to buy, was this needed so I can see the remote sations from my local stations or this could have been done without it also instead of taking individual points can I create a home page in my local station and hyperlink to individual units in my fx60 because I already have all the graphics set up at each fx60.

To transfer existing graphics that are already made in a Jace to a Server takes about 20 seconds a piece.

Copy the PX's from JACE to Server. Then go to PX text editor and find and replace..anything linking the path in the jace to the new path in the server.
While leaving the point name in tact.
Example: station:|slot:/Drivers/JciN2Network_COM3/UNT_12/points/AUDITORIUM_T/out/value
Would become: station:|slot:/Drivers/NiagaraNetwork/High_School/points/High_School/Pneumatic_Zones/AUDITORIUM_T/out/value



Repacing first example with second with find and replace.

[techno98]

Freddy I will try it and let you know. thanks

[freddy-b]

Freddy I will try it and let you know. thanks

Just tinker with it, and you will become fast at it. If you know a supervisor will be on the job. Dont even bother with this step and create the graphics in the supervisor from the get go..
Also in niagara point folders..you can put suscribed points from multiple controllers in the same folder or the same point in many folders..ex: OA_T. for a more organized tree based on area or type. This will make make NAV file creation a drag and drop deal.

Also...as a side note... have all the names and facets the way you want them before you suscribe the points to the supervisor...so they follow seemlessly and stay consistent on the JACE network, and your suscribed points in the supervisor.
A little time setting things right from the begginning will save you lots of time later.

Also...stay away from dashes and spaces in the names. Underscores are your friend. This saves you from the unwanted characters in your alarm and history paths...they work, but they look like crap.

Also add a string writable in each controller in the JACE before you subscribe them. Call it ID or what ever you want..then add this point to the header of your graphic. Then add this string to your alarm and history path. Here is a example with ID as the string name. It will relativize just like any other point
%parent.parent.parent.points.ID.out.value%/%parent.name%
This will allow a super easy way to edit the name of a room/description.. with the set command right from the graphic. and histories and alarms will add that to the description in the reports. This will allow you to maintain print descriptions for your benefit and futurw print searching for anybody...and the customer a easy way to rename them to what makes sense to them.

"Set" the string writable to (Sysints_Office).

Loytec/Penthouse/VAV_22/Roomtemp alarm may not make sense to them, but Loytec/Penthouse/VAV_22/Sysints_Office/Roomtemp High Alarm will.


Its the best of both worlds.