What's the best way to integrate Carrier CCN to a LON network?

[engmgr]

I have a CCN network with a small boiler room system, one RTU and 16 FP vav boxes. I'm looking for an integration solution that won't cost a small fortune to put this on an existing LON network. The CCN was installed in 2002 if that matters.

Thanks!

[noskilltech]

I'm looking foreward to hearing responses on this. I can't even get CCN to interface reliably with a Carrier chiller, let alone to another communication protocol. :D

[crab master]

I've put gotten data with LON card in multiple Carrier chillers and RTU's. A few of my gripes is that they don't follow the LON spec when I've worked with them. Occupancy input is a SNVT Switch not a SNVT Occupancy. Send it a 1 for occupied and a zero for unoccupied.
The other thing is point names. Basically from what I've gathered is it is up individual that maps the points across on how discriptive they are going to be on the point names. I hate it when I get a list nvitemp1, nvitemp2,...., nviDO1, nviDO2, nvo temp1, nvopress1... and then they don't tell me what each one is.

[Ausccn]

There is no easy way to do it. If you were to use the LON equipment interface from Carrier then you would need one interface for each controller on the CCN which could get expensive. Another option if the existing LON network is Tridium you could try and get the CCN driver from Carrier but as far as I know it is only R2. Next would be to put an i-Vu web box onto the CCN which would supply BACnet/IP and then get a gateway to goto LON!!! All seems to be pretty messy.

Aus..

[Chris_Worthington]

Another option if the existing LON network is Tridium you could try and get the CCN driver from Carrier but as far as I know it is only R2.

Aus..

I have done the CCN driver on R2 to OBIX to AX and found that to be slow and quirky on the integration :rolleyes:

Will be beta testing the CCN driver for AX next week :eek:

Anyone out there had the chance to test this yet? and if so, any issues noted??

[engmgr]

Chris, do you know when the CCN driver for AX will be released? Please let us know how the Beta test goes. Thanks!

[sysint]

Maybe with a system this small you should price replacement for LON controllers.

Then you can start to pitch the Proprietary Carrier controls. The RTU could receive their LON card (tenuous), the FP's I'd retrofit with LON ASC controllers and since Carrier has a programmable for the boiler controls, eventually I'd pitch that also. EDIT: Essentially, you should be able to find replacement controllers that work with all your existing sensors and actuators. You can probably do that with the Carrier FP's also because Carrier claimed they invented the direct coupled actuator already in the 90's...

By the time the local AX contractor is done, your costs will be similar and really, how did you tie into your existing LON network? Or maybe consider a field server instead.

I guess some questions is why is this system installed? Did you inherit it? Does it work? If it works, why not just leave it alone? How is your existing LON network controlled?

[engmgr]

This is a college campus and we have Distech Controls w/Tridium AX Jace panels. The Carrier system (in a different campus building) is to be integrated as a change order to the base project.

We have no problem changing out the FPB controls, it's the RTU that is the headache as it has a CCN PIC controller and as far as I can tell the RTU will not accept a LON card. The RTU is a VAV unit with factory wired VFD's on the supply and exhaust fans.

We're going to have a look at the RTU on Wednesday, if we can figure out EVERYTHING wired to the PIC then perhaps we could just swap out the controller. I hate to do that because if they lose a compressor down the road we'll get blamed.

As you know, it's always the control guy's fault. :mad:

[sysint]

Well, if you already have AX, this is the way to go.

I understand about the warranty with the RTU. It's interesting to me our local Carrier rep over the years hacked up their factory controls regularly to get it to do what they wanted...

Anyway, I still think you replace controllers and reuse sensors as the best way to go. Then you avoid the hassles of the driver which simply puts off the inevitable with CCN. It's on the way out even for Carrier. Why prolong it?

Also, maybe consider ebay-in the 6400 (probably for boilers) and the FP controls. At least you get a small return on a bad investment.

[s2k008]

There is no easy way to do it. If you were to use the LON equipment interface from Carrier then you would need one interface for each controller on the CCN which could get expensive. Another option if the existing LON network is Tridium you could try and get the CCN driver from Carrier but as far as I know it is only R2. Next would be to put an i-Vu web box onto the CCN which would supply BACnet/IP and then get a gateway to goto LON!!! All seems to be pretty messy.

Aus..

What is this Gateway you speak of?
I have a Carrier "Chiller in a box" with the I-vu web box that I would like to somehow integrate into my existing r2 on site. In the r2 station I added a folder and brought in the I-vu object. It's been a while but I think I remember doing this via the IP address of the I-vu box. Anyway, I'm not able to link any inputs or outputs to the object in order to get values or link external start/stop commands. Any thoughts? Do I need a driver or some kind of hardware in between in order to properly integrate with my r2 Unc?

[davedmc]

Guys, I've been looking for a solution to the CCN to AX Platform for a while. We have worked with a Driver Delveloper that created a Trane UCM Driver. I know there is talk of someone testing a CCN Driver and I'm looking for a Carrier System Upgrade solution and would like to use Tridium. I've played the the Carrier I-vu and have successfully created read/write points Bacnet/IP from AX to CCN Stuff. Anyone have info as to where or when the magic will happen!?

[engmgr]

Okay, we've decided to buy a Carrier 33CNTRANLON Lonworks Carrier Translator to pick up the RTU and we're going to replace the 16 box controllers with new LON controllers.

We'll avoid all RTU internal wiring this way other than the com bus. Also, we'll be able to dump the existing CCN workstation.

Thanks for all the replies!

[Ausccn]

What is this Gateway you speak of?
I have a Carrier "Chiller in a box" with the I-vu web box that I would like to somehow integrate into my existing r2 on site. In the r2 station I added a folder and brought in the I-vu object. It's been a while but I think I remember doing this via the IP address of the I-vu box. Anyway, I'm not able to link any inputs or outputs to the object in order to get values or link external start/stop commands. Any thoughts? Do I need a driver or some kind of hardware in between in order to properly integrate with my r2 Unc?

The gateway I was thinking about :-

http://www.csimn.com/CSI_pages/BBIPXL.html