Home Forums General Discussion Technical Questions Kone KCM831 Shaft Comm Not OK

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?

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?

5_7_2 is a forced lon download and is not recommended for 90% of applications according to Kone tech support

How critical is the cartop battery? Could it cause some of our problems?

Have you checked the 120 ohm !/2 watt resistor on the last FCB? it is the end of line terminating resister.

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?

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.

PM your email

Check 4-1 to see elevator operation mode.
Replace cartop battery if it didn’t recharge.
Check UPS is on and good.

We have ordered new FCB boards and will see what that is our problem

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.

Did you try doing a new shaft learn ?

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.

Shaft setup, 5-2 typically works for the shaft comm and to get rid of the 14xx faults.

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.

For some reason the shaft setup won't start. Drove the car down to the
lowest landing. 61U, 77N, 77S, 30, are lit. 5-2 set to 1, turned RDF to norm but car just re-levels and stops. What are we missing? Normally you would see the dashes and the car moved up the hoistway.

When we checked 4-1 it comes back as 4-1-10 OSS. Wońt go into normal. Is there a “floor table” that has to be set / reset

After replacing the dallas chip, programming the parameters again, it took a dozen tries to get the shaft learn to finally take and the shaft communication finally came on line Thanks for everyone who helped.

I have many Kone monospace elevators with LCECPUnc. This problem comes after 10-14 years up. The battery inside the NVRAM dies and NVRAM loses all parameters after turning off the power of an elevator. Chaft Comm led is one of the symptoms.