Alerton to AX

[Igotworms]

I was able to find some old submitals of a clients building. It looks like there is an alerton IBEX system in the building. I have never worked on these controls and the original contractor is out of the picture. I'd like to propose an integration option into AX. Is there anyway to bring this into an FX60? If so, has anyone accomplished this? From what I'm reading it doesn't seem to be the easiest thing. I'm also open to any other options/suggestions. Thanks in advance.

[noskilltech]

If you can get your hands on a BCM-TUX and the alerton software, it can be done. It is extremely time consuming though. Other than that, I don't believe there is any other option.

[kontrolphreak]

You would think that seeing Honeywell owns Alerton and Tridium they would develop a driver for the TUX protocol.

kontrol out

[CB_Matt]

There was a little disscussion a while back about developing the driver for this. I dont think that it will happen because these controls are being phased out now. If you can get your hands on the BCM-Eth, BCM-Pwr, and BCM-Tux, it would be easy to accomplish this. The controllers would be routed to the Jace through either Bacnet/IP or Bacnet Ethernet, your choice, and then they will discover as individual controllers. If you are dealing with App specific controllers, I.E. Tx-Vav, Tx-SA, then the points list will be the same for all controllers.

If they are programmable controllers, then you are going to need some help to reverse engineer the programming to develope the points list. Unless you are lucky to have some documentation that has this info.

[pault]

I will need VisualLogic to program BCM. And probably IBEX TDS to read programs from existing controllers in case there are no point lists available.

[noskilltech]

There was a little disscussion a while back about developing the driver for this. I dont think that it will happen because these controls are being phased out now. If you can get your hands on the BCM-Eth, BCM-Pwr, and BCM-Tux, it would be easy to accomplish this. The controllers would be routed to the Jace through either Bacnet/IP or Bacnet Ethernet, your choice, and then they will discover as individual controllers. If you are dealing with App specific controllers, I.E. Tx-Vav, Tx-SA, then the points list will be the same for all controllers.

If they are programmable controllers, then you are going to need some help to reverse engineer the programming to develope the points list. Unless you are lucky to have some documentation that has this info.

Easy if someone didn't write 5000 global ddc and ibex points in the apex.

[CB_Matt]

Easy if someone didn't write 5000 global ddc and ibex points in the apex.

This does not make it any tougher to do the swap. You will not need the Ibex points any longer, so they can go away. If they are application specific you will not need most of the global ddc, which was there mainly for display purposes.

[Igotworms]

Thanks for all the info. It looks like I'm going to propose a whole new control system.

[CB_Matt]

Thanks for all the info. It looks like I'm going to propose a whole new control system.

Good Choice.