Results 1 to 13 of 17
-
04-03-2009, 08:18 AM #1
Professional Member
- Join Date
- Feb 2008
- Location
- Jerzee
- Posts
- 32
Trane LCI-I Lon interface for I-Pak help please
Have a stand alone 75 ton RTU with a LCI-I Lon-Talk comm. interface, all com. lights ok on LCI-I board except for red service light flashing every second. Indicates LCI- I is unconfigured. Intergrating with Honeywell WEBS AX. Have A Jace 600 and 30 xl10 vav controllers. Tried all different ways to discover the LCI-I and no luck. Started a new station hooked up directly and tried different Domain Id and length. No problem communicated to xl10.
-
04-03-2009, 10:31 PM #2
Professional Member
- Join Date
- Feb 2007
- Posts
- 239
If its unconfigured, then it thinks its a toaster or a washing machine....
you cant discover it no matter what you do, it must be flashed back with the LCI code
-
04-03-2009, 10:46 PM #3
Regular Guest
- Join Date
- Oct 2007
- Posts
- 12
You need Trane's Rover software to flashdownload to lci
-
04-09-2009, 10:07 PM #4Build it and it will break. Fix it and it will work. Ignore it and will cost more. Patch it and it will get worse. Cross the bridge before the flood.
-
04-10-2009, 07:55 AM #5
The 'contractor version' is the same as the 'tech version'. All the software exists on the disk. The only difference is the licensing. The software is licensed to the machine. Licensing will turn on any of the applications of the software. 'Looking' at a copy will not help you without a license.
"Controls is a lifestyle not a job" -klrogers
-
04-11-2009, 07:46 PM #6
Ok then. Does trane make it so that only trane can get the full license?
Build it and it will break. Fix it and it will work. Ignore it and will cost more. Patch it and it will get worse. Cross the bridge before the flood.
-
04-11-2009, 07:57 PM #7
No, $ get it done.
-
04-11-2009, 08:06 PM #8
We dont do enough with trane to invest any more $. In fact due to the issues we have had with their lon lci junk, we no longer want to install any of their rtu's that are going to be integrated. I sure hope they fix all of their reliability issues.
Build it and it will break. Fix it and it will work. Ignore it and will cost more. Patch it and it will get worse. Cross the bridge before the flood.
-
04-11-2009, 08:38 PM #9
Curious what 'issues' you had? I have never had a 'reliability' problem that I am aware of. Have integrated many IntelliPaks with LCI cards.
"Controls is a lifestyle not a job" -klrogers
-
04-11-2009, 09:19 PM #10
Banned
- Join Date
- Mar 2006
- Posts
- 3,641
Tranes "Lon reliability issues"...were in the beginning and possibly are still because they don't admit and/or rectify for the undisciplined/incorrect topology....Wrong wire..etc it was basic butchering of the install from the start at the core level on early comm5 jobs. They have manned up and made it right here and there...but not everywhere.
Once that is corrected...I have had not noticed anymore issues from Trane than anyone else.
-
04-12-2009, 08:37 PM #11
Still have issues with points not reading properly. Vfd running and maintaining good static but reporting 0%, a whole slew of points doing the same thing, have even plugged in with rover to see exactly what it is doing and got the same results. The biggest issue I have had is the fact that Trane has not at all been cooperative in getting these issues resolved. Nope no more trane, if you can not even support your product enough to fix the glitches that any product is going to have than I have no use for it.
Build it and it will break. Fix it and it will work. Ignore it and will cost more. Patch it and it will get worse. Cross the bridge before the flood.
-
04-12-2009, 09:08 PM #12
Permanently Removed
- Join Date
- May 2002
- Posts
- 9,564
-
04-15-2009, 09:58 PM #13
"unconfigured" means logically unconfigured, as in the lon configuration. You need to use your network tool/manager to re-assign the NID/dsn etc...
This doesn't mean that the board thinks it is a "washing machine or toaster", it is still an LCI-I.
This can happen if you have added the controller to a network, and then held the service pin in for 10+ seconds, also in rare occasions I've seen power issues cause this.


Reply With Quote

