Results 1 to 6 of 6
Thread: Tridium CCN driver
-
01-04-2013, 06:44 PM #1
Regular Guest
- Join Date
- Nov 2009
- Location
- Boston Ma
- Posts
- 19
Tridium CCN driver
Can anyone tell me if they have installed and commissioned the Carrier CCN driver in the Tridium Product ?
Did you have any issues getting the network to Discover ?
We have setup per the Tridium driver config manual and can not establish communication on the CCN .
We have the service tool and confirmed correct bus and element addressing.
Not sure if we are missing anything ?
Thank you in advance
-
01-04-2013, 07:06 PM #2
Regular Guest
- Join Date
- Mar 2010
- Location
- Maryland
- Posts
- 13
Sounds like a software revision conflict. Thats what make's the geeky world spin.
-
01-04-2013, 07:38 PM #3
Professional Member
- Join Date
- Dec 2011
- Location
- Charlotte, NC
- Posts
- 39
I have used it without issue with both 3.6 and 3.7. Make sure you set the network number for the network you are joining, and set a unique node address. Outside of that, discovery should just work.
-
01-04-2013, 07:49 PM #4
Regular Guest
- Join Date
- Nov 2009
- Location
- Boston Ma
- Posts
- 19
We set the bus as 0 ( Zero)
and the element as 1
we have it on a demo / training board so its all right in front of us....
The jace was set with an address of 0-230
the ccn bus plus term was set to + on the jace 485 card and - to - and g to c
no bus or eol terminaters required ?
-
01-04-2013, 08:08 PM #5
Professional Member
- Join Date
- Dec 2011
- Location
- Charlotte, NC
- Posts
- 39
Can you discover the CCN device from NST? Baud rates the same? And when I said network and node, I meant bus and element, but you caught that...
-
01-04-2013, 08:10 PM #6
Professional Member
- Join Date
- May 2004
- Location
- SE Pennsylvania
- Posts
- 508
Set the Jace bus 0 or whatever your devices bus is and the element to 238, it needs to be higher than the highest device address. 239 is reserved for Comfort View and Service Tool. Baud rate must be 9600.


Reply With Quote