Elevator Forum

Kone KCM831 Shaft C...
 
Notifications
Clear all

Kone KCM831 Shaft Comm Not OK

19 Posts
10 Users
0 Reactions
13.5 K Views
(@char-les)
Eminent Member
Joined: 17 years ago
Posts: 28
Topic starter   [#38637]
The building for this job had a major power failure from a windstorm and had no power for 4 days. Cartop battery was dead. Once power came back on the elevator will run on inspection, relevel at the floors but it will not take take calls from the car, hall, or controller. The Shaft Comm OK light is NOT on. We are getting the expected "14xx" fault codes but no other code. All of the FCB boards have the green Led and no fault lights. We unplugged the Hall CANBUS cable and got the expected fault code. Made sure the roll call was in the right direction. Several LON downloads to make sure. Position indicator works fine in the car. This job does not have a hall PI. Not sure what the difference between a 5-7-1 and 5-7-2 Lon download is but only performed a 5-7-1 Lon download. Checked all the cables between the FCBs. I believe we turned off the battery monitoring for now. Anyone have any other ideas or something we may have missed?



   
Quote
(@char-les)
Eminent Member
Joined: 17 years ago
Posts: 28
Topic starter  
Figured out the difference between a 5-7-1 Lon download and 5-7-2 Lon download. 5-7-2 is used when updating software without checking existing node software version. No software has changed so should we performing a 5-7-2 instead of a 5-7-1 Lon download?



   
ReplyQuote
(@bowtiedrooster16)
Reputable Member
Joined: 17 years ago
Posts: 279

   
ReplyQuote
(@char-les)
Eminent Member
Joined: 17 years ago
Posts: 28

   
ReplyQuote
(@john-jay)
Prominent Member
Joined: 17 years ago
Posts: 798

   
ReplyQuote
 MX4
(@mx4)
Estimable Member
Joined: 17 years ago
Posts: 226
 
Cartop battery will cause a 0169 fault and will shut the car down.

14** faults could be a number of things, are you working on resolve, mono, mini, eco etc?



   
ReplyQuote
(@char-les)
Eminent Member
Joined: 17 years ago
Posts: 28
Topic starter  
Checked the termination resistor and its ok. Not getting the 0169 fault as the battery monitoring has been turned off. We are working on an eco.



   
ReplyQuote
 MX4
(@mx4)
Estimable Member
Joined: 17 years ago
Posts: 226

   
ReplyQuote
(@hunter)
Eminent Member
Joined: 17 years ago
Posts: 14

   
ReplyQuote
(@char-les)
Eminent Member
Joined: 17 years ago
Posts: 28

   
ReplyQuote
(@lowoil)
Reputable Member
Joined: 17 years ago
Posts: 270
 
I think I've said it before here, sometimes you have to try multiple lon downloads and it then will it roll call and come up with shaft communication. Some cars can be finicky. 5-7-2 forces all nodes which is not a bad thing.

Last edited by lowoil; 12/23/24 09:45 PM.


   
ReplyQuote
 Kyo
(@kyo)
Active Member
Joined: 17 years ago
Posts: 4

   
ReplyQuote
(@char-les)
Eminent Member
Joined: 17 years ago
Posts: 28
Topic starter  
We have ordered a couple new FCB boards and will try things again once we are back on site. Hopefully new boards and multiple lon downloads will kick start it.



   
ReplyQuote
(@local8elev8rman)
Estimable Member
Joined: 17 years ago
Posts: 108

   
ReplyQuote
(@jadam)
Estimable Member
Joined: 17 years ago
Posts: 110
 
If you do a new shaft setup, the input from 30 + B30 must match with fcb borad as it counts in the lon download.
So if it counts the door zone sensor incorrectly you won't get your shaft com to work. I use hyperterminal to check when it's bugging me.



   
ReplyQuote
Page 1 / 2
Share:
Scroll to Top