HVAC-Talk: Heating, Air & Refrigeration Discussion banner

Honeywell CBUS Lon integration

4.5K views 5 replies 3 participants last post by  Milkman Spawn  
#1 ·
I am trying to integrate a building consisting of a SymmetrE front-end, 2 XL5000(or XL500?) type controllers, and dozens of XL10 terminal controllers with everything wired LON. There are 'point servers' on the front end for Lonworks and Excel5000. The front end computer has interfaces for Cbus and Lonworks. I'm really not familiar with Honeywell's network architecture or their controller compatibility. My first instinct is that this is a normal LON integration, but I was unsuccessful using a test Jace to pull in devices. Others have told me that although it is LON it is possibly still honeywell's proprietary cbus protocol over lon. How can I tell?
I recently worked on a cbus integration using the EasyIO mig tool and the wiring was RS485. I also know that Ive had XL10s on a normal Lon network before. Are there different flavors of XL controllers based on the protocol? The manual I found for the controller mentions "E-bus" :confused:

Can someone please school me on Honeywell's networking architecture, protocols, hardware generations, etc. so that I know what to look for and can figure out how to integrate it?

Thanks!
 
#2 ·
If the XL500 controllers have the CBUS\ Lon com module you are still going to have a problem bringing them in. You would need the project files and the CARE software to create the points in the XL500 as Lon points.

You would probably be better off using the CBUS driver, or if there are only two controllers and they are XL50's and not XL500's you might just consider replacing them with a controller of your choice and rewriting the program for these.

That system is going to have an LNS database that CARE generates and creates an unique domain for the Lon network. I would use the Lon utility manager identify feature and hit the service pin on one of the XL10 controllers and that should give you the domain that the controllers are on.
 
#4 ·
Is there anything special about the XL10 controllers that prevents me from bringing them in as regular lon devices? If I isolate them from the two XL5000 controllers could they be discoverable to a Jace? I dont have the tools or knowledge to muck around around with settings within the honeywell controllers themselves.
 
#5 ·
You should be able to discover them as they are once you set your Lon network on the Jace to the domain they are on.

Use the identify function like I explained in the previous post to see what domain the controllers are on. Then go set the domain on the Jace to be the same and try a discover.

Are you using a Honeywell or Vykon Jace or some other brand. I believe the lon honeywell ax wizard will work in a Vykon Jace.
 
#6 ·
I will have to try the identify function next time I am on site. My test jace is honeywell, but the one being installed will be Talon.

Also, since I dont really know the difference between XL5000, 500, 50 etc, I have the part #s for the only controllers I can find on site that are NOT XL10s. There is an XCL5010 with 5 "XFL..." I/O modules, and an XFC3A06001. These devices all show up under the Lonworks pointserver's controllers. There are two controllers listed under the Excel5000 pointserver("EXCEL5000@1@2@@", "XL500 SMART") but I dont know if these are:

a. devices that are also listed under Lon
b. devices that have been decommissioned
c. devices that are hidden somewhere in the building that we can't find.

It sounds like we will at least be able to pull in the XL10s though, which is my main concern since the eventual plan is the replace the other controllers.
 
You have insufficient privileges to reply here.