CCN AX

[mechmike2]

Anyone know how many CCN devices can be put on a Jace 6, Jace 2. Just using the supplied RS-485 port for now, no option cards. Looking to put a number (13) of E-series RTUs on a Jace and wondering if I can get away with a Jace 2.

[BostonCtls]

Anyone know how many CCN devices can be put on a Jace 6, Jace 2. Just using the supplied RS-485 port for now, no option cards. Looking to put a number (13) of E-series RTUs on a Jace and wondering if I can get away with a Jace 2.

Can you tell me if you got this ccn network communicating ?
We just purchased a CCN driver and followed all the steps in the Tridium ccn driver manual and could not get the network to discover ?
Can you tell me if you ran into any issues initially and what you did to get the devices to discover ?

[mechmike2]

I did get it to work. It was a demo Jace I got from our supplier to check out integrating some E-series RTU's. At first the Jace would not discover anything, the jace had a Zig-Bee wireless receiver installed on it, once I took the Zig-Bee off it worked fine. Discovered E-series hooked up to some 3V devices also. I'll try attaching screenshots(2) of how driver was set up.

[BostonCtls]

I did get it to work. It was a demo Jace I got from our supplier to check out integrating some E-series RTU's. At first the Jace would not discover anything, the jace had a Zig-Bee wireless receiver installed on it, once I took the Zig-Bee off it worked fine. Discovered E-series hooked up to some 3V devices also. I'll try attaching screenshots(2) of how driver was set up.

Could not see to clearly the setup screens.....but i think we were pretty close to what you had.....
Tell me we wired the ccn bus to a 485 that existed and had a bacnet bus attached to comm3....
there would be no issue connecting the ccn bus to the 2nd port on this card ?

and you terminated + To + , - To - and did you connected the 3rd conductor ?

[mechmike2]

I had an issue with Zig-bee on an option slot.
I was using the on-board Jace RS-485 port so don't know about dual option card issue if any. Maybe try putting whatever is on the Comm 2 Jace port to the other rs-485 port on dual option card. What Jace are you using?

[BostonCtls]

I had an issue with Zig-bee on an option slot.
I was using the on-board Jace RS-485 port so don't know about dual option card issue if any. Maybe try putting whatever is on the Comm 2 Jace port to the other rs-485 port on dual option card. What Jace are you using?

We have an FX20.....this is a training board in our office.....theres a N2 bus with an FX16 ad FX_VMA.....a Bacnet bus on one port of the 485 card with PCG and a PCV on it.....we just added a CCN driver and hope to connect to a Carrier 6400 and CID vav controller.....

So you think try to move to com2 on the base board ?

[mechmike2]

Don't know comm port designations on JCI jaces but I assume that comm port 2 is the on-board rs-485. As far as I know you can not assign the jace ports you have to use the ports as they are assigned in the jace. Comm port 2 is the rs-485 port that comes on the Honeywell jaces I use unsure if JCI is different, wouldn't make sense but wouldn't be surprised. Check the literature and be sure ports are assign properly?

[dracula]

Are you using BACnet MSTP to integrate into the RTU's CCN devices?
I was not aware that Jace's could directly tie into the Carrier RTU CCN buss, which is a EIA485 buss, but the data packets are
CCN properitey not conforming completely to EIA485 rules.
I am not a Jace expert (yet), but I do have extensive skills on BACnet MSTP and IP integration, and CCN integration.
If the existing RTU's have CCN Controls, and no "Carrier CCN or Carrier i-VU BACnet" devices installed, you may need to get some
Carrier BACnet Translators boards, or a Carrier i-Vu UPC Open Protocol converter onto the RTU's and then use someone familiar with mapping CCN points to BACnet points, then you can interface via BACnet MSTP.

This can be a bit tricky, and I do integration every day. Carrier CCN points have refresh and write limitations like almost all legacy controls do, that can greatly limit some of the integration control requirements.

Let me know if you need more info.

Respectfully submitted

Drac

Just food for thought.

[mechmike2]

With the CCN AX driver you can connect directly to the CCN bus. Depending on the license (CCN or CCN1) you can get access to Status, Setpoint, and Schedule points or those points along with Maintenance, Config, Service.

[CountryBumpkin]

I have successfully integrated the CCN driver into AX. I had a problem with the CCN driver working after I upgraded the Jace to 3.6.47 and had to revert back to 3.5.39 to get it to work again. I have not tried it with 3.7 but if you are using anything newer than 3.5.39 you may want to revert back just to see if it helps.

[ControlY0urMind]

I have successfully integrated the CCN driver into AX. I had a problem with the CCN driver working after I upgraded the Jace to 3.6.47 and had to revert back to 3.5.39 to get it to work again. I have not tried it with 3.7 but if you are using anything newer than 3.5.39 you may want to revert back just to see if it helps.

I just did one today with 40 devices on a Vykon 3.6.47 JACE-6 with absolutely no problems at all.

[hvac69]

With the CCN AX driver you can connect directly to the CCN bus. Depending on the license (CCN or CCN1) you can get access to Status, Setpoint, and Schedule points or those points along with Maintenance, Config, Service.

I just did one today with 40 devices on a Vykon 3.6.47 JACE-6 with absolutely no problems at all.

The last time I checked with Tridium the CCN full driver was not available and only schedule, status and setpoint tables would be able to be discovered. I ran a test station and confirmed this on VAV terminal controllers. Have they released the full version?

[ControlY0urMind]

The last time I checked with Tridium the CCN full driver was not available and only schedule, status and setpoint tables would be able to be discovered. I ran a test station and confirmed this on VAV terminal controllers. Have they released the full version?

I don't think so. It was not even mentioned when we purchased the license.