ALC to Jace201

[bradgreen80]

I am looking to integrate a existing ALC system into a Jace 201 NiagaraAX system. The actual system installed is LGE, which is a rebranded verision of ALC. They are using M-Line and S-Line controllers to control Lighting, HVAC and other loads throughtout the building. I have never intergrated with ALC before from NiagaraAX. I am wanting to leave the existing system in place from control and gain as much read/write access to the system?

Does anyone have any information on Driver interfaces, and or gateways into the Arcnet communications that is resident at the LGE routers?

Any information and/or links are appreciated.

Thanks

[kontrolphreak]

As stated in numerous threads, unless the ALC was specifically coded for BACnet integration the chances for a smooth integration are slim if possible. The ALC points have to be enabled for "Network Visibility" for third party integration.

kontrol out

[MaxBurn]

Is it running EXEC6 or EXECB? Is it WEBctrl or supervision?

If EXEBB WEBctrl should be an easy task to go through and note the points you need, turn on network visibility and run a point list report. I'm guessing that's not the case though?

[bradgreen80]

I do not have any information on the system it is running. Is there a way that I can tell from the installed date? I do not have access to the system remotely.

[MaxBurn]

Not really. The LGE and M line modules are dual EXECB or EXEC6 modules, can be either. No idea on the S line modules, never seen them.

Do you have the ability to work with Webctrl? If so then I would look at the possibility to switch this thing over to execb so you can integrate to it via bacnet fairly easily but if it isn't already bacnet/execB you are rebuilding the system software from scratch.

[CTRLman]

The LGE is a standard, but aging ALC router. It is exec 6 or exec B as are the M line and S line controllers. So you can upgrade them either way and run the natively under WebCTRL. The network visibility of the points is selectable so if you dont know how to turn them on, you probably shouldn't be attempting an integration in the first place. All the BACnet points are BACnet/MSTP discoverable so even if you dont know whats there, you can find out. You don't even need WebCTRL to run them. They are BACnet compatible modules so If you have a BACnet/IP front end of any type you have all the functionality that was originally written in to them. There in lies your problem. If the original application engineer didnt use any BACnet points, your going to have to re-write all the control programs, which meand your going to have to have WebCTRL anyway.