Home Forums General Discussion Technical Questions Otis Elevonic-R NAV fault

MCB board does give the reason for abort

Are you in the states ? I've not heard Americans refer to controllers as MCS before .. That's how we refered to controller in the u.k ..mcs 120 , mcs 220 etc... The reason I ask is the process is different if your using the European controller for example do you have NTSD and ETSD vanes and switches ? On the American controllers if it aborts a learn run it will give you a reason for this in the MCSS logb ( M-2-2-2 ) . Not in the drive .

I'm sure even if your using a controller from Berlin you can still check the M222 log for reasons a learn run is aborted

Am using the controller from Berlin.
You're right the error log is in Motion control board not really the drive.

What did the MCB log say ? I've not worked on European controllers for 9 years , we used the 220 back then for traction . Guess the 321 is similar ..

please and please I also need help with my lift. ‎Every single help on my Otis Gen2 will be highly appreciated.  my Otis lift motor suddenly start to vibrate and the whole car shaking seriously on stopping. I adjusted the motor encoder and tested it on normal  run just to see if it okay. i didn't  try to do the learning because it started working fine again just as usual. so we start using the lift again, so after some few runs, the lift stopped working again. the car got stocked at the ground floor. the lift was shotdown. the event log and the error codes shown on my service too is as follows: 912- No floorInfo, 528-profile err, 725-UCM BrkBlock, 400- Brake S1 SAS, 909-CAN BusOff, 902-CAN err, 000-power on
‎