JCI NAE to Trane Intellapak LON Integration

[harley2003rkc]

We're looking at adding 4 more Intellapak RTU's with LON cards to the existing LON trunk on an NAE. Does anyone have any experience with this intergration? Can the points be auto discovered or do they have to be manually put in? Did the install go well or was it troublesome?

[NickDeal]

In my opinion they are a real pain in the butt. First make sure you have the original LN-Builder database. Assuming JCI installed the first set. If you don't you will need to build one with all the new units, the old units and the NAE. Once they are commissioned in LN-Builder I'm not sure if you can auto discover the devices I'm pretty sure you can, but you can definitely auto discover the points.

That is the beginning of the problem. Unless Trane has changed their system when you auto discover the points you will have duplicates of most of the points and you will have some points that don't work at all. This is due to the way Trane does their LON systems. The problem with the NAE is that you cannot have 2 duplicate identifiers. So when you do the auto discover you will have to go through and change the identifiers of the duplicates. I usually just add a 1 to the end of the point. Then just go through and delete what isn't working.

[harley2003rkc]

I have no idea what LN Builder is. We have a jci server workstation. I can see the the Lon trunk on the NAE. We're looking to add four additional RTUs to the same trunk. If all else fails. Can we create controllers and points manually.

[harley2003rkc]

Since I know people find these posts while searching for info, I thought I would update this. I found a manual from JCI that I think clarifies everything I was looking for. Although I would still like to here from others who have completed this integration. I don't think I need LN-Builder on this site because I'll be working through the Workstation, and the Trane RTU's will be factory configured. I should be able to get the resource files from Trane since this integration is for them.

JCI LON Integration Manual

[scrooloose]

I would have to think the duplicate points you see is specific to a NAE.

When i discover those points with a Jace or Summit they come in just fine.

[NickDeal]

Since I know people find these posts while searching for info, I thought I would update this. I found a manual from JCI that I think clarifies everything I was looking for. Although I would still like to here from others who have completed this integration. I don't think I need LN-Builder on this site because I'll be working through the Workstation, and the Trane RTU's will be factory configured. I should be able to get the resource files from Trane since this integration is for them.

JCI LON Integration Manual

You will need LN-Builder to put the Trane units on the same subsystem as the other units and the NAE. I have integrated these units to NAEs before and was unable to to it without LN-Builder or some other LNS Database tool. JCI Tech Support told me that LNS has to be used for the NAE to communicate with devices on the LON trunk. You will need the resource files for the NAE to be able to read values from the devices.

LN-Builder and the database should have been included with the original installation package.

[NickDeal]

You will need LN-Builder to put the Trane units on the same subsystem as the other units and the NAE. I have integrated these units to NAEs before and was unable to to it without LN-Builder or some other LNS Database tool. JCI Tech Support told me that LNS has to be used for the NAE to communicate with devices on the LON trunk. You will need the resource files for the NAE to be able to read values from the devices.

LN-Builder and the database should have been included with the original installation package.

In addition to the device specific resource files, the LONWORKS Integration object
requires the STANDARD.TYP and STANDARD.FPT resource files, and a
NVConfig.dat file. This NVConfig.dat file is created automatically, but you need
to update it with the correct configuration data using a network configuration tool,
such as LN Builder. See Defining an Engine on the LONWORKS Trunk in the
Detailed Procedures section of this document.

This is from the integration document.

[roadgear16]

The points are duplicated on the LCI-I, half are for SCC and the other are for DAC, so which ever profile you have will determine which points will have valid data.

[MatrixTransform]

from what I understand LON in an NAE is painful. Havent done it but heard the rumours

my recommendation is to use a JACE with a lon card and a Bacnet Driver and stick in between the Trane and the NAE.

...actually why dont you ...

.... nah I wont say it!

[MatrixTransform]

...
requires the STANDARD.TYP and STANDARD.FPT resource files, and a
NVConfig.dat file.

...that's what I mean by painful ...only JCI does LON so ... er beautifully!

[ewang]

The points are duplicated on the LCI-I, half are for SCC and the other are for DAC, so which ever profile you have will determine which points will have valid data.

They expose all of these points? How do they have enough room? Aren't most LON devices limited on the number of variables? (50ish?)

Can anyone post a screenshot of the duplicate's? I am curious. Thanks!

[harley2003rkc]

Hanging a Jace on the wall is our backup plan if this gets to complicated or painful.

[scrooloose]

They expose all of these points? How do they have enough room? Aren't most LON devices limited on the number of variables? (50ish?)

I know the mp580 has over 600+ points. I never heard of a limit on variables.