Codigos de Error Miconic MX-GC

OPERATION: Errors
Range Section
Contents
0...149 Travel Control
150...199 Variodyn E
200...299 Door Control
300...399 Varidor70 Door Drive
400...599 Lift
600...699 MC PVF
700...739 MC PVEC
740...799 Magnetek
800...899 800_899_Varidor35_Door_Drive
900...999 IO
1000...1199 CPU
1200...1249 LON
1250...1299 BIO2
1300...1349 1300_11349_CAN
1400...1499 VF
1500...1999 Travel Control Ext
2000...2099 2000_2099_Load_Measurement
2100...2299 2100_2299_MOSIS
2300...2499 2300_2499_SALSIS
5000...5099 5000_5099_Remote_Monitoring
8000...8099 8000_8099_Remote_Alarm
9000...9999 9000_9999_Status
INVENTIO AG This design and information is our intellectual property. It must without our written consent
Restrictions CH-6052 Hergiswil neither be copied in any way nor used for manufacturing nor communicated to third
parties.
0...149 Travel Control
No. Section
Contents
0000 No Event
0001 NormalStop
0002 ExceptionMC
0003 NoKSE_STDSTL
0004 InvldMovement
0005 SH_on_STDSTL
0006 SB_on_STDSTL
0007 SH_Fault
0008 SB_Fault
0009 KB_Fault
0010 FC_Fault
0011 FC_Block
0012 DirectionErr
0013 OverSpeed
0014 UnderSpeed
0015 NoTargetLow
0016 NoTargetUp
0017 OverSpeedKSE
0018 NoLowerKSE
0019 NoUpperKSE
0020 PositionLost
0021 HigherPrio
0022 MaskErased
0023 JHC_Pressed
0024 JHC1_Pressed
0025 JHSG_Pressed
0026 JHR_Pressed
0027 JHM_Pressed
0028 OverTempMotor
0029 TripBlocked
0030 NewTripBlockd
0031 PrepNewDest
0032 PrepClearDest
0033 RelvNewDest
0034 SH_Timeout
0035 FC_Timeout
0036 Timeout Preparing
0037 CarAtLevel
0038 TargetLost
0039 NoDirRelv
0040 NoPHS_Learn
0041 ErrTachoFact
0042 LowKSE_Low
0043 LowKSE_High
0044 UpperKSE
0045 NoFloorTop
0046 ErrFloorTop
0047 ErrReleveling
0048 InvldTripType
0049 ErrFloorCTP
0050 NoDistRelv
0051 ZeroParam
0052 OverflowCTP
0053 NoSTR_Com
0054 PCT_Checksum
0055 NoMCR_Com
0056 CarNoStop
0057 MCR_NoStop
0058 SH_NoStop
0059 SingleReset
0060 DoubleReset
0061 RSE1_Fault
0062 RSE2_Fault
0063 RSE3_Fault
0064 PHS_Fault
0065 PHNR_D_Fault
0066 NoGetAnswer
0067 KUET_Fault
0068 SGRB_Fault
0069 SBNH_Fault
0070 SW_Warning
0071 SW Error
0072 Safety 110V
0073 Safety SPT
0074 Safety KNE
0075 Safety RTS
0076 Safety End
0077 LM_PrintsErr
0078 LM_NoCommiss
0079 Topt_Fault
0080 OverTempMCR
0081 TripV_Tacho
0082 NoSupply12V
0083 NoSupply24V
0084 DMS_Spoiled
0085 LM_ComErr
0086 RUET_Fault
0087 RTSC_Fault
0088 TachoFault
0089 TripTimeExp
0090 StopOverFault
0091 SMPB_Fault
0092 REC / RH HW Failure
0093 AccessSwitch
0094 DoorLockFault
0095 ETSL_Overspeed
0096 ETSL_VaneError
0097 ETSL_DeviceError
0098 COM_Busreconf
0099 RSK_Fault
0100 RFE_Fault
0101 RTRT_Fault
0102 RKUET_Fault
0103 HighSpeedStop
0104 CDOOR Bypass
0105 SDOOR Bypass
0106 PHASE Loss
0107 Pit Oil Switch
0108 Over Temperature Oil
0109 KSE Failure
0110 Motor Overload
0111 No Floor Slowdown
0112 Pressure Switch
0113 Thermistor Failure
0114 Anti Stall Failure
0115 Duty Cycle Regulation
0116 KLU Fault
0117 KLD Fault
0118 NodeAlive
0119 Node Dead
0120 Door Lock Failure
0121 Switch Fault
0122 KSE Fail 2
0123 EV Error
0124 EV Shutdown
0125 EV Event
0126 Wrong hardware
0127 SI_Error
0128 LOWER_KSE_LOW_SYNCH
0129 EQ_Midpoint_Fault
0130 PCT_Drive_Para
0131 SI KNE active
0132 SI ETSL active
0133 Inverter Para Not Accepted
0134 NTSD active
0135 DREC_DRH_button
0136 Safety Bypass
0137 JHCC_Pressed
0138 Brake Not Set
0139 Unintended Movement detected
0140 Safety T4B
0141 Safety T1
0142 Safety T2
0143 Safety T2A
0144 Safety T2B
0145 Safety T3
0146 Safety T3A
0147 Safety T3B
0148 Safety T4
0149 Safety T5
parties.
150...199 Variodyn E
No. Section
Contents
0150 Max Eevent Id TravelControl
0151 LearnTrip
0152 CorrTrip
0153 SynchTrip
0154 KS_MagnetPos
0155 KSE_MagnetPos
0156 LearnMesProbl
0157 DeltaS_2BP
0158 SF_Fault
0159 NoBpReaction
0160 SK ErrorStart
0161 CarNotAtLevel
0162 CarOutOfFloor
0163 TargetFailure
0164 FC_ShortBrake
0165 FC_StopSpeed
0166 SW_BlockPerm
0167 LastBlockTime
0168 ShaftChecksum
0169 Supply24V
0170 FloorPrec
0171 InvDrivePCT
0172 InvDriveParam
parties.
200...299 Door Control
No. Section
Contents
0200 Door Error Base
0201 ConfigErr
0202 DoorOperErr
0203 ThermoDoorMot
0204 DoorRevDevErr
0205 DoorContrErr
0206 DoorBoltErr
0207 CloseSeqErr
0208 DoorDevErr
0209 DoorContact
0210 Lift Guardian
0211 COM_Busreconf
0212 Open Sequence KOKB
0213 DT-O Continous Activation
0214 RPHT Continous Activation
0215 REP Continous Activation
0216 KTL Continous Activation
0217 KSKB Continous Activation
0218 DT-S Continous Activation
0219 RTS Continous Activation
0220 KOKB Continous Activation
0221 Door inverter failure
0240 SW-Warning
0251 Door Command Timeout
0252 Door Unavailable
0253 Door Wrong Response
0254 Floor Zone Not Available
0255 Floor Weight Not Available
0256 Out Of Floor Zone
0260 Reserve_Error_260
0261 Door Postion Recovery Failure
0271 Door Command Failure
parties.
300...399 Varidor70 Door Drive
No. Section
Contents
0300 CTR_PAR_ACCESS
0301 CTR_CALC
0302 TRC_PAR_ACCESS
0303 TRC_POS_ERR
0304 TRC_CALC
0305 OS_CYCLE_OVERRUN
0306 PAR_NOVRAM_MISSING
0307 HW_PAR_ACCESS
0308 HW_POSITION
0309 HW_POSREF
0310 HW_DRV_SERIOUS
0311 DRIVE _OVER_TEMP
0312 HW_FLASH_READ
0313 HW_FLASH_WRITE
0314 HW_WATCHDOG
0315 IAC_MOD_UPD_FAIL
0316 IAC_PAR_UPD_FAIL
0317 IAC_UNKNOWN_LEVEL
0318 IAC_DOOR_TYPE_UNKNOWN
0319 IAC_CLUTCH_FAILURE
0320 ESTIMATED_CONSTRUCT_DATA
0321 ESK_INTERNAL
0322 ESK_PARAM_WRITE
0323 ESK_PARAM_READ
0324 ESK_COMMUNICATION_ERR
0325 VLON_INTERNAL
0326 VLON_TRANSMIT
0327 VLON_RECEIVE
0328 EMERGENCY
0329 NORMAL_RESET
0330 EST_LRACCU_OVERFL
0331 BLOCKED_OPENING_DIRECTION
0332 BLOCK_CLOSE_DIRECTION
0333 SLV70_OBSTACLE_DETECT
0334 SLV70_RESULT_RANGE
0335 IAC_CLUTCH_WARNING
0336 DRIVE_OVER_TEMP_WARNING
0337 HOLDING_FORCE_AT_CLOSED_POSITION
0338 Reserve_8
0339 Reserve_9
0340 Reserve_10
0341 Reserve_11
0342 Reserve_12
0343 Reserve_13
0344 Reserve_14
0345 Reserve_15
parties.
400...599 Lift
No. Section
Contents
0400 No_Error
0401 VCOM Node Connected
0402 VCOM Node Disconnected
0403 PowerUp
0404 Start Monitor Expired
0405 Permanent Active Call
0406 ExceptionMC
0407 COM Bus Stress
0408 PIOL_ConfErr
0409 COM_Bus Reconfiguration
0410 PIO-Error
0411 ARA-Service
0412 KTHM-Service
0413 TAB-Service
0414 SDU-Service
0415 SID Alive
0416 SID Dead
0418 IO Subsys_checksum error
0419 ParamGrp checksum error
0420 SCT/PCT-Checksum
0421 Invalid Parameter Value
0422 FLASH Failure
0423 PCT define
0424 Parameter Missing
0425 SCT/PCT write error
0426 Wrong SBT Data
0427 Wrong SCT Data
0428 End Monitor Expired
0429 Chipcard general error
0430 Chipcard general warning
0431 Chipcard general event
0432 Chipcard expansion done
0433 Chipcard not valid
0434 SCT Expansion
0435 Invalid SCT
0440 Invalid Parameter Access
0441 Invalid Telegram Data
0442 Invalid Telegram Attribute
0443 Invalid Telegram ID
0444 Invalid Telegram Group
0445 Invalid Lift Number
0449 PCT config error
0450 Parameter Configuration Error
0451 IO Configuration Error
0452 SCT/PCT read error
0453 Timer Table Overflow
0454 Totals log overflow
0455 Unknown task id
0456 CT download_successful
0460 VCOM Init
0461 VCOM open
0462 VCOM close
0463 VCOM provide
0464 VCOM unprovide
0465 VCOM request
0466 VCOM unrequest
0467 VCOM send
0468 VCOM pend
0469 VCOM get
0470 VCOM accept
0471 VCOM reply
0472 VCOM queue overflow
0473 VCOM table full
0474 VCOM Comms Queue Full
0475 Too much Bus reconfiguration
0476 Elevator Operation Interrupted
0477 Elevator Operation Resumed
0478 OVERLAY failure
0480 No Modem
0481 Modem Present
0482 Modem Calling
0483 Modem Answering
0484 Modem Online
0485 Modem Error
0486 Modem Line Busy
0487 Modem No Dialtone
0488 Modem No Carrier
0489 Modem Delayed
0490 Table_Overflow
0491 User Level 3 disabled
0492 User Level 3 reenabled
0493 Low Building Sway Active
0494 Medium Building Sway Active
0495 High Building Sway Active
0496 Building Sway Deactivated
0497 Ins IO Missing
0498 Group 24VDC Fail
0499 Lift 24VDC Fail
0500 12VDC Power Fail
0501 Battery Charging
0502 Battery Charge Low
0503 Battery Charge Very Low
0504 Battery Dead / Missing
0505 Battery Charge Time Expired
0506 Battery Charge Low on PEBO
0507 Building Sway Detection Device Error
0508 WAD-Service
0509 Group Master Conflict
0510 TM Stress Warning Limit Exceeded
0511 TM Stress Maximum Limit Exceeded
0512 TM Aging Warning Limit Exceeded
0513 TM Aging Maximum Limit Exceeded
0514 TM Defect Steel Cord in Coated Traction Media
0515 Flash Write Shaft Image
0516 TM Virgin Store Detected
0517 TM Reference Key Mismatch
0518 TM Mismatch but Same Reference Key
0519 TM Undefined Data
0520 Chipcard Missing
0521 TM Aging Clock Warning
0522 TM Aging Clock Error
0523 TM Aging Clock Failure Recovered
0524 PEBO Device Failure
0525 TM Data Storage Recovery Successfull
0526 TM Data Storage Recovery Failed
0527 PEBO Battery and Device OK
0528 SDU Critical Rope Stretch
0529 SDU Inadmissible Rope Stretch
0530 Group 24VDC Ok
0531 Lift 24VDC Ok
0532 12VDC Power Ok
0533 Battery Ok and Charged
0534 534
0535 Group Comm Transmit (Tx) Stress
0536 Group Comm Receive (Rx) Overflow
0537 Group Comm Offline
0538 TM Installation Data Entered
0539 TM Stress Count Entered
0540 Battery Charge Low on AES Device
0541 Battery OK on AES Device
0542 VCOM ID Conflict
0543 Speed Governor Rope Tension LOW
0544 EAQ operation activated
0545 EAQ operation de-activated
0546 Traction Media 1 Broken
0556 Building Sway Manual Override
0557 KEF input of AES device broken
0558 OEM Policy Disabled
0559 OEM Policy Status Undefined
0560 OEM Order Data Mismatch for OEM Never Enable
0561 Invalid TMM Configuration
0562 Parameter Length Different
0563 Parameter Type Different
0564 OEM Policy Status Disabled
0565 OEM Policy Status Enabled Not Active
0566 OEM Policy Status Enabled Active
0567 OEM Policy Status Never Enable
0599 LC_MAX_Errors_LC
parties.
600...699 MC PVF
No. Section
Contents
0600 Attempt to start not allowed
0601 Attempt to restart not allowed
0602 Overtemperature
0603 SW warning
0604 DL overvolt trigg
0605 DL overvolt
0606 DC link undervoltage
0607 Control Hardware command wrong
0608 Charging DC link failure
0609 Discharging DC link failure
0610 Current loop not OK
0611 Deactivate current loop failure
0612 Input contactor failure
0613 Charge contactor failure
0614 Current difference warning
0615 SW encoder warning
0616 Over current warning
0617 Over speed warning
0618 Start direction wrong
0619 Speed reference warning
0620 Time control motor exceeded
0621 Receive uart failure
0622 Message source failure
0623 Message length failure
0624 Receive state wrong
0625 Transmit state wrong
0626 EPROM checksum failure
0627 RAM failure
0628 Board battery failure
0629 RAM checksum failure
0630 Watchdog failure
0631 Transmit failure
0632 Open safety circuit
0633 HW encoder warning
0634 Exception vector
0635 Contactor time exceeded
0636 Driver Print power failure
0637 Overtemperature brake resistor
0638 FCR no start
0639 FCR no stop
0640 FCR interrupt
0641 External error
0642 PCC failure
0643 Supply failure cc1
0644 Input contactor failure cc1
0645 Charge contactor failure cc1
0646 DL overvolt trigg cc1
0647 Current difference warn cc1
0648 Current loop failure cc1
0649 Overtemperature cc1
0650 External error cc1
0667 Dummy 1
0668 Dummy 2
0669 Dummy 3
parties.
700...739 MC PVEC
No. Section
Contents
0700 Memory Failure
0701 SW Warning
0702 Communication Failure
0703 Overcurrent Motor
0704 Encoder Failure
0705 Speed Difference
0706 Speed Ref Missing
0707 SGRW Failure
0708 SH Failure
0709 Safety Circuit
0710 FCR Not Ready
0711 Overcurrent Inverter
0712 Power Electronic Failure
0713 Current Difference
0714 Current Not Zero
0715 Current Sum Failure
0716 Overtemp HS Trigger
0717 Overtemp HS Limit
0718 DCL Overvoltage Trigger
0719 DCL Overvoltage
0720 DCL Undervoltage
0721 DCL Unsymmetric Voltage
0722 DCL Charging Time
0723 DCL Discharging Time
0724 Power Supply
0725 Overtemp KTHBR
0726 Overtemp MH
0727 HW failure
0728 Phase failure
0729 Fan failure
0730 FCM failure
0731 FCM overtemperature
0732 Overtemp Line Choke
0733 Mains Current Difference
0734 Mains Overcurrent
0735 Mains Phase Interruption
0736 Mains Voltage Failure
0737 UEM detected
parties.
740...799 Magnetek
No. Section
Contents
0740 Overspeed
0741 Tach Loss
0742 Reverse Tach
0743 not_a_number
0744 overflow
0745 underflow
0746 divide by zero
0747 Motor overload
0748 Motor field overcurrent
0749 Contactor fault
0750 1 minute full field
0751 Open armature circuit
0752 safety circuit
0753 PAC fault
0754 DCU CEMF fault
0755 PCU CEMF fault
0756 PCU reset
0757 loop fault
0758 IST fault
0759 Power supply
0760 Line synch
0761 Low line
0762 Field loss
0763 DCU failure
0764 Bad thermistor
0765 High temperature
0766 Exessive ripple
0767 Blown fuse
0768 shorted doubler
0769 Open SCR
0770 bad parameter
0771 Forcing fault
0772 AV feedback reversed
0773 Parameter too high
0774 Parameter out of range
0776 Bridge fault
0777 parameter out of range
0780 Field supply fault
0781 PCU software fault
parties.
800...899 800_899_Varidor35_Door_Drive
No. Section
Contents
0800 VD35 base
0809 wCommand Unknown
0812 wWrong Motion Direction
0821 Door Movement too Fast
0832 wKET-S2 Failure
0833 eKET-S2 Short; Contact Bridged
0834 wMotor Over Temperature
0835 eAuto Setup Failed
0836 wCAN Messages Too Fast
0837 eLocked Position Failure
0838 eLocking Jam
0839 eUnlocking Jam
0840 wNGT 24VDC Over 5% Limit
0841 wNGT 24VDC Under 5% Limit
0842 eNGT 24VDC Over 10% Limit
0843 eNGT 24VDC Under 10% Limit
0844 ePower Door Off
0849 eOver Current
0850 eOver Voltage
0851 eUnder Voltage
0852 eDoor Drive Over Temperature
0855 eInternal Software
0856 eSoftware Internal Parameter
0857 eSensor Position
0858 eCAN Overrun
0863 eCAN Bus Off
0864 eCAN Rx Queue Overflow
0865 eCAN Tx Queue Overflow
0867 ePosition Following
0868 eHall Sensor
0869 eIndex Processing
0870 eEncoder Resolution
0874 eHall Angle Detection
0875 eSoftware Position Limit
0876 ePosition Sensor Breach
0877 eSystem Overloaded
parties.
900...999 IO
No. Section
Contents
0900 IOH Error Base
0901 ConfigErr
0902 PIO Error
0903 IO Table Overflow
0904 IO_Missing
0905 COP Configuration Error
0906 Duplicate_BMK
0910 COM_Busreconf
0920 PCT IO Section Checksum
0921 PCT Parameter Section Checksum
0922 VCOM Request
0923 VCOM Provide
0924 Board Configuration Error
0925 IO_reserve_925
0951 IO_Configuration_Error
0952 EEP_BurnProbl
0953 Deployment_Rule_Failure
0954 Freeze Table Invalid Entry
0961 EEP_BurnPrbl
0970 Timer Error
0971 IO_VCOM Telegram Missmatch
parties.
1000...1199 CPU
No. Section
Contents
1000 Bus Error
1001 Address Error
1002 Illegal Instruction
1003 Zero Divide
1004 CHK Instruction
1005 TRAPV Instruction
1006 Privilege Violation
1007 TRACE
1008 Uninitialized Int Vect
1009 Spurious Interrupt
1010 TRAP Instruction
1011 User Interrupt Vector
1012 Stuck IRQ
1013 Task Create
1014 Queue create
1015 Operating system RTEMS
1016 New Config Reset
1017 Event Handler Reset
1018 Appl. Requested Reset
1019 Memory Allocation Failure
1020 Line1010 Instruction Emulation
1022 HW Breakpoint
1023 FP protocol violation
1024 Format error
1025 Reserved interrupt
1026 Autovector 1
1027 Autovector 2
1028 Autovector 3
1029 Autovector 4
1030 Autovector 5
1031 Autovector 6
1032 Autovector 7
1033 FP Reserved
1034 FP Br Unord
1035 FP Inexact Result
1036 FP Div Zero
1037 FP Underflow
1038 FP Operand Error
1039 FP Overflow
1040 FP Signaling NAN
1041 FP Unimplemented DataType
1042 MMU Reserved
1043 MMU Config error
1044 MMU Illegal Operation
1045 MMU Access Level Violation
1046 TPU Interrupt
1047 SCI Interrupt
1048 SPI Interrupt
1049 CPM Interrupt
1050 External H Reset
1051 PowerUpReset
1052 Watchdog Reset
1053 DoubleBusFaultReset
1054 ClockLossReset
1055 External S-Reset
1056 BErr Released Write
1057 BErr Prefetch
1058 BErr Operand Read
1059 BErr Operand Write
1060 BErr MoveMultiple
1061 BErr Exception Processing
1062 Dead Task
1063 Group24vFail
1064 Lift24vFail
1065 12vPowerFail
1066 BatteryCharging
1067 BatteryLow50
1068 BatteryLow25
1069 BatteryDeadOrMissing
1070 LiftIdSwitchInvalid
1071 MissingEB
1072 Saved Registers
1073 ManualDoubleReset
1074 Init NVRAM
1075 Bad_SIMM Memory
1076 CPLD_Programmed
1077 OS Fault
1078 OS Restriction Failure
1079 Appl Restriction Failure
1080 BKPT BGND
1081 Page Fault on Instruction Fetch
1082 Page Fault on Operand Read
1083 Page Fault on Operand Write
1084 Bus Error Read Protection
1085 Bus Error Write Protection
1086 Bus Tenure
1087 Date Time First Init
parties.
1200...1249 LON
No. Section
Contents
1200 LON Error Base Id
1201 PowerUpReset
1202 Exception68332
1203 ExtReset
1204 DeadTask
1205 WdogReset
1206 MysteryReset
1207 NiInitFail
1208 NewNodeFound
1209 Missing Node
1210 NiErrLogged
1211 NodeErrLogged
1212 SvcPinEvent
1213 NiReset
1214 DupLocID
1215 NiErrCounter
1216 DiffCksGP_Konf
1217 DiffCksIO_Konfl
1218 TmoCksGP_Konf
1219 TmoDatGP_Konf
1220 TmoCksIO_Konf
1221 TmoDatIO_Konf
1222 DnLdGP_Konf
1223 DnLdIO_KOnf
1224 CksErrGP_Konf
1225 CksErrIO_Konf
1226 DoubleReset
1227 HWisLCTRL
1228 NiNoInAppBuf
1229 NiNoInNetBuf
1230 PmipNoOutQ
1231 PmipIqOverflow
1232 SubsystemStart
1233 SybsystemDead
1234 VcomUpcall
1235 KonfWipe
1236 CadiReset
1237 VcomAllDied
1238 KonfTableFull
1239 TelTrap
1240 LonDistQFull
1241 LonPupXON
1242 LonDownNACK
1243 FreezeFailed
1244 No Response Critical Node
1245 LON Error Debug
1246 LonErr46
1247 LonErr47
1248 LonErr48
1249 NodePowerFail
parties.
1250...1299 BIO2
No. Section
Contents
1250 BIO2_ISR_Initialisation_Error
1251 BIO2_ISR_Buffering_Error
1252 BIO2_ISR_Queueing_Error
1253 BIO2_ISR_Communication_Error
1254 BIO2_ISR_Busmaster_Error
1255 BIO2_spare
1256 BIO2_Reserve_1256
1260 BIO2 Queue Failure
1261 BIO2 Requestor Failure
1262 BIO2 Dispatcher Failure
1263 BIO2 Missing Node
1264 BIO2 Node Alive Again
1265 BIO2 No_Address_Left
1266 BIO2 Unsupported_Protocol
1267 BIO2 Multiple Node on address
1268 BIO2 Multiple BIOGIO Nodes
1269 BIO2 Nodes Manually Cleared
parties.
1300...1349 1300_11349_CAN
No. Section
Contents
1300 CAN Error Base Id
1301 CAN Missing Node
1302 CAN Node Alive Again
1303 CAN Node SW Download Failed
1304 CAN
1305 CAN Duplicate Node Detected
1306 CAN Dynamic Node ID Configuration Error
1307 CAN Node Configuration Failed
1308 CAN GC Controller Error
1309 CAN GC Controller Bus Off
1310 CAN GC Controller Bus Warning
1311 CAN Peripheral Controller Bus Off
1312 CAN LSS No Node Id Left
parties.
1400...1499 VF
No. Section
Contents
1401 SW_Event
1402 SW_Warning
1403 SW Error
1404 VarOutOfRange
1405 JHC_Pressed
1406 JHM_Pressed
1407 JHSG_Pressed
1408 Supply24V_OFF
1409 DriveLocked
1410 UnknownFloor
1411 SF_Fault
1412 SF1_Fault
1413 KB_Fault
1414 ShaftChecksum
1415 StartFailed
1416 TargetFailure
1417 CarNotAtLevel
1418 CarOutOfFloor
1419 KSE_Int_Fail
1420 KS_MagnetPos
1421 KSE_MagnetPos
1422 KS_Bounce
1423 KSE_Bounce
1424 SynchFailed
1425 IO_NotPresent
1426 VF_Notstop
1427 DeltaS_2BP
1428 TEL_Request
1429 TEL_Provide
1430 TEL_Reply
1431 TEL_Get
1432 TEL_ReadQueue
1433 TEL_VCOMopen
1434 Unknown_TEL
1435 No_ANT_PCT (Not Used)
1436 No_VF20_PCT
1437 OverTempMotor
1438 NoIncrement
1439 InvldMovement
1440 OverSpeed
1441 OverSpeedKSE
1442 DirectionErr
1443 DirNotAllowed
1444 PosLost_Tacho
1445 PosLost_KS
1446 PosLost_KSE
1447 FloorPrec
1448 RSK_Fault
1449 RSK1_Fault
1450 TIF_WriteErr
1451 TIF_ReadErr
1452 NoStartOK
1453 SK ErrorStart
1454 SK ErrorRun
1455 SynchTrip
1456 LearnTrip
1457 CorrTrip
1458 Inv_VF20_PCT
1459 Inv_BMG_Param
1460 LastBlockTime
1461 LearnFailed
1462 LearnMesProbl
1463 TEL_Send
1464 NoBpReaction
1465 Jump_Tacho
1466 SK_Bridging
1467 PosLost_IUET
1468 Supply24VOn
1469 VF20_Blocked
1470 Safety110V
1471 SafetySPT
1472 SafetyKNE
1473 SafetyRTS
1474 SafetyEnd
1475 SW_BlockPerm
1476 DataDestroyed
1477 VF_StartError
1478 VF_ShortBrake
1479 VF_StopSpeed
parties.
1500...1999 Travel Control Ext
No. Section
Contents
1500 Travel Control Ext Error Base Id
1501 Invalid Car Position
1502 Position Jump
1503 SI_Sensor_Defect
1504 Safety T6
1505 Invalid Floor Position during Trip
1506 Invalid Floor Position in Standstill
1507 KB ON standstill
1508 KB not ON start
1509 KB OFF Run
1510 KB not OFF stop
1511 Broken Traction Media
1512 SI Communication Lost
1513 SI UET device fault
1514 Si floor device fault
1515 SI Internal Log
1516 No Target Lower KSE Slowdown
1517 No Target Upper KSE Slowdown
1518 JNH active
1519 Bypass Plug Conflict
1520 Door Bypass Recall
1521 SI Teach-in Mode
1522 SI ETSL device fault
1523 SI KNE device fault
1524 CAN Sync Send
1525 CAN Controller
1526 ZSB Fault
1527 KTS Bridged
1528 KTC Bridged
1529 RCAM Fault
1530 RTC Fault
1531 RTS Fault
1532 KTS Fault
1533 KTC Fault
1534 Door State Fault
1535 KTS/KTC Bridged
1536 Invalid SI Flash
1537 SI Commission Number not Matching
1538 SI Mismatch of Number of Stops
1539 CLC Zero Load Calibration Frequency Failed
1540 CLC Reference Load Calibration Frequency Failed
1541 CLC Continuous Adjustment Not Successful
1542 CLC No Signal from Sensor
1543 CLC Invalid Signal from Sensor
1544 UET Bridged
1545 SB ON standstill
1546 SB not ON start
1547 SB OFF Run
1548 SB not OFF stop
1549 RB ON standstill
1550 RB not ON start
1551 RB OFF Run
1552 RB not OFF stop
1553 Load Measurement Functions Disabled
1554 Load Measurement Functions Enabled
1555 MBB Open Timeout Current
1556 MBB Close Timeout Current
1557 MBB IGBT3 Fault
1558 MBB Hardware Fault
1559 MBB Current Difference
1560 MBB Mains Not Off
1562 MBB Voltage Difference
1563 Shaft Door Opened Not Permitted
1564 LUET Off at Floor
1565 UET circuit failed
1566 KTS/KTC Fault
1567 INSP cmd to ACUM Failure
1568 KNE KPG bypass activated
1570 Car Damping Device Activation Failure
1571 Car Damping Device Deactivation Failure
1572 CLC Continuous Adjustment Exceeded
1573 SI Verification Trip Failed
1574 Safety Circuit Bridged
1575 Brake Emergency Stop Warning Limit Exceeded
1576 Brake Emergency Stop Blocking Limit Exceeded
1577 Brake Emergency Stop Data - virgin stor detected
1578 Brake Emergency Stop Data - Storage Mismatch
1579 Brake Emergency Stop - New Block Limit Calculated
1580 Brake Emergency Stop - Undefined Data
1581 Brake Emergency Stop Data Store recover Success
1582 Brake Emergency Stop Data Storage Not Recover
1583 Brake Emergency Stop Key Entered - Initialized
1584 Brake Emergency Stop Counter Values Entered
1585 Brake Emergency Stop - Air Gap Value Exceeded
1586 Brake Emergency Stop - Air Gap Entered
1587 Safety Circuit Overvoltage at Relay
1588 Safety Circuit Undervoltage Output
1589 Safety Circuit Overvoltage Output
1590 Safety Circuit Overcurrent
1591 Stop Override Relay 1
1592 SI Hoistway Image Upload Failed
1593 Hoistway Access Guard Fault
1594 SI Communication OK
1595 SI Communication Dead
1596 Overspeed KSE-U
1597 Overspeed KSE-D
1598 SI UET Command Lost
1599 Traction Loss
1600 JREC Switch Fault
1601 JRECC Switch Fault
1602 JRH Switch Fault
1603 JACCEN Switch Fault
1604 JUEKTS Switch Fault
1605 JUEKTC Switch Fault
1606 MBB Current Difference Channel2
1607 MBB Open Timeout Current Channel2
1608 MBB Close Timeout Current Chanel2
1609 SI Configuration Mismatch
1610 Improve Flight Time Disabled
1611 Improve Flight Time Failed - Open SC
1612 Improve Flight Time Failed - Overtravel
1613 Improve Flight Time Failed - Locking Withdrawn
1614 Overspeed Drive
1615 Underspeed Drive
1616 Overspeed Car
1617 Underspeed Car
1618 Speed Reference Limit Exceeded
1619 CLC Blocked Sensor Detected
1620 SI PHNRU wrongly IN fin
1621 SI PHNRU wrongly OUT fin
1622 SI PHNRD wrongly IN fin
1623 SI PHNRD wrongly OUT fin
1624 SI PHNRU tolerance
1625 SI PHNRD tolerance
1626 SI PHNRU stuck
1627 SI PHNRD stuck
1628 Car Damping Device Permanent Activated
1629 FC_Start_Failed
1630 FC_Preparation_Failed
1631 Extensive Zero Speed Trip for Inverter
1632 SI PHNR fault
1633 SI Maximum Speed Exceeded
1634 SI Maximum Teaching Speed Exceeded
1635 SI Outside Learned Shaft
1636 Sync Trip Aborted
1637 RSK ON standstill
1638 RSK not ON start
1639 RSK OFF Run
1640 RSK not OFF stop
1641 SI Validation Failed
1999 MAX_EVENTS_EXT
parties.
2000...2099 2000_2099_Load_Measurement
No. Section
Contents
2001 2001
2002 2002
parties.
2100...2299 2100_2299_MOSIS
No. Section
Contents
2100 No Error
2101 Software Position
2103 Internal Floor Error
2104 Floors Erased Command
2105 RAM Channel AB Exchange
2106 Position AB not fit
2107 Position Channel AB Exchange
2108 floor RAM is erased
2109 RelayTest - Overbridging Pick
2110 Emergency-State
2111 Strange Position - Floors erased
2112 Position Warning
2113 Software Version Mismatch
2114 floor detection mismatch
2115 Unintended Car Movement
2116 Speedfilter
2117 Learning Trip failed
2118 ETSL Drop
2119 KNE Drop
2120 UET Drop
2121 Position Channel AB Communication
2122 Floor RAM Communication
2123 RelayTest - KNE Pick
2124 RelayTest - ETSL Pick
2125 RelayTest - Overbridging Drop
2126 RelayTest - KNE Drop
2127 RelayTest - ETSL Drop
2128 ETSL Pick
2129 KNE Pick
2130 UET Pick
2131 Learn fail - speed
2132 Learn fail - time out
2133 floor numbers mismatch
2134 floor mismatch - lowest
2135 floor mismatch - highest
2136 floor mismatch
2137 floor mismatch - channel B
2138 stuck-at of the parallel communication
2148 CAN - Bus OFF
2149 CAN - ERROR
2150 CAN - Overrun
2151 CAN - SYNC-Burst
2152 CAN - Node
2164 ETSL (dyn) closed before close
2165 KNE (dyn) closed before close
2166 UET (dyn) closed before close
2167 Overbridging (dyn) closed before close
2168 ETSL (dyn) close
2169 KNE (dyn) close
2170 UET (dyn) close
2171 Overbridging (dyn) close
2172 ETSL (dyn) open
2173 KNE (dyn) open
2174 UET (dyn) open
2175 Overbridging (dyn) open
2176 ETSL (dyn) open before open
2177 KNE (dyn) open before open
2178 UET (dyn) open before open
2179 Overbridging (dyn) open before open
2180 ETSL (static) open
2181 KNE (static) open
2182 UET (static) open
2183 Overbridging (static) open
2184 ETSL (static) close
2185 KNE (static) close
2186 UET (static) close
2187 Overbridging (static) close
2188 ETSL startup
2189 KNE startup
2190 UET startup
2191 Overbridging startup
2192 Relay closing statemachine
2193 Relay opening statemachine
2194 Parameter - false relay request
2195 Relay-Test statemachine
2196 Overbridging closed at test start
parties.
2300...2499 2300_2499_SALSIS
No. Section
Contents
2300 No Error
2301 ETSL Relay Drop Fail
2302 KNE Relay Drop Fail
2303 UET Relay Drop Fail
parties.
5000...5099 5000_5099_Remote_Monitoring
No. Section
Contents
5000 No Error
5002 No Physical Data Connection to Control Center
5003 Data Line to Control Center Busy
5004 No Logical Data Connection to Control Center
5005 Max Data Connection Attempts to Control Center
5006 Max Data Connection Time to Control Center Exceede
5007 Data Communication Device Dead
5008 Data Communication Device Alive
5009 Data Communication Device Faulty
parties.
8000...8099 8000_8099_Remote_Alarm
No. Section
Contents
8000 Alarm Error Base
8009 Alarm Device is Off Hook
8010 Alarm Device is On Hook
parties.
9000...9999 9000_9999_Status
No. Section
Contents
9000 S_OUT_OF_SERVICE_OPERATION
9001 S_PASSENGER_TRAVEL_OPERATION
9002 S_INDEPENDENT_OPERATION
9003 S_FIRE_OPERATION
9004 S_FIREFIGHTER_OPERATION
9005 S_EMERGENCY_POWER_OPERATION
9006 S_EARTHQUAKE_OPERATION
9007 S_EMERGENCY_MEDICAL_TECHNICIAN
9009 S_WATER_IN_PIT_OPERATION
9011 S_PASSENGER_TRAVEL_OPERATION_WITHOUT_LOAD_MONITOR
9012 S_PASSENGER_RELEASE_TRAVEL_OPERATION
9014 S_BUILDING_EMERGENCY_POWER_RECALL
9015 S_PRIORITY_TRAVEL
9016 S_HOSPITAL_EMERGENCY_TRAVEL
9039 S_OVERLOAD_SERVICE
9044 S_OUT_OF_SERVICE_FROM_REMOTE
9045 S_OUT_OF_SERVICE_STM_MONITORING_FAILURE
9050 S_SERVICE_TECHNICIAN_VISIT
9051 S_INSTALLATION_TRAVEL
9070 S_ELEVATOR_RECOVERY
9072 S_ELEVATOR_CAR_POSITION_RECOVERY
9080 S_STOP_SWITCH
9098 S_ELEVATOR_BREAKDOWN
9200 S_SERVICE_CHANGE
9201 S_CLEAR_MAINTENANCE_MSG
INVENTIO AG This design and information is our intellectual property. It must without our written consent neither
Restrictions CH-6052 Hergiswil be copied in any way nor used for manufacturing nor communicated to third parties.
0000 No Event
This section describes the Travel Control error No Event.

Summary
Normal termination of the trip. Note: The default event handling code
Description prevents this event being logged in CADI.
None.
Extra Info
None.
Source ID
0001 NormalStop
This section describes the Travel Control error NormalStop.

Summary
Normal termination of the trip. Note: The default event handling code
Description prevents this event being logged in CADI.
None.
Extra Info
None.
Source ID
ID Possible causes of message Actions to be taken

Causes and
1 None. No measure needed.
Actions
0002 ExceptionMC
This section describes the Travel Control error ExceptionMC.

Summary
Exceptions of microprocessor. The system jumps to the exception

Description routine and blocks itself. The exceptions are logged separately in the
exception log. Use special CADI Menu to view the exception log.
Only relevant to Miconic VX and TX4 (IVXVF board)
None.
Extra Info
None.
Source ID

Causes and
1 None. Report problem on hotline.
Actions
Make sure to have all related
error information from CADI
available.
2 EMC problems Check for strong EMC
interference sources in the
building.
3 Check that the 24V power
supply is separated from higher
voltage cables, e.g. the power
supply cables of the brake.
4 Make sure that the PCB
ground and mass connections
are done acc. to related
instructions.
5 Check all ground and mass
connections in the cabinet and
to the converter.
6 Defective PCB Change PCB.
0003 NoKSE_STDSTL
This section describes the Travel Control error NoKSE_STDSTL.

Summary
La cabina se detiene en uno de los extremos del hueco y detecta que

Description la señal KSE no se corresponde con la posición calculada por el
tacómetro de distancia.
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Valores de parámetro Comprobar que la posición
Actions
incorrectos física de los imanes KSE del
hueco es igual al valor(es) de
los parámetros
'KSE_DISTANCE' y
'SHAFT_PARA.GAP_LENGTH'
(parámetros del hueco).
2 Polaridad del imán incorrecta Comprobar la polaridad de los
imanes.
3 El imán KSE más bajo es un
sur.
4 El siguiente imán (el imán
inferior del siguiente tramo) es
un norte.
5 El imán más alto es un sur.
6 Interruptor KSE Comprobar el interruptor KSE.
7 Comprobar la conexión entre
el interruptor KSE y el circuito
impreso.
0004 InvldMovement
This section describes the Travel Control error InvldMovement.

Summary
Invalid movement. A movement of the car was detected while Travel

Description Control is in standstill phase.The event is logged when the car starts to
move after the brake is opened manually and Travel Control is able to
detect the movement.
None.
Extra Info
None.
Source ID

Causes and
1 Defective drive brake or bad Check the mechanical brake (
Actions
brake adjustment (brake torque Adjustment of brake , possible
not sufficient to hold car at wear of brake lining ). Brake
standstill) torque sufficient to hold fully
loaded or empty car.
2 Verify brake action by
performing an emergency stop
at full speed in up direction
with empty car and check if the
car comes to rest. Use brake
test to measure average
deceleration after emergency
stop. Be aware of possible
rope slip.
0005 SH_on_STDSTL
This section describes the Travel Control error SH_on_STDSTL.

Summary
The contactor SH or SH1 is active in standstill.

Description
Remark: older drive systems have two main contactors SH, SH1.
0: error on SH
Extra Info 1: error on SH1
None.
Source ID

Causes and
1 Main contactor SH (SH1) Check the auxiliary contacts of
Actions
broken SH, SH1
2 SH or SH1 are operated by None.
hand
3 Faulty input circuit on interface Check status of input when
board for auxiliary contacts contact closes, opens. Replace
SH, SH1 pcb if necessary.
0006 SB_on_STDSTL
This section describes the Travel Control error SB_on_STDSTL.

Summary
The control detects that the brake control hardware (e.g. contactor SB)
Description activates the brake during standstill phase.
00 (hex)/ 0 (dec):,: RB fault (for MX-GC) :RB open before starting a trip
Extra Info 0C (hex)/12 (dec): MBB brake module: Brake open during standstill
(MBB_OPEN_STANDSTILL)
None.
Source ID

Causes and
1 Bad connection/wiring of the Check the auxiliary contacts of
Actions
feedback contact SB and the wiring
2 Contactor SB moved manually
3 Dust in the control cabinet or Remove dust.
other difficult environmental
conditions causing conductivity
problems.
ID Location Actions to be taken

Field Feedback
1 Drive Comprobar el contacto de freno SB (polvo,
suciedad). Comprobar Información de Campo
Nr. 239
0007 SH_Fault
This section describes the Travel Control error SH_Fault.

Summary
Los contactos auxiliares de SH / SH1 (o RH / RH1) se abrieron

Description mientras la cabina estaba en movimiento.
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Circuito de seguridad abierto Comprobar el circuito de
Actions
seguridad
2 Valor de parámetro incorrecto Si el error de produce cuando
la cabina está aproximándose
al piso destino, este puede
estar causado por el circuito
de apertura anticipada de
puertas. Reducir el valor del
parámetro
MAX_DOOR_ZONE.
3 Cableado incorrecto Comprobar el cableado del
contacto auxiliar de SH, SH1
(RH, RH1)
0008 SB_Fault
This section describes the Travel Control error SB_Fault.

Summary
El contacto auxiliar SB se abrió cuando la cabina se estaba

Description desplazando o se produjo un error en el módulo de freno (p.ej., MBB)
Con MBB:
Extra Info 01 (hex)/ 1 (dec): (MBB_TASK_CREATE_ERROR) = Mensaje de
estado
02 (hex)/ 2 (dec): (MBB_BUFFER_OVERFLOW_ERROR) = Mensaje
de E/S
03 (hex)/ 3 (dec): (MBB_INT_WRONG_MSG) = Recibido mensaje
desconocido
04 (hex)/ 4 (dec): (MBB_ZERO_MESSAGE) = Enviado mensaje de
longitud cero
05 (hex)/ 5 (dec): (MBB_UNKNOWN_COMMAND) = Recibido
comando desconocido
06 (hex)/ 6 (dec): (MBB_KB_FAULT) = Fallo en KB
07 (hex)/ 7 (dec): (MBB_KB1_FAULT) = Fallo en KB1
08 (hex)/ 8 (dec): (MBB_OPEN_TIMEOUT_CURRENT) = Tiempo de
espera para apertura, sin corriente
09 (hex)/ 9 (dec): (MBB_CLOSE_TIMEOUT_CURRENT) = Tiempo de
espera para cierre, sin corriente 0
0A (hex)/10 (dec): (MBB_IGBT3_FAULT) = Fallo en IGBT u otro error
0B (hex)/11 (dec): (MBB_HW_FAULT) = Error en el HW de MBB
0C (hex)/12 (dec): (MBB_OPEN_STANDSTILL) = Freno abierto
durante reposo
0D (hex)/13 (dec): (MBB_CLOSED_RUNNING) = Freno cerrado
durante viaje
0E (hex)/14 (dec): (MBB_MBX_ERROR) = Error en buzón del MBB
0F (hex)/15 (dec): (MBB_MAX_MESSAGE_SIZE) = Tamaño de
mensaje de MBB demasiado largo
10 (hex)/16 (dec): (MBB_CURRENT_DIFF_ERROR) = Error de
diferencia de corriente del MBB
11 (hex)/17 (dec): (MBB_MAINS_NOT_OFF) = La corriente eléctrica
no se desactivó
12 (hex)/18 (dec): (MBB_IGBT1_FAULT) = Comprobación de IGBT1
no OK
13 (hex)/19 (dec): (MBB_VOLTAGE_DIFF_ERROR) = Error de
diferencia de tensión del MBB
Módulo de freno MX:
14 (hex)/20 (dec): (MBB_KBR_FAULT) = Fallo de RB (para MX-GC)
15 (hex)/21 (dec): (MBB_ZSB_FAULT) = Fallo del relé de
temporización del freno (para MX-GC)
Ninguna.
Source ID

Causes and
1 Circuito de seguridad abierto Comprobar el circuito de
Actions
seguridad
2 Los contactos auxiliares de Comprobar el funcionamiento
SB/SB1 no funcionan de los contactos auxiliares de
SB/SB1.
3 Comprobar el cableado de los
contactos auxiliares de
SB/SB1
4 El relé RB no funciona Comprobar el funcionamiento
del relé RB
5 Polvo en el armario de Eliminar el polvo
maniobra y otras condiciones
ambientales adversas están
causando problemas de
conductividad.

Field Feedback
1 Drive Comprobar el contacto de freno SB/SB1 (polvo,
suciedad). Comprobar Información de Campo
Nr. 239
0009 KB_Fault
This section describes the Travel Control error KB_Fault.

Summary
Los contactos de freno KB ó KB1 no conmutan adecuadamente. La

Description maniobra de control de viaje espera información de KB y KB1. En el
caso de que sólo exista un contacto KB, comprobar que hay un puente
en el conector del circuito impreso.
Comentario: Con tracciones sin reductor, comprobar que los contactos
del freno funcionan correctamente, y que la alimentación de corriente
del freno es adecuada; cuando se abre el freno, primero se acciona
SB (alimentación completa del freno), y justo después se activa la
reducción de tensión del freno (p.ej., SGRB o módulo de freno
electrónico). La reducción de tensión es independiente del estado de
KB y KB1.
Existe un tiempo determinado dentro del cual debe abrirse el freno;
transcurrido este tiempo, los contactos son comprobados. El/los
contacto(s) del freno es/son un/unos componente(s) delicado(s) del
sistema de maniobra. Asegurarse de que los contactos están bien
fijados y limpios. Consultar las instrucciones correspondientes para
ajustar los contactos del freno (la experiencia muestra que el mejor
ajuste es, probablemente, dejar una holgura de 1 mm entre el contacto
y el elemento accionador cuando el freno está cerrado).
Con MBB:
Extra Info 01 (hex)/ 1 (dec): (MBB_TASK_CREATE_ERROR) = Mensaje de
estado
02 (hex)/ 2 (dec): (MBB_BUFFER_OVERFLOW_ERROR) = Mensaje
de E/S
03 (hex)/ 3 (dec): (MBB_INT_WRONG_MSG) = Recibido mensaje
desconocido
04 (hex)/ 4 (dec): (MBB_ZERO_MESSAGE) = Enviado mensaje de
longitud cero
05 (hex)/ 5 (dec): (MBB_UNKNOWN_COMMAND) = Recibido
comando desconocido
06 (hex)/ 6 (dec): (MBB_KB_FAULT) = Fallo en KB
07 (hex)/ 7 (dec): (MBB_KB1_FAULT) = Fallo en KB1
08 (hex)/ 8 (dec): (MBB_OPEN_TIMEOUT_CURRENT) = Tiempo de
espera para apertura, sin corriente
09 (hex)/ 9 (dec): (MBB_CLOSE_TIMEOUT_CURRENT) = Tiempo de
espera para cierre, sin corriente 0
0A (hex)/10 (dec): (MBB_IGBT3_FAULT) = Fallo en IGBT u otro error
0B (hex)/11 (dec): (MBB_HW_FAULT) = Error en el HW de MBB
0C (hex)/12 (dec): (MBB_OPEN_STANDSTILL) = Freno abierto
durante reposo
0D (hex)/13 (dec): (MBB_CLOSED_RUNNING) = Freno cerrado
durante viaje
0E (hex)/14 (dec): (MBB_MBX_ERROR) = Error en buzón del MBB
0F (hex)/15 (dec): (MBB_MAX_MESSAGE_SIZE) = Tamaño de
mensaje de MBB demasiado largo
10 (hex)/16 (dec): (MBB_CURRENT_DIFF_ERROR) = Error de
diferencia de corriente del MBB
11 (hex)/17 (dec): (MBB_MAINS_NOT_OFF) = La corriente eléctrica
no se desactivó
12 (hex)/18 (dec): (MBB_IGBT1_FAULT) = Comprobación de IGBT1
no OK
13 (hex)/19 (dec): (MBB_VOLTAGE_DIFF_ERROR) = Error de
diferencia de tensión del MBB
Ninguna.
Source ID

Causes and
1 Contacto(s) de freno Comprobar los contactos de
Actions
defectuoso(s) freno.
2 Mal ajuste del/de los Comprobar el funcionamiento
contacto(s) de freno del/de los contacto(s) de freno
y (re)ajustarlo(s) si es
necesario
3 Problema mecánico en el Comprobar el freno.
freno
4 Observar el freno cuando se
abre.
5 Ambos lados del freno deben
abrirse simétricamente.
6 Valor de parámetro incorrecto Comprobar los parámetros de
para el parámetro 'KB tracción (ajustes) para corregir
feedback type' el tipo de freno.

Field Feedback
1 Drive Comprobar el contacto de freno KB/KB1 (polvo,
suciedad, permitir un hueco de 1 mm entre el
contacto y el elemento actuante cuando el freno
esté cerrado)
0010 FC_Fault
This section describes the Travel Control error FC_Fault.

Summary
a) El variador de frecuencia solicitó una parada de emergencia.

Description b) La maniobra detectó un problema de comunicación con el variador
de frecuencia.
Comentarios: El control de tracción monitoriza el contactor SH.

Cuando el circuito de seguridad se abre durante un viaje, el control de
la tracción puede detectarlo antes que la maniobra de control de viaje.
Por lo que esta situación sólo puede estar causada por un problema
en el circuito de seguridad. Consultar también la descripción del error
'SH_Fault'.
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Problema interno de la Para más información,
Actions
tracción comprobar el registro de
eventos del control de la
tracción.
2 Comunicación con el variador Comprobar el cableado y los
de frecuencia (temporalmente) conectores del cable de
interrumpida conexión entre el VF y la
maniobra.
0011 FC_Block
This section describes the Travel Control error FC_Block.

Summary
El estado del control de la tracción es "bloqueado"

Description
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Consultar los diagnósticos
Actions
relativos al control de la
tracción
2 Variodyn E: BARMAG, LED Reiniciar el variador de
rojo de error en ER113 frecuencia. Si no se tiene
éxito, consultar el registro de
errores interno del variador de
frecuencia con una emulación
de terminal.
Manual de guía rápida:
1. Para iniciar, pulsar 's' / 2.
Pulsar 'f' y leer el error (ver
más abajo) /
3. Para salir, pulsar F10 /
4. Volver a reiniciar el variador
de frecuencia.
3 Mensajes de error internos del Posibles causas:
variador de frecuencia:
4 U_ZK < UZK_MIN Tensión de la red eléctrica
demasiado baja. Ausencia de
fase en la red eléctrica.
5 U_ZK > UZK_MIN Chopper no conectado, mal
especificado (Ohm) o
defectuoso. Configuración de
parámetros incorrecta.
6 I > I_MAX Variador de frecuencia
VF20/30 defectuoso.
Cortocircuito o derivación a
tierra en el cableado del motor.
Configuración de parámetros
incorrecta.
7 TIBR > 5 S El circuito impreso de interfaz
no restaura la señal de
arranque. Comprobar el
funcionamiento del freno.
8 NET > OFF Mal funcionamiento del
variador de frecuencia
VF20/30.
9 KEINE IMPULSE Comprobar la alimentación del
tacómetro (patillas 1 y 2 del
conector IG100). Placa de
control del variador de
frecuencia VF20/30
defectuosa. Deslizamiento del
cable del tacómetro.
Tacómetro defectuoso.
10 ZEIT V K-FAHRT La orden de viaje de
corrección no se ha reiniciado.
11 VBET < 1.15 x VKN/2 El valor de VKN se ha
ajustado demasiado alto.
DELTA_U demasiado bajo.
Deslizamiento del cable del
tacómetro. Defectos en el
cableado. Variador de
frecuencia defectuoso. Defecto
mecánico en el sistema de
ascensor.
12 VBET > 1.15 x VKN El valor de VKN se ha
ajustado demasiado bajo.
FC_MAX_R ajustado
demasiado alto. MM_IMP
ajustado demasiado alto.
Defecto mecánico en el
sistema de ascensor.
13 TEMP > T_MAX La corriente nominal se supera
de forma continua. Los
ventiladores de refrigeración
no están conectados o son
defectuosos. Flujo de aire
restringido. Dirección o
rotación incorrecta.
0012 DirectionErr
This section describes the Travel Control error DirectionErr.

Summary
The car moved more than 2.5 cm in the wrong direction.

Description
In case of the Australian Standard (AS1735): The car tried to start a
trip in a direction, which is not allowed by the direction limit switches
(KSEB-D / KSEB-U).
None.
Extra Info
None.
Source ID

Causes and
1 Incorrect load input Check the load measurement
Actions
information.
2 Wrong parameter values Check the parameters on
Motor Control.
3 Incorrect tacho polarity Check the polarity of the
position tacho.
4 Direction limit Check the direction limit
switches(AS1735 only) switches (KSEB-D / KSEB-U),
the inputs and wiring to the
controller, and the actual
position of the car.
5 Variodyn E only: Manual trip Check tacho. Reset
on cabin roof in wrong Synchronization trip.If
direction in shaft end area necessary perform a learn trip.
0013 OverSpeed
This section describes the Travel Control error OverSpeed.

Summary
Si la diferencia entre la velocidad real de la cabina, calculada a partir

Description del encoder de posición, y la velocidad de referencia (velocity_ref)
sobrepasa el límite calculado (tolerancia de velocidad), el viaje se
interrumpirá con una parada de emergencia. La diferencia de
velocidad permitida (tolerancia) se calcula de la siguiente manera:
6,25% de la velocidad de referencia real con un mínimo de 0,1m/s. La
diferencia de velocidad permitida es 0,1m/s hasta una velocidad de
1,6m/s.
Ninguna.
Extra Info
Identifies the file in the core software from where the message is
Source ID generated.
Refer to error 70 for the description.

Causes and
1 Valores de parámetro Comprobar los parámetros,
Actions
incorrectos tanto en la maniobra de control
de viaje como en el control de
la tracción.
2 Entrada incorrecta desde el Comprobar el tacómetro de
tacómetro de posición posición.
3 Valor de carga incorrecto en el Comprobar el pesacargas y los
sistema de medición de la parámetros de carga. Estas
carga, lo que causa un par comprobaciones deben
erróneo en la máquina realizarse también si el evento
se produce justo al principio
del viaje.
4 La cabina se desplaza por Comprobar si el freno de la
encima del límite de velocidad máquina aplica un par
de detección mientras la mecánico suficiente. Llevar a
tracción/motor se encuentra cabo el test de freno de
desactivada/o. Puede estar acuerdo con las instrucciones
causado por una pérdida de del test de aceptación.
tracción en reposo o por una
apertura manual del freno.

Field Feedback
1 Shaft Comprobar: guías (limpias, engrasadas),
distancia entre guías.
2 Car Comprobar el pesacargas
3 Office Reportar problema a R&D-PLE (Fax +41 41 445
5030)
0014 UnderSpeed
This section describes the Travel Control error UnderSpeed.

Summary
Si la diferencia entre la velocidad real de la cabina, calculada a partir

Description del encoder de posición, y la velocidad de referencia (velocity_ref)
sobrepasa el límite calculado (tolerancia de velocidad), el viaje se
interrumpirá con una parada de emergencia. La diferencia de
velocidad permitida (tolerancia) se calcula de la siguiente manera:
6,25% de la velocidad de referencia con un mínimo de 0,1m/s. La
diferencia de velocidad permitida es 0,1m/s, hasta una velocidad de
1,6m/s.
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Valores de parámetro Comprobar los parámetros,
Actions
incorrectos tanto en la maniobra de control
de viaje como en el control de
la tracción.
2 Entrada incorrecta desde el Comprobar el tacómetro de
tacómetro de posición posición.
3 Entrada de carga incorrecta Comprobar el pesacargas y los
parámetros de carga. Estas
comprobaciones también
deben realizarse si el evento
se produce justo al principio
del viaje.
4 El valor de referencia de Comprobar los parámetros de
velocidad sobrepasa las velocidad y aceleración.
capacidades del inversor; el
inversor no puede seguir la
curva de viaje.
5 Cabina o contrapeso Asegurarse de que la cabina y
bloqueado mecánicamente el contrapeso pueden moverse
por las guías.
6 Deslizamiento de cable en la Comprobar el correcto
polea tractora equilibrado de la
cabina/contrapeso.

Field Feedback
1 Shaft Comprobar: guías (limpias, engrasadas),
distancia entre guías.
2 Car Comprobar el pesacargas
3 Office Reportar problema a R&D-PLE (Fax +41 41 445
5030)
0015 NoTargetLow
This section describes the Travel Control error NoTargetLow.

Summary
The car enters the lower KSE zone and no target was set in Travel
Description Control logic
None.
Extra Info
None.
Source ID

Causes and
1 Incorrect KSE signal Check KSE parameters and
Actions
magnets.
2 Please inform Ebikon if this
event appears
0016 NoTargetUp
This section describes the Travel Control error NoTargetUp.

Summary
The car enters the upper KSE and no target was set in Travel Control
Description logic
None.
Extra Info
None.
Source ID

Causes and
1 Incorrect KSE signal Check KSE parameters and
Actions
magnets.
2 Please inform Ebikon if this
event appears
0017 OverSpeedKSE
This section describes the Travel Control error OverSpeedKSE.

Summary
Overspeed detected while car is inside the upper or lower KSE position
Description (KSE-U / KSE-D).
0: Overspeed detected with car in KSE zone.

Extra Info
10: For MX only (no KSE): Learn trip aborted because learn speed
(V_LEARN) to high. Trip curve does not allow to stop the car normally
within a distance equal to: FIN_LENGTH / 2.
None.
Source ID

Causes and
1 Incorrect KSE input Check KSE parameters and
Actions
position of magnets. Repeat
the learn trip.
2 Variodyn E: Improper Check KSE distance
parameter settings (frequency
converter) Check frequency
converter parameter values
0018 NoLowerKSE
This section describes the Travel Control error NoLowerKSE.

Summary
There was a discrepancy between the position of the lower KSE switch
Description in the shaft and its position value stored during the learn trip.
Comment: In case of IG type position tacho the event will be generated
if the car is moved manually without position value update within
Travel Control (e.g. position tacho disconnected). This way the next trip
will start with a wrong car position value.
None.
Extra Info
None.
Source ID

Causes and
1 Wrong KSE parameter or Check the KSE parameters
Actions
faulty magnets and position of magnets in the
shaft. Execute new learn trip
after magnet was moved.
2 Check the position tacho.
0019 NoUpperKSE
This section describes the Travel Control error NoUpperKSE.

Summary
There was a discrepancy between the position of the upper KSE switch
Description in the shaft and its position value stored during the learn trip.
Comment: In case of IG type position tacho the event will be generated
if the car is moved manually without position value update within
Travel Control (e.g. position tacho disconnected). This way the next trip
will start with a wrong car position value.
None.
Extra Info
None.
Source ID

Causes and
1 Wrong KSE parameter or Check the KSE parameters
Actions
faulty magnets and position of magnets in the
shaft. Execute new learn trip
after magnet was moved.
2 Check the position tacho.
0020 PositionLost
This section describes the Travel Control error PositionLost.

Summary
El error se produce cuando:

Description
- La cabina pasa por una pantalla/imán de piso que se encuentra en
una posición situada a más de 15 cm de la posición de referencia
guardada durante el viaje de aprendizaje.
"- La cabina pasa por una posición de piso sin detectar la

pantalla/imán de piso que se encuentra en esa
posición guardada durante el viaje de aprendizaje."
- La cabina se aproxima a un piso destino sin encontrar la

pantalla/imán de piso que se encuentra en la posición de piso
correspondiente guardada durante el viaje de aprendizaje.
- La cabina se encuentra a nivel de piso y no detecta ninguna

pantalla/imán de piso.
Comentarios:
- La maniobra de control de viaje inicia un viaje de sincronización
después de producirse el error. En caso se existir un tacómetro de
posición incremental (IG), la cabina realizará un viaje hasta la posición
del KSE. En caso se existir un tacómetro de posición tipo encoder
absoluto (AGSI), la cabina se desplazará hasta el siguiente nivel de
piso.
- Si la cabina está detenida a nivel de piso y una de las células
fotoeléctricas envía un mensaje OUT_FIN incorrecto, la maniobra de
control de viaje toma la información de ésta como real y asume que la
cabina se encuentra en el borde de la lengüeta y no a nivel de piso.
(Esta situación puede producirse en edificios grandes con un
alargamiento de cable significativo si la cabina está detenida durante
mucho tiempo a nivel de piso). La maniobra de control de viaje
sobrescribe la posición y se inicia un relevel_trip (viaje de renivelación)
para una distancia de 15 mm. Dado que la cabina se encontraba a
nivel de piso al comienzo de este viaje, la segunda célula fotoeléctrica
quedará fuera de la lengüeta. Ahora las dos células fotoeléctricas se
encuentran fuera de la lengüeta, pero la maniobra de control de viaje
sigue asumiendo que la cabina está casi a nivel, lo que es detectado
como una POSITION_LOST.
0 (hex)/ 0 (dec): Con la cabina a nivel de piso, ni la señal PHS ni la

Extra Info señal PHNR_D están activas ('IN_FIN'). La transición 'OUT_FIN' de la
señal PHS se produce más tarde de lo esperado.
1 (hex)/ 1 (dec): La transición 'OUT_FIN' de la señal PHNR_D se
produce más tarde de lo esperado.
2 (hex)/ 2 (dec): TX-GC2: Información de hueco corrupta ==> Posición
de piso / MX-GC con AGSI: El LUET no se activó al pasar por un piso.
3 (hex)/ 3 (dec): MX-GC/TX-GC: Información de hueco corrupta ==>
Posición de piso
4 (hex)/ 4 (dec): TX-GC2: Información de hueco corrupta ==> KSE-D /
Discrepancia detectada entre la información de la zona de nivel de
puerta (KUET) y el valor de posición del dispositivo de información de
la posición de cabina (AGSI/IGS). La señal digital de la zona de nivel
de puerta de la información del hueco (LUET) está activa, pero el valor
de posición de la cabina dice que la cabina está fuera de la zona de
nivel de puerta.
5 (hex)/ 5 (dec): MX-GC/TX-GC: Información de hueco corrupta ->
KSE-D
8 (hex)/ 8 (dec): TX-GC2: Información de hueco corrupta -> KSE-U
9 (hex)/ 9 (dec): MX-GC/TX-GC: Información de hueco corrupta ->
KSE-U
A (hex)/ 10 (dec): La posición del imán KSE-U se encontró a más de
15 cm de la posición guardada durante el viaje de aprendizaje.
B (hex)/ 11 (dec): La posición del imán KSE-D se encontró a más de
15 cm de la posición guardada durante el viaje de aprendizaje.
C (hex)/ 12 (dec): Mientras se realizaba un viaje de sincronización, el
imán KSE-D se activó a más de 15 cm de la posición guardada
durante el viaje de aprendizaje.
Ninguna.
Source ID

Causes and
1 Problema mecánico con la Comprobar la posición de las
Actions
información del hueco. lengüetas o los imanes.
Repetir el viaje de aprendizaje.
2 Comprobar la distancia
horizontal entre las
lengüetas/imanes y la célula
fotoeléctrica/interruptor.
Asegurarse de que la holgura
de la cabina no es demasiado
grande cuando ésta se
encuentra en los niveles de
piso.
3 El tacómetro de posición (tipo Comprobar el deslizamiento
IG o tipo AGSI) no funciona mecánico en el tacómetro de
correctamente. posición.
4 Comprobar que el tacómetro
funciona sin problemas.
5 Comprobar el cable del
tacómetro y su fuerza tensora,
así como las dos poleas del
cable. La garganta de las
poleas del tacómetro tiene que
estar limpia (especialmente en
IGS-200).
6 Valores de posición de cabina Comprobar el valor de posición
incorrectos proporcionados por de cabina mostrado en el
el tacómetro de posición de SMLCD (o UI1). Comprobar si
cabina. existen problemas de EMC y
consultar las explicaciones
sobre valores de información
adicionales.
7 Problema de interferencias Comprobar la alimentación de
eléctricas en las células las células fotoeléctricas.
fotoeléctricas (PHS / PHNR_D
o interruptores magnéticos)
8 Comprobar la conexión a tierra
que se encuentra en la parte
superior de la cabina y la que
existe entre el cuarto de
máquinas/armario de maniobra
y la cabina.

Field Feedback
1 Shaft Comprobar información de hueco (posición de
los soportes y los imanes)
2 Shaft/Drive Comprobar la posición del tacómetro y
deslizamiento del cable.
3 Shaft/ Car/ Comprobar fotocélula PHS/PHNR_D (corriente),
Controller conexión a tierra (cabina y controlador).
4 Comprobar la Información de Campo Nr. 275,
283, 291 (problema EMC
0021 HigherPrio
This section describes the Travel Control error HigherPrio.

Summary
This message is logged when the software detects the interruption of a

Description trip after a manipulation in the machine room etc; e.g. Recall Swtich
JRH is activated while the elevator is running. This is a normal
operation and therefore logged as an 'Event'. Refer to the extra info
value for details about the transition.
The message may be useful for troubleshooting if trips are interrupted
unexpectedly due to hardware problems (wiring, loose contacts etc)
The value indicates which trip was interrupted and therefore not
Extra Info finished normally and the reason of the interruption.
Note: In the explanations 'any manual switch' means one of the inputs
[JREC, JRECC, JRH, ACCESS, JUEKTS, JUEKTC]
0 (hex)/ 0 (dec): Installation trip with RECALL [JMOF + JRH], and

JREC is switched ON.
1 (hex)/ 1 (dec): Running in ACCESS [ACCESS_ENABLE] and either
JREC or JMOF is switched ON
2 (hex)/ 2 (dec): Running in In Car Inspection [JRECC] and either
JREC or JMOF switched ON
3 (hex)/ 3 (dec): Running in RECALL [JRH] and JREC switched ON
4 (hex)/ 4 (dec): Running in ACCESS [ACCESS_ENABLE] and
KTC/KTS bypass switch is switched ON
5 (hex)/ 5 (dec): Running in LEARN_TRIP [JLF] and
"any_manual_switch" or JMOF is switched ON
6 (hex)/ 6 (dec): Running in SYNCH_TRIP and "any_manual_switch"
or JMOF is switched ON or Learn_trip [JLF] is needed on the system
7 (hex)/ 7 (dec): Running in CONTROL_TRIP and
"any_manual_switch" or JMOF is switched ON or, Learn_trip [JLF] or
Synch_trip is needed on the system
8 (hex)/ 8 (dec): Running in NORMAL_TRIP and "any_manual_switch"
or JMOF is switched ON or, Learn_trip [JLF] or Synch_trip is needed
on the system
9 (hex)/ 9 (dec): Running in RELEVEL_TRIP and "any_manual_switch"
or JMOF is switched ON or, Learn_trip [JLF] or Synch_trip is needed
on the system
A (hex)/ 10 (dec): Running in RECALL [JRH] and JRECC switched ON
B (hex)/ 11 (dec): Running in ACCESS [ACCESS_ENABLE] and
JRECC is switched ON
C (hex)/ 12 (dec): Running in RECALL [JRH] and both JUEKTCNA and
JUEKTSNA bypass switched ON [for NA]
D (hex)/ 13 (dec): Not used.
E (hex)/ 14 (dec): Running in RAMP_TRIP [JRF] and
"any_manual_switch" or JMOF is switched ON
F (hex)/ 15 (dec): Running in RECALL [JRH] and ACCESS switched
ON
10 (hex)/ 16 (dec): RUETFF(1) and KUETFF(1) are on, but the
command to enable these relays are not given by the control.
11 (hex)/ 17 (dec): Running in RECALL [JRH] and JUEKTS or JUEKTC
bypass switched ON [HongKong]
None.
Source ID

Causes and
1 - None.
Actions
0022 MaskErased
This section describes the Travel Control error MaskErased.

Summary
The car is performing a trip in a trip type for which the control deletes
Description the related trip type mask. This is a normal operation event. The trip
under execution will be finished, but no new trip of the same type can
be triggered until the trip type mask is set again.
None.
Extra Info
None.
Source ID

Causes and
1 Activation of special control Check why the control deleted
Actions
mode or service. the trip type mask
(VXT_STCMD_DRIVE
/VXT_TRIP_TYPE_MASK
)
0023 JHC_Pressed
This section describes the Travel Control error JHC_Pressed.

Summary
The trip was interrupted with an emergency stop because the stop
Description button on top of the car JHC was pressed. Note: This is a normal
operation event.
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0024 JHC1_Pressed
This section describes the Travel Control error JHC1_Pressed.

Summary
The trip was interrupted with an emergency stop, because the stop
Description button JHC1on top of the car has been pressed. Note: This is a normal
operation event.
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0025 JHSG_Pressed
This section describes the Travel Control error JHSG_Pressed.

Summary
Description button JHSG in the lower end of the shaft has been pressed.Note: This
is a normal operation event
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0026 JHR_Pressed
This section describes the Travel Control error JHR_Pressed.

Summary
Description button in the roller room JHR has been pressed.
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0027 JHM_Pressed
This section describes the Travel Control error JHM_Pressed.

Summary
Description button JHM in the machine room was pressed. Note: This is a normal
operation event
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0028 OverTempMotor
This section describes the Travel Control error OverTempMotor.

Summary
The measured motor temperature exceeds the temperature limits

Description defined by the parameter 'Mot Temp Limit' (PCT:
P_ANT_TEMP_OVERHEAT_MOTOR) and the minimum temperature
limit (-10°C). For motors with a temperature sensor type 'PT100
resistor' the error may indicate a problem with the sensor (short circuit
or open). The elevator system will normally recover by itself when the
motor temperature drops below the overtemperature level (see also
description for extra info).
Remark: Before the introduction of the parameter 'Mot Temp Limit' the
overtemperature limit was fix at 150°C (Check motor parameters
'supervision').
0(hex): The motor temperature is below the minimum limit of -10°C.

Extra Info The elevator remains blocked until the motor temperatur rises above
the minimum limit (fixed value)
1(hex): The motor temperature is above the maximum limit defined by

the parameter 'Mot Temp Limit'
(PCT_ANT_TEMP_OVERHEAT_MOTOR). The elevator remains
blocked until the motor temperature drops 20°C below the maximum
limit.
A(hex): The motor temperature is above the maximum limit defined by

the parameter 'PCT_ANT_TEMP_OVERHEAT_MOTOR' for more than
30min. The elevator remains blocked until the motor temperature drops
20°C below the maximum limit.
None.
Source ID
Causes and
1 In case of normal motor
Actions
temperature:
2 Incorrect or missing connection Check wiring of temperature
of the temp. sensor (PT100) measurement device.
on the motor.
3 Wrong value of parameter. Check for correct parameter
values of Motor Control ('Mot
Temp Limit').
4 Temperature sensor on motor Measure resistance of sensor
broken and use other if broken.
5 Wrong selection of sensor type Check position of
on ASILOGx board. switch/jumper on ASILOGx
board
6 When motor temperature is too
high:
7 Faulty motor windings. Check the motor windings for
short circuit on the motor
terminal box.
8 Overtemperature due to Check the main supply
excessive current. connection to the motor and
the ground connection.
9 Faulty ventilation on the motor. Check the motor ventilator(s).
10 Excessive temperature in the Measure temperature in the
machine room. machine room.
0029 TripBlocked
This section describes the Travel Control error TripBlocked.

Summary
The controller sent a telegram to Travel Control blocking the trip

Description
None.
Extra Info
None.
Source ID

Causes and
1 Establish why the controller
Actions
wants to block the drive.
2 Check for active control
features e.g. fire service or
emergency power supply
controls.
0030 NewTripBlockd
This section describes the Travel Control error NewTripBlockd.

Summary
The controller sent a telegram to Travel Control blocking the beginning

Description of a new trip but allowing the termination of the current trip.
Variodyn E: Drive has been blocked by control. This is a normal
operation event.
None.
Extra Info
None.
Source ID

Causes and
1 Establish why the controller
Actions
wants to block the drive.
2 Check for active control
features e.g. fire service or
emergency power supply
controls.
0031 PrepNewDest
This section describes the Travel Control error PrepNewDest.

Summary
While starting a new trip, before opening the brake, the controller
Description sends a new destination command in the opposite direction. The
present preparation is aborted and a new one in opposite direction
started. This is a normal procedure.
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0032 PrepClearDest
This section describes the Travel Control error PrepClearDest.

Summary
While starting a new trip, before opening the brake, the controller
Description cancels the destination sent to Travel Control. Note: This is a normal
procedure.
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0033 RelvNewDest
This section describes the Travel Control error RelvNewDest.

Summary
While executing a re-levelling trip, a new destination is received. Note:

Description A re-levelling trip should only take place if the load in the car changes
so, that the ropes length change by more than 3mm.
None.
Extra Info
None.
Source ID

Causes and
1 Check if the drive repeats the
Actions
re-levelling trip frequently. If
this is the case check the
shaft_parameter in Travel
Control, specially the
tacho_factor. If any of these
values is changed, repeat the
learn_trip.
2 A car becomes much lighter None. A re-levelling trip is then
while at rest. normal. In that case this event
does not mean abnormal
operation.
0034 SH_Timeout
This section describes the Travel Control error SH_Timeout.

Summary
During trip preparation the auxiliary (feedback) contact of the main

Description contactor SH or SH1 (resp. RH or RH1 if fitted) failed to indicate that
the contactor is on (input KSF/KSF1). The trip preparation is aborted.
Software name of error message:
CONTACTOR_TIMEOUT_PREPARING
Value is depending on the type of frequency converter and the control

Extra Info system in use. Value indicates the circumstances of the trip abortion
and the phase of the trip preparation.
Identification of source code file ('prepare_trip')

Source ID

Causes and
1 Defect in control circuit of main Check the wiring of the main
Actions
contactor contactor including safety
circuit and triggering of
contactor from drive.
2 Faulty contactor Check the main contactor SH,
SF (auxiliary contact) and the
wiring to the control pcb.
3 Faulty input on control pcb. Check if input for feedback
contact is working; replace pcb
if necessary (ASIXxx,
ASILOGxx, GCIOxx )
4 Timing problem The software uses the internal
parameter 'SH_DELAY' for this
monitoring. This parameter can
not be adjusted with CADI or
SMLCD. Contact field support.
0035 FC_Timeout
This section describes the Travel Control error FC_Timeout.

Summary
Trip preparation aborted due to timeout or negative preparation

Description acknowledge message from inverter. Software name of error message:
FC_TIMEOUT_PREPARING.
When preparing for a new trip Travel Control requests the preparation
status of the inverter (Motor Control). If the Motor Control does not
respond as expected (e.g. within the predefined time), Travel Control
aborts the preparation of the trip. The preparation of a trip by travel
control consists of the following states (phases):
INIT_START_DRIVE
WAIT_CONTACTORS
WAIT_SH_CLOSED
ASK_FC_STATUS
ACTIVATE_FC
WAIT_VECSYS_SH_CLOSED (not used with DC drive)
START_DRIVE_END
See also error message 'SH Timeout'
Variodyn E only: VF20/30 interrupted starting trial that had been

already begun.
Value indicates the cause of the trip abortion and the phase of the trip
Extra Info preparation:
with VecSYS/Variosys inverter

10(hex0A): 'Preparation False' message received from inverter in
phase 'WAIT_CONTACTORS'
20(hex14): 'Preparation Wrong Trip Type' message received from
inverter in phase 'WAIT_CONTACTORS'
01(hex01): 'Preparation False' message received from inverter in
phase 'ASK_FC_STATUS'
21(hex15): 'Preparation Wrong Trip Type' message received from
inverter in phase 'ASK_FC_STATUS'
02(hex02): Timeout occurred in phase 'ASK_FC_STATUS' because no
response from inverter after time FC_DELAY.
03(hex03): Timeout occurred in phase 'ACTIVATE_FC' because
'FC_STATE' (inverter state) not in state 'FC_RUNNING' after time
defined by FC_DELAY
with Magnetek inverter:

01(hex01): Timeout occurred in phase 'ASK_FC_STATUS' because no
response from inverter after time FC_DELAY.
02(hex02): Timeout occurred in phase 'ACTIVATE_FC' because
'FC_STATE' (inverter state) not in state 'FC_RUNNING' after time
defined by FC_DELAY.
with Variodyn E:
Distance covered away from start [mm].

Source ID

Causes and
1 Motor Control (inverter) not Check Inverter.Check
Actions
ready for new trip connection to Motor Control.
2 Incorrect parameter on Travel Adjust the time that Travel
Control Control waits for Motor Control
by the parameter
START_UP_PARA.FC_DELAY
3 Variodyn E: Inaccurate Check (and adjust if
parameter setting (frequency necessary) frequency
converter) converter parameter.
0036 Timeout Preparing
This section describes the Travel Control error Timeout Preparing.

Summary
The trip preparation exceeds the maximum allowed time limit defined
Description by the parameter (P_ANT_TIME_START_UP). In addition to the
contactor timeout and the 'fc-timeout' the overall timeout monitoring
checks if the preparation for a trip exceeds the predefined time limit.
This maximum time is not field adjustable.
Software name of error message is
OVERALL_TIMEOUT_PREPARING.
Modification Jan 26 2010: Error renamed from 'No Start Ok' to 'Timeout
Preparing'
Value of the internal variable 'prepare_state'. Identifies the trip

Extra Info preparation phase during which the error occurs. Not all preparation
phases are used in the different deployments (control systems); it
depends on the control system architecture. The numbers for the
different states of the individual trip preparation steps are not in
ascending order for the trip preparation sequence.
Extra info values for SW since 2009:

00 (hex)/ 0 (dec): PREP_INIT,
01 (hex)/ 1 (dec): PREP_END
02 (hex)/ 2 (dec): PREP_ABORT
03 (hex)/ 3 (dec): WAIT_FOR_RUET_OFF
04 (hex)/ 4 (dec): DECIDE_DRIVE, DECIDE_DRIVE
05 (hex)/ 5 (dec): WAIT_FOR_ISKT3
06 (hex)/ 6 (dec): DECIDE_AFTER_ISKT3
07 (hex)/ 7 (dec): WAIT_FOR_RFE_ON
08 (hex)/ 8 (dec): FINDING_DIRECTION
09 (hex)/ 9 (dec): WAIT_FOR_ISKT5_SPEZ_DOOR
0A (hex)/10 (dec): WAIT_CALC_FINISHED
0B (hex)/11 (dec): WAIT_FOR_REDUCE_ACCELERATION
0C (hex)/12 (dec): DECIDE_REDUCED_SPEED
0D (hex)/13 (dec): DECIDE_MOTOR_TRIP_TYPE,
WAIT_FOR_RUET_ON
0E (hex)/14 (dec): WAIT_FOR_RSK_OFF
0F (hex)/15 (dec): EARLY_SB, WAIT_FOR_RSK_ON
10 (hex)/16 (dec): WAIT_FOR_TRIP_START, WAIT_FOR_RFE_OFF
11 (hex)/17 (dec): WAIT_FOR_T2_TOGGLE
12 (hex)/18 (dec): WAIT_FOR_SAFETY_CHAIN,
DECIDE_MOTOR_TRIP_TYPE
13 (hex)/19 (dec): STARTING_DRIVE
14 (hex)/20 (dec): EARLY_SB
15 (hex)/21 (dec): WAIT_FOR_RUET, WAIT_FOR_TRIP_START
16 (hex)/22 (dec): WAIT_FOR_SAFETY_BYPASS_CONTACTS
17 (hex)/23 (dec): WAIT_FOR_SAFETY_CHAIN
18 (hex)/24 (dec): WAIT_FOR_DOOR_CONTACTS
19 (hex)/25 (dec): WAIT_FOR_DOOR_LOCK_MONITOR
1A (hex)/26 (dec): WAIT_FOR_RUET
1B (hex)/27 (dec): WAIT_FOR_T2_TOGGLE STARTING_TRIP
1C (hex)/28 (dec): WAIT_FOR_LEARN_STATUS
1D (hex)/29 (dec): WAIT_FOR_MAX_FLOOR_LEARNT
1E (hex)/30 (dec): WAIT_FOR_KCAM
1F (hex)/31 (dec): WAIT_FOR_CDD_DEACTIVATED
20 (hex)/32 (dec): WAIT_FOR_ALL_FLOORS_POSITION
21 (hex)/33 (dec): WAIT_FOR_COMMISSION_NR_CHECK
22 (hex)/34 (dec): WAIT_FOR_CDD_DEACTIVATED_EARLY_SB,
23 (hex)/35 (dec): PREP_STARTING_TRIP
Extra info values for control SW before 2009:

00 (hex)/ 0 (dec): PREP_INIT,
01 (hex)/ 1 (dec): PREP_END,
02 (hex)/ 2 (dec): PREP_ABORT,
03 (hex)/ 3 (dec): WAIT_FOR_RUET_OFF,
04 (hex)/ 4 (dec): DECIDE_DRIVE,
05 (hex)/ 5 (dec): WAIT_FOR_ISKT3,
06 (hex)/ 6 (dec): DECIDE_AFTER_ISKT3,
07 (hex)/ 7 (dec): WAIT_FOR_RFE_ON,
08 (hex)/ 8 (dec): FINDING_DIRECTION, determine the direction of
movement for the given trip_type
09 (hex)/ 9 (dec): WAIT_FOR_ISKT5_SPEZ_DOOR,
0A (hex)/10 (dec): WAIT_CALC_FINISHED, Calculation of the trip plan
0B (hex)/11 (dec): WAIT_FOR_RSK_ON,
0C (hex)/12 (dec): WAIT_FOR_RFE_OFF,
0D (hex)/13 (dec): DECIDE_MOTOR_TRIP_TYPE,
0E (hex)/14 (dec): STARTING_DRIVE, Start the drive (inverter) in
order to prepare it for the trip.
0F (hex)/15 (dec): EARLY_SB,
10 (hex)/16 (dec): WAIT_FOR_TRIP_START, Wait for the trip release
signal from the control (VXT_START_OK)
11 (hex)/17 (dec): WAIT_FOR_SAFETY_BYPASS_CONTACTS,
12 (hex)/18 (dec): WAIT_FOR_SAFETY_CHAIN, Wait for safety circuit
closed
13 (hex)/19 (dec): WAIT_FOR_DOOR_CONTACTS, Maximum time
delay (Parameter: door_contact_delay) for bouncing contacts
KTS/KTC
14 (hex)/20 (dec): WAIT_FOR_DOOR_LOCK_MONITOR,
15 (hex)/21 (dec): WAIT_FOR_RUET,
16 (hex)/22 (dec): STARTING_TRIP
17 (hex)/23 (dec): WAIT_FOR_REDUCED_ACCELARATION
18 (hex)/24 (dec): DECIDE_REDUCED_SPEED
19 (hex)/25 (dec): WAIT_FOR_RUET_ON
1A (hex)/26 (dec): WAIT_FOR_RSK_OFF
1B (hex)/27 (dec): WAIT_FOR_T2_TOGGLE
1C (hex)/28 (dec): WAIT_FOR_LEARN_STATUS
Source ID

Causes and
1 Depending on number in extra Check that the start-up
Actions
info. parameters are set correct:
The parameter time_start_up
has to be bigger than the
parameters fc_delay +
sh_delay.
0037 CarAtLevel
This section describes the Travel Control error CarAtLevel.

Summary
The car receives a destination command to the floor where it is at rest.

Description Note: If the internal Travel Control call simulation is active, this event
appears periodically.
None.
Extra Info
None.
Source ID
0038 TargetLost
This section describes the Travel Control error TargetLost.

Summary
The target (destination) floor received is outside the range known by

Description Travel Control. Therefore no direction decision was taken.
None.
Extra Info
None.
Source ID

Causes and
1 Incorrect parameters Check the parameter
Actions
shaft_para.max_floor.
2 Incorrect selector translation Check also the selector
table translation table.
3 Problems in the controller Establish why the controller
wants to send the drive to go
to a none existent floor
0039 NoDirRelv
This section describes the Travel Control error NoDirRelv.

Summary
A re-levelling request appears, but no direction decision can be taken,

Description because the car is outside the re-levelling range.
None.
Extra Info
None.
Source ID

Causes and
1 Give a call to any floor
Actions
0040 NoPHS_Learn
This section describes the Travel Control error NoPHS_Learn.

Summary
For IG type position tacho (incremental):

Description At the beginning of the learn trip (after the preparation trip) the car
should be within the fin of PHS Photocell (IN_FIN). If this is not the
case the preparation for the learn_trip is aborted. If the PHS
connection to Travel Control is missing, the internal status is
PHS=IN_FIN. Therefore, without PHS connected, the learn trip will
start normally. The trip will abort when passing the first KSE magnet.
For AGSI/ALSIS type position tacho (absolute encoder):

Trip will be aborted if the learn trip is triggered outside door zone
magnet (KUET).
For MOSIS / SALSIS:

At the end of the preparation trip the control expects to have crossed
the lowest floor while the car is slowing down. This because the
preparation ends 2cms beyond [below] the lowest floor. If the car
undertravels this distance, then the lowest floor will not be learnt and if
the learn trip continues, then the learn trip will learn 1 less floor [i.e. the
lowest floor] and end unsuccessfully. A possible reason for this error
would be misaligned floor magnets [which the control expects at
KSE_DISTANCE below the lower KSE]. Another reaason could be
incorrectly adjusted drive parameters [like interia, etc] which would
affect the speed regulation so the car is not following the speed curve.
Not used
Extra Info
None.
Source ID
Causes and
1 With IG type (incremental) Check the KSE signal
Actions
position tacho: (distance, polarity of magnet,
wiring).
2 With IG type (incremental) Check wiring to PHS input.
position tacho:
3 With IG type (incremental) Check ground connection of
position tacho: photocell PHS.
4 With AGSI or ALSIS (absolute Check the KUET signal
encoder) type position tacho: (polarity of magnet, wiring).
5 With AGSI or ALSIS (absolute Check operation of KUET(1)
encoder) type position tacho: inputs on car interface board
6 With MoSIS / SALSIS type Check sensor & magnet for
position tacho: floor detection
7 Incorrect drive parameters Check drive setting parameters
0041 ErrTachoFact
This section describes the Travel Control error ErrTachoFact.

Summary
Missmatch detected between actual fin length and value defined with
Description parameter 'FIN_LENGTH' during learn trip after passing a fin. The
actual fin length is measured using the position tacho signal and
converted with the parameter 'TACHO_FACTOR' (inc/m).
None.
Extra Info
None.
Source ID

Causes and
1 Incorrect parameter values Check the parameters
Actions
(shaft) 'tacho_factor' and 'fin_length'
(shaft_para).
0042 LowKSE_Low
This section describes the Travel Control error LowKSE_Low.

Summary
Actual distance from bottom floor level to the position of the lower KSE
Description magnet is shorter than the value defined with parameter
'KSE_DISTANCE'. Measurment is done when the car passes the lower
KSE magnet during the learn trip. The trip is aborted if the difference is
more than 5cm.
Comments: See also error description for error 'No_PHS_Learn'.
None.
Extra Info
None.
Source ID

Causes and
1 PHS not connected Check the PHS signal. If PHS
Actions
is not connected this event will
occur (status of car appears
'IN_FIN' constantly ).
2 Incorrect shaft information Check the KSE signal
(distance, polarity of magnet,
wiring ).
3 Check that the PHS photocell
is working correctly and is
mounted in the right position.
0043 LowKSE_High
This section describes the Travel Control error LowKSE_High.

Summary
Actual distance from bottom floor level to the position of the lower KSE
Description magnet is longer than the value defined with parameter
'KSE_DISTANCE'. Measurment is done when the car passes the lower
KSE magnet during the learn trip. The trip is aborted if the difference is
more than 5cm.
Comments: See also error description for error 'No_PHS_Learn'.
None.
Extra Info
None.
Source ID

Causes and
1 PHS not connected Check the PHS signal. If PHS
Actions
is not connected this event will
occur (status of car appears
'IN_FIN' constantly ).
wiring ).
3 Check that the PHS photocell
is working correctly and is
mounted in the right position.
0044 UpperKSE
This section describes the Travel Control error UpperKSE.

Summary
Travel control compares the actual position of the switch KSE-U (from
Description the top floor) with the value defined by the parameter 'KSE distance'. If
the difference is bigger than the allowed limit of 150mm the learn trip
does not finish.
None.
Extra Info
None.
Source ID

Causes and
1 Incorrect position of KSE Check position and polarity of
Actions
magnet in shaft. KSE magnets.
2 Distances and parameters not Check distance between the
equal two upper KSE magnets; it has
to match the value of
parameter 'GAP_LENGTH'.
0045 NoFloorTop
This section describes the Travel Control error NoFloorTop.

Summary
When the car passes the upper KSE (KSE-U) during learn trip (up-
Description direction), travel control expects to reach the uppermost floor after the
distance defined with parameter 'kse_distance'. The car then slows
down accordingly. If PHS is not IN_FIN at the end of the trip, the learn
procedure is aborted.
None.
Extra Info
None.
Source ID

Causes and
1 Check KSE distance and
Actions
polarity of magnet.
0046 ErrFloorTop
This section describes the Travel Control error ErrFloorTop.

Summary
The number of floors found during the learn trip does not match the
Description number of floors calculated from the configuration data (PCT). The
number of floor is derived from the
'SELECTOR_TRANSLATION_TABLE' in the PCT. The learn trip will
be aborted if values do not match.
Comments: Some types of floor fins have an additional hole to attach a
safety cord from fin to fin. Make sure these holes are not in the track of
the photocell PHS or are covered reliably so that the photocell will not
detect a wrong floor this way. For troubleshooting verify the number of
floors and the related floor distances with CADI (shaft image). Possibly
there were more floors found than configured and some floor distances
may be too small (e.g. 100mm)
None.
Extra Info
None.
Source ID
ID Possible causes of Actions to be taken

Causes and message
Actions
1 Incorrect parameters Check parameter values in table
'SELECTOR_TRANSLATION_TABLE'
with CADI (number of entries in table
is equal to number of floors for
elevator).
2 Problem with floor Use CADI to examine the shaft image
detection for number of floors found during learn
trip.
3 PHS device not mounted Check the horizontal distance
properly between PHS photocell and the fin.
0047 ErrReleveling
This section describes the Travel Control error ErrReleveling.

Summary
During a re-levelling trip the car moves/drifts outside the distance for
Description relevelling set by the parameter 'Relevel Distance'. Trigger Condition:
abs( actual_position - car_position_current_stop ) > relevel_dist
Not used
Extra Info
Identification number of source code file

Source ID

Causes and
1 Check the Motor Control.
Actions
2 Load measuring device sends Check the load information
incorrect laod value from the load measurement
device. Recalibrate load
measurement device.
3 Vertical oscillation of car during Try to increase the values for
(un-) loading of car parameters J_RELEVEL,
A_RELEVEL, V_RELEVEL (
motion parameters ).
0048 InvldTripType
This section describes the Travel Control error InvldTripType.

Summary
Invalid trip type. Software error

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call Ebikon.
0049 ErrFloorCTP
This section describes the Travel Control error ErrFloorCTP.

Summary
Software error
Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call Ebikon.
0050 NoDistRelv
This section describes the Travel Control error NoDistRelv.

Summary
The software detects that the car is outside the relevel zone defined by
Description the parameter 'Relevel Distance' during the preparation for a relevel
trip. The software aborts the preparation for the relevel trip. In case the
error occurs too frequent the elevator shuts down with fatal error. This
situation may occur in situations where the car moves due to a high
'load change rate' when the car is loaded or unloaded on a floor. The
same effect may be caused by high rope stretch/shrink when the car
load changes (bouncing effects).
Based on field experience the decision was made to no longer log this
error (modification in software June 2011).
None.
Extra Info
None.
Source ID

Causes and
1 Wrong parameter values. Check the parameter for the
Actions
relevelling zone 'Relevelling
Distance'. 'Minimum Distance'
2 Excessive car movement at Check for causes of the car
standstill. movement at standstill.
3 Inappropriate triggering of the Check/adjust the parameter
relevelling trip. 'Relevelling delay'.
0051 ZeroParam
This section describes the Travel Control error ZeroParam.

Summary
Problem found during trip preparation when calculating the trip plan.
Description See extra info value for more details.
00: one of the parameters (motion parameters) for trip curve

Extra Info computation is zero (CTP_ZERO_PARAMETER)
01: not used
02: attempt is made to start for a NORMAL trip without a tripplan
Identification number of the source code file (MOD_PREPARE_TRIP)

Source ID

Causes and
1 Check for zero parameters in
Actions
motion_para.
2 Call field support
0052 OverflowCTP
This section describes the Travel Control error OverflowCTP.

Summary
The RAM area allocated for the calculation of the trip_plan is not large
Description enough. For high rise buildings with high nominal speeds a large room
area is needed, but even this will not be sufficient if extremely low
acceleration and TERV parameters are set. Ensure that these
parameters are set at between 300 and 2000 (mm/s2 and mm/s3).
None.
Extra Info
None.
Source ID

Causes and
1 Increase the parameters which
Actions
define the curves:
motion_para.j1 - a2 - j3 - j5 -
a6 - j7
2 This is a software deficiency.
Please inform Ebikon even if
you where able to solve the
problem by increasing the
parameters
0053 NoSTR_Com
This section describes the Travel Control error NoSTR_Com.

Summary
The communication with the controller is broken.

Description Travel Control is still able to run if the safety circuit is closed. Use CADI
to simulate calls on Travel Control. This procedure is useful to find out
if whether the drive is healthy and eventually to evacuate passengers.
None.
Extra Info
None.
Source ID

Causes and
1 Check the hardware
Actions
connections.
2 Check the healthiness of the lift
bus members.
0054 PCT_Checksum
This section describes the Travel Control error PCT_Checksum.

Summary
Unable to calculate checksum of pct_drive during the configuration

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call Ebikon.
0055 NoMCR_Com
This section describes the Travel Control error NoMCR_Com.

Summary
Communication with frequency converter (motor control) can not be

Description established or is lost. The communication between control and inverter
is also monitored in standstill; the control requests the commissioning
and error state periodically from the inverter.
Remark: On control software versions released before Sep. 2012

interruption of the communication between inverter and (travel) control
is logged with error 'FC_Fault'.
Information about the circumstances when communication to the

Extra Info inverter is not working:
0: Communication interrupted during a trip, e.g. bus cable physically

removed while the car is moving.
1: The travel control does not get a response from the inverter after
requesting parameters.
2: The travel control does not get a response from the inverter when
expecting the parameter checksum to be received.
3: The travel control does not get a response from the inverter when
expecting the acknowledge message after sending a parameter to the
inverter.
4: The travel control could not send the STOP_EDIT message to the
inverter.
5: The travel control receives a negative acknowledge from the inverter
after sending the STOP_EDIT command.
6: The travel control does not receive an acknowledge from the
inverter after sending the STOP_EDIT command.
7: The travel control does not receive an acknowledge from the
inverter after requesting the commissioning state or error state. Travel
control requests commissioning state and error state periodically from
the inverter.
None.
Source ID

Causes and
1 Bus cable between Travel Check if bus cable is
Actions
Control and Motor Control not connected to pcb on Motor
connected. Control (inverter) and Travel
Control (ASIX, ASILOG, etc).
2 Broken pcb on frequency Check if pcb on Inverter (Motor
converter. Control) is damaged and
replace if necessary. Try to
access the Motor Control with
SMLCD or CADI. This will
check the hardware
connection.
3 Interface pcb on control where Replace pcb if necessary.
bus cable is connected to
broken (ASILOGx, ASIXx)
4 EMC Problems Check shielding (motor cable,
encoder, RS422...), separate
motor cable from all others.
0056 CarNoStop
This section describes the Travel Control error CarNoStop.

Summary
The trip monitoring detects that the car is still moving after the brake
Description has closed. This may occur when the brake capability of the machine
brake is insufficient.
When finishing a trip (normal stop or emergency stop) the travel control
deactivates the brake and waits for the brake to close. After the brake
contacts indicate that the brakes have closed the software checks the
car speed periodically and expects the car to stop within the time limit
defined by the internal parameter 'MOVE_SHUTDOWN' (default value:
4 sec). The condition that the car has stopped is that the car does not
move more than 10mm within 1 sec (for a tacho factor of 3000inc/m). If
the car still moves after the time defined by the parameter
'MOVE_SHUTDOWN' the error is generated and the control aborts the
trip. There is no way to set the parameter 'MOVE_SHUTDOWN'
manually.
This monitoring detects an unintended movement of the car at the end

of a trip if the brake torque is insufficient or if the car keeps moving for
another reason (monitoring of the car speed in standstill is done with
'overspeed' detection). This monitoring is also active during an
emergency stop but only if mains power is available.
See also error message #737 (motor control)
None.
Extra Info
For internal use only

Source ID
Causes and
1 Incorrect brake adjustment or Verify brake action by
Actions
faulty brake. performing an emergency stop
at full speed in up direction
with empty car and check if the
car comes to rest. Adjust
brake.
Remark: Use the brake test
(acceptance test) to measure
the average car deceleration
rate after emergency stop. Be
aware of possible rope slip on
the traction sheave.
2 Insufficient traction between Check for rope slip.
ropes and traction sheave
0057 MCR_NoStop
This section describes the Travel Control error MCR_NoStop.

Summary
Drive (Motor Control) does not send message FC_IDLE or

Description ERR_NON_FATAL after trip is completed which means the motor
control itself did not finish the trip. ( internal event name:
FIN_NO_FC_IDLE )
None.
Extra Info
None.
Source ID

Causes and
1 Check the serial link to Motor
Actions
Control (pcb).
2 Check the serial interface
board on Motor Control.
3 Incorrect parameter in Travel Check the value of parameter
Control 'FC_SHUTDOWN'
0058 SH_NoStop
This section describes the Travel Control error SH_NoStop.

Summary
Monitoring of auxiliary contacts of main contactors SH/SH1 (resp.

Description RH/RH1) or brake contactors SB/SB1 has detected that contactor(s)
did not drop off after a trip within the predefined time (defined by
parameter SH_SHUTDOWN).
The extra info indicates the faulty hardware for different control
Extra Info systems.
01 (hex) / 1 (dec) : KSK/KSK1 at MX-GC, TX-GC2

02 (hex) / 2 (dec) : KSGR at TX-R5, GX-GC
03 (hex) / 3 (dec) : KSK at TX-R5, GX-GC
04 (hex= / 4 (dec) : KSK1 at TX-R5, GX-GC
05 (hex) / 5 (dec) : KSB at MX-GC, TX-R5, GX-GC
06 (hex) / 6 (dec) : KSB1 at MX-GC, TX-R5, GX-GC
None.
Source ID

Causes and
1 Bad wiring Check the auxiliary contacts of
Actions
SH, SH1, RH, RH1 or of the
component reported in the
extra info
2 Incorrect parameter value in Check the value of parameter
Travel Control 'SH_SHUTDOWN' (default
value : 200 * 10 ms = 2 sec.)
3 Faulty inputs on interface Replace interface board or
board (pcb) or brake module brake module (depending on
the control system)
0059 SingleReset
This section describes the Travel Control error SingleReset.

Summary
Event produce after every new power up of Travel Control. Also

Description pressing the reset buttons generates these event. The values stored in
RAM are not changed during a reset.
None.
Extra Info
None.
Source ID

Causes and
1 None.
Actions
0060 DoubleReset
This section describes the Travel Control error DoubleReset.

Summary
When two resets appears within 5 sec, the second one is logged as a
Description double reset.
Comments: The double reset is recognized by the software, and the
stored values in RAM are deleted. This forces the default values stored
in EEPROM and EPROM to be down-loaded. Since the car position is
also lost, a synchronisation trip will follow automatically. The double
reset can be a useful help, for example when changing a software
version that does not have the exact same data organization., or if a
parameter is altered by CADI and the default value is required.
None.
Extra Info
None.
Source ID

Causes and
1 None
Actions
0061 RSE1_Fault
This section describes the Travel Control error RSE1_Fault.

Summary
Appears when the RSE1 and RSE11 relay do not change status in
Description parallel.
None.
Extra Info
None.
Source ID

Causes and
1 Check the magnets for RSE1
Actions
and RSE11 and the relay.
0062 RSE2_Fault

Summary
Appears when the RSE2 and RSE21 relay do not change status in
Description parallel.
None.
Extra Info
None.
Source ID

Causes and
Actions
0063 RSE3_Fault

Summary
RSE3 FAULT Appears when the RSE3 and RSE31 relay do not
Description change status in parallel.
None.
Extra Info
None.
Source ID

Causes and
Actions
0064 PHS_Fault
This section describes the Travel Control error PHS_Fault.

Summary
The state of the signal from the photocell PHNR-U or PHS is changing
Description too often within a short time or distance ("bouncing"), or doesn't
change at all during a trip.
Monitoring Conditions:
1. The car left the fin but the PHS input is in state 'IN_FIN' or
2. the car is at floor level and PHS input is in state 'OUT_FIN' or
3. two PHS signals are received within a too short time which means
that the PHS signal is bouncing.
The error does not trigger an emergency stop. When the error is
detected during a trip the software will log it only after the trip when the
car has stopped. Therefore the trip-phase is always logged as
STANDSTILL in the error log. If the error occurs too frequently the
software blocks the car with FATAL. Manual reset is required.
Due to ambiguous reporting, newer SW (2012) will log the error 1626
PHNRU_STUCK instead.
8 digit hexadecimal number (0xABCDEFGH)

Extra Info
The cause of the problem has be be known for the interpretation of the
extra info.
Meaning when PHNR-U(PHS) bounces:

00000000
Meaning when the photocell didn't change at all during a trip
The states of relevant signals are encoded, see below:

Meaning of value ‘AB’:
None (Always zero)
Meaning of value 'C' :

0 'KUET_20' false, 'KUET1_20' false
1 'KUET_20' true, 'KUET1_20' false
2 'KUET_20' false, 'KUET1_20' true
3 'KUET_20' true, 'KUET1_20' true
Meaning of value 'D' :

Only for AGSI shaft info
0: PHS OUT-FIN, IUET1 false, IUET false
1: PHS OUT-FIN, IUET1 false, IUET true
2: PHS OUT-FIN, IUET1 true, IUET false
3: PHS OUT-FIN, IUET1 true, IUET true
4: PHS IN-FIN, IUET1 false, IUET false
5: PHS IN-FIN, IUET1 false, IUET true
6: PHS IN-FIN, IUET1 true, IUET false
7: PHS IN-FIN, IUET1 true, IUET true
Meaning of value 'E' :

Only for SiV/IG shaft info:
0: PHNRU(PHS)=OUT_FIN, PHNRD = OUT_FIN
1: PHNRU(PHS)=IN_FIN, PHNRD = OUT_FIN
2: PHNRU(PHS)=OUT_FIN, PHNRD = IN_FIN
3: PHNRU(PHS)=IN_FIN, PHNRD = IN_FIN
Meaning of value 'F' :

0: 'KUET' false, 'KUET1' false, 'Enable UET' false
1: 'KUET' true, 'KUET1' false, 'Enable UET' false
2: 'KUET' false, 'KUET1' true, 'Enable UET' false
3: 'KUET' true, 'KUET1' true, 'Enable UET' false
4: 'KUET' false, 'KUET1' false, 'Enable UET' true
5: 'KUET' true, 'KUET1' false, 'Enable UET' true
6: 'KUET' false, 'KUET1' true, 'Enable UET' true
7: 'KUET' true, 'KUET1' true, 'Enable UET' true
Meaning of value 'GH':

None (Always zero)
R&D use only
Source ID

Causes and
1 Interruption on wiring from Check the PHS connection
Actions
photocell to interface pcb from the photocell to the PCB.
(traveling cable)
2 Photocell not working Check the function of the
photocell: dirt, holes in the fins
(for attaching a rope) not
sealed so that the photocell
detects it, the rope between
fins, horizontal distance
beween fin and photocell.
3 Problem with ground Check the ground connection
connection between car and on top of the car and to the
machine room machine room.
4 Faulty input on the IO interface Check operation of input and
board replace pcb if necessary.
0065 PHNR_D_Fault
This section describes the Travel Control error PHNR_D_Fault.

Summary
The state of the signal from the photocell PHNR-D is changing too
Description often within a short time or distance ("bouncing"), or doesn't change at
all during a trip.
Monitoring Conditions:
1. The car left the fin but the PHNR_D input is in state 'IN_FIN' or
2. the car is at floor level and PHNR_D input is in state 'OUT_FIN' or
3. two PHNR_D signals (transitions) are received within a too short
time which means that the PHNR_D signal is bouncing.
The error does not trigger an emergency stop. When the error is
detected during a trip the software will log it only after the trip when the
car has stopped. Therefore the trip-phase is always logged as
STANDSTILL in the error log. If the error occurs too frequently the
software blocks the car with FATAL. Manual reset is required.
Due to ambiguous reporting, newer SW (2012) will log the the error
#1627 PHNRD_STUCK instead.
8 digit hexadecimal number (0xABCDEFGH)

Extra Info
The cause of the problem has be be known for the interpretation of the
extra info.
Meaning when PHNR-U(PHS) bounces:

00000000
Meaning when the photocell didn't change at all during a trip
The states of relevant signals are encoded, see below:

Meaning of value ‘AB’:
None (Always zero)
Meaning of value 'C' :

0 'KUET_20' false, 'KUET1_20' false
1 'KUET_20' true, 'KUET1_20' false
2 'KUET_20' false, 'KUET1_20' true
3 'KUET_20' true, 'KUET1_20' true
Meaning of value 'D' :

Only for AGSI shaft info
0: PHS OUT-FIN, IUET1 false, IUET false
1: PHS OUT-FIN, IUET1 false, IUET true
2: PHS OUT-FIN, IUET1 true, IUET false
3: PHS OUT-FIN, IUET1 true, IUET true
4: PHS IN-FIN, IUET1 false, IUET false
5: PHS IN-FIN, IUET1 false, IUET true
6: PHS IN-FIN, IUET1 true, IUET false
7: PHS IN-FIN, IUET1 true, IUET true
Meaning of value 'E' :

Only for SiV/IG shaft info:
0: PHNRU(PHS)=OUT_FIN, PHNRD = OUT_FIN
1: PHNRU(PHS)=IN_FIN, PHNRD = OUT_FIN
2: PHNRU(PHS)=OUT_FIN, PHNRD = IN_FIN
3: PHNRU(PHS)=IN_FIN, PHNRD = IN_FIN
Meaning of value 'F' :

0: 'KUET' false, 'KUET1' false, 'Enable UET' false
1: 'KUET' true, 'KUET1' false, 'Enable UET' false
2: 'KUET' false, 'KUET1' true, 'Enable UET' false
3: 'KUET' true, 'KUET1' true, 'Enable UET' false
4: 'KUET' false, 'KUET1' false, 'Enable UET' true
5: 'KUET' true, 'KUET1' false, 'Enable UET' true
6: 'KUET' false, 'KUET1' true, 'Enable UET' true
7: 'KUET' true, 'KUET1' true, 'Enable UET' true
Meaning of value 'GH':

None (Always zero)
R&D use only
Source ID

Causes and
1 Interruption on wiring from Check the PHNR_D
Actions
photocell to interface pcb connection from the photocell
(traveling cable) to the PCB.
2 Photocell not working Check the function of the
photocell: dirt, holes in the fins
(for attaching a rope) not
sealed so that the photocell
detects it, the rope between
fins, horizontal distance
beween fin and photocell.
3 Problem with ground Check the ground connection
connection between car and on top of the car and to the
machine room machine room.
4 Faulty input on the IO interface Check operation of input and
board replace pcb if necessary.
0066 NoGetAnswer
This section describes the Travel Control error NoGetAnswer.

Summary
The controller does not respond to VCOM GET requests

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check the controller
Actions
connection.
2 Check the controller.
0067 KUET_Fault
This section describes the Travel Control error KUET_Fault.

Summary
La monitorización de las señales de puenteo de puerta (información

Description desde los relés RUET y RUET1) indica que no funcionan
correctamente. Los relés RUET y RUET1 no conmutan en paralelo o
lo hacen fuera de la pantalla/imán de la zona de nivel de puerta.
Comentarios: Ambas señales son transmitidas a través del bus de

comunicación de la cabina. El error no activa una parada de
emergencia. Un error detectado durante un viaje sólo se registra
cuando la cabina pasa a estado de reposo. Por lo tanto, la fase de
viaje guardada en el registro siempre aparece como STANDSTILL
(reposo).
Este error también se genera en ascensores con sistema MOSIS.

Para más información acerca de la causa del error, consultar la
descripción de la información adicional que aparece más abajo. Con
MoSIS, este error queda registrado también cuando existe una
discrepancia entre el número de pisos aprendido por el MOSIS y por el
sistema de control.
El valor de información adicional es un número hexadecimal de 8

Extra Info dígitos (0xABCDEFGH) y tiene que ser decodificado/ convertido a
formato binario (cada bit tiene un significado específico).
Significado del valor 'GH' (Bit0 a Bit7):

0000 0001(bin) / 01(hex): Los estados de KUET y KUET1 son
diferentes
0000 0010(bin) / 02(hex): Enable UET falso o fuera de un piso, pero
KUET o KUET1 es VERDADERO
0000 0011(bin) / 03(hex): Enable UET verdadero y en piso, pero
KUET o KUET1 es FALSO
0000 0100(bin) / 04(hex): Los estados de KUET_20 y KUET1_20 son
diferentes
0000 0101(bin) / 05(hex): Enable UET_20 falso o fuera de un piso,
pero KUET_20 o KUET1_20 es VERDADERO
Diagnósticos adicionales para MX sólo:
0000 0110(bin) / 06(hex): Cabina en piso sin puerta en el lado 1, pero
IUET o IUET1 es verdadero
0000 0111(bin) / 07(hex): Cabina en piso con puerta en el lado 1, pero
IUET o IUET1 es falso
0000 1000(bin) / 08(hex): Cabina fuera de piso, pero IUET o IUET1 es
verdadero
0000 1001(bin) / 09(hex): Cabina en piso sin puerta en el lado20, pero
IUET_20 o IUET1_20 es verdadero
0000 1010(bin) / 0A(hex): Cabina en piso con puerta en el lado20,
pero IUET_20 o IUET1_20 es falso
0000 1011(bin) / 0B(hex): Cabina fuera de piso, pero IUET_20 o
IUET1_20 es verdadero
Significado del valor 'F' (Bit8 a Bit11):

0000(bin) / 00(hex): 'KUET' falso, 'KUET1' falso, 'Enable UET' falso
0001(bin) / 01(hex): 'KUET' verdadero, 'KUET1' falso, 'Enable UET'
falso
0010(bin) / 02(hex): 'KUET' falso, 'KUET1' verdadero, 'Enable UET'
falso
0011(bin) / 03(hex): 'KUET' verdadero, 'KUET1' verdadero, 'Enable
UET' falso
0100(bin) / 04(hex): 'KUET' falso, 'KUET1' falso, 'Enable UET'
verdadero
0101(bin) / 05(hex): 'KUET' verdadero, 'KUET1' falso, 'Enable UET'
verdadero
0110(bin) / 06(hex): 'KUET' falso, 'KUET1' verdadero, 'Enable UET'
verdadero
0111(bin) / 07(hex): 'KUET' verdadero, 'KUET1' verdadero, 'Enable
UET' verdadero
Significado del valor 'E' (Bit12 a Bit15): para TX sólo

0000(bin) / 00(hex): 'PHS' = OUT_FIN, 'PHNR_D' = OUT_FIN
0001(bin) / 01(hex): 'PHS' = IN_FIN, 'PHNR_D' = OUT_FIN
0010(bin) / 02(hex): 'PHS' = OUT_FIN, 'PHNR_D' = IN_FIN
0011(bin) / 03(hex): 'PHS' = IN_FIN, 'PHNR_D' = IN_FIN
Significado del valor 'D' (Bit16 a Bit19): para MX sólo
0000(bin) / 00(hex): 'IUET' falso, 'IUET1' falso, 'LUET' falso
0001(bin) / 01(hex): 'IUET' verdadero, 'IUET1' falso, 'LUET' falso
0010(bin) / 02(hex): 'IUET' falso, 'IUET1' verdadero, 'LUET' falso
0011(bin) / 03(hex): 'IUET' verdadero, 'IUET1' verdadero, 'LUET' falso
0100(bin) / 04(hex): 'IUET' falso, 'IUET1' falso, 'LUET' verdadero
0101(bin) / 05(hex): 'IUET' verdadero, 'IUET1' falso, 'LUET' verdadero
0110(bin) / 06(hex): 'IUET' falso, 'IUET1' verdadero, 'LUET' verdadero
0111(bin) / 07(hex): 'IUET' verdadero, 'IUET1' verdadero, 'LUET'
verdadero
Significado del valor ‘AB’ (Bit24 a Bit31): para MoSIS sólo

(decodificación de bits)
0000 0001(bin) / 01(hex): MoUET_RelaisFail activo.
0000 0010(bin) / 02(hex): MoUET_WrongFloors activo.
0000 0100(bin) / 04(hex): MoUET_reserve2 activo.
0000 1000(bin) / 08(hex): MoUET_inLuet activo.
0001 0000(bin) / 10(hex): MoUET_CmdOn activo.
0010 0000(bin) / 20(hex): MoUET_inDoorZone activo.
0100 0000(bin) / 40(hex): MoUET_v_below activo.
1000 0000(bin) / 80(hex): MoUET_OK activo.
Significado del valor “CDEFGH” (Bit0 a Bit23): ninguno (siempre
'000000')
Ejemplo 1: Error 67 con valor de información adicional h68000000 en
un sistema MoSIS
68 (Hex) / 01101000(bin): MoUET_inLuet y MoUET_inDoorZone y
MoUET_v_below activos.
Ejemplo 2: Error 67 con valor de información adicional h31000000 en
un sistema MoSIS
31(Hex) / 00110001(bin): MoUET_RelaisFail y MoUET_CmdOn y
MoUET_inDoorZone activos.
Consultar la explicación del valor de información adicional

Source ID

Causes and
1 Cableado incorrecto en la Comprobar la conexión de las
Actions
cabina señales RUET/RUET1 y de
información al circuito impreso
de interfaz de la cabina.
2 Comprobar el cableado de los
dispositivos de detección de la
zona de nivel de puerta
(PHUET / KUET)
3 Malas condiciones Comprobar si existe suciedad
ambientales (polvo, suciedad) en la célula
en el hueco fotoeléctrica/interruptores
magnéticos de la cabina.
4 Problemas eléctricos Comprobar la conexión a tierra
de la cabina y la alimentación
del circuito impreso de interfaz
y del dispositivo de puenteo de
la puerta (p.ej., PHUET)
5 Problemas de comunicación Comprobar la conexión del bus
entre el armario de maniobra y (LON) entre el armario de
la cabina maniobra y la cabina.
Advertencia: El error KUET
puede indicar un problema de
comunicación causado por otro
nodo LON (puertas, etc.)
6 Comprobar si existen
problemas de EMC causados
por el equipo Schindler o de
otros fabricantes (MX-GC:
consultar la información de
campo Nº 291)
7 Configuración Comprobar si el número de
pisos y la disposición del
hueco (puertas
delanteras/traseras) en la
configuración coincide con las
pantallas de piso situadas en
el hueco.
MX-GC: La maniobra de
control de viaje verifica, en
cada acceso, si está presente
una pantalla KUET en la parte
delantera y/o trasera.
8 Problema mecánico con los Comprobar el montaje de los
interruptores interruptores/lengüetas KUET
9 Con MoSIS: El MOSIS fue Realizar un viaje de
reemplazado, p.ej., por una aprendizaje.
unidad de otra instalación
(discrepancia en los pisos
aprendidos)

Field Feedback
1 Car Roof Comprobar conexiones a cabina RUET/RUET1,
PHUET/KUET
2 Car Roof Comprobar Fotocélula/ interruptores magnéticos
(suciedad)
3 Car Roof Comprobar conexión a tierra PHUET
4 Car Roof / Comprobar la conexión bus de la cabina al
Controller controlador
5 Comprobar Información de Campo Nr. 291
(problema EMC)
0068 SGRB_Fault
This section describes the Travel Control error SGRB_Fault.

Summary
Relay SGRB does not work properly

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check the relay and its
Actions
auxiliary contacts
0069 SBNH_Fault
This section describes the Travel Control error SBNH_Fault.

Summary
Relay SBNH does not work properly

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
auxiliary contacts
0070 SW_Warning
This section describes the Travel Control error SW_Warning.

Summary
The software detected an abnormal situation which is not considered to

Description be severe for the operation of the elevator. Warning messages are
also used to provide additional information related to other messages
logged. For further details refer to comments for the extra info and the
source identifier.
1(hex)/1(dec): Flash write error

Extra Info 2(hex)/2(dec): Flash write error
3(hex)/3(dec): Flash read error
4(hex)/4(dec): Message is sent together with error 94 'door lock fault'
(door open with KTS closed)
5(hex)/5(dec): Message is sent together with error 94 'door lock fault'
(door open with KTC closed)
043(hex)/67(dec): No acknowledge message received from inverter
(time limit 10sec.)
064(hex)/100(dec): Monitoring of drive mask in travel control
166(hex)/358(dec): Travel control IO handling error
175(hex)/373(dec): Unexpected application message received from
inverter
190(hex)/400(dec): Unknown logical state of KSE found (kse_status)
1D3(hex)/467(dec): Travel control IO handling error
1F4(hex)/500(dec): State of ETD (evaluate trip demand) found IDLE
during a trip
209(hex)/521(dec): Unknown inverter (MC) application state in travel
control
27B(hex)/635(dec): Travel control IO handling error
2FE(hex)/766(dec): Unknown state of travel control found
35A(hex)/858(dec): Calculated velocity reference too high (with
overspeed error)
446(hex)/1094(dec): Unknown acknowledge message from motor
control (VF)
44B(hex)/1099(dec): Unknown acknowledge message from motor
control (VF)
451(hex)/1105(dec): Unknown acknowledge message from motor
control (VF)
45B(hex)/1115(dec): No acknowledge message from motor control
(VF)
50D(hex)/1293(dec): Unexpected acknowledge message from inverter
while waiting for trip start scknowledge
526(hex)/1318(dec): Unknown message id from inverter while waiting
for trip start scknowledge
5A0(hex)/(1440): Unknown acknowledge message from motor control
(VF) while waiting for trip stop acknowledge
6A2(hex)/1698(dec): The VF has sent something wrong intentionally or
the message got corrupt.
6BA(hex)/1722(dec): Wrong trip type found (trip type check function)
9A3(hex)/2467(dec): Error when computing new tacho factor (function:
win_auto_tacho)
FA1(hex)/4001(dec): The function Handle_DFM had an exception
because it received a DFM telegram with invalid direction attribut
(direction BOTH instead of UP or DOWN).
Identifies the file in the core software (travel control) from where the
Source ID warning message is generated. This information gives general hint
about the nature of the problem. The extra information (see below)
gives additional information about the exact cause.
Meaning of the source id.:

1(dec): ADJUST_EVENT_VEX
2(dec): ASY_CURVES
3(dec): AUTO_TRIP
4(dec): BRAKE_PARA
5(dec): CALCULATE_VELOCITY
6(dec): CALC_TRIP_PLAN
7(dec): CHECK_VERSION
8(dec): CMD_IVXVF
9(dec): CM_COM
10(dec): CONFIG_AN
11(dec): CONTROLER_PARA_PVF
12(dec): DEFAULT_VALUES
13(dec): DIAG_TASK
14(dec): DLK_PVF
15(dec): DOORINFO_IO
16(dec): DRIVE
17(dec): DRV_TASK
18(dec): DWG_PFC_COM
19(dec): EEP_INTERFACE
20(dec): ELEVATOR_PARA_PVF
21(dec): ERROR_LOGS_PVF
22(dec): ERROR_LOG_VEX
23(dec): ETD
24(dec): EVENT_COUNTER_VEX
25(dec): EVENT_HANDLING
26(dec): EVENT_LOGS
27(dec): EXECUTE_TRIP
28(dec): FAIL_FILTERS_PVF
29(dec): FAULT_COUNTERS_PVF
30(dec): FAULT_LOG
31(dec): FINISH_TRIP
32(dec): FLT_LOGS_PVF
33(dec): FSA_TRACER
34(dec): GCI_MENU_TREE
35(dec): HANDLE_EXTERNALS
36(dec): INI_IVXVF_APPL
37(dec): INPUTS_PCC
38(dec): INPUTS_PVF
39(dec): INTSTATUS_IO
40(dec): INVERTER_PARA_PVF
41(dec): IVXVF_COMMANDS
42(dec): IVXVF_FAULT_LOGS
43(dec): IVXVF_IO
44(dec): IVXVF_TRACER
45(dec): IVXVF_UART_CTRS
46(dec): IVX_LINK_VERSION
47(dec): KALENDER
48(dec): KSE_VX
49(dec): LCD_CAR_PARA
50(dec): LCD_COMMANDER
51(dec): LCD_CONFIG_LIFT
52(dec): LCD_DATE_TIME
53(dec): LCD_DIS_LINE
54(dec): LCD_DOOR_PARA
55(dec): LCD_DRIVE_PARA
56(dec): LCD_EDIT
57(dec): LCD_ERROR_LOGS_STO
58(dec): LCD_ERR_LOGS
59(dec): LCD_GET_SELECTION
60(dec): LCD_GUINP
61(dec): LCD_HW_DRIVER
62(dec): LCD_IO
63(dec): LCD_IO_DRIVE
64(dec): LCD_IO_GET
65(dec): LCD_LIFT_STATUS
66(dec): LCD_LMS_HANDLER
67(dec): LCD_LOGIN
68(dec): LCD_MENU_TREE
69(dec): LCD_PCTACCESS
70(dec): LCD_READ_KBD
71(dec): LCD_SERVICE
72(dec): LCD_SHOW
73(dec): LCD_STATISTIC
74(dec): LCD_STO_STATISTIC
75(dec): LCD_TASK
76(dec): LCD_TIMER
77(dec): LCD_TM1_LC
78(dec): LCD_TM_STO
79(dec): LCD_VCOM_HANDLER
80(dec): LCD_VERSION
81(dec): LCD_VER_STO
82(dec): LEARN_TRIP
83(dec): LMK_VX
84(dec): LMS_COM
85(dec): LMS_COMMPARA
86(dec): LMS_FP_EXT
87(dec): LMS_LCOM
88(dec): LMS_LSTATUS
89(dec): LMS_PARA
90(dec): LMS_STATUS
91(dec): LMS_VX
92(dec): LM_CONTROL
93(dec): LOADINFO_IO
94(dec): LOAD_PARA
95(dec): LOGICAL_IO
96(dec): LON_LM
97(dec): LON_MB
98(dec): MANUAL_TRIP
99(dec): MDI_SESS
100(dec): MDI_TASK
101(dec): MMB_FUNC
102(dec): MMB_INT
103(dec): MMB_TASK
104(dec): MONITOR
105(dec): MONITOR_IO_VEX
106(dec): MOTIONCONT_IO
107(dec): MOTION_PARA
108(dec): MOTOR_PARA_PVF
109(dec): OUTPUTS_PVF
110(dec): PARA_EVENT_LOGS
111(dec): PAR_INP
112(dec): PHYSICAL2_IO
113(dec): PHYSICAL_IO
114(dec): PREPARE_TRIP
115(dec): PVF_SETTINGS
116(dec): PVF_TRACER
117(dec): REGULATION_PARA
118(dec): RESERVE_IO
119(dec): RESET_PROOF_RAM
120(dec): SEL_TRAN_TAB
121(dec): SHAFT_IMAGE
122(dec): SHAFT_PARA
123(dec): SHUTDOWN_PARA
124(dec): SIGNALS
125(dec): SIGNAL_LIST
126(dec): SIGNAL_LIST_PVF
127(dec): SIMUL_CMD
128(dec): SIM_PARA
129(dec): SIM_TASK
130(dec): SLT_EDI_INIT
131(dec): SLT_LATER
132(dec): SLT_SWITCH_SUBSYS
133(dec): START_UP_PARA
134(dec): STATISTIC_IO
135(dec): STATUS_PVF
136(dec): STATUS_VEX
137(dec): STR_CF
138(dec): STR_ER
139(dec): STR_RX
140(dec): STR_TX
141(dec): SUPERVISOR_PARA_PVF
142(dec): SWITCHES2_IO
143(dec): SWITCHES_IO
144(dec): SYNCH_TRIP
145(dec): SYSTEM_PARA_VEX
146(dec): SYSTEM_TEST
147(dec): TAR_SESS1
148(dec): TAR_SESS2
149(dec): TAR_SESS3
150(dec): TEK_PRINTF
151(dec): TEL_INTERN
152(dec): TEST_PVF
153(dec): TIF_HANDLER
154(dec): TIME_TRIP_COUNTER_PVF
155(dec): TRACED_DATA
156(dec): TRACER_SETTINGS_IVXVF
157(dec): TRACER_TRIGGERS_IVXVF
158(dec): TRACE_COND_IVXVF
159(dec): TRACE_COND_PVF
160(dec): TRACE_VARIABLES_PVF
161(dec): TRIPINFO_IO
162(dec): TRIP_CURVE_PARA_PVF
163(dec): TRIP_PROFILE
164(dec): UART2
165(dec): VCOM_ERR_CTRS
166(dec): VF_APPL_COMM
167(dec): VF_CONFIG
168(dec): VF_NET_HANDLER
169(dec): VF_SWG_COMM
170(dec): VRTX_ERROR
171(dec): VXDC_PARA
172(dec): VXDC_STATUS
173(dec): VXT_SCREEN
174(dec): VX_VRTX
175(dec): WARNING_LOGS_PVF
176(dec): WARNING_LOG_VEX
177(dec): WAR_ERR_COUNTERS_PVF
178(dec): LM_ADT
179(dec): CAN_TASK
180(dec): DCF_PARA

Causes and
1 Contact R&D department in
Actions
Ebikon if no details about the
cause of the message is
provided in the help here.
Please report all the values
logged in the event log as well
as the Travel Control Local log
entries. These are clues for the
software specialist to detect
the source of the problem.
0071 SW Error
This section describes the Travel Control error SW Error.

Summary
A severe error in the software was detected. The message indicates a

Description major problem in the software. For further details refer to comments for
the extra info. Normally no such error should occur in the field with an
ofiicially released software.
Provides information (in addition to the source ID) about the error trap
Extra Info in the software which generated the error message:
14E(hex)/334(dec): Error in trip plan calculation

155(hex)/341(dec): Unknown value for CTP message found (calculate
trip plan)
1B0(hex)/432(dec): Undefined trip type found (TP.current_trip)
200(hex)/512(dec): Undefined value for velocity state (speed
calculation)
21A(hex)/538(dec): Unknown Command to motor control (inverter)
23F(hex)/575(dec): Unknown application message from motor control
(inverter)
25B(hex)/603(dec): Unknown value in trip preparation 'start drive state'
323(hex)/803(dec): Unknown configuration message from motor
control (inverter)
3B8(hex)/952(dec): Undefined value for deceleration state found
(speed calc.)
4FC(hex)/1276(dec): Wrong application command for motor control
(inverter)
55F(hex)/1375(dec): Wrong configuration command for motor control
(inverter)
Identifies the file in the core software (travel control) from where the
Source ID message is generated. Refer to the list in the description for source id.
for error number 70.
Causes and
Actions
Ebikon.
2 Please report all the values
logged in the event log as well
as the Travel Control Local log
entries. These are clues for the

Field Feedback
1 Controller Actualizar el software MX-GC V-2.51
0072 Safety 110V
This section describes the Travel Control error Safety 110V.

Summary
This message was replaced with the message number 141 'Safety T1'
Description (Nov 2003). The description here is valid for software versions which
still use the message 72. If in doubt please check which error is logged
when the safety circuit opens.
The safety circuit opened before the first tap (ISKT1). Problem with
safety circuit power supply.
Comments: This error may be logged after main power supply is
disconnected. Other safety circuit tap inputs (ISKT2 etc.) will not create
corresponding error messages.
= 00000000: no information available

Extra Info
= xxyyyyyy: First 2 digits (xx) show diagnostics information for the
safety circuit supply (SKS). The remaining 6 digits (yyyyyy) show the
car position (decimal value in mm) when the error occured.
Extra information safety circuit supply (xx):

00: no power safety circuit suppy
For control systems with pcb SKS the following extra information is
provided:
01: Safety circuit voltage at the relays too high. In the event of a HW
failure (malfunction of the voltage regulation) the safety circuit power
supply is switched off if the voltage at the relays is too high. The
voltage level is 27.0 to 28.0 volts.
02: Safety circuit voltage at the source too low. In the event of a HW
failure (malfunction of the voltage regulation) the safety circuit power
supply is switched off if the output voltage is too low. The voltage level
is 19.0 to 20.0 volts.
03: Safety circuit output voltage too high. In the event of a HW failure
(malfunction of the voltage regulation) the safety circuit power supply is
switched off if the output voltage is too high. The voltage level is 60.1
to 60.7 volts.
04: Safety circuit Overcurrent. In the event of a short circuit to GND or
leakage current to GND the safety circuit supply is switched off. The
overcurrent limit is 300 to 500mA.
None.
Source ID

Causes and
1 No supply voltage on the Check the power supply for the
Actions
safety circuit safety circuit.
2 In case of a regulated voltage
supply: Reset the short circuit
protection of the safety circuit
supply.
3 Relais RKPH Check the phase control relay
RKPH (if available).
4 Faulty input on interface board Check the interface board and
for safety circuit tap inputs the connections to the safety
circuit. Replace board if
necessary.
0073 Safety SPT
This section describes the Travel Control error Safety SPT.

Summary
The safety circuit opened before the second tap (ISKT2) but after the
first tap (ISKT1).
Comments: Downward safety circuit tap inputs (ISKT3 etc.) will not
create corresponding error messages. Refer to wiring diagram for
contacts causing the error.
= 00000000: no information
Extra Info
= xxyyyyyy: First 2 digits (xx) hold information for software
development only.
The remaining 6 digits (yyyyyy) show the car position ( decimal value
in mm ) when the error occured.
None.
Source ID

Causes and
1 Open contact in safety circuit Check the corresponding
Actions
section in the safety circuit.
2 Bad wiring of contact(s) in Check wiring to and between
safety circuit contacts.
necessary.
0074 Safety KNE
This section describes the Travel Control error Safety KNE.

Summary
The safety circuit opened before the third tap (ISKT3) but after the
second tap (ISKT2).
Extra Info
= xxyyyyyy: First 2 digits (xx) show information for diagnostics (see
below).
Extra information (xx):

64 (hex)/100 (dec): Safety circuit is open before the third tap (ISKT3)
for more than 15 minutes. The error will not occur with switches JHC or
JHM on or active recall- or inspection control.
None.
Source ID

Causes and
Actions
section in the safety circuit.
safety circuit contacts.
necessary.
0075 Safety RTS
This section describes the Travel Control error Safety RTS.

Summary
The safety circuit opened before the fourth tap (ISKT4) but after the
third tap (ISKT3). Used for the monitoring of the landing door contacts
KTS.
Comments: Downward safety circuit tap input (ISKT5) will not create
corresponding error message. Refer also to wiring diagram for contacts
causing the error.
If this error persists increase the value of the drive parameter
'DOOR_CONTACT-DELAY' to 50 (corresponds to 0.5 s), 70 or 100.
This is time the logic waits during startup from the first time the SKD
signal 5 (safety end) is received to the moment when the door
overbridging is disabled. During this time, the door contacts may
bounce. Do not increase the value for this parameter too much
because it will further increase the trip preparation timer. More care
should be taken to improve the adjustment of the door movement.
Extra Info
development only.
None.
Source ID
Causes and
1 Bad landing door contact(s) Check switching of landing
Actions
KTS door contacts.
2 Bad wiring of landing door Check wiring to and between
contact(s) in safety circuit landing door contacts.
necessary.

Field Feedback
1 Shaft Comprobar los contactos de las puertas de
hueco
2 Controller Comprobar las conexiones al print del circuito de
seguridad
3 Controller Comprobar RTS y ajuste
0076 Safety End
This section describes the Travel Control error Safety End.

Summary
The safety circuit opened before the fifth tap (ISKT5) but after the
fourth tap (ISKT4). Used for the monitoring of the car door contact(s)
KTC.
Comments: Refer also to wiring diagram for contacts causing the error.
If the pre-opening of the door during landing is not working properly
this event may appear instead of error 'SafetyRTS'. If this error
persists, change the drive parameter 'DOOR_CONTACT_DELAY' from
50 (0.5 s) to 70 or 100. This is time the logic waits during startup from
the first time the SKD signal 5 (safety end) is received to the moment
when the door overbridging is disabled. During this time, the door
contacts may bounce. Do not increase the value for this parameter too
much because it will further increase the trip preparation timer. More
care should be taken to improve the adjustment of the door movement.
Extra Info
development only.
None.
Source ID
Causes and
1 Door contacts KTC Check switching of car door
Actions
contacts
2 Bad wiring of car door contacts Check wiring to car door
in safety circuit contacts
3 Door bridging circuit Check the door bridging circuit
necessary.

Field Feedback
1 Car Door Comprobar el contacto KTC de la puerta de
cabina
2 Car Door Comprobar el puente de contacto de la puerta
3 Controller Comprobar el print del circuito de seguridad y
los conectores
0077 LM_PrintsErr
This section describes the Travel Control error LM_PrintsErr.

Summary
Unexpected behaviour of the load measurement device. See extra

Description information for possible error causes.
Software name of error: LMS_DEVICE_FAULT
10(hex): First load measuring device (deck one) missing/faulty

Extra Info 20(hex): Second load measuring device (deck two) missing/faulty
64(hex): Load limit exceeded (20% of nominal load) for automatic zero
load calibration of the (serial) load measuring device (performed at
night).
Monitoring of load contacts. When a load contact is active the software

checks if the contacts for the lower load limits are active too. If not an
error message is sent.
Monitoring of load contacts for NA:

214(hex): KL-M is inactive with KL-X active
224(hex): KL-V is inactive with KL-X active
234(hex): KL-H is inactive with KL-X active
212(hex): KL-M is inactive with KL-V active
213(hex): KL-M is inactive with KL-H active
223(hex): KL-H is inactive with KL-V active
Monitoring of load contacts for EUAP:

114(hex): KL-M is inactive with KL-X active
124(hex): KL-H is inactive with KL-X active
134(hex): KL-V is inactive with KL-X active
112(hex): KL-M is inactive with KL-H active
113(hex): KL-M is inactive with KL-V active
123(hex): KL-H is inactive with KL-V active
None.
Source ID

Causes and
1 Check the LMS device and the
Actions
bus connection to the control
cabinet.
2 Incorrect calibration of load Check (repeat) calibration of
measuring system. load measuring system.
3 With load contacts: Wrong Check proper function of load
status of load contact inputs. contacts KL-M / KL-H /KL-V /
(e.g. KL-V active but KL-M KL-MAX / KL-X.
inactive)
4 Incorrect baud rate Check that the baud rate of the
lift bus is the same on both
Travel Control and LMS pcb
0078 LM_NoCommiss
This section describes the Travel Control error LM_NoCommiss.

Summary
The load measurement device is not commissioned.

Description Software name of error: LMS_NOT_COMMISSIONED
Identification of the load measuring system:

Extra Info 10(hex): First load measuring device (deck one)
20(hex): Second load measuring device (deck two)
None.
Source ID

Causes and
1 Do the commissioning of the
Actions
load measuring device
according to the TK.
0079 Topt_Fault
This section describes the Travel Control error Topt_Fault.

Summary
The optocoupler in parallel with the coil of SH is not working properly.

Description At standstill, TOPT reports a closed SH while the SH feedback reports
an open SH contractor.
Comments: The TOPT device is connected to Motor Control and its
status is passed by telegram to the Travel Control.
None.
Extra Info
None.
Source ID

Causes and
1 Check TOPT.
Actions
0080 OverTempMCR
This section describes the Travel Control error OverTempMCR.

Summary
Over temperature detected within Motor Control (VF).

Description Comments: The Motor Control PCB has temperature sensors on the
heat sink of the power electronics and on the brake resistors (for BR
type converters). If temperature limit is exceeded on one of the sensors
during the trip, Travel Control has 20 sec to stop the car at the next
floor, before Motor Control aborts the trip. Elevator remains blocked for
as long as overtemperature is detected.
None.
Extra Info
None.
Source ID

Causes and
1 Check the frequency converter
Actions
for overtemperature and check
the temperature sensors.
2 See also the event log in Motor
Control.
0081 TripV_Tacho
This section describes the Travel Control error TripV_Tacho.

Summary
El tacómetro de posición (distancia) de cabina falló durante el viaje. La

Description maniobra de control de viaje continúa el viaje hasta el piso más
cercano usando la información del tacómetro de velocidad del
inversor/control de la tracción.
Comentarios: La información del tacómetro de velocidad es
suministrada por el control de la tracción en forma de señal
"handshake" a cada telegrama de referencia de velocidad (bucle
cerrado). Esta información es utilizada por la maniobra de control de
viaje para calcular la posición y la velocidad de la cabina, y para
continuar el viaje actual con el tacómetro de velocidad solamente. La
cabina se detiene en el piso más cercano; no se puede garantizar una
precisión de parada normal. No obstante, la cabina se detendrá lo
suficientemente cerca del piso como para que las puertas se puedan
abrir normalmente y los pasajeros puedan salir de la cabina.
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Problema con la señal Comprobar el tacómetro de
Actions
proveniente del tacómetro de posición, así como su
posición conexión al circuito impreso de
interfaz y al hardware de éste.
2 Cable incorrecto/roto entre el Comprobar el cableado
tacómetro de posición y el
armario de maniobra
3 Tacómetro de posición Sustituir el tacómetro de
defectuoso posición
4 Problemas de EMC Comprobar si existen
interferencias EMC causadas
por el equipo Schindler o de
otros fabricantes

Field Feedback
1 Drive/ Comprobar la posición del tacómetro y las
Controller conexiones al interface
2 Comprobar Información de Campo Nr. 291, 283
(problema EMC)
0082 NoSupply12V
This section describes the Travel Control error NoSupply12V.

Summary
The emergency power supply is not connected to the Travel Control

Description print.
Comments: The Travel Control PCB has total functionality with only
24V. If a reset is carried out and 12V are not connected, a
synchronization trip is started.
None.
Extra Info
None.
Source ID

Causes and
1 Check connection 12V.
Actions
2 Check emergency power
module.
0083 NoSupply24V
This section describes the Travel Control error NoSupply24V.

Summary
No supply 24V connected to the Travel Control print (Variodyn E: PGO)

Description Comments: This event will appear every time the main switch JH is
deactivated and Travel Control keeps running under 12V. The Travel
Control runs in a very reduced mode, maintaining only the car position.
None.
Extra Info
None.
Source ID

Causes and
1 Check fuse 24V supply.
Actions
2 Check 24V connection.
3 Variodyn E:
4 Missing or defective 24V Check 24V supply
supply
5 Missing WD (resistor-diode) Install appropriate device
device on the brake (electro- properly
magnetical interferences)
6 Net power failure
0084 DMS_Spoiled
This section describes the Travel Control error DMS_Spoiled.

Summary
Strain gauge (DMS) is not working properly.

Description Software name of error: DMS_SPOILED

None.
Source ID

Causes and
1 Bad connection of strain gauge Check the connection of the
Actions
to load measuring box strain gauge devices to the
load measuring box.
2 Faulty strain gauge device Replace strain gauge device
(use strain gauge test tool for
troubleshooting)
0085 LM_ComErr
This section describes the Travel Control error LM_ComErr.

Summary
The software detects that the communication to the load measuring

Description system (LMS) is lost. Software name of error:
LMS_COM_UNAVAILABLE
Comments: TX4: With CADI in Travel Control under the menu EVENT
LOGS enter the submenu VCOM ERR CTRS to see the performance
of the lift bus connection with Travel Control.

6E(hex)/110(dec): No communication to load measuring device after

power down/power up
None.
Source ID

Causes and
1 Check the LMS device and the
Actions
bus connection to the control
cabinet
2 Incorrect baud rate TX4 only: Check the baud rate
adjustment on the pcb's.
0086 RUET_Fault
This section describes the Travel Control error RUET_Fault.

Summary
The feedback information of the relay RUET does not close during
Description preparation of a new trip.
None.
Extra Info
None.
Source ID

Causes and
1 Check the relay RUET and the
Actions
connection of the feedback
contact to the interface board.
2 Check if the related input of the
interface boad is broken.
0087 RTSC_Fault
This section describes the Travel Control error RTSC_Fault.

Summary
The feedback information of relay RTSC does not pick up during trip
Description preparation.
None.
Extra Info
None.
Source ID

Causes and
1 Check the relay RTSC and the
Actions
connection of the feedback
contact to the pcb.
0088 TachoFault
This section describes the Travel Control error TachoFault.

Summary
Major problem with the position tacho of the car. The position value
Description read from the position tacho (for incremental or absolute encoders) is
inconsistent. The value representing the car position either jumped
(difference between values too big) or no tacho impulses were
detected during the trip.
Remark: always perform a learn trip after exchange of the positon

tacho or main pcb. On controls with AGSI/ALSIS always disconnect the
position encoder (cable) with power off.
0 (hex): No signal (speed feedback) from position tacho when starting

Extra Info a trip while speed reference below the limit for underspeed error. This
monitoring is disabled with active JMOF or when finishing a trip.
1 (hex): During INSPECTION or RECALL trip the car is allowed to

move for a distance of 0.5m with a faulty position tacho (S_TACHO).
After a distance of 0.5m running with V_TACHO (speed feedback from
inverter) the control stops the car with error TACHO_FAULT.
A (hex) / B(hex): The position value read from the position tacho is not
in the shaft range. (Absolute encoder was disconnected during manual
trip.)
C (hex) / D(hex): The position value read from the position tacho is not
in the shaft range. (Absolute encoder was disconnected during
inspection trip in up direction.)
E (hex): The position value read from the position tacho is not in the
shaft range. (Absolute encoder was disconnected during inspection trip
in down direction.)
F (hex): The position value read from the position tacho is not in the
shaft range. An inspection trip in up direction was initiated with the
tacho disconnected or with the elevator out of the shaft range.
10(hex): The position value read from the position tacho is not in the
shaft range. An inspection trip in down direction was initiated with the
tacho disconnected or with the elevator out of the shaft range
10BADCAB(hex): refer to description of error 1501 'Invalid Position'
20BADCAB(hex): refer to description of error 1502 'Position Jump'
None.
Source ID

Causes and
1 Bad connection/wiring of the Check the connection of the
Actions
position tacho. position tacho to the control
(cable).
2 The position tacho is Check position tacho itself.
damaged.
3 Mechanical problems with Check that the tacho runs
position tacho/encoder. smoothly.
4 Position tacho disconnected. Reconnect position tacho.
5 Broken circuit on the interface Replace pcb.
board (ASILOGx, ASIXx) for
the position tacho.
0089 TripTimeExp
This section describes the Travel Control error TripTimeExp.

Summary
The maximum time for the duration of a trip was exceeded. The
Description monitoring of the trip time is required as per EN81-70 (chapt. 12.10)
and aims to prevent damage (mechanical wear) of the moving parts
(traction sheave, ropes) or damage of the motor, the brake and the
inverter caused by overheating. For SW releases dated earlier than
April 2006 the maximum trip time is defined by the parameter
'MAX_TRIP_TIME' only (see also description of extra info). For
software releases with later date the software calculates the maximum
trip time before each automatic trip based on the maximum speed for
the selected trip type and the maximum possible travel distance (HQ).
The software uses the calculated value to monitor the trip duration (if
the maximum travel distance is not known the parameter
'MAX_TRIP_TIME' is used instead). The software applies the following
formula to calculate the maximum trip time:
Tmax = 4*A_MAX/J_MIN + V4/A2 + V4/A6 + [(SHAFT_LENGTH -

V4*V4/A2 - V4*V4/A6) / V4] + 10s
where:
A_MAX: highest value of A2 and A6
J_MIN: lowest value of J1, J3, J5, J7
Minimum value for runtime limit is 20s
Extra info values in wwxxyyzz(hex) format are

Extra Info
wwxx(hex): Runtime limit in seconds. To calculate the runtime limit
swap the hex. values for 'ww' and 'xx' ('xxww') then convert to decimal
(see example below).
yy(hex): Zero parameter error. Values are:

00: parameters A2, A6, V4, J1, J3, J5, J7 have normal values
01: one of the parameters A2, A6, V4, J1, J3, J5, J7 used for the
calculation of the trip time is 0.
zz: The trip type of the trip for which the error is reported. Values (in
hex) are:
00: UNDEFINED_TRIP
01: INSPECTION_UP
02: INSPECTION_DOWN
03: RECALL_UP
04: RECALL_DOWN
05: INSP_CAR_UP
06: INSP_CAR_DOWN
07: UPPER_ACCESS_UP
08: UPPER_ACCESS_DOWN
09: LOWER_ACCESS_UP
0A: LOWER_ACCESS_DOWN
0B: LEARN_DRV
0C: SYNCH_DRV
0D: NORMAL_DRV
0E: RELEVEL_DRV
0F: NO_TRIP_DRV
10: RAMP_UP_DRV
11: RAMP_DOWN_DRV
Example: Extra info = 2C01000B

ww = 2C / xx = 01: calculated runtime limit is 012C (hex) = 300 s (dec).
yy = 00: no parameter with value zero.
zz = 0B: means Trip Type = LEARN_DRV (learn trip).
None.
Source ID

Causes and
1 Check the parameter Time
Actions
Stop Precision.
2 Check the traction relation.
0090 StopOverFault
This section describes the Travel Control error StopOverFault.

Summary
For A17.1 code (US and Canada) it is required that during Fire Recall
Description (JBF) the in car stop switch is not active. The control therefore includes
a relay RUEHC which jumps out the in car stop switch (COP) in the
safety circuit while the car is being recalled to the lobby. Travel Control
will report STOP_OVERRIDE_FAULT if it sees this relay go on when
the car is not on fire recall service.
Comments: Not used.
None.
Extra Info
None.
Source ID
0091 SMPB_Fault
This section describes the Travel Control error SMPB_Fault.

Summary
Relay SMPB does not work properly.

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
auxiliary contacts on Travel
Control.
0092 REC / RH HW Failure
This section describes the Travel Control error REC / RH HW Failure.

Summary
The monitoring of I/O's in Travel Control detects abnormal status of

Description I/O's of inspection panel circuit for REC or RH panel. The malfunction
can be due to unexpected activation of relays (feedback contact), bad
overbridgings or bad status of inputs. Check extra info for detailed
description of possible cause. See also error #135.
The error blocks the control persistently; a manual reset is required.
Remark: This failure message was formerly named "IVXVF HW fault".
0 (hex): All relays controlled by Travel Control are active

Extra Info unintentionally
A (hex): DRH-U button on the recall panel is pressed without active

recall control JRH; check wiring of JRH / DRH-U
B (hex) DRH-D button on the recall panel is pressed without active

recall control JRH; check wiring of JRH / DRH-D
14( hex): DREC-U button on the inspection panel is pressed without

active inspection control JREC; check wiring of JREC / DREC-U
15 (hex): DREC-D button on the inspection panel is pressed without

active inspection control JREC; check wiring of JREC / DREC-D
16 (hex): DREC-E button on the inspection panel is pressed without

active inspection control JREC; check wiring of JREC / DREC-E.
17 (hex): DREC-U button pressed for more than 30 seconds and no

trip because DREC-E not pressed simultaneously; both buttons must
be released before a new trip is initiated.
18 (hex): DREC-D button pressed for more than 30 seconds and no
trip because DREC-E not pressed simultaneously; both buttons must
19 (hex): DREC-E button pressed for more than 30 seconds and no

trip because DREC-U or DREC-D not pressed simultaneously; buttons
must be released before a new trip is initiated.
1E (hex): DRH-E button on the recall panel is pressed without active

recall control JRH; check wiring of JRH / DRH-E
32 (hex): The status of the input RTCCON is not same as the status of
the input RTC1CON (check) for more than 0.6 seconds.
33 (hex): The status of the input RTSCON is not same as the status of
the input RTS1CON (check) for more than 0.6 seconds.
34 (hex): The status of the input RTSCON_20 is not same as the

status of the input RTS1CON_20 (check) for more than 0.6 seconds.
5C (hex): Manually bridged safety circuit detected (between taps 3 and

5) with active inspection control REC. Activation of inspection control
on car is not allowed with bridge safety circuit across the inspection
control panel (JREC / JHC)
5D (hex): Used for NA: Manually bridged safety circuit detected

(between taps 3 and 5) with active inspection control REC. Activation
of inspection control on car is not allowed with bridge safety circuit
across the inspection control panel (JREC / JHC)
64 (hex): refer to description of extra information for error 74.

(monitoring of open safety circuit before the third tap ISKT3 for more
than 15 minutes is done with error 74 /changed 20.02.03)
14D (hex): The status of the input JRH is not same as the status of the
input JRHCH (check) for more than 20 seconds.
Reserved
Source ID
Causes and
1 Handling problem (wrong none
Actions
manipulation on recall- or
inspection panel)
2 Grounding or EMC problem Remove all possible ground
loops from the corresponding
pcb (i.e. use AC mains socket
in the control cabinet to power
the service laptop).
3 PCB fault Check function of I/Os' (refer to
extra info) and replace the pcb
(IVXVF / GCIOx) if necessary
4 Wiring fault Check wiring for related input
(see extra info value).
5 Safety circuit is bridged Remove bridge in safety circuit
6 Extra info 14D (hex): LDBCS If ASIXA 33 PCBA, for the
plug in BYPASS position and operation of LDBCS (landing
JRH switch not activated (only door bypass) JRH must be
for MX control system) switched ON before LDBCS
plug is set to BYPASS position.

Field Feedback
1 Car Roof Conectar inspección, presionar botones
subida/bajada, desconectar inspección
0093 AccessSwitch
This section describes the Travel Control error AccessSwitch.

Summary
NA only: The Access relay is switched on and the selected trip type is
Description not allowed.
Comments: By using the ACCESS-Key the manual trip ACCESS is
allowed in a restricted range at specific floors only. The two ACCESS-
key switches are installed on two floors:
At the floor defined with parameter 'UPPER ACCESS FLOOR' and at
the LOWEST FLOOR in the lower shaftend. Only if the car in one of
these floors, its possible to move
The car must be on one of these two floor in order to be moved using
the corresponding ACCESS-Key.
None.
Extra Info
None.
Source ID

Causes and
1 Wrong parameter values Check the value for the
Actions
parameters 'UPPER ACCESS
FLOOR' and 'LOWEST
FLOOR'.
2 Shaftinfo ACCESS Check the connection and the
wiring to the corresponding pcb
0094 DoorLockFault
This section describes the Travel Control error DoorLockFault.

Summary
El circuito de seguridad muestra que la puerta de piso o cabina está

Description cerrada (tomas de derivación ISKT4 o ISKT5 activas) mientras el
estado de la puerta es 'open' (abierta).
Comentarios: El estado de la puerta (abierto) debe coincidir con la

información (KTS y KTC) leída en el circuito de seguridad.
5(hex)/5(dec): Error de activación de la rampa de retirada (RCAM)

Extra Info 6(hex)/6(dec): Error de liberación de la rampa de retirada (RCAM)
28(hex)/40(dec): Estado del monitor del circuito de seguridad
(contactos puenteados)
29(hex)/41(dec): Estado del monitor del circuito de seguridad
(contactos puenteados)
2A(hex)/42(dec): Contacto de puerta de piso (KTS) anulado (COREA)
2B(hex)/43(dec): Contacto de puerta de cabina (KTC) anulado
(COREA)
940(hex)/2368(dec): Contacto de puerta de piso (KTS) puenteado en
el circuito de seguridad
941(hex)/2369(dec): Contacto de puerta de cabina (KTC) puenteado
en el circuito de seguridad
942(hex)/2370(dec):
943(hex)/2371(dec):
944(hex)/2372(dec): Problema en el enclavamiento de puerta durante
la preparación del viaje con TX-GC2
945(hex)/2373(dec): Problema en el enclavamiento de puerta durante
la preparación del viaje con MX-GC/TX-GC
Consultar también el mensaje de advertencia del software enviado con
'door lock fault'
Identifica el archivo del software principal desde donde se genera el

Source ID mensaje.
104(dec): Monitor
114(dec): Preparar el viaje

Causes and
1 Problema con los contactos de Comprobar los contactos de
Actions
puerta puerta y el cableado del
circuito impreso de interfaz de
la puerta.
2 Circuito de seguridad Comprobar los puentes
configurables del circuito de
seguridad.
0095 ETSL_Overspeed
This section describes the Travel Control error ETSL_Overspeed.

Summary
Overspeed detected by the ETSL device within the upper or lower

Description deceleration zones in the hoistway.
This event is generated according to the status signals (parallel inputs)

from the ETSL device (see schematics). A separate contact from the
ETSL device is used to interrupt the safety circuit (independent from
the status information signals). See also TK of ETSL device for more
information.
None.
Extra Info
None.
Source ID

Causes and
1 Wrong parameter values Check the values for
Actions
parameters A2 (acceleration)
and A6 (deceleration).
2 Other drive system error Check the operation of the
drive system.
3 Installation issue Check the vertical position of
the vanes in the shaft end
according to K603046.
0096 ETSL_VaneError
This section describes the Travel Control error ETSL_VaneError.

Summary
Unsafe operating condition detected by the ETSL device while

Description scanning the vanes.
from the ETSL. A separate contact from the ETSL device is used to
interrupt the safety circuit (independent from the status information
signals).
None.
Extra Info
None.
Source ID

Causes and
1 Wrong alignment between Check the alignment.
Actions
PHVKSE and vanes/metal
stripe.
2 Deformed or twisted metal Check the tension of the metal
stripe in the hoistway stripe.
3 A gap in the check track Cover the gap with something
without a measure vane in that interrupts IR-light. A single
front of it. plastic tape is probably not
enough.
4 There is no cutout behind a Check the cutouts.
measure vane or cutout partly
covered.
5 Dirt on optical parts. Clean the lenses in the gap of
the PHVKSE with a clean
cloth.
0097 ETSL_DeviceError
This section describes the Travel Control error ETSL_DeviceError.

Summary
Unsafe operating condition detected by the ETSL device (internal

Description error).
from the ETSL. A separate contact from the ETSL device is used to
interrupt the safety circuit (independent from the status information
signals).
None.
Extra Info
None.
Source ID

Causes and
1 Internal error of PHVKSE Cycle power (off/on) on the
Actions
PHVKSE, repeat the last trip
and test the ETSL system.
Replace the PHVKSE if the
same error message appears
again.
2 If the same error only happens
now and then, check the
electrical environment for
possible EMC problems
(unpermitted strong electro-
magnetic interference by some
other defective component like
contactors etc.)
0098 COM_Busreconf
This section describes the Travel Control error COM_Busreconf.

Summary
During the hourly supervision period, VCOM detected a number of

Description communication bus reconfigurations. This number is too high in
comparison to the number of telegrams sent and received during the
same one hour period. Telegrams can be lost.Reliable operation is no
longer guaranteed.
1 = Too many reconfigurations on the lift bus

Extra Info 2 = Too many reconfigurations on the group bus
None.
Source ID

Causes and
1 bus is faulty Check lift -, groupbus if all links
Actions
and terminators are functional.
2 Check the communication of all
subsystems which are
connected with the Bus.
3 too many messages are Trace the telegram traffic in
generated in a certain period of order to determine the source
time of the telegram flood and test
the corresponding subsystem
to verify its operation and if
necessary to exchange it.
4 another subsystem is not The problem might be caused
working properly by faulty operation of another
subsystem. To locate the faulty
subsystem, separate every
single subsystem from the bus
until the problem disappears.
5 wrong addressing on the bus Check that the number of
subsystems connected to the
bus is correct and that they all
have the correct bus
addresses
6 other possibilities Reset the Lift Control and
check if the reconfigurations
still appear.
7 NOTE: If the problem still
occurs, please contact the VX-
Center.
0099 RSK_Fault
This section describes the Travel Control error RSK_Fault.

Summary
Problema con la información de los relés RSK / RSK1

Description (comportamiento incorrecto del relé).
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Contacto de retroalimentación Comprobar el cableado y/o la
Actions
de los relés RSK / RSK1 funcionalidad de los relés RSK
defectuoso / RSK1.
2 RSK / RSK1 no se desactiva Sustituir los relés RSK/RSK1 o
según lo esperado el circuito impreso que los
alberga.
3 RSK/RSK1 no se activa Comprobar el circuito de
durante la preparación del seguridad (ISKT4 &
viaje según lo esperado ISKT5).

Field Feedback
1 Controller Comprobar RSK/RSK1, quizás cambiar el print
2 Shaft Comprobar el circuito de seguridad ISKT4 y
ISKT5
0100 RFE_Fault
This section describes the Travel Control error RFE_Fault.

Summary
Problem with the feedback contact of the relay RFE (malbehaviour of

Description relay). The relay RFE is monitored during the trip preparation. Relay
RFE has to drop after relays RSK & RSK1 have picked.
Comments: This error is only generated if the trip initiation circuit is

with relay RFE (not valid for MX-GC and TX-GC2). See also
schematics.
None.
Extra Info
None.
Source ID

Causes and
1 RFE is turned on and does not Check the wiring and the
Actions
pick up within 5 seconds functionality of RFE.
(Timeout)
2 Check all contacts/contactors
in the RFE circuit (SH, RSK,
RF, etc).
3 RFE does not turn off Check RSPFE.
0101 RTRT_Fault
This section describes the Travel Control error RTRT_Fault.

Summary
The software monitors the state of the relay RTRT (feedback contact
Description from relay)and checks if the feedback of the relay RTRT is equal to the
reference state (output which drives the relay). During a normal trip the
relay RTRT is turned on when the car speed is lower than 0.75 m/s.
Only applicable for control systems which have a dedicated RTRT
relay (TXR5 etc.) in the safety circuit.
0: Indicates the RTRT relay is not on in standstill

Extra Info 1: Indicates the RTRT relay is on during a trip at a speed above 1m/s
Identifies the file in the core software from where the message is
Source ID generated.
Refer to error message #70 for the description of the value.

Causes and
1 Bad wiring of relay RTRT or Check the wiring and the
Actions
relay broken functionality of relay RTRT.
2 Faulty electronics circuit on Replace interface board for
interface board which drives relay RTRT
the relay RTRT (see wiring
diagrams)
0102 RKUET_Fault
This section describes the Travel Control error RKUET_Fault.

Summary
Hardware error detected after activation of door bridging for door

Description preopening.
Comments: The feedback is monitored during a normal trip. RKUET
has to turn off at the trip start and must turn on when approaching the
target floor.
None.
Extra Info
None.
Source ID

Causes and
1 Malfunction of door bridging Check the operation of
Actions
RKUET.
2 Check KUET / KUET1 and
RUET / RUET1.
0103 HighSpeedStop
This section describes the Travel Control error HighSpeedStop.

Summary
For SSDC drives only: Emergency stop when the car was moving with
Description more than 0.75 m/s (150 FPM). After emergency the dymanic braking
resistors will heat up from the kinetic energy depending on the speed.
With this event the car is blocked for a short time after too many
emergency stops within a short period of time in order to prevent the
resistors from overheating.
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0104 CDOOR Bypass
This section describes the Travel Control error CDOOR Bypass.

Summary
Message when the Car Door Bypass switch (JGB) is turned on (Hydro
Description only)
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0105 SDOOR Bypass
This section describes the Travel Control error SDOOR Bypass.

Summary
Message when the Hoistway Door Bypass switch (JGB) is turned on

Description (Hydro only)
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0106 PHASE Loss
This section describes the Travel Control error PHASE Loss.

Summary
The safety circuit opened at point SKD1 (Hydro only); indicating loss of
Description 110 VAC supply to the safety string, or the power line monitor has
tripped
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0107 Pit Oil Switch
This section describes the Travel Control error Pit Oil Switch.
Summary
The oil level in the tank is low. Check to see where it went! (Hydro
Description only)
65 Hex (101 Dec): The input K_PIT_OIL is on; note that this input is
Extra Info only checked when the car is at the Fire Recall Floor.
66 Hex (102 Dec): The input K_NO_OIL is on; note that this is only
used on Electronic Valve systems, not on EECO.
None.
Source ID

Causes and
1 Oil leakage check and fix
Actions
0108 Over Temperature Oil
This section describes the Travel Control error Over Temperature Oil.
Summary
Oil temperature sensor reads above 55 degrees C. (Hydro only)

Description
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0109 KSE Failure
This section describes the Travel Control error KSE Failure.

Summary
The KSEU or KSED switch input disagrees with other inputs or with
Description where car is meant to be in the hoistway. (Hydro only)
191 Hex (401 Dec): KSED says the car is at the bottom terminal, but
Extra Info the software thought it was at another floor.
192 Hex(402 Dec): KSEU says the car is at the top terminal, but the
software thought it was at another floor.
193 Hex(403 Dec): The software thinks the car is at the bottom
terminal, but KSED isn't open.
194 Hex(404 Dec): The software thinks the car is at the top terminal,
but KSED is open.
195 Hex(405 Dec): The car is in the top terminal, but KSEU, ETSL1,
and ETSL2 don't all agree with eachother. On a Dynahyd, ETSL3 and
ETSL4 must also agree.
None.
Source ID

Causes and
1 none
Actions
0110 Motor Overload
This section describes the Travel Control error Motor Overload.

Summary
The motor overload in the linestarter has tripped, or the fault relay in
Description the softstarter has tripped. (Hydro only)
On systems with Electronic Valve, this can also be caused by ETS
overspeed opening SKD6.
None
Extra Info
None.
Source ID

Causes and
1 none
Actions
0111 No Floor Slowdown
This section describes the Travel Control error No Floor Slowdown.

Summary
Slowdown magnet sequence error. (Hydro only)

Description
191 Hex(401 Dec): car running up coming into a floor, Up slowdown

Extra Info was never seen.
192 Hex(402 Dec): car running down coming into a floor, Down
slowdown was never seen.
193 Hex(403 Dec): car running down away from a landing, Up

slowdown was not seen.
194 Hex(404 Dec): car running up away from a landing, Down

slowdown was not seen.
195 Hex(405 Dec): Car is at a floor, KHU is stuck on.
196 Hex(406 Dec): car is at a floor, KHD is stuck on.
197 Hex(407 Dec): Car missed KHD magnet going up
198 Hex(408 Dec): Car missed KHU magnet while going down.
199 Hex(409 Dec): Car fell off end of the KSEU magnet (Top Terminal
Stop)
19A Hex(410 Dec): Car fell off end of the KSED magnet (Bottom
Terminal Stop)
None.
Source ID

Causes and
1 none
Actions
0112 Pressure Switch
This section describes the Travel Control error Pressure Switch.

Summary
The pressure switch is open for more than 1 second. (Hydro only).
Description May indicate the car is hung up on an obstruction or tight rails.
None
Extra Info
None.
Source ID

Causes and message
Actions
1 none
0113 Thermistor Failure
This section describes the Travel Control error Thermistor Failure.

Summary
Occurs when the software detects that the thermistor for sensing the
Description oil temperature has failed. (Hydro only)
x65 (hex)/101 (dec): The reading is out of range. Thermistor (Analog

Extra Info Oil Temp Sensor) not detected or bad thermistor.
xC9 (hex)/201 (dec): The oil is still cold after 10 attempts to heat it with
bypass operation.
x12D (hex)/301 (dec): Oil temperature has reached 62 degrees and
was in the hot oil temperature range before (> 55 degrees). Motor can
not shutdown dispatch immediately.
x191 (hex)/401 (dec): Oil temperature has jumped more than +/- 5
degrees within 1 second. Check temp sensor / oil level
None.
Source ID

Causes and
1 Broken sensor replace sensor.
Actions
2 Low oil level refill oil.
0114 Anti Stall Failure
This section describes the Travel Control error Anti Stall Failure.
Summary
The car did not reach the floor as expected. (Hydro only)
Description
C8 Hex (200 Dec): check K_PIT_OIL input.

Extra Info C9 Hex (201 Dec): check K_NO_OIL input.
CA Hex (202 Dec): check MOTOR-THERMAL input
CB Hex (203 Dec): check for missing floor magnet (KLU or KLD)
CC Hex (204 Dec): 90 second travel timer has expired. Check valve
adjustment.
CD Hex (205 Dec): Reason Unknown. Notify HX help center.
None.
Source ID

Causes and
1 none
Actions
0115 Duty Cycle Regulation
This section describes the Travel Control error Duty Cycle Regulation.
Summary
not used
Description
None
Extra Info
None.
Source ID

Causes and
1 none
Actions
0116 KLU Fault
This section describes the Travel Control error KLU Fault.

Summary
KLU floor switch/magnet is not working properly. (Hydro only)

Description
C9 Hex(201 Dec): Releveling, but can't find KLU. Check KLU switch
Extra Info and wiring.
191 Hex(401 Dec): At the end of an up trip, saw KLU and KLD, but
never saw KLU alone. Check for slow acting KLU switch, check for
short between KLU and KLD.
192 Hex(402 Dec): Running up, got to KLD without ever seeing KLU.
Check for broken KLU switch or wiring.
193 Hex(403 Dec): Leaving floor on a down trip, never saw KLU on
alone. Check for slow acting KLU switch, check for short between KLU
and KLD.
194 Hex(404 Dec): KHU just went on, meaning car is a couple feet
from the floor, but KLU is also on. Check for KLU stuck on. Check for
KHU going on when it shouldn't.
195 Hex(405 Dec): KHD just went on, meaning car is a couple feet
from the floor, but KLU is also on. Check for KLU stuck on. Check for
KHD going on when it shouldn't.
196 Hex(406 Dec): Ran past a floor without seeing KLU turn on.
197 Hex(407 Dec): KLU is on when far from a floor, outside slowdown
zone.
FFF Hex(4095 Dec): The encoder says we are at the floor, but the KLU
signal is missing. Check KLU sensor and wiring.
None.
Source ID

Causes and
1 none
Actions
0117 KLD Fault
This section describes the Travel Control error KLD Fault.

Summary
KLD floor switch/magnet is not working properly. (Hydro only)

Description
C9 Hex(201 Dec): Releveling, but can't find KLD. Check KLD switch
Extra Info and wiring.
191 Hex(401 Dec): At the end of an up trip, saw KLU and KLD, but
never saw KLD alone. Check for slow acting KLD switch, check for
short between KLU and KLD.
192 Hex(402 Dec): Running down, got to KLU without ever seeing
KLD. Check for broken KLD switch or wiring.
193 Hex(403 Dec): Leaving floor on an up trip, never saw KLD on

alone. Check for slow acting KLD switch, check for short between KLU
and KLD.
194 Hex(404 Dec): KHU just went on, meaning car is a couple feet
from the floor, but KLD is also on. Check for KLD stuck on. Check for
KHU going on when it shouldn't.
195 Hex(405 Dec): KHD just went on, meaning car is a couple feet
from the floor, but KLD is also on. Check for KLD stuck on. Check for
KHD going on when it shouldn't.
196 Hex(406 Dec): Ran past a floor without seeing KLD turn on.
197 Hex(407 Dec): KLD is on when far from a floor, outside slowdown
zone.
FFF Hex(4095 Dec): The encoder says we are at the floor, but the KLD
signal is missing. Check KLD sensor and wiring.
None.
Source ID

Causes and
1 none
Actions
0118 NodeAlive
This section describes the Travel Control error NodeAlive.

Summary
The error is logged when the communication with the CPB board in the
Description car station is reestablished after a 'Node_Dead' error. (Hydro NA only)
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0119 Node Dead
This section describes the Travel Control error Node Dead.

Summary
Lost communications with the CPB board in the car station. (Hydro
Description only)
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0120 Door Lock Failure
This section describes the Travel Control error Door Lock Failure.
Summary
Car door or hoistway door lock opened while the car was running. (for
Description Hydro only)
The extra info shows the floor number (not the floor name) the car was
Extra Info closest to when it happened.
None.
Source ID

Causes and
1 none
Actions
0121 Switch Fault
This section describes the Travel Control error Switch Fault.

Summary
Conflicting status of input signals.

Description
Hydro:
Extra Info 65 Hex(101 Dec): The normally open and normally closed contacts of
JRECC (In Car Inspection switch ).
66 Hex(102 Dec): The normally open and normally closed contacts of
JRH (Machine Room Inspection switch ).
67 Hex(103 Dec): Top of car UP or DOWN button pressed but JREC
(top of car inspection switch) on AUTO.
68 Hex(104 Dec): ISKT6 is on, but RSK1 is off.
69 Hex(105 Dec): ISKT6 is off, but RSK1 is on.
6A Hex(106 Dec): ISKT6 is on, but RSK2 is off.
6B Hex(107 Dec): ISKT6 is on, but RSK2 in on.
6E Hex(110 Dec): The normally open and normally closed contacts of
JREC (Top of Car Inspection switch ).
6F Hex(111 Dec): The normally open and normally closed contacts of
JGB (car door bypass switch ).
JLB (hoistway door bypass switch ).
ACCESS_EN (ACCESS Enable switch in car station).
78 Hex(120 Dec): The LVL_ZONE relay is not going on and off when
KLU and KLD go on and off.
TX R5:
A Hex(10 Dec): The normally open and normally closed contacts of
ACCESS_EN (ACCESS Enable switch in car station).
B Hex(11 Dec): The normally open and normally closed contacts of
C Hex(12 Dec): The normally open and normally closed contacts of
D Hex(13 Dec): The normally open and normally closed contacts of
JRH (Machine Room Inspection switch ).
E Hex(14 Dec): The normally open and normally closed contacts of
JLB (hoistway door bypass switch ).
F Hex(15 Dec): The normally open and normally closed contacts of
JGB (car door bypass switch ).
None.
Source ID
0122 KSE Fail 2
This section describes the Travel Control error KSE Fail 2.

Summary
The software thought it was at the top floor, but the KSE and ETS
Description magnets say it is not at the top floor. Car makes a synch trip. (Hydro
only)
None.
Extra Info
None.
Source ID

Causes and
1 none
Actions
0123 EV Error
This section describes the Travel Control error EV Error.

Summary
An error has been reported by the Electronic Valve control. (Hydro

Description only)
1F5 Hex (501 Dec) = Dynahyd A1 = Replace CRIPEV board.

Extra Info 1F6 Hex (502 Dec) = Dynahyd A2 = Replace CRIPEV board.
1F9 Hex (505 Dec) = Dynahyd A5 = No upwards start. Check mainline
for missing phase, blown fuse, or incorrect phase rotation.
1FA Hex (506 Dec) = Dynahyd A6 = No upwards start due to
softstarter UTS signal being on when it shouldn't be. Softstarter "off
delay" must be set to zero.
1FB Hex (507 Dec) = Dynahyd C1 = No start due to the safety circuit
being open.
1FC Hex (508 Dec) = Dynahyd C2 = No upward start due to the CCR
relay being on when it shouldn't. Replace the CRIPEV board.
1FD Hex (509 Dec) = Dynahyd C3 = No upward start due to CCR relay
not picking when it should. Replace the CRIPEV board.
1FE Hex (510 Dec) = Dynahyd C5 = No upward start due to abnormal
servo valve current. Check the servo valve and the wiring to it. Replace
the Servo Valve or the CRIPEV board.
1FF Hex (511 Dec) = Dynahyd C7 = No downward start due to wrong
operational mode. Trying to make a trip while in "air bleed", "learn
hydro" or "learn floor" mode.
202 Hex (514 Dec) = Dynahyd E1 = Replace the CRIPEV print
203 Hex (515 Dec) = Dynahyd E2 = Stopped during an upward travel
due to the softstarter run command being off. Replace the CRIPEV
board.
204 Hex (516 Dec) = Dynahyd E6 = Stop during up trip. Check
mainline for missing phase or blown fuse.
206 Hex (518 Dec) = Dynahyd H7 = Stopped during an upward travel
after overrunning the destination floor. Check the encoder rope for
slack. Make a new “Learn Hydraulic Travel” with cold oil. Replace
servo valve.
207 Hex (519 Dec) = Dynahyd H8 = Car moved while in air bleed
mode (bypass). Replace the servo valve.
208 Hex (520 Dec) = Dynahyd R1 = Communication software timeout.
226 Hex (550 Dec) = Dynahyd A9 = "Learn floor" cannot be started.
The car must be level at the bottom floor (KLU, KLD, KSED all on).
258 Hex (600 Dec) = Unable to send messages to the Dynahyd
control. Check that Dynahyd software chip is installed. Replace
CRIPEV.
259 Hex (601 Dec) = Dynahyd D5 = Got an up command when the car
was at the top floor. May be ignored if on inspection, otherwise do a
new "learn floor".
25A Hex (602 Dec) = Dynahyd D6 = Got a down command when the
car was at the bottom floor. May be ignored if on inspection, otherwise
do a new "learn floor".
2BC Hex (700 Dec) = Dynahyd D4 = The floor was found more than
50mm from where it used to be. Check for encoder slip. Check to see if
KLU/KLD magnet has moved.
2BD Hex (701 Dec) = Dynahyd P1 = The "learn floor" travel in the up
direction failed because it did not see all the magnets properly. Check
magnets and try again.
2BE Hex (702 Dec) = Dynahyd P2 = The "learn floor" travel in the
down direction failed because it did not see all the magnets properly.
Check magnets and try again.
320 Hex (800 Dec) = Dynahyd D3 = The learn floor travel in up
direction failed because it did not see KSED magnet properly. Check
magnet and switch and try again.
322 Hex (802 Dec) = Dynahyd U6 = The car stopped where the
encoder says the floor is, but KLU and KLD are missing. Check for
missing floor magnet, check for encoder slip.
None.
Source ID
Causes and
1 none
Actions
0124 EV Shutdown
This section describes the Travel Control error EV Shutdown.

Summary
A serious error has been reported by the Electronic Valve control.

Description (Hydro only)
1F5 Hex (501 Dec) = Framing error communicating with Dynahyd.

Extra Info Replace Dynahyd software chip. Replace CRIPEV board.
1F6 Hex (502 Dec) = Checksum error communicating with Dynahyd.
Replace Dynahyd software chip. Replace CRIPEV board.
1F7 Hex (503 Dec) = Count error communicating with Dynahyd.
1F8 Hex (504 Dec) = Timeout error communicating with Dynahyd.
1F9 Hex (505 Dec) = Unknown message recieved from Dynahyd.
1FB Hex (507 Dec) = Dynahyd A7 = The "UTS" (motor up to speed)
signal from the softstarter did not arrive in time. Check the wiring,
check the softstarter, check the sizing of the motor and softstarter.
1FC Hex (508 Dec) = Dynahyd C4 = The command to start the motor
isn't working. Replace CRIPEV board.
1FD Hex (509 Dec) = Dynahyd C6 = Incorrect current thru the Servo
Valve. Check wiring. Replace CRIPEV board. Replace Servo Valve.
204 Hex (516 Dec) = Dynahyd E3 = Replace CRIPEV board.
205 Hex (517 Dec) = Dynahyd E4 = Replace CRIPEV board.
206 Hex (518 Dec) = Dynahyd E5 = CCR relay dropped during an up
trip . Replace CRIPEV board.
207 Hex (519 Dec) = Dynahyd E7 = Motor run time is too long during
up trip. Check car speed, check for encoder slipping.
208 Hex (520 Dec) = Dynahyd H1 = Servo valve at full current, but car
not moving up. Check the Pressure relief valve. Clean the servo filter.
Check out the encoder system. Replace the servo valve. Replace
CRIPEV board.
209 Hex (521 Dec) = Dynahyd H2 = Speed feedback says car is not
moving during up trip. Check the encoder system. Check the Pressure
relief valve. Check for overloaded or hung-up car.
20A Hex (522 Dec) = Dynahyd H3 = Servo valve at minimum current,
but car not moving down. Make sure the check valve near the
Pressure relief valve is closed. Check out the encoder system. Check
the wiring to the VMD valve. Clean the servo filter. Dismantle the valve
under the screw and check for any dirt. Replace the VMD valve.
Replace the servo valve. Replace CRIPEV board.
20B Hex (523 Dec) = Dynahyd H4 = Speed feedback says car is not
moving during down trip. Check the encoder system. Make sure the
check valve near the Pressure relief valve is closed. Check the rupture
valve. Check the VMD coil and wiring. Dismantle the valve under the
screw and check for any dirt. Replace the VMD valve. Replace the
servo valve. Replace CRIPEV board.
20C Hex (524 Dec) = Dynahyd H5 = 30% overspeed during a down
trip. Check the encoder system. Check the servo valve and wiring.
Replace the servo valve.
20D Hex (525 Dec) = Dynahyd H6 = The VMD valve did not close at
the end of a down trip. Caution: do not turn off power until after you
lower the car to the buffer using the manual lowering valve. Power on
the servo valve is preventing the car from falling. Dismantle the VMD
valve and check for any dirt. Replace the VMD if necessary. Replace
the CRIPEV print.
20E Hex (526 Dec) = Dynahyd H9 = The car speed exceeded 0.3 m/s
while relevelling. Replace the servo valve. Replace the CRIPEV print.
20F Hex (527 Dec) = Dynahyd D7 = The KSEU magnet was found
more than 50mm from where it used to be. Check for encoder slip.
Check to see if KSEU magnet has moved.
210 Hex (528 Dec) = Dynahyd D8 = The KSEU magnet was found too
far from where it used to be. Check for encoder slip. Check to see if
KSED magnet has moved.
321 Hex (801 Dec) = Dynahyd U5 = KLU or KLD signal stuck on during
a trip. Check switches and wiring. Replace CRIPEV board.
384 Hex (900 Dec) = Dynahyd U1 = Car didn't slow down in response
to the servo current as it approached the top floor
385 Hex (901 Dec) = Dynahyd U2 = Car didn't slow down in response
to the servo current as it approached the bottom floor
None.
Source ID

Causes and
1 none
Actions
0125 EV Event
This section describes the Travel Control error EV Event.

Summary
Information (event) reported by the Electronic Valve control. (Hydro

Description only)
1F5 Hex (501 Dec): Dynahyd C8 = Command to stop at this floor

Extra Info arrived too late (up trip). If this happens often, notify Gettysburg.
1F6 Hex (502 Dec): Dynahyd C9 = Command to stop at this floor

arrived too late (down trip). If this happens often, notify Gettysburg.
1F7 Hex (503 Dec): Dynahyd T1 = Communication software timeout.

None.
Source ID
0126 Wrong hardware
This section describes the Travel Control error Wrong hardware.

Summary
The software detects hardware not compatible with the configuration

Description (PCT) or with the deplyoment (basic control system). The value given
in the extra info defines the wrong combination.
0x00000000: The software detects a CAN interface board (EBCAN)

Extra Info which is not supported for the actual deplyoment or configured (refer to
the parameter SHAFT_INFO_SETTING).
NA only:
1: PCT specifies A17.1-2000, which requires ASIBNA2 relay board.
2: PCT specifies A17.1-2000, which requires CRIPNA3 board.
3: PCT specifies A17.1-2000, which requires CRIPEV3 board.
None.
Source ID
0127 SI_Error
This section describes the Travel Control error SI_Error.

Summary
Error on MoSis. Problem with configuration of/for MoSis detected.

Description
0x00000000: Software detects a CAN interface board (EBCAN) but

Extra Info MoSis is not supported/configured by the software (based on
deployment).
0x00000001: Software detects mismatch between MoSis and control

(number of learnt floors). Occurs after replacing MoSis device or after
exchange of main controller board (GCIOB).
None.
Source ID

Causes and
1 Wrong hardware configuration Check hardware (interface
Actions
(extra info: 0) boards)
2 Mismatch (extra info: 1) Do a learn/measuring trip.
0128 LOWER_KSE_LOW_SYNCH
This section describes the Travel Control error

Summary LOWER_KSE_LOW_SYNCH.
When the car passes the lowest KSE magnet during the synch trip,its
Description position is checked. If the measured value is less than the value given
with the parameter 'shaft_para.kse_distance' the trip is aborted.
This error is similar to LowKSE_Low which occurs during learn trip.
None
Extra Info
None.
Source ID

Causes and
1 PHS signal not connected Check the PHS signal. If PHS
Actions
is not connected (always
IN_FIN) this event will appear.
wiring).
Check that the PHS photocell
works properly and is
mechanically in the right
position.
0129 EQ_Midpoint_Fault
This section describes the Travel Control error EQ_Midpoint_Fault.

Summary
The error is generated when the Earthquake service requires 'EQ

Description midpoint' and the EQ midpoint (car position when car and
counterweight on same level) is not set or invalid. The error is not
generated if the Earthquake service is not available or if
P_STR_COLLISION_SWITCH is not set. The EQ midpoint position is
considered to be valid anywhere between bottom and top floor level.
Ideally the EQ midpoint should be set when the car position is exactly
at same position with counterweight.
01: The error message indicates that the Earthquake service is

Extra Info available and the parameter P_STR_COLLISION_SWITCH is TRUE
but the EQ midpoint position is not set or invalid.
02: The error indicates that the EQ midpoint set command was done
with the elevator control in normal mode. The EQ midpoint set
command is allowed only in Inspection/Recall mode and with the drive
in standstill condition.
None.
Source ID

Causes and
1 The lift has a collision switch Park the car where the car and
Actions
(counterweight derailment counterweight crossheads are
switch) but the midpoint is not even, and use the "set EQ
set. The control will only switch midpoint" function on CADI or
to automatic operation after SMLCD.
the midpoint is set and valid.
0130 PCT_Drive_Para
This section describes the Travel Control error PCT_Drive_Para.

Summary
The value of a PCT Drive Parameter does not match with the current
Description hardware or
is not allow the according to the Deploment Rules. Refer to the Extra
Info for identification of the Drive Parameter.
Parameter Id. (hexadecimal) of parameter with wrong value.

Extra Info for example:
0h4B : P_ANT CODE_TYPE

0h77 : P_ANT_SAFETY_TYPE
None.
Source ID

Causes and
1 A PCT has been downloaded Download PCT with correct
Actions
with a wrong parameter value, value or modifiy parameter to
or the correct value with CADI or
SMLCD.
2 The Parameter has been Modifiy parameter to the
changed to an invalid value. correct value with CADI or
SMLCD.
0131 SI KNE active
This section describes the Travel Control error SI KNE active.

Summary
Activation of KNE switch due to overtravel in the hoistway top or

Description bottom terminal end.
This message is send by MoSis/SALSIS to indicate the reason of the
opening of the KNE switch.
none
Extra Info
None.
Source ID

Causes and
1 Car is in KNE zone (below Move car out of KNE zone.
Actions
bottom floor or above top floor)
2 Unintended car movement Refer to description for error
detected 139
3 Internal error in MOSIS Refer to description for error
1515
0132 SI ETSL active
This section describes the Travel Control error SI ETSL active.

Summary
Opening of the ETSL switch due to the detection of the ETS / ETSL
Description overspeed condition in the top or bottom hoistway terminals.
This message is send by MoSis/SALSIS device to report the reason of

the activation of the ETSL switch. The MoSis/SALSIS device has
detected that the car speed has exceeded the ETS / ETSL speed
monitor curve in the hoistway terminal.
none
Extra Info
None.
Source ID

Causes and
1 Car speed exceeded the limit Check parameter for speed
Actions
for ETSL monitoring; ETSL and acceleration. Check
monitoring is done by MOSIS. configuration data of drive.
This error will occur during
acceptance test for ETSL.
2 Car speed exceeded the limit Check parameter for speed
for NTSD monitoring; NTSD and acceleration. Check
monitoring is done by MOSIS. configuration data of drive.
This error will occur during
acceptance test for NTSD.
3 Internal error in MOSIS Refer to description for error
1515
0133 Inverter Para Not Accepted
This section describes the Travel Control error Inverter Para Not
Summary Accepted.
The inverter (motor control) rejects a parameter which is sent by the

Description travel control because:
- the value of the drive parameter is out of range
= xxxxyyyy: First 4 digits (xxxx) indicate the (hex) value of the

Extra Info PCT_GROUP of the parameter. The next 4 digits (yyyy) indicate the
(hex) value of the PCT_ID of the parameter.
None.
Source ID

Causes and
1 Value of the drive parameter is Check and correct the value of
Actions
out of range or incorrect. the rejected parameter or
reinitialize the inverter.
0134 NTSD active
This section describes the Travel Control error NTSD active.

Summary
This error is logged when the NTSD monitoring is activated and the
Description control brings the car to the terminal stop using the dedicated
deceleration rate instead of the normal speed curve. The NTSD
(normal terminal slowdown) monitoring detects that the car speed is
above the speed limit calculated from the car position and the
deceleration rate defined with the parameter A_NTSD [see also
settings parameter 'ETSL_TYPE'].
For this error message the severity is calculated based on the

occurence rate related to number of trips and not to time; the error type
reported is depending on the number of trips that the elevator does.
The following limkits are used: When the NTSD is triggered once or
twice in 1000 trips, a warning is logged. When NTSD is triggered 3
times in 1000 trips, an ERROR is sent. When it is triggered more than
3 times in 1000 trips, the control blocks the elevator permanently
(FATAL).
The error count keeps accumulating until the FATAL is reset. Therefore
resetting the actual counter value with CADI has no influence on the
severity.
None
Extra Info
None
Source ID

Causes and
1 Elevator moves too fast Check the value of the
Actions
towards the shaft end (top or parameter 'A_NTSD'. The
bottom) value shall be between
0.8m/s2 and 1.4m/s2
2 Wrong parameter value Check parameters
KSE_DISTANCE and A_NTSD
and set to correct value.
0135 DREC_DRH_button
This section describes the Travel Control error DREC_DRH_button.

Summary
The software monitors the inputs for inspection control and logs an
Description error if it detects an abnormal status of the inputs. This monitoring
does not block the elevator. See extra info for detailed description of
cause.
23.04.04 Error message added

10.06.04 DREC-Z replaced with DREC-E
A (hex)/10 (dec): DRH-U button on the recall panel is pressed without

Extra Info active recall control JRH; check wiring of JRH / DRH-U
B (hex)/11 (dec): DRH-D button on the recall panel is pressed without

active recall control JRH; check wiring of JRH / DRH-D
D (hex)/13 (dec) DRH-U button pressed for more than 30 seconds and
no trip because DRH-E not pressed simultaneously; both buttons must
E (hex)/14 (dec) DRH-D button pressed for more than 30 seconds and
no trip because DRH-E not pressed simultaneously; both buttons must
F (hex)/15 (dec) DRH-E button pressed for more than 30 seconds and
no trip because DRH-U or DRH-D not pressed simultaneously; buttons
14( hex)/20 (dec): DREC-U button on the inspection panel is pressed

without active inspection control JREC; check wiring of JREC / DREC-
U
15 (hex)/21 (dec): DREC-D button on the inspection panel is pressed
D
16 (hex)/22 (dec) DREC-E button on the inspection panel is pressed

E.
17 (hex)/23 (dec) DREC-U button pressed for more than 30 seconds

and no trip because DREC-E not pressed simultaneously; both buttons
18 (hex)/24 (dec) DREC-D button pressed for more than 30 seconds

and no trip because DREC-E not pressed simultaneously; both buttons
19 (hex)/25 (dec) DREC-E button pressed for more than 30 seconds

and no trip because DREC-U or DREC-D not pressed simultaneously;
buttons must be released before a new trip is initiated.
1E (hex)/30 (dec): DRH-E button on the recall panel is pressed without

active recall control JRH; check wiring of JRH / DRH-E
None.
Source ID

Causes and
1 Handling problem (wrong none
Actions
manipulation on recall- or
inspection panel)
2 Bad wiring of inspection panel Check wiring of inspection
panels and wiring from
inspection panels to control
cabinet
3 Faulty input on IO interface Check input and replace board
board if input is not working
0136 Safety Bypass
This section describes the Travel Control error Safety Bypass.

Summary
Error detected by the monitoring for the korea fire operation safety
Description circuit bypass device. For Fire Recall and Firefighter Operation in
Korea parts of the safety circuit (pit, emergency exit, and door
contacts) is bridged by the control.
This bypass devices are monitored whether the relay is switching ON /

OFF and whether the two inverted feedback contacts have a plausible
status. The relay has to switch within 3 seconds.
The failed bypass device is indicated in the extra info as follows:

Extra Info
0x01: RUESG/KUESG/KUESG1 check failed
0x02: RUENA/KUENA/KUENA1 check failed
0x03: RUETFF/KUETFF/KUETFF1 check failed
None.
Source ID

Causes and
1 Faulty interface Replace corresponding pcb
Actions
0137 JHCC_Pressed
This section describes the Travel Control error JHCC_Pressed.

Summary
Description button JHCC in the car was pressed. Note: This is a normal operation
event
None
Extra Info
None.
Source ID

Causes and
1 None
Actions
0138 Brake Not Set
This section describes the Travel Control error Brake Not Set.
Summary
Brakes do not close at the end of a trip. After a normal (automatic) trip
Description the machine brakes do not close as expected (status of KB contacts
show open brakes) after the 'brake off' command timeout following the
'SB off' command. This is a critical situation because potentially no
mechanical torque is applied to the traction sheave. In this situation the
inverter remains powered and keeps the car on the floor. The door(s)
are closed immediately and remain closed (door open button is
disabled).
Version 1: With closed doors the inverter is switched off and the
elevator is blocked permanently with fatal error.
Version 2: The monitoring of the closing of the brakes was extended

with a safety parking trip. As soon as the door(s) are closed the
elevator performs a slow speed trip top the top floor where the inverter
is switched off.
Before opening the doors manually to release the passengers a check

must be done to confirm that the brake applies sufficient mechanical
torque to hold the car.
On elevators with only one physical switch on the brake (KB) a safety
parking is done if the KB does not indicate closed brake at the end of a
trip.
ndef
Extra Info
None.
Source ID
Causes and
1 Brake does not close due to Check brake for correct
Actions
mechanical obstruction function (sufficient mechanical
torque applied to machine)
2 Problem with wiring of KB Check wiring and operation of
contacts to control KB contacts
3 Faulty input circuit for KB Check input status of KB
contacts (both !) contacts. Replace pcb if
necessary
0139 Unintended Movement detected
This section describes the Travel Control error Unintended Movement

Summary detected.
Unintended car movement detected. The unintended movement

Description detection device opens the safety circuit. The detection device
depends on the control system and the area. The control shuts down
the elevator until manual reset of FATAL state.
No car movement is allowed until the unintended movement detection

device is manually reset. Unintended movement protection device is
required by the following codes: A17.1 / Hong Kong Code of Practice
(Am.10) / Korean Code / EN81-1 Am.3. (list subject to change)
The error is also logged when the acceptance test for unintended
movement is performed. The limits for the detection of unintended
movement depend on the detection device. With MoSIS the limits are:
distance from floor > 100mm or speed >0.3m/s.
For NA: a unintended movement of the traction sheave (motor

encoder) on the motor detected by the inverter is considered as an
uninteneded movement. The inverter logs the error #737.
The control also logs the error.
not used
Extra Info
None.
Source ID

Causes and
1 Problem with traction system Check machine brake and
Actions
friction between traction
sheave and ropes.
2 Wrong car movement Check load measuring system,
(direction/speed) during position tacho.
releveling
0140 Safety T4B
This section describes the Travel Control error Safety T4B.

Summary
El circuito de seguridad se abrió antes de la toma de derivación

Description (ISKT4B), pero después de la toma de derivación previa (ISKT4). Esta
toma de derivación sólo está disponible en un hardware específico
(p.ej., LONICK).
Comentarios: Las entradas de toma de derivación anteriores del
circuito de seguridad (ISKT5, etc.) no crearán mensajes de error
correspondientes. Consultar el esquema eléctrico para conocer los
contactos que causan el error.
= 00000000: sin información

Extra Info
= xxyyyyyy: Los 2 primeros dígitos (xx) contienen información para
desarrollo de software exclusivamente.
Los 6 dígitos restantes (yyyyyy) muestran la posición de la cabina
(valor decimal en mm) en el momento en que se produjo el error.
Ninguna.
Source ID

Causes and
1 Contacto(s) KTS de la puerta Comprobar la conmutación de
Actions
de piso defectuoso(s) los contactos de la puerta de
piso.
2 Cableado defectuoso de los Comprobar el cableado hacia y
contactos de la puerta de piso entre los contactos de la
en el circuito de seguridad puerta de piso.
3 Entrada defectuosa en el Comprobar el circuito impreso
circuito impreso de interfaz de interfaz (LONICK) y las
para las entradas de toma de conexiones con el circuito de
derivación del circuito de seguridad. Reemplazar el
seguridad circuito si es necesario.
0141 Safety T1
This section describes the Travel Control error Safety T1.

Summary
The safety circuit opened before the first tap (ISKT1) or there was a
Description problem with safety circuit power supply.
Comments: This error may be logged after main power supply is

disconnected. Other safety circuit tap inputs (ISKT2 etc.) will not create
corresponding error messages when the input T1 opens.
Rem: New error messages were introduced (May 10, 2011) for the
monitoring of safety circuit supply (see message numbers 1587, 1588,
1589, 1590).
00000000: no information available

Extra Info
Decoding of 8 digit hexadecimal number (yyzzzzzz)
yy: diagnostics information for the safety circuit supply (SKS). The SKS
board monitors the safety cuircuit supply for undervoltage, overvoltage
and overcurrent.
zzzzzz: these 6 digits show the car position (decimal value in mm)
when the error occured.
Extra information safety circuit supply (yy):

00: no power safety circuit suppy
For control systems with pcb SKS (TX2) the following extra information
is provided:
01: Safety circuit voltage at the relays RSK/RSK1 too high (SAFVRHI).
In the event of a HW failure (e.g. malfunction of the voltage regulation)
the safety circuit power supply is switched off if the voltage at the
relays is too high. The voltage limit is 27.0 to 28.0 volts.
02: Safety circuit supply voltage too low (SAFVLO). In the event of a
HW failure (malfunction of the voltage regulation) the safety circuit
power supply is switched off if the output voltage is too low. The
voltage limit is 19.0 to 20.0 volts.
03: Safety circuit supply voltage too high (SAFVHI). In the event of a
HW failure (malfunction of the voltage regulation) the safety circuit
power supply is switched off if the output voltage is too high. The
voltage limit is 60.1 to 60.7 volts.
04: Safety circuit Overcurrent (SAFOVCURR). In the event of a short

circuit to GND or leakage current to GND the safety circuit supply is
switched off. The overcurrent limit is 300 to 500mA.
TX2 control only: When the SKS detects a fault on the safety circuit
supply the LED on the SKS board indicates on which channel (1-5) the
error occurred. This information (channel number) is not available to
the software.
Identification of source code file

Source ID

Causes and
1 No supply on the safety circuit Check the power supply for the
Actions
safety circuit. In case of
regulated voltage suppy: Reset
the short circuit protection for
safety circuit supply (push
button DUEISK).
2 Relais RKPH faulty. Check the phase control relay
RKPH (if available).
necessary.
0142 Safety T2

Summary
The safety circuit opened before the second tap (ISKT2) but after the
Description first tap (ISKT1).
00000000: no information
Extra Info
yy: information for software development only.

Source ID

Causes and
1 Open contact in safety circuit Check the contacts in the
Actions
(between ISKT1 and ISKT2) corresponding section in the
safety circuit.
safety circuit (between ISKT1 contacts in safety circuit as per
and ISKT2) wiring diagram.
necessary.

Field Feedback
1 Comprobar el circuito de seguridad ISKT1,
ISKT2, ISTK3
0143 Safety T2A
This section describes the Travel Control error Safety T2A.

Summary
The safety circuit opened before the tap (ISKT2A) but after the first tap
Description (ISKT1).
Extra Info

Source ID

Causes and
Actions
(between ISKT1 and ISKT2A) section in the safety circuit.
Refer to wiring diagram.
safety circuit (between ISKT1 contacts.
and ISKT2A)
necessary.
0144 Safety T2B

Summary
The safety circuit opened before the tap (ISKT2B) but after the
Description previous tap (ISKT2A).
Extra Info

Source ID

Causes and
Actions
between ISKT2A and ISKT2B section in the safety circuit.
Refer to wiring diagram.
safety circuit (between ISKT2A contacts.
and ISKT2B)
necessary.
0145 Safety T3

Summary
El circuito de seguridad se abrió antes de la tercera toma de

Description derivación (ISKT3), pero después de la segunda toma de derivación
(ISKT2).

Extra Info
= xxyyyyyy: Los 2 primeros dígitos (xx) muestran información de
diagnóstico (ver más abajo).
Información adicional (xx):

64 (hex)/100 (dec): El circuito de seguridad está abierto antes de la
tercera toma de derivación (ISKT3) durante más de 15 minutos. El
error no se producirá si los interruptores JHC o JHM están activados o
si la maniobra de recuperación o inspección está activa.
Ninguna.
Source ID

Causes and
1 Contacto abierto en el circuito Comprobar la sección
Actions
de seguridad correspondiente del circuito de
seguridad.
2 Cableado defectuoso del/de Comprobar el cableado hacia y
los contacto(s) del circuito de entre los contactos.
seguridad
circuito impreso de interfaz de interfaz y las conexiones al
para las entradas de toma de circuito de seguridad.
derivación del circuito de Reemplazar el circuito si es
seguridad necesario.
0146 Safety T3A
This section describes the Travel Control error Safety T3A.

Summary

Description (ISKT3A), pero después de la toma de derivación previa (ISKT2).
circuito de seguridad (ISKT3B, etc.) no crearán mensajes de error

Extra Info

Ninguna.
Source ID

Causes and
Actions
seguridad.
seguridad
0147 Safety T3B

Summary

Description (ISKT3B), pero después de la toma de derivación previa (ISKT3A).

Extra Info

Ninguna.
Source ID

Causes and
Actions
seguridad.
seguridad
0148 Safety T4

Summary
Utilizado para la monitorización de los contactos KTS de la puerta de

Description piso. El circuito de seguridad se abre antes de la cuarta toma de
derivación (ISKT4), pero después de la tercera (ISKT3). El mensaje
queda registrado si:
a) El circuito de seguridad se abre durante un viaje debido a la
apertura inesperada de un contacto (cualquiera) de la puerta de piso.
b) El circuito de seguridad no se cierra como estaba previsto después
de que la puerta se haya cerrado.
Comentarios: La entrada de toma de derivación anterior del circuito de

seguridad (ISKT5) no creará un mensaje de error correspondiente.
Consultar también el esquema eléctrico para conocer los contactos
que causan el error.
Si persiste este error, se deberá aumentar el valor del parámetro de
tracción 'DOOR_CONTACT-DELAY' a 50 (que corresponde a 0,5 s),
70 ó 100. Este es el tiempo que espera la lógica durante el arranque,
desde la primera vez que se recibe la señal SKD 5 (lado de seguridad)
hasta el momento en que se deshabilita el puenteo de puerta. Durante
este tiempo, los contactos de puerta pueden rebotar. No aumentar
demasiado el valor de este parámetro, ya que aumentará también el
temporizador de la preparación del viaje. Se ha de tener mucho
cuidado para mejorar el ajuste del movimiento de la puerta.

Extra Info
Ninguna.
Source ID

Causes and
1 Contacto(s) KTS de la puerta Comprobar la conmutación de
Actions
de piso defectuoso(s) los contactos de la puerta de
piso KTS.
2 Cableado defectuoso de los Comprobar el cableado hacia y
contactos de la puerta de piso entre los contactos de la
en el circuito de seguridad puerta de piso.

Field Feedback
1 Shaft Comprobar los contactos de las puertas de
embarque KTS
0149 Safety T5

Summary
Usado para la monitorización de los contactos KTC de la puerta de

Description cabina. El circuito de seguridad se abre antes de la quinta toma de
derivación (ISKT5), pero después de la cuarta (ISKT4). El mensaje
queda registrado si:
a) El circuito de seguridad se abre durante un viaje debido a la
apertura inesperada de un contacto (delantero o trasero) de la puerta
de cabina.
b) El circuito de seguridad no se cierra como estaba previsto después
de que la puerta se haya cerrado.
Comentarios: Consultar también el esquema eléctrico para conocer los

Si la apertura anticipada de puertas no funciona correctamente
durante la aproximación al piso, entonces puede aparecer este evento
en lugar del error 'SafetyRTS'. Si persiste este error, se deberá
cambiar el parámetro de tracción 'DOOR_CONTACT-DELAY' de 50
(0,5 s) a 70 ó 100. Este es el tiempo que espera la lógica durante el
arranque, desde la primera vez que se recibe la señal SKD 5 (lado de
seguridad) hasta el momento en que se deshabilita el puenteo de
puerta. Durante este tiempo, los contactos de puerta pueden rebotar.
No aumentar demasiado el valor de este parámetro, ya que aumentará
también el temporizador de la preparación del viaje. Se ha de tener
mucho cuidado para mejorar el ajuste del movimiento de la puerta.

Extra Info
Ninguna.
Source ID

Causes and
1 Contactos de puerta KTC Comprobar la conmutación de
Actions
los contactos de la puerta de
cabina
2 Cableado defectuoso de los Comprobar el cableado de los
contactos de puerta de cabina contactos de la puerta de
en el circuito de seguridad cabina
3 Circuito de puenteo de puertas Comprobar el circuito de
puenteo de puertas

Field Feedback
1 Car Door Comprobar los contactos de la puerta de cabina
KTC, puente de contacto de la puerta.
0150 Max Eevent Id TravelControl
This section describes the Variodyn E error Max Eevent Id

Summary TravelControl.
Description
Extra Info
Source ID
0151 LearnTrip
This section describes the Variodyn E error LearnTrip.

Summary
A learn trip has been started

Description Comment: For information only
None.
Extra Info
None.
Source ID
0152 CorrTrip
This section describes the Variodyn E error CorrTrip.

Summary
A correction trip has been started

None.
Extra Info
None.
Source ID
0153 SynchTrip
This section describes the Variodyn E error SynchTrip.

Summary
A synchronisation trip has been started

None.
Extra Info
None.
Source ID
0154 KS_MagnetPos
This section describes the Variodyn E error KS_MagnetPos.

Summary
Wrong position of KS magnet in shaft detected during learn trip

Description
Affected floor
Extra Info
None.
Source ID

Causes and message
Actions
1 Check KS magnets
0155 KSE_MagnetPos
This section describes the Variodyn E error KSE_MagnetPos.

Summary
Wrong position of KSE magnet in shaft detected during learn trip

Description
Affected floor;
Extra Info 0x01: Lower KSE magnet;
0x02: Upper KSE magnet;
0x03: Uppermost KSE magnet;
None.
Source ID

Causes and message
Actions
1 Check and adjust KSE
magnets
0156 LearnMesProbl
This section describes the Variodyn E error LearnMesProbl.

Summary
Contradictory results of learn trip

Description
0x00: Number of floors out of range;

Extra Info 0x01: Affected floor
None.
Source ID
0157 DeltaS_2BP
This section describes the Variodyn E error DeltaS_2BP.

Summary
Distance error KS_Interrupt - 2nd brake point

Description
s2 [Inc]
Extra Info
None.
Source ID

Causes and
1 Possible error causes Actions to be taken
Actions
2 Inaccurate parameter setting Check frequency converter
(frequency converter) drive parameter
0158 SF_Fault
This section describes the Variodyn E error SF_Fault.

Summary
SF relay error
Description
None.
Extra Info
None.
Source ID

Causes and
1 Open safety circuit Check safety circuit
Actions
2 Check auxiliary contacter of SF
and SF1
0159 NoBpReaction
This section describes the Variodyn E error NoBpReaction.

Summary
frequency converter does not react on brake point

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check wiring PGO-frequency
Actions
converter
2 Check frequency converter
ER113 module
0160 SK ErrorStart
This section describes the Variodyn E error SK ErrorStart.

Summary
Safety chain prevents the elevator from starting a trip

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check safety chain
0161 CarNotAtLevel
This section describes the Variodyn E error CarNotAtLevel.

Summary
Bad stopping precision on target floor

Description
None.
Extra Info
None.
Source ID

Causes and
1 Inaccurate setting of frequency Check frequency converter
Actions
converter parameters parameters
0162 CarOutOfFloor
This section describes the Variodyn E error CarOutOfFloor.

Summary
Car has not reached target floor

Description
Position [Inc]
Extra Info
None.
Source ID

Causes and
1 Trip interruption caused by Check wiring PGO-frequency
Actions
frequency converter converter
0163 TargetFailure
This section describes the Variodyn E error TargetFailure.

Summary
Target out of permitted range

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Position lost Perform a learn trip
2 Wrong direction Perform a learn trip
0164 FC_ShortBrake
This section describes the Variodyn E error FC_ShortBrake.

Summary
VF20/30 stopped too early after 1st brake point

Description
Distance to target floor [mm]

Extra Info
None.
Source ID

Causes and
1 Inaccurate parameter setting Check (and adjust if
Actions
(frequency converter) necessary) frequency
converter parameter
0165 FC_StopSpeed
This section describes the Variodyn E error FC_StopSpeed.

Summary
VF20/30 over-speed at activation of mechanical brake

Description
Speed at activation of brake [mm/s]. Informational message

Extra Info
None.
Source ID

Causes and
1 Malfunction of frequency Check wiring to frequency
Actions
converter converter
2
0166 SW_BlockPerm
This section describes the Variodyn E error SW_BlockPerm.

Summary
Fatal software error occured / Exceeded range for parameter value /

Description Illegal data changement during runtime
None.
Extra Info
None.
Source ID

Causes and
1 Solve the problem and reset
Actions
the system
2 RAM data destroyed Double-reset PGO
3 ROM data destroyed Call EBI for software
replacement
4 Double-reset PGO
5
0167 LastBlockTime
This section describes the Variodyn E error LastBlockTime.

Summary
Provides block time after a long blocking period

Description
Time [min]. Informational message

Extra Info
None.
Source ID

Causes and message
Actions
1
0168 ShaftChecksum
This section describes the Variodyn E error ShaftChecksum.

Summary
Destroyed shaft image data

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Corrupted data Perform a learn trip
2
0169 Supply24V
This section describes the Variodyn E error Supply24V.

Summary
24V supply activated

Description
Informational message
Extra Info
None.
Source ID

Causes and message
Actions
1
0170 FloorPrec
This section describes the Variodyn E error FloorPrec.

Summary
ERROR: Inaccurate stopping on 8 of 10 trips; WARNING: Inaccurate

Description stopping on 4 of 10 trips; NO_LOG: Accurate stopping of the last 10
trips; Note: Message used for Servitel
None.
Extra Info
None.
Source ID

Causes and
1 Elevator system improperly Improve elevator adjustment
Actions
adjusted
2
0171 InvDrivePCT
This section describes the Variodyn E error InvDrivePCT.

Summary
Invalid parameter in VF20/30 parameter group

Description
0x05: P_VF20_30_LOAD_TYPE
Extra Info 0x06: P_VF20_30_DRIVE_RES_1
0x07: P_VF20_30_DRIVE_RES_2
0x20: P_VF20_30_FN
0x21: P_VF20_30_VKN
0x22: P_VF20_30_FC_MAX_R
0x23: P_VF20_30_MM_IMP
0x24: P_VF20_30_FT_RU1
0x25: P_VF20_30_DELTA_U
0x26: P_VF20_30_frequency converter_RES_0
0x27: P_VF20_30_T_DIFF
0x28: P_VF20_30_T_AUF
0x29: P_VF20_30_U_END
0x2A: P_VF20_30_S_KBR_2
0x2B: P_VF20_30_ frequency converter_RES_
0x2C: P_VF20_3 frequency converter_RES_0_
0x80: P_VF20_30_SELECTOR_TRANS_TABLE
0xFE: condition U_END >= DELTA_U not fulfilled.
0xAA (GENERAL_PARAM): Stored general drive parameter (Tacho
Factor, KSE-Distance, KSERE-Distance, GAP-Length, Load Type) out
of range.
0xBB (frequency converter_PARAM): Stored converter-specific drive
parameter (FN, VKN, MM_IMP, S_KBR_2, FT_RU1, DELTA_U,
FC_MAX_R, T_DIFF, T_AUF, U_END) out of range
None.
Source ID

Causes and
1 Parameter value wrongly set in Adjust appropriate parameter
Actions
PCT
2 PCT structure invalid (one or Replace PCT (Perform a PCT-
more parameters missing) download with CADI or change
PEROM)
0172 InvDriveParam
This section describes the Variodyn E error InvDriveParam.

Summary
Parameter values stored in the frequency converter (BARMAG ER113)

Description do not correspond with their equivalents in the control software
(inconsistence)
frequency converter parameter ID: 0x01: FN;

Extra Info 0x02: VKN;
0x03: MM_IMP;
0x04: S_KBR_2;
0x05: FT_RU1;
0x06: DELTA_U;
0x07: FC_MAX_R;
0x08: T_DIFF;
0x09: T_AUF;
0x0A: U_END;
None.
Source ID

Causes and
1 Communication PGO Check RS232 connection PGO
Actions
frequency converter not frequency converter
successful/impossible
2 Communication PGO Perform double-reset on PGO
frequency converter had been and reset on frequency
interrupted converter, wait approx. 5
minutes (!)
0200 Door Error Base
This section describes the Door Control error Door Error Base.
Summary
Description
Extra Info
Source ID
0201 ConfigErr
This section describes the Door Control error ConfigErr.

Summary
Configuration data error. The Door Control did not receive all the
Description necessary configuration data or the data contained invalid values. The
door control can not operate except if the extra info value is 1,7 or 8.
01: No response to PCT version number request.

Extra Info 02: No parameters or incomplete parameter list received from
controller.
03: No I/O definition or incomplete I/O definition received from
controller.
04: Received parameters contain invalid values.
05: Received I/O definitions contain invalid values.
06: The local PCT checksum is not consistent with data checksum.
07: No error, internal message that the car print has requested a new
configuration.
08: No error, internal message that the car interface board has
received a new configuration.
None.
Source ID

Causes and
1 Wrong position of ID switch on Check switch setting and
Actions
door-/car-interface board verify.
2 Configuration data not TX4: Check lift bus connection
received or data corrupted to controller.
3 Check if configuration data is
loaded on the controller.
0202 DoorOperErr
This section describes the Door Control error DoorOperErr.

Summary
Door operator error. Error detected on the door drive behaviour by

Description door control.
The door can not reach its end position. After several attempts the
door will be blocked.
Hex digits STUVWXYZ

Extra Info
Meaning of digit S: side (introduced with SW v10.08.00 and newer)
0: n/a
1; Side 1 (front door/upper deck door)
2: Side 20 (rear door/lower deck door)
3: Side 30 (not used)
4: Side 40 (not used)
Meaning of digits YZ:

01: KET-O and KET-S are active at the same time (illegal status)
02: KET-S does not switch when expected
03: KET-O does not switch when expected
04. Output VST-S is faulty or has short circuit.
05: Output VST-O is faulty or has short circuit.
06: The door drive does not move the door, although VST-O / VST-S
is active.
07: For manually-operated or semi-automatic doors the RTS contact
feedback (shaft door closed) is not active after a close command has
been given. Either the shaft door is open or the shaft door contact
(RTS) is faulty.
08: Door motor moves the door in the wrong direction
For extra info 02 and 03 the maximum time is according the value of
the PCT parameter 'Max Door Travel Time' (PCT:
P_KAB_MAX_DOOR_TRAVEL_TIME). If this parameter does not exist
or the value of the parameter is 0, then a default value of 15 seconds is
taken for the monitoring of the door travel time.
None.
Source ID

Causes and
1 Extra info 1,2,3 Check the door contacts KET-
Actions
O, KET-S and the related
wiring
2 Check if the door can reach
the end position mechanically
3 Check for dirty door guides.
4 Extra Info 3: Mechanical Check if the door unlocking
unlocking does not function; works
the door can not open
5 Extra info 4,5 Check the connections to the
door drive
6 Replace the interface board
7 Extra info 6 Check the door drive board
and connections (fuse and
power supply).
8 Check the physical door parts
(V-belt)
9 Extra info 7 For manually-operated or
semi-automatic doors check if
the landing door is closed.
10 Check the landing door
contacts and wiring.
11 Extra info 8 Check if electrical phase
sequence is correct.
12 Check if VST-O/VST-S or
wiring is mixed up
0203 ThermoDoorMot
This section describes the Door Control error ThermoDoorMot.

Summary
For door drives with inverter (e.g. IDD, SEMATIC, QKS9VF, DODSF9,
Description VD35) the message indicates that the thermal protection device of the
door motor detects excessive temperature or if there is a general
problem on the door inverter. The error is logged when the door
inverter is blocked due to a severe error detected by the inverter
software. In this situation the door is no longer able to operate. The
door may not be moved manually. Check the error log of the door
inverter for more information. Possibly the door drive will not recover
by simple power cycle (JH off/on)
For doors without inverter such as QKS9:

The thermal protection device of the door motor indicates excessive
temperature. The thermal contact KTHMT of the door motor is active.
After detection of the overtemperature the control attempts to open the
door once so passengers are not trapped. The door control allows that
the current door movement is finished and the magnetic brake will be
released; all outputs from the door drive are then switched off and the
door control blocks the door. The door can still be moved manually.
Hex digits STUVWXYZ

Extra Info
Meaning of digit S: side (Defined with SW v10.08.00 and newer)
0: n/a
1; Side 1 (Front/upper deck)
2: Side 20 (Rear/lower deck)
3: Side 30
4: Side 40
Meaning of digits TUVWXYZ:

None.(R&D use)
None.
Source ID

Causes and
1 Problem on door drive / Check the door inverter (error
Actions
inverter log)
2 Jammed door / excessive Check the mechanics of the
torque door drive and the door itself
for smooth operation (dirt,
wear etc.).
3 Input signal KTHMT faulty Check input for KTHMT on
interface board; replace if
necessary.
0204 DoorRevDevErr
This section describes the Door Control error DoorRevDevErr.

Summary
Door reversing device error. The error is generated by the door control
Description when:
a) the same reversing device was active permanently twice during 5
complete opening and closing cycles.
b) a reversing device is permanently active so that even after the final
timer has timed out the door can not close.
Hex digits STUVWXYZ

Extra Info
0: n/a
3: Side 30
4: Side 40

01: DT-O / KTL is permanently active.
02: RPHT is permanently active (Lightcurtain).
03: Radar is permanently active (REP).
04. Reserve Reserving Device is permanently active.
05: Closing force limiter KSKB is permanently active.
06: DT-S is permanently active.
07: KTHMT is permanently active.
08: RTS (safety circuit tap) is permanently inactive (only for manual
shaft door).
None.
Source ID
Causes and
1 Damaged or badly adjusted Check the function of the
Actions
reversing device reversing device indicated by
the extra info value.
2 Bad connection or faulty input Check the connection from the
on the interface board on car interface board to the reversing
(e.g. device. Replace interface
PIOC/ICE/TIC/LONIBV/LONIC board.
etc.). See schematics for
details.
0205 DoorContrErr
This section describes the Door Control error DoorContrErr.

Summary
Door control error. The status of one of the 24VDC car interface board
Description outputs is not as expected or the interface board power level has
dropped below a certain point.
01: Power supply level of the car print too low.

Extra Info 02: Output VRVRT (slow door speed)
03: Output VRET (door inspection)
04: Output RVEC (car ventilator)
05: Output RLC (car light)
06: Output VRMGH (holding-brake)
07: Output VKETSO (light-barrier)
08: Output VENABLE (door bridging device)
09: Output VKSPEPO (lobby radar)
None.
Source ID

Causes and
1 Defective output or short circuit Check the wiring of the output.
Actions
2 Replace interface board on
car.
0206 DoorBoltErr
This section describes the Door Control error DoorBoltErr.

Summary
Door bolt error. The door locking contact (KV/RKV) does not close
Description after a door locking command or does not open when the door is
unlocked (for manually operated and semi-automatic doors).
None.
Extra Info
None.
Source ID

Causes and
1 Locking contact not functioning Check the locking mechanism
Actions
and the locking contact.
2 Check the wiring of the locking
device (motor / magnet).
0207 CloseSeqErr
This section describes the Door Control error CloseSeqErr.

Summary
Door close sequence error. The error is generated by the door control
Description when:
a) a reversing device is activated during x attempts to close the door

repeatedly on the same floor and if this occured twice within five trips.
b) the same reversing device becomes active too often (8 times =

warning, 12 times = error) during door closing.
Hex digits STUVWXYZ

Extra Info
0: n/a
3: Side 30
4: Side 40

01: DT-O is triggered repeatedly.
02: RPHT is triggered repeatedly.
03: Radar is triggered repeatedly.
04: Reserve reserving device is permanently active.
05: Closing force limiter KSKB is triggered repeatedly.
None.
Source ID
Causes and
1 Damaged or badly adjusted Check the reversing devices.
Actions
reversing device
2 Bad connection or faulty input Check the connection from the
on interface board on car (e.g. interface board to the reversing
PIOC/ICE/TIC/LONIBV/LONIC device. Replace interface
etc.) board.
0208 DoorDevErr
This section describes the Door Control error DoorDevErr.

Summary
Door device error. Door control malfunction. See extra info for details.
Description
Hex digits STUVWXYZ

Extra Info
0: n/a
3: Side 30
4: Side 40
Meaning of digits YZ: Identifies the causing component:

01: Input from light barrier (PROGARD L etc.).
02: I/O-Bus error.
03: JHCT pressed.
04: Door motor power failed.
05: Door node communication failed or power fail for door node.
None.
Source ID

Causes and
1 Faulty device Examine the device and
Actions
replace it if necessary.
2 Extra Info = 2 Check I/O-bus cable.
3 Check I/O-bus drivers.
4 Extra Info = 3 Check JHCT switch and the
related wiring.
5 Extra Info = 4 Check the power supply on the
door driver pcb (fuse).
6 Extra Info = 5 Check LON bus and 24V
power supply to door interface
board.
7 Check LON node and its rotary
switch settings.
8 Check LON bus to other
nodes. (remove for test)
9 Check pcb EBLON (TX/TX2) or
ASIXx (MX).
10 Check for EMC disturbances.
0209 DoorContact
This section describes the Door Control error DoorContact.

Summary
For manually operated and semi-automatic doors: manual landing

Description door doesn't close after a close or lock command from the controller.
Hex digits STUVWXYZ

Extra Info
0: n/a
3: Side 30
4: Side 40

None.(R&D use)
None.
Source ID

Causes and
1 Faulty RTS device Examine the device and if
Actions
necessary exchange it.
2 Check output VSTS
3 Check doorbolt contact and
wiring to I/O board
4 Landing door has been left None (close the door)
opened
0210 Lift Guardian
This section describes the Door Control error Lift Guardian.

Summary
Door control detects faulty DT-O button or car light not on during a trip.
Description
Hex digits STUVWXYZ

Extra Info
01 = the car light is off or flickers
- Warning after 3 trips with car light flickering
- Error after 3 trips with the car light permanently off
02 = defective DT-O
- Warning after 200 consecutive door cycles without DT-O being
pressed
- Error after 400 consecutive door cycles without DT-O being pressed
None.
Source ID

Causes and
1 Car light is defective Check the lamp, light network,
Actions
wiring, relays and car control
outputs.
2 Sensor for car light defective or
covered.
3 DT-O input signal is not Check the button, the wiring,
working IO bus cable and the IO
interface board. ( message is
also logged when elevator is
running from call simulator )
0211 COM_Busreconf
This section describes the Door Control error COM_Busreconf.

Summary

same one hour period. Telegrams can be lost. Reliable operation is no
longer guaranteed.
Only relevant to Miconic VX and TX4 (RC board)

None.
Source ID

Causes and
1 Bus is faulty Check lift-, groupbus; all links
Actions
and terminators functional.
connected with the bus.
3 Too many messages are Trace the telegram traffic in
generated within a certain order to determine the source
period of time of the telegram flood and test
4 Another subsystem is not The problem might be caused
5 Wrong addressing on the bus Check that the number of
addresses.
6 Other possibilities Reset the Lift Control board
and check if the
reconfigurations still appear.
7
occurs, please contact the
supplier hotline or the VX-
Center.
0212 Open Sequence KOKB
This section describes the Door Control error Open Sequence KOKB.
Summary
Door can not open due to repeated activation of KOKB (Door opening
Description force limiter).
Detection condition: The reversing device KOKB is active during 10

consecutive attempts to open the door on the same floor.
Hex digits STUVWXYZ

Extra Info
0: n/a
3: Side 30
4: Side 40

None.(R&D use)
None.
Source ID

Causes and
1 Mechanical obstruction on Check operation of door
Actions
door (opening). Door panels can
move without excessive
friction.
0213 DT-O Continous Activation
This section describes the Door Control error DT-O Continous

Summary Activation.
Description when:
a) DT-O was active permanently twice during 5 complete opening and
closing cycles.
b) DT-O is permanently active so that even after the final timer has
timed out the door can not close.
Extra Info
None.
Source ID
0214 RPHT Continous Activation
This section describes the Door Control error RPHT Continous

Summary Activation.
Description when:
a) RPHT was active permanently twice during 5 complete opening and
closing cycles.
b) RPHT is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0215 REP Continous Activation
This section describes the Door Control error REP Continous

Summary Activation.
Description when:
a) REP was active permanently twice during 5 complete opening and
closing cycles.
b) REP is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0216 KTL Continous Activation
This section describes the Door Control error KTL Continous

Summary Activation.
Description when:
a) KTL was active permanently twice during 5 complete opening and
closing cycles.
b) KTL is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0217 KSKB Continous Activation
This section describes the Door Control error KSKB Continous

Summary Activation.
Description when:
a) KSKB was active permanently twice during 5 complete opening and
closing cycles.
b) KSKB is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0218 DT-S Continous Activation
This section describes the Door Control error DT-S Continous

Summary Activation.
Description when:
a) DT-S was active permanently twice during 5 complete opening and
closing cycles.
b) DT-S is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0219 RTS Continous Activation
This section describes the Door Control error RTS Continous

Summary Activation.
Description when:
a) RTS was active permanently twice during 5 complete opening and
closing cycles.
b) RTS is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0220 KOKB Continous Activation
This section describes the Door Control error KOKB Continous

Summary Activation.
Description when:
a) KOKB was active permanently twice during 5 complete opening and
closing cycles.
b) KOKB is permanently active so that even after the final timer has
Extra Info
None.
Source ID
0221 Door inverter failure
This section describes the Door Control error Door inverter failure.
Summary
For door drives with inverter (e.g. IDD, SEMATIC, QKS9VF, DODSF9,
Description VD35) the message indicates that the door inverter is blocked due to a
severe error detected by the inverter software. In this situation the door
is no longer able to operate. The door may not be moved manually.
Check the error log of the door inverter for more information. Possibly
the door drive will not recover by simple power cycle (JH off/on)
Extra Info
None.
Source ID
0240 SW-Warning
This section describes the Door Control error SW-Warning.

Summary
The software detected an abnormal situation which is not considered to

Description be severe for the operation of the elevator.
Identifies the cause of the warning:

Extra Info
01: Unknown VCOM telegram info (Tel_id, tel_grp_id, attr1, attr2)
received
02: Invalid VCOM telegram data received
03: VCOM queue full
04: VCOM communication queue full
05: VCOM local table full
06: VCOM updates full
07: VCOM bus stressed
08: VCOM provide error
09: VCOM request error
None.
Source ID

Causes and
1 Various Contact the R&D department
Actions
in Ebikon if no details about
the cause of the message is
provided in the help here.
logged in the error/event log.
Also include information about
the occurrence rate if possible.
These are clues for the
2
0251 Door Command Timeout
This section describes the Door Control error Door Command Timeout.
Summary
Error is logged when the door does not respond to the commad sent
Description by the GC.
Meaning of 8 digit hex number 0xAABBCCDD:

Extra Info
AA = Type of command to Door
01:Door_HW_ID_Rqst,
02:Door_SW_ID_Rqst
03:Door_State_Rqst,
04:Door_Cmd_Motion,
05:Door_Saf_Dev_Enable_Rqst,
06:Door_Param_Read_Rqst,
07:Door_Write_Rqst,
08:Door_Test_Rqst,
09:Door_Insp_Enable_Cmd,
10:Door_Error_Reset_Cmd,
BB: Data part of the above sent command to the Door. This has
various combination for each of them and difficult to list here.
CC: Expected response from the Door

0:Door_Unknown_Change,
1:Door_Availabilty,
2:Door_Motion,
3:Door_Error,
4:Door_Over_Temp,
5:Saf_Dev_Enable,
6:HW_ID,
7:SW_ID,
8:Param_Read_Resp,
9:Param_Write_Resp
DD: Data Received from the door for the above type of response. Each
response has its own set of data and is difficult to list here.
Not used
Source ID
0252 Door Unavailable
This section describes the Door Control error Door Unavailable.

Summary
Error logged when the door responds with a message saying that it is
Description not available (UNV) for any of the sent commands.

Extra Info
01:Door_HW_ID_Rqst,
02:Door_SW_ID_Rqst
03:Door_State_Rqst,
04:Door_Cmd_Motion,
07:Door_Write_Rqst,
08:Door_Test_Rqst,

1:Door_Availabilty,
2:Door_Motion,
3:Door_Error,
4:Door_Over_Temp,
5:Saf_Dev_Enable,
6:HW_ID,
7:SW_ID,
8:Param_Read_Resp,
9:Param_Write_Resp
Not used
Source ID
0253 Door Wrong Response
This section describes the Door Control error Door Wrong Response.
Summary
Error logged when the door does not respond as expected (based on
Description the command sent before).

Extra Info
01:Door_HW_ID_Rqst,
02:Door_SW_ID_Rqst
03:Door_State_Rqst,
04:Door_Cmd_Motion,
07:Door_Write_Rqst,
08:Door_Test_Rqst,

1:Door_Availabilty,
2:Door_Motion,
3:Door_Error,
4:Door_Over_Temp,
5:Saf_Dev_Enable,
6:HW_ID,
7:SW_ID,
8:Param_Read_Resp,
9:Param_Write_Resp
Not used
Source ID
0254 Floor Zone Not Available
This section describes the Door Control error Floor Zone Not
Summary Available.
Floor zone information not available in real-time

Description
R&D only
Extra Info
Source ID

Causes and
1 Report to supplier hotline or
Actions
R&D
0255 Floor Weight Not Available
This section describes the Door Control error Floor Weight Not
Summary Available.
Floor weight information not available when opening, as a

Description consequence the door is opened at slow speed
R&D only
Extra Info
Source ID

Causes and
1 report to R&D
Actions
0256 Out Of Floor Zone
This section describes the Door Control error Out Of Floor Zone.
Summary
Car out of floor zone.

Description
No longer used.
none
Extra Info
Source ID

Causes and message
Actions
1 Report to R&D
This section describes the Door Control error Reserve_Error_260.

Summary
Description
R&D only
Extra Info
Not used
Source ID
0261 Door Postion Recovery Failure
This section describes the Door Control error Door Postion Recovery
Summary Failure.
The door could not be taken to the requested position

Description
R&D only
Extra Info
Source ID

Causes and
1 Report to R&D
Actions
0271 Door Command Failure
This section describes the Door Control error Door Command Failure.
Summary
This error is logged when the door drive does not respond to a
Description commad sent by the GC with an expected answer after some retries
and within a given deadline.
It may signalize a slow door reaction due to mechanical reasons.
This error applies to following commands:

- OPEN
- CLOSE
- LOCK
- SAFETY DEVICE MASK SET
Following retries and timeouts apply:

- OPEN: 3 retries, timeout between retries 1000ms if locked or closing,
50ms otherwise
- CLOSE: 3 retries, timeout between retries 120ms
- LOCK: 3 retries, timeout between retries 1000ms if opening, 120ms if
open
- SAFETY DEVICE MASK SET: 3 retries, timeout between retries
100ms
ExtraInfo is compressed and needs a bitwise interpretation (b0..b31):

Extra Info - b31..b30: side
- b29..b26: number of messages received during the transaction
- b25..b24: heavy/low speed command
- b23..b20: command code (4=motion, 5= safety dev set)
- b19..b16: if motion -> command code (close=1,lock=2,open=3)
- b15..b8: received motion state (see enum below)
- b7..b0: reason of motion state change -> b7=KTFP,
b6=Otherwise,b5=CMD,
b4=KOKB,b3=REP,b2=KTL,b1=RPHT,b0=KSKB
b15..b8 enum:
FE_DOOR_STATE_UNKNOWN = 0,
FE_DOOR_STATE_CLOSED,
FE_DOOR_STATE_CLOSING,
FE_DOOR_STATE_OPENED,
FE_DOOR_STATE_OPENING,
FE_DOOR_STATE_STOPPED,
FE_DOOR_STATE_LOCKED,
FE_DOOR_STATE_RESERVED,
FE_DOOR_STATE_MANUAL,
FE_DOOR_STATE_STANDBY_CLOSED,
FE_DOOR_STATE_REF = 0x80, /*Values for the referencing mode*/
FE_DOOR_STATE_REF_CLOSED = 0x81,
FE_DOOR_STATE_REF_CLOSING = 0x82,
FE_DOOR_STATE_REF_OPENED = 0x83,
FE_DOOR_STATE_REF_OPENING = 0x84,
FE_DOOR_STATE_REF_STOPPED = 0x85,
FE_DOOR_STATE_REF_LOCKED = 0x86,
FE_DOOR_STATE_REF_RESERVED = 0x87,
FE_DOOR_STATE_REF_MANUAL = 0x88
Not used
Source ID

Causes and
1 slow door movement due to check door locking mechanism
Actions
deteriorated parts rep.
obstacles
0300 CTR_PAR_ACCESS
This section describes the Varidor70 Door Drive error

Summary CTR_PAR_ACCESS.
[V70 Door Controller SW]

Description Door Controller could not access a Parameter.
Error response: Stop all door motions immediatly, and stop all further
motions too.
Easy Setup: BarGraph-RED-LED-7 [ON]
The most common parameters which might cause this error are
Extra Info a. Mass
b. Control Amplification
c. Drive Delay
This error is generated from the PID Control SW Module

Source ID (PID Control = Proportional Integral Differential Control)

Causes and
1 1. A parameter is not defined 1. Check the validity of
Actions
or incorrect parameter definitions
described
2. Try Downloading a fresh
PCT with correct values
2 2. A Parameter access failed 1. Check the validity of
parameter definitions
described
2. Try Downloading a fresh
PCT with correct values
3. Try Resetting Door
Controller
3 3. Flash is gone bad 1. If the error
"PAR_NOVRAM_MISSING"
occurs too, change the Door
Controller PCB and boot the
door again
0301 CTR_CALC
This section describes the Varidor70 Door Drive error CTR_CALC.

Summary

Description An attempt was made to set an unknown Control Mode
This is an internal SW Error.
Error response: Stop the door immediately, no more door motions

allowed.
Easy Setup: Bargraph-RED-LED-7 [ON]
Presently there are 3 control modes

Extra Info a. Position Control
b. Speed Control
c. Force Control
This error is generated from the PID Control SW Module

Source ID (PID Control = Proportional Integral Differential Control)

Causes and
1 1. An Attempt to set an 2. Reset the door controller
Actions
unknown mode was done
0302 TRC_PAR_ACCESS

Summary TRC_PAR_ACCESS.

Description Trip Curve Converter/Generator parameter access failed.
Error response: Stop the door immediately
The most common parameters which might cause this errors are
Extra Info a. Safety Standard
b. Energy Limits
c. Emergency Parameters
d. Mass
e. Curve Type
f. Jerk,Acceleration,Speed Limits both Open & Close Directions
g. Door Type
This error is generated from Trip Curve Generator

Source ID

Causes and
1 1. Parameter not defined or 1. Check validity of parameter
Actions
incorrect definitions described
2 2. Parameter access failed 2. Try resetting the door
controller
3 3. Flash is gone bad 3. If the error
"PAR_NOVRAM_MISSING"
occurs too, then change the
Door Controller PCB and boot
the door again.
0303 TRC_POS_ERR

Summary TRC_POS_ERR.

Description Reference position information is not or no more valid.
Error response: Wait till the door opens and then stop all further door
motions
This occurs when the current position counter value is not within the
Extra Info limits of closed and open positions. On both directions a 2% tolerance
is allowed.
Two main HW components which might lead to this error are
a. Position Counter
b. Position Sensor Unit
This error is generated from the Trip Curve Generator

Source ID

Causes and
1 1. Referencing Not done 1. Power off and on the door
Actions
properly and do a referencing trip
2 2. Resolver is loosely cabled or 1. Try reconnecting the cables
cable is damaged 2. Try a new cable or
connector
3 3. Position Sensor Unit is 1. Try reconnecting the cables
loosely cabled or cable is 2. Try a new cable or
damaged connector
4 4. Cables are loosely fitted 1. Try reconnecting the cables
5 5. Resolver is faulty 1. Replace with new Door
Controller/Drive
6 6. Position Sensor is faulty 1. Replace with new Position
Sensor Unit
7 7. Door Controller PCB is 1. Replace with new Door
faulty Controller PCB
0304 TRC_CALC
This section describes the Varidor70 Door Drive error TRC_CALC.

Summary

Description Error in Trip Curve Generator/Converter calculation
Error response: Stop the Door Motions Immediatly, and dont do any
more motion
This error will occur when there is a problem with the calculation of trip
Extra Info curves. Since, its would be dangerous to do any motions without a
proper trip curve, the door stops, unless it is reset.

Source ID

Causes and
1 Trip calculation fails Reboot the door
Actions
0305 OS_CYCLE_OVERRUN

Summary OS_CYCLE_OVERRUN.

Description CPU load 100%, not all tasks can be processed
This is not an Error, but a Warning
Error response: None
None
Extra Info
None.
Source ID

Causes and
1 CPU load exceeds 100% Inform EBI about the Problem
Actions
0306 PAR_NOVRAM_MISSING

Summary PAR_NOVRAM_MISSING.

Description Parameter value not valid or the Flash is gone bad.
Error response: Wait untill the door is open, and then stop all door
motions
This error mostly occurs at startup time, when the parameters are
Extra Info initialized
This error is generated from the Param

Source ID

Causes and
1 1. No access to Flash Memory 1. Reset the Door Controller
Actions
2. Change the Door Controller
PCB and boot the door again.
2 2. Flash Memory is gone bad 1. Reset the Door Controller
PCB and boot the door again.
0307 HW_PAR_ACCESS

Summary HW_PAR_ACCESS.

Description Parameter Access failed when the controller was trying to do a motion.
The error could also be raised if the read parameter values are not
correct, or when a certain changed parameter is set back to the
parameters.
Error response: Stop all door motions, and dont do any more door
motions
This error generally occurs when the force is being applied in a motion.
Extra Info The parameters because of which the error could rise are
a. d0
b. DriveNewtonmeterPerVolt
c. iGear
d. DrivePoleLength
e. DriveEncoderIncr
f. ZeroSpeed
g. StalledSpeed
h. OscillatingSpeed
This error is generated from the HWAct

Source ID

Causes and
1 1. Invalid Parameter Values 1. Check the valdity of the
Actions
parameters described in the
error description
2 2. Cannot Access Parameters 1. Reset the Door Controller
2. Replace the Door Controller
PCB
3 3. Flash is gone bad 1. Reset the Door Controller
PCB
0308 HW_POSITION
This section describes the Varidor70 Door Drive error HW_POSITION.

Summary

Description Strange referencing state value.
Error response: Stop all door motions, and dont do any more motions
Easy Setup: Bargraph-RED_LED-8 [ON]
This error occurs if the current position counter value is not within the
Extra Info open and closed positions including tolerance. This check is made with
reference to the Position Sensor Unit. A misalignment at runtime in the
position sensor can also cause this error
The Error is generated from the Control Task

Source ID

Causes and
1 1. Current Position Counter 1. Check the drive motor
Actions
value is not within the allowed resolver cable connection to
limits of open and closed the frequency converter
positions 2. Reset the Door Controller
2 1. Check the Position Sensor 1. Do proper alignment of the
Unit if it is loose or misaligned Position Sensor Unit
2. Check the cables of the
Positon Sensor Unit
0309 HW_POSREF
This section describes the Varidor70 Door Drive error HW_POSREF.

Summary

Description Error in positon referencing
This error is raised when the position sensor unit goes bad or is
removed or someway disconnected.
Error response: Stop all door motions and stop all further door
motions, till the error stops, once the Sensor Unit is reconnected the
door can resume the motions
Once the Position Sensor Unit is re-connected the door resumes the
Extra Info usual operation. This error is generated at the startup or whenever a
parameter update takes place
This error is generated from Sensor Unit

Source ID

Causes and
1 1. Position Sensor Unit cable is 1. Check the cable for damage.
Actions
disconnected or loose 2. Disconnect and Reconnect
the cable
2 2. Position Sensor Unit is gone 1. Replace Position Sensor
bad Unit
0310 HW_DRV_SERIOUS

Summary HW_DRV_SERIOUS.

Description Drive error from frequency converter.
Error response: Stop door motions now, and stop all further door
motions
The error is a signal from the drive that there is some serious problem
Extra Info with the Drive Motor or the Drive Frequency Convertor(Inverter)
This error is generated from the Drive

Source ID

Causes and
1 1. Motor or frequency 1. Check the door drive
Actions
converter error system, motor and mechancial
parts
2. Reset the Door Controller
2 2. Overheating/overloading of 1. Refer to Cause/Action list of
the door drive DRIVE_OVER_TEMP
0311 DRIVE _OVER_TEMP
This section describes the Varidor70 Door Drive error DRIVE

Summary _OVER_TEMP.

Description Drive motor over temperature
This is not an error, but a warning.
Error response: This is a warning, The Controller performs load

reduction, i.e., the door mode is reduced by 1, and if the error
continues to stay, the door is further reduced in steps till nudging.
Below nudging speed, the door cant move.
This error could be generated because of continous door motions for a

Extra Info prolonged time, because of which the door motor could get heated up,
above the preset tolerance limits. Another source of this error could be
permanent collision with an obstacle in an unattended system.
This error is generated from the Drive

Source ID

Causes and
1 1. Drive overload 1. If the overlaoding is not a
Actions
temporary problem, then set
the drive force less
2. If the over load problem
persists my be the drive has
gone bad.
2 2. Cables 1. Touch the door drive to
sense the temperature. If the
temperature is no too high and
this error is present all the
time, then my be the cables
are defective or a loose
connection can be predicted
0312 HW_FLASH_READ

Summary HW_FLASH_READ.

Description It is not possible to read data from the NOVRAM memory.
Error response: Wait untill the door is open, and then stop all further
motions
This error occurs when the params are getting restored at power up.
Extra Info

Source ID

Causes and
Actions
PCB
0313 HW_FLASH_WRITE

Summary HW_FLASH_WRITE.

Description It was not possible to write onto the Flash.
Error response: Wait till the door is open and the stop all further door
motions
This error occurs at the start up when the Flash is being checked for
Extra Info consistency. This error also occurs in the Param Backup task, when it
encounters Flash writing problems.

Source ID

Causes and
Actions
PCB
0314 HW_WATCHDOG

Summary HW_WATCHDOG.

Description This is not an error, but a warning.
This warning comes after the door controller had had a reset because
of a Watchdog or a self reset
Error response: None, just to notify that there was a Watchdog initiated
reset
Easy Setup: Bargraph-RED_LED-8 [ON]
This could be beacuse of a runaway task. Watchdog will reset the

Extra Info system if it has not been notified within a preset period of time. This
warning is generated at startup of the system.
This warning is generated from General Init

Source ID

Causes and
1 1. Watchdog caused a reset, None
Actions
the reasons are explained in
the Error Description above
2 2. Errors in Peripheral units None
can cause seld resets to
reactivate the Peripherals
0315 IAC_MOD_UPD_FAIL

Summary IAC_MOD_UPD_FAIL.

Description Unable to update the Speed Mode in the Trip Curve Generator.
Error response: Stop all door motions and stop all further door motions
Easy Setup: Bargraph-RE-LED-7 [ON]
Door Mode is set per command, every command has a door mode
Extra Info associated with it. Mostly this error will occur if a door command with
an unsupported door mode is sent. The other reason this error could
occur is when the speed mode dependent parameters cannot be
accessed/read from the Flash.
Trip Curve Generator, when the door mode needs to be changed. This
Source ID error is generated from only one location.

Causes and
1 1. Invalid Door Mode in the 1. Check the debug logs
Actions
command 2. Check the lon trace if it is on
for any door commnad with
invalid door mode in the
command
2 2. Speed Mode dependent 1. Check the speed mode
parameter access failure dependent parameters
2. If
"PAR_NOVRAM_MISSSING"
is also accompanied with this
error, consider replacing the
door controller
0316 IAC_PAR_UPD_FAIL

Summary IAC_PAR_UPD_FAIL.

Description Unable to access the parameters in the IAC
This error could be generated because of the following parameters

Extra Info a. MaxRefrSpeed
b. ReferencingAccDec
c. RefrAccStopping
d. Mass
e. locking_zone_closing_nudging
f. locking_zone_closing_night
g. locking_zone_closing_soft
h. LockingZone
i. locking_zone_closing_turbo
j. ClosedZone
k. ReopeningMode
This error is generated from the IACPanel and SafeDev SW Modules

Source ID

Causes and
1 1. Paremeters not correct 1. Check validity of the
Actions
described parameters
2 1. Flash is not working properly 1. Reset the Door Controller
or gone bad 2. Replace Door Controller
0317 IAC_UNKNOWN_LEVEL

Summary IAC_UNKNOWN_LEVEL.

Description A Command with unknown or incorrect level information was sent.
Error response: Wait till the doors open, and then stop all door motions
If a command with unknown level/floor information is handled, the SW

Extra Info cannot find the corresponding mass for the floor, and without that
information of mass, the door motions cannot be done.
This error is generated from the IAC Panel

Source ID

Causes and
1 1. Unknown floor info a door 1. Check the debug logs
Actions
command 2. Reset the Door Controller
2 2. Incorrect LONV70 Firmware 1. Connect CADI-GC to the lift
controller and check for a valid
version of the LON Firmware
on the LONV70
2. Download valid LONV70
Firmware
3 2. Faulty or loosely fitted 1. Remove and refit the
LONV70 Card LONV70 card
2. Replace the LONV70 card
0318 IAC_DOOR_TYPE_UNKNOWN

Summary IAC_DOOR_TYPE_UNKNOWN.

Description Door type is not known/incorrect from the parameters.
There are two types of door

Extra Info a. Center Door Type (param value: 0,2,4)
b. Telescope Door Type (param value: 1,3,5)
The Parameter involved in this case is

a. TypeOfDoor
This error is generated when the trip is being calculated

Source ID

Causes and
1 1. Incorrect Parameter 1. Check the parameters and
Actions
the actual door type
0319 IAC_CLUTCH_FAILURE

Summary IAC_CLUTCH_FAILURE.

Description Clutch is not locked or unlocked within a preset amount of time
Error response: Wait till the door is open, and then stop all further door
motions
This error is raised because of a timeout, and the timeout can be

Extra Info changed via a parameter
1. ClutchTimeOut
But there could be other mechanical reasons for this error
This error is generated from the IAC Clutch SW Module

Source ID

Causes and
1 1. Too Less timeout value 1. Increase the timout value,
Actions
which will suit the clutch in
question
2 2. Locking zone too small 1. Check the locking zone
value, may be they are too
less, set the parameter values
accodingly for the different
door speed modes
3 3. Clutch electronic cables 1. Check the clutch electronics
cables, disconnect and
reconnect them
4 4. Clutch Sensors Faulty 1. Check the Sensors
2. Replace the Sensors
5 5. EBox Temperature is high 1. Stop the door and removed
the lid cover
2. Use more ventilation
6 6. Clutch Motor Failure 1. Check the working of the
Clutch Motor.
2. Replace the Clutch Motor
0320 ESTIMATED_CONSTRUCT_DATA

Summary ESTIMATED_CONSTRUCT_DATA.
Reserve
Description
None
Extra Info
None.
Source ID
0321 ESK_INTERNAL

Summary ESK_INTERNAL.

Description Error in the ESK controller.
This is not an error, instead its a Warning

This error is generated if the ESK is not in any of the pre-defined state.
Extra Info This is an internal SW error.
This error is generated from ESK State Machine

Source ID

Causes and
1 1. Internal ESK SW error 1. Reset the Door Controller
Actions
2 2. ESK HW fault or loosely 1. Disconnect and reconnect
fitted the ESK cables
3. Replace the ESK HW
3 3. ESK Cables short circuit 1. ESK's flat cable could be
getting short somewhere with
the Ebox body, check for this
2. Shield the flat cable for short
circuit.
0322 ESK_PARAM_WRITE

Summary ESK_PARAM_WRITE.

Description ESK could not write to a parameter. This is not an Error, but a
Warning.

This error/warning is raised when certain parameters when modified

Extra Info via ESK and being set back to the parameters. When the parameters
cannot be written, this error is raised
This error is generated from the ESK SW Module

Source ID

Causes and
Actions
PCB
2 1. ESK is gone bad or ESK 1. Reset the Door Controller
Cables are gone bad 2. Check the cables of the ESK
4. Consider shielding the ESK
Cables
0323 ESK_PARAM_READ

Summary ESK_PARAM_READ.

Description ESK could not read from a parameter. This is not an Error, but a
Warning.

This error/warning is raised when certain parameters when modified

Extra Info via ESK and being set back to the parameters. When the parameters
cannot be read, this error is raised
This error is generated from the ESK SW Module

Source ID

Causes and
Actions
PCB
2 2. ESK is gone bad or ESK 1. Reset the Door Controller
Cables are gone bad 2. Check the cables of the ESK
4. Consider shielding the ESK
Cables
0324 ESK_COMMUNICATION_ERR

Summary ESK_COMMUNICATION_ERR.

Description No communication between Easy Setup and Door Controller. This is a
warning and not an error.

None
Extra Info
This error/warning is generated from ESK SW Module

Source ID

Causes and
1 1. ESK HW is gone bad 1. Reset the Door Controller
Actions
2. Check the ESK HW
2 2. ESK Cables 1. Check the ESK Cables and
connectors
2. Consider Shielding the
cables for short circuits.
0325 VLON_INTERNAL

Summary VLON_INTERNAL.

Description Error in the VLON software or hardware. This is an internal SW Error.
Error response: Wait till door is open, and then stop all door motions
This error is generated if the LON Task could not successfully create
Extra Info the required Queues, Mailboxes or Memory Partitions. Another
possibility is if the mail box pend fails in the task. Then there is also a
possibility of a run away task and then one might get a reset also,
which would have been initiated by the Watchdog.
This error is generated from LON SW Module

Source ID

Causes and
1 1. LON Firmware not valid 1. Check the validity of the
Actions
LON Firmware version via
CADI GC
2. Update the LON Firmware
to valid version
2 2. LONV70 Card has gone bad 1. Reset the Door Controller
2. Replace the LONV70 card
3 3. OS Problem with memory 1. Reset the Door Controller
0326 VLON_TRANSMIT

Summary VLON_TRANSMIT.

Description LON Module could not send a LON Message, this is an internal SW
error.
Error response: Wait till the doors are open and then stop all door
motions
Easy Setup: Bargraph-RED-LED-2 [ON] & LCI-Conn-RED-LED [ON]
This error could be raised because of memory problems with LONV70

Extra Info and the OS
This error is generated from the LON SW Module

Source ID

Causes and
1 1. Memory Problems wiht OS 1. Reset the Door Controller
Actions
2 2. LON Firmware is not correct 1. Check the validity of the
version of the LON firmware on
the LONV70 via CADI-GC
2. Update the LON Firmware
3 3. LONV70 Card is gone bad 1. Replace the LONV70 card
0327 VLON_RECEIVE

Summary VLON_RECEIVE.

Description VLON receiving error, this is an internal SW error
Error response: Wait till door is open, then stop all door motions
Easy Setup: Bargraph-RED-LED-2 [ON], LC-Comm-RED-LED [ON]
This error occurs of the message from the incoming lon queue could
Extra Info not be read
This error is generated from the LON SW Module

Source ID

Causes and
1 1. Memory Problems 1. Reset the Door Controller
Actions
2 1. LON Firmware is not OK 1. Check the validity of the
LON Firmwaer via CADI-GC
2. Update the LON Firmware if
required
3 2. LONV70 Card has gone bad 1. Replace the LONV70 Card
0328 EMERGENCY
This section describes the Varidor70 Door Drive error EMERGENCY.

Summary

Description Drive is not in normal operation anymore and after 2 secs Door
Contoller will reboot.
Error Response: Stop all door motions and stop all further door
motions
This error is generated when the door is requested to do an

Extra Info Emergency Off. This can happen from several locations
a. Control task: when the HW_POS Error is generated
b. Safedev: when the door is in blocked state
This error is generated from Control Task

Source ID

Causes and
1 1. Obstacle in the door way 1. Remove the obstacle in the
Actions
door way
2. Reset the Doot Controller
2 2. Refer to cause and action of 1. Refer to cause and action of
Error HW_POS Error HW_POS
0329 NORMAL_RESET

Summary NORMAL_RESET.

Description A Reset was done. This is a warning and not an error
Error Reponse: None

Easy Setup: None
This error is generated at the startup, which indicated what was the
Extra Info cause of last reset. There could be two causes,
a. Deliberate Reset
b. Watchdog Reset
This is error/warning is generated from General Init

Source ID

Causes and
1 1. A reset had taken place None
Actions
0330 EST_LRACCU_OVERFL

Summary EST_LRACCU_OVERFL.
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and
1 has to be defined has to be defined
Actions
0331 BLOCKED_OPENING_DIRECTION

Summary BLOCKED_OPENING_DIRECTION.

Description The door is blocked in the opening direction.
Error Response: Stop all door motions, and stop all further door
motions
This error is generated in response to the blocked state detected in the

Extra Info Mechanical supervisor module. When, applied force is unable to move
the door in the open direction.
This error is generated from SafeDev SW Module

Source ID

Causes and
1 1. Obstacle in the door ways 1. Remove the Obstacle in the
Actions
door way if any
2 2. Panels Jammed beacuse of 1. Remove or clean the dirt in
dirt on the panel gangway the panel gang way
0332 BLOCK_CLOSE_DIRECTION

Summary BLOCK_CLOSE_DIRECTION.

Description The door is blocked in the closing direction.
Error Response: Stop all door motions, and stop all further door
motions
This error is generated in response to the blocked state detected in the

Extra Info Mechanical supervisor module. When, applied force is unable to move
the door in the open direction.
This error is generated from SafeDev SW Module

Source ID

Causes and
1 1. Obstacle in the door ways 1. Remove the Obstacle in the
Actions
door way if any
2 2. Panels Jammed beacuse of 1. Remove or clean the dirt in
dirt on the panel gangway the panel gang way
0333 SLV70_OBSTACLE_DETECT

Summary SLV70_OBSTACLE_DETECT.

Description An Obstacle was detected during self learning process, this is a
warning and not an error
Error Response: None

Easy Setup: None
None
Extra Info
This error/warning is generated from Self Learning Task

Source ID

Causes and
1 1. Obstacle in the door ways 1. Remove the Obstacel from
Actions
during Self Learning the door ways and start Self
Learning again
0334 SLV70_RESULT_RANGE

Summary SLV70_RESULT_RANGE.

Description Measured parameter value(s) exceed out of range
Error Response: None

Easy Setup: None
This error is generated when measured value(s) is/are out specified

Extra Info range e.g.
a. Mass
b. ForceFriction
c. ForceClosingWeight
d. ForceSigma
This error/warning is generated from Self Learning Task

Source ID

Causes and
1 1. Initial Mass 1. Provide the right initial mass,
Actions
the increments are in
increments of 100kg: 100 to
400 Kg
0335 IAC_CLUTCH_WARNING

Summary IAC_CLUTCH_WARNING.
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and
Actions
0336 DRIVE_OVER_TEMP_WARNING

Summary DRIVE_OVER_TEMP_WARNING.
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and
Actions
0337
HOLDING_FORCE_AT_CLOSED_POSITION

Summary HOLDING_FORCE_AT_CLOSED_POSITION.
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and
Actions
0338 Reserve_8
This section describes the Varidor70 Door Drive error Reserve_8.

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0339 Reserve_9

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0340 Reserve_10

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0341 Reserve_11

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0342 Reserve_12

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0343 Reserve_13

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0344 Reserve_14

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0345 Reserve_15

Summary
has to be defined
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
0400 No_Error
This section describes the Lift error No_Error.

Summary
Base of lift errors definition.

Description
Extra Info
None.
Source ID
0401 VCOM Node Connected
This section describes the Lift error VCOM Node Connected.

Summary
The control software detects a new VCOM bus node (subsystem) on

Description the bus. The message is logged when the connection to the
node/subsystem is established after it was interrupted for some time or
if the node/subsystem is reinitialising. A manual reset of the elevator
control causes this message to be logged on the other elevators in the
group.
(8 digit hex. value xABCDEFGH).

Extra Info
Value of digits ABCDEF: information for R&D only
Value of digits GH: identification number of the VCOM node (pcb):

Old encoding (SUBSYS):
x07 = Controller Lift 1
x0A = Controller Lift 4
x0B = Controller Lift 5
x0C = Controller Lift 6
x0D = Controller Lift 7
x0E = Controller Lift 8
New encoding "LOGADDR"

xD9 = E-Vision PC
xFA = PC_1 (SID Mainstation or M10 overlay)
xF9 = PC_2 (SID Mainstation or M10 overlay)
xF8 = Gateway Interface Board (GW/GW2)
xD1 = SID embedded Lift 1 (PTG1/2)
Examples:
Extra info value = AF56E131: Controller of Elevator #3 connected to
VCOM
Extra info value = 00000081: Controller of Elevator #8 connected to
VCOM
Extra info value = 2901E5FA: SID PC (#1) connected to VCOM
R&D use
Source ID

Causes and
2 Reset button pressed and none (Normal behavior)
Actions
released
3 Power switched on none (Normal behavior)
1 VCOM bus cable connected none (Normal behavior)
4 Ethernet hub/switch powered none (Normal behavior)
on
0402 VCOM Node Disconnected
This section describes the Lift error VCOM Node Disconnected.

Summary
The control software detects that a VCOM bus node (subsystem) is no

Description longer present. The message is logged after the connection to a
node/subsystem is interrupted or when the node/subsystem is
reinitialising. A manual reset of the elevator control causes this
message to be logged on the other elevators in the group.
(8 digit hex. value xABCDEFGH).

Extra Info
Value of digits ABCDEF: information for R&D only
Value of digits GH: identification number of the VCOM node (pcb):

Old encoding (SUBSYS):
x0A = Controller Lift 4
x0B = Controller Lift 5
x0C = Controller Lift 6
x0D = Controller Lift 7
x0E = Controller Lift 8
New encoding "LOGADDR"

xD9 = E-Vision PC
xFA = PC_1 (SID Mainstation or M10 overlay)
xF9 = PC_2 (SID Mainstation or M10 overlay)
xF8 = Gateway Interface Board (GW/GW2)
Examples:
Extra info value = AF56E131: Controller of Elevator #3 disconnected to
VCOM
Extra info value = 00000081: Controller of Elevator #8 disconnected to
VCOM
Extra info value = 2901E5FA: SID PC (#1) disconnected to VCOM
None.
Source ID

Causes and
2 Reset button pressed none (Normal behavior)
Actions
3 Power switched off none (Normal behavior)
1 VCOM cable for group bus none (Normal behavior)
(Ethernet or RS485) manually
unplugged
4 Bad cable connection, EMC, If this message appears very
HW defect, VCOM bus often without an obvious
termination switches on reason, check the VCOM bus
EBCOM set wrongly; Ethernet connection/termination and test
hub/switch powered off the corresponding VCOM node
to verify its operation;
exchange pcb it if necessary.
Check shielding of bus cable.
0403 PowerUp
This section describes the Lift error PowerUp.

Summary
The CPU on the main control pcb reinitialises. Check log for CPU error
Description codes (1000 to 1100).
Depending on Source ID. See below.

Extra Info
00 = Power up the first time

Source ID Extra Info: 01 = First time power up after installation of new SW or
configuration
Extra Info: 02 = Power up after double reset
------------------------------------------------------------------
01 = Power up manual reset or unknown reason
------------------------------------------------------------------
02 = Power up due to CADI reset
------------------------------------------------------------------
03 = Power up due to preparation for new download.
------------------------------------------------------------------
04 = Power up caused by errorhandler:
Extra Info: 01 = Limit for reset action reached
Extra Info: 02 = Reset after "Fatal error block system short"
Extra Info: 03 = Reset after "Fatal error block system long"
Extra Info: 04 = Reset after "Fatal error block system permanent"
------------------------------------------------------------------
05 = Power up Watchdog
Extra Info: Information about internal circumstances of the task(s)
which stopped responding.
See also CPU error 1062.
------------------------------------------------------------------
Causes and
1 Power up after internal Scan error log for reason of
Actions
problem (e.g. Watchdog, reset
Software exception handling)
2 External reason for power up Source Id contains information
(e.g. reset button pressed, about reason for power up
complete loss of power)
0404 Start Monitor Expired
This section describes the Lift error Start Monitor Expired.

Summary
The control generates the error 'trip start monitor expired' when a trip
Description was not initiated within the predefined timeout after sending a trip
command. The error itself has no impact on the operation of the
elevator.
Remark: This error may also occur if a trip command was given and
the door was blocked with PHTS (passengers standing between the
doors).
Possible reasons are:
a) The doors did not close or communication with the door drive(s) was
interrupted.
b) The drive refused to or could not travel or communication with the
drive was interrupted.
c) The door(s) did not to lock or communication with the door drive(s)
was interrupted.
d) An unknown fault occured during one of the trip preparation phases.
01 = Drive print dead while starting

Extra Info 02 = Drive error while starting
03 = Door print dead. Doors couldn't close
04 = Door error. Doors couldn't close
05 = Unknown error while starting
06 = Door print dead. Doors couldn't lock
07 = Door error. Doors couldn't lock
08 = Unknown error while locking
Not relevant
Source ID
Causes and
1 Faulty safety circuit Check the door contacts.
Actions
2 Check the safety circuit.
3 Connection to subsystem lost Check the bus connection and
test corresponding subsystem
necessary to exchange it
0405 Permanent Active Call
This section describes the Lift error Permanent Active Call.

Summary
Permanently active call button. After serving a call the acknowledge

Description lamp or LED of the call button can not be cleared. The call input will be
ignored for a period of time (3 min).
Remark: this monitoring function can not be done on interface with
separate input and output circuitry.
Floor number of the call button I/O

Extra Info
Call type:
Source ID 01 = Car-call side 1
02 = Car-call side 20
03 = Floor-call side 1
04 = Floor-call side 20

Causes and
1 Defective call button or button Check the call button.
Actions
is pressed continuously
2 Check the wiring of the call
button.
0406 ExceptionMC
This section describes the Lift error ExceptionMC.

Summary
Software Warning "EXCEPTION of 68000 microprocessor". The

Description system jumps to the exception routine and causes a watchdog reset.
Reason for the exception (MSByte) and the address where the
Extra Info exception occured (Byte3 - Byte1).
Task_Id where the exception occured. When '0', no task involved.

Source ID

Causes and
1 Faulty EPROM or pcb. Change EPROMs/FLASH or
Actions
Lift Control Processor board. If
the problem can not be solved
contact the field support hotline
or the VX-Center.
0407 COM Bus Stress
This section describes the Lift error COM Bus Stress.

Summary
COM_BUS_STRESSED. The communication System VCOM does not

Description have enough time to work through the telegram buffer on the Data Link
level. External messages, which come in through the bus, might get
lost. Reliable operation is no longer guaranteed.
stress_id from the VCOM_upcall VCOM_BUS_STRESSED

Extra Info 01 = lift bus transmit stressed
02 = lift bus receive stressed
03 = group bus transmit stressed
04 = group bus receive stressed
None.
Source ID

Causes and
1 Bus is faulty Check lift -, groupbus if all links
Actions
and terminators are functional.
generated in a certain period of order to determine the source
time of the telegram flood and test
0408 PIOL_ConfErr
This section describes the Lift error PIOL_ConfErr.

Summary
PIOL CONFIGURATION DATA ERROR.The PIOL print did not receive

Description all the configuration data, or the data contained invalid values.
01 = No response to PCT version number request

Extra Info 02 = No parameters or incomplete parameter list received from
controller
03 = No I/O definition or incomplete I/O definition received from
controller.
04 = Received parameters contain invalid values.
05 = Received I/O definitions contain invalid values.
06 = The local PCT checksum is not consistent with data checksum.
07 = No error, internal message that the cabine print has requestet a
new configuration.
08 = No error, internal message that the cabine print has received a
new configuration.
Note: relevant for Miconic VX, TX release 4 (RS, PIOL print)
None.
Source ID

Causes and
1 Configuration data not Check PROM.
Actions
received
0409 COM_Bus Reconfiguration
This section describes the Lift error COM_Bus Reconfiguration.

Summary

longer guaranteed.

None.
Source ID

Causes and
1 Bus is faulty Check lift -, groupbus; all
Actions
links and terminators are
functional.
addresses
and check if the
7 NOTE : If the problem still
Center.
0410 PIO-Error
This section describes the Lift error PIO-Error.

Summary
Note: relevant for Miconic VX, TX release 4 (RS, PIOL print)

Description
Extra Info
None.
Source ID

Causes and
1 Check the indicated
Actions
components and if necessary
change them
2 Check the wiring of the
described component
0411 ARA-Service
This section describes the Lift error ARA-Service.

Summary
Aramid rope monitoring activated (input KKSA).

Description
not used
Extra Info
ndef
Source ID

Causes and message
Actions
1 none
0412 KTHM-Service
This section describes the Lift error KTHM-Service.

Summary
Overtemperature in machineroom or hoistway detected. The input

Description signal from the temperature sensor installed in the MR or hoistway is
active (normally closed contact). The control activates the service
KTHM and the elevator stops serving calls.
8 digit hex number: 0xSTUVWXYZ where:

Extra Info
ST: not used (always 00)
UV: represents the status of lift input KTHS
WX: represents the status of lift input KTHML
YZ: represents the status of group input KTHM (sensor in
machineroom)
examples:
00000001 (hex) : KTHM is active
00000100 (hex) : KTHML is active
00010000 (hex) : KTHS is active
Combination of signals is possible.
ndef
Source ID

Causes and
1 Overtemperature detected none related to elevator control
Actions
2 Temperature sensor faulty Replace sensor
3 Fault in wiring of sensor Check wiring
4 IO Interface board for sensor Check interface board and
connection faulty (input replace if necessary
electronics)
5 Connector of cable to sensor Check connectors
not plugged in.
0413 TAB-Service
This section describes the Lift error TAB-Service.

Summary
Technical out of service operation activated. The TAB service is

Description activated when a peripheral IO board with critical IO's is no longer alive
(loss of communication).
Critical I/Os are are marked in the schematics and BMK lists (e.g. Fire
Switch JBF, Emergency Power RNO, Earthquake KEB).
Remark: TAB may also occur if a group is temporarily divided. With the
SMLCD command "Service Visit" TAB can be bypassed for trouble
shooting.
The extra information is a 8 digit hex code (Example: x020E8903). The

Extra Info code identifies the peripheral LON IO board causing the activation of
the TAB service. For BIO bus nodes the extra information is 0.
Meaning per digit for LON boards: xABCDEFGH

(refer to error 1209 'Missing Node' for the description of the Board Id
and the Board Type)
AB: Board Id
CD: Board Type
EF: Subnet id
GH: Node id
not used
Source ID

Causes and
1 Missing I/O board(s)/node(s) check peripheral I/O boards
Actions
on the user bus (CAN / LON / (faulty or disconnected); see
BIO2) error log for error 'missing
node'.
2 MX/TX2: A critical I/O was Always exccute the 'Freeze'
configured and then removed command after configuration
(reconfigured). This I/O may be and verification of IOs.
hard to find because it's not
visible in CADI.
0414 SDU-Service
This section describes the Lift error SDU-Service.

Summary
The monitoring device for rope stretch (ASSx) detects

Description inadmissible/critical rope stretch of suspension ropes.
Not used
Extra Info
ndef
Source ID

Causes and
1 Check for excessive rope Shorten ropes if necessary
Actions
stretch
0415 SID Alive
This section describes the Lift error SID Alive.

Summary
The control software resumes/detects communication to PTGx (SID).

Description The message is logged when the connection to the PTGx board is
established after it was interrupted for some time or if the PTGx is
reinitialising. The control monitors the communication to SID
permanently; see also message #416.
not used
Extra Info
R&D use only

Source ID

Causes and
1 PTGx/SID starts running None (normal behavior)
Actions
2 Power supply for PTGx/SID None (normal behavior)
switched on with power on to
control system
3 Bus cable to PTGx/SID None (normal behavior)
manually plugged in
0416 SID Dead
This section describes the Lift error SID Dead.

Summary
The control software detects that no communication to PTGx/SID is

Description possible. The message is logged because the connection to PTGx/SID
is interrupted or when the PTGx/SID is reinitialising. The control
monitors the communication to SID permanently; when communication
is lost the message is logged after 15s. See also message #415. The
parameter 'SID monitoring' is used to configure the monitoring for the
embedded SID.
not used
Extra Info
ndef
Source ID

Causes and
1 PTGx/SID stops running Start PTGx/SID
Actions
2 Power supply for PTGx/SID Restore power to PTGx/SID
switched off with power on to
control system
3 Bus cable to PTGx/SID Connect cable
manually unplugged
4 Bad cable connection, EMC, If this message appears very
HW defect often without an obvious
reason, check the bus
connection (cable, plugs);
check shielding of bus cable.
Exchange pcb it if necessary.
This section describes the Lift error Reserve_Error_417.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0418 IO Subsys_checksum error
This section describes the Lift error IO Subsys_checksum error.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0419 ParamGrp checksum error
This section describes the Lift error ParamGrp checksum error.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0420 SCT/PCT-Checksum
This section describes the Lift error SCT/PCT-Checksum.

Summary
CT CHECKSUMME ERROR. The configuration data of the PCT / SCT

Description are no longer consistent or have been partially destroyed, or the
download was not correct. Reliable operation is no longer guaranteed.
Faulty configuration data group

Extra Info 0x1 = PCT input/outputs
0x2 = PCT parameter
0x4 = PCT Download Checksum Error
0xFC = SCT
Function which detected the error.

Source ID

Causes and
1 During the checksum test of Examine the EEPROM.
Actions
the configuration data
PCT/SCT an illegal change
was detected.
2 Please contact the VX-Center.
3 The download of the When download checksum
configuration data PCT/SCT error occurs, examine the
was not successfull. connection to the configurator.
0421 Invalid Parameter Value
This section describes the Lift error Invalid Parameter Value.

Summary
Software Error "invalid PCT parameter value". Parameter value is out

Description of the predefined range (below allowed minimum value or above
allowed maximum value).
Id. of PCT_GROUP and PCT_ID of the parameter.

Extra Info
None.
Source ID
0422 FLASH Failure
This section describes the Lift error FLASH Failure.

Summary
An error occurred while accessing the FLASH memory. Either read or

Description write access failed. Please check/replace the FLASH devices.
The 8 digit hexadecimal number (0xABCDEFGH) has the following

Extra Info meaning:
Value 'AB': Id of the SW module which tried to access the flash. The
values are:
1: HCO_HANDLE_CONFIG
2: HCO_MEM_MEMORY_MANAGER
3: HCO_SCT_TEST
4: HSCT_SERVICE_LIB
Value 'CD': Id of the flash part which failed to access. The values are:
1: HCO_PCT_SHAFTIMG
2: HCO_PCT
3: HCO_SCT
4: HCO_LEARNTRIP
5: HCO_CHECKSUM_HIGH
6: HCO_CHECKSUM_LOW
7: HCO_EXPANSION_STATE
8: HCO_ALL
9: HCO_SCT_SERVICE
A: HCO_SERVICE_TABLE
B: HCO_FREEZE
Value 'F': read failed indication if value is F
Value 'G': delete failed indication if value is F

Value 'H': write failed indication if value is F
None.
Source ID
0423 PCT define
This section describes the Lift error PCT define.

Summary
Software Error "LPCT create". Parameter group missing in PCT. The

Description software expects the following parameter groups to be present in the
PCT:
PCT_GP_RS_GENERAL, PCT_GP_RS_TIMEOUT,
PCT_GP_RS_COST_CALC, PCT_GP_RS_DOOR_TIME_S1,
PCT_GP_RS_DOOR_TIME_S20
PCT_GP_RS_DOOR_MODE, PCT_GP_RS_PARKING_ZONE
PCT_GP_RS_SERV, PCT_GP_RS_SERV_NAME
PCT_GP_RS_PEAK, PCT_GP_RS_SUBGROUP, PCT_GP_LIFT
PCT_GP_SYSTEM, PCT_GP_RC_1, PCT_GP_RC_20
PCT_GP_ANT, PCT_GP_M10_CONTROL, PCT_GP_M10_DEVICES
PCT_GP_VOICE, PCT_GP_BUS_SYSTEM
None.
Extra Info
None.
Source ID
0424 Parameter Missing
This section describes the Lift error Parameter Missing.

Summary
Indicates that the software tried to access a parameter which is not in

Description the PCT. Software Error Name"PCT parameter not found". Make sure
the correct PCT is downloaded. If necessary contact the hotline of the
supplier. On MX control the PCT is alway consistent with the control
software; exception is if a PCT is downloaded. See extra info value for
information about the missing parameter.
Decoding of the 8 digit hex number xABCDEFGH:

Extra Info There are three different types of extra info used with this message.
Type 1. Identification of the 'para_group_ID' and 'para_ID' of the

missing parameter.
ABCD (Hex): PCT Parameter Group ID
EFGH (Hex): PCT Parameter ID
This extra info is used by most of the software task or store module.
Example: (hex) 00300010
0030: PCT_GP_SYSTEM (0x30)
0010: P_SYS_KS_ASSIGN_MODE (0x10)
2. Special extra info. (for development only)

AB (Hex): Module ID
CD (Hex): Function ID
EF (Hex): No. of error usage in module
GH (Hex): Error info (e.g. VCOM error)
This extra info is used by source ID 13 (store module) and 37, 45
(software tasks
SPG and HLS resp.)
3: Extra info contains defined value. (fro development only)

This extra info is used by source ID 1,5,14 (store module).
4. Extra info contains service variable ID
(e.g. Name: SYS_CONTROL_MODE, Kid ID = 2805) )
This extra info is used by source ID 6 (store module)
Source code file identifier

Source ID
0425 SCT/PCT write error
This section describes the Lift error SCT/PCT write error.

Summary
Software Error "PCT_SCT_write_error". Please contact the VX-Center,

Description reliable operation is no longer guaranteed.
None.
Extra Info
None.
Source ID
0426 Wrong SBT Data
This section describes the Lift error Wrong SBT Data.

Summary
Software Error "invalid service sequence data (SBT)".

Description
This error is generated when the Service Behaviour Table in the SCT
does not have a valid value. Normally this should not happen.
Indicates a possible inconsistency between target software and SCT
(services) version.
For troubleshooting purposes (development).

Extra Info
None.
Source ID
0427 Wrong SCT Data
This section describes the Lift error Wrong SCT Data.

Summary
Software Error "invalid SCT data". Indicates a possible inconsistency

Description between the target software and the SCT (services) version. The error
is logged with different extra info values depending on the problem:
- max number of services in SCT exceeded

- unknown service variable in service
Contact the supplier of the controller.
None.
Extra Info
None.
Source ID

Causes and
1 Service in SCT not compatible Compare services in SCT
Actions
with core SW against released services of
core SW. For each SW version
a list of valid standard services
is available in PNC.
0428 End Monitor Expired
This section describes the Lift error End Monitor Expired.

Summary
Liftcontrol monitors if the trip command sent to travel control, due to a

Description call, is served within a predefined time. After a timeout the liftcontrol
requests update of certain drive staus information.
The liftcontrol starts a timer when sending the start command

(Start_OK) to travel control while starting a trip. When this timer
elapses and the trip has not finished this message will be generated.
The trip will not be interrupted and the software restarts the same
timer. After a trip has started the software stops the timer when:
- the call is served (drive decelerates)
- call is cancelled (new destination)
- travel control 'drive state' is 'unavailable'
- lift stops with travel control 'drive state' = 'standing'
Time limit used for 'End Monitor Expired':

MX: 700s
TX/TX2: 120s
This monitor was introduced on TX4 where separate CPUs existed for
liftcontrol and travel contol. With GC control this monitor is not relevant
because the communication between liftcontrol and travel control can
not be interrupted.
Number of times the message is logged during a trip (max.:4).

Extra Info
Identification number of the source file in the software which generates

Source ID the message.
Causes and
1 Value of parameter V4 (max. None
Actions
speed for normal trip) low
0429 Chipcard general error
This section describes the Lift error Chipcard general error.

Summary
-
Description
-
Extra Info
-
Source ID
0430 Chipcard general warning
This section describes the Lift error Chipcard general warning.

Summary
-
Description
-
Extra Info
-
Source ID
0431 Chipcard general event
This section describes the Lift error Chipcard general event.

Summary
-
Description
-
Extra Info
-
Source ID
0432 Chipcard expansion done
This section describes the Lift error Chipcard expansion done.

Summary
-
Description
-
Extra Info
-
Source ID
0433 Chipcard not valid
This section describes the Lift error Chipcard not valid.

Summary
Software detected invalid chip card. (Chip card data not valid)
Description Comments: MX type controllers will shut down the elevator for normal
use after chip card is removed.
-
Extra Info
-
Source ID

Causes and
1 Chip card data invalid or faulty Order new chip card from
Actions
chip card supplier.
0434 SCT Expansion
This section describes the Lift error SCT Expansion.

Summary
This warning is generated when there is a problem while expanding the

Description SCT on systems where the SCT is configured and not downloaded
(MX). This warning would be accompanied by the PCT/SCT checksum
error. Reasons for such problems are detailed in the extra information,
which is populated as soon as the warning occured.
0xAABBCCDD:
Extra Info
Meaning of DD:
01: SCT size overrun has occurred (HSCT Service Lib module).
02: Maximum number of services has been reached while generation
of SCT (HSCT Service Lib module)
03: Size of individual service is too big while generation of SCT (HSCT
Service Lib module)
04: Size of SCT is too big while generation in the HSCT service lib
module
Meaning of AA: (for development only)

Byte 1 (MSB) in the extra info indicates that the HSCT module is the
source of the warning.
Meaning of BB: (for development only)

not used (always left as "00")
Meaning of CC: (for development only)

Byte 3 indicates the count of the warning.
Task Id.
Source ID
Causes and
1 Too many services ordered. Verifiy oder data.
Actions
0435 Invalid SCT
This section describes the Lift error Invalid SCT.

Summary
The internal consistency check for the SCT failed; the SCT may be
Description corrupted.
Encoded information of the internal consistency check which failed:

Extra Info Format of extra info: 0xAABBCCDD
Meaning of AA: Module ID

Meaning of BB: Circumstance of the error
Meaning of CC: circumstance of the error
Meaning of DD: Identifies the test which failed
ID of the software task that reported the error

Source ID

Causes and
1 Corrupted SCT or internal error On elevator control which
Actions
require PCT/SCT download:
Download the SCT again.
Depending on the cause, it
may be necessary to download
the PCT again, too.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0440 Invalid Parameter Access
This section describes the Lift error Invalid Parameter Access.

Summary
The software attempted to access (read or write) data which is not

Description available or initialized. For details refer to source id number and extra
info value. For the intepretation of the error both source id and extra
info number are required.
Example: if a message is sent to the software requesting a VCOM

telegram for the door status of the rear door and no relar door is
configured in the PCT then this error will be logged.
Source Id: 1 (st_cls)

Extra Info 0000(hex): Entrance side above max. value (CLS_nbr_of_side >
MAX_NUMBER_OF_SIDE)
0100(hex): Wrong floor number when checking for cabin call
(CLS_Is_there_a_cabin_call)
0101(hex): Wrong floor number when writing cabin call
(CLS_Write_cabin_call)
0102(hex): Floor out of range when checking for registered cabin call
(CLS_WRONG_FLOOR)
0500(hex): Entrance side out of range when reading door info
(CLS_Read_door_info)
0501(hex): Side out of range when setting door state to locked
(CLS_Write_door_info)
Source Id: 3 (ffc_id)

00C1(hex): Wrong input parameter found while writing the favourite lift
in the table
0100(hex): Wrong input parameter found while reading the favourite lift
from the table
0101(hex): Wrong input parameter found while adding valid floor calls
to table
0140(hex): Wrong input parameter found while deallocating floor call
for specific lift
0180(hex): Wrong input parameter found while searching for best
active floor calls
01C1(hex): Wrong input parameter found while writing end of serving
(WRONG_LN_CALLTYPE_IN_WRITE)
Source Id: 4 (st_gsi)

0100(hex): Wrong floor number or wrong direction found while reading
boarding rate
0101(hex): wrong floor number or wrong direction found while writing
boarding rate
Source Id: 5 (st_gss)

0001: BAC code cannot be written to store for specific side and floor
(BAC: button access code)
0002: The code that is read is not of BAC code type (BAC: button
access code)
0003: The specific floor and side do not have a BAC code (BAC:
button access code)
0004: The KSF code for specific side and floor cannot be written to
store (KSF: keyless security function)
0005: The code that is read is not of KSF code type (KSF: keyless
security function)
0006: The specific floor and side do not have KSF code
0007: The RAC code cannot be written to specific side and floor
0008: RAC code for a specific floor and side cannot be read
0009: The specific floor and side do not have RAC code
Source Id: 7 (st_lsi)

0000(hex): Invalid Lift Status
0100(hex): failure reading the status of the door reversing devices for
front or rear door (LSI_READ_ACTIVE_REV_DEV)
0101(hex): failure writing the status of the door reversing devices for
front or rear door (LSI_WRITE_ACTIVE_REV_DEV)
0200(hex): failure reading the door availability status for front or rear
door(LSI_READ_DOOR_AVAILABLE)
0201(hex): failure writing the door availability status for front or rear
door(LSI_WRITE_DOOR_AVAILABLE)
0300(hex): failure reading the door interface board status for front or
rear door(LSI_READ_DOOR_IS_ALIVE)
0301(hex): failure writing the door interface board status for front or
rear door(LSI_WRITE_DOOR_IS_ALIVE)
0400(hex): failure reading the state of the door state machine for front
or rear door(LSI_READ_DOOR_MACH_STATE)
0401(hex): failure writing the state of the door state machine for front
or rear door(LSI_WRITE_DOOR_MACH_STATE)
0500(hex): failure reading the state of the door for front or rear
door(LSI_READ_DOOR_STATUS)
0501(hex): failure writing the state of the door for front or rear
door(LSI_WRITE_DOOR_STATUS)
0600(hex): failure reading the status that the door timer has counted
down to the specified time in the table
(LSI_READ_DOOR_TIME_EXPIRED)
0601(hex): failure writing the status that the door timer has counted
down to the specified time in the table
(LSI_WRITE_DOOR_TIME_EXPIRED)
0700(hex): failure reading the status of the final timer for the specified
side(LSI_READ_FINAL_TIMER_ACTIVE)
0701(hex): failure writing the status of the final timer for the specified
side(LSI_WRITE_FINAL_TIMER_ACTIVE)
0800(hex): failure reading the current final timer mask for the specified
side(LSI_READ_FINAL_TIMER_MASK)
0801(hex): failure writing the final timer mask for the specified
side(LSI_WRITE_FINAL_TIMER_MASK)
0900(hex): failure reading the current door reversing devices mask for
specific door side (LSI_READ_REV_DEVICES_MASK)
0901(hex): failure writing the door reversing devices mask for specific
door side (LSI_WRITE_REV_DEV_MASK)
Source Id: 15 (st_inp_hls)

0001: Invalid input read for VXT_INP_GROUP (input_id >=
MAX_INP_GROUP)
0002: Invalid input read for VXT_INP_LIFT (input_id >=
MAX_INP_LIFT)
0003: Invalid input write for VXT_INP_GROUP (input_id >=
MAX_INP_GROUP)
0004: Invalid input write for VXT_INP_LIFT (input_id >=
MAX_INP_LIFT)
0005: Fatal status written to Wrong subsystem id (subsys_id >=
MAX_SUBSYSTEM)
0006: Fatal status read from Wrong subsystem id (subsys_id >=
MAX_SUBSYSTEM)
For source Id. = 16/17: Parameter group id. and parameter id. of
parameter (hex)
Source Id: 37
0x02000100: parameter id is out of range
0x02000300: parameter priority is out of range while evaluation best lift
0x03000100: wrong service found while checking the service status
change
0x03000200: wrong service phase found while checking the phase
conditions
0x03000400: wrong service phase found while cheking the phase
condition for BS2 service
condition for DNF2 service
condition for JBF and JNFF service
0x03000700: while service id found while checking the phase
conditions for different services
0x000000CB: phase found to be out of range for RNO service
0x03000A00: phase found to be out of range for BS2 service
0x03000B00: phase found to be out of range for DNF2 service
0x03000C00: phase found to be out of range for JBF and JNFF service
0x03000D00: phase found to be out of range for SO service
0x06000400: none of the timer id's are available for the timer request
0x06000200: Call Validation Handler did not accept the next M10
terminal call request
0x04000100: wrong phase number found while reading the next phase
of specific service
0x05000100: No free place is available in the database to store the
specific timer status
0x05000200: the specific timer is not available in the table for writing its
status
Source Id: 45
0x01000100: Telegram does not exist in VXT_INP_GROUP
0x02010100: side1 or side2 or side 3 do not exist of lift does not exist
for serving the floor calls
0x021F0200: side 1 or side 2 or all sides do not exist for that cabin call
0x021F0300: side 1 or side 2 or all sides do not exist for that floor call
0x021F0400: side 1 or side 2 or all sides do not exist for that floor and
cabin call
0x021F0500: call type is neither floor call not cabin call
0x04000100: timer request failed
0x04000200: Reading status from Invalid Timer
0x04000300: Writing status to invalid timer
0x04000400: Invalid service id found for deleting a set timer for a
specific service
0x04000500: Invalid Timer found before clearing a specific timer
0x05000100: Wrong service id found while reading the active status of
the service
0x05000200: Service id is out of bound while reading the address of
service header id
service active id
0x05000400:Service id is out of bound while reading the address of
service deactive id
0x05000500: Service id is out of bound while reading the address of lift
phase id
phase of specific service
0x05000700: Invalid service phase
0x05000800: Service id is out of bound while reading the address of lift
asynch id
0x05000900: Service asynch is incorrect while reading the status of
asynch from the table
0x05001000: Service id is out of bound while reading the next phase of
the specified service
0x05001100: Service id is out of bound while reading the specified
service id
0x05001200: Service id is out of bound while reading the non volatile
information of specified service
0x05001300: Service id is out of bound while returning the recall phase
flag of specific service
0x05001400: Service id is out of bound while returning the service
priority
0x05001500: Service id is out of bound while writing the status of
service into the vector table
0x05001600: Service asynch is incorrect while writing the status of
asynch to the table
5001700 Service id is out of bound while writing the actual current
service to the table
5001800 Service id is out of bound while writing the phase number to
be executed next to the vector table
5001900 Service id is out of bound while writing non volatile
information of specific service in the vector table
5002000 Service id is out of bound while writing the recall phase of
specific service to the vector table
5002100 service id and priority are incorrect while writing the service
priority of specific service to the vector table
5002200 Invalid service flag id for a specific service
5002300 Reading invalid service flag for a specific service
5002400 setting a value to invalid service variable
5002500 reading invalid service variable
0C000100 writing invalid service variable to non volatile memory
0C000200 reading invalid service variable from non volatile memory
Source Id: 80 LPCT parameter not found during the initialization of

GIO_CR module
Format: 0x00XX00YY where XX: PCT_GP_SYSTEM and YY:
P_SYS_CONTROL_MODE
Source Id: 82 Initialization problem for BMKs in ioc_conf

0x02000100: Conversion of numeric digits failed
0x02000300: The special string info was not found
Software task identifier or source code file identifier.

Source ID
Source Id. 1(dec): Error in st_cls.cpp
Source Id. 3(dec): Error in ffc_id.cpp
Source Id. 4(dec): Error in st_gsi.cpp
Source Id. 5(dec): Error in st_gss.cpp
Source Id. 7(dec): Error in st_lsi.cpp
Source Id. 15(dec): Error in st_inp_hls.cpp Wrong telegram data or info
on INP_GROUP or INP_LIFT telegram.
Source Id. 16/17(dec): Wrong parameter.
Source Id. 45(dec): SCT/service problem.
Source Id. 80(dec): GIO_TASK_ID
Source Id. 82(dec): IOC_TASK_ID / BMK string not valid.

Causes and
1 Wrong parameter in PCT Check configration of the
Actions
control (PCT) with CADI.
0441 Invalid Telegram Data
This section describes the Lift error Invalid Telegram Data.

Summary
The software detects invalid value in data part of a VCOM telegram.

Description
Identification of the telegram with the invalid data:

Extra Info
01000200(hex): VXT_DNF1 floor
01000300(hex): VXT_DDF1 floor
01000400(hex): VXT_DGSC floor
01000500(hex): VXT_DFDC floor
01000600(hex): VXT_JNFE floor
01000800(hex): VXT_KKL floor or side
010008xx(hex): DDF1 destination side

01000900(hex): DDF1 boarding side
010009xx(hex): DDF1 destination floor
01000A00(hex): DDF1 boarding floor
01000B00(hex): JRV/JLI boarding floor
01000C00(hex): JRVJLI boarding side
Task id.
Source ID
0442 Invalid Telegram Attribute
This section describes the Lift error Invalid Telegram Attribute.

Summary
The software detects invalid value for an attribute in a VCOM telegram.

Description
Identification of the telegram with the invalid data:

Extra Info
01000100(hex): VXT_JSPZS wrong side
01000200(hex): VXT_DNF1 wrong side
01000300(hex): VXT_DDF1 wrong side
01000400(hex): VXT_DGSC wrong side
01000500(hex): VXT_DFDC wrong side
01000600(hex): VXT_JNFE wrong side
Task id.
Source ID
0443 Invalid Telegram ID
This section describes the Lift error Invalid Telegram ID.

Summary
The software detects an invalid telegram ID for a VCOM telegram.

Description
Identification of the telegram group with wrong telegram id.:

Extra Info
01000700(hex): wrong id for telegram group VXT_INP_LIFT
01000100(hex): wrong id for telegram group VXT_INT_LIFT
01000200(hex): wrong id for telegram group VXT_EVENTS
Task id.
Source ID
0444 Invalid Telegram Group
This section describes the Lift error Invalid Telegram Group.

Summary
The software detects an invalid telegram group ID for a VCOM

Description telegram.
None.
Extra Info
None.
Source ID
0445 Invalid Lift Number
This section describes the Lift error Invalid Lift Number.

Summary
Software Warning "wrong lift number"

Description
Lift number defined with rotary switch exceeds value of parameter
'NUMBER OF LIFTS'
None.
Extra Info
None.
Source ID

Causes and
1 Wrong configuration data Order/correct configuration
Actions
(TX/MX: PCT) data.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0449 PCT config error
This section describes the Lift error PCT config error.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0450 Parameter Configuration Error
This section describes the Lift error Parameter Configuration Error.

Summary
Sofware Warning "param_config_process_error"

Description
Source Id: 41 (hco_handle_config)

Extra Info 0000: error reading parameter group
other values: error in function HCO_reply_param_group
Source Id: 80
0000: configuration error (gio_conf)
0001: LONICx/LONGICx configuration error (gio_ic)
Software task identifier or source code file identifier.

Source ID
Source Id. 41(dec): HCO_TASK_ID
Source Id. 80(dec): GIO_TASK_ID
0451 IO Configuration Error
This section describes the Lift error IO Configuration Error.

Summary
Sofware Warning "io_config_request_error"

Description
Error 451 is no longer used. Please refer to error 951 'IO Configuration
Error'
None.
Extra Info
None.
Source ID
0452 SCT/PCT read error
This section describes the Lift error SCT/PCT read error.

Summary
Software Warning "st_ct_read"

Description
None.
Extra Info
None.
Source ID
0453 Timer Table Overflow
This section describes the Lift error Timer Table Overflow.

Summary
Software Warning "timeout table overflow"

Description
None.
Extra Info
None.
Source ID
0454 Totals log overflow
This section describes the Lift error Totals log overflow.

Summary
The error counters log is full

Description
None.
Extra Info
None.
Source ID
0455 Unknown task id
This section describes the Lift error Unknown task id.

Summary
Software Warning "unknown_task_id in error handler"

Description
None.
Extra Info
None.
Source ID
0456 CT download_successful
This section describes the Lift error CT download_successful.

Summary
Software Warning "CT_download_successfull"

Description
None.
Extra Info
None.
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0460 VCOM Init
This section describes the Lift error VCOM Init.

Summary
Software Warning "VCOM_init"

Description
None.
Extra Info
None.
Source ID
0461 VCOM open
This section describes the Lift error VCOM open.

Summary
Software Warning "VCOM_open"

Description
None.
Extra Info
None.
Source ID
0462 VCOM close
This section describes the Lift error VCOM close.

Summary
Software Warning "VCOM_close"

Description
None.
Extra Info
None.
Source ID
0463 VCOM provide
This section describes the Lift error VCOM provide.

Summary
Software Warning "VCOM_provide"

Description
None.
Extra Info
None.
Source ID
0464 VCOM unprovide
This section describes the Lift error VCOM unprovide.

Summary
Software Warning "VCOM_unprovide"

Description
None.
Extra Info
None.
Source ID
0465 VCOM request
This section describes the Lift error VCOM request.

Summary
Software Warning "VCOM_request"

Description
None.
Extra Info
None.
Source ID
0466 VCOM unrequest
This section describes the Lift error VCOM unrequest.

Summary
Software Warning "VCOM_unrequest"

Description
None.
Extra Info
None.
Source ID
0467 VCOM send
This section describes the Lift error VCOM send.

Summary
Software Warning "VCOM_send"

Description
None.
Extra Info
None.
Source ID
0468 VCOM pend
This section describes the Lift error VCOM pend.

Summary
Software Warning "VCOM_pend"

Description
None.
Extra Info
None.
Source ID
0469 VCOM get
This section describes the Lift error VCOM get.

Summary
Software Warning "VCOM_get"

Description
None.
Extra Info
None.
Source ID
0470 VCOM accept
This section describes the Lift error VCOM accept.

Summary
Software Warning "VCOM_accept"

Description
None.
Extra Info
None.
Source ID
0471 VCOM reply
This section describes the Lift error VCOM reply.

Summary
Software Warning "VCOM_reply"

Description
None.
Extra Info
None.
Source ID
0472 VCOM queue overflow
This section describes the Lift error VCOM queue overflow.

Summary
A software-task received too many messages within a short period of

Description time, or is not responding. Software Warning "VCOM_queue_full".
IMPORTANT: If the error keeps appearing during normal operation

reliable operation of the elevators is no longer guaranteed. Save the
error log(s) and note the circumstances under which the error
occurred. Contact the Ebikon help desk or the hotline of the supplier.
The error indicates that internal messages may be lost; some services
or I/O may get stuck; eventually a reset on the lift control may be
necessary to restore normal operation.
This error is reported in 2 stages. The difference can be identified by
the Extra Info:
OV_MOD_WARNING: This indicates a brief period of extreme stress

has activated the "OV-MOD" protection mechanism. No messages are
lost, but the system is in a dangerous condition. If the extreme stress
persists message will finally be lost. (This serves as a warning that to
adjust the size of the queue concerned.)
VCOM_QUEUE_FULL: This error normally appears after the OV-MOD

warning. The protection mechanism has reached its limits and
messages are now being lost.
Note that this error is reported in the log only for the first overflow of a
particular queue for a period of several seconds; subsequent overflows
are not reported in order to prevent further bus stress on the system.
Represents the queue_id from the VCOM_upcall

Extra Info VCOM_QUEUE_FULL:
x100000yy, yy=queue_id from the VCOM_upcall
VCOM_OV_WARNING
x0F0000yy, yy=queue_id from the VCOM_upcall
VCOM_QUEUE_FULL
x000000yy, (TX4) yy=queue_id from the VCOM_upcall
VCOM_QUEUE_FULL
None.
Source ID

Causes and
1 Problem with VCOM Remove elevator control from
Actions
communication group communication and
check if error disappears.
2 EMC interferences Check for EMC problems
(shielding, separate cables ...)
3 Faulty pcb Check EBCOM and replace if
necessary.
0473 VCOM table full
This section describes the Lift error VCOM table full.

Summary
Software Warning "VCOM_table_full"

Description One of the internal tables used by the communication system VCOM is
full or overflowed. These tables keep track of which tasks send and
receive messages to and from which other tasks. (Like an address
book) If these tables are full, messages cannot be delivered. This
condition is generally not affected by the total volume of messages, but
by too many tasks which must send and receive too many different
kinds of messages to each other.
IMPORTANT!
Immediately save all error logs, and note the circumstances of the
error.
Please immediately contact the VX-Center, reliable operation is no
longer guaranteed.
Encoded information from the VCOM_upcall:

Extra Info 0x00000100 + cause: VCOM_ADMIN_FULL:
0x00000101: cause == 1 <--- horizontal dimension (requestor)
0x00000102: cause == 2 <--- horizontal dimension (provider)
0x00000103: cause == 3 <--- vertical dimension
0x00000200: VCOM_UPDATES_FULL
0x00000300 + cause: VCOM_LOC_TABLE_FULL:
0x00000301: cause == 1 <--- (requestor)
0x00000302: cause == 2 <--- (provider)
None.
Source ID
Causes and
1 Too many special telegrams or Please contact the VX-Center.
Actions
special custom services
configured in the PCT/SCT
2 Incorrect use of wildcards and Please contact the VX-Center.
MYLIFT in the PCT
3 Too many times the same Please contact the VX-Center.
telegram is configured on
multiple I/O boards in PCT.
4 Software problem. Please contact the VX-Center.
0474 VCOM Comms Queue Full
This section describes the Lift error VCOM Comms Queue Full.
Summary
Software Warning "VCOM_comms_queue_full".

Description Generated from the VCOM_upcall VCOM_COMMS_Q_FULL
IMPORTANT!
Immediately save all error logs, and note the circumstances of the
error.
Contact the R&D hotline or the VX-Center; reliable operation is no
longer guaranteed.
None.
Extra Info
None.
Source ID
0475 Too much Bus reconfiguration
This section describes the Lift error Too much Bus reconfiguration.
Summary
Software Warning "Too much Bus reconfiguration"

Description
None.
Extra Info
None.
Source ID
0476 Elevator Operation Interrupted
This section describes the Lift error Elevator Operation Interrupted.

Summary
This message indicates the interruption of the elevator operation due to

Description the activation of the FATAL service (elevator breakdown). The FATAL
service is used to block the elevator temporarily or permanently after a
severe error condition is detected in a subsystem (drive, door etc.);
with active FATAL service the output signal RSM is active.
Normally a specific error is logged just before this message (see also
description for extra info value). With active FATAL service the elevator
is no longer available for transport. When the elevator recovers from
FATAL service the control logs the message 477 'Elevator Operation
Resumed'. See description of error 477 for recovery conditions.
See value of extra information for further details about:

- predefined duration of temporary or permanent active fatal service
- current service before activation of fatal service
- error number which caused the activation of the fatal service (reason)
Interpretation (decoding) of the 8 digit hex. value (0xABCDEFGH)

Extra Info
Value of 'ABCD': Value of the error number that caused the activation
of FATAL service.
Example: if the value of ABCD is 012C(hex) it needs to be converted to
decimal value:
Hex012C => Dec300 => Error 300 caused the Fatal Error (use
calculator or smartphone app to convert).
Value of 'EF': Service Id. number of the Current Service when the error
ocurred.
For Example:
01: Normal Service 'N'
0A Inspection Service 'INS'
0E: Unavailable Service 'UNV'
1B: SAB Service
Value of 'GH':
00: Fatal Service with Permanent Blockage
01: Fatal Service with Short Blockage
05: Fatal Service with Long Blockage
1E: Fatal Service with Blockage from Door Module
Identifies the software task which requests the lift control to take the
Source ID system into fatal service.
1: Init Task
45(dec): Lift Service Task
90(dec): Door Control Front Door (Module RC1)
91(dec): Door Control Rear Door (Module RC2)
117(dec): Travel Control

Causes and
1 An error occurred which sets Please refer to the extra
Actions
the elevator to status 'fatal'. information of this message for
This message itself is not an the causing error. The
error. description of the causing error
shall be used for further
analysis.
2 Example: The door is kept None, the controller resumes
open by blocking PHTS for normal operation as soon as
more than 5 minutes. the PHTS is released. Reason
for activation of FATAL service
is taking the elevator out of the
group because calls on other
floors can no longer be served.
In some cases no separate
error might be logged.
0477 Elevator Operation Resumed
This section describes the Lift error Elevator Operation Resumed.

Summary
The message indicates deactivation of FATAL service; the elevator

Description resumes operation. See also error 476 for description of activation of
FATAL service (temporary or permanent).
See value of extra information for further details about:
- cause of fatal service reset (manual reset of permanent or temporary

fatal service or time-based reset of temporary fatal service)
- current service before activation of fatal service
- error number which caused the activation of the fatal service (reason)
Interpretation (decoding) of the 8 digit hex. value (0xABCDEFGH)

Extra Info
Value of 'ABCD': Value of the error number that caused the activation
of FATAL service.
Example: if the value of ABCD is 012C(hex) it needs to be converted to
decimal value:
Hex012C => Dec300 => Error 300 caused the Fatal Error (use
calculator or smartphone app to convert).
Value of 'EF'(Bit 8 to Bit 15) : Service Id. number of the active (current)
service before Fatal service ON (see error 476)
For Example:
01: Normal Service 'N'
0A: Inspection Service 'INS'
0E: Unavailable Service 'UNV'
1B: SAB Service
Value of 'GH': Fatal Reset cause

00: Fatal service OFF after Reset Timer expired
01: Fatal service Off after Manual Reset
Identifies the software task which requests the lift control to take the
Source ID system out of fatal service.
1: Init Task
45(dec): Lift Service Task
90(dec): Door Control Front Door (Module RC1)
91(dec): Door Control Rear Door (Module RC2)
117(dec): Travel Control

Causes and
1 not applicable (the message
Actions
'Fatal Error OFF' is not an
error)
0478 OVERLAY failure
This section describes the Lift error OVERLAY failure.

Summary
The message indicates a status change of the overlay Master and/or

Description Slave PC (M10 overlay/Schindler ID) detected by the control software.
This message is generated when the communication with the Overlay
Master/Slave PC (M10 or Schindler ID) fails.
Interpretation of values:
Extra Info
0101(hex): PC1 ok, PC2 failed, Communication to overlay OK
0011(hex): PC1 failed, PC2 ok, Communication to overlay OK
0000(hex): Communication Failure
None.
Source ID

Causes and
1 Failure of master or slave Check overlay PC and replace
Actions
overlay (PC) if necessary
2 Communication link to master Check connection between
or slave overlay (PC) control and overlay PC.
disconnected Reestablish communication
3 Overlay software (application) Check operation of overlay
no longer responding or shut application
down
4 Problem with interface board Replace interface board
on master/slave overlay PC

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0480 No Modem
This section describes the Lift error No Modem.

Summary
No Modem
Description
ndef
Extra Info
ndef
Source ID
0481 Modem Present
This section describes the Lift error Modem Present.

Summary
Modem present
Description
ndef
Extra Info
ndef
Source ID
0482 Modem Calling
This section describes the Lift error Modem Calling.

Summary
Modem is dialing a telephone number. See also message 484 'Modem

Description Online'
None
Extra Info
ndef
Source ID

Causes and
1 None. This message indicates
Actions
the number of calls that were
attempted.
0483 Modem Answering
This section describes the Lift error Modem Answering.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0484 Modem Online
This section describes the Lift error Modem Online.

Summary
Modem is already in a call with another modem. This indicates the

Description number of calls that successfully contacted the ADSS modem. See
also message'482' Modem Calling.
not used
Extra Info
ndef
Source ID

Causes and
1 None. This indicates the
Actions
modem successfully contacted
the ADSS modem.
0485 Modem Error
This section describes the Lift error Modem Error.

Summary
Modem cannot initiate a call because the telephone number

Description information in the PCT is not valid.
not used
Extra Info
ndef
Source ID

Causes and
1 Wrong phone number Check that the correct ADSS
Actions
programmed phone number has been
programmed, including any
special prefixes (such as 8 or 9
or) which may be required for
the modem to reach an outside
phone line.
0486 Modem Line Busy
This section describes the Lift error Modem Line Busy.

Summary
Modem initiates a call but the destination telephone number is busy.

Description
not used
Extra Info
ndef
Source ID

Causes and
1 All lines (e.g. on ADSS) could None
Actions
possibly be busy, but this
should be a rare occurance.
2 Wrong phone number Check that the correct ADSS
programmed phone number has been
programmed, including any
special prefixes (such as 8 or 9
or) which may be required for
the modem to reach an outside
phone line.
0487 Modem No Dialtone
This section describes the Lift error Modem No Dialtone.

Summary
Modem wants to initiate a call but does not detect a dialtone.

Description
not used
Extra Info
ndef
Source ID

Causes and
1 Phone line dead Check phoneline for dialtone if
Actions
problem persists
0488 Modem No Carrier
This section describes the Lift error Modem No Carrier.

Summary
Modem no carrier
Description
ndef
Extra Info
ndef
Source ID
0489 Modem Delayed
This section describes the Lift error Modem Delayed.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0490 Table_Overflow
This section describes the Lift error Table_Overflow.

Summary
The software detects a table overflow in the IO handler or an overflow

Description of the buffer (200 messages) that is provided between the target and
the remote monitoring system (typically the error is generated when
there is a burst of updates sent to the Servitel system).
The extra info identifies the unique function call that led to the table
Extra Info overflow. It defines the table, the index value and the specific function
in the code that caused the overflow.
Identifies the source that caused the data overflow. The number
Source ID identifies the STR task.
23 = SAP_TASK
81 = GIO TASK
82 = IOC TASK
83 = GIOT TASK
84 = IOH TASK
88 = UDS TASK
0491 User Level 3 disabled
This section describes the Lift error User Level 3 disabled.

Summary
This event is sent when the control disables the access from the ESM
Description to all menu dialogs for the enhanced service functions. The message
means that the user level 3 (UL3) is disabled.
This occurs after:

1. the elevator has made 10,000 trips serving a floor call or a car call
including door opening.
2. the elevator has made 2000 trips serving a floor call or a car call
including door opening when the enhanced I&M functions were re-
enabled before.
3. the command 'Disable enhanced service functions' is done on ESM

or SPECI.
Extra Info
Source ID

Causes and
1 normal action none
Actions
0492 User Level 3 reenabled
This section describes the Lift error User Level 3 reenabled.

Summary
The control reports this message (event) when the enhanced service
Description functions (User Level 3) are Re-Enabled manually from the ESM or
SPECI. The disabling of the enhanced service functions can be
undone once (!) by selecting the corresponding dialog in the
ESM/SPECI menu.
Extra Info
Source ID

Causes and
1 normal action none
Actions
0493 Low Building Sway Active
This section describes the Lift error Low Building Sway Active.
Summary
Low Building Sway is activated (KGS1)

Description
None
Extra Info
Not used
Source ID
0494 Medium Building Sway Active
This section describes the Lift error Medium Building Sway Active.
Summary
Medium Building Sway is activated (KGS2)

Description
None
Extra Info
Not used
Source ID
0495 High Building Sway Active
This section describes the Lift error High Building Sway Active.
Summary
High Building Sway is activated (KGS3)

Description
None
Extra Info
Not used
Source ID
0496 Building Sway Deactivated
This section describes the Lift error Building Sway Deactivated.

Summary
Building Sway is deactivated

Description
None
Extra Info
Source ID
0497 Ins IO Missing
This section describes the Lift error Ins IO Missing.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
0498 Group 24VDC Fail
This section describes the Lift error Group 24VDC Fail.

Summary
The Group 24V supply voltage is out of tolerance (24V20%). If the

Description warning 'Lift24VDCFail' occurs simultaneously, the system may be
running on the backup battery power only.
Note: The battery charge level is tested every hour and after a manual
reset. After either 'Lift24VDCFail' or 'Group24VDCFail' event the
battery is not tested, since testing the battery could eventually interrupt
power to the control.
ndef
Extra Info
None
Source ID
0499 Lift 24VDC Fail
This section describes the Lift error Lift 24VDC Fail.

Summary
The Lift 24V supply voltage is out of tolerance (24V20%). If the warning
Description 'Group24VDCFail' occurs simultaneously, the system may be running
on the backup battery power only.
Note: The battery charge level is tested every hour and after a manual
reset. After either 'Lift24VDCFail' or 'Group24VDCFail' event the
battery is not tested, since testing the battery could eventually interrupt
power to the control.
None
Extra Info
None
Source ID
0500 12VDC Power Fail
This section describes the Lift error 12VDC Power Fail.

Summary
The internal 12V supply voltage is out of tolerance.

Description
Note: The 12VDC supply powers optional encoders and I/O circuits on
the ASILOG/ASIX.
None
Extra Info
None
Source ID
0501 Battery Charging
This section describes the Lift error Battery Charging.

Summary
The errors occurs if the control cannot perform the battery test
Description because the battery is being charged. After that the control attempts to
check the battery every 5min. The battery charging is done
automatically by the hardware. Refer also to error message 'Battery
Charge Time Expired'.
Remark: This event is normal following a power failure. If the battery

requires increasingly charging, the battery should be checked to see if
it is OK, and replaced if necessary. Normally, the battery level is tested
at every reset and once an hour there after, however if the battery is
charging then the reserve level of the battery is not tested since the
battery needs charging anyway.
None
Extra Info
None
Source ID
0502 Battery Charge Low
This section describes the Lift error Battery Charge Low.

Summary
The battery test indicates that the battery charge is less than 50% of
Description the nominal charge. The battery charge level is tested every hour and
after a manual reset. If the battery is consistently low it should be
checked to see if it is ok, and be replaced if necessary.
NA requirement (A17.1/B44): On MRL installations the elevator is shut

down (FATAL) because it is not allowed to run the elevator with
insufficient battery charge.
None
Extra Info
None
Source ID
0503 Battery Charge Very Low
This section describes the Lift error Battery Charge Very Low.
Summary
The battery test indicates that the battery charge is less than 10% of
Description the nominal charge. The battery charge level is tested every hour and
after a manual reset. If the battery is consistently low it should be
checked to see if it is ok, and be replaced if necessary.
NA requirement (A17.1/B44): On MRL installations the elevator is shut

down (FATAL) because it is not allowed to run the elevator with
insufficient battery charge.
None
Extra Info
None
Source ID
0504 Battery Dead / Missing
This section describes the Lift error Battery Dead / Missing.

Summary
The battery test indicates that the battery is either completely

Description discharged, dead, damaged, or disconnected (battery voltage too low).
The battery voltage level is tested once every hour and after a manual
reset provided normal voltage supply (Group24VDC/Lift24VDC to
ASILOG/ASIX) is on.
None
Extra Info
Source ID

Causes and
1 Battery not connected Check the wiring and
Actions
connections to the battery
2 Leave the controller powered
on, see if the battery is
charged eventually
3 Low battery voltage Measure the voltage of the
battery.
It should be about 12VDC
4 If the error occurs again, check
the battery and replace it if
necessary
0505 Battery Charge Time Expired
This section describes the Lift error Battery Charge Time Expired.
Summary
The control monitors the charging time of the battery. The error occurs
Description if the control detects that the charging of the battery is active for more
than 10 hours. (Typical behavior of a lead type accumulator after ist
lifetime has elapsed.)
As the battery charging is hardware controlled the software can no
longer test the battery if the charging does not stop.
None
Extra Info
None
Source ID

Causes and
1 Battery broken Replace the battery
Actions
0506 Battery Charge Low on PEBO
This section describes the Lift error Battery Charge Low on PEBO.
Summary
This message is reported in case the manual passenger evacuation

Description device has a battery low condition.
The elevator is shut down (FATAL service ) because it is not allowed to
run the elevator with insufficient battery charge.
This message can be reported in case of a PEBO type evacuation
device or in case of a BCM type evacuation device with a external
power battery supply.
The extra info shows the number and the status of the assembled
Extra Info batteries.
The information is shown in a 8 digit number.

The first digit at the left side shows the number of assembled batteries
(1 to 7)
The other 7 digits show the status of each battery. The battery 1 is
shown at the most right digit.
Battery status
0 : Battery charge invalid (for not assembled battery)
1 : Battery charge low -> Trigger for message
2 : Battery charge limit 10%
3 : Battery charge limit 50%
4 : Battery charge high
None
Source ID
0507 Building Sway Detection Device Error
This section describes the Lift error Building Sway Detection Device
Summary Error.
Building Sway Detection Device has an error (ie the validity status =
Description invalid)
None
Extra Info
Source ID
0508 WAD-Service
This section describes the Lift error WAD-Service.

Summary
Water detection in pit active (input KWSG). The elevator will resume
Description normal operation after activation of the input KWSG-A.
not used
Extra Info
ndef
Source ID
0509 Group Master Conflict
This section describes the Lift error Group Master Conflict.

Summary
The master switching algorithm encountered an error determining the

Description correct master.
For example:If there is more than one master, only the lowest
numbered lift should remain master. In case one lift has a
communication disturbance, however, it might not detect this situation
and not relinquish mastership.
If one lift can transmit but not receive group communication or vice
versa, this error will appear.
not used
Extra Info
ndef
Source ID

Causes and
1 Defective EBCOM (can only Replace EBCOM if persistent
Actions
transmit or can only receive). group operation problems are
Red LED on EBCOM may be observed
on or blink.
0510 TM Stress Warning Limit Exceeded
This section describes the Lift error TM Stress Warning Limit

Summary Exceeded.
The monitoring of the traction media done with the related trip counter
Description or the bent cycle counter reports that the elevator has reached the
warning limit defined by the parameter
“P_TMM_STRESS_COUNT_WARN_LIM”.
not used
Extra Info
ndef
Source ID
0511 TM Stress Maximum Limit Exceeded
This section describes the Lift error TM Stress Maximum Limit

Summary Exceeded.
The monitoring of the traction media done with the related trip counter
Description or the bent cycle counter reports that the elevator has exceeded the
maximum limit defined by the parameter “Name
P_TMM_STRESS_COUNT_MAX_PERMIT_LIM”.
not used
Extra Info
ndef
Source ID
0512 TM Aging Warning Limit Exceeded
This section describes the Lift error TM Aging Warning Limit

Summary Exceeded.
The monitoring of the aging time detects that the traction media (belt)
Description has reached its lifetime warning limit defined by the parameter
“P_TMM_AGING_DURATION_WARN_LIM”.
not used
Extra Info
ndef
Source ID
0513 TM Aging Maximum Limit Exceeded
This section describes the Lift error TM Aging Maximum Limit

Summary Exceeded.
The monitoring of the aging time detects that the traction media (belt)
Description has reached its lifetime maximum limit defined by the parameter
“P_TMM_AGING_DURATION_MAX_PERMIT”. The elevator is no
longer available. The traction media must be replaced.
not used
Extra Info
ndef
Source ID
0514 TM Defect Steel Cord in Coated
Traction Media
This section describes the Lift error TM Defect Steel Cord in Coated
Summary Traction Media.
The elevator is shutdown due to a part of the steel cord of the traction
Description media (belt) touching a pulley (ground fault detected). This message is
logged at activation of the input IGFTM. The elevator is blocked and
automatic operation can only be resumed with a manual reset
(command from SMLCD). Manual trips (inspection) are still possible.
The traction media must be replaced. See also cause & action.
not used
Extra Info
Source ID

Causes and
1 Belt damaged due to wear or Check condition of belt
Actions
other reason for steel core (traction media)
ground fault
2 Fault in wiring of the electrical Check corresponding wiring
circuit for the input IGFTM
3 Broken IO interface board or Check operation of the input;
electronics. replace interface board if
damaged.
0515 Flash Write Shaft Image
This section describes the Lift error Flash Write Shaft Image.
Summary
Indicates the software writes the Shaft Image values from RAM to
Description FLASH memory.
not used
Extra Info
Source ID
0516 TM Virgin Store Detected
This section describes the Lift error TM Virgin Store Detected.

Summary
NEW:
Description A mismatch between the reference keys is detected and one storage is
virgin. The controller copies the TMM Installation from the non virgin
storage to the virgin one.
OLD, not used

TM New Storage detected
TMNewStoDetec
The reference key mismatch was found and one of storage is detected
as new(virgin). Data copied from non virgin device to virgin device.
not used
Extra Info
not used
Source ID
0517 TM Reference Key Mismatch
This section describes the Lift error TM Reference Key Mismatch.

Summary
A mismatch between the reference keys is detected and none of the

Description storages is virgin. The elevator is blocked until the fitter enters the
reference key. The controller restores the TMM installation data from
the storage matching the reference key to the other one.
OLD, not used

TM Reference Key Mismatch Detected
TMRefKeyMism
The reference key mismatch is found and none of the storage device is
detected as new (virgin). The controller is waiting for the fitter to enter
reference key on user interface. TMMB service is triggered.
not used
Extra Info
not used
Source ID
0518 TM Mismatch but Same Reference Key
This section describes the Lift error TM Mismatch but Same Reference
Summary Key.
TMM data storage failure – Data mismatched but identical reference

Description key
TMM installation data mismatch is detected but the the reference keys
are indentical. The controller merges the highest stress count value
and the lowest maximum permitted limit in both storages.
OLD, not used:

TM Data Restored
TMDataRestore
After a mismatched of theeSTM data in the redundant storage is
detected, reference key was not found. The controll selected and
copied the highest STM monitoring trip counter value and the lowest
STM monitoring trip limit of the two STM monitoring data storage
devices.
not used
Extra Info
not used
Source ID
0519 TM Undefined Data
This section describes the Lift error TM Undefined Data.

Summary
The TMM installation data are not defined in any storage. The
Description controller is blocked until the fitter enters the installation data.
OLD, not used

TM Undefined Data In Storages
TMUndefData
The STM installation data in both the storages is undefined. TMMB
service is triggered. The fitter must enter STM installation data.
not used
Extra Info
not used
Source ID
0520 Chipcard Missing
This section describes the Lift error Chipcard Missing.

Summary
The backup storage media SDM chip card is missing. The control
Description activates TMMB service.
NEW:
TMM data storage failure – Backup storage missing
The backup storage is missing. The controllers is blocked until the
backup storage is detected.
not used
Extra Info
not used
Source ID
0521 TM Aging Clock Warning
This section describes the Lift error TM Aging Clock Warning.

Summary
An invalid or wrong clock has been detected by the aging time

Description detection monitor at a time more than 1 year before the end of life limit
of the belt
not used
Extra Info
not used
Source ID

Causes and
1 A failure ot the clock used for Set the clock with the actual
Actions
monitoring the aging time of date and time within 7 months
the belt has been detected
0522 TM Aging Clock Error
This section describes the Lift error TM Aging Clock Error.

Summary
An invalid or wrong clock has been detected by the aging time

Description detection monitor at a time not more than 1 year before the end of life
limit of the belt
not used
Extra Info
not used
Source ID

Causes and
1 A failure ot the clock used for Set the clock with the actual
Actions
monitoring the aging time of date and time
the belt has been detected
0523 TM Aging Clock Failure Recovered
This section describes the Lift error TM Aging Clock Failure

Summary Recovered.
An invalid or wrong clock has been recovered

Description
not used
Extra Info
not used
Source ID
0524 PEBO Device Failure
This section describes the Lift error PEBO Device Failure.

Summary
This message is reported in case a internal failure of the PEBO

Description (manual evacuation device) or a communication problem to the PEBO
was detected.The elevator is shut down (FATAL service ) because it is
not allowed to run the elevator with defect manual evacuation means.
PEBO error code

Extra Info 001 (hex 01) = booster overtemperature (T>110 ºC)
010 (hex 02) = pickup undervoltage (Vpk below 90% from rated value)
011 (hex 03) = holding undervoltage (Vhl below 90% from rated value)
100 (hex 04) = RBE, RBE1 or RBE2, RBE3 not OK
101 (hex 05) = undervoltage (pickup or holding) AND overtemperature
110 (hex 06) = RBE, RBE1 or RBE2, RBE3 not OK AND
overtemperature
111 (hex 07) = RBE, RBE1 or RBE2, RBE3 not OK AND undervoltage
(pickup or holding)
PEBO communication failure

Hex 10 = No data can be read from PEBO device. No battery status,
no error code is available.
None
Source ID
0525 TM Data Storage Recovery Successfull
This section describes the Lift error TM Data Storage Recovery

Summary Successfull.
TMM data storage mismatch is successfully restored

Description
1 (hex/dec) data restored from master to backup

Extra Info 2 (hex/dec) data restored from backup to master
3 (hex/dec) master and backup data merged
not used
Source ID
0526 TM Data Storage Recovery Failed
This section describes the Lift error TM Data Storage Recovery Failed.
Summary
TMM data storage mismatch is unsuccessfully restored. The reference

Description key entered does not match any existing ones.
1: data restore failed from master to backup storage

Extra Info 2: data restore failed from backup to master storage
3: failed master and backup data merge
4: reference key does not match master or backup storage
not used
Source ID
0527 PEBO Battery and Device OK
This section describes the Lift error PEBO Battery and Device OK.
Summary
This message is reported in case the manual passenger evacuation

Description device has recovered after a battery low condition or after a internal
device failure.
This message can be reported in case of a PEBO type evacuation
device or in case of a BCM type evacuation device with a external
power battery supply.
none
Extra Info
None
Source ID
0528 SDU Critical Rope Stretch
This section describes the Lift error SDU Critical Rope Stretch.
Summary
Monitoring device of rope stretch (in pit) detects critical rope stretch of
Description suspension ropes. The error is logged with activation of input from
contact KKBA (critical rope stretch at top of tensioning device). Only
applicable for elevators with monitored tensioning device on
compensation ropes.
none
Extra Info
None
Source ID
0529 SDU Inadmissible Rope Stretch
This section describes the Lift error SDU Inadmissible Rope Stretch.
Summary
Monitoring device of rope stretch (in pit) detects inadmissible rope

Description stretch of suspension ropes. The error is logged with activation of
inputs from contacts KBA (Contact inadmissible rope stretch at top of
tensioning device) or contact KUSSA Contact inadmissible rope stretch
at bottom of tensioning device). Only applicable for elevators with
monitored tensioning device on compensation ropes.
none
Extra Info
None
Source ID
0530 Group 24VDC Ok
This section describes the Lift error Group 24VDC Ok.

Summary
The Group 24V supply voltage has established and is within tolerance
Description (24V20%).
none
Extra Info
None
Source ID
0531 Lift 24VDC Ok
This section describes the Lift error Lift 24VDC Ok.

Summary
The Lift 24V supply voltage has established and is within tolerance
Description (24V20%).
None
Extra Info
None
Source ID
0532 12VDC Power Ok
This section describes the Lift error 12VDC Power Ok.

Summary
The internal 12V supply has established and is within tolerance.

Description
None
Extra Info
None
Source ID
0533 Battery Ok and Charged
This section describes the Lift error Battery Ok and Charged.

Summary
The battery test indicates that the battery is Ok and completely

Description charged.
None
Extra Info
None
Source ID
0534 534
This section describes the Lift error 534.

Summary
Description
None
Extra Info
None
Source ID
0535 Group Comm Transmit (Tx) Stress
This section describes the Lift error Group Comm Transmit (Tx) Stress.
Summary
The group communication has reached 100% capacity for several

Description seconds, and VCOM messages are being buffered. Messages from
this lift may be delayed several seconds before reacing their
destination, some services or features may show poor responsiveness.
All messages will still be transmitted correctly.
for R&D use

Extra Info
for R&D use

Source ID
0536 Group Comm Receive (Rx) Overflow
This section describes the Lift error Group Comm Receive (Rx)
Summary Overflow.
The Group Communication receives messages at a higher rate than

Description the hardware and CPU is able to buffer and process them. Messages
have been lost. If critical messages got lost, the system may not
operate correctly.
for R&D use

Extra Info
for R&D use

Source ID
0537 Group Comm Offline
This section describes the Lift error Group Comm Offline.

Summary
The group communication is physically disconnected or no longer

Description active. There is no communication with any other lift at all.
note: Loss of communication with a single lift will generate error '402
VCOM Node Disconnected'. The logging of '402 VCOM Node
Disconnected' is suppressed following this event.
With RS485 group bus the error is logged when there is no token
passing on the bus or no traffic is received at all for several seconds.
Possible causes are:
- The cable is disconnected or wired wrong
- The termination switches are set wrong
- The other lifts are switched off
With Ethernet group bus the error is logged when there are no Link
Monitor Pulses on the ethernet bus or no traffic is received at all for
several seconds. Possible causes are:
- The cable is disconnected or wired wrong,
- The hub/switch is no longer powered,
- All other lifts are switched off
for R&D use

Extra Info
for R&D use

Source ID
0538 TM Installation Data Entered
This section describes the Lift error TM Installation Data Entered.

Summary
This is an information that the TMM installation data has been entered.
Description
Extra Info
not used
Source ID

Causes and
1 The fitter has entered the TMM none
Actions
installation data
0539 TM Stress Count Entered
This section describes the Lift error TM Stress Count Entered.

Summary
This is an information that the TMM stress counter has been manually
Description set with a new stress count value.
Extra Info
not used
Source ID

Causes and
1 The fitter has set the TMM none
Actions
stress count with a new value
0540 Battery Charge Low on AES Device
This section describes the Lift error Battery Charge Low on AES
Summary Device.
Low battery charge or missing battery on AES device (automatic

Description evacuation device).
In this case the AES device / elevator controller is not able to perform a
automatic evacuation in case of mains power fail.
none
Extra Info
None
Source ID

Causes and
1 The battery of the AES device Exchange battery pack.
Actions
is bad (too old or defective).
2 Information signal Check connection and wires.
IAES_BATOK is broken or not IAES_BATOK is a normally
connected to the elevator closed contact.
controller.
0541 Battery OK on AES Device
This section describes the Lift error Battery OK on AES Device.

Summary
This message is reported in case the AES device (automatic

Description evacuation device)has recovered after a battery low condition.
none
Extra Info
None
Source ID
0542 VCOM ID Conflict
This section describes the Lift error VCOM ID Conflict.

Summary
There are several members (lifts) present on the group bus with the
Description same ID setting.
This error can also be reported if the Group Ethernet is connected to a

TCP/IP network, but TCP/IP group communication isn't enabled.
The lifts with conflicting IDs will cease group communication. All other
functionality is unaffected.
8 digit hexadecimal number indicating the internal logical (VCOM)

Extra Info address of the conflicting ID:
11: Lift1
21: Lift2
31: Lift3
41: Lift4
51: Lift5
61: Lift6
71: Lift7
81: Lift8
R&D use only.

Source ID

Causes and
1 More than one lift with the Check the Lift-ID rotary switch
Actions
same Lift Id. number. on the ASILxxx/ASIXxxx of all
lifts in the group. Each lift must
have a unique setting.
0543 Speed Governor Rope Tension LOW
This section describes the Lift error Speed Governor Rope Tension
Summary LOW.
Car speed governor rope tension too low and the switch slack rope
Description speed governor has tripped
none
Extra Info
None
Source ID
0544 EAQ operation activated
This section describes the Lift error EAQ operation activated.

Summary
Earthquake operation has been activated.

Description
None
Extra Info
Source ID
0545 EAQ operation de-activated
This section describes the Lift error EAQ operation de-activated.

Summary
Earthquake operation has been de-activated.

Description
None
Extra Info
Source ID
This section describes the Lift error Traction Media 1 Broken.

Summary
The control detected that the traction media KTMB1 is broken

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID

Summary

Description
Extra Info
not used
Source ID
0556 Building Sway Manual Override
This section describes the Lift error Building Sway Manual Override.
Summary
Building Sway is manually overriden (deactivted by command on

Description embedded user interface)
None
Extra Info
Source ID
0557 KEF input of AES device broken
This section describes the Lift error KEF input of AES device broken.
Summary
The KEF trigger input of AES device (automatic evacuation device) is

Description switched when mains power is still available. This is a unexpected
action and might be due to broken wire of the KEF signal.
none
Extra Info
None
Source ID
0558 OEM Policy Disabled
This section describes the Lift error OEM Policy Disabled.

Summary
OEM policy was disabled by a OEM disabler device.

Description
none
Extra Info
None.
Source ID

Causes and message
Actions
1 None. OEM status None.
information only.
0559 OEM Policy Status Undefined
This section describes the Lift error OEM Policy Status Undefined.
Summary
OEM Policy Status Undefined

Description
Extra Info
None.
Source ID

Causes and message
Actions
1 None. OEM status information None.
only.
0560 OEM Order Data Mismatch for OEM
Never Enable
This section describes the Lift error OEM Order Data Mismatch for
Summary OEM Never Enable.
The current OEM policy status of the elevator controller is 'OEM Never
Description Enable' but order data does not have the 'OEM Never Enable' bit set.
This is a misuse case.
A elevator controller with "OEM Never Enable" status put to a elevator

with order data device which has not "OEM Never Enable" is not
allowed. The elevator must have by definition a order data with "OEM
Never Enable" to prevent uncontrolled OEM policy changes.
none
Extra Info
None.
Source ID

Causes and
1 Wrong OEM order data. Verify that the order data has
Actions
the OEM state "OEM never
enable" set.
2 Corrupted hardware. Replace flash, chipcard and
controller.
0561 Invalid TMM Configuration
This section describes the Lift error Invalid TMM Configuration.

Summary
A configuration related to traction media monitoring feature detected

Description wrong, elevator system is blocked and remains in UNV until
configuration is corrected. Purpose is to avoid using a software without
traction media monitoring function on a elevator where this monitoring
is required. This is applicable only for NA system using ASILOGA3 or
ASILOGT3 board. The software appliess the following conditons for
interlocking:
ASILOGA3 and no TMM configuration in PCT/SCT: Elevator is working

ASILOGT3 and no TMM configuration in PCT/SCT: Elevator remains in
UNV state with Error 0561 "Invalid TMM configuration"
ASILOGT3 and TMM configuration in PCT/SCT: Elevator is working
ASILOGA3 and TMM configuration in PCT/SCT: Elevator remains in
UNV state with Error 0561 "Invalid TMM configuration"
The extra info defines the different faults like wrong hardware
identification, wrong PCT, wrong SCT.
1: wrong PCT: TMM feature is disabled in PCT, but hardware

Extra Info identification says TMM should be enabled.
Action for recovery: Download correct PCT to enable TMM feature.
2: wrong SCT: TMMB service does not present in SCT, but hardware
identification says TMMB service should be present in SCT.
Action for recovery: Download correct SCT having TMMB service to
enable TMM feature.
3: Wrong Hardware identification: Hardware identification does not
support TMM feature, but TMM is enabled in PCT.
Action for recovery: Change the hardware to enable TMM feature.
None.
Source ID

Causes and
1 1: Wrong PCT: TMM feature is Action for recovery: Download
Actions
disabled in PCT, but hardware correct PCT to enable TMM
identification says TMM should feature.
be enabled.
2 2: Wrong SCT: TMMB service Action for recovery: Download
does not present in SCT, but correct SCT having TMMB
hardware identification says service to enable TMM feature.
TMMB service should be
present in SCT.
3 3: Wrong Hardware Action for recovery: Change
identification: Hardware the hardware to enable TMM
identification does not support feature.
TMM feature, but TMM is
enabled in PCT.
0562 Parameter Length Different
This section describes the Lift error Parameter Length Different.

Summary
This error will occur typically while editing parameters where the
Description parameter set telegram contains the parameter length different from
that in the PCT.
0xaabbccdd
Extra Info aa: parameter group of the parameter where the error was discovered.
bb: parameter id of the parameter where the error was discovered.
cc: parameter length of the parameter in the PCT
dd: parameter length of the parameter in the telegram used to edit the
value of the parameter.
Action for recovery: Check the PCT and correct the parameter length,
or contact the development team.
None.
Source ID
0563 Parameter Type Different
This section describes the Lift error Parameter Type Different.

Summary
This error will occur typically while editing parameters where the
Description parameter set telegram contains the parameter type different from that
in the PCT.
0xaabbccdd
Extra Info aa: parameter group of the parameter where the error was discovered.
bb: parameter id of the parameter where the error was discovered.
cc: parameter type of the parameter in the PCT
dd: parameter type of the parameter in the telegram used to edit the
value of the parameter.
Action for recovery: Check the PCT and correct the parameter type, or
contact the development team.
None.
Source ID
0564 OEM Policy Status Disabled
This section describes the Lift error OEM Policy Status Disabled.
Summary
OEM Policy Status Disabled

Description
Extra Info
None.
Source ID

Causes and message
Actions
1 None. OEM status None.
information only.
0565 OEM Policy Status Enabled Not Active
This section describes the Lift error OEM Policy Status Enabled Not
Summary Active.
OEM Policy Status Enabled Not Active

Description
Extra Info
None.
Source ID

Causes and
Actions
only.
0566 OEM Policy Status Enabled Active
This section describes the Lift error OEM Policy Status Enabled Active.
Summary
OEM Policy Status Enabled Active

Description
Extra Info
None.
Source ID

Causes and
Actions
only.
0567 OEM Policy Status Never Enable
This section describes the Lift error OEM Policy Status Never Enable.
Summary
OEM Policy Status Never Enable

Description
Extra Info
None.
Source ID

Causes and
Actions
only.
0599 LC_MAX_Errors_LC
This section describes the Lift error LC_MAX_Errors_LC.

Summary
Description
Extra Info
Source ID
0600 Attempt to start not allowed
This section describes the MC PVF error Attempt to start not allowed.
Summary
This error can onlybe detected atthe start of the 1st trip and usually
Description occurs when 1 or more fatal errors were detected during either the
stand-still or boot-phase.
None.
Extra Info
None.
Source ID

Causes and
1 One of more of the following Check the corresponding error
Actions
errors were detected: 626, description.
627, 629, 630.
0601 Attempt to restart not allowed
This section describes the MC PVF error Attempt to restart not

Summary allowed.
This error can occur at the start of any trip and indicates that a fatal
Description error has already been detected and stored.
None.
Extra Info
None.
Source ID

Causes and
1 Fatal error Check fatal error in log.
Actions
0602 Overtemperature
This section describes the MC PVF error Overtemperature.

Summary
Overtemperature check has detected power transistorsoverheated.

Description When the car is at standstill, it will be blocked. If the car is in motion,
the trip is completed, as if it remains in motion for over 30 sec,
emergency stop is generated.
None.
Extra Info
None.
Source ID

Causes and
1 Overtemperature on the Check power transistors.
Actions
Inverter's heat sink.
2 Wrong wiring of the input Check wiring of the input signal
signal KTHVF KTHVF (X5.3)
3 Variodyn 35, 45, 70, 100/BR: Check brake chopper and
Malfunction of the Brake brake resistor
Chopper, Brake Resistor.
0603 SW warning
This section describes the MC PVF error SW warning.

Summary
Software error detected and stored in logs.

Description
None.
Extra Info
None.
Source ID

Causes and
1 Absolutely wrong parameters Check parameters
Actions
2 Wrong program logic, run-time Contact Ebikon, dept.
failures R&D-DR.
0604 DL overvolt trigg
This section describes the MC PVF error DL overvolt trigg.

Summary
DC link overvoltage detected if > 730 V. Checked at start and every 10

Description ms during the trip by software.
None.
Extra Info
None.
Source ID

Causes and
1 Variodyn 35, 45, 70, 100/BR: Check Board TBR (VF70-94),
Actions
Malfunction of the Brake brake chopper Skiip module
Chopper, Brake Resistor. (VF35, 45, 70-95, 100/BR)
2 Screws of the brake chopper Check screws of the brake
badly tighten. chopper (IGBT).
3 Variodyn 100/140/220 has its Ignore
own control circuits and this
monitoring function is
redundant.
0605 DL overvolt
This section describes the MC PVF error DL overvolt.

Summary
DC link voltage is higher than the upper limit. Could be preceded by

Description error 604. Can also be produced by Charge and Test DC link functions
with CADI. During trip this upper limit is given by the inverter parameter
udcl_upp_lim. During stand still this upper limit is given by the inverter
parameter udcl_upp_lim multiplied by 0.94.
This control function is slower than the overvoltage trigger, normally
error 604 occurs first.
None.
Extra Info
None.
Source ID

Causes and
1 See errror 604
Actions
2 Bad parameter Check parameter udcl_upp_lim
0606 DC link undervoltage
This section describes the MC PVF error DC link undervoltage.

Summary
1.) DC link voltage below lower limit. During trip an error is produced.
Description At stand still, only a warning is produced and the contactor SGR
opens.
2.) VF 35, 45, 70, 100/BR: may be produced by current loop or
capacitor pulse forming test with CADI.
This lower limit is given by the inverter parameter udcl_low_lim.
None.
Extra Info
None.
Source ID

Causes and
1 The charge- or input-contactor Check contactors and
Actions
is bad, or wrong parameters parameters
("t_char_on / off", "t_inp_on /
off"), in which case error 606 is
combined with error 635, 608,
612 or 613 (VF35 - 100/BR
only).
2 DC link or main supply Check mains and fuses
malfunction. The parameter
t_dcl, time for charging DC link
is too short.
3 Bad parameter Check parameter udcl_low_lim
0607 Control Hardware command wrong
This section describes the MC PVF error Control Hardware command

Summary wrong.
Internal SW monitoring function. Has nothing to do with physical HW

Description states and should never occur.
None.
Extra Info
None.
Source ID

Causes and
Actions
failures R&D-DR.
0608 Charging DC link failure
This section describes the MC PVF error Charging DC link failure.

Summary
Occurs if the DC link cannot be charged at the beginning of a trip or

Description during a test function.
None.
Extra Info
None.
Source ID

Causes and
1 Input contactor or charge Check input or charge
Actions
contactor malfunction, in which contactors (SGRW, SGR, see
case this error appears warning log).
together with warning 612 or
613.
2 Check coul of contactors.
3 Wrong feedback from one of Check auxiliary contacts and
these contactors, in which wiring (PVF X4.10, X4.11).
case this error appears
together with warning 612 or
613.
4 Converter power supply Check converter power supply.
problems, in which case this
error appears together with
error 606
5 New AEG inverter (one
contactor), parallel inverter
(with AEG): front end converter
could not be switched on,
check converter and contacts
RSK, RSK1
6 New AEG inverter (one It is possible, that after an
contactor), parallel inverter emercency stop Travel Control
(with AEG): Bad tries to start a new trip while K2
synchronisation with Travel is open, so the dc link could
Control, Error 608 as a not be charged.
consequence of an other error
7 Check previous errors, check
Travel Control local event log if
any Travel Control error
occurred.
8 Parallel inverter with Schindler Check input or charge
converter: Input or charge contactors of the parallel
contactor malfunction, in which converter (SGRWx, SGRx, see
case this error appears warning log), check auxiliary
together with warning 644 or contacts and wiring (PCC X3.2,
645 ( 651 or 652 / 658 or 659). X3.4, ...).
9 Wrong PVF parameters, See error 606 (first cause)
concerning input- and load-
contactor timing.
0609 Discharging DC link failure
This section describes the MC PVF error Discharging DC link failure.

Summary
This failure may occur during "Test current loop" and "Test DC link"
Description functions started from CADI. The command to switch-off both charge-
and input-contactors is issued but the DC link voltage does not
decrease.With Variodyn 100, 140, 220 this error will always occur,
because the DC link and contactors are not under control of the PVF
board.
None.
Extra Info
None.
Source ID

Causes and
1 Input contactor or charge Check input and charge
Actions
contactor malfunction, in which contactors SGRW, SGR.
case this error appears
together with error 612 or 613.
2 Wrong feedback from one of Check auxiliary contacts on
these contactors. SGRW, SGR
0610 Current loop not OK
This section describes the MC PVF error Current loop not OK.
Summary
1.) Feedback from LEMs missing (point a).

Description 2.) VF 35, 45, 70, 100/BR only: CADI test loop function detects
difference between IST and REF outside tolerance (point b to f).
None.
Extra Info
None.
Source ID

Causes and
1 The feedback cable X1 bad or Check feedback cable X1.
Actions
not connected in its socket.
2 Interruption in the current
loop,any of the components:
power IGBTs, motor supply in
cables, motor wiring. LEM
malfunction or wrong
installation.
3 The shortcut circuit monitor
system at the driver board has
triggered.
4 Wrong current measurement Check board, see CADI PVF
resistors on PVF. Help under Current Measuring
Resistors
5 Wrong PVF parameters "Is Check parameters
ADC12 res" or/and "Is ADC8
res".
6 The cable X6, link from PVF to
the driver boards, bad or
wrong wired.
0611 Deactivate current loop failure
This section describes the MC PVF error Deactivate current loop

Summary failure.
1.) Current value not zero at end of trip or during standstill (higher than
Description 1% of A/D range).
2.) Current value of parallel converter not zero at end of trip or during
standstill.
None.
Extra Info
None.
Source ID

Causes and
1 Contactor SH and /or Check contactor SH and
Actions
frequency converter failure Frequency converter
2 Interferences, bad shielding of Check shielding of the LEM
theLEM converter cable cable
3 Faulty LEM converter Check voltage (LEM pin M to
ground ) during stand still. If
the value is not about zero,
replace LEM converter.
4 Parallel converter connected: Check warning log if one of
Err 11 as a consequence of these errors has occurred,
warning 47/55/63 during stand check parallel converter (same
still. procedure as above).
0612 Input contactor failure
This section describes the MC PVF error Input contactor failure.

Summary
1.) Input contactor (SGR, is equivalent to K16 in new AEG inverters

Description with onlyone contactor) not responding to switch on / off signal.
2.) Input contactor (SGR, is equivalent to K16 in new AEG inverters)
opens during trip.
None.
Extra Info
None.
Source ID

Causes and
1 Input contactor failure Check contactor coil (SGR)
Actions
(Variodyn 35, 45, 70, 100/BR,
280 only)
2 Input relay failure (Variodyn Check contactor coil (K16)
100, 140, 220 with one
contactor)
3 Wrongfeedback: X3.4 and/or Check auxiliary contacts and
X4.10 wrong wiring. wiring.
4 If SGR coil is connected on Check UKE2 error LEDs.
UKE2 board (UKE2 X4.8):
UKE2 detects an error and
cuts off the SGR supply.
5 Check signal VSGR
(connection PVF X3.4 - UKE2
X4.9)
6 If the contactor SGR does not
open after a switch off
command, this error
isgenerated and the error state
is set to fatal, independent of
the error filter (for EN81, from
PVF SW version 4.20 on).
0613 Charge contactor failure
This section describes the MC PVF error Charge contactor failure.

Summary
Charge contactor (SGRW) not responding to switch on / off signal.

Description
None.
Extra Info
None.
Source ID

Causes and
1 Charge contactor failure Check contactor coil
Actions
(Variodyn 35 - 100/BR only)
2 Wrong feedback. X3.3 and/or Check auxiliary contacts and
X4.11 wrong wiring. wiring
3 Wrong parameters (t_char_on Check parameters t_char_on /
/ off are too small) off
0614 Current difference warning
This section describes the MC PVF error Current difference warning.

Summary
During a trip, one of the current components Is Alpha or Is Beta,

Description calculated from the actual current values Iu, Iv and Iw,differs from its
reference value more than is_diff_limit. The bang-bang controller is not
able to follow its reference values.
None.
Extra Info
None.
Source ID

Causes and
1 Interrupted IGBT driver signals Check error LEDs on the
Actions
due to any monitoring function: UKE2 board *)
2 VF 35, 45, 70-95, 100/BR,
FCR: UKE2 board detects an
error and cuts off the IGBT
driver signals.
3 VF 100, 140, 220: PWR board Check error LEDs on the PWR
detects an error (e.g. bad front board *)
end converter, overcurrent or
overvoltage) and cuts off the
IGBT driver signals.
4 [This occurs only, if the
external monitoring function
(PVF X4.5 connected) is not
enabled (see under elevator
parameter Inv_Model).]
5 faulty PWR or UKE2 board Replace board
6 Interrupted current loop: IGBT Check IGBTs
short circuit.
7 VF 70-94: check the supply
LEDs on the VL board if they
are off. *)
8 The current controller reaches Check LEM wiring connections
its limits, too much current
needed.
9 Bad NGL supply due to VF 70-94: check 24V supply
interferences. for VL board (X3 pin 7, has to
be higher than 19V) with an
oscilloscope.
10 Wrong PVF parameters Check motor and inverter
parameters
11 Feed from LEMs missing Check LEM wiring connection
12 If parallel converter connected: See warning log, if warning 47
Failure of one of these / 55 / 63 stored, check parallel
converters could produce an converter.
E14, normally only a warning
14 is produced.
13 Speed to high (Travel Control Reduce speed till the max.
motion parameter V4) fequency of the motor
(revolutions) is equal fs_nom
divided by number of pole
pairs.
14 *) After a non fatal error on
PVF, the PVF does a reset to
erase some errors on the
external unit (PWR or UKE2).
So the error LEDs on this
board go out and you can not
see the cause for the error. To
prevent the reset, you have to
change the PVF error filter 14,
fifth column (errorfilters,
max_nmb), from 3 to 1 (CADI
motor control / log /local / fail
filters... filter now: 213 4 1 1 7).
In this case, each error 14 is
fatal, no reset occurs and the
PVF is blocked. If the cause for
error 14 is the
externalunit,atleast one error
LED on this board (or on the
AEG current inverter, board
A101) should light. After
checking thecause of the error
14, you have to reset theerror
filter 14 to the previous value
3,otherwise each error 14
blocks the elevator constantly
!!
15 Unfortunately with the Travel
Control SW older than V7.00 it
is not possible to change the
PVF error filters with CADI,
because there is a
compatibility problem. In this
case the reset of the external
devicecan be prevented as
follow: Remove the cable from
PVFX2pin6 (it is not soeasy)
and connect this cable to
ground (e.g. PVF X4 pin 4). So
the board UVVF or UKE2 is
not reset during a PVF reset. If
there is an old VF 70-94,
remove the cable from PVF X3
pin 7 and connect it to X3 pin
6. So there is no reset on the
VL board.
16 All this applies also to other
errors, like error 641, 650, 658,
666. In this case, the
corresponding error filter has
to be changed.
0615 SW encoder warning
This section describes the MC PVF error SW encoder warning.

Summary
Software detects no movement of motor. During a trip, the speed

Description reference value is higher than the tolerance limit (0.12 m/s) and current
speed calculated from the rotor angle increments is equal to zero.
None.
Extra Info
None.
Source ID

Causes and
1 Themotor is blocked, Check adjustment of brake.
Actions
mechanical brake is closed or
opens too slowly.
2 Speed controller is too slow Check control parameters
(p_gain_speed, ti_speed) and
elevator parameters (gear_rat,
trac_dia, inertias is too small)
3 The motion of the car is
blocked
4 The V-tacho opto-electronic Check V-tacho (IG).
bad or tacho disc is slipping.
0616 Over current warning
This section describes the MC PVF error Over current warning.

Summary
Over current detected during the constant speed phase of a trip. The
Description max. allowed value = is_nom x over_current_fact.
None.
Extra Info
None.
Source ID

Causes and
1 The motor consumes to much Check machine and
Actions
electrical energy: the motor mechanical brake.
brake does not open properly;
the car is overloaded; wrong
counterweight or car
balancing.
2 Check if car & counter
weight are balanced.
3 Wrong PVF parameters Readjust PVF parameters.
4 Wrong motor tacho polarity. Check motor tacho polarity
This error could occur during (PVF X9),exchange wire X9.2
intallation travel, when the and X9.3 if necessary
speed is very slow (error 18 is
not detected, not enough
distance in the wrong
direction).
0617 Over speed warning
This section describes the MC PVF error Over speed warning.

Summary
1.) Car moves more than 20 cm during standstill

Description 2.) Overspeed detected during PVF test trip (DRE_D or DRE_U
active). Note: This monitoring function is inactive during normal
operation, i.e. if PVF is running together with an interface board (Travel
Control).
None.
Extra Info
None.
Source ID

Causes and
1 The brake is faulty. Check the brake.
Actions
2 Overspeed during trip: Must Check if no test trip was
not occur in normal performed.
installations.
0618 Start direction wrong
This section describes the MC PVF error Start direction wrong.

Summary
Car moves in wrong direction. At the beginning of a trip, the signs of

Description speed reference value and actual speed value are different. The
elapsed distance in the wrong direction becomes longer than the
supervisor parameter dist_diff_limit.
None.
Extra Info
None.
Source ID

Causes and
1 The motor leads-in or motor- Check motor direction
Actions
tacho wrongly wired.
2 Check wiring PVF X9
3 Wrong Load data. Check Load Measurment
system.
4 The car is overloaded. Check car load.
5 Speed controller is too slow Check control parameters and
elevator parameters (gear_rat,
trac_dia).
6 Wrong counterweight or Check if car is balanced.
balance
0619 Speed reference warning
This section describes the MC PVF error Speed reference warning.

Summary
1.) After field exciting phase and max. time delay (0.55 sec.), the
Description telegram carrying speed reference value from the interface board does
not come.
2.) During any other trip phase, the telegram carrying speed reference
value from the interface board does not come for at least once within
20 ms.
None.
Extra Info
None.
Source ID

Causes and
1 Lost of communication. Check connection to Travel
Actions
Control board.
2 Problem with the interface Check Travel Control board
board. local event log, if any error or
reset has been performed
during trip.
0620 Time control motor exceeded
This section describes the MC PVF error Time control motor

Summary exceeded.
Software programme loop time exceeded. Should never happen.

Description
None.
Extra Info
None.
Source ID

Causes and
1 Run-time problems. Contact Ebikon, dept.
Actions
R&D-DR.
0621 Receive uart failure
This section describes the MC PVF error Receive uart failure.

Summary
Error detected in UART (parity or overrun or framing error). PVF stops

Description receiving the telegram and wait for a new telegram. The remaining
bytes of the old telegram produce error 622.
None.
Extra Info
None.
Source ID

Causes and
1 Communication disturbance or Check communication between
Actions
interference. PVF & Travel Control.
2 Check for interference.
3 Bad UART. Change PVF board if persists.
0622 Message source failure
This section describes the MC PVF error Message source failure.

Summary
PVF gets a telegram with unknown first byte (destination). Can be

Description produced if telegram data length does not correspond with header
length. Comes in combination with 621. Communication lost.
None.
Extra Info
None.
Source ID

Causes and
1 See error 621.
Actions
0623 Message length failure
This section describes the MC PVF error Message length failure.

Summary
Received header length is bigger than 12. PVF stops receiving the
Description telegram and wait for a new telegram. Comes in combination with error
621.
None.
Extra Info
None.
Source ID

Causes and
1 See error 621.
Actions
0624 Receive state wrong
This section describes the MC PVF error Receive state wrong.

Summary
SW monitoring detects communication failure. Should never occure.

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
failures. R&D-DR.
0625 Transmit state wrong
This section describes the MC PVF error Transmit state wrong.

Summary
Software monitoring detects communication failure. Should never

Description occure.
None.
Extra Info
None.
Source ID

Causes and
Actions
failures. R&D-DR.
0626 EPROM checksum failure
This section describes the MC PVF error EPROM checksum failure.

Summary
A checksum over the contents of the EPROM address space is

Description calculated during the first boot of the system and saved in the static
part of the RAM. After each reset and after each trip, there is a new
checksum calculation and comparison with the saved one. If they do
not match, this warning is generated. By default this produces a fatal
failure, because it means that the contents of the EPROMs have been
changed.
None.
Extra Info
None.
Source ID

Causes and
1 The previous contents of the Empty RAM (Check
Actions
RAM are not deleted before instruction).
exchanging EPROMs.
2 Remove jumper from PRUM
board for 30 secs or remove
the two RAM (IC 76, 77) for 10
sec (new PRUM board with
capacitor)
3 EPROM or RAM failure. Change the software.
4 Change RAM or board.
0627 RAM failure
This section describes the MC PVF error RAM failure.

Summary
After each reset of the system and after each trip, the whole RAM
Description address space is checked for consistency of the read and write
operation. Fault in RAM detected.
None.
Extra Info
None.
Source ID

Causes and
1 RAM failure. Change RAM or board.
Actions
0628 Board battery failure
This section describes the MC PVF error Board battery failure.

Summary
After each reset and after eachtrip, the reliability of the system battery
Description (capacitor) is approved.If this failure occurs, the battery (capacitor)
should be exchanged as soon as possible, because with the power-off,
all data from RAM will be deleted.
None.
Extra Info
None.
Source ID

Causes and
1 Old or too long operated Replace battery or capacitor.
Actions
battery.
2 Check date on battery.
3 Wrong mounting or handling Check connections on PRUM
board.
4 Discharged through bad
packaging material.
0629 RAM checksum failure
This section describes the MC PVF error RAM checksum failure.

Summary
A checksum over the parameter range of the RAM address space is

Description calculated duringthe first boot of the system and after each parameter
change, and saved in the static part of the RAM. After each reset and
after each trip, there is a new checksum calculation and comparison
with the saved one. If they do not match, this warning is generated. By
default this produces a fatal failure, becauseit means that the contents
of the static part of the RAM have been changed out of control.
None.
Extra Info
None.
Source ID

Causes and
1 The previous contents of the Empty RAM (as before).
Actions
RAM are not deleted before
exchanging EPROMs.
2 RAM failure. Change RAM or board.
0630 Watchdog failure
This section describes the MC PVF error Watchdog failure.

Summary
At the beginning of the first system boot, the functionality of the HW

Description Watchdog is proved.
None.
Extra Info
None.
Source ID

Causes and
1 Watchdog IC failure or wrong Change board.
Actions
mounting
0631 Transmit failure
This section describes the MC PVF error Transmit failure.

Summary
At least one byte to send is waiting to be sent. The interrupt is

Description activated but RTS (Ready-to-send) status of the communication UART
is not set (e.g. Travel Control performs a reset at that moment and
could not communicate). After 1 sec warning 31 is produced.
None.
Extra Info
None.
Source ID

Causes and
1 The communication line is Check communication cable
Actions
blocked. (X8)
2 Disturbance or interference. Check shielding
3 Travel Control not responding. Could happen if Travel Control
perfomes a reset while PVF
wants to send a byte.
4 Bad UART Change board
0632 Open safety circuit
This section describes the MC PVF error Open safety circuit.

Summary
1.) After receiving a start command from the interface board, the state
Description of motor contactor SH1 (VF 70-94) or K3 (old VF 100, 140) is proved.
If it is de energised, this error is generated. AEG with only one
contactor (K2) or Variodyn with UKE2 board (VF 35, 45, 70-95,
100/BR): Feedback RSK and RSK1 is proved. Parallel Operation:
Feedback RSK, RSK1 (Mic V: RH, RH1) and K2 of the slave (cabinet
AS3) is proved.
2.) During test function "check current loop", started from CADI motor
contactors must be closed. If they are not, the current loop is open and
the test is finished by issuing this error.
3.) During a trip, if the motor contactors open for the period of time
shorter than 10 ms, and close again, a warning (no error) is issued to
suggest that the PVF controller may get problems to follow reference
current values. The trip is finished andstopsimmediately. Subsequent
warning or error may be error 614. If the motor contactors become
open during a trip, and stay open for longer then 10 ms, no warning
and no error is generated. The PVF assumesthat such a trip is finished
and stops immediately. This is usual situation for the montage or
inspection trip.
None.
Extra Info
None.
Source ID

Causes and
1 At the beginning of a trip, Check safety chain
Actions
motor contactors are switched
off before PVF gets stop
command, after the start
command is already received:
the car or shaft door contacts,
or any other component in the
safety chain is not stable.
2 Bad TOPT (only VF 70-94 and Replace TOPT
old VF 100, 140).
3 Bad relay RSK or RSK1 Check feedback of relay RSK
(feedback) and RSK1
4 Wrong feedback wiring. Check PVF input X4.6
5 Bad supply of the motor Check supply of SH, SH1 (SF),
contactors. (K2)
0633 HW encoder warning
This section describes the MC PVF error HW encoder warning.

Summary
Motor tacho warning: The signals A, A-, B, B- from the motor tacho are
Description proved by the PVF HW during stand still and during trip. If a failure is
detected at trip start, an error is generated and the start is not allowed.
During a trip, each time the failure is detected a warning is generated.
In such case, the consecutive warning may be error 614.
None.
Extra Info
None.
Source ID

Causes and
1 Bad tacho electronic or tacho Check motor tacho, cable and
Actions
cable (connector is not connectors (PVF X9 and/or IG
inserted properly or damaged connector).
cable)
2 Disturbance or interference. Check tacho shielding.
3 Mechanical vibrations of the
tacho plate at the beginning
and the end of a trip.
0634 Exception vector
This section describes the MC PVF error Exception vector.

Summary
The PVF processor detects an internal fault (e.g. division by zero).

Description After this error is generated, the CPU peripheral is reset (means reset
on PVF board). The Id, type ot the exception, date, time, trip number,
etc. and the contents of all CPU registers are saved in the CPU Status
Log. Date, time, trip number, etc. are saved as usual in the Error Log
too. For diagnostics, the PVF "CPU Status Log" & "CPU Staus
Counters" should be used as well as "Warning & Error Logs" and
"Warning & Error Counters". Normally this error should not occur.
None.
Extra Info
None.
Source ID

Causes and
1 Absolutely wrong parameters Check PVF parameters.
Actions
2 Check PVF CPU status log: If
the event zero divide is stored,
some parameters must be
wrong.
3 RAM not properly deleted after Remove the two RAM (IC 76,
a change ot the software. 77) at least for 10 sec. This is
absolutely necessary, if the
PVF SW (EPROMs) has been
changed.
4 CPU or peripherals failure. Disturbance or interference.
Change PVF board.
5 Bad power supply (5V) Check UVVF or UKE2.
6 Software problem If it is not possible to resolve
the problem using the actions
described above, contact
Ebikon, dept. R&D-DR.
0635 Contactor time exceeded
This section describes the MC PVF error Contactor time exceeded.

Summary
During each switching on or off of the charge- and/or input-contactor,

Description their logical states are controlled by the monitoring function. If any of
these states is not defined for longer than 10 Sec. this warning will be
generated. Same as before.
None.
Extra Info
None.
Source ID

Causes and
1 Bad set of PVF parameters: Set these parameters to the
Actions
"t_char on / off", "t inp on / off" default value (0.2 sec.).
(higher than 10 sec.)
0636 Driver Print power failure
This section describes the MC PVF error Driver Print power failure.
Summary
During the bootcycle of the SW, a signal is set to the power-supply

Description board (UVVF) to switch-on the relay for the power supply of the driver
board. If there is a short circuit on the driver board (VF100, 140,
220:PWR board), the PVF supply (UVVF) breaks down and the PVFis
reset, the boot-cycle is started again. If this happens max. number of
retries (currently 3) in arow, this error will be generated. If this failure is
generated with the Variodyn 70-94, it may bea by-product of other
power-supply problems.
None.
Extra Info
None.
Source ID

Causes and
1 Bad power-supply board or Check UVVF or UKE2 ( VF35,
Actions
wiring. 45 ,70-95, 100/BR) board.
2 Bad driver board or wiring. Check wiring and supply of
PWR board (VF100, 140, 220)
0637 Overtemperature brake resistor
This section describes the MC PVF error Overtemperature brake

Summary resistor.
Overtemperature check has detected brake resistors overheated.

Description When lift is at standstill (and call is given) it will be blocked, if in motion
trip will be completed. If it remains in motion for over than 30 sec. an
emergency stop follows.
None.
Extra Info
None.
Source ID

Causes and
1 Variodyn 35, 45,70, 100/BR: Check brake chopper and
Actions
Overtemperature on the brake resistor
Inverter's brake resistor.
Malfunction of the Brake
Chopper, Brake Resistor.
2 Wrong wiring of the input Check connection of the signal
signal X4.9. KTHBR.
0638 FCR no start
This section describes the MC PVF error FCR no start.

Summary
After a trip command, the PVF enables the FCR. If it does not start,
Description this error will be generated. Only active, if elevator parameter
Inverter_Model is set to 15 (FCR).
None.
Extra Info
None.
Source ID

Causes and
1 No internal FCRclearance due Check FCR error log
Actions
to undervoltage (mains), Skiip
failure, ...
2 Bad input wiring Check wiring connections PVF
X4.5 (input)
3 Bad output wiring Check wiring connections PVF
X3.7
0639 FCR no stop
This section describes the MC PVF error FCR no stop.

Summary
One minute after trip stop or after disconnecting the DC link, PVF
Description disables the FCR. If it does not stop, this error will be generated. Only
active, if elevator parameter Inverter_Model is set to 15 (FCR).
None.
Extra Info
None.
Source ID

Causes and
1 FCR problems Check FCR
Actions
X4.5 (input)
3 Bad output wiring Check wiring connections PVF
X3.7
0640 FCR interrupt
This section describes the MC PVF error FCR interrupt.

Summary
During trip, FCR stops running (cause see FCR error log). Only active,
Description if elevator parameter Inverter_Model is set to 15 (FCR).
None.
Extra Info
None.
Source ID

Causes and
1 Bad mains, FCR overtemp, ... Check FCR error log
Actions
X4.5
0641 External error
This section describes the MC PVF error External error.

Summary
This error occurs, if the input EXTERNAL_OPERATION (previous

Description name RESERVE2; PVF X4.5) is not on high level (high level = higher
than 9 V). If PFV elevator parameter Inverter_Model is set to 11 (AEG
NEW MONITOR),20 (MONITOR EXTERNAL DEVICE) or to any
parallel operation, this input is checked at trip start and during trip,
otherwise it is not checked. This input represents the current state of
an external device.
PVFP board: X4.5 internally connected with X5.8. Itis possible to use
this improved error handling (reduced appearance of error614) for all
Variodyns with AEG converter and PVF board.Connect PVF X4.5 to
X5.8 (solder a wire on the back of the board) and set the parameter
inverter_model to 20 (old VF100, 140) or to 11 (new VF100, 140, 220
with onecontactor). In case of the one contactor inverter, the resistor
R184 on the PWR board mustbereplaced by a new one with the
value100 kOhm.
None.
Extra Info
None.
Source ID

Causes and
1 External device detects anerror Check error LEDs on external
Actions
device (normally UKE2 or
PWR board) *)
2 Safety circuit opens during trip Check Travel Control event
(produces normally 1 warning) log, if there are safety circuit
problems, compare times
3 Bad input wiring Check wiring connections (PVF
X4.5 or PVFP X5.8)
4 Note: VF 35, 45, 70-95,
100/BR, 280: external device =
UKE2 boardVF 100, 140, 220:
external device = PWR board
5 *) More information about how
to check the error LEDs, see
under error 614 !
0642 PCC failure
This section describes the MC PVF error PCC failure.

Summary
One or more of the three parallel controllers on the PCC board are not
Description enabled (CC1: bridge 9 on the PCC board) and the PVF elevator
parameter Inverter_Model is set to parallel operation. Checked at trip
start.
None.
Extra Info
None.
Source ID

Causes and
1 Parallel controller not enabled Check bridges on PCC board
Actions
2 Wrong PVF parameter Check elevator para
Inverter_model
This section describes the MC PVF error Supply failure cc1.

Summary
The internal 5V supply of the controller CC1 is smaller than 4.5V.

Description Checked at tip start and during trip.
None.
Extra Info
None.
Source ID

Causes and
1 24V supply faulty or bad wiring Check 24V input (PCC X1.2)
Actions
2 DC-DC converter on PCC Replace PCC board.
board is faulty
This section describes the MC PVF error Input contactor failure cc1.
Summary
Input contactor of the parallel converter (1_SGR) not responding to

Description switch on or switch off signal.
That applies only to the parallel operation with Schindler converters(VF
280).If there is Parallel operationwith AEG converters(VF 140 / 220),
the contactor feedback is not connected and this error should never
occur (except PVF elevator paraInverter_Model is wrong).
None.
Extra Info
None.
Source ID

Causes and
1 Input contactor failure Check contactor coil
Actions
2 Wrong feedback Check auxiliary contacts and
wiring PCC X3.2
3 Wrong wiring, no driver signal Check driver signal VSGR on
PVFP X3.4
This section describes the MC PVF error Charge contactor failure cc1.
Summary
Charge contactor of the parallel converter (1_SGRW) not responding

Description to switch on or switch off signal.
That applies only to the parallel operation with Schindler converters

(VF 280). If there is Parallel operation with AEG converters (VF 140 /
220), the contactor feedback is not connected and this error should
never occur (except PVF elevator paraInverter_Model is wrong).
None.
Extra Info
None.
Source ID

Causes and
Actions
wiring PCC X3.4
3 Wrong wiring, no driver signal Check driver signal VSGRW
on PVFP X3.3
This section describes the MC PVF error DL overvolt trigg cc1.

Summary
DC link overvoltage CC1 detected if > 730 V. Checked during stand

Description still, at trip start and every 10 ms during the trip by software.
None.
Extra Info
None.
Source ID

Causes and
1 Variodyn 280 (Schindler): Check FCR
Actions
Malfunction of the front end
converter (FCR)
2 Variodyn 100/140/220 (AEG) Ignore
has its own control circuits and
this monitoring function is
redundant.
3 Interferences or bad voltage Measure voltage between PCC
measurement X3.9 and X3.10. Should be
UDCL/100
This section describes the MC PVF error Current difference warn cc1.
Summary
1) Current difference on CC1 controller between actual and reference

Description detected during trip.
2) Current value CC1 not zero during stand still (produces warning
followed by error 11)
None.
Extra Info
None.
Source ID

Causes and
1 Interrupted current loop on Check IGBT, check error LEDs
Actions
CC1: IGBT short circuit on PWR board (only AEG
(Variodyn 280) or any other converter, VF 140 / 220)
monitoring function (Variodyn
100/140/220: overcurr.
overvolt, etc.) activated.
its limits, too much current CC1
needed.
3 Wrong PVFP parameters Check parameters
4 Current difference error stored Check error log, if error
on PCC board during stand detected at the trip phase
still (e.g. caused by EXCITING_FIELD.
interferences), detected at trip
start
5 Then check PCC board
6 PVFP does not detect an Check Travel Control event log
opened safety circuit and tries if there are safety circuit
to run. problems
7 Bad contactor K2 Check contactor K2
8 Feed from LEMs of converter Check LEM wiring connection
CC1 missing CC1
the LEM converter cable cable
10 Motor cables mixed up Check motor cable wiring
11 Current value not zero during Check contactor K2 and
stand still (e.g. interferences) Frequency converter
12 Warning as a consequence of See warning log
error 46/54/62 or 48/56/64 or
50
This section describes the MC PVF error Current loop failure cc1.
Summary
Feedback from the LEMs of converter CC1 missing.

Description
None.
Extra Info
None.
Source ID

Causes and
1 The feedback cable X2 on
Actions
PCC board is bad or not
connected in its socket.
This section describes the MC PVF error Overtemperature cc1.

Summary
Over temperature check has detected power transistors on converter

Description CC1 overheated. When the lift is at standstill, it will be blocked, if itis in
motion, the trip will be completed. If it remains in motion for over 30
sec, an emergency stop will be generated.
None.
Extra Info
None.
Source ID

Causes and
1 Overtemperature on the heat Check power transistors.
Actions
sink of inverter CC1.
signal 1_KTHVF PCC X3.6)
This section describes the MC PVF error External error cc1.

Summary
This error occurs, if the input X3.1 (1_READY) on the PCC board is
Description noton high level (high level = higher than 9 V). This input represents
the current state of the converter CC1. Checked at trip start and during
trip.
None.
Extra Info
None.
Source ID

Causes and
1 Converter CC1 detects an Check converter CC1 (AEG
Actions
error converter: see error LEDs on
PWR board)
3 Bad input wiring Check wiring connections
(PCC X3.1 or PWR X102.6)
4 Note: Parallel operation with
AEG converter: Check error
LEDs on PWR board Parallel
operation with Schindler
converter: Check error LEDs
on UKE2 board
5 More information about how to
check the error LEDs, see
under error 614 !

Summary

None.
Extra Info
None.
Source ID

Causes and
Actions
board is faulty
Summary

(VF 280). If there is Paralleloperationwith AEG converters (VF 140 /
220), the contactor feedback is not connected and this error should
never occur (except PVF elevator para Inverter_Model is wrong).
None.
Extra Info
None.
Source ID

Causes and
Actions
wiring PCC X?.?
PVFP X3.4
Summary

(VF 280). If there is Parallel operation with AEG converters (VF 140
/220), the contactor feedback is not connected and this error should
None.
Extra Info
None.
Source ID

Causes and
Actions
wiring PCC X?.?
PVFP X3.3

Summary

Description still, at trip start and every 10 ms during the tripby software.
None.
Extra Info
None.
Source ID

Causes and
1 Variodyn 280 (Schindler): Check FCR
Actions
converter (FCR)
redundant.
measurement X?.? and X?.?.
4 Should be UDCL/100
Summary

None.
Extra Info
None.
Source ID

Causes and
1 Interrupted current loop on Check IGBT, check error LEDs
Actions
CC2: IGBT short circuit on PWR board (only AEG
100/140/220: overcurr.
overvoltage, etc.) activated.
needed.
start
to run. problems
CC2 missing CC2
error 46/54/62 or 48/56/64 or
58
Summary

Description
None.
Extra Info
None.
Source ID

Causes and
1 The feedback cable X? on
Actions

Summary

Description CC2 overheated. When the lift is at standstill, it will be blocked, if it is in
motion, the trip will be completed. If it remains in motion for over
30sec, an emergency stop will be generated.
None.
Extra Info
None.
Source ID

Causes and
Actions
signal 2_KTHVF (PCC X?.?)

Summary
This error occurs, if the input X?.? (2_READY) on the PCC board is
Description noton high level (high level = higher than 9 V). This input represents
trip.
None.
Extra Info
None.
Source ID

Causes and
Actions
PWR board)
(PCC X?.? or PWR X102.6 /
UKE2 X?.?)
LEDs on PWR boardParallel
on UKE2 board
under error 614 !

Summary

None.
Extra Info
None.
Source ID

Causes and
Actions
board is faulty
Summary

That applies only to theparallel operation with Schindler converters (VF
280). If there is Parallel operation with AEG converters (VF 140 / 220),
the contactorfeedback is not connected and this error should never
occur (except PVF elevator paraInverter_Model is wrong).
None.
Extra Info
None.
Source ID

Causes and
Actions
wiring PCC X?.?
PVFP X3.4
Summary

(VF 280). If there is Parallel operation with AEG converters (VF 140
/220), the contactor feedback is not connected and this error should
None.
Extra Info
None.
Source ID

Causes and
Actions
wiring PCC X?.?
3 Wrong wiring, no driver signal Check driver signal VSGRW
on PVFP X3.3

Summary

Description still, at trip start and every 10 ms during the tripby software.
None.
Extra Info
None.
Source ID

Causes and
1 Variodyn 280(Schindler): Check FCR
Actions
converter (FCR)
redundant.
measurement X?.? and X?.?. Should be
UDCL/100
Summary

None.
Extra Info
None.
Source ID

Causes and
1 Interrupted current loop Check IGBT, check error LEDs
Actions
onCC3: IGBT short circuit on PWR board (only AEG
100/140/220: overcurr.
overvoltage, etc.) activated.
needed.
start
to run. problems.
CC3 missing CC3
error 46/54/62 or 48/56/64 or
66
Summary

Description
None.
Extra Info
None.
Source ID

Causes and
1 The feedback cable X? on
Actions

Summary

Description CC3 overheated. When the lift is at standstill, it will be blocked, if it is in
motion,the trip will be completed.Ifit remains in motion for over 30 sec,
an emergency stop will be generated.
None.
Extra Info
None.
Source ID

Causes and
Actions
signal 3_KTHVF (PCC X?.?)

Summary
This error occurs, if the input X?.? (3_READY) on the PCC board is
Description not on high level (high level = higher than 9 V). This input represents
trip.
None.
Extra Info
None.
Source ID

Causes and
Actions
PWR board)
(PCC X?.? or PWR X102.6 /
UKE2 X?.?)
LEDs on PWR boardParallel
on UKE2 board
under error 614 !
0667 Dummy 1
This section describes the MC PVF error Dummy 1.

Summary
Not used
Description
None.
Extra Info
None.
Source ID
0668 Dummy 2

Summary
Not used
Description
None.
Extra Info
None.
Source ID
0669 Dummy 3

Summary
Not used
Description
None.
Extra Info
None.
Source ID
0700 Memory Failure
This section describes the MC PVEC error Memory Failure.

Summary
Incorrect memory access.

Description
Note: When a memory failure occurs, please reset the VF and
download parameters by setting the commissioning state to 0 from
SMLCD or with CADI. This is for safety reason.
01: Error after reading from or writing to RAM

Extra Info 02: PLD not programmed (only for pcb PIOVEC)
03: SW not released for this inverter
04: No valid motor parameter table found
05: Wrong dsp program loaded
06: No valid inverter parameter table
07: No valid inverter current table
08: A failure occurred during memory test
For Parallel Inverter and Line Converter there is an offset in the Extra
Info set in order to assign the event to the relevant subsystem:
valid for Vecsys/Variosys 1.10
Slave 1: + 100
Slave 2: + 200
valid from Variosys 1.12

Slave 1: + 0x01000000
Slave 2: + 0x02000000
Line Converter: + 0x10000000
See General Information

Further
Information
None.
Source ID

Causes and
1 Extra Info = 1: Defective RAM Replace the pcb PVEC or
Actions
on pcb PVEC or Variocon. Variocon.
2 Extra Info = 2: PLD on Replace the pcb PIOVEC or
PIOVEC not programmed program its PLD
3 Extra Info = 3: Check SW version / Inverter
Type
4 Extra Info = 4 / 6 / 7: Programm 2nd Flash of
Variocon: Check service
flasher setup (Variocon with 2x
AM29F800B)
5 Extra Info = 5: problem with hw
detection of UIFCM in inverter
cabinet (AC converter
recognized as DC converter or
vice versa)
6 Extra Info = 8: A not supported Check SW version / Inverter
section was called during Type
memory test
0701 SW Warning
This section describes the MC PVEC error SW Warning.

Summary
The software detected an exceptional behavior of either the software or

Description of the hardware. These events are stored in the warning log only and
never generate an error.
Values not listed here can be decoded by developers of R&D-DR.

Extra Info 0E(hex)/14(dec): Start command received while running
5A(hex)/90(dec): Recovery test was started
5B(hex)/91(dec): Inconsistent HW Configuration (Check inverter id)
73(hex)/115(dec): Missing error state request from CO while in error
state
74(hex)/116(dec): Missing csm state request from CO while not
commissioned
8C(hex)/140(dec): Power up, SW-Reset
8F(hex)/143(dec): Error state set to dead (inverter blocked permanent)
90(hex/144(dec): Warning log deleted
91(hex)/145(dec): Error log deleted
96(hex)/150(dec): CSM state set to 'Not Commissioned' by control
AB(hex)/171(dec): HW watchdog
AC(hex)/172(dec): SW watchdog
C7(hex)/199(dec): Flash 2 write issue
C8(hex)/200(dec): Flash FS block write failed
DC(hex)/220(dec): Serial message failed (LC-VIP communication)
DD(hex)/221(dec): Serial message wrong header (LC-VIP
communication)
1xxx(hex): Illegal parameter on inverter where 'xxx' is the inverter
parameter id (Comm Id) according to J41400465
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID
0702 Communication Failure
This section describes the MC PVEC error Communication Failure.

Summary
Error on the serial communication links.

Description
1: UART framing error (from the Motor Control to the Travel Control)
Extra Info 2: UART parity error (from the Motor Control to the Travel Control)
3: UART overrun error (from the Motor Control to the Travel Control)
4: overflow TX buffer (from the Motor Control to the Travel Control)
5: unknown source (from the Motor Control to the Travel Control)
6: telegram length to large (from the Motor Control to the Travel
Control)
7: overflow RX buffer (from the Motor Control to the Travel Control)
8: overflow RX queue (from the Motor Control to the Travel Control)
9: CAN bus Warning (Parallel Converter)
10(dec)/0A(hex): CAN bus off (Parallel Converter)
11(dec)/0B(hex): CAN MSG to frame (Parallel Converter)
12(dec)/0C(hex): CAN frame to MSG (Parallel Converter)
13(dec)/0D(hex): CAN bus occupied (Parallel Converter)
17(dec)/11(hex): No SSI communication (Parallel Converter)
20(dec)/14(hex): CAN bus Warning (DriveBus)
21(dec)/15(hex): CAN bus off (DriveBus)
22(dec)/16(hex): CAN MSG to frame (DriveBus)
23(dec)/17(hex): CAN frame to MSG (DriveBus)
24(dec)/18(hex): CAN bus occupied (DriveBus)
30(dec)/1E(hex): I2C Bus not available
31(dec)/1F(hex): I2C operation error
32(dec)/20(hex): I2C Bus Busy
33(dec)/21(hex): No communication to VIP
34(dec)/22(hex): No communication from VIP
35(dec)/23(hex): No communication to VarioLC
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Extra info 1 - 3: EMC problems Check whether all screen
Actions
cables are grounded correctly.
2 Extra info 1 - 3: Check the connection between
Communication cable or the Motor Control (Inverter)
plug/connector faulty and the Travel Control
(ASIX/ASILOG).
3 Extra info 4 - 8 / 14 / 15: Report to R&D-DR
software problems
4 Extra info 9-13: CAN (Parallel Check CAN connections
converter)
5 Extra info 30-32: i2c Check VIP connection
Extra info 33-34: VIP
communication
6 Extra info 35: LC Check if LC is ready
communication
0703 Overcurrent Motor
This section describes the MC PVEC error Overcurrent Motor.

Summary
There are two possible reasons for the error:

Description
1. The motor current exceeds the maximum value at constant speed
(Extra Info 1).
The motor current monitoring at constant speed makes it possible to
detect inadmissible operating conditions. The limit depends on the
parameter "over current fact" (Supervisor Parameters) and relates to
the rated motor current "Is nom" (Motor parameters).
The effective limits are:
- gearless induction motors: over current fact * 1.15 = 1.38
- planetary gear: over current fact * 1.2 = 1.44
- worm gear: over current fact * 1.25 = 1.5
- synchronous motors (typically underslung): over current fact * 1.25 =
1.5
2. Unexpected change of motor torque (Extra Info 2). This reason only
applies to gearless induction motor drives with load measuring device.
1: Current exceeded at constant speed (Over current factor exceeded)

Extra Info 2: Unexpected change of motor torque
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Brake that does not open or check brake
Actions
opens only partially
2 Wrong parameters check parameters
3 Wrong dimensioning of drive check drive calculation (speed,
system acceleration, car weight, rated
load, etc.)
4 Wrong balancing check balancing of the elevator
(counterweight) of the elevator
5 Too much friction check guide shoes
6 Trip into the buffers upwards check why a trip into the
with insufficient rope slip or trip buffers.
into an obstacle. check for obstacle and remove
it.
7 Blocked return pulley Replace the pulley
8 Wrong counting direction of Check/correct parameter
motor encoder and/or wrong 'phase_dir',
phase direction of Motor for induction motors: perform
direction test
0704 Encoder Failure
This section describes the MC PVEC error Encoder Failure.

Summary
The feedback signal from the motor encoder is missing. The encoder
Description failure signal is generated on the related control board (e.g.
PIOVECxx) and read by the software.
1: Measured speed is zero and speed reference is not zero

Extra Info 2: Encoder signal input on frequency converter is faulty
3: Data transaction failed (absolute encoder with serial interface)
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Encoder cable not connected Check the cable and its
Actions
or not correctly plugged in. connection between the
encoder and the corresponding
pcb (PIOVECxx).
Check the plug.
2 Motor encoder not correctly Check the mounting of the
mounted encoder
3 Defective incremental encoder Replace encoder cable and/or
or encoder cable encoder
0705 Speed Difference
This section describes the MC PVEC error Speed Difference.

Summary
The difference between the speed reference value from travel control
Description and the actual speed feedback derived from the motor encoder
exceeds the value defined by the parameter OVER_SPEED_FACT.
The parameter OVER_SPEED_FACT relates to nominal speed.
Further error cause: In spite of a high torque no actual speed can be
measured (speed control error).
x01: underspeed
Extra Info x02: overspeed
x03: speed control error
x04: wrong sense of rotation detected during test 'sense of rotation'
(direction test for asynchronous motors)
x05: emergency stop during adjust tacholess control test
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Extra info 0x01 - 0x03: a) ensure the brakes do not
Actions
a) the controller can not remain closed
provide enough torque to b) check that the car is
follow the speed reference; balanced at 50%
possible causes are: c) reduce acceleration or
- the break does not open deceleration values
- elevator not balanced d) check elevator parameter
- output power of frequency impu ref
converter too small e) check the encoder
b) the incremental encoder is
defective
2 Extra info 0x04 with AC change either tacho signals or
machine: tacho signals or motor phases or execute
motor phases inverted (error direction test
detection immediately after trip
start)
3 Extra info 0x04 with DC Check motor parameters:
machine: Current limited Rated Motor Current,
Maximum Motor Current
4 Extra info 0x0001nnnn: Motor Check motor brake
brake not working properly
0706 Speed Ref Missing
This section describes the MC PVEC error Speed Ref Missing.

Summary
The speed reference telegrams from the Travel Control (MX- / TX- /
Description PTCM controller) are missing for at least two consecutive periods
(20ms).
x01: Time out for speed references on CAN (trip phase

Extra Info EXCITING_FIELD)
x02: Speed reference not received on CAN (during trip)
x03: Time out for speed references on RS422 (trip phase
EXCITING_FIELD)
x04: Speed reference not received on RS422 (during trip)
x05: Plausibility check of speed reference on CAN failed (acceleration
would be too high).
x06: Plausibility check of speed reference on RS422 failed
(acceleration would be too high).
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Interrupted transmission line Check serial communication
Actions
from Travel Control (e.g. pcb (cable and connection to pcb's)
ASILOG/ASIX) to Motor
Control (e.g. pcb PIOVECxx /
PVEC)
2 Problem with Travel Control Check if problem persists with
software other version of inverter
software or control software
3 Interface board (pcb) defective Replace respective pcb
0707 SGRW Failure
This section describes the MC PVEC error SGRW Failure.

Summary
Control or auxiliary feedback contact of charging contactor SGRW

Description faulty.
Meaning of extra info value:

Extra Info 1: SGRW contact not ON when VSGRW is ON
2: SGRW contact not OFF when VSGRW is OFF
+4(bitmask 0x4): Event before trip (trip preparation)
+8(bitmask 0x8): DC link was discharged < 50V
Examples of extra info values:

6(4+2): SGRW switches not OFF when VSGRW is OFF during
preparation for trip
1(1+0): SGRW switches not ON when VSGRW is ON at end of trip
9(1+8): SGRW contact not ON when VSGRW ON when charge of DC
link after long mains separation ('Long' means DC link is completely
discharged).
2(2+0): SGRW contact not OFF when VSGRW is OFF. Mains
separation in standstill when DC link is charged.
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000
Further
Information
None.
Source ID

Causes and
1 Wiring of control signal Check related wiring acc. to
Actions
VSGRW or of feedback signal wiring diagrams
SGRW broken or not
connected
2 Contactor SGRW faulty Check contactor SGRW
3 PIOVEC/VARIOcon PCB faulty replace PCB
0708 SH Failure
This section describes the MC PVEC error SH Failure.

Summary
Control or auxiliary feedback of contactor SH faulty.

Description
Meaning of extra info value:

Extra Info 1: SH contact not ON when VSH is ON
2: SH contact not OFF when VSH is OFF
+4(bitmask 0x4): Event before trip (trip preparation)
+8(bitmask 0x8): DC link was discharged (<50V)
Examples of extra info values (since VARIOsys V1.05):

5(1+4): SH switches not ON when VSH is ON during preparation for a
trip
1(1+0): SH is not ON when VSH is ON during a trip
2(2+0): SH switches not OFF when VSH is OFF at end of trip
2(2+0): SH contact not OFF when VSH is OFF. Mains separation in
standstill when DC link is charged.
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Wiring of control signal VSH or Check related wiring acc. to
Actions
of feedback signal SH broken wiring diagrams
or not connected
2 Contactor SH faulty Check contactor SH
3 TX-GC: the safety circuit Check safety circuit and total
opens during a trip or a test error log
(extra info values 1 or 5)
4 PIOVEC/VARIOcon PCB faulty replace PCB
5 Known problem in VecSys Update VecSys software to
software. version 2.14 (or higher)
0709 Safety Circuit
This section describes the MC PVEC error Safety Circuit.

Summary
The frequency converter detects that the safety circuit opens (relay
Description RSK off) during a trip or a test. The monitoring of the safety circuit
done by the control (travel control) may also generate a message
when the safety circuit opens. On Schindler frequency converters the
monitoring of the safety circuit is more sensitive than the one done by
travel control.
Caution: This error does not report a fault or an abnormal behaviour of

the power assembly (frequency converter, PVEC/PIOVEC) but of the
system as a whole; refer also to safety circuit monitoring (errors) of
travel control.
The error is not generated during inspection or recall trips (electrical
emergency operation).
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000
None.
Extra Info

Further
Information
None.
Source ID

Causes and
1 The safety circuit opened Check safety circuit and logs of
Actions
during a trip or a test. The other subsystems (total error
safety circuit may have been log)
interrupted only for a very short
time.
2 Cable of safety circuit signal Check wiring from control
broken or not connected (ASxxx board) to frequency
converter.
0710 FCR Not Ready
This section describes the MC PVEC error FCR Not Ready.

Summary
The FCR is not ready to run.

Description
1: FCR not started correctly

Extra Info 2: FCR not stopped correctly
3: FCR wrong feedback
4: FCR failure
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID
Causes and
1 check FCR error log
Actions
0711 Overcurrent Inverter
This section describes the MC PVEC error Overcurrent Inverter.

Summary
The actual current exceeds the maximum current of the frequency

Description converter.
The limit is set automatically according to the following parameters:
'Accel Inv Current'/'Rated Motor Current'/'IMotPeak'/'Gear Type'.
The effective limits are:

- worm gear: Accel Inv Current * 1.1/0.85 + 6 [A]
- all other: Accel Inv Current * 1.1 + 6 [A]
The value may be reduced as follows:

- induction motors: 3* rated motor current*sqrt(2)
- synchronous motors: IMotPeak +
Meaning of extra info value for VecSys 2.15 / VARIOsys 1.02 and
Extra Info higher
x01(bitmask Bit 0): Error in phase U
x02(bitmask Bit 1): Error in phase V
x04(bitmask Bit 2): Error in phase W
below (older)
x01: overcurrent in phase U
x02: overcurrent in phase V
x03: overcurrent in phase W
Slave 1: + 100
Slave 2: + 200
Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Malfunction of current Check cables from SKiiP or
Actions
measurement from LEMs
2 IGBTS faulty Replace power unit
3 Incorrect inverter or motor Check parameters, use
parameters settings
4 Short circuit
0712 Power Electronic Failure
This section describes the MC PVEC error Power Electronic Failure.

Summary
The feedback of the power electronics module(s) report an error.

Description
Extra Info higher:
x00: Any error in power module
x01(Bitmask Bit 0): Error in phase U / VF11BR: overcurrent / DC: not
used
x02(Bitmask Bit 1): Error in phase V / VF11BR: supply voltage error /
DC: error in half bridge A1
x04(Bitmask Bit 2): Error in phase W / DC: error in half bridge A2
x08(Bitmask Bit 3): AC/DC: Error in brake chopper
below (older):
x01: error in phase U
x02: error in phase V
x03: error in phase W
x04: error in brake chopper
x05: any error in power module
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Cable from power unit broken check cable and connectors
Actions
or not connected
2 Power module faulty replace power unit
3 Fan faulty check that the fan runs during
a trip, run fan test, check
cables, replace fan
4 Brake resistor/chopper faulty check brake resistor and
(overvoltage trigger) cables
5 Temperature in machine room
or hoistway too high
6 Wrong dimensioning
(calculation) of the drive
system
7 For extra info value=0: thyristor
not on (VF30BR only)
Power module turned off
(VF88PF1 V2 only)
8 For extra info value=5:
overcurrent / short circuit
0713 Current Difference
This section describes the MC PVEC error Current Difference.

Summary
The control deviation of the current controller exceeds the value

Description specified by supervisor parameter IS_DIFF_LIM.
01: Difference between reference value and actual value too big
Extra Info 02: DC converter only: current loop interrupted at start-up
03: Offset of current measurement too big
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Interrupted transmission of Check cables
Actions
transistor signals
2 Defective igbts Replace power unit
3 Malfunction or interrupted Check cables
transmission of current
measurement.
4 If the error occurs at the end of If the error occurs at the end of
the acceleration phase: faulty the acceleration phase: reduce
dimensioning of drive system the nominal speed
5 Modernization: wrong motor Check wiring
wiring
6 VFxxDC: Voltage Limited Check parameter Rated Motor
Voltage (this parameter can be
increased in small steps; do
not increase the value too
much)
0714 Current Not Zero
This section describes the MC PVEC error Current Not Zero.

Summary
Motor current not zero at standstill

Description
Extra Info Info set in order to assign the event to the relevant subsystem:
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Current measurement faulty Check cables, LEM
Actions
2 Power assembly faulty Replace power unit
0715 Current Sum Failure
This section describes the MC PVEC error Current Sum Failure.

Summary
Sum of motor phase currents is not zero. The error is generated when
Description the current sum exceeds 30 % of the inverter nominal current.
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Short circuit between phase Check wiring and motor
Actions
and ground on the motor side
2 Current measurement faulty Check cables, LEM
(EMC)
0716 Overtemp HS Trigger
This section describes the MC PVEC error Overtemp HS Trigger.

Summary
The overtemperature trigger on the heatsink is active.

Description
Meaning of extra info value for Variosys 1.17 and higher:

Extra Info 0xSI0PTTTT
S: Subsystem: 0 MC, 1 LC
I: Inverter ID: 0 Master, 1 Slave 1, 2 Slave 2
P: Phase: 1 U/L1, 2 V/L2, 4 W/L3
TTTT: Temparature: measured temperature
special values:
over temperature = 1
no signal = 2
short cut = 3
out of range = 4
ambient = 20
Meaning of extra info value for VecSys 2.15 / VARIOsys 1.02 to

Variosys 1.16:
x01(Bitmask Bit 0): overtemperature in phase U
x02(Bitmask Bit 1): overtemperature in phase V
x04(Bitmask Bit 2): overtemperature in phase W
below (older):
01(x01): overtemperature of heatsink
11(x0B): overtemperature trigger phase U
12(x0C): overtemperature trigger phase V
13(x0D): overtemperature trigger phase W
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Fan faulty Check fan
Actions
2 Cable from klixon broken or Check cable
not connected
3 Temperature of machine room
too high
4 Faulty dimensioning of drive
system
0717 Overtemp HS Limit
This section describes the MC PVEC error Overtemp HS Limit.

Summary
Temperature limit of the heatsink or of the brake chopper (if available)

Description exceeded. (See supervisor parameter INV_TEMP_LIM --> parameter
description).
A trip must be terminated by the Travel Control on the next floor.

P: Phase: 1 U/L1, 2 V/L2, 4 W/L3
special values:
no signal = 2
short cut = 3
out of range = 4
ambient = 20
For Variosys 1.13 to Variosys 1.16

0xn1 Overtemperature of power module
0xn2 No temperature signal of sensor power module
0xn3 Shortcut of sensor power module
0x0m Sensor of converter with one single power module
0x1m Sensor of power module phase 1
For VecSYS and software versions below 1.13 of Variosys software

01: overtemperature of heatsink
02: no temperature signal from heatsink
03: overtemperature of brake chopper
04: no temperature signal from brake chopper
dec11(h0B): Overtemperature phase U
dec12(h0C): Overtemperature phase V
dec13(h0D): Overtemperature phase W
dec21(h15): No temperature signal from heatsink phase U
dec22(h16): No temperature signal from heatsink phase V
dec23(h17): No temperature signal from heatsink phase W
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
Actions
2 Cable from heatsink broken or Check cable
not connected
too high
4 Faulty dimensioning of drive
system
0718 DCL Overvoltage Trigger
This section describes the MC PVEC error DCL Overvoltage Trigger.

Summary
Overvoltage in DC link.
Description The overvoltage trigger signal is generated on the motor control board
or line control board and read by software, the voltage level is at about
875 V.
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Diode bridge at the input of DC Check brake chopper and
Actions
link:malfunction of the brake brake resistor
chopper or brake resistor
2 Line converter at the input of Check line converter
DC link (VF120 - VF280,
VF55PF1 - 3xVF288PF1 AC,
VF155PF1 - VF288PF1
DC):malfunction of line
converter
0719 DCL Overvoltage
This section describes the MC PVEC error DCL Overvoltage.

Summary
Overvoltage in DC link.
Description The DC link voltage is measured by an AD-converter. The limit is
determined by the supervisor parameter Udcl Upp Lim Idle (see
parameter description). It can only occur during standstill.
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Overvoltage in mains Check mains supply voltage
Actions
2 Parameter wrong Check the parameter Input
voltage setting and/or Udcl
Upp Lim Idle
VF155PF1 - VF288PF1
converter
DC link (VF120 - VF280, parameters
VF155PF1 - VF288PF1
DC):wrong parameters of line
converter
0720 DCL Undervoltage
This section describes the MC PVEC error DCL Undervoltage.

Summary
Undervoltage in DC link.
Description The DC link voltage is measured by an AD-converter. The limit is
determined by the supervisor parameter Udcl Low Lim Idle (see
parameter description) during stand still and Udcl Low Lim Ride during
the trip.
In addition, the dc link voltage is monitored by line control (VarioLC).
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Undervoltage in mains Check mains supply voltage
Actions
2 Parameter wrong Check the parameters Input
voltage setting, Udcl Low Lim
Idle and Udcl Low Lim Ride
3 Defective diode bridge Replace power unit
VF155PF1 - VF288PF1
converter
DC link (VF120 - VF280, parameters
VF155PF1 - VF288PF1 DC):
wrong parameters of line
converter
0721 DCL Unsymmetric Voltage
This section describes the MC PVEC error DCL Unsymmetric Voltage.

Summary
DC link voltage not symmetric

Description
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 DC link capacitor faulty Replace it
Actions
0722 DCL Charging Time
This section describes the MC PVEC error DCL Charging Time.

Summary
Maximum DC link charging time exceeded.

Description
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Undervoltage in mains Check mains supply voltage
Actions
2 Parameter wrong Check the parameters Input
voltage setting and/or Udcl
Low Lim Idle
3 Defective diode bridge Replace power unit
0723 DCL Discharging Time
This section describes the MC PVEC error DCL Discharging Time.

Summary
Maximum DC link discharging time exceeded.

Description
01: discharging time exceeded

Extra Info
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 symmetry resistor faulty replace power unit
Actions
2 During dc link test / Discharge replace power unit
dc link test with VFxxBR:
symmetry resistor faulty, brake
chopper/resistor faulty
3 During dc link test / Discharge check motor connection
dc link test with VFxxPF1 and replace power unit
Variosys > 1.16: symmetry
resistor faulty, connection to
motor wrong, motor power
module faulty
0724 Power Supply
This section describes the MC PVEC error Power Supply.

Summary
Power supply faulty

Description
Variocon (MC and LC): The extra info is the measured VKK at the time
Extra Info the failure occurred.
The value is in hexadecimal, the unit is 100 mV
PVEC:
1: 24V supply faulty
2: 15V or 5V supply faulty
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Voltage interruption of mains Check mains supply voltage
Actions
2 24V power supply faulty Replace power supply unit
0725 Overtemp KTHBR
This section describes the MC PVEC error Overtemp KTHBR.

Summary
Overtemperature on the brake chopper resistor (detected with PT100 /

Description KTJ84 / KTHBR). On some PF1 inverters (with VarioLC)
overtemperature of line choke. Please check in schematics.

P: Probe: 0 unknown, 1 none, 2 PT100, 3 KTY84
special values:
no signal = 2
short cut = 3
out of range = 4
ambient = 20
Meaning of extra info value for Variosys 1.16 and older:

1: Overtemperature of BR (detected with klixon KTHBR)
2: No temperature signal from sensor BR / open
3: Shortcut of sensor BR
4: No feedback from FAN (converters with VARIOcon / VIP only)
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
Actions
2 Cable from sensor (klixon) Check cable
broken or not connected
too high
4 Wrong dimensioning of drive Verify drive calculation
system
5 Wrong value of parameter Correct parameter according to
"Brake Chopper Type" the parameter description
0726 Overtemp MH
This section describes the MC PVEC error Overtemp MH.

Summary
Overtemperature of the hoisting motor (detected with PT100 / KTJ84).

Description On some PF1 inverters overtemperature of line choke. Please check
schematics.

special values:
no signal = 2
short cut = 3
out of range = 4
ambient = 20

1: Overtemperature of MH
2: No temperature signal from MH / open
3: Shortcut of sensor MH
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 MH fan faulty check fan
Actions
2 THMH cable MH broken or not check cable
connected
too high
4 Wrong dimensioning of drive Verify drive calculation
system
5 Wrong value of parameter Set parameter according to
"Motor Temp Lim" parameter description
0727 HW failure
This section describes the MC PVEC error HW failure.

Summary
HW failure of converter detected.

Description
Yaskawa inverter:
Extra Info 1: for further details see Yaskawa documentation CPF04
2: for further details see Yaskawa documentation CPF05
VARIOSys parallel inverter the extra info

0x0001: no CAN communication to master
0x0002: no CAN communication to slaves (at least one slave did not
answer)
0x0003: no dsmc alive
0x0004: dsmc progerr
0x0005: wrong pcb (inverter setting does not correspond to hardware)
0x8xxx: (until v1.17)
Bit 0 (0x1): no capture signal
Bit 1 (0x2): TMOD not synchronized
Bit 2-5 (0x4/0x8/0x10/0x20): Timeout ssi
Bit 6/7 (0x40/0x80): Transmission error (data/flag)
Bit 8 (0x100): mode u/v/w not synchronized
Bit 9 (0x200): task_counter not synchronized
Bit 10 (0x400): master_int_counter not synchronized
0x8xxx: (v1.18 and beyond)
Bit 0 (0x1): no capture signal
Bit 1 (0x2): TMOD not synchronized
Bit 2-5 (0x4/0x8/0x10/0x20): Timeout ssi
Bit 6/7 (0x40/0x80): Transmission error (data/flag)
Bit 8 (0x100): task_count & mast_int_count not synchronized / line
angle not synchronized
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Yaskawa: faulty inverter refer to Yaskawa
Actions
hardware documentation for details
2 VARIOSys parallel inverter: Check SSI/CAN wiring of VIP3
SSI/CAN communication board
interrupted
3 VARIOSys parallel inverter: Check grounding connections
Disturbance on SSI/CAN (screws) of VIP3 board and
connection shielding of SSI/CAN
communication cables
4 VARIOSys parallel inverter: Check warning log of master
Reset of master inverter inverter for SW warning (E1)
with extra info value 140
5 VARIOSys inverter info Change Variocon board,
0x0003, 0x0004: Fatal download new software
program/hardware failure of
dsmc
6 VarioLC inverter info 0x81xx Phase sequence of mains
supply not the same for master
and slaves
0728 Phase failure
This section describes the MC PVEC error Phase failure.

Summary
Variosys: Input Phase failure

Description Yaskawa: Output phase failure
Variosys/VarioLC
Extra Info 0: Phase sequence test failed
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000
Yaskawa
0: see Yaskawa documentation LF
1: see Yaskawa documentation SE1
2: see Yaskawa documentation SE2

Further
Information
None.
Source ID

Causes and
1 for Variosys: Mains current Check wiring
Actions
and / or voltage sensors
connected wrongly
2 for Yaskawa: Faulty inverter refer to Yaskawa
hardware documentation
0729 Fan failure
This section describes the MC PVEC error Fan failure.

Summary
Failure of the fan

Description
BR converters
Extra Info 1: no feedback of VFVE (motor converter fan)
4: no feedback of VFVE-BR (brake resistor fan)
PF1 converters
1: no feedback of VFVE-CO (motor converter fan)
4: no feedback of VFVE-FCR (line resistor fan)
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 VF288: no 48 V supply (NG48) Check power supply unit:
Actions
all other converters: no 24 V measure supply and output
supply voltage
2 VF288: no control signal on Check wiring of connector
fan VIP3.FAN OUT
3 VF288: no feedback signal Check wiring of connector
from FAN VIP3.FAN IN
0730 FCM failure
This section describes the MC PVEC error FCM failure.

Summary
Failure of the field control module (FCM)

Description
1: Time out switching on

Extra Info 2: FCM not on
3: Time out switching off
4: FCM not off
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID
Causes and
1 Error occurred on FCM Check status of LED's on FCM
Actions
unit for further diagnostics
2 Wrong wiring between UIFCM Check wiring of UIFCM
in drive cabinet and on FCM
0731 FCM overtemperature
This section describes the MC PVEC error FCM overtemperature.

Summary
Overtemperature of the field control module (FCM)

Description
1: No signal
Extra Info 2: Over-temperature
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 No power supply on FCM Check Power supply on FCM
Actions
2 FCM over heated Check fan on FCM
0732 Overtemp Line Choke
This section describes the MC PVEC error Overtemp Line Choke.

Summary
Over temperature of line choke.

Description

special values:
no signal = 2
short cut = 3
out of range = 4
ambient = 20

0x01: Line choke overtemperature measured
0x02: Sensor open, no signal
0x03: Sensor short circuit
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Line choke overheated Check fan of line choke
Actions
2 Sensor broken Check / replace sensor
3 Line choke fan faulty Check / replace fan
0733 Mains Current Difference
This section describes the MC PVEC error Mains Current Difference.

Summary
The control deviation of the mains current controller exceeds the limit.
Description
0x01: Mains current difference phase U

Extra Info 0x02: Mains current difference phase V
0x04: Mains current difference phase W
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Interrupted transmission of Check cables
Actions
transistor signals
2 Defective IGBTs Replace power unit
3 Malfunction or interrupted Check cables
transmission of current
measurement.
4 Bad mains quality (high mains Check mains voltage quality
impedance, voltage drops,
voltage interruptions)
5 Wrong line control parameters Check Inverter setting, inverter
input voltage setting
0734 Mains Overcurrent
This section describes the MC PVEC error Mains Overcurrent.

Summary
The actual mains current exceeds the maximum current of the

Description frequency converter.
0x01: Overcurrent mains phase U

Extra Info 0x02: Overcurrent mains phase V
0x04: Overcurrent mains phase W
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Malfunction of current Check cables from power
Actions
measurement module(s)or from LEMs
2 IGBTs faulty Replace power unit
3 Wrong line control parameters Check Inverter setting, inverter
input voltage setting
4 Short circuit Check wiring
0735 Mains Phase Interruption
This section describes the MC PVEC error Mains Phase Interruption.

Summary
Interruption on Mains Supply (VarioLC).

Description
0x01: Mains phase U interrupted

Extra Info 0x02: Mains phase V interrupted
0x04: Mains phase W interrupted
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Wiring faulty Check mains wiring
Actions
2 Mains voltage sensor faulty Check/replace LVM pcb on
inverter
0736 Mains Voltage Failure
This section describes the MC PVEC error Mains Voltage Failure.

Summary
Mains voltage too high or too low or mains voltage frequency too high
Description or too low.
0x01: Mains voltage out of range: undervoltage

Extra Info 0x02: Mains voltage out of range: overvoltage
0x03: Mains frequency out of range: frequency too low
0x04: Mains frequency out of range: frequency too high
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID
Causes and
1 Incorrect inverter parameters Check settings parameter of
Actions
inverter (Inverter Input Voltage)
2 Mains supply voltage not Measure 3 phases of mains
stable voltage
0737 UEM detected
This section describes the MC PVEC error UEM detected.

Summary
Motor encoder moved in standstill. Unintended encoder movement.

Description
0x0001nnnn: Motor moves when motor control is at standstill; nnnn:

Extra Info distance of car movement in [mm]
Examples for extra info values:

0x0001000A: traction sheave moved resulting in a car movement of 10
mm in up direction.
0x0001FFF6: traction sheave moved resulting in a car movement of 10
mm in down direction.
Slave 1: + 100
Slave 2: + 200

Slave 1: + 0x01000000
Slave 2: + 0x02000000

Further
Information
None.
Source ID

Causes and
1 Motor brake faulty Replace motor brake
Actions
2 Motor brake adjustment wrong Adjust brake (if adjustment is
allowed)
3 Wrong measurement of Check/replace encoder
encoder
0740 Overspeed
This section describes the Magnetek error Overspeed.

Summary
Magnetek error 97
Description Either the pattern was too high or the car speed was too high.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Speed command too high Check pattern value tuning
2 Check position loop tuning
3 Car didnt follow pattern Check speed loop tuning
0741 Tach Loss
This section describes the Magnetek error Tach Loss.

Summary
Magnetek error 98
Description The armature voltage is high enough that the motor should be
spinning, but the encoder is not generating pulses.
None.
Extra Info
None.
Source ID

Causes and
1 The motor encoder installation Check for broken wires or a
Actions
may be broken loose coupling.
2 The motor encoder may be Check if motor moves
broken
3 Replace Encoder
0742 Reverse Tach
This section describes the Magnetek error Reverse Tach.

Summary
Magnetek error 99
Description The motor encoder is running backwards.
None.
Extra Info
None.
Source ID

Causes and
1 If the motor is running the Swap the A and A~ wires.
Actions
correct direction
2 If the motor is running the Check the armature and motor
wrong direction field connections.
0743 not_a_number
This section describes the Magnetek error not_a_number.

Summary
Magnetek error 100

Description Problem with Magnetek software.
None.
Extra Info
None.
Source ID

Causes and
1 Problem with Magnetek Try replacing PROMS U39 and
Actions
software U40 on the drive.
2 Unknown cause Inform field engineer
0744 overflow
This section describes the Magnetek error overflow.

Summary
Magnetek error 101

None.
Extra Info
None.
Source ID

Causes and
Actions
0745 underflow
This section describes the Magnetek error underflow.

Summary
Magnetek error 102

None.
Extra Info
None.
Source ID

Causes and
Actions
0746 divide by zero
This section describes the Magnetek error divide by zero.

Summary
Magnetek error 103

None.
Extra Info
None.
Source ID

Causes and
Actions
0747 Motor overload
This section describes the Magnetek error Motor overload.

Summary
Magnetek error 400

Description The drive supplied too much current to the motor for too long.
None.
Extra Info
None.
Source ID

Causes and
1 a) Something dragging / Check for problems in the
Actions
binding hoistway
2 Check that the brake doesnt
drag
3 Check that the parameters
motor_ovld_tout has not been
changed
4 Check that the parameter
motor_ovld_level has not been
changed
0748 Motor field overcurrent
This section describes the Magnetek error Motor field overcurrent.

Summary
Magnetek error 401

Description
None.
Extra Info
None.
Source ID

Causes and
1 Short in winding or wiring Check the motor field current
Actions
2 Bad supply Replace field regulator board if
necessary
0749 Contactor fault
This section describes the Magnetek error Contactor fault.

Summary
Magnetek error 402

Description The output contactor did not pick when we expected it to.
None.
Extra Info
None.
Source ID

Causes and
1 The output contactor did not Check coil wiring
Actions
pick
2 The monitoring circuit is Check auxillary contact
broken connected to TB1-7
0750 1 minute full field
This section describes the Magnetek error 1 minute full field.

Summary
Magnetek error 403

Description The control system asked for full motor field, but didnt start a trip within
1 minute.
None.
Extra Info
None.
Source ID

Causes and
1 Check the parameter System
Actions
Type of travel controller
0751 Open armature circuit
This section describes the Magnetek error Open armature circuit.

Summary
Magnetek error 404

Description The motor armature circuit is disconnected.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check the DC fuse
2 Check the output contactor
3 Check the brushes
0752 safety circuit
This section describes the Magnetek error safety circuit.

Summary
Magnetek error 405

Description The contacts of the safety circuit relays (RH, RH1 or RSK,RSK1) wired
to TB3-6 are not opening and closing properly. This error is reported
whenever you jump the contacts to do a self tune.
None.
Extra Info
None.
Source ID

Causes and
1 Check for a jumper
Actions
2 Check that both relays drop out
properly
0753 PAC fault
This section describes the Magnetek error PAC fault.

Summary
Magnetek error 406

Description The speed reference or actual motor speed changed too rapidly.
None.
Extra Info
None.
Source ID

Causes and
1 Check that the acceleration
Actions
and jerk rates are reasonable
2 Check that the acceleration
limit (function 21) is greater
than the normal acceleration
3 Check for noise on the motor
encoder.
0754 DCU CEMF fault
This section describes the Magnetek error DCU CEMF fault.

Summary
Magnetek error 407

Description Motor armature voltage is wrong.
None.
Extra Info
None.
Source ID

Causes and
1 Check that the actual voltage
Actions
from the isolation transformer
matches the parameter
NOMINAL_AC (function 9).
2 Check that the full and running
motor field currents are correct.
3 Check that motor field
weakening starts and stops at
the proper speeds.
0755 PCU CEMF fault
This section describes the Magnetek error PCU CEMF fault.

Summary
Magnetek error 408

Description Motor armature voltage is wrong.
None.
Extra Info
None.
Source ID

Causes and
1 Check that the actual voltage
Actions
from the isolation transformer
matches the parameter
NOMINAL_AC (function 9).
2 Check that the full and running
motor field currents are correct.
3 Check that motor field
weakening starts and stops at
the proper speeds.
0756 PCU reset
This section describes the Magnetek error PCU reset.

Summary
Magnetek error 409

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Replace drive processor
board
2 Inform field Engineer
0757 loop fault
This section describes the Magnetek error loop fault.

Summary
Magnetek error 900

Description Output contactor opened unexpectedly.
None.
Extra Info
None.
Source ID

Causes and
1 Check contactor
Actions
2 Check auxilliary contact
connected to drive.
0758 IST fault
This section describes the Magnetek error IST fault.

Summary
Magnetek error 901

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check for short circuit in the
Actions
motor armature circuit
2 Check tuning of current
regulator
0759 Power supply
This section describes the Magnetek error Power supply.

Summary
Magnetek error 902

Description A power supply voltage is missing.
None.
Extra Info
None.
Source ID

Causes and
1 Check for short in wiring to
Actions
motor encoder or aux. contact
of output encoder
2 Check for a short on a board
inside the drive
3 Check for 115 vac control
voltage into drive
4 May need to replace power
supply board inside drive (on
back of door).
0760 Line synch
This section describes the Magnetek error Line synch.

Summary
Magnetek error 903

Description The drive monitors its 3-phase power input to determine whento turn
on the SCRs. If it does not detect 3-phase AC power it cannot operate.
None.
Extra Info
None.
Source ID

Causes and
1 Check for loose connections
Actions
on input mainline wiring
2 Check for dips on mainline
voltage.
3 Check voltage divider on
Armature Interface board
0761 Low line
This section describes the Magnetek error Low line.

Summary
Magnetek error 904

Description The 3-phase power supply voltage is too low.
None.
Extra Info
None.
Source ID

Causes and
1 Check for dips in input mainline
Actions
voltage
2 Check for blown input fuse
3 Check taps on isolation
transformer
0762 Field loss
This section describes the Magnetek error Field loss.

Summary
Magnetek error 905

Description Motor field current is off or less than commanded.
None.
Extra Info
None.
Source ID

Causes and
1 Check wiring
Actions
2 Check input fuses
3 Check that the feed to the
motor field supply has the
same phase sequence as the
main power
0763 DCU failure
This section describes the Magnetek error DCU failure.

Summary
Magnetek error 906

Description DCU microprocessor failure.
None.
Extra Info
None.
Source ID

Causes and
1 DCU microprocessor failure Replace main processor board
Actions
in drive
0764 Bad thermistor
This section describes the Magnetek error Bad thermistor.

Summary
Magnetek error 907

Description Thermistor on drive heat sink is open or shorted, or the actual
temperature is way out of range.
None.
Extra Info
None.
Source ID

Causes and
1 Thermistor on drive heat sink Check wiring and resistance of
Actions
is open or shorted thermistor (normally around
200 k at 25 C)
2 The actual temperature is way
out of range
0765 High temperature
This section describes the Magnetek error High temperature.

Summary
Magnetek error 908

Description The temperature inside the cabinet is too high.
None.
Extra Info
None.
Source ID

Causes and
1 Check machine room ambient
Actions
temperature
2 Check that the fan on the drive
is running
3 Check that the air flow into and
out of the cabinet is not
blocked.
4 Bad thermistor Thermistor is wired between
TB6.4 and TB6.5 inside the
drive. At 25C it should measure
200 k
0766 Exessive ripple
This section describes the Magnetek error Exessive ripple.

Summary
Magnetek error 909

Description The drive output is not stable.
None.
Extra Info
None.
Source ID

Causes and
1 Check for loose connections in
Actions
the power circuit and gate
leads
2 Check if the parameter Use
SelfTune Values is set to 1
(Magnetek function #2) Re-do
the Test Self-Tune
3 Replace the armature interface
board or the drive control
board
0767 Blown fuse
This section describes the Magnetek error Blown fuse.

Summary
Magnetek error 910

Description There is no power detected on one of the power input lines.
None.
Extra Info
None.
Source ID

Causes and
1 Check input fuses
Actions
2 Check mainline fuses
3 Check for loose connnections
in power circuit
4 Check SCRs
0768 shorted doubler
This section describes the Magnetek error shorted doubler.

Summary
Magnetek error 911

Description An SCR (or pack of 2 SCRs) is shorted.
None.
Extra Info
None.
Source ID

Causes and
1 Replace SCR (or multi-SCR
Actions
doubler pack)
0769 Open SCR
This section describes the Magnetek error Open SCR.

Summary
Magnetek error 912

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Replace SCR
0770 bad parameter
This section describes the Magnetek error bad parameter.

Summary
Magnetek error 915

Description One or more setup parameter is out of range.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check:
2 Nominal_AC,
3 Rated_armature_voltage,
4 Rated_armature_current,
5 Full_field_current,
6 Current_limit
0771 Forcing fault
This section describes the Magnetek error Forcing fault.

Summary
Magnetek error 916

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Inform field Engineer
0772 AV feedback reversed
This section describes the Magnetek error AV feedback reversed.

Summary
Magnetek error 917

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check that themotor is turning
Actions
the correct direction. If it is,
reverse the armature voltage
feedback wires (TB5-1, TB5-
2).
0773 Parameter too high
This section describes the Magnetek error Parameter too high.

Summary
Magnetek error 918

Description
None.
Extra Info
None.
Source ID

Causes and
1 The supervisor parameter Adjust the parameter
Actions
current_limit is set too high
This section describes the Magnetek error Parameter out of range.

Summary
Magnetek error 919

Description
None.
Extra Info
None.
Source ID

Causes and
1 The elevator parameter Adjust the parameter
Actions
Nominal_AC is set too high or
too low
This section describes the Magnetek error Parameter out of range.

Summary
Magnetek error 921

Description
None.
Extra Info
None.
Source ID

Causes and
1 The motor parameter Adjust the parameter
Actions
Rated_armature_voltage is too
high or too low
0776 Bridge fault
This section describes the Magnetek error Bridge fault.

Summary
Magnetek error 921

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check connector J14
Actions
2 Check power-range-selector
resistor on TB6
3 Replace Armature interface
board or drive control board
This section describes the Magnetek error parameter out of range.

Summary
Magnetek error 922

Description
None.
Extra Info
None.
Source ID

Causes and
1 The parameter Inform field Engineer, since
Actions
rated_frequency is too high or this parameter is not user
too low adjustable

Summary
Magnetek error 923

Description
None.
Extra Info
None.
Source ID

Causes and
1 The motor parameter Adjust the parameter
Actions
Rated_armature_current is too
high or too low
2 Check power-range-selector
resistor on TB6
3 Replace Armature interface
board or drive control board

Summary
Magnetek error 924

Description
None.
Extra Info
None.
Source ID

Causes and
1 The parameter Check the parameter setting
Actions
Full_field_current doesnt
match the motor field supply
installed
2 Check that the motor field
supply is configured correctly
3 Check connector J13 and the
motor field supply board
0780 Field supply fault
This section describes the Magnetek error Field supply fault.

Summary
Magnetek error 925

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check connector J13
Actions
2 Replace the motor field supply
board
3 Replace the drive control
board
0781 PCU software fault
This section describes the Magnetek error PCU software fault.

Summary
Magnetek error 926

Description
None.
Extra Info
None.
Source ID

Causes and
1 The software in the PCU (U13, Replace proms
Actions
U14) reset unexpectedly or is
an incompatible version
0800 VD35 base
This section describes the 800_899_Varidor35_Door_Drive error VD35

Summary base.
base ID for VD35 errors.

Description
not applicable
Extra Info
not applicable
Source ID
0809 wCommand Unknown
This section describes the 800_899_Varidor35_Door_Drive error

Summary wCommand Unknown.
This Warning is sent if DD has received a DOOR MOTION command

Description (DOOR_MOTION_CMD message) but can not interpret its detail
command (e.g. open)
Door Side:
Extra Info 1 = front door
2 = rear door
3 = upper deck front (double deck only)
4 = upper deck rear (double deck only)
not applicable
Source ID

Causes and
1 Elevator control sends wrong The command is ignored and
Actions
data. no further actions can be
taken. Elevator control needs
to be checked for inappropriate
instruction information.
0812 wWrong Motion Direction

Summary wWrong Motion Direction.
Inconsistency between the required movement and the door position

Description feedback (opening with a close command or vice-versa).
Opened position is reached (transition from 'Opening' to 'Opened') in
Referencing Mode and KETS-2 is active
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 The door drive is configured 1. Check motion direction
Actions
with a wrong motion direction. setting given by Motor Rotation
Direction
2. Execute AutoSetup.
2 An unreferenced door drive 1. Check for proper function of
detects a mechanical limit the car door lock and for a
during an opening motion and blocked clutch during opening
KET-S2 is closed
3 An unreferenced door drive 1. Check mechanical
detects a mechanical stop adjustment of KET-S2 contact.
after the execution of the 2. Check electrical functionality
clutch folding motion and KET- of KET-S2 contact
S2 is detected open. (check LED 'Closed on HMI')
3. Replace KET-S2 Contact
4. Execute AutoSetup
0821 Door Movement too Fast
This section describes the 800_899_Varidor35_Door_Drive error Door

Summary Movement too Fast.
Transition from closed to open state (or vice versa) has occurred in a
Description time smaller than the minimum expected.
No Varidor 35 error. This error is generated by EC.
Door Side:
2 = rear door
not applicable
Source ID
0832 wKET-S2 Failure

Summary wKET-S2 Failure.
This warning is triggered after each 5th time in serie if KET-S2 sensor (
Description switch) is not closed when motion state Closed is reached (transition
from 'Closing' to 'Closed') in normal mode. With this warning the
SpeedPerformance is set to 35% if not already reduced by warning
834_ wMT_OverTemp. If KET-S2 intermittently works again the
SpeedPerformance is set back to previous level. ErrCounter is set to 0.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 KET-S2 is not closed when the 1. Check the mechanical
Actions
referenced door panels reach adjustment of KET-S2.
their closed position 2. Execute AutoSetup.
3. Check for broken wiring of
KET-S2.
4. Replace KET-S2 contact
0833 eKET-S2 Short; Contact Bridged

Summary eKET-S2 Short; Contact Bridged.
- Door Drive System is not in Referencing mode and Opened Position

Description is reached (transition from 'Opening' to 'Opened') and KETS-2 active.
The door stops and torque remains applied to the motor.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 KET-S2 is still closed when the Check KET-S2 for proper
Actions
referenced door panels reach function and for short circuits in
their opened position. the wiring.
0834 wMotor Over Temperature

Summary wMotor Over Temperature.
The warning is triggered if the motor or electronics temperature has

Description reached a critical level. This warning is accompanied by a performance
reduction and represents a pre state of the KTHMT signal. It is
intended to indicate potentially too high settings of the motion
parameters to the EC and signalizes the maintenance / fitter to reduce
the opening speed for very heavy doors with high speed settings.
On this warning the door performance will be reduced by 30% The

door performance is set back to its original settings if the temperature
gets below 90% of its maximum operation temperature.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Increased friction due to 1. Check the mechanical
Actions
ageing or damage of the fitness of the door
mechanical components 2. Check especially if there is
an increased friction.
3. Replace parts that cause the
friction
4. Run AutoSetup
2 Strong closing springs with 1. Reduce open-hold-time or
high demanding forces at 2. Reduce pre-tension of
opened position. And/Or: Very closing spring
high door mass in conjunction 3. Only if no stong closing
with frequent motion changes . spring: Reduce parameter
39_Speed_Close and
40_Speed_Open
3 The power stage exhibits a 1. Check environmental
high temperature conditions.
2. Reduce parameter
39_Speed_Close and
40_Speed_Open
0835 eAuto Setup Failed
This section describes the 800_899_Varidor35_Door_Drive error eAuto

Summary Setup Failed.
- An Error occurred during the auto setup sequence (including auto

Description tuning errors). Further details of the error that caused the failure are
logged to the parameter 184_SetupErrReason and 185_SetupErrValue.
Door Side:
2 = rear door
not applicable
Source ID
ID Possible Actions to be taken

Causes and causes
Actions of
message
1 Many Check Blinking code on HMI and compare with
possible EQ_41350884_01_DoVar35_Commissioning_Diagnostics
causes. (chapter 10.2). OR check Param 184_SetupErrReason:
0: No failure
1: General door error during motion trip -> see
Param_185 for Error Id
2: Door has stopped due to EC command
3: Door has stopped due to a safety device
4: Auto-Setup timeout
5: Equals to Lock Pos Failure according to error handling
specs
6: Equals to KET-S2-Failure according to error handling
specs
7: Data collection in closing direction failed
8: Current control parameters too low (< 0, negative
values)
9: Position control parameters too low < 0, negative
values)
10:Open position too small (< 300mm + Closed Position)
or KET-S2 position too small.
11: Motor polarity detection changed the polarity more
than once.
12: Door mass out of range ( < 10kg or > 300kg) -> see
Param_185 for estimated value.
13: Door closing spring const out of range (< -10N/m or
>200N/m) -> see Param_185 for estimated value
0836 wCAN Messages Too Fast

Summary wCAN Messages Too Fast.
The warning is triggered if two or more messages have been received

Description by the CAN bus within 5 ms. SCAN message sequence processing
cannot be assured in this case. Excluded from this are Parameter
Reads or Writes
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Elevator control acts to fast. No further actions can be
Actions
taken. Elevator control needs
to decrease the frequency of
its command bursts
0837 eLocked Position Failure

Summary eLocked Position Failure.
- Locking jam while locking in referencing mode The Moving distance

Description from KET-S2 closing position (closed) to locked is to small. Distance is
(PosClose - PosLock - 10mm) Only possible while the referencing
mode is active. As an effect, the door is set to Manual state after a
normal stop in order to relieve the clutch
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Mechanical blockage of the 1. Check the clutch's
Actions
clutch mechanical condition;
2. Try to lock and unlock the
door by means of HMI and
examine the clutch
mechanically
3. Run AutoSetup
2 An obstacle or foreign object 1.Remove any foreign object
was placed in the mechanics of and obstacle from the path the
the clutch clutch has to move on
0838 eLocking Jam

Summary eLocking Jam.
If the the clutch locking motion is jamed i.e. the motor is blocked in
Description closing direction the BSKB (blocked while closing) is set.
- BSKB is activated while a motion command is executed in closing
direction if the speed is zero for a defined time. See parameter No. ###
'SensitivityLevel_BlockedDoor_Closing [ms]
Door Side:
2 = rear door
not applicable
Source ID
0839 eUnlocking Jam

Summary eUnlocking Jam.
If the clutch unlocking motion is jammed i.e. the motor is blocked in

Description opening direction the BOKB (blocked while opening) is set.
- BOKB is activated while a motion command is executed in opening
direction if the speed is zero for a defined time. See parameter No. ###
'SensitivityLevel_BlockedDoor_Opening [ms]
Door Side:
2 = rear door
not applicable
Source ID
0840 wNGT 24VDC Over 5% Limit

Summary wNGT 24VDC Over 5% Limit.
The warning is triggered if the power supply 24 VDC exceeds the 5%

Description upper limit. The door drive checks the limit each time entering motion
state Closed.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Incorrect Power Supply 1. Check Power Supply
Actions
Voltage Voltage with X5_24VDC on
DDE-V35 disconnected.
2. Replace if Power Supply
Voltage is > 25V
0841 wNGT 24VDC Under 5% Limit

Summary wNGT 24VDC Under 5% Limit.
The warning is triggered if the power supply 24 VDC falls below the 5%
Description lower limit. The door drive checks the limit each time entering motion
state Closed.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
Actions
Voltage is < 23VDC
2 Abnormal power consumption 1. Check if any load
of the connected load (i.e. door component absorbs power
drive) above its specified value and
check if a replacement of the
component eliminates the
problem. Else:
2. Replace Power Supply
0842 eNGT 24VDC Over 10% Limit

Summary eNGT 24VDC Over 10% Limit.
The error is triggered if the power supply 24 VDC exceeds the 10%
Description upper limit. The door drive checks the limit each time entering motion
state Closed. The door is set to Manual State after a normal stop has
been executed.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 1. Incorrect Power Supply 1. Check Power Supply
Actions
Voltage is > 25V
0843 eNGT 24VDC Under 10% Limit

Summary eNGT 24VDC Under 10% Limit.
The error is triggered if the power supply 24 VDC falls below the 10%
Description lower limit. The door drive checks the limit each time entering motion
state Closed
Door Side:
2 = rear door
not applicable
Source ID

Causes and
Actions
Voltage is < 23VDC
2 Abnormal power consumption 1. Check if any load
of the connected load (i.e. door component absorbs power
drive) above its specified value and
check if a replacement of the
component eliminates the
problem. Else:
2. Replace Power Supply
0844 ePower Door Off

Summary ePower Door Off.
The error is triggered - without an error log entry - if a POWT_OFF is

Description detected.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
Actions
Voltage is < 23VDC
2 JHT/JHCT pressed 1. Check JHT/JHCT Switch if
switched on.
0849 eOver Current

Summary eOver Current.
The current measurement unit of the door drive has detected a current
Description that is out of the range of measurement which is about 19A. The power
stage is disabled immediately i.e. the door state is manual
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Short circuit in the motor 1. Replace the unit and return
Actions
winding or Damaged power it to the factory for examination
stage of the door drive
2 Too high controller gains 1. Run AutoSetup
(velocity control parameter set;
Position control parameter set)
3 Profile acceleration and/or 1. Run AutoSetup
profile deceleration too high 2. Reduce parameter
39_Speed_Close and
40_Speed_Open
0850 eOver Voltage

Summary eOver Voltage.
This Error is raised when the input voltage of the power supply is
Description >30V. This error is raised in any position.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Too much energy is fed back 1. Run AutoSetup
Actions
from the motor during a 2. Reduce parameter
deceleration phase 39_Speed_Close and
40_Speed_Open
2 The power supply is damaged 1. Replace power supply
3 Oscillation of the mechanical 1. Check belt tension
system (mass/belt) that leads 2. Run AutoSetup
to energy pulsation of energy
0851 eUnder Voltage

Summary eUnder Voltage.
This error will never occur because Error Door Power Off and NGT
Description 24VDC Under 10% Limit suppress and substitute it.
Door Side:
2 = rear door
not applicable
Source ID
0852 eDoor Drive Over Temperature

Summary eDoor Drive Over Temperature.
This error indicates that the destruction temperature of the door drive
Description (electronics and/or motor has been reached. In order to prevent
damage of the part the power stage is disabled immediately but a
MotGenStop can still be executed if necessary.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Increased friction due to 1. Check the mechanical
Actions
ageing or damage of the fitness of the door
mechanical components 2. Check especially if there is
an increased friction.
3. Replace parts that cause the
friction
4. Run AutoSetup
2 Strong closing springs with 1. Reduce open-hold-time or
high demanding forces at 2. Reduce pre-tension of
opened position. And/Or: Very closing spring
high door mass in conjunction 3. Only if no stong closing
with frequent motion changes . spring: Reduce parameter
39_Speed_Close and
40_Speed_Open
3 The power stage exhibits a 1. Check environmental
high temperature conditions.
2. Reduce parameter
39_Speed_Close and
40_Speed_Open
0855 eInternal Software

Summary eInternal Software.
An internal Software error has occurred.

Description
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 An unknown event set the 1. Restart door drive by
Actions
door drive to a state where the pluging off POWT and CANT
determinate behaviour of the (DOOR) on OKR.
system cannot be guaranteed
anymore
0856 eSoftware Internal Parameter

Summary eSoftware Internal Parameter.
Too high Target position with too low Profile velocity

Description
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Extreme motion profile 1. Check if a parameter was
Actions
parameters changed recently. If yes,
change it back to default value.
2. Run AutoSetup
0857 eSensor Position

Summary eSensor Position.
The detected position from position sensor is no longer valid in case of:
Description - Changed Position Sensor Parameters
- Wrong Position Sensor Parameters
- Other Errors which influences the absolute position detection (Hall
Sensor Error,
Encoder Index Error, ...)
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 DDE-V35 encoder has 1. Reset DDE-V35 by shortly
Actions
encountered an error. plugging of POWT and CANT
(DOOR) on OKR.
2. Run AutoSetup
0858 eCAN Overrun

Summary eCAN Overrun.
One of the CAN mail boxes had a overflow because of too high
Description communication rate
- (Objects lost)
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 A lot of events that cause 1. Check CAN Cable
Actions
messages to be transferred 2. Check CAN Communication
have been triggered
synchronously This error may
indicate that the SCAN
connection has been
disconnected and/or connected
again. The elevator control
transmits a burst of unjustified
messages to the door drive.
The door drive does not
operate with full performance
due to an internal problem.
0863 eCAN Bus Off

Summary eCAN Bus Off.
The CAN Controller has entered CAN bus off state

Description
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 A defective or unplugged 1. Check CAN Cable
Actions
wiring of the CAN bus connection
connection between door drive
and elevator control
0864 eCAN Rx Queue Overflow

Summary eCAN Rx Queue Overflow.
One of the CAN receive queues had a overrun because of too high
Door Side:
2 = rear door
not applicable
Source ID

Causes and
Actions
have been triggered
synchronously. This error may
connection has been
again. The elevator control
transmits a burst of unjustified
messages to the door drive.
The door drive does not
operate with full performance
due to an internal problem.
0865 eCAN Tx Queue Overflow

Summary eCAN Tx Queue Overflow.
One of the CAN transmit queues had a overrun because of too high
Door Side:
2 = rear door
not applicable
Source ID

Causes and
Actions
have been triggered
synchronously. This error may
connection has been
again. The door drive
generates a burst of messages
due to the detection of errors
or due to erroneous behaviour.
0867 ePosition Following

Summary ePosition Following.
The difference between Position demand value and Position actual

Description value is higher then
Maximal following error
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 An obstacle that slows down or Check for obstacles or blocking
Actions
stops the door (only possible if situations, challenge the
force limit detection application setting of KOKB,
KSKB/KOKB are disabled) KSKB
0868 eHall Sensor
This section describes the 800_899_Varidor35_Door_Drive error eHall

Summary Sensor.
The motor hall sensors report an impossible signal combination.

Description
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Damaged hall sensors of the If error repeats, replace DDE-
Actions
motor or high level of noise on V35
the signal .
0869 eIndex Processing

Summary eIndex Processing.
The encoder index signal was not found within two turns at start-up.
Description This error can only be triggered with a setting of encoder type 1 which
is not usual for the door drive because the default encoder type of the
door drive is 2.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Unknown If error repeats, replace DDE-
Actions
V35
0870 eEncoder Resolution

Summary eEncoder Resolution.
The encoder pulses counted between the first two index pulses doesn’t
Description fit to the resolution:
- Setting of encoder resolution (Sensor Configuration) is wrong
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Wrong encoder resolution set. 1. Reset DDE-V35 by shortly
Actions
plugging-off POWT and CANT
on OKR.
2. Restore all default
parameters by SMLCD
3. If error occurs again:
Replace DDE-V35
0874 eHall Angle Detection
This section describes the 800_899_Varidor35_Door_Drive error eHall

Summary Angle Detection.
The angle difference measured between encoder and hall sensors is

Description too high.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Wrong setting of encoder 1. Reset DDE-V35 by shortly
Actions
resolution or pole pair number plugging-off POWT and CANT
or Defective encoder or hall on OKR.
sensor 2. If error occurs again:
Replace DDE-V35
0875 eSoftware Position Limit

Summary eSoftware Position Limit.
Movement commanded or actual position higher than maximum

Description position limit or lower than minimum position limit (Software position
limit). For the door drive the position limits are set to the most extreme
values, thus this error should never occur.
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 Unknown 1. Reset DDE-V35 by shortly
Actions
on OKR.
Replace DDE-V35
0876 ePosition Sensor Breach

Summary ePosition Sensor Breach.
The position sensor supervision has detected a bad working condition.

Description This error will hardly be triggered in the door drive because the HW is
not able to detect sensor breaches. This is no problem because the
sensor is supervised by hall sensors and additionally an EC motor is
not able to rotate without proper position sensor signals
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 1. Unknown 1. Reset DDE-V35 by shortly
Actions
on OKR.
Replace DDE-V35
0877 eSystem Overloaded

Summary eSystem Overloaded.
The device has not enough free resources to process the new target
Description value
Door Side:
2 = rear door
not applicable
Source ID

Causes and
1 1. The device has not enough 1. Reset DDE-V35 by shortly
Actions
free resources to process the plugging-off POWT and CANT
new target value on OKR.
Replace DDE-V35
0900 IOH Error Base
This section describes the IO error IOH Error Base.

Summary
Description
Extra Info
Source ID
0901 ConfigErr
This section describes the IO error ConfigErr.

Summary
PIOG CONFIGURATION DATA ERROR. The PIOG print did not

Description receive all the configuration data, or the data contained invalid values.
01 = No response to PCT version number request

Extra Info 02 = No parameters or incomplete parameter list received from
controller
03 = No I/O definition or incomplete I/O definition received from
controller.
04 = Received parameters contain invalid values.
05 = Received I/O definitions contain invalid values.
06 = The local PCT checksum is not consistent with data checksum.
07 = No error, internal message that the cabine print has requestet a
new configuration.
08 = No error, internal message that the cabine print has received a
new configuration.
None.
Source ID

Causes and
1 Pcb 'PIOG' ID switch not set Check ID switch on PIOG.
Actions
correctly.
2 Configuration data not Check group bus connection.
received
0902 PIO Error
This section describes the IO error PIO Error.

Summary
One of the components, which are connected to the Lift Control,

Description reports a fault.
Points out the false component.

Extra Info 01 = IOBUS detects no periphery
02 = PCB supply below error limit
03 = PCB supply below warning limit
Meaning: The function of the indicated component is disturbed. (f.e.
IOBUS cable defect)
None.
Source ID

Causes and
1 Check the indicated
Actions
components and if necessary
change them
2 Check the wiring of the
described component
0903 IO Table Overflow
This section describes the IO error IO Table Overflow.

Summary
The software detects an overflow in one of the following data tables

Description handled by the core software.
1: ascii_table
2: message_table
3: table melody
4: table pin_to_floor
5: table ga_volume
6: table access_request
7: table io_sdb[]
The extra info value identifies the table and the index value that
Extra Info caused the overflow.
Interpretation of extra info value xAABBCCDD:

AA: Table number (see description)
BB: index number
CC: not used (00)
DD: not used (00)
Identifies the source code file that caused the data overflow.
Source ID

Causes and
1 Wrong configuration section in Check PCT
Actions
PCT
2 Configuration out of range Check application limits
3 Problem in software with table Report to R&D Ebikon
limits
0904 IO_Missing
This section describes the IO error IO_Missing.

Summary
During startup the elevator control checks if IO's which are required for
Description the safe operation of the elevator are configured. Today IO's like
JREC, DREC-U and DREC-D are in the list of such IO's. If these IO's
are not present, then the control software will not allow normal
operation of the elevator (NORMAL).
The user needs to check why the IO's are missing and fix the problem.
The value is used to identify the missing input/output signal.

Extra Info
x00000001 (Bit0): Input JREC not configured
x00000002 (Bit1): input DREC-D not configured
x00000004 (Bit2): Input DREC-U not configured
None.
Source ID

Causes and
1 Error in PCT (for TX-GC, TX- Correct error in IO
Actions
M10, TXR5) configuration section of the
PCT
2 Harware problem with Replace interface board
hardware interface pcb for
related IO (see extra info
value)
0905 COP Configuration Error
This section describes the IO error COP Configuration Error.

Summary
Wrong configuration of COP node (LONCOP or LONCPI). Number of

Description car calls found on SPI chain is zero.
xABCDEFGH (8 digit hex number)

Extra Info
AB (Byte 3): Subnet address
CD (Byte 2): Node address
EF (Byte 1): Node id
G (Byte 0/Upper nibble): Side
H (Byte 0/Lower Nibble) -> Bit 0(1 = LSB): left column flag
H (Byte 0/Lower Nibble) -> Bit 1(2): middle column flag
H (Byte 0/Lower Nibble) -> Bit 2(4): right column flag
H (Byte 0/Lower Nibble) -> Bit 3(8 = MSB): Unused
None.
Source ID

Causes and
1 Problem with hardware Check COP interface board
Actions
and connections of connected
boards (NWxxx)
0906 Duplicate_BMK
This section describes the IO error Duplicate_BMK.

Summary
The software detects that a input signal is configured more than once
Description on the same lift. This is not allowed. In case the software finds a
duplicate entry in the internal IO database for such a signal (e.g. for a
critical input) an error will be logged for each entry in the database.
The software performs the check each time a node is detected on the
bus. The first number in the extra info indicates the sequence of the
entries in the IO database (the same BMK may be configured twice on
the same node).
Remark: Some configurable lift signals are allowed to be defined more

than once on the same lift (e.g. DT-O). The software will handle such
signals so that the related function is active whenever one of the
signals is on.
The following signals may not be configured multiple times on a

elevator.
hex code, BMK name

0x0017, "JBFFG"
0x0018, "JBFFGH1"
0x0019, "JBFFGH2"
0x001A, "JBFH1"
0x001B, "JBFH2"
0x0021, "JBFL"
0x0032, "JBFF"
0x0038, "JNFF"
0x0039, "JNFF-S"
0x0044, "KBFF"
0x0045, "KGEB"
0x004A, "KTHMF"
0x004F, "KBFEH"
0x0051, "KBFEL"
0x0058, "KKSA"
0x0059, "JNFFH1"
0x005A, "JNFFH2"
0x0063, "JBF"
0x0070, "KBF"
0x0071, "KBFH1"
0x0072, "KBFH2"
0x0073, "KBFH3"
0x0074, "KEB"
0x0078, "RNO"
0x0084, "JBFLH1"
0x009F, "JBFLH2"
0x00B4, "KBFM"
0x00E8, "JBFFH1"
0x00E9, "JBFFH2"
0x00F0, "JNFFP"
0x00FD, "KGS1"
0x00FE, "KGS2"
0x0104, "KUESG"
0x0105, "KUESG1"
0x0109, "KTL"
0x010B, "KSE-U"
0x010C, "KSE-D"
0x0110, "KB"
0x0111, "KB1"
0x0226, "KSKHWA"
0x026B, "KSKBLDG"
0x026C, "KSKLBY"
0x026E, "KSKMR"
0x026F, "KSKMRA"
0x0272, "RNO2"
0x02F3, "RNOPRW"
0x02F4, "RNOPRW2"
0x0302, "KUEHC"
0x0308, "JBFR"
0x030F, "JBF1"
0x0311, "JBFR1"
0x0317, "KL-RX"
0x0318, "KSKB"
0x0322, "PHT"
0x0327, "KACZB"
0x0328, "KACZT"
0x0334, "KSSBV"
0x034C, "IKVK"
0x0367, "KEBVL"
0x0368, "KEBL"
0x0369, "KEBH"
0x036B, "JEB"
0x036C, "JEBFE"
0x0373, "JZHPK"
0x0400, "DA"
0x0409, "RUM_I"
0x040A, "RUM1_I"
0x040B, "IBCL"
0x0415, "KRUET"
0x0416, "KRUET1"
0x041E, "IBCLC"
0x0426, "IRUEHC"
0x0427, "IRUEHC1"
0x042B, "IRUM"
0x042C, "IRUM1"
0x042D, "IRUMD-E"
0x042E, "IRUM1D-E"
0x042F, "IRUML-E"
0x0430, "IRUM1L-E"
0x1F02, "KUENA"
0x1F03, "KUENA1", },
0x1F06, "KUETFF", }
Identifies the board/node type of the bus node on which the same
Extra Info BMKs are configured and the signal (4 digit hex code).
xABCDEFGH (8 digit hex number) where:
A: is the index number of the entry in the internal IO database

B: Identifies the IO Domain
CD: Node type
EF: Higher byte of BMK code (e.g. 00 for JBF)
GH: Lower byte of BMK code (e.g. 63 for JBF)
Remark: on SW version released before Aug. 2010 the number
(EFGH) indicates the node id and not the BMK code.
(A) Identification numbers of the sequence number:

1: first found node entry in the IO database
2: other node entry in the database
(B) Identification numbers of the IO Domains:

1: IO_DOMAIN_LOCAL
2: IO_DOMAIN_LON
3: IO_DOMAIN_BIO2
4: IO_DOMAIN_CAN
(CD) For explanation of the LON node types (IO_DOMAIN_LON)

please refer to the description of error 1209.
(CD) Identification numbers ob BIO bus node types

(IO_DOMAIN_BIO2):
0x00: SLOP2 /*BIO1 Node*/
0x02: SLOPM2 /*BIO1 Node used for first tests with BIO2*/
0x04: SLIN2 /*BIO1 Node*/
0x05: SLOPB1 /*BIO1 Node*/
0x07: SLOPSASB1 /*BIO1 Node*/
0x09: SLOPBM1 /*BIO1 Node*/
0x0A: SLOPBSASM1 /*BIO1 Node*/
0x0B: SLCU1 /*BIO1/BIO2 Node*/
0x0C: SLCUM1 /*BIO1/BIO2 Node*/
0x0D: BIOPCSE /*BIO2 Node*/
0x0E: BIODCE /*BIO2 Node*/
0x0F: SLCUX /*BIO2 Node*/
0x10: BIOPCT1 /*BIO2 Node*/
0x11: BIODCT1 /*BIO2 Node*/
0x12: BI2SCT1MCT1 /*BIO2 Node*/
0x13: BI2NCT1MDT1 /*BIO2 Node*/
0x16: SLOPM51 /*BIO1 Node*/
0x1A: SLINV5 /*BIO1 Node*/
0x1B: CLIF1 /*BIO2 Node*/
0x1C: SLOPE51
0x1D: SLOPE52
0x1E: SLOPEB51
0x1F: SLOPEB52
0x20: SLOPDMA5
0x21: BIOAPI1
0x22: SLINK5
0x23: PSI1
0x24: BIO2_LOP
0x25: BIOGIO1
0x26: SLOPNA51_53
0x27: SLOPNA52_54
0x28: SLOPMAT1
0x29: SLOPEBH5
0x2A: SLINVNA51
0x2B: SLINVNA52
0x2C: SLCUX2
0x2D: BLOPG11
0x2E: BLOPG12
0x2F: BLOPILG1
0x30: BLOPIHG1
0x31: BLINVLG1
0x32: BLINVHG1
0x33: BLINHHG1
(CD) Identification numbers of CAN bus node types

(IO_DOMAIN_CAN):
0x6A (106) CANIC
0x6C (108) COP
0x6D (109) CANGIO
0x6E (110) ZLFB
(EFGH) Identification numbers ob BMK: see list in error description

Identification number of the SW task (IOC_TASK_ID)
Source ID

Causes and
1 Bad IO configration (same Check configured IOs on the
Actions
signal configured twice or interface boards with SMLCD
more). or CADI and modifiy
configuration so that the signal
acc. to the extra info value is
only set once on the control.
0910 COM_Busreconf
This section describes the IO error COM_Busreconf.

Summary

longer guaranteed.

None.
Source ID

Causes and
1 Bus is faulty Check lift -, groupbus: all
Actions
links and terminators are
functional.
connected with the bus.
addresses
and check if the
Center.
0920 PCT IO Section Checksum
This section describes the IO error PCT IO Section Checksum.

Summary
Checksum error when reading IO section of the PCT.

Description
Extra info: 0xAABBCCDD where

Extra Info
AA: PCT_IO_ID (hex)
BB: checksum value (hex)
CC: PCT Parameter Version Byte from shopkeeper rules
DD: System parameter version number (It is by default set to one. But
when new data is defined in PCT_GP_PCT, PCT_GP_SCT,
PCT_GP_SYSTEM or PCT_GP_LIFT then it will init a new version
number).
None.
Source ID
0921 PCT Parameter Section Checksum
This section describes the IO error PCT Parameter Section Checksum.

Summary
Checksum error when reading the PCT_PARAMETER_GROUP

Description section of the PCT.
Extra info: 0xAABBCCDD where

Extra Info
AA: PCT_IO_ID (hex)
BB: Checksum value (hex)
CC: PCT Parameter Version Byte from shopkeeper rules
DD: System parameter version number (It is by default set to one. But
when new data is defined in PCT_GP_PCT, PCT_GP_SCT,
PCT_GP_SYSTEM or PCT_GP_LIFT then it will init a new version
number).
None.
Source ID
0922 VCOM Request
This section describes the IO error VCOM Request.

Summary
VCOM request by 'ioc task' failed

Description
Identifies the VCOM messages for which the request command failed
Extra Info Extra info: 0xAABBCCDD where:
AA: VCOM Telegram Group Number

BB: VCOM Telegram Id
CC: VCOM attribute 1
DD: VCOM attribute 2
None.
Source ID
0923 VCOM Provide
This section describes the IO error VCOM Provide.

Summary
VCOM provide by 'ioc task' failed

Description
Identifies the VCOM messages for which the provide command failed
Extra Info Extra info: 0xAABBCCDD where:
AA: VCOM Telegram Group Number

BB: VCOM Telegram Id
CC: VCOM attribute 1
DD: VCOM attribute 2
None.
Source ID
0924 Board Configuration Error
This section describes the IO error Board Configuration Error.

Summary
Invalid configuration on a peripheral interface board. Setting for floor

Description outside of range. On plug & play LON interface boards floor setting '00'
is not allowed (e.g. LONIOC3)
8 digit hex value: 0xABCDEFGH where:

Extra Info
A: Channel Number (1 for LON Channel 1, 2 for LON Channel 2, 3 for
LOCAL Channel, 4 For BIO etc...)
B: Side setting
CD: Node Type (hex value)
EF: Upper byte of node Id (hex value)
GH: Lower byte of node Id (hex value)
CD) For explanation of the LON node types (IO_DOMAIN_LON)


(IO_DOMAIN_BIO2):
0x1C: SLOPE51
0x1D: SLOPE52
0x1E: SLOPEB51
0x1F: SLOPEB52
0x20: SLOPDMA5
0x21: BIOAPI1
0x22: SLINK5
0x23: PSI1
0x24: BIO2_LOP

(IO_DOMAIN_CAN):
0x6A (106) CANIC
0x6C (108) COP
0x6D (109) CANGIO
0x6E (110) ZLFB
None.
Source ID
0925 IO_reserve_925
This section describes the IO error IO_reserve_925.

Summary
Description
8 digit hex value: 0xABCDEFGH where:

Extra Info
A: Channel Number (1 for LON Channel 1, 2 for LON Channel 2, 3 for
LOCAL Channel, 4 For BIO etc...)
B: Side setting
CD: Node Type (hex value)
EF: Upper byte of node Id (hex value)
GH: Lower byte of node Id (hex value)
CD) For explanation of the LON node types (IO_DOMAIN_LON)


(IO_DOMAIN_BIO2):
0x1C: SLOPE51
0x1D: SLOPE52
0x1E: SLOPEB51
0x1F: SLOPEB52
0x20: SLOPDMA5
0x21: BIOAPI1
0x22: SLINK5
0x23: PSI1
0x24: BIO2_LOP

(IO_DOMAIN_CAN):
0x6A (106) CANIC
0x6C (108) COP
0x6D (109) CANGIO
0x6E (110) ZLFB
None.
Source ID
0951 IO_Configuration_Error
This section describes the IO error IO_Configuration_Error.

Summary
The software detects a problem with the configuration of the

Description inputs/outputs. May be caused by:
- an error in the IO configuration in the PCT (TX-GC/TXR5)

- a conflict when the software adds BMK's to the internal IO database
(MX-GC/TX-GC2)
Configuration of IO's with TX-GC/TXR5: in PCT with separate IO

section
Configuration of IO's with MX-GC/TX-GC2: plug & play (LON) interface
boards with setting of rotary switches for BMK code. In addition
parameter are used to configure IO in case of special needs.
x02000200: Problem retrieving information from BMK name

Extra Info x02aabbcc: Invalid entry in PCT section PCT_INPUT_OUTPUT or
wrong parameter value for parameter IO_BMK_SET (aa:node_id;
bb:ioType;cc:pinID)
xdddddddd: Problem reading PCT (dddddddd: subsys_id)
x03aabbcc: Problem retrieving VCOM Telegram for configuration (aa:
not used ; bbcc BMK Code)
Identification of task (source code).

Source ID 82(dec): IOC_TASK

Causes and
1 Incorrect IO configuration in Check/correct PCT
Actions
PCT (TX-GC/TX-R5)
2 Incorrect configuration of Verify correct configuration of
peripheral IO interface boards configurable IO interface
boards.
3 Incorrect value for parameter Modify parameter
IO_BMK_SET (TX-GC2 / MX)
0952 EEP_BurnProbl
This section describes the IO error EEP_BurnProbl.

Summary
Malfunction burning EEPROM-Page

Description
None.
Extra Info
None.
Source ID

Causes and
1 Call EBI for EEPROM
Actions
replacement (new
configuration)
0953 Deployment_Rule_Failure
This section describes the IO error Deployment_Rule_Failure.

Summary
Software detects wrong system configuration based on the deployment

Description rules.
Mod. 18.02.2004 New error Id. (old Id. 971)
1: Error_Bus_Architecture. Incorrect bus architecture type set in PCT.

Extra Info Check PCT parameter "PCT_GP_BUS_SYSTEM"
2: Error_IO_PCT_Config_Not_Allowed. System does not allow IO

configuration through PCT.
3: Error_IO_PNP_Config_Not_Allowed. The system detects a plug and

play board but does not allow Plug and Play IO configuration.
4: Error_IO_BIO_Config_Not_Allowed. The system detects a BIO

interface board but does not allow BIO nodes.
5: Error_IO_Invalid_Config_Type. Invalid Configuration detected.
None.
Source ID

Causes and
1 Wrong or missing hardware Remove inappropriate
Actions
installed or connected. hardware.
2 Wrong PCT parameter value Check/modify PCT parameter
PCT_GP_BUS_SYSTEM
3 Incorrect PCT downloaded TX: Check/modify PCT
(remove IO section in case of
plug and play interface
boards).
MX: trigger a new chip card
expansion in order to create a
a valid PCT.
Rem: on MX controls
(Rel.1/2/3 and Rel.4/2.41) the
uploaded PCT contains a
dummy I/O section. If such a
PCT is downloaded to a MX
Rel.4 the software will detects
this.
0954 Freeze Table Invalid Entry
This section describes the IO error Freeze Table Invalid Entry.

Summary
Board type mismatch found while expanding the IO freeze database.

Description The affected board should be displayed as connected (blue in CADI
node overview screen).
8 digit code AABBCCDD where:

Extra Info
AA: 01 (always)
BB: Channel ID
CC: Node ID
DD: not used
Values for BB (Channel ID):

00 = CHANNEL_NONE, ANY_CHANNEL
01 = CHANNEL_1, LIFT_LON
02 = CHANNEL_2, GROUP_LON
03 = LOCAL_CHANNEL
04 = BIO2_CHANNEL
05 = CAN_CHANNEL
06 = CAN_SHAFT_CHANNEL
None.
Source ID

Causes and
1 Internal type mismatch Check that the board is
Actions
displayed as connected (blue)
and perform a freeze
command.
Remark: for every error
message a board must be
displayed as connected (blue)
0961 EEP_BurnPrbl
This section describes the IO error EEP_BurnPrbl.

Summary
refer to description for error number 952.

Description
None.
Extra Info
None.
Source ID
0970 Timer Error
This section describes the IO error Timer Error.

Summary
The IO-Handler has detected a problem with a timer (i.e. timer could
Description not be started). Internal software error.
01: timer for 'send IOH-Availability prio-ready' was not started

Extra Info 02: timer for 'send IOH-Availability fully-ready' was not started
None.
Source ID

Causes and
1 Internal software error Use other software version and
Actions
report exact error message.
0971 IO_VCOM Telegram Missmatch
This section describes the IO error IO_VCOM Telegram Missmatch.

Summary
The IO-Handler detected a wrong received VCOM telegram. This is an

Description Internal software error. The VCOM Telegram and the corresponding
BMK don't match.
The consequence can be:

- non activaton of an output
- no reaction to an input change
Identifies the VCOM messages for which the handling failed.

Extra Info 8 digit hex value: 0xABCDEFGH where:
ABCD is the VCOM Telegram Group
EFGH is the VCOM Telegram Id
None.
Source ID

Causes and
Actions
Ebikon.
logged in the log together with
the SW version. These are
clues for the software
specialist to detect the source
of the problem.
1000 Bus Error
This section describes the CPU error Bus Error.

Summary
The CPU attempted to read/write to a memory address that does not

Description exist, read/write access is not allowed, or the ~BERR signal was
asserted to the CPU.
This error is reported if a more specific cause for the bus-error error
cannot be determined. Normally, a more specific reason for the bus-
error can be determined by the software. See also:
1057 BErr Prefetch
R&D use. (Program counter)

Extra Info
R&D use.
Source ID

Causes and
1 Save all error and event logs
Actions
and report to supplier hotline or
R&D
hint: save logs to SDcard with
GCIOCF SW v10.07.xx and
newer
2 EMC problems Check for strong EMC source
in the building.
voltage cables, for example,
the power supply cables of the
brake.
4 Make sure that the pcb's
ground and mass connections
are properly done.
5 Check all of the ground and
mass connections in the
cabinet
6 Defective PCB Replace PCB
1001 Address Error
This section describes the CPU error Address Error.

Summary
The CPU attempted a 16/32 bit read/write data or instruction fetch at

Description an odd address in a situation that only aligned access is possible.
R&D use (Program counter)

Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
1002 Illegal Instruction
This section describes the CPU error Illegal Instruction.

Summary
The (CPU) has fetched an illegal or inimplemented instruction, or a

Description permament breakpoint instruction, such as ILLEGAL or BGND. This
can also happen when attempting to execute Floating-point
Coprocessor, cache, or memory management instructions on a
processor that does not support these features, or if the co-processor
is not functioning. For example, the 68360 can execute some 68020
instructions, but the 68000 cannot. Coldfire (MCF5475) implements
most but not all 68000 instructions.
Other instructions are reserved by Motorola/Freescale for future
68xxx/MCF5xxx family processors.
Illegal instructions A000-AFFF are generally reported with error 1020

"Line1010"
Illegal instructions F000-FFFF are generally reported with error 1021
"Line1111"

Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
2 defective HW Check GCIO and flash SIMM
version
1003 Zero Divide
This section describes the CPU error Zero Divide.

Summary
A division by 0 has been encountered by the CPU.

Description
Return Program counter value after the fault

Extra Info
None.
Source ID

Causes and
Actions
R&D
Remark: save logs to SDcard
with GCIOCF SW v10.07.xx
and newer
1004 CHK Instruction
This section describes the CPU error CHK Instruction.

Summary
The value is outside of the valid range verified by the CHK or CHK2
Description instruction of the CPU.

Extra Info
None.
Source ID

Causes and
Actions
R&D
and newer
1005 TRAPV Instruction
This section describes the CPU error TRAPV Instruction.

Summary
Overflow exception detected by the FTRAPcc, TRAPcc, TRAPV of the

Description CPU.
Return Program counter after the fault

Extra Info
None.
Source ID
1006 Privilege Violation
This section describes the CPU error Privilege Violation.

Summary
The CPU tries executing a privileged instruction in user mode. This

Description includes instructions such as ANDI-SR, ORI-SR, MOVE-SR, MOVE-
USP, LPSTOP, RESET, MOVEC, MOVES and RTE.
All task-level software executes in User Mode, while the multitasking
operating system and device drivers execute in Supervisor mode.
R&D use(Program counter)

Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
1007 TRACE
This section describes the CPU error TRACE.

Summary
The CPU is in trace mode (for single stepping)

Description

Extra Info
None.
Source ID
1008 Uninitialized Int Vect
This section describes the CPU error Uninitialized Int Vect.

Summary
A device is attempting to interrupt the CPU, but its interrupt vector

Description register has not yet been initialised. This is only possible with devices
that have a programmable interrupt vector register. And do not use the
autovector mechanism.

Extra Info
None.
Source ID
1009 Spurious Interrupt
This section describes the CPU error Spurious Interrupt.

Summary
There is a glitch on an IRQ signal: An IRQ signal is asserted, but

Description deactivated before the CPU interrupt acknowledge cycle can process
it. This can be caused by a HW glitch on the IRQ signal, or else by SW
that masks or disables an interrupt at the same time as comes.

Extra Info
R&D use
Source ID

Causes and
1 HW defect Check that the CPU and
Actions
ASILxxx / ASIXxxx / CRIPxxx
board is the latest revision
R&D
newer
1010 TRAP Instruction
This section describes the CPU error TRAP Instruction.

Summary
Trap instruction (CPU executes from a predefined address)

Description

Extra Info
None.
Source ID
1011 User Interrupt Vector
This section describes the CPU error User Interrupt Vector.

Summary
User defined interrupt vector of the CPU.

Description

Extra Info
Vector number.
Source ID

Causes and
Actions
R&D
and newer
1012 Stuck IRQ
This section describes the CPU error Stuck IRQ.

Summary
A hardware interrupt request signal remains active too long

Description
None.
Extra Info
None.
Source ID
1013 Task Create
This section describes the CPU error Task Create.

Summary
The operating system failed to create a task/thread. This can result in

Description unreliable behavior.
Task number of the task which the operating system failed to create.
Extra Info
Reg_TaskID [dec.53]
Source ID
1014 Queue create
This section describes the CPU error Queue create.

Summary
The operating system failed to create a queue for the application. This
Description can result in unreliable behavior.
None.
Extra Info
None.
Source ID
1015 Operating system RTEMS
This section describes the CPU error Operating system RTEMS.

Summary
CPU reset caused by operating system (RTEMS).

Description
Function calling: 'rtems_fatal_error_occurred' directive or
'Internal_error_occurred' directive due to an irrecoverable error.
R&D use only

Extra Info
This is the type indicator and is dependent upon the source of the
error. Possible error causes:
0(dec): INTERNAL_ERROR_NO_CONFIGURATION_TABLE
1(dec): INTERNAL_ERROR_NO_CPU_TABLE
2(dec): INTERNAL_ERROR_INVALID_WORKSPACE_ADDRESS
3(dec): INTERNAL_ERROR_TOO_LITTLE_WORKSPACE
4(dec): INTERNAL_ERROR_WORKSPACE_ALLOCATION
5(dec): INTERNAL_ERROR_INTERRUPT_STACK_TOO_SMALL
6(dec): INTERNAL_ERROR_THREAD_EXITTED
7(dec): INTERNAL_ERROR_INCONSISTENT_MP_INFORMATION
8(dec): INTERNAL_ERROR_INVALID_NODE
9(dec): INTERNAL_ERROR_NO_MPCI
10(dec): INTERNAL_ERROR_BAD_PACKET
11(dec): INTERNAL_ERROR_OUT_OF_PACKETS
12(dec): INTERNAL_ERROR_OUT_OF_GLOBAL_OBJECTS
13(dec): INTERNAL_ERROR_OUT_OF_PROXIES
14(dec): INTERNAL_ERROR_INVALID_GLOBAL_ID
15(dec): INTERNAL_ERROR_BAD_STACK_HOOK
16(dec): INTERNAL_ERROR_BAD_ATTRIBUTES
R&D use only

Source ID
Identifies the API (application program interface) responsible for the
fatal or internal error.
0: INTERNAL_ERROR_CORE
1: INTERNAL_ERROR_RTEMS_API
2: INTERNAL_ERROR_POSIX_API
3: INTERNAL_ERROR_ITRON_API

Causes and
1 Faulty processor board Replace processor board of
Actions
control
2 Error in software Download other version of
software (this error should not
occur on a released version)
R&D
newer
1016 New Config Reset
This section describes the CPU error New Config Reset.

Summary
The CPU is reset as a normal part of the configuration (download)

Description process. This is a normal event when downloading a PCT or SCT or
when inserting a chip card (MX). This reset makes sure the new
parameters are read as part of a clean start of the software, and any
old parameters are no longer in effect.
Identifies the case in the configuration process that required the reset
Extra Info (For R&D internal use)
Task identification number (depends on the SW version; for R&D

Source ID internal use)

Causes and
1 Chipcard expansion or new no error
Actions
PCT/SCT loaded
1017 Event Handler Reset
This section describes the CPU error Event Handler Reset.

Summary
The CPU is reset because another error with the error severity set to
Description "RESET" occurs. The severity "RESET" for an error will cause the
CPU to be reset, and the event 'CPU Event Handler Reset' will be
reported once the system restarts. The causing error itself will normally
be logged before the reset happens.
(Note: "CPU" errors 1000-1199 always report the reason for a reset
AFTER it has happened.)
Identifies the case in the event handler process that required the reset
Extra Info (For R&D internal use)


Causes and
1 An error with severity 'reset' is Check the action of the other
Actions
logged error with 'reset' severity
1018 Appl. Requested Reset
This section describes the CPU error Appl. Requested Reset.

Summary
The CPU was reset at the request of the normally running software.
Description Resets due to errors or software failures are reported and logged by
other CPU error ID's.
Identifies the case in the application that required the reset (For R&D
Extra Info internal use)


Causes and
1 SW initiated a reset as an no error
Actions
intended part of normal
operation
2 R&D SW development no error
environment: debug command
1019 Memory Allocation Failure
This section describes the CPU error Memory Allocation Failure.

Summary
The SW was unable to allocate a required amount of memory space.

Description One or more error message 1072 "saved registers may be logged as
well and provide further information about the circumstance of the
error.
Information depending on SW version.

Extra Info
None.
Source ID

Causes and
1 CADI-GC VCOM If CADI-GC is connected,
Actions
Communication loaded at unplug CADI-GC or reduce
100% for a long time. requested information at CADI-
GC.
2 Long term disturbance at Check environment for EMC
VCOM bus cables. sources. Check VCOM bus
grounding and connections.
3 CPU loaded at 100% for a long Check SW release notes for
time. known problems and update
SW if proposed.
This section describes the CPU error Line1010 Instruction Emulation.

Summary
The CPU tried to execute a illegal or unimplemented instruction,

Description opcodes A000-AFFF.

Extra Info
R&D use
Source ID

Causes and
1 defective HW Check GCIO and flash SIMM
Actions
version
This section describes the CPU error Line1111 Instruction Emulation.

Summary
The CPU tried to execute an illegal or unimplemented instruction,

Description opcodes F000-FFFF.

Extra Info
R&D use
Source ID

Causes and
1 Defective HW Check GCIO and flash SIMM
Actions
version
1022 HW Breakpoint
This section describes the CPU error HW Breakpoint.

Summary
The breakpoint signal was asserted to the CPU

Description

Extra Info
None.
Source ID
1023 FP protocol violation
This section describes the CPU error FP protocol violation.

Summary
The floating-point coprocessor protocol to the CPU was violated.

Description

Extra Info
None.
Source ID
1024 Format error
This section describes the CPU error Format error.

Summary
The CPU detected that the interrupt or exception stack frame was
Description corrupted (When executing an RTE instruction)

Extra Info
None.
Source ID
1025 Reserved interrupt
This section describes the CPU error Reserved interrupt.

Summary
The CPU jumped a reserved interrupt vector. These vectors are

Description reserved by Motorola for future expansion and should not be used.

Extra Info
None.
Source ID
1026 Autovector 1
This section describes the CPU error Autovector 1.

Summary
The CPU was interrupted by a external device connected to IRQ1, but

Description the Exception Vector Table has not been initialized by the device driver
for that device.

Extra Info
None.
Source ID
1027 Autovector 2

Summary

for that device.

Extra Info
R&D use
Source ID
1028 Autovector 3

Summary

for that device.

Extra Info
R&D use
Source ID
1029 Autovector 4

Summary

for that device.

Extra Info
R&D use
Source ID
1030 Autovector 5

Summary

for that device.

Extra Info
R&D use
Source ID
1031 Autovector 6

Summary

for that device.

Extra Info
R&D use
Source ID
1032 Autovector 7

Summary
The CPU was interrupted by a external device connected to IRQ7

Description (Non-maskable interrupt), but the Exception Vector Table has not been
initialized by the device driver for that device.

Extra Info
R&D use
Source ID
1033 FP Reserved
This section describes the CPU error FP Reserved.

Summary
The floating-point coprocessor (68881, 68882 or built-in) informed the

Description CPU of an exception condition (Catch-all).

Extra Info
None.
Source ID
1034 FP Br Unord
This section describes the CPU error FP Br Unord.

Summary
The floating-point coprocessor informed the CPU of an branch or set

Description on unordered condition. This corresponds to the ‚BSUN bit in the FPU
exception byte.

Extra Info
None.
Source ID
1035 FP Inexact Result
This section describes the CPU error FP Inexact Result.

Summary
The floating-point coprocessor informed the CPU of an inexact result

Description condition.

Extra Info
None.
Source ID
1036 FP Div Zero
This section describes the CPU error FP Div Zero.

Summary
The floating-point coprocessor informed the CPU of an divide by zero

Description condition. This corresponds to the ‚DZ bit in the FPU exception byte.

Extra Info
None.
Source ID
1037 FP Underflow
This section describes the CPU error FP Underflow.

Summary
The floating-point coprocessor informed the CPU of an underflow

Description condition. (Values smaller than 2.2E-308 or 1.7E-4932, depending on
precision) This corresponds to the ‚UNFL bit in the FPU exception byte.

Extra Info
None.
Source ID
1038 FP Operand Error
This section describes the CPU error FP Operand Error.

Summary
The floating-point coprocessor informed the CPU of an Operand Error

Description condition. This corresponds to the ‚OPERR bit in the FPU exception
byte.

Extra Info
None.
Source ID
1039 FP Overflow
This section describes the CPU error FP Overflow.

Summary
The floating-point coprocessor informed the CPU of an overflow

Description condition. (Values larger than 18E+308 or 1.2E+4932, depending on
precision) This corresponds to the ‚OVFL bit in the FPU exception byte.

Extra Info
None.
Source ID
1040 FP Signaling NAN
This section describes the CPU error FP Signaling NAN.

Summary
The floating-point coprocessor informed the CPU of a Not-A-Number

Description condition.

Extra Info
None.
Source ID
1041 FP Unimplemented DataType
This section describes the CPU error FP Unimplemented DataType.

Summary
The floating-point coprocessor informed the CPU of an unimplemented

Description data type condition. Check if the Packed Decimal Real format
(Supported only on MC68040 and greater!) or some other invalid data
format is being used.

Extra Info
None.
Source ID
1042 MMU Reserved
This section describes the CPU error MMU Reserved.

Summary
The Memory Management Unit (68851 or built-in) informed the CPU of

Description an exception condition (Catch-all).

Extra Info
None.
Source ID
1043 MMU Config error
This section describes the CPU error MMU Config error.

Summary
The Memory Management Unit informed the CPU of an Configuration

Description Error condition.

Extra Info
None.
Source ID
1044 MMU Illegal Operation
This section describes the CPU error MMU Illegal Operation.

Summary
The Memory Management Unit informed the CPU of an Illegal

Description Operation condition.

Extra Info
None.
Source ID
1045 MMU Access Level Violation
This section describes the CPU error MMU Access Level Violation.
Summary
The Memory Management Unit informed the CPU of an Access Level

Description Violation condition.

Extra Info
None.
Source ID
1046 TPU Interrupt
This section describes the CPU error TPU Interrupt.

Summary
The Time Processing Unit interrupted the CPU but there was no
Description installed interrupt handler.

Extra Info
None.
Source ID
1047 SCI Interrupt
This section describes the CPU error SCI Interrupt.

Summary
The Serial Communication Interface (SCI), Serial Communication

Description Controller (SCC) or Programmable Serial Controller (PSC) interrupted
the CPU due to an error or there is interrupt handler is not installed.

Extra Info
R&D use
Source ID
1048 SPI Interrupt
This section describes the CPU error SPI Interrupt.

Summary
The Serial Peripheral Interface (SPI/DSPI)interrupted the CPU

Description because of an error or there is no interrupt handler installed.
R&D use(Program counter)

Extra Info
R&D use
Source ID
1049 CPM Interrupt
This section describes the CPU error CPM Interrupt.

Summary
The RISC Communication CoProcessor Module interrupted the CPU

Description but there was no installed interrupt handler, or Communication
Processing Module informed the CPU of an error condition, such as a
DMA bus error, or if a CPM interrupt was masked prior to servicing.

Extra Info
Vector number 160..191 indicating the sub-module:

Source ID
160: CPM error
161: PC11
162: PC10
163: SMC2/PIP
164: SMC1
165: SPI
166: PC9
167: Timer 4
168: (Reserved-SCC-d shadow)
169: PC8
170: PC7
171: PC6
172: Timer 3
173: (Reserved-SCC-c shadow)
174: PC5
175: PC4
176: (Reserved-SCC-b shadow)
177: RISC Timer table
178: Timer 2
179: (Reserved-SCC-a shadow)
180: SDMA2
181: SDMA1
182: SDMA Bus error
183: PC3
184: PC2
185: Timer 1
186: PC1
187: SCC4
188: SCC3
189: SCC2
190: SCC1
191: PC0
1050 External H Reset
This section describes the CPU error External H Reset.

Summary
The CPU was reset by the RESET or HRESET signal from the
Description hardware; usually because the RESET button was pressed or because
the hardware on the CPU board activated the RESET signal.
None.
Extra Info
None.
Source ID

Causes and
1 Reset button on GCIOx No error.
Actions
pressed
2 Power restored after being No error.
turned off
1051 PowerUpReset
This section describes the CPU error PowerUpReset.

Summary
The CPU was reset due to the power turning on.

Description
None.
Extra Info
None.
Source ID
1052 Watchdog Reset
This section describes the CPU error Watchdog Reset.

Summary
The CPU was reset by the hardware watchdog. This indicates that the
Description interrupt service routines and the operating system stopped
responding. Since the CPU is reset directly by a hardware timer, no
further information regarding the fault is saved.
None.
Extra Info
None.
Source ID
1053 DoubleBusFaultReset
This section describes the CPU error DoubleBusFaultReset.

Summary
The CPU was reset due to a double bus fault when a bus-error
Description resulted in another bus-error. Due to the utterly hopeless catastrophic
nature of this failure, no exception state information can be saved.
None.
Extra Info
None.
Source ID
1054 ClockLossReset
This section describes the CPU error ClockLossReset.

Summary
The CPU was reset due to the Clock Synthesizer loosing the Crystal
Description Frequency Reference signal.
The GCIO360 uses a 4.192 MHz crystal and generates 25.0 or 33.3
MHz using a Phase Lock Loop. If the Crystal Reference is lost, the
processor resets.
None.
Extra Info
None.
Source ID
1055 External S-Reset
This section describes the CPU error External S-Reset.

Summary
The CPU detected an external device driving the RESET-S signal.

Description Normally, this signal is driven by the processor in response to the
RESET-H signal.
This event may be reported if a more specific reset cause couldn't be
determined (default case)
None.
Extra Info
None.
Source ID

Causes and
1 BootROM CPUCF54 is out of Upgrade BootROM on the
Actions
date CPU print:
CPUCF54 v1.2.0 or newer
CPUCF540 v2.1.0 or newer
2 R&D environment only: SW No error.
developer Debugger is
connected
This section describes the CPU error BErr Released Write.

Summary
The 32-bit Motorola 68020, 68360 and newer processors may still be
Description writing data (Released Write) from a previous instruction while the next
instruction is being fetched or executed. The CPU was reset due to a
Bus Error while performing a released-write.
Program counter before the fault

Extra Info
None.
Source ID

Causes and
Actions
R&D
newer
1057 BErr Prefetch
This section describes the CPU error BErr Prefetch.

Summary
The CPU was reset due to a Bus Error while fetching the next
Description instruction(s) to be executed. Due to the 32-bit architecture of the
68360, 68020 and newer, several instructions may be fetched
simultaneously in advance of being executed. Typically, the SW
execution branches to a memory location that does not exist.
Therefore, the program counter in the Extra Info is the address of the
last valid instruction executed before the fatal branch or jump.

Extra Info
None.
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error BErr Operand Read.

Summary
The CPU was reset due to a Bus Error while reading a data operand
Description value from a memory location that does not exist, or is restricted to
supervisor-only access.

Extra Info
None.
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error BErr Operand Write.

Summary
The CPU was reset due to a Bus Error while writing a data operand
Description value to a memory location that does not exist, is restricted to read-
only access, or is restricted to supervisor-only access.

Extra Info
None.
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error BErr MoveMultiple.

Summary
The CPU was reset due to a Bus Error while reading or writing multiple
Description values to a memory location that does not exist, is restricted to read-
only access, or is restricted to supervisor-only access. Move-Multiple
usually happens when the CPU saves or restores several register
values simultaneously at the beginning or end of a function call. This
may be due to the User Stack Pointer being corrupted.
This can happen with instructions like:
MOVEM A5/A4/A3/A2/A1/D3/D2/D1/D0, -(A7)

Extra Info
None.
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error BErr Exception Processing.

Summary
The CPU was reset due to a Bus Error while saving or restoring the
Description stack-frame state information from another exception.

Extra Info
None.
Source ID
1062 Dead Task
This section describes the CPU error Dead Task.

Summary
The CPU was reset due to a thread that didn't report itself alive within
Description the corresponding supervision interval. Typically, the system is still
running, but a lower priority thread does not get enough CPU time
because a high priority task uses too much of the CPU resource.
Note, this is NOT the same as a hardware watchdog reset. See error
1052 for a description of the hardware watchdog reset.
Description of which tasks didn't respond, varies according to SW

Extra Info version. (For R&D internal use)
None.
Source ID

Causes and
Actions
R&D
newer
1063 Group24vFail
This section describes the CPU error Group24vFail.

Summary
The CPU was reset, and the Group 24V supply is below tolerence
Description (24V20%). If warning 1064 LiftPowerFail also appears at the same time
as this warning, the system may be running on the backup battery
power only.
TX5 Note: Normally, the battery level is tested at every reset, however
if either 1064 LiftPowerFail or 1064 LiftPowerFail event appears, then
the reserve level of the battery is not tested, since testing the battery
could possibly interrupt power to the control in this case.
None.
Extra Info
None.
Source ID
1064 Lift24vFail
This section describes the CPU error Lift24vFail.

Summary
The CPU was reset, and the Group 24V supply is below tolerence
Description (24V20%). If warning 1063 GroupPowerFail also appears at the same
time as this warning, the system may be running on the backup battery
power only.
TX5 Note: Normally, the battery level is tested at every reset, however
if either 1064 LiftPowerFail or 1064 LiftPowerFail event appears, then
the reserve level of the battery is not tested, since testing the battery
could possibly interrupt power to the control in this case.
None.
Extra Info
None.
Source ID
1065 12vPowerFail
This section describes the CPU error 12vPowerFail.

Summary
The CPU was reset, and the internal 12V supply is below tolerence.
Description TX5 Note: This supply powers optional 12V encoders and I/O circuits
on ASILOG.
None.
Extra Info
None.
Source ID
1066 BatteryCharging
This section describes the CPU error BatteryCharging.

Summary
The CPU was reset, and the battery needs charging. The battery is
Description automatically charged.
TX5 Note: This event is normal following a power failure. If the battery
requires increasingly charging, the battery should be checked to see if
it is OK, and replaced if necessary.
Normally, the battery level is tested at every reset, however if the
battery is charging then the reserve level of the battery is not tested
since the battery needs charging anyway.
None.
Extra Info
None.
Source ID
1067 BatteryLow50
This section describes the CPU error BatteryLow50.

Summary
The CPU was reset, and the battery has less than 50% charge
Description remaining
TX5 Note: Normally, the battery level is tested at every reset, and also
once every day. If the battery is consistently low, the battery should be
checked to see if it is OK, and replaced if necessary.
None.
Extra Info
None.
Source ID
1068 BatteryLow25
This section describes the CPU error BatteryLow25.

Summary
The CPU was reset, and the battery has less than 25% charge
Description remaining
TX5 Note: Normally, the battery level is tested at every reset, and also
once every day. If the battery is consistently low, the battery should be
checked to see if it is OK, and replaced if necessary.
None.
Extra Info
None.
Source ID
1069 BatteryDeadOrMissing
This section describes the CPU error BatteryDeadOrMissing.

Summary
The CPU was reset, and the battery was dead or missing
Description TX5 Note: Normally, the battery level is tested at every reset (As long
as Group24V and Lift24V to ASILOG are OK) and also once every day.
The battery voltage was tested, and found to be too low. The battery is
either completely discharged, dead, damaged, or disconnected.
None.
Extra Info
None.
Source ID

Causes and
1 Check the wiring and
Actions
connections to the battery
2 Leave the controller powered
on, see if the battery is
charged eventually
3 Measure the voltage of the
battery. It should be about 12v
4 If the error continues, check
the battery and replace if
necessary
1070 LiftIdSwitchInvalid
This section describes the CPU error LiftIdSwitchInvalid.

Summary
The lift-ID switch is set incorrectly

Description The LiftID switch is read at every reset. It must be set to a value from 1
to 9, or A (A=10) according to which lift it is in a group of elevators.
Switch settings 0 and B through F are not allowed in normal operation,

the default setting LiftID=1 is used instead.
None.
Extra Info
None.
Source ID

Causes and
1 Check that the switch setting
Actions
matches the correct Lift ID (1-
9, A)
2 Check that the switch really
clicked into the correct setting,
for example, sometimes the
switch is halfway between 0
and 1
3 If the error persists, suspect a
defective ASILxx / ASIXxxx /
CRIPxxx board
1071 MissingEB
This section describes the CPU error MissingEB.

Summary
A required EB (Expansion Board) is missing, incompatible, or

Description malfunctioning.
All ‚EB expansion boards (Like EBLON and EBCOM) are identified at
every reset, and the device drivers are initialized accordingly. Some
system configurations require certain EBs to be installed.
For example, if LiftID=2 or greater, than an EBCOM is required for
group communication. A minimum of one EBLON is always required
for LON communication.
ID of the missing EB:

Extra Info 90: ASILOG3 missing
C0: EBLON2 missing
C1: EBCOM missing
C2: EBLON1 missing
C3: Embedded EBLON (in CRIP) missing
B0: CRIPHNA missing
E0: Embedded SMLCD missing
None.
Source ID
1072 Saved Registers
This section describes the CPU error Saved Registers.

Summary
This error provides additional "Extra Info" for another CPU error.
Description
This information usually includes the contents of various CPU
registers.
See the actual error (Usually a CPU reset) for more details.
R&D internal use (Value of the register)

Extra Info
R&D internal use (Identification of the register which was saved)

Source ID

Causes and
1 Additional information to a See the action for the
Actions
'reset' error (buserror, page associated 'reset' error.
fault etc)
R&D
newer
1073 ManualDoubleReset
This section describes the CPU error ManualDoubleReset.

Summary
The CPU was reset because the reset button was pressed twice. One
Description region (memory range) of the NVRAM is cleared. Be aware that certain
regions of the NVRAM are not cleared by a double reset. See the
description of CPU error 1074 for a description of the cases when the
whole NVRAM gets cleared.
None
Extra Info
None
Source ID

Causes and
1 The reset button is pressed no error
Actions
twice
1074 Init NVRAM
This section describes the CPU error Init NVRAM.

Summary
At startup the software detects that NVRAM contains a recorded

Description software version signature different from the FLASH and reinitializes all
of the NVRAM (non volatile RAM) memory. This happens typically if
either after a new SW is downloaded, or (more rarely) if the elevator
has been switched off for a very long time and the NVRAM has lost its
data. When the NVRAM is initialized the following data is lost: Content
of Errorlogs, error counters, on-site error adjustments (limits).
None
Extra Info
None
Source ID

Causes and
1 New software installed no error.
Actions
2 power restored after being off no error.
for a long time (several days or
more)
1075 Bad_SIMM Memory
This section describes the CPU error Bad_SIMM Memory.

Summary
Bad SIMM memory detected

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Faulty SIMM memory Replace
1076 CPLD_Programmed
This section describes the CPU error CPLD_Programmed.

Summary
This is no error but a message !

Description When it is detected that either the CPLD is not programmed or the
program in the CPLD is not the same as the expected program,
determined by detecting the System Configuration (i.e. Incremental
Tacho Interface or Absolute Tacho Interface), or the program in the
CPLD is an older version, the CPLD is programmed.
None.
Extra Info
None.
Source ID

Causes and
1 1. The CPLD is blank, i.e. not none
Actions
programmed.
2 2. The GCIOB360 CPU board none
is inserted into a different
system configuration. for
example, the GCIOB360 board
was earlier being used for a
System Configuration with
incremental tacho interface
and is now used for the first
time for a system with absolute
tacho interface.
3 3. The program in the CPLD is none
an older version.
1077 OS Fault
This section describes the CPU error OS Fault.

Summary
The CPU was reset due to a fault related to the operating system, or
Description due to an application call to the operating system.
for R&D internal use

Extra Info

Source ID
1078 OS Restriction Failure
This section describes the CPU error OS Restriction Failure.

Summary
The CPU was reset due to an operating system call that is prohibited in
Description a certain context. For example, a "queue pend" call in an ISR (interrup
service routine). This fault is effectively the opposite of a privelege
violation.

Extra Info

Source ID
1079 Appl Restriction Failure
This section describes the CPU error Appl Restriction Failure.

Summary
The CPU was reset due to an application call that is prohibited in a

Description certain context. For example: "VCOM_send" or "printf" call in an ISR.
This fault is effectively the opposite of a privelege violation.

Extra Info

Source ID
1080 BKPT BGND
This section describes the CPU error BKPT BGND.

Summary
The CPU was reset due to a permanent breakpoint or "assert()" within

Description the software; typically in a check for a condition that should never
happen in a correctly running system.
Program counter value

Extra Info
none
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error Page Fault on Instruction Fetch.
Summary
TLB miss on instruction fetch (MMU)

Description
R&D use
Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error Page Fault on Operand Read.
Summary
TLB miss on data read (MMU)

Description
R&D use
Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error Page Fault on Operand Write.
Summary
TLB miss on data write (MMU)

Description
R&D use
Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error Bus Error Read Protection.
Summary
Error on attempted read or RMW to protected space

Description
R&D use
Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
This section describes the CPU error Bus Error Write Protection.
Summary
Error on attempted write to protected space

Description
R&D use
Extra Info
R&D use
Source ID

Causes and
Actions
R&D
newer
1086 Bus Tenure
This section describes the CPU error Bus Tenure.

Summary
The CPU/software attempted to read/write to a address that is either

Description not physically connected, not responding, or else the bus controller is
hung.
This results in a timeout of the bus monitor/bus tenure arbiter.
R&D use
Extra Info
R&D use
Source ID

Causes and
1 HW defect Check that the CPU board
Actions
(CPUCFxx) is the latest
revision
R&D
newer
1087 Date Time First Init
This section describes the CPU error Date Time First Init.
Summary
At startup the software detects that the Real Time Clock (RTC) has
Description stopped or contains an illegal date/time. The content of the NVRAM is
often lost as well, an error "1074 Init NVRAM" may also appear. The
date/time of subsequent entries in the errorlog are incorrect.
no meaning
Extra Info
none
Source ID

Causes and
1 New processor board Check the date/time with
Actions
GCIOxxx has been installed SMLCD or CADI and set it to
the current value
2 The power has been switched Check the date/time with
off for a long time during which SMLCD or CADI and set it to
the backup power (battery) for the current value
the RTC was interrupted.
3 The backup supply (Goldcap) Replace GCIO board
on the GCIO is defective
1200 LON Error Base Id
This section describes the LON error LON Error Base Id.
Summary
Description
None.
Extra Info
None.
Source ID
1201 PowerUpReset
This section describes the LON error PowerUpReset.

Summary
Generated when SIOL or SIOG powers up.

Description (SIOL/SIOG ONLY) TX5 reports either CPU errors 1000 ... 1100 or
403 instead.
None.
Extra Info
SIOL or SIOG
Source ID

Causes and
1 The main disconnect was No action required
Actions
turned ON
2 The building had a power No action required
failure
3 JNGG or JNGL tripped and No action required
was reset
4 Loose power connection to the Check for loose wiring
SIO
1202 Exception68332
This section describes the LON error Exception68332.

Summary
This error is generated by the SIO in resposnse to an MC68332

Description Exeption.
(SIOL/SIOG ONLY) TX5 reports CPU errors 1000 ... 1100 instead.
Program counter
Extra Info
SIOL or SIOG
Source ID

Causes and
1 Save error logs and report to
Actions
supplier hotline or R&D
2 EMC problems Close the AS1 cabinet doors.
3 Check for strong EMC source
in the building.
brake.
5 Make sure that the SIO ground
and mass connections are
properly done.
cabinet
7 Defective SIO board Replace SIO board.
8 Software failure Save error logs and report to
1203 ExtReset
This section describes the LON error ExtReset.

Summary
Generated when SIOL or SIOG is reset by an external cause.

Description (SIOL/SIOG ONLY)
TX5 reports either CPU errors 1000 ... 1100 or 403 instead.
None.
Extra Info
SIOL or SIOG
Source ID

Causes and
1 RESET button pressed No action required
Actions
2 EMC problems Close the AS1 cabinet doors.
3 Check for strong EMC source
in the building.
brake.
5 Make sure that the SIO ground
and mass connections are
properly done.
cabinet
7 Voltage monitor Check +24V supply voltage
8 Check for loose wiring
1204 DeadTask
This section describes the LON error DeadTask.

Summary
Generated when the task monitor on SIOL or SIOG detects that a

Description software task is not responding.
(SIOL/SIOG ONLY) TX5 reports either CPU errors 1000 ... 1100 or
403 instead.
One bit per task in binary.

Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
2 Excessive VX bus traffic Check VCOM diagnostics
3 Excessive LON bus traffic Save error logs and report to
1205 WdogReset
This section describes the LON error WdogReset.

Summary
Generated when the SIOL or SIOG was reset by a timeout of the

Description watchdog timer; The watchdog timer detected that the system software
stopped running. (SIOL/SIOG ONLY)
TX5 reports CPU errors 1000 ... 1100 instead.
floor number
Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
2 Excessive VX bus traffic Check VCOM diagnostics
3 Excessive LON bus traffic Save error logs and report to
1206 MysteryReset
This section describes the LON error MysteryReset.

Summary
Generated when the SIOL or SIOG is reset for an unknown or unlisted

Description reason. (SIOL/SIOG ONLY)
TX5 reports CPU errors 1000 ... 1100 instead.
Reset cause ID
Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
1207 NiInitFail
This section describes the LON error NiInitFail.

Summary
Generated when the SIOL / SIOG software could not initialize the LON
Description network interface hardware (ILTP78 daughterboard) and/or MIP
software.
TX5/HX: Generated when the LON driver software could not initialize
the LON network interface hardware (EBLON1,EBLON2
daughterboard or Embedded LON channel on CRIPHNA) and/or MIP
software.
None.
Extra Info
None.
Source ID

Causes and
Actions
3 Defective EBLON board (for Replace EBLON board.
controls with LON bus e.g.
TX5)
1208 NewNodeFound
This section describes the LON error NewNodeFound.

Summary
Generated when a new node was found on the LON network

Description
Node type and location ID.

Extra Info
None.
Source ID
1209 Missing Node
This section describes the LON error Missing Node.

Summary
The error is logged when a node (pcb) is missing on the LON network
Description for some time (maximum 1 min.) or when an output on a missing LON
can not be set because the node is no longer responding. When a
LON node is found missing the control system will respond depending
on the IO's configured on the node (e.g. TAB for critical IOs). The
message is not logged when mains power is turned off.
Comment: A node will only be considered missing if it is included in the

LON node reference list maintained by the SW. The node list is either
generated after a 'freeze LON tree' command (for p&p IO interfaces) or
is part of the physical configuration table (PCT). For details about the
status of the LON nodes refer to SMLCD or CADI 'I/O tracer'.
Change history:
Oct.25 2007 extra information value includes LON channel number
LON channel identifier; Node type and Location ID.

Extra Info
LON channel identifier, LON node type and LON node location ID are
encoded in a 32-bit value (8 digit hex. value)
wxxxyyyy: The first digit (w) identifies the LON channel (0,1 or 2); 0
means that the control software does not provide this information. The
next 3 digits (xxx) identify the Node type. The last 4 digits (yyyy) show
the Node Id.
The 'Node type' defines which type of node is affected (see the list
below).
The 'Node id' defines the location-ID of the node, typically set by a
(dip-) switch, or configured through the M10-keypad.
Examples:
10010002: LON channel 1, Node type=01, ID=02. (LONIO,
dipswitch=02. See list below for node types)
10030004: LON channel 1, Node type=03, ID=04. (LFT-DPI,
dipswitch=04.)
Meaning of values for Node type:
Value / software name / board names

000(hex) / 0(dec): UNDEF should never occur
001(hex) / 1(dec): GENERIC_IO_BOARD LONIOS16, LONIOH16,
ICE, (H)TIC
002(hex) / 2(dec): ARRIVAL_INDICATOR LONDAG
003(hex) / 3(dec): DIGITAL_POSITION_INDICATOR LFTSDPI8,
LFTDPI50
004(hex) / 4(dec): LMS_MODUL LONLMS
005(hex) / 5(dec): MACHINE_MODUL not used
006(hex) / 6(dec): CIOHNA Cab IO for HX system
007(hex) / 7(dec): HPBHNA Hall node for HX system
008(hex) / 8(dec): M10_TERMINAL ZRTL
009(hex) / 9(dec): M10_DESTINATION_INDICATOR AZRC
00A(hex) / 10(dec): M10_SPEECH ANN
00C(hex) / 12(dec): MX_COP LONCOP, LONCPI
00D(hex) / 13(dec): MX_LOP LONCUS, LONIO(C), LOND(G)I
00E(hex) / 14(dec): MX_OPT_LIP_BIG LONCUB, LON(P/D)GIO,
LONDY(H/IO), LONPII, LONVEx
01E(hex) / 30(dec): MX_LONIC LONIC, LONGIC
036(hex) / 54(dec): CAR_DOOR_NODE LONIBV, LONDIM, LONV70,
PLDA
037(hex) / 55(dec): SHAFT_DOOR_NODE not used
03C(hex) / 60(dec): HIOMRLPP HIOMRL plug and play for NA
064(hex) / 100(dec): LOCAL_IO_BOARD ASILOG(A), ASIX(A)
None.
Source ID

Causes and
1 No power at fixture or I/O Check power LED's and power
Actions
board wiring.
2 Communcation to pcb Check bus cables and wiring
interrupted (APPL LED on LON interface
board indicates if board is
communicating).
3 Damaged or defective fixture Replace damaged fixture or I/O
or I/O board (corrupted interface board and repeat
software or other defect) LON freeze command if
necessary.
1210 NiErrLogged
This section describes the LON error NiErrLogged.

Summary
Generated when the LON network interface processor has logged an

Description error. the errors are defined by Echelon.
None.
Extra Info
None.
Source ID

Causes and
Actions
supplier hotline.
2 Defective board Replace SIO or EBLON board.
3 Unauthorized equipment Remove unauthorized
connected to LON bus equipment.
1211 NodeErrLogged
This section describes the LON error NodeErrLogged.

Summary
Generated when a node on the LON network has logged an error. The
Description errors are defined by Echelon.

Extra Info
None.
Source ID

Causes and
1 Damaged or defective fixture Replace damaged fixture or I/O
Actions
or I/O board board.
2 Software failure Save error logs and call
EBI/RAND
1212 SvcPinEvent
This section describes the LON error SvcPinEvent.

Summary
This event is logged in normal operation when a mechanic presses a

Description Service/Test button on a LON node, generated when a node on the
LON network has generated a service pin event.

Extra Info
None.
Source ID
1213 NiReset
This section describes the LON error NiReset.

Summary
Generated when a reset occured on the LON network interface

Description hardware (EBLON). May be caused by an incoming message, power
up or a watchdog reset on the LON network interface hardware.
TXR5/HX: Reported by the the LON network driver when the EBLON1
or EBLON2 resets unexpectedly.
The following interpretation of the extra info value is only valid for
Extra Info control software versions released later than Nov.2009
Information about LON channel, reset cause etc.

Meaning of the 8 digit hex. value (xABCDEFGH).
A: LON channel number (1 or 2)
B: Reset Cause (1-5) with meaning

[1]: Power-up reset
[2]: External reset
[3]: Watchdog reset
[4]: Software reset
[5]: Cleared
Remark: the following information is for R&D use only

CD: Error Log (from LON firmware) with meaning:
no_error = 0
bad_event = 129
nv_length_mismatch = 130
nv_msg_too_short = 131,
eeprom_write_fail = 132,
bad_address_type = 133,
preemption_mode_timeout = 134,
already_preempted = 135,
sync_nv_update_lost = 136,
invalid_resp_alloc = 137,
invalid_domain = 138,
read_past_end_of_msg = 139,
write_past_end_of_msg = 140,
invalid_addr_table_index = 141,
incomplete_msg = 142,
nv_update_on_output_nv = 143,
no_msg_avail = 144,
illegal_send = 145,
unknown_PDU = 146,
invalid_nv_index = 147,
divide_by_zero = 148,
invalid_appl_error = 149,
memory_alloc_failure = 150,
write_past_end_of_net_buffer = 151,
appl_cs_error = 152,
cnfg_cs_error = 153,
invalid_xcvr_reg_addr = 154,
xcvr_reg_timeout = 155,
write_past_end_of_appl_buffer = 156,
io_ready = 157,
self_test_failed = 158,
subnet_router = 159,
Authentication_mismatch = 160,
self_inst_semaphore_set = 161,
read_write_semaphore_set = 162,
appl_signature_bad = 163,
router_firmware_version_mismatch = 164
EF: Link state at reset with meaning:

0: unknown_state = 0,
1: fatal_error = 1,
2: before_ISR = 2,
3: reset_state = 3, /* The hardware has been reset */
5: wrote_resync =5,
6: wrote_resync_eom = 6,
7: read_acksync = 7, /* Resynchronized, we have token. */
8: no_acksync = 8
10: we_own_token = 10,
11: wrote_xfer = 11,
12: wrote_len = 12,
13: wrote_localcmd = 13,
14: wrote_data = 14,
15: wrote_xfer_eom = 15,
16: wrote_null = 16,
17: wrote_null_eom = 17
20: neuron_has_token = 20,
21: read_xfer
22: read_null /* <-- Normally we idle in this state */
23: read_len
24: read_qmdq
25: read_data
GH: Status register at Reset (8bits: abcdefgh)

a: fled (The LED is: 0= off / 1=ON)
b: resie (The RESI interrupt is: 0=disabled / 1=Enabled)
c: ulie (The ULI interrupt is: 0=disabled / 1=Enabled)
d: hsie (The HSI interrupt is: 0=disabled / 1=Enabled)
e: hs ( The interface is: 0=ready / 1=busy)
f: resi (The RESI is: 0=Clear / 1=The Neuron was reset)
g: uli (The ULI is: 0=Clear / 1=There was an uplink interrupt)
h: hsi (The HSI is: 0=Clear / 1=HS went to 0(Ready))
Not used
Source ID

Causes and
Actions
supplier hotline.
1214 DupLocID
This section describes the LON error DupLocID.

Summary
Generated when the Network Manager detects two fixtures or I/O

Description boards on the LON network with the type and same location ID setting.
The Location ID is usually set by a dipswitch or keypad.

Extra Info
None.
Source ID

Causes and
1 Two fixtures of the same type Make sure every LON fixture
Actions
have same dipswitch setting has the correct setting.
1215 NiErrCounter
This section describes the LON error NiErrCounter.

Summary
Generated when one of the MIP error counters on the LON network
Description interface increases by a preset amount. The amount of increase
depends on the error counter involved.
Cumulative count value since the SIO was last reset.

Extra Info
None.
Source ID

Causes and
1 Communication errors Save error logs and call
Actions
EBI/RAND
1216 DiffCksGP_Konf
This section describes the LON error DiffCksGP_Konf.

Summary
The SIO requests PCT configuration checksum information from the

Description RS after every reset. This event is generated by the SIO when one of
the configuration paramater checksums on RS has changed and the
configuration on the SIO is no longer correct.
The SIO will now download a new configuration.
New checksum value (16 bits)

Extra Info
SIOL or SIOG
Source ID

Causes and
1 First power-up None
Actions
2 A new PCT was downloaded to None
RS
3 Download Configuration None
command
4 Software on SIO replaced None
1217 DiffCksIO_Konfl
This section describes the LON error DiffCksIO_Konfl.

Summary

Description RS after every reset. This event is generated by the SIO when one of
the I/O mapping configuration checksums on RS has changed
changed and the configuration on the SIO is no longer correct.
The SIO will now download a new I/O mapping configuration.
New checksum value (16 bits)

Extra Info
SIOL or SIOG
Source ID

Causes and
1 First power-up None
Actions
2 A new PCT was downloaded to None
RS
3 Download Configuration None
command
4 Software on SIO replaced None
1218 TmoCksGP_Konf
This section describes the LON error TmoCksGP_Konf.

Summary

Description RS after every reset. This error is generated by the SIO when the
checksum for this paramater group is not received and a timeout
occurrs.
On the SIOG, the PCT information is requested from the lowest
numbered lift first. If the information is not received, the SIOG
continues to try each lift in turn until the information is received.
The SIOL always downloads its PCT configuration from the RS in the
same lift.
SIOL: not used

Extra Info SIOG: lift-ID of the RS which did not respond
SIOL or SIOG
Source ID

Causes and
1 Incorrect or corrupted PCT Download a correct
Actions
configuration file.
2 Error on RS Save error logs and call
EBI/RAND
1219 TmoDatGP_Konf
This section describes the LON error TmoDatGP_Konf.

Summary

Description RS after every reset. If the checksum is different, hte configuration data
is downloaded. This error is generated by the SIO when the checksum
for this paramater group was received, but the data was not received
and a timeout occurrs.
same lift.
SIOL: not used

SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1220 TmoCksIO_Konf
This section describes the LON error TmoCksIO_Konf.

Summary

checksum for this I/O mapping paramater group is not received and a
timeout occurrs.
continues to try each lift in turn until the I/O mapping information is
received.
same lift.
SIOL: not used

SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1221 TmoDatIO_Konf
This section describes the LON error TmoDatIO_Konf.

Summary

Description RS after every reset. If the checksum is different, the I/O mapping
configuration data is downloaded. This error is generated by the SIO
when the checksum for this paramater group was received, but the I/O
mapping data was not received and a timeout occurrs.
same lift.
SIOL: not used

SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1222 DnLdGP_Konf
This section describes the LON error DnLdGP_Konf.

Summary

Description RS after every reset. If the checksum is different, the configuration data
is downloaded. This error is generated by the SIO when the response
from the RS indicates an error condition.
Error code response message from RS

Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1223 DnLdIO_KOnf
This section describes the LON error DnLdIO_KOnf.

Summary

Description RS after every reset. If the checksum is different, the I/O mapping
configuration data is downloaded. This error is generated by the SIO
when the response from the RS indicates an error condition.

Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1224 CksErrGP_Konf
This section describes the LON error CksErrGP_Konf.

Summary

checksum response from the RS indicates an error condition.

Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1225 CksErrIO_Konf
This section describes the LON error CksErrIO_Konf.

Summary

checksum response from the RS indicates an error condition.

Extra Info
SIOL or SIOG
Source ID

Causes and
Actions
configuration file.
EBI/RAND
1226 DoubleReset
This section describes the LON error DoubleReset.

Summary
Generated when SIOL or SIOG is double reset by the mechanic. The

Description configuration tables are cleared, and the configuration is loaded again
from the RS.
None.
Extra Info
None.
Source ID
1227 HWisLCTRL
This section describes the LON error HWisLCTRL.

Summary
Generated when SIOL or SIOG detects it is running on the wrong HW

Description type.
None.
Extra Info
None.
Source ID
1228 NiNoInAppBuf
This section describes the LON error NiNoInAppBuf.

Summary
Generated when the Application Buffers in the Network Interface ( MIP

Description on ILTP78, EBLON1 or EBLON2) overflow due to too many messages
on the LON network. This condition is detected on the Neuron Chip.
None.
Extra Info
None.
Source ID

Causes and
Actions
1229 NiNoInNetBuf
This section describes the LON error NiNoInNetBuf.

Summary
Generated when the Network Buffers in the network interface ( MIP on

Description ILTP78, EBLON1 or EBLON2) overflow due to too many messages on
the LON network. This condition is detected on the Neuron Chip.
None.
Extra Info
None.
Source ID

Causes and
Actions
supplier hotline.
1230 PmipNoOutQ
This section describes the LON error PmipNoOutQ.

Summary
Generated when the LON driver software attempts to transfer a

Description message to the LON network interface hardware (EBLON1,EBLON2
daughterboard or Embedded LON channel on motherboard ASIX,
ASILOG, CRIPHNA, etc.) but the MIP (microprocessor interface
program) software on the Neuron Chip reports that all buffers are full.
The buffer transfer attempt is repeated until the messages is accepted,
or all the buffers in the LON network driver are full. This error may
indicate a serious communication problem.
LON channel identification.

Extra Info
decoding of the 8 digit hex. number ABCDEFGH:
A: LON channel number (1: channel 1 / 2: channel 2)
OQ-size
None.
Source ID

Causes and
1 Defective board Replace SIO or EBLON
Actions
interface board.
Replace motherboard with
LON bus interface.
supplier hotline.
1231 PmipIqOverflow
This section describes the LON error PmipIqOverflow.

Summary
Generated when the MIP software on the Neuron Chip has received
Description several messages that need to be transferred to the main processor,
but the buffers in the LON driver software are completely full and
overflowing. This error may indicate a serious communication problem.
IQ-size
Extra Info
None.
Source ID

Causes and
Actions
supplier hotline.
1232 SubsystemStart
This section describes the LON error SubsystemStart.

Summary
VCOM on SIOL/SIOG detected another print on group-bus or lift-bus

Description started communicating.
(SIOL/SIOG ONLY) TX5 reports event 401 instead.
Bits 15..8: cause=01=VCOM_PRINT_START

Extra Info Bits 7..4: Lift ID of subsystem
Bits 3..0: Logical address of subsystem
Example: 00000111 = RS Lift 1
Example: 00000112 = Travel Control Lift 1
None.
Source ID
1233 SybsystemDead
This section describes the LON error SybsystemDead.

Summary
VCOM on SIOL/SIOG detected another print on group-bus or lift-bus

Description stopped communicating
(SIOL/SIOG ONLY) TX5 reports error 402 instead.
Bits 15..8: cause=02=VCOM_PRINT_DEAD

Extra Info Bits 7..4: Lift ID of subsystem
Bits 3..0: Logical address of subsystem
Example: 00000212 = Travel Control Lift 1
None.
Source ID

Causes and
1 Noise on group- or lift-bus Check bus terminations,
Actions
grounding, cable shields. Make
sure connectors are plugged in
firmly.
3 Other defective board on Replace/remove other boards
group- or lift-bus on lift bus or group bus to
isolate problem.
supplier hotline.
1234 VcomUpcall
This section describes the LON error VcomUpcall.

Summary
VCOM on SIOL/SIOG detected an abnormal condition. This is usually

Description catastrophic, and reliable operation can not be guaranteed.
Bits 15..8: cause=

Extra Info 03=VCOM_QUEUE_FULL, paramater is Queue-ID
04=VCOM_ADMIN_FULL
05=VCOM_UPDATES_FULL
06=VCOM_COMMS_Q_FULL
07=VCOM_BUSSED_STRESSED, paramater is stress-ID
08=VCOM_LOC_TABLE_FULL
09=VCOM_ADMIN_CONFLICT
Bits 7..0: paramater from VCOM.H
Example: 000003CB = VCOM_QUEUE_FULL, paramater=CB hex
None.
Source ID

Causes and
1 Noise on group- or lift-bus Check bus terminations,
Actions
firmly.
3 Other defective board on Replace/remove other boards
isolate problem.
supplier hotline.
1235 KonfWipe
This section describes the LON error KonfWipe.

Summary
Generated when SIOL or SIOG erases its configuration and then

Description reloads the PCT from RS. This is normal following a software upgrade,
when swapping a SIOL with another lift, or after a double reset.
Reason for konf-wipe. See below (One or more may be set)

Extra Info 00000001 Master checksum
00000020 Domain ID
00000300 Subnet/node
00004000 Lift-ID changed
00050000 SW-Version changed
None.
Source ID
1236 CadiReset
This section describes the LON error CadiReset.

Summary
Generated when SIOL or SIOG is reset due to a CADI command

Description
CAD1CAD1
Extra Info
None.
Source ID
1237 VcomAllDied
This section describes the LON error VcomAllDied.

Summary
Generated when SIOL or SIOG is detects all other subsystems dead,

Description and resets itself to try to restore communication
A110DEAD
Extra Info
None.
Source ID

Causes and
1 Noise on Group or Lift-bus Check bus terminations,
Actions
firmly.
3 Other defective board on Replace/remove other board
isolate problem.
supplier hotline.
1238 KonfTableFull
This section describes the LON error KonfTableFull.

Summary
Generated when SIOL or SIOG configuration tables are full, due to a

Description PCT that is too large
Table-size
Extra Info
None.
Source ID
1239 TelTrap
This section describes the LON error TelTrap.

Summary
Generated when SIOL or SIOG detects a Group Input pin change, for
Description example, Fire Phase 1, JBF, Smoke Detectors, RNO, etc.
This mechanism logs any transition on these fire inputs into the SIOs
local log, even if CADI telegram tracer is not connected or running.
This information may be used to troubleshoot faulty fire input signals.
It is normal for these events to be logged any time the SIO is powered
on. The Extra Info contains the state of the fire inputs.
It is normal for these events to be logged any time the fire inputs
change.
If the system goes on Fire Service unexpectedly, these events may
show a ‚glitch on one of the fire inputs.
Encoded TelGrp, TelID, Data:

Extra Info Bits 31..24: Tel_Grp
Bits 23..16: Tel_ID
Bits 15..12: Att_1
Bits 11..8: Att_2
Bits 7..0 : Data
Example: 0F010001 VXT_INP_GROUP, VXT_JBF, 0, 0 Data=1 Switch
JBF is ON
None.
Source ID
1240 LonDistQFull
This section describes the LON error LonDistQFull.

Summary
The LON-telegram distributor task could not deliver a message to a

Description task due to a queue full condition. This error indicates a possibly
serious communication problem.
00100qq: LON_Q_FULL (qq=queue-id)

Extra Info 00200qq: LON_INVALID_MSG_QUEUE (qq=queue-id)
00300qq: LON_QUEUE_NOT_DEFINED (qq=queue-id)
Task-ID
Source ID
1241 LonPupXON
This section describes the LON error LonPupXON.

Summary
There was a large burst of traffic on the LON bus, and the main The
Description CPU was very busy at the time. To prevent disturbing the drive
software, the LON driver temporarily allowed incomming messages to
be buffered in the LON ‚MIP coprocessor for later retrieval, thus
providing more available CPU time for critical drive tasks.
This event is normally fairly infrequent and not a problem, however if it
is observed frequently, or along with other errors at the same time it
may indicate a possible communication, wiring, or configuration
problem.
Check Subsystem > Communication > LON, Status > Network > Lift
LON or Group LON, make sure the ‚Lost Messages and ‚Missed
Messages are both 0, other values indicate a serious communication
problem.
Check that all devices connected to the LON busses and all devices
parallel wired to LON I/O boards are functioning correctly. Sometimes
an input may be toggling frequently and creating abnormal excessive
LON-bus traffic.
n is the channel-ID (1=LiftLON, 2=GroupLON)

Extra Info n010'0000 + iq_size now = IQ is nearly full - Downlink Quench XOFF
n020'0000 + iq_size now = IQ is better now - Downlink Resume XON
n030'0000 + iq_size now = IQ was nearly full & got better XON and
XOFF close together
None.
Source ID
1242 LonDownNACK
This section describes the LON error LonDownNACK.

Summary
Too many messages were sent at the same time to the LON bus
Description interface, and there was no more space on the Neuron chip to allocate
a buffer (LON downlink buffer full). The Neuron chip then replies with a
'downlink NACK'.
This event is normally quite rare, however if it is observed repeatedly,

or along with other errors at the same time it indicates a
communication or configuration problem.
8 digit hex. value: yxxxxxxx

Extra Info
The first digit (y) identifies the LON channel (1 or 2).
Meaning of 'xxxxxxx' when source Id. = 2:

Number of 'DownNack' events during the last 5 seconds
Meaning of 'xxxxxxx' when source Id. = 4:

x0000000: Timer creation has failed
Identification for source code file

Source ID
1243 FreezeFailed
This section describes the LON error FreezeFailed.

Summary
Freeze command not completed successfully. Refer to extra

Description information for reason.
x01: Master switch occured during freezing

Extra Info x02: Node subsystem not resonding
x03: IO Subsystem not respnding
x04: Master not responding
None.
Source ID
1244 No Response Critical Node
This section describes the LON error No Response Critical Node.

Summary
After power up a LON node with critical IO's does not answer after 4
Description attempts to establish communication.
None.
Extra Info
None.
Source ID

Causes and
1 Problem with LON Contact Field Engineering
Actions
communication or LON node Ebikon
1245 LON Error Debug
This section describes the LON error LON Error Debug.

Summary
LON manager failled to send LON message. For R&D internal

Description debugging purposes only.
None.
Extra Info
None.
Source ID
1246 LonErr46
This section describes the LON error LonErr46.

Summary
To be defined.
Description This and all higher error codes within this block are reserved for future
use by LON
None.
Extra Info
None.
Source ID
1247 LonErr47

Summary
To be defined.
use by LON
None.
Extra Info
None.
Source ID
1248 LonErr48

Summary
To be defined.
use by LON
None.
Extra Info
None.
Source ID
1249 NodePowerFail
This section describes the LON error NodePowerFail.

Summary
Generated when the voltage (normally 24VDC) to a LON node is too

Description low (limit -20%)
Node type and location ID encoded as a 32-bit value. Please refer to

Extra Info description for error number 1209 for encoding information of extra info
value.
None.
Source ID

Causes and
1 Low voltage on LON node Check voltage on node.
Actions
board.
1250 BIO2_ISR_Initialisation_Error
This section describes the BIO2 error BIO2_ISR_Initialisation_Error.

Summary
BIO2 driver initialisation error. An error has occurred during the BIO2
Description driver initialisation or later due to the failed initialisation.
0xCCSS???? CC = Error code / SS = Source

Extra Info
Meaning of error code (CC):
01 = Missing BIO2 Hardware (EBBIO)
02 = Driver has already been initialised
03 = Driver has not yet been initialised
Meaning of source (SS):

01 = Function BIO2_ISR_open
02 = Function BIO2_ISR_write
03 = Function BIO2_ISR_read
04 = Function BIO2_ISR_pend
Task Id.
Source ID

Causes and
1 Defective hardware Replace hardware
Actions
1251 BIO2_ISR_Buffering_Error
This section describes the BIO2 error BIO2_ISR_Buffering_Error.

Summary
BIO2 driver message buffering error. An error has occurred while

Description buffering messages passed to or from the BIO2 driver.
0xCCSSMMBB
Extra Info
CC = Error code / SS = Source / MM = Message length / BB = Buffer
size
Meaning of Error code (CC):

04 = Message too long for specified buffer
05 = Buffer too small for requested message
Meaning of source (SS):

02 = Function BIO2_ISR_write
03 = Function BIO2_ISR_read
04 = Function BIO2_ISR_pend
Task Id.
Source ID
1252 BIO2_ISR_Queueing_Error
This section describes the BIO2 error BIO2_ISR_Queueing_Error.

Summary
BIO2 driver message queueing error. An error has occurred while

Description queueing incoming or outgoing messages within the BIO2 driver.
0xCC??IIOO CC = Error code / II = Input queue usage / OO = Output

Extra Info queue usage

06 = Input queue is full
07 = Output queue is full
Task Id.
Source ID
1253 BIO2_ISR_Communication_Error
This section describes the BIO2 error

Summary BIO2_ISR_Communication_Error.
An error has occurred in the communication between the BIO2 driver

Description and the EBBIO.
0xCC??IIOO
Extra Info CC = Error code / II = Input queue usage / OO = Output queue usage

08 = EBBIO uplink buffer full
09 = Short circuit on the bus
Task Id.
Source ID
1254 BIO2_ISR_Busmaster_Error
This section describes the BIO2 error BIO2_ISR_Busmaster_Error.

Summary
An error has occurred on the BIO2 hardware (EBBIO)

Description
0xCC??TTSS
Extra Info
CC = Error code / TT = Link state at event / SS = Status register at
event

0A = Synchronisation driver/hardware lost
0B = Hardware has or was reset
0C = Hardware restarted by watchdog
Task Id.
Source ID
1255 BIO2_spare
This section describes the BIO2 error BIO2_spare.

Summary
None
Description
None
Extra Info
None.
Source ID
This section describes the BIO2 error BIO2_Reserve_1256.

Summary
None
Description
None
Extra Info
None.
Source ID

Summary
None
Description
None
Extra Info
None.
Source ID

Summary
None
Description
None
Extra Info
None.
Source ID

Summary
None
Description
None
Extra Info
None.
Source ID
1260 BIO2 Queue Failure
This section describes the BIO2 error BIO2 Queue Failure.

Summary
Error occured in BIO2 queue handling. A message queue is not defind

Description or full
0x0010xxxx: Invalid message queue (queue id = xxxx)

Extra Info 0x0030xxxx: BIO2 queue not defined (queue id = xxxx)
0x0040xxxx: BIO2 queue full (queue id = xxxx)
160: BIO2_DISP_TASK_ID
Source ID
1261 BIO2 Requestor Failure
This section describes the BIO2 error BIO2 Requestor Failure.

Summary
Error occurred in BIO2-requestor. The requestor table of the BIO2-

Description BUS is full.
0x0010xxxx: requestor table full (queue id = xxxx)

Extra Info 0x0020xxxx: no request found (queue id = xxxx)
Source ID
1262 BIO2 Dispatcher Failure
This section describes the BIO2 error BIO2 Dispatcher Failure.

Summary
An error occurred according to the BIO2 dispatcher. While dispatching

Description a received BIO2 message a failure occurred.
0x00100000: BIO2_DISP_INTERNAL_ERROR
Extra Info 0x00200000: BIO2_DISP_SYSTEM_ERROR
0x00300000: BIO2_DISP_UNDEFINED_ERROR
Source ID
1263 BIO2 Missing Node
This section describes the BIO2 error BIO2 Missing Node.

Summary
Falta un nodo en el bus BIO2. Hay un nodo BIO2 que ha sido

Description reconocido y que ya no responde.
Un nodo BIO2 no responde cuando es escaneado (nodo sin E/S
crítica) o ya no envía la señal heartbeat (nodo con E/S crítica). Es
posible que el nodo ausente esté defectuoso, por lo que debe ser
sustituido por uno nuevo. También es posible que el nodo ausente
haya sido reconfigurado. Esto significa que el nodo en realidad
funciona correctamente, pero el host no puede recibir ninguna
respuesta de la dirección antigua de éste. El host no puede decir si se
ha instalado un nuevo nodo o si se ha reconfigurado uno antiguo. En
este caso se debe realizar una congelación.
0x0000yyxx
Extra Info
xx = lado de acceso (01 = parte delantera/02 = parte trasera)
yy = número de piso
Task Id.
Source ID

Causes and
1 Sin comunicación con el Comprobar el circuito impreso
Actions
circuito impreso BIO2 del nodo BIO2 en el piso
correspondiente
2 Pérdida de alimentación en el Comprobar el circuito impreso
circuito impreso BIO2 del nodo BIO2 en el piso
correspondiente
3 Reconfigurar el nodo BIO2 Ejecutar el comando de
congelación tras la verificación
del funcionamiento del nodo.
4 Hardware defectuoso (circuito Sustituir el circuito impreso.
impreso BIO2)
1264 BIO2 Node Alive Again
This section describes the BIO2 error BIO2 Node Alive Again.
Summary
Message is generated after a previously missing node on the BIO2 bus

Description is detected alive again.
0x0000yyxx: xx = floor number / yy = access side

Extra Info
Task Id.
Source ID
1265 BIO2 No_Address_Left
This section describes the BIO2 error BIO2 No_Address_Left.

Summary
The BIO2 manager can not handle more nodes. If there are nodes that
Description are removed from the bus restart the system. While teachin the
maximum number of nodes was exceeded and the BIO2 BUS driver
has no address left.
none
Extra Info
Task Id.
Source ID

Causes and
1 Too many teach in's. Restart System
Actions
1266 BIO2 Unsupported_Protocol
This section describes the BIO2 error BIO2 Unsupported_Protocol.

Summary
While scanning or teach-in a node with a not supportet protocol

Description version is detected. The node is not able to support the requested
protocol version from the control.
The floor and side information is read from the node if a teach-in was
done before for the same node. If the teach-in for the node was done
on the elevator it is connected to, then the floor and side information is
correct. Otherwise the floor/side values read from the node may not
correspond to the floor and side where the node is placed.
0xAABBFFZZ
Extra Info AA: The protocol version of the host
BB: The protocol version of the node
FF: Floor number read from the node
ZZ: Side info read from the node
Task Id.
Source ID

Causes and
1 BIO2 node with incompatible Remove the board (BIO2
Actions
version. node) from the bus because it
is not supported by the control.
1267 BIO2 Multiple Node on address
This section describes the BIO2 error BIO2 Multiple Node on address.
Summary
Two or more nodes with the same node address are or were detected
Description (used) on the bus.
0xAABBCCDD
Extra Info
AA: Floor of the first node
BB: Side of the first node
CC: Floor of the second node
DD: Side of the second node
Task Id.
Source ID

Causes and
1 Repeat teach-in for both BIO2
Actions
nodes
1268 BIO2 Multiple BIOGIO Nodes
This section describes the BIO2 error BIO2 Multiple BIOGIO Nodes.
Summary
Two or more BIOGIO nodes with the same node address are detected
Description on the BIO bus.
0xAABBCCDD
Extra Info
AA: not used
BB: not used
CC: not used
DD: address of the BIOGIO node
Task Id.
Source ID
1269 BIO2 Nodes Manually Cleared
This section describes the BIO2 error BIO2 Nodes Manually Cleared.
Summary
This information is reported when the service technician has entered a

Description "Clear Bio Nodes" command at the service interface.
All BIO nodes, which where connected at this time to the BIO bus are
reset to their factory settings. With a "Clear Bio Nodes" command, all
IOs on the connected nodes are cleared and the node ID is set to its
virgin value. If the node has dip-switches to set the device address
(e.g. IO nodes in the control cabinet for building interface IOs), the
DIP-switch setting is read and the device address is set accordingly.
0xAABBCCDD
Extra Info
AA: not used
BB: not used
CC: not used
DD: address of the BIOGIO node
Task Id.
Source ID
1300 CAN Error Base Id
This section describes the 1300_11349_CAN error CAN Error Base Id.
Summary
Description
Extra Info
Source ID
1301 CAN Missing Node
This section describes the 1300_11349_CAN error CAN Missing

Summary Node.
A node is missing on the CAN bus. There is a CAN node that has been
Description recognised and does not respond any more. Node may no longer be
connected to bus, node may be broken or power supply to node is off.
8 digit hex value 0xABCDEFGH where:

Extra Info
AB: defines the node_type
01(hex): CANIC
02(hex): Door
03(hex): COP
04(hex): CANGIO
05(hex): CANM10
CD: instance (if floor > 0 then instance is the position for M10 else it is
the riser number)
EF: floor (it is the group stop starting by 0)
GH: bit 6..7 deck, bit 4..5, side, bit 0..3 bus
Identification of software source file

Source ID

Causes and
2 A CAN node is missing Check the CAN bus / power
Actions
because the CAN bus / power tab to this node for
cable tab to this node is disconnection or broken wires.
disconnected or broken.
3 Multiple CAN nodes are Check CAN bus / power cable
missing because the CAN bus for disconnection or broken
/ power cable to these nodes is wires.
broken or disconnected.
1 A CAN node is missing Replace node HW and execute
because the node HW is node freeze comand in service
defect. interface.
1302 CAN Node Alive Again
This section describes the 1300_11349_CAN error CAN Node Alive

Summary Again.
The software detects a node communicating on the CAN bus. The

Description CAN node that has been recognised and does not respond any more.
The node resumes operation after it was disconnected or was
replaced.

Extra Info
01(hex): CANIC
02(hex): Door
03(hex): COP
04(hex): CANGIO
05(hex): CANM10
the riser number)

Source ID
1303 CAN Node SW Download Failed
This section describes the 1300_11349_CAN error CAN Node SW

Summary Download Failed.
The node SW download to a particular CAN node has failed. There is a

Description CAN node that has been recognised. During a node SW download an
error occured because the node is no longer connected to the bus, the
node may be broken or power supply to the node is off.

Extra Info
01(hex): CANIC
02(hex): Door
03(hex): COP
04(hex): CANGIO
05(hex): CANM10
06(hex): CANSG
the riser number)

Source ID

Causes and
1 CAN node SW download failed Check the CAN bus / power
Actions
because the CAN bus / power tab to this node for
cable tab to this node is disconnection or broken wires.
disconnected or broken.
2 CAN node SW download failed Plug off some can nodes and
because of high bus traffic process a controller reset.
After the SW download is
done, plug in the other nodes.
These nodes should be served
now.
3 CAN node SW download failed Replace node HW and execute
because the node HW is node freeze command in
defect service interface
1304 CAN
This section describes the 1300_11349_CAN error CAN.

Summary
Description

Extra Info
01(hex): CANIC
02(hex): Door
03(hex): COP
04(hex): CANGIO
05(hex): CANM10
06(hex): CANSG
the riser number)

Source ID
1305 CAN Duplicate Node Detected
This section describes the 1300_11349_CAN error CAN Duplicate

Summary Node Detected.
The CAN network management detected a duplicate CAN node. There

Description are at least two CAN nodes which have identical node IDs.
8 digit hex value 0xSTUVWXYZ where:

Extra Info
ST: defines the node_ID which is duplicated

Source ID

Causes and
1 An additional node was Use a nonexistent node ID
Actions
connected to the CAN bus with (range 1 to 127) for the new
a node-ID which is already node.
connected in the network.
1306 CAN Dynamic Node ID Configuration
Error
This section describes the 1300_11349_CAN error CAN Dynamic

Summary Node ID Configuration Error.
The CAN LSS (Layer Setting Service) failed. There is at least one CAN
Description node which requested the LSS service. During LSS, an error was
generated. This error is recorded only once a day in the errorlog
regardless of the occurrence rate.

Extra Info
AB: Number of errors which occured since the last controller reset.
Highest number of errors is 255. In case the amount of errors exceeds
255, the number will still be 255.
CD: not used
EF:not used
GH:not used

Source ID

Causes and
1 CAN Layer Setting Service Disconnect related node
Actions
Error because expected
answer from LSS slave not
received
Error because a LSS slave
was configured but still
answers to LSS commands
Error because identified node
(by LSS) can not be configured
with new node-ID
1307 CAN Node Configuration Failed
This section describes the 1300_11349_CAN error CAN Node

Summary Configuration Failed.
The software (CAN node configurator) failed to configure a CANopen

Description node. The writing down of the related parameters was not successful.

Extra Info
AB: defines the node_ID of the node
CD: defines the location

00(hex): undefined
01(hex): floor location
02(hex): car location
EF: defines the parameter type which failed to configure

00(hex): undefined
01(hex): Floor Terminal
(to be extended)
GH: defines the node type

00(hex): undefined
01(hex): CANIC
02(hex): Door
03(hex): COP
04(hex): CANGIO
05(hex): CANM10
06(hex): CANSG

Source ID
Causes and
1 New core SW has been Wait until SW download to all
Actions
installed which demands a FW M10 terminals has been
download to the M10 finished.
terminals. This SW download
has not been done yet.
2 Terminal resets during Reset elevator control
configuration
3 M10 terminal is defect Exchange related M10 terminal
(see extra info)
4 CAN bus disturbance Check CAN bus wiring. Check
CAN bus terminating resistor.
There must be only two
resistors in the whole network.
Thus the resistance between
the two CAN lines should be
around 60 Ohm
1308 CAN GC Controller Error
This section describes the 1300_11349_CAN error CAN GC Controller

Summary Error.
The Can controller failed to successfully send one or more Can

Description messages.
Hexadecimal value 0xABCDEFGH, where:

Extra Info
A: channel number (1 or 2)
then B..H are for R&D use only:
B: software module ID
CD: number of failed tx_rqst
EF: number of failed new_dat
GH: number of failed rmt_pnd
R&D only: Identification of software source file

Source ID

Causes and
1 defect CAN controller replace the board where the
Actions
CAN controller for the CAN
channel listed in the "A" field of
the extra info is located
(depending on system: EBLON
or ASIX)
1309 CAN GC Controller Bus Off

Summary Bus Off.
The Can controller entered the "Busoff" state.

Description Busoff is entered when there is an abnormal rate of occurrences of
errors on the CAN bus. This results in the controller going busoff.
During busoff, no messages can be received or transmitted. GC
software recognizes this state of the controller and re-initializes it.

Extra Info
B: software module ID (for R&D only)
CDEFGH: number of busoff occurrences since last report

Source ID

Causes and
1 CAN bus cable characteristics check and replace CAN bus
Actions
cable
2 CAN bus installation: cable check and correct bus
quenches, bad termination installation
resistors, bad terminal
connectors
3 External disturbance sources remove disturbance sources
1310 CAN GC Controller Bus Warning

Summary Bus Warning.
The Can controller entered the "Bus warning" state.

Description This state is entered when there is an abnormal rate of occurrences of
errors on the CAN bus.

Extra Info
B: software module ID (for R&D only)
CDEFGH: number of bus warning occurrences since last report

Source ID
1311 CAN Peripheral Controller Bus Off
This section describes the 1300_11349_CAN error CAN Peripheral

Summary Controller Bus Off.
The CAN controller of a peripheral node has been in the "Busoff" state.
Description Busoff is entered when there is an abnormal rate of occurrences of
errors on the CAN bus. This results in the controller going busoff.
During busoff, no messages can be received or transmitted.
Hexadecimal value 0x00CDEFGH, where:

Extra Info
CDEF: reporting node code (106=CANIC)
GH: node channel code (for CANIC: 1=CANopen, 2=S-CAN)

Source ID

Causes and
1 CAN bus cable characteristics check and replace CAN bus
Actions
cable
2 CAN bus installation: cable check and correct bus
quenches, bad termination installation
resistors, bad terminal
connectors
3 External disturbance sources remove disturbance sources
1312 CAN LSS No Node Id Left
This section describes the 1300_11349_CAN error CAN LSS No Node

Summary Id Left.
The CAN LSS (Layer Setting Service) tries to assign a new Node Id to
Description a node which was identified by LSS procedure but failed because of
lack of free Node identifiers. This can happen if the max number of
configurable nodes allowed in the bus is reached or a huge amount of
nodes
have to be reconfigured by LSS due to duplicated nodes in the
bussystem.
The maximum number of configurable CAN nodes is 58.
None
Extra Info

Source ID

Causes and
1 CAN LSS No Node Id Left Remove CAN nodes.
Actions
Event because of max number
of configurable CAN nodes in
the bus have been exceeded.
2 CAN LSS No Node Id Left Perform single controller reset.
Event because of distribution
of new node ids by LSS. This
can happen if duplicated nodes
are detected in the bussystem.
These nodes are resetted and
new configured by LSS. The
old node id can only new
distributed after a controller
reset.
1401 SW_Event
This section describes the VF error SW_Event.

Summary
General software event

Description
Normal operation event

Extra Info
None.
Source ID
1402 SW_Warning
This section describes the VF error SW_Warning.

Summary
General software warning

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1403 SW Error
This section describes the VF error SW Error.

Summary
General software error

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1404 VarOutOfRange
This section describes the VF error VarOutOfRange.

Summary
Exceeded range for parameter value

Description
None.
Extra Info
None.
Source ID

Causes and
1 RAM data destroyed Double-reset PGO
Actions
2 ROM data destroyed Call EBI for software
replacement
1405 JHC_Pressed
This section describes the VF error JHC_Pressed.

Summary
Stop button JHC pressed

Description

Extra Info
None.
Source ID
1406 JHM_Pressed
This section describes the VF error JHM_Pressed.

Summary
Stop button JHM pressed

Description

Extra Info
None.
Source ID
1407 JHSG_Pressed
This section describes the VF error JHSG_Pressed.

Summary
Stop button JHSG pressed

Description

Extra Info
None.
Source ID
1408 Supply24V_OFF
This section describes the VF error Supply24V_OFF.

Summary
No 24V supply
Description
None.
Extra Info
None.
Source ID

Causes and
1 Missing or defective 24V Check 24V supply
Actions
supply
2 Missing WD (resistor-diode) Install appropriate device
device on the brake (electro- properly
magnetical interferences)
3 Net power failure
1409 DriveLocked
This section describes the VF error DriveLocked.

Summary
Drive has been blocked by control

Description

Extra Info
None.
Source ID
1410 UnknownFloor
This section describes the VF error UnknownFloor.

Summary
Demanded floor has not been learnt

Description
None.
Extra Info
None.
Source ID

Causes and
1 Number of learnt floors does Check Selector Translation
Actions
not correspond with PCT Table
1411 SF_Fault
This section describes the VF error SF_Fault.

Summary
SF relay error
Description
None.
Extra Info
None.
Source ID

Causes and
Actions
and SF1
1412 SF1_Fault
This section describes the VF error SF1_Fault.

Summary
SF1 relay error

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
and SF1
1413 KB_Fault
This section describes the VF error KB_Fault.

Summary
Error del contactor KB

Description Los contactos de freno KB ó KB1 no conmutan adecuadamente.
El software espera información de KB y KB1
Ninguna.
Extra Info
Ninguna.
Source ID

Causes and
1 Contactos de freno Comprobar el ajuste de los
Actions
defectuosos contactos
2 Mal funcionamiento del freno Comprobar el freno
mecánico
3 Observar el freno durante su
apertura - ambos lados deben
abrirse simétricamente
1414 ShaftChecksum
This section describes the VF error ShaftChecksum.

Summary
Destroyed shaft image data

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Corrupted data Perform a learn trip
1415 StartFailed
This section describes the VF error StartFailed.

Summary
Trip start failed due to missing reaction of Variodyn

Description
None.
Extra Info
None.
Source ID

Causes and
1 BARMAG error ® red LED on Perform reset on BARMAG
Actions
ER113 ER113
2 Open safety circuit (after- Check door contacts
effect)
1416 TargetFailure
This section describes the VF error TargetFailure.

Summary
Target out of permitted range

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Position lost Call EBI
2 Wrong direction Call EBI
1417 CarNotAtLevel
This section describes the VF error CarNotAtLevel.

Summary
Bad stopping precision on target floor

Description
None.
Extra Info
None.
Source ID

Causes and
1 Inaccurate setting of BARMAG Check BARMAG parameters
Actions
parameters
1418 CarOutOfFloor
This section describes the VF error CarOutOfFloor.

Summary
Car has not reached target floor

Description
Position [Inc]
Extra Info
None.
Source ID

Causes and
1 Trip interruption caused by Check wiring PGO-BARMAG
Actions
BARMAG
1419 KSE_Int_Fail
This section describes the VF error KSE_Int_Fail.

Summary
No interrupt in spite of signal change

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Interferences on KSE
signal
1420 KS_MagnetPos
This section describes the VF error KS_MagnetPos.

Summary
KS magnet unexactly set (test during learn trip)

Description
Affected floor
Extra Info
None.
Source ID

Causes and message
Actions
1 Check KS magnets
1421 KSE_MagnetPos
This section describes the VF error KSE_MagnetPos.

Summary
KSE magnet unexactly set (test during learn trip)

Description
0x01: Lower KSE magnet

Extra Info 0x02: Upper KSE magnet
0x03: Uppermost KSE magnet
Affected floor
None.
Source ID

Causes and message
Actions
1 Check and adjust KSE
magnets
1422 KS_Bounce
This section describes the VF error KS_Bounce.

Summary
Malfunction caused KS interrupt

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Interferences on KS
signal
1423 KSE_Bounce
This section describes the VF error KSE_Bounce.

Summary
Malfunction caused KS interrupt

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Interferences on KS
signal
1424 SynchFailed
This section describes the VF error SynchFailed.

Summary
Unsuccessful synchronisation trip

Description
None.
Extra Info
None.
Source ID

Causes and
1 KS on bottom floor not found Check KSE distance
Actions
2 Check KS magnet
3 After-effect of a previous error Check system for previous
errors
1425 IO_NotPresent
This section describes the VF error IO_NotPresent.

Summary
Not all necessary I/O’s are configured

Description
None.
Extra Info
None.
Source ID

Causes and
1 Destroyed ROM data Call EBI for software
Actions
replacement
1426 VF_Notstop
This section describes the VF error VF_Notstop.

Summary
Variodyn performed emergency stop before brake point

Description
Speed at brake activation [mm/s]

Extra Info
None.
Source ID

Causes and
1 Improper connection PGO- Check connection PGO-
Actions
BARMAG BARMAG
1427 DeltaS_2BP
This section describes the VF error DeltaS_2BP.

Summary
Distance error KS_Interrupt - 2nd brake point

Description
s2’ [Inc]
Extra Info
None.
Source ID

Causes and
1 Possible error causes Actions to be taken
Actions
2 Inaccurate parameter setting Check BARMAG drive
(BARMAG) parameter (CADI/SMLCD)
1428 TEL_Request
This section describes the VF error TEL_Request.

Summary
Telegram could not be requested

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1429 TEL_Provide
This section describes the VF error TEL_Provide.

Summary
Telegram could not be provided

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1430 TEL_Reply
This section describes the VF error TEL_Reply.

Summary
Telegram could not be replied

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1431 TEL_Get
This section describes the VF error TEL_Get.

Summary
Unsuccessful VCOM_Get on telegram

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1432 TEL_ReadQueue
This section describes the VF error TEL_ReadQueue.

Summary
Reading error on telegram queue

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1433 TEL_VCOMopen
This section describes the VF error TEL_VCOMopen.

Summary
Error on VCOM_open
Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1434 Unknown_TEL
This section describes the VF error Unknown_TEL.

Summary
Unknown telegram occurred

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1435 No_ANT_PCT (Not Used)
This section describes the VF error No_ANT_PCT (Not Used).

Summary
Missing standard drive parameter in PCT

Description
ID of parameter group (PCT_GP_ANT = 02h)

Extra Info
None.
Source ID
1436 No_VF20_PCT
This section describes the VF error No_VF20_PCT.

Summary
Missing VF20/30 drive parameter group in PCT

Description
ID of parameter group (PCT_GP_VF20_30 = 6Eh)

Extra Info
None.
Source ID

Causes and
1 Wrong PCT for the concerned Change PEROM with a
Actions
commission suitable PCT or perform a
PCT-download with CADI
1437 OverTempMotor
This section describes the VF error OverTempMotor.

Summary
Response of engine temperature measuring

Description
Temperatur value [Celsius degrees]

Extra Info
None.
Source ID

Causes and
1 Engine temperature too high Elevator system will recover by
Actions
itself under normal
circumstances. Otherwise, put
the elevator temporarily out of
service
2 Missing temperatur element Check installation
KD150
1438 NoIncrement
This section describes the VF error NoIncrement.

Summary
No tacho increments during trip

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Improper installation of Check tacho and wiring
tacho
1439 InvldMovement
This section describes the VF error InvldMovement.

Summary
Invalid car movement

Description
Should not occur (SW problem)

Extra Info
None.
Source ID

Causes and message
Actions
1 Trip start before ending of Check tacho
previous trip
1440 OverSpeed
This section describes the VF error OverSpeed.

Summary
Car speed exceeded

Description
None.
Extra Info
None.
Source ID

Causes and
1 Improper parameter settings Check BARMAG parameter
Actions
(BARMAG) values (CADI/SMLCD)
1441 OverSpeedKSE
This section describes the VF error OverSpeedKSE.

Summary
Speed exceeded in shaft end

Description
None.
Extra Info
None.
Source ID

Causes and
1 Improper parameter settings Check BARMAG parameter
Actions
(BARMAG) values (CADI/SMLCD)
2 Check KSE distance
1442 DirectionErr
This section describes the VF error DirectionErr.

Summary
Car movement in wrong direction

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check tacho
1443 DirNotAllowed
This section describes the VF error DirNotAllowed.

Summary
Wrong direction in shaft end

Description
None.
Extra Info
None.
Source ID

Causes and
1 Manual trip on cabin roof in Reset ® Synchronization trip
Actions
wrong direction in shaft end
area
2 If still necessary, perform a
learn trip
1444 PosLost_Tacho
This section describes the VF error PosLost_Tacho.

Summary
Tacho check showed position error

Description
None.
Extra Info
None.
Source ID

Causes and
1 Reset ® Synchronization trip
Actions
learn trip
1445 PosLost_KS
This section describes the VF error PosLost_KS.

Summary
KS check showed position error

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
learn trip
1446 PosLost_KSE
This section describes the VF error PosLost_KSE.

Summary
KSE check showed position error

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
learn trip
1447 FloorPrec
This section describes the VF error FloorPrec.

Summary
Inaccurate stopping on 8 of 10 trips

Description WARNING: Inaccurate stopping on 4 of 10 trips
NO_LOG: Accurate stopping of the last 10 trips
Message used for Servitel

Extra Info
None.
Source ID

Causes and
1 Elevator system improperly Improve elevator adjustment
Actions
adjusted
1448 RSK_Fault
This section describes the VF error RSK_Fault.

Summary
RSK state does not correspond with the input

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
2 Check auxiliary contacter of
RSK and RSK1
1449 RSK1_Fault
This section describes the VF error RSK1_Fault.

Summary
RSK1 state does not correspond with the input

Description
None.
Extra Info
None.
Source ID

Causes and
Actions
2 Check auxiliary contacter of
RSK and RSK1
1450 TIF_WriteErr
This section describes the VF error TIF_WriteErr.

Summary
Error on write access to TIF register.

Description
Error (difference) [Increments]

Extra Info
None.
Source ID

Causes and message
Actions
1 Malfunction of TIF device Replace TIF
1451 TIF_ReadErr
This section describes the VF error TIF_ReadErr.

Summary
Error on read access to TIF register.

Description
Error (difference) [Increments]

Extra Info
None.
Source ID

Causes and message
Actions
1 Malfunction of TIF device Replace TIF
1452 NoStartOK
This section describes the VF error NoStartOK.

Summary
Drive is waiting for StartOK signal of the control

Description
System normally recovers by itself

Extra Info
None.
Source ID

Causes and message
Actions
1 Reset PGO
1453 SK ErrorStart
This section describes the VF error SK ErrorStart.

Summary
Safety chain prevents the elevator from starting a trip

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1454 SK ErrorRun
This section describes the VF error SK ErrorRun.

Summary
Safety chain has interrupted a trip

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Open contact KS or KTC Check door contacts
1455 SynchTrip
This section describes the VF error SynchTrip.

Summary
A synchronisation trip has been started

Description
Extra Info
None.
Source ID
1456 LearnTrip
This section describes the VF error LearnTrip.

Summary
A learn trip has been started

Description
Extra Info
None.
Source ID
1457 CorrTrip
This section describes the VF error CorrTrip.

Summary
A correction trip has been started

Description
Extra Info
None.
Source ID
1458 Inv_VF20_PCT
This section describes the VF error Inv_VF20_PCT.

Summary
Invalid parameter in VF20/30 parameter group

Description
0x01-0x80 (parameter-ID):
Extra Info Drive parameter in PCT out of range
0x01: P_VF20_30_TACHO_FACTOR
0x02: P_VF20_30_KSE_DISTANCE
0x03: P_VF20_30_KSERE_DISTANCE
0x04: P_VF20_30_GAP_LENGTH
0x05: P_VF20_30_LOAD_TYPE
0x20: P_VF20_30_FN
0x21: P_VF20_30_VKN
0x22: P_VF20_30_FC_MAX_R
0x23: P_VF20_30_MM_IMP
0x24: P_VF20_30_FT_RU1
0x25: P_VF20_30_DELTA_U
0x26: P_VF20_30_BARMAG_RES_0
0x27: P_VF20_30_T_DIFF
0x28: P_VF20_30_T_AUF
0x29: P_VF20_30_U_END
0x2A: P_VF20_30_S_KBR_2
0x2B: P_VF20_30_ BARMAG_RES_
0x2C: P_VF20_3 BARMAG_RES_0_
0x80: P_VF20_30_SELECTOR_TRANS_TABLE
0xFE: condition U_END >= DELTA_U not fulfilled.
0xAA (GENERAL_PARAM): Stored general drive parameter (Tacho-
1m, KSE-Distance, KSERE-Distance, GAP-Length, Load-Type) out of
range.
0xBB (BARMAG_PARAM): Stored converter-specific drive parameter
(FN, VKN, MM_IMP, S_KBR_2, FT_RU1, DELTA_U, FC_MAX_R,
T_DIFF, T_AUF, U_END) out of range
None.
Source ID

Causes and
1 Parameter value wrongly set in Adjust appropriate parameter
Actions
PCT with CADI/SMLCD
2 PCT structure invalid (one or Replace PCT (Perform a PCT-
more parameters missing) download with CADI or change
PEROM)
1459 Inv_BMG_Param
This section describes the VF error Inv_BMG_Param.

Summary
Parameter values stored in the frequency converter (BARMAG) do not

Description correspond with their equivalents in the control software
(inconsistence)
0x01: 0x0A: BARMAG parameter ID

Extra Info 0x01: FN
0x02: VKN
0x03: MM_IMP
0x04: S_KBR_2
0x05: FT_RU1
0x06: DELTA_U
0x07: FC_MAX_R
0x08: T_DIFF
0x09: T_AUF
0x0A: U_END
None.
Source ID

Causes and
1 Communication PGO - Check RS232 connection PGO
Actions
BARMAG not - BARMAG
successful/impossible
2 Communication PGO - Perform double-reset on PGO
BARMAG had been interrupted and reset on BARMAG, wait
approx. 5 minutes (!)
1460 LastBlockTime
This section describes the VF error LastBlockTime.

Summary
Provides block time after a long blocking period

Description
Time [min]
Extra Info Informational message
None.
Source ID
1461 LearnFailed
This section describes the VF error LearnFailed.

Summary
Unsuccessful learn trip

Description
None.
Extra Info
None.
Source ID

Causes and
1 After-effect of a previous error Check system for previous
Actions
errors
1462 LearnMesProbl
This section describes the VF error LearnMesProbl.

Summary
Contradictory results of learn trip

Description
0x00: Number of floors out of range

Extra Info 0x01: Affected floor
None.
Source ID
1463 TEL_Send
This section describes the VF error TEL_Send.

Summary
Telegram could not be sent successfully

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Call EBI
1464 NoBpReaction
This section describes the VF error NoBpReaction.

Summary
BARMAG does not react on brake point

Description
None.
Extra Info
None.
Source ID

Causes and
1 Check wiring PGO-BARMAG
Actions
2 Check BARMAG ER113
module
1465 Jump_Tacho
This section describes the VF error Jump_Tacho.

Summary
Tacho value has jumped

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check tacho
1466 SK_Bridging
This section describes the VF error SK_Bridging.

Summary
Hardware error on trial of premature door-opening

Description
None.
Extra Info
None.
Source ID

Causes and
1 Malfunction of door bridging Check relays VRKUET and
Actions
KUET/KUET1
1467 PosLost_IUET
This section describes the VF error PosLost_IUET.

Summary
IUET check showed position error

Description
None.
Extra Info
None.
Source ID

Causes and
1 Reset PGO, then perform a
Actions
Learn Trip
1468 Supply24VOn
This section describes the VF error Supply24VOn.

Summary
24V supply activated

Description
Extra Info
None.
Source ID
1469 VF20_Blocked
This section describes the VF error VF20_Blocked.

Summary
VF20 has not been ready for start for more than 10 seconds (TRV
Description signal)
None.
Extra Info
None.
Source ID

Causes and
1 Reset BARMAG. If not
Actions
successful, check internal
error-log of BARMAG with a
terminal emulation:
2 Short Manual: To start, press
‘s’
3 Press ‘f’, read error (s. below)
4 To quit, press F10
5 Reset BARMAG again.
6 Internal BARMAG error Possible Causes
messages:
7 U_ZK < UZK_MIN Power mains voltage low
8 Missing mains phase
9 U_ZK > UZK_MIN Chopper resistor not
connected, wrong specificied
(Ohm) or defective
10 Improper parameter setting
11 I > I_MAX Defective freq. converter
VF20/30
12 Short-circuit (ground) on motor
wiring
13 Improper parameter setting
14 TIBR > 5 S Interface board does not reset
start signal
15 Check brake function
16 NET > OFF Malfunction of freq. converter
VF20/30
17 KEINE IMPULSE Check tacho power supply (Pin
1 and 2 on IG100-connector)
18 Defective VF20 control board
19 Slippage of tacho rope
20 Defective tacho device
21 ZEIT V K-FAHRT Instruction correction trip has
not been reset
22 VBET < 1.15 x VKN/2 Value VKN set too high
23 DELTA_U too low
24 Slippage of tacho rope
25 Wiring defects
26 Defective freq. convert.
27 Mechanical defect on elevator
system
28 VBET > 1.15 x VKN Value VKN set too low
29 FC_MAX_R set too high
30 MM_IMP set too high
31 Mechanical defect on elevator
system
32 TEMP > T_MAX Permanent exceeding of
nominal current
33 Cooling blowers not connected
or defective
34 Air stream restrained
35 Wrong direction of rotation
1470 Safety110V
This section describes the VF error Safety110V.

Summary
Detected open safety chain away from T1

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1471 SafetySPT
This section describes the VF error SafetySPT.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1472 SafetyKNE
This section describes the VF error SafetyKNE.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1473 SafetyRTS
This section describes the VF error SafetyRTS.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1474 SafetyEnd
This section describes the VF error SafetyEnd.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1475 SW_BlockPerm
This section describes the VF error SW_BlockPerm.

Summary
Fatal software error occurred

Description
None.
Extra Info
None.
Source ID

Causes and
1 Solve the problem and reset
Actions
the system
1476 DataDestroyed
This section describes the VF error DataDestroyed.

Summary
Illegal data changement during runtime

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Double-reset PGO
1477 VF_StartError
This section describes the VF error VF_StartError.

Summary
VF20/30 interrupted starting trial that had been already begun

Description
Distance covered away from start [mm]

Extra Info
None.
Source ID

Causes and
Actions
(BARMAG) necessary) BARMAG
parameter with CADI/SMLCD
1478 VF_ShortBrake
This section describes the VF error VF_ShortBrake.

Summary
VF20/30 stopped too early after 1st brake point

Description
Distance to target floor [mm]

Extra Info
None.
Source ID

Causes and
Actions
(BARMAG) necessary) BARMAG
parameter with CADI/SMLCD
1479 VF_StopSpeed
This section describes the VF error VF_StopSpeed.

Summary
VF20/30 over-speed at activation of mechanical brake

Description
Speed at activation of brake [mm/s]

Extra Info Informational message
None.
Source ID

Causes and message
Actions
1 Malfunction of BARMAG Check wiring to BARMAG
1500 Travel Control Ext Error Base Id
This section describes the Travel Control Ext error Travel Control Ext
Summary Error Base Id.
Description
Extra Info
Source ID
1501 Invalid Car Position
This section describes the Travel Control Ext error Invalid Car Position.
Summary
The actual car position read from the position encoder is not in the
Description range of the learnt floor/stop positions (1m above the top floor / 1m
below the bottom floor).
The monitoring is not active when a learn trip is needed or is being

performed. It is not reported with active montage (JMOF on). The error
is surpressed during active acceptance testing, since some of the tests
require the elevator to move beyond the normally acceptable range
[extreme floors +/- 1meter]. On systems with incremental position
tachos this error is not reported.
Actual car position (decimal value in [mm]) when the error occurred.
Extra Info
Identification number of the source code file

Source ID

Causes and
1 Car position encoder was Do a learn trip
Actions
moved (without car) while not
connected to control or with
power down (AGSI)
2 Car position encoder was Do a learn trip
replaced
3 Car position encoder faulty Replace encoder and do a
learn trip
1502 Position Jump
This section describes the Travel Control Ext error Position Jump.
Summary
The software calculates a difference of the car position values for two
Description consecutive readings (read cycle: 10msec) which exceeds a travel
distance of 240mm. After 5 consecutive wrong reading cycles the
software logs the error: the elevator performs an emergency stop and
is blocked permanent.
This monitoring limits the 'change rate' of the readings from the position
tacho and prevents that the software calculates wrong a false floor
position (or speed) for the car. The limit value of 240mm is
independent of the car speed (240mm is less than the foreseen
minimum floor distance). The limit distance is not adjustable.
Value of position tacho [increments]

Extra Info
Identification number of source file

Source ID

Causes and
1 EMC problems with car Check wiring of car position
Actions
position encoder (absolute encoder
encoder)
2 Faulty car position encoder Replace encoder
3 Faulty wiring of car position Check wiring and connectors
encoder
1503 SI_Sensor_Defect
This section describes the Travel Control Ext error SI_Sensor_Defect.

Summary
During a trip MOSIS sends a message to the control when it

Description detects/passes a floor magnet; the control checks if for each floor
position learnt during the learn trip MOSIS sends a corresponding
message to the control. In case MOSIS detects no floor magnet
(missing magnet) for a learnt floor the control will log the error
message. The monitoring of the floor sensors is done during automatic
trips only.
The default severity for this error is set to 'no log' which means the
error is not logged under normal circumstances. The logging can be
activated by setting the corresponding severity to 'Error' or other with
CADI.
The position value for the missing floor sensor

Extra Info
Identification number of the source file in the core software

Source ID

Causes and
1 Sensors made of steel causes Change sensor to Aluminium
Actions
problems of detection at low type.
speeds.
2 Magnet on the floor dropped Put the floor magnet back in
off. place.
1504 Safety T6
This section describes the Travel Control Ext error Safety T6.
Summary
Used for the monitoring of the landing door lock contacts KV. The
Description safety circuit is open before the last tap but after the previous tap. The
message is logged if:
a) the safety circuit opens during a trip due to a landing door lock
contact (any) which opens unexpectedly.
b) the safety circuit does not close as expected after the door has
closed.
Refer also to wiring diagram for contacts causing the error.
Extra Info
development only.

Source ID

Causes and
1 Bad landing door lock
Actions
contact(s) KV
1505 Invalid Floor Position during Trip
This section describes the Travel Control Ext error Invalid Floor
Summary Position during Trip.
Inconsistent floor position found during a trip. The error is logged when:
Description a.) the software detects no related floor signal (e.g. hardware input
KUET/KUET2) at a car position for which a floor/stop was detected
during the learn trip;
b.) the software sees the input for the floor/stop detection (e.g.
KUET/KUET2) switching at a car position not related to a position
found during the learn trip.
The monitoring is disabled:

- when a learn trip is needed or is being performed.
- with active montage (JMOF on).
- when the mains switch JH is off
On systems with incremental position tachos this error is not reported

when the car position is unknown and during a 'sync trip' .
Extra Info
Identification of the source code file

Source ID

Causes and
1 Missing floor magnet or floor Check the hardware in the
Actions
vane (KUET/KUET2). hoistway.
2 Faulty input on interface board Check/replace the interface
for KUET/KUET2. board.
3 Mechanical problem with Check fixation of vane(s).
fixation of floor vane.
1506 Invalid Floor Position in Standstill
This section describes the Travel Control Ext error Invalid Floor
Summary Position in Standstill.
Inconsistent floor position found in standstill. The error is logged when:

Description a.) the software detects no related floor signal (e.g. hardware input
KUET/KUET2) at a car position for which a floor/stop was detected
during the learn trip;
b.) the software sees the input for the floor/stop detection (e.g.
KUET/KUET2) switching at a car position not related to a position
found during the learn trip.
The monitoring is disabled:

- when a learn trip is needed or is being performed.
- with active montage (JMOF on).
- when the mains switch JH is off.
On systems with incremental position tachos this error is not reported

when the car position is unknown and during a 'sync trip' .
Extra Info
Identification of the source code file

Source ID

Causes and
1 Missing floor magnet or floor Check the hardware in the
Actions
vane (KUET/KUET2). hoistway.
2 Faulty input on interface board Check/replace the interface
for KUET/KUET2. board.
3 Mechanical problem with Check fixation of vane(s).
fixation of floor vane.
1507 KB ON standstill
This section describes the Travel Control Ext error KB ON standstill.

Summary
The control detects that a brake is released (ON) in standstill. A brake

Description contact KB is logically active in standstill indicating that the respective
brake (lever) is not in the closed position.
Shows the status of the individual KB inputs. The 8 digit hexadecimal

Extra Info number (0xABCDEFGH) has the following meaning:
Value 'A': Internal state of brake control channel 1 (brake_state, ch1) in

software. The values are:
0: BRAKE_INIT
1: NO_PARAMETERS (Brake parameters missing)
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'B':Internal state of brake control channel 2 (brake_state, ch2) in

0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'C': Physical state (0/1) of contact KB

Value 'D': Physical state (0/1) of contact KB1
Value 'E': Physical state (0/1) of contact KB2 [only if input used, else 0]
Value 'F': Physical state (0/1) of contact KB3 [only if input used, else 0]
Value 'G': Physical state (0/1) of contact KB4 [only if input used, else 0]
Value 'H': Physical state (0/1) of contact KB5 [only if input used, else 0]

Source ID

Causes and
1 Faulty brake contact(s) KBx Check the function of the brake
Actions
contacts.
2 Bad adjustment of the brake Check the operation of the
contact(s) brake contact(s) and (re-
)adjust if necessary
3 Mechanical problem on the Check the brake. Observe the
brake brake when it opens. Both
sides of the brake should open
symmetrically.
4 Wrong parameter value for Check drive parameters
parameter 'KB feedback type' (settings) for correct brake
type.
5 Faulty input on the interface Verifiy faulty input and replace
board for the KB inputs board
(ASILOG, ASIX . .etc).
1508 KB not ON start
This section describes the Travel Control Ext error KB not ON start.
Summary
The control detects that the brake does not open (open = ON) during
Description trip start as expected. A brake contact KB does not switch when
starting a trip indicating that the respective brake (lever) does not open
after activation of the brake (SB or MBB). The error may also indicate a
faulty KB contact.

Value 'A': Internal state of brake control (brake_state) in software. The

values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING

0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING

Idnetification number of source file

Source ID

Causes and
Actions
contacts.
symmetrically.
type.
1509 KB OFF Run
This section describes the Travel Control Ext error KB OFF Run.
Summary
The control detects that a brake is closed (OFF) during a trip. A brake
Description contact KB is inactive during a trip indicating that the respective brake
(lever) is not in the open position.


values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING

0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING


Source ID

Causes and
Actions
contacts.
symmetrically.
type.
1510 KB not OFF stop
This section describes the Travel Control Ext error KB not OFF stop.
Summary
The control detects that the brake does not close (closed = OFF) at the
Description end of a trip as expected. A brake contact KB does not switch when
finishing a trip as expected indicating that the respective brake (lever)
did not close after deactivation of the brake (SB or MBB). The error
may also indicate a faulty KB contact.
There is an additional monitoring done by the software in case both
(all) brake contacts do not switch at the end of a trip. In this case a so
called safety parking is performed. See error 'Brake not Set' (#138) for
more details.


values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING

0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING

Source ID

Causes and
Actions
contacts.
symmetrically.
type.
1511 Broken Traction Media
This section describes the Travel Control Ext error Broken Traction
Summary Media.
Description
Extra Info

Source ID

Causes and
1 Failure of electrical wiring of Check the wiring and input,
Actions
the KSS switch or input repair or replace as required
2 Malfunction of the KSS switch Check and eventually replace
switch
3 A traction media went loose or Check for a slack or broken
is broken traction media, repair or
replace as required
1512 SI Communication Lost
This section describes the Travel Control Ext error SI Communication

Summary Lost.
The control detects a lost CAN communication to the shaft info system
Description (MoSIS / SALSIS). The control constantly monitors the position
messages recevied over the CAN bus. It logs the error if no position
message arrives for more than 50ms during a trip or 500ms at
standstill (MoSIS/SALSIS send messages every 10ms during a trip and
every 100ms in standstill). The message is logged when the CAN bus
is interrupted (e.g. plug of CAN bus cable removed) or after
interrupting power supply for MoSIS/SALSIS. If the communication fails
during a trip:
For elevator system with STM belt traction media and small traction
sheave diameter:
the control performs a rampdown stop and moves the car with slow
speed to the next floor.
For elevators with steel rope traction media:

the control continues the trip to serve the call using the speed signal
from the inverter (V_TACHO). The control will switch back to the signal
from MoSIS/SALSIS (S_TACHO) if the communication is reestablished
within 1sec. This avoids unneccessary aborting of trips. If the
communication is lost for more than 1sec the control stops at the
nearest floor [current SELECTOR] and waits for the communication to
be reestablished.
The elevator is no longer available and no trips can be performed

unless the communication is established again. If the communication to
MOSIS/SALSIS remains interrupted the control will activate FATAL
service (breakdown); see also error 1595.
not used
Extra Info

Source ID
1513 SI UET device fault
This section describes the Travel Control Ext error SI UET device fault.
Summary
This error is reported if the UET relay opens for a reason other than
Description the normal door overbridging, if the relay test fails, or other error
condition related to the UET function of MoSIS/SALSIS. The extra info
describes the message sent by MoSis/SALSIS together with status
change of UET relay.
The extra information is a 8 digit hexadecimal code with the following

Extra Info meaning per digit: STUVWXYZ
S=1: Doors are overbridged

T=1: Below max overbridging speed
U=1 : In door zone
V=1: Overbridging command given
W=1: LUET A magnet detected within 25mm
X=1: Internal error. The error "1515 MOSIS_INTERNAL_LOG" may
also be reported if this bit is set.
Y=1: Error: Number of floors in MoSIS don’t fit number of floors in
control
Z=1: Error: The MoUET relay failed to pick correctly

Source ID

Causes and
1 An internal circuit or relay of Reset the MoSis/SALSIS
Actions
the MoSis/SALSIS device has device by power off/on cycle. If
a severe malfunction. the problem occurs again,
replace the MoSis/SALSIS
device.
1514 Si floor device fault
This section describes the Travel Control Ext error Si floor device fault.
Summary
This error is logged if the MoSIS / SALSIS reports an error condition

Description related to the floor sensor function of MoSIS/ SALSIS. The extra info
describes the message sent by MoSis / SALSIS together with the
status change of floor sensor.

S=1: MoSIS made an adjustment to the floor position

T=1: MosSIS stored this as a new floor
U=0 : Reserved
V=1: Internal error. The error "1515 MOSIS_INTERNAL_LOG" may
also be reported if this bit is set.
W=1: No adjustment made, floor is >50mm from old position
X=1: Floor not stored, another floor is <300mm on opposite side
Y=1: Floor not stored, another floor is <2m on same side
Z=1: New floor not stored or adjusted, speed is >1m/s

Source ID

Causes and
1 An internal circuit or sensor of Reset the MoSIS/SALSIS
Actions
a severe malfunction. the problem still occurs,
replace the MoSis/SALSIS
device.
1515 SI Internal Log
This section describes the Travel Control Ext error SI Internal Log.
Summary
This error is reported if MoSIS / SALSIS logs an entry in its internal

Description error log. An internal error is usually reported together with one or
more of the following errors:
0131 MoSis_KNE_Fault .
0132 SI_ETSL_Fault
1513 SI_UET_Fault
1514 SI_FLOOR_Fault
The message contains the contents of the MoSIS / SALSIS internal

error log as extra info value.
Caution: The meaning of the error codes on MOSIS and SALSIS are
different.

Extra Info meaning per digit: S00000YY
S: Channel number on MoSIS / SALSIS that reports the error. There

are 2 channels (1,2) for redundancy.
YY= MoSIS / SALSIS internal ID of the error being logged

(Hexadecimal):
Error Numbers for MOSIS (for SALSIS see below):

Value: Name / Meaning
hex00: NoError / No error, warning or info to report
hex01: ERR_SOFTW_POS / Position error detected by filter in MOSIS
software
hex02: not used
hex03: ERR_INTERNAL_FLOOR_ERR / Case #1:Error detected
concerning the redundant storage of highest and lowest floor; the floor
RAMs is erased immediately.
Case #2: Failed comparison between the RAM contents of channel A
and B The KNE will open immediately but the RAM is only erased if
the problem occurs more than 5 times to avoid false RAM erasing
caused by undetected communication errors.
hex04: ERR_FLOORS_ERASED_CMD / Floor positions erased
because of a command from the control.
hex05: ERR_RAM_AB_EXCH / Communication error between channel
A and B when exchanging the RAMs content (UART0)
hex06: ERR_POS_AB_NOT_FIT / Difference of Positions on channel
A and B is greater than 1000mm
hex07: ERR_POS_AB_EXCH / Communication error between channel
A and B when exchanging absolute position (UART1)
hex08: ERR_FLOORS_ERASED_TOOK_PLACE / Floor RAMs erased
after error ERR_INTERNAL_FLOOR_ERR. Occurs after errors 03h,
04h and 0Bh(11dec).
hex09: ERR_RELAIS_TEST_PICK_FAIL / Periodic Relay Test failed
hex0A/dec10: ERR_EMERGENCY / MoSiS detected too many errors;
it is in emergency state. None of the relais will operate until after a
power up. Power to MoSIS must be switched off (JH) and then on
again to clear this error.
hex0B/dec11: ERR_FLOORS_ERASED_STRANGE / MoSIS powered
up on a strange place and erases the floor RAMs
Rem: powering up in precommisioned state will allways cause this
error
hex0C/dec12: WARNING_MEASURING_SYSTEM / not used
hex0D/dec13: ERR_VERSIONS_AB_NOT_FIT / Software-Versions of
channal A and B do not fit
hex0E/dec14: ERR_FLOOR_AGREEMENT / Floor position from B
does not fit the floor position from A. It is normally not possible that the
floor position received from B does not fit the floor position from A,
because B has already testet the condition after it received the floor
from A and will then only send its floor-position back to A if they fit. Can
only occur on channal A.
hex0F/dec15: ERR_UNINTENDED / Unintended car movement
detection; MoSIS goes to emergency mode.
hex10/dec16: ERR_SPEED_FILTER / speed-filter failed
hex11/dec17: ERR_FLOORS_ERASED_NFC / Learn-trip stopped due
to command, or time elapsed or when car speed higher than 1m/s and
MoSIS has not yet learnt the number of commissioned floors; MoSIS
erases floor-RAMs.
hex12/dec18: ERR_ETSL_REL_DROP_FAIL / ETSL-Relay failed to
drop.
hex13/dec19: ERR_KNE_REL_FAIL / KNE-Relay failed to drop
correctly.
hex14/dec20: ERR_UET_REL_FAIL / UET-Relay failed to pick or drop
correctly
hex15/dec21: EXCH_POS_FAILED / Exchange of position between
channels failed
hex16/dec22: EXCH_FLOOR_FAILED / Exchange of floor positions
between channels failed
hex17/dec23: TEST_KNE_PICK_FAIL / KNE Relay failed to pick
during relay test
hex18/dec24: TEST_ETSL_PICK_FAIL / ETSL Relay failed to pick
during relay test
hex19/dec25: TEST_OVERBRL_PICK_FAIL / Test Relay failed to pick
during relay test
hex1A/dec26: TEST_KNE_DROP_FAIL / KNE Relay failed to drop
during relay test
hex1B/dec27: TEST_ETSL_DROP_FAIL / ETSL Relay failed to drop
during relay test
hex1C/dec28: ETSL_PICK_FAIL / ETSL Relay failed to pick
hex1D/dec29: KNE_PICK_FAIL / KNE Relay failed to pick
hex1E/dec30: UET_PICK_FAIL / UET Relay failed to pick
hex1F/dec31: FLOOR_ERASED_LEARN_TOO_FAST / Floor RAM
was erased because the car ran too fast during the learn-trip
hex20/dec32: FLOOR_ERASED_LEARN_TOO_LONG / Floor RAM
was erased because the learn-trip lasted too long
hex21/dec33: INT_FLOOR_ERROR_NUMBER / Floor RAM was
erased because the number of floor is not the same on both channels
hex22/dec34: INT_FLOOR_ERROR_LOWEST / Floor RAM was
erased because the position of bottom floor is not the same on both
channels
hex23/dec25: INT_FLOOR_ERROR_HIGHEST / Floor RAM was
erased because the position of top floor is not the same on both
channels
hex24/dec36: INT_FLOOR_ERROR_POSITION / Floor RAM was
erased because the position of some floor is not the same on both
channels
hex25/dec37: INT_FLOOR_ERROR_CHANNEL_B / Floor RAM was
erased because a floor position was incorrectly verified by channel B
hex26/dec38: STUCK_AT_TEST_FAILED / Stuck-at test at start-up
failed (wrong relay status at start-up)
hex27–2F / … / Reserved for additional errors (Allocated sequentially)
hex30/dec48: CAN_BUS-OFF /
hex31/dec49: CAN_BUS-ERR / unspecified lowlevel bus error
hex32/dec50: CAN Overrun / new message has overwritten the old
one before it was read
hex33/dec51: CAN Sync-Burst / 5 of 10 SYNC messages are sent
within 5ms after the previous one
hex34/dec52: CAN unknown error interrupt / unknown error of the
CAN controller
hex35–3F / … / Reserved for additional errors
hex40/dec64: ETSL (dyn) closed before close / Relay is not open
before the closing
hex41/dec65: KNE (dyn) closed before close / Relay is not open before
the closing
hex42/dec66: UET (dyn) closed before close / Relay is not open before
the closing
hex43/dec67: Overbridging (dyn) closed before close / Relay is not
open before the closing
hex44/dec68: ETSL (dyn) close fail / Unable to engage the relay in
time
hex45/dec69: KNE (dyn) close fail / Unable to engage the relay in time
hex46/dec70: UET (dyn) close fail / Unable to engage the relay in time
hex47/dec71: Overbridging (dyn) close fail / Unable to engage the
relay in time
hex48/dec72: ETSL (dyn) open fail / Unable to disengage the relay in
time
hex49/dec73: KNE (dyn) open fail / Unable to disengage the relay in
time
hex4A/dec74: UET (dyn) open fail / Unable to disengage the relay in
time
hex4B/dec75: Overbridging (dyn) open fail / Unable to disengage the
relay in time
hex4C/dec76: ETSL (dyn) open before opening / Relay is already open
before opening
hex4D/dec77: KNE (dyn) open before opening / Relay is already open
before opening
hex4E/dec78: UET (dyn) open before opening / Relay is already open
before opening
hex4F/dec79: Overbridging (dyn) open before opening / Relay is
already open before opening
hex50/dec80: ETSL (static) open fail / relay is not open as expected
hex51/dec81: KNE (static) open fail / relay is not open as expected
hex52/dec82: UET (static) open fail / relay is not open as expected
hex53/dec83: Overbridging (static) open fail / relay is not open as
expected
hex54/dec84: ETSL (static) close fail / relay is not closed as expected
hex55/dec85: KNE (static) close fail / relay is not closed as expected
hex56/dec86: UET (static) close fail / relay is not closed as expected
hex57/dec87: Overbridging (static) close fail / relay is not closed as
expected
hex58/dec88: ETSL start up fail / ETSL is detected as closed at startup
hex59/dec89: KNE start up fail / ETSL is detected as closed at startup
hex5A/dec90: UET start up fail / ETSL is detected as closed at startup
hex5B/dec91: Overbridging start up fail / ETSL is detected as closed at
startup
hex5C/dec92: Closing Relay state machine fail / SW state machine
has invalid state
hex5D/dec93: Opening Relay state machine fail / SW state machine
has invalid state
hex5E/dec94: Feedback request of non existing relay / False function
parameter
hex5F/dec95: Relay test state machine failed / SW state machine has
invalid state
hex60/dec96: Overbridging relay closed at test start / -
hex70/dec112: Interrupt Watchdog / Internal watchdog timeout
hex71/dec113: Interrupt Break Instruction / Break instruction executed
hex72/dec114: Interrupt Division by Zero / -
hex73/dec115: Power Supply fail / Main supply voltage (24V) below
17V
hex80/dec128: UART 1 time out / Other channel does not respond in
time on this interface
hex81/dec129: UART 1 frame error / Communication frame is
damaged
hex82/dec130: UART 1 parity fail / -
hex83/dec131: UART 1 sequence fail / Expected sequence of
messages is not communicated
hex84/dec132: UART 1 Overrun / New message received before the
last one was read
hex85/dec133: UART 0 time out / Other channel does not respond in
time on this interface
hex86/dec134: UART 0 frame error / Communication frame is
damaged
hex87/dec135: UART 0 parity fail / -
hex88/dec136: UART 0 sequence fail / Expected sequence of
messages is not communicated
hex89/dec137: UART 0 Overrun / New message received before the
last one was read
hex8A–8F / … / Reserved for additional errors
hex90/dec144: UART 1 state machine failed / SW state machine has
invalid state
hex91/dec145: UART 0 state machine failed / SW state machine has
invalid state
hexA0/dec160: Floor Agreement Front failed / Agreement about a
detected floor failed
hexA1/dec161: Floor Agreement Rear failed / Agreement about a
detected floor failed
hexA2/dec162: Floor Agreement Front state machine failed / SW state
machine has invalid state
hexA3/dec163: Floor Agreement Rear state machine failed / SW state
machine has invalid state
hexA4-FF / … / Reserved for SW warnings and infos for development
use only…etc. (Not reported on CADI)
Error Numbers for SALSIS:

Value: Name / Meaning
hex00: NoError / No error/warning or info to report
hex01: ETSL_RELAY_DROP_FAIL / ETSL relay failed to drop.
SALSIS goes to emergency mode. Either feedback contact does not
conduct (oxydized contacts) or the working contact is stuck in the
closed position.
hex02: KNE_RELAY_DROP_FAIL / KNE relay failed to drop. SALSIS
goes to emergency mode. Either feedback contact does not conduct
(oxydized contacts) or the working contact is stuck in the closed
position.
hex03: UET_RELAY_DROP_FAIL / UET relay failed to drop. SALSIS
goes to emergency mode. Either feedback contact does not conduct
(oxydized contacts) or the working contact is stuck in the closed
position.
hex04: OVERBRIDGING_RELAY_DROP_FAIL / ETSL overbridging
relay failed to drop. SALSIS goes to emergency mode. Either feedback
contact does not conduct (oxydized contacts) or the working contact is
stuck in the closed position.
hex05: ETSL_RELAY_PICK_FAIL / ETSL relay failed to pick. SALSIS
goes to emergency mode. The relay cannot be activated or does not
stay active. Also happens when the other channel goes into emergency
state and cuts the relay supply
hex06: KNE_RELAY_PICK_FAIL / KNE relay failed to pick. The relay
cannot be activated or does not stay active.
hex07: UET_RELAY_PICK_FAIL / UET relay failed to pick. The relay
cannot be activated or does not stay active.
hex08: OVERBRIDGING_RELAY_PICK_FAIL / Overbridging relay
failed to pick. The relay cannot be activated or does not stay active.
hex09: VEL_POS_SUCC_SGN_CONTRADICTION / Position/velocity
plausibility check failed; position change is in contradition with speed
sign.
hex0A/dec10: TOO_BIG_POS_DIFF_MOD_SAF / Position/velocity
plausibility check, unplausible acceleration.
hex0B/dec11: TOO_BIG_VEL_MOD_POS / Position/velocity
plausibility check failed; position is above the maximum possible value
and speed is above maximum possible value.
hex0C/dec12: TOO_BIG_VEL_MOD_SAF / Position/velocity
plausibility check, speed is too high, not plausible.
hex0D/dec13: POS_A_B_DO_NOT_FIT / Difference between position
on channel A and B too large (>400mm); SALSIS goes to emergency
mode
hex0E/dec14: POS_FILTER_ERR / Too many erros in positon filter
(three wrong position in a row); SALSIS goes to emergency mode
hex0F/dec15: ERR_UNINTENDED_CAR_MOVEMENT / Unintended
car movement detection; SALSIS goes to emergency mode
hex10/dec16: POWER_SUPERV3_3V_OVER_ERR / Overvoltage
supervision 3.3V failed ; SALSIS goes to emergency mode
hex11/dec17: POWER_SUPERV3_3V_UNDER_ERR / Undervoltage
supervision 3.3V failed; SALSIS goes to emergency mode
hex12/dec18: POWER_SUPERV2V_OVER_ERR / ; Over-voltage
supervission 2V failed; SALSIS goes to emergency mode
hex13/dec19: POWER_SUPERV2V_UNDER_ERR / Undervoltage
supervision 2V failed; SALSIS goes to emergency mode
hex14/dec20: POWER_SUPERV12V_OVER_ERR / Overvoltage
hex15/dec21: POWER_SUPERV12V_UNDER_ERR / Undervoltage
hex16/dec22: POWER_SUPERV24V_OVER_ERR / Overvoltage
hex17/dec23: POWER_SUPERV24V_UNDER_ERR / Power supply
undervoltage supervision 24V failed; SALSIS goes to emergency mode
hex18/dec24: NORMAL_REL_SUPPLY_ERR / Power supply
supervision of Relay Supply failed; SALSIS goes to emergency mode
hex19/dec25: WD_TEST_ERR / Watchdog test failed; SALSIS goes to
emergency mode
hex1A/dec26: FLOORS_ERASED_NB_FLOORS_NOT_FIT / Number
of floors/stops does not fit other channel; floors/stop values are erased
hex1B/dec27: FLOORS_ERASED_FLOOR_POS_NOT_FIT / Floor
position does not fit other channel; floors/stop values are erased
hex1C/dec28: not used
hex1D/dec29: FLOORS_ERASED_STRANGE_PLACE / Power up at
strange place (start-up more than 5m past end floor); floors/stop values
are erased
hex1E/dec30: ERR_DUMMY5 / ERR_DUMMY5
hex1F/dec31: ETSL_EXISTANCE_UNDEF /
ETSL_EXISTANCE_UNDEFINED
hex20/dec32: CONTRADICTION_ETSL_DETECTION1 / Contradiction
ETSL Detection 1
ETSL Detection 2
ETSL Detection 3
ETSL Detection 4
ETSL Detection 5
ETSL Detection 6
hex26/dec38: AB_CONTRADICTION_ETSL_DETECTION / Other
channel wants to close ETSL although this channel says there is no
ETSL
hex27/dec39: UET_EXISTANCE_UNDEF /Errors due to detection of
UET relay
hex28/dec40: CONTRADICTION_UET_DETECTION1 / Contradiction
UET Detection 1
hex29/dec41: CONTRADICTION_UET_DETECTION2 / Contradiction
UET Detection 2
hex2A/dec42: CONTRADICTION_UET_DETECTION3 / Contradiction
UET Detection 3
hex2B/dec43: CONTRADICTION_UET_DETECTION4 / Contradiction
UET Detection 4
hex2C/dec44: AB_CONTRADICTION_UET_DETECTION / Other
channel wants to close UET althogh this channel says there is no UET
hex2D/dec45: RELAY_PATTERN_UNDEF / Undefined relay-Pattern
hex2E/dec46: ERR_DUMMY17 / ERR_DUMMY17
hex2F/dec47: ERR_DUMMY18 / ERR_DUMMY18
hex30/dec48: ERR_DUMMY19 / ERR_DUMMY19
hex31/dec49: ERR_DUMMY20 / ERR_DUMMY20
hex32/dec50: EEPROM_WRITE_ERROR / Error while writing
EEPROM
hex33/dec51: EEPROM_READ_ERROR / Error while reading
EEPROM
hex34/dec52: EEPROM_CHECKSUM_ERROR / Error, CRC-
checksum does not fit
hex35/dec53: HIGH_BYTE_OF_FLOOR_INFO_NZ / Error due to
plausibility check floor information from EEPROM
hex36/dec54: EMERGENCY_DUE_TO_OTHER_CHANNEL /
Emergency state forced by other channel
hex37/dec55: SOFTWARE_VERSION / Software version does not fit
the other channel

Source ID

Causes and
1 Refer to diagnostics TK of Refer to diagnostics TK of
Actions
MOSIS or SALSIS MOSIS or SALSIS
1516 No Target Lower KSE Slowdown
This section describes the Travel Control Ext error No Target Lower
Summary KSE Slowdown.
While decelerating the car enters the lower KSE zone (KSE-D active)
Description and no target (stop) is set in Travel Control logic.
Extra Info

Source ID
1517 No Target Upper KSE Slowdown
This section describes the Travel Control Ext error No Target Upper
Summary KSE Slowdown.
While decelerating the car enters the upper KSE zone (KSE-U active)
Description and no target (stop) is set in Travel Control logic.
Extra Info

Source ID
1518 JNH active
This section describes the Travel Control Ext error JNH active.
Summary
Input JNH active; no trips are possible

Description
not used
Extra Info

Source ID
1519 Bypass Plug Conflict
This section describes the Travel Control Ext error Bypass Plug
Summary Conflict.
The software detects that the bypass plugs/switches are in a state

Description where trips are not allowed (interlock in software to prevent trips with
bypasses door contacts).
not used
Extra Info

Source ID
1520 Door Bypass Recall
This section describes the Travel Control Ext error Door Bypass
Summary Recall.
The software detects that the bypass plugs/switches are in a state

Description where trips are not allowed in inspection operation (applicable for HK
COP)
not used
Extra Info

Source ID
1521 SI Teach-in Mode
This section describes the Travel Control Ext error SI Teach-in Mode.
Summary
Preparation for learn trip aborted because SALSIS is in teach-in mode.

Description
not used
Extra Info

Source ID
1522 SI ETSL device fault
This section describes the Travel Control Ext error SI ETSL device
Summary fault.

Description related to the ETSL function of MoSIS. The extra info describes the
message sent by MoSis together with the status change of floor
sensor.
The extra information value is a 8 digit hexadecimal number

Extra Info (0xABCDEFGH)
A=0: ETSL relay closed (normal)

A=1: ETSL relay open (reason for opening see other digits)
B=_: RESERVED FOR FUTURE USE
C=1: NTSD overspeed. (Normal Terminal Stopping Device)
D=1: MoSis internal hardware or software error relating to the ETSL.
Check the error-log (MoSis) for further info.
E=1: Relay test failure (EtslRelayFail)
F=1: Commissioned speed exceeded (MaxSpeed).
G=1: Pre-commissioned limit of 1m/s exceeded (1mps)
H=1: Exceeded ETS/ETSL curve towards terminal (Curve)
Source ID

Causes and
1 An internal circuit or relay of Reset the MoSIS/SALSIS
Actions
a severe malfunction.e the error occurs again, replace
the MoSIS/SALSIS device..
1523 SI KNE device fault
This section describes the Travel Control Ext error SI KNE device fault.
Summary

Description related to the KNE function of MoSIS.
The extra information value is a 8 digit hexadecimal number

Extra Info (0xABCDEFGH)
A=0: KNE relay closed (normal)

A=1: KNE relay open (reason for opening see other digits)
B=_: RESERVED FOR FUTURE USE
C=1: KNE open because of detection of unintended car movement
D=1: MoSis internal hardware or software error relating to the KNE.
Check the error-log (MoSis) for further info.
E=1: Relay test failure (KneRelayFail)
F=1: Car travelled past the end of the known shaft range
(StrangePlace). MoSis was never at this position before (past the last
floor).
G=1: Travel past last known floor (Overtravel)
H=1: Pre-commissioned state; no floors discovered (Precom)
Source ID

Causes and
1 An internal circuit or relay of Reset the MoSIS/SALSIS
Actions
a severe malfunction. the error occurs again, replace
the MoSIS/SALSIS device..
1524 CAN Sync Send
This section describes the Travel Control Ext error CAN Sync Send.
Summary
Error in the CAN layer when attempting to send the SYNC message.
Description

not used

Source ID
1525 CAN Controller
This section describes the Travel Control Ext error CAN Controller.
Summary
tbd
Description

Extra Info meaning per digit: ABCDEFGH: not used

Source ID
1526 ZSB Fault
This section describes the Travel Control Ext error ZSB Fault.
Summary
Error on brake control (MX control). The software monitors the status
Description of the input KZSB (feedback signal of the relay ZSB on the brake
module). The ZSB timer reduces the brake voltage/current after the
brake has openend (opening voltage/holding voltage). The error
indicates that the status of the input KZSB is not as expected during a
trip.

Extra Info meaning per digit (ABCDEFGH). Decoding of the value:
The extra info value indicates the status of the input

H: Status of the input of the KZSB contact
00000001: KZSB on
00000000: KZSB off

Source ID
1527 KTS Bridged
This section describes the Travel Control Ext error KTS Bridged.
Summary
The error is reported in case the software detects a bridged KTS

Description contact in the safety circuit.
The monitor checks the open state of the KTS contact when the door
is fully opened and when the door starts closing.
none
Extra Info

Source ID
1528 KTC Bridged
This section describes the Travel Control Ext error KTC Bridged.
Summary
The error is reported in case the software detects a bridged KTC

Description contact in the safety circuit.
The monitor checks the open state of the KTC contact when the door
is fully opened and when the door starts closing.
none
Extra Info

Source ID
1529 RCAM Fault
This section describes the Travel Control Ext error RCAM Fault.
Summary
The software detects a failure of the operation of the retiring cam

Description RCAM. Activation or release of the RCAM failed.
Only used for NA control sytems.

Extra Info meaning per digit(0xWWXXYYZZ). Decoding of the value:
WW: not used.
XX: side for which the RCAM and KCAM are in implausible states.
YY: KCAM state for that side
ZZ: RCAM state for that side.

Source ID

Causes and
1 Faulty relay RCAM Check operation of relay;
Actions
replace if necessary
1530 RTC Fault
This section describes the Travel Control Ext error RTC Fault.
Summary
The relay RTCx or 2RTCx did not operate as expected.

Description
On older software version the error 95 'Door Lock Fault' was logged in
this situation.

SKEUAP:
ABCDEF: not used
G: Status of feedback contact on relay RTC1 (RTC1CON)
H: Status of feedback contact on relay RTC (RTCCON)
SKNA:
ABCDEF: not used
G: Status of feedback contact on relay 2RTC (CDOORCONT20)
H: Status of feedback contact on relay RTC (CDOORCONT)

Source ID

Causes and
1 Problem with relay RTC/RTC1 Replace pcb
Actions
1531 RTS Fault
This section describes the Travel Control Ext error RTS Fault.
Summary
The relay RTSx or 2RTSx (shaft door lock relay) did not operate as
Description expected. This error is logged in these cases:
1. The controller periodically monitors the status of door lock relay

coil/contacts for both sides when the lift is standstill.
Trigger condition for TX2 EUAP system (SKEAP): The status of
RTSCON does not match with the status of RTS1CON.
Trigger condition for TX2 NA system (SKNA): The status of shaft door
coil input and contact input are not matching.
2. During preparation of a trip at a point when it is confirmed that the
doors are closed, the status of door relay coils / contacts for both sides
are monitored.
Trigger condition for TX2 EUAP system: The status of RTSCON and
RTS1CON inputs, for the respective side, do not match.
Trigger condition for TX2 NA system: The status of shaft door coil and
contact for any side, do not match.
Remark: On older software version the error 95 'Door Lock Fault' was
logged in this situation.

Extra Info meaning per digit (STUVWXYZ). Decoding of the value:
for pcb SKEAP:

STUV: not used
W: Status of feedback contact on relay 2RTS1 (2RTS1CON)
X: Status of feedback contact on relay 2RTS (2RTSCON)
Y: Status of feedback contact on relay RTS1 (RTS1CON)
Z: Status of feedback contact on relay RTS (RTSCON)
for pcb SKNA:
STUVWX: not used
Y: Status of feedback contact on relay 2RTS (SDOORCONT20)
Z: Status of feedback contact on relay RTS (SDOORCONT)

Source ID

Causes and
1 Problem with relay RTS/RTS1 replace pcb
Actions
or 2RTS/2RTS1
1532 KTS Fault
This section describes the Travel Control Ext error KTS Fault.
Summary
The error is reported in case the software detects that the KTS contact
Description in the safety circuit does not close as expected. The monitor checks
the closed state of the KTS contact when the door received a door lock
command. In case of unsuccessful check, the control performs a
number of lock - unlock cycles to recover the contact problem.
none
Extra Info

Source ID
1533 KTC Fault
This section describes the Travel Control Ext error KTC Fault.
Summary
The error is reported in case the software detects that the KTC contact
Description in the safety circuit does not close as expecgted.
The monitor checks the closed state of the KTC contact when the door
received a door lock command.
In case of unsuccessful check, the control performs a number of lock -
unlock cycles to recover the contact problem.
none
Extra Info

Source ID
1534 Door State Fault
This section describes the Travel Control Ext error Door State Fault.
Summary
Description


Source ID
1535 KTS/KTC Bridged
This section describes the Travel Control Ext error KTS/KTC Bridged.
Summary
The error is reported in case the software detects a bridged KTS or

Description KTC contact in the safety circuit.
The monitor checks the open state of the KTS and KTC contacts when
the door is fully opened and when the door starts closing.
Note: This error is reported in case the control system can not
determine whether KTS or KTC is bridged.
none
Extra Info

Source ID
1536 Invalid SI Flash
This section describes the Travel Control Ext error Invalid SI Flash.
Summary
This error is reported when shaft image data is invalid for both RAM
Description and FLASH
Checksum data for the shaft image

Extra Info

Source ID
1537 SI Commission Number not Matching
This section describes the Travel Control Ext error SI Commission

Summary Number not Matching.
This error is reported if the commission number stored in the SALSIS

Description device is different than the commission number of the elevator control.
This is a indication of mismatch of the shaft image in the SALSIS
device and the shaft image of the elevator control. The commission
numbers are compared every time the SALSIS device is connected to
the elevator control. If a mismatch is detected, the shaft images in the
SALSIS device and in the elevator control are cleared and no normal
operation is possible.
Commission number stored in the SALSIS device. In case of 0xFFFF a

Extra Info new, virgin SALSIS device is detected.

Source ID

Causes and
1 Replacement of SALSIS with a New teaching of SALSIS
Actions
used SALSIS device of device and new learn trip of
another elevator elevator control required
2 Initial installation of a new,
virgin SALSIS device
3 Teaching of SALSIS device
and learn trip of elevator
control required
1538 SI Mismatch of Number of Stops
This section describes the Travel Control Ext error SI Mismatch of

Summary Number of Stops.
This error is reported in case the number of Stops in the elevator

Description control configuration and the number of Stops teached to the SALSIS
device are not the same. If the check has failed, the shaft image of the
elevator control is cleared and no normal operation is possible.
Number of Stops teached to the SALSIS device

Extra Info

Source ID

Causes and
1 Teaching of SALSIS device Repeat teaching of SALSIS
Actions
was not done properly to top or device over the full hoistway
bottom terminal floor lenght
2 Missing floor magnet (actuator)
at a landing
3 check and adjust or repair the
floor magnet and then repeat
the teaching of the SALSIS
device over the full hoistway
lenght
1539 CLC Zero Load Calibration Frequency
Failed
This section describes the Travel Control Ext error CLC Zero Load
Summary Calibration Frequency Failed.
This error is reported in case the frequency signal of the CLC sensor is
Description out of the tolerance range at the zero load calibration point. In this case
the load measurement device is not commissioned.
01 (hex) : Sensor 1 has failed

Extra Info 02 (hex) : sensor 2 has failed
03 (hex) : Sensor 1 and 2 have failed

Source ID

Causes and
1 Mechanical tension to CLC Mechanical fitting and
Actions
sensor too high at zero load adjustment of screws has to be
condition done according installation
manual
2 CLC sensor defect and signal
is outside tolerance
3 Replace CLC sensor
1540 CLC Reference Load Calibration
Frequency Failed
This section describes the Travel Control Ext error CLC Reference
Summary Load Calibration Frequency Failed.
This error is reported in case the frequency signal of the CLC sensor is
Description out of the tolerance range at the reference load calibration point. The
slope of the load measurement is evaluated. In case the slope is
outside the tolerance, the reference calibration is invalid. In this case
the load measurement device is uncommissioned.
01 (hex) : Sensor 1 has failed

Extra Info 02 (hex) : sensor 2 has failed
03 (hex) : Sensor 1 and 2 have failed

Source ID

Causes and
1 Mismatch of reference load in repeat reference load
Actions
car and reference load value calibration with correct
entered in SMLCD reference load and value in
SMLCD
2 CLC sensor is defect and the
slope of the weight curve is
outside tolerance
3 Replace CLC sensor and
repeat zero and reference car
load calibration procedure
1541 CLC Continuous Adjustment Not
Successful
This section describes the Travel Control Ext error CLC Continuous
Summary Adjustment Not Successful.
This error is reported in case the automatic, continous zero load

Description calibration of the car load cell (CLC) has detected the possibility of an
left object in the car (e.g. trolley, box, etc.).
The limit for the failure condition is >= the minimal load value (defined
by a parameter) compared to the current zero load reference value.
The continous zero load calibration is made at every floor when the
elevator is in idle status. In case the failure is detected, the zero load
reference value is not changed at this floor.
The error message is just reported in case the problem remained for 5
days. The error is afterwards reported every 5th day, until the problem
recovers.
The elevator remains in operation.
Remark: See error 1572 for detection of a sensor signal drift failure.
none
Extra Info

Source ID

Causes and
1 Sensor drift is too high replace the sensors and
Actions
commission the CLC load
device again.
2 Object in the car during Observe the continuous LMS
measurement deviation during several days.
In case the continuous LMS
deviation adjustment is not
successful, perform LMS learn
traavel and check LMS
hoistway analysis image or
calibrate the load sensor again.
1542 CLC No Signal from Sensor
This section describes the Travel Control Ext error CLC No Signal from
Summary Sensor.
This error is reported in case the CLC sensor does not give a
Description frequency signal to the load measurement device which determines the
car load.
01 (hex) : Sensor 1 has no signal

Extra Info 02 (hex) : sensor 2 has no signal
03 (hex) : Sensor 1 and 2 have no signal

Source ID
1543 CLC Invalid Signal from Sensor
This section describes the Travel Control Ext error CLC Invalid Signal
Summary from Sensor.
This error is reported in case the CLC sensor gives a invalid frequency
Description signal to the load measurement device which determines the car load.
The invalid signal is due to a signal which is out of the tolerance limit of
the sensor specification.
01 (hex) : Sensor 1 has invalid signal, out of maximum frequency

Extra Info 02 (hex) : sensor 2 has invalid signal, out of maximum frequency
11 (hex) : Sensor 1 has invalid signal, out of miminum frequency
12 (hex) : sensor 2 has invalid signal, out of minimum frequency
03 (hex) : sensor 1 and 2 have both invalid signal, out of maximum
frequency
13 (hex) : sensor 1 and 2 have both invalid signal, out of minimum
frequency
23 (hex) : Sensor 1 has invalid signal, out of maximum frequency and
sensor 2 has invalid signal, out of minimum frequency
33 (hex) : Sensor 1 has invalid signal, out of miminum frequency and
sensor 2 has invalid signal, out of maximum frequency
43 (hex) : Signals are inside range, but the difference of the signals of
Sensor 1 and 2 is too big.
Definition of extra info 43:

The chekc of the difference is done only if one of the sensors has a
signal with a load above 20% of the reference load value. The check
has failed if the difference of the 2 sensor load values is higher than
50% of the load value of the sensor with the higher value.

Source ID
1544 UET Bridged
This section describes the Travel Control Ext error UET Bridged.
Summary
Door bridging circuit UET found bridged permanently. The bridging

Description circuit of the door contacts KTC and KTS must not be bridged when
the control disables the bypass device (PHSIS, MOSIS, SALSIS). For
the check the software uses the state of the safety circuit taps (refer
also to schematics).
Exception: the monitoring is not enabled when hoistway access or a
bypass switch is active.

not used

Source ID

Causes and
1 check if the door closed
Actions
contacts are manually bridged
1545 SB ON standstill
This section describes the Travel Control Ext error SB ON standstill.

Summary
The control detects that the brake contactor is active (ON) in standstill.
Description The feedback contact indicates open contactor while the related output
to activate the brake (SB) is inactive.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Value 'G': SB contact state
Value 'H': SB1 contact state

Source ID
1546 SB not ON start
This section describes the Travel Control Ext error SB not ON start.
Summary
The control detects that the brake contactor does pick (ON) during trip
Description start as expected. The feedback contact of SB/SB1 does not switch
when starting a trip.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used

Source ID
1547 SB OFF Run
This section describes the Travel Control Ext error SB OFF Run.
Summary
The control detects that a brake contactor closed (OFF) during a trip.
Description The feedback contact is inactive during a trip indicating that the
respective contactor is not on.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used

Source ID
1548 SB not OFF stop
This section describes the Travel Control Ext error SB not OFF stop.
Summary
The control detects that the brake contactor (SB/SB1) does not close
Description (closed = OFF) at the end of a trip as expected. An auxiliary contact
does not switch when finishing a trip as expected indicating that the
respective contactor did not drop after deactivation of the related
ouput. The error may also indicate a faulty output.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used

Source ID
1549 RB ON standstill
This section describes the Travel Control Ext error RB ON standstill.

Summary
The control detects that the brake relay contact is active (ON) in
Description standstill.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Value 'G': not used
Value 'H': RB contact state

Source ID
1550 RB not ON start
This section describes the Travel Control Ext error RB not ON start.
Summary
The control detects that the brake relais contact does not pick (ON)
Description during trip start as expected. The feedback contact of RB does not
switch when starting a trip.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Value 'G': not used

Source ID
1551 RB OFF Run
This section describes the Travel Control Ext error RB OFF Run.
Summary
The control detects that a brake relais contact closed (OFF) during a
Description trip. The feedback contact is inactive during a trip indicating that the
RB contact is not on.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Value 'G': not used

Source ID
1552 RB not OFF stop
This section describes the Travel Control Ext error RB not OFF stop.
Summary
The control detects that the brake relais contact RB does not close
Description (closed = OFF) at the end of a trip as expected. The auxiliary contact
does not switch when finishing a trip as expected indicating that the
relay did not drop after deactivation of the related output. The error
may also indicate a faulty output.

Extra Info meaning:
Value 'A': not used

Value 'B': not used
Value 'C': not used
Value 'D': not used
Value 'E': not used
Value 'F': not used
Value 'G': not used

Source ID
1553 Load Measurement Functions Disabled
This section describes the Travel Control Ext error Load Measurement
Summary Functions Disabled.
The load measurement functions (overload protection, load value for

Description car occupation, load value for drive pre-torque) are disabled. The
disable command was entered at the service interface and the disable
state is active for 2 hours.
none
Extra Info

Source ID
1554 Load Measurement Functions Enabled
This section describes the Travel Control Ext error Load Measurement
Summary Functions Enabled.
The load measurement functions (overload protection, load value for

Description car occupation, load value for drive pre-torque) are enabled. The
disable timer (2 hours) has elapsed or a load measurement enable
command was entered at the service interface.
0 : Enabled by service technician with command in service interface

Extra Info 1 : Enabled by elapsed time

Source ID
1555 MBB Open Timeout Current
This section describes the Travel Control Ext error MBB Open Timeout
Summary Current.
The brake does not open after applying the set voltage to the brake
Description circuit.
After the brake_open command is given to the brake module the
brakes are not opened within the maximum time. The maximum time is
defined by the PCT parameter 'KB_time'. Its min value is 1sec and
max value is 2.3 sec.
Possible reason: Insufficent current in brake circuit when reference
value for current in brake circuit applied by control.
For MBBG2 this error is for channel 1.
8 digit hex number: 0xaabbccdd where

Extra Info aa: internal_brake_state (state machine)
bb: brake_state
cc: current reference applied to brake module (hex value)
dd: voltage reference applied to brake module (hex value)
Values for 'internal_brake_state':

00: MBB_CLOSED / Brake is closed
01(hex01): MBB_GO_PREPARING / Start preparing brake
02(hex02): MBB_PREPARING / Brake is preparing to open
03(hex03): MBB_GO_OPENING / Start opening
04(hex04): MBB_OPENING_WITH_PROBLEM / Open with IGBT
check
05(hex05): MBB_OPENING / Brake is opening
06(hex06): MBB_OPENING_AFTER_KB / Wait high voltage after KB
07(hex07): MBB_OPEN / Brake is open
08(hex08): MBB_GO_CLOSING_SLOW / Start closing slow
09(hex09): MBB_CLOSING_SLOW / Brake is closing slow
10(hex0A): MBB_GO_CLOSING_FAST / Start closing fast
11(hex0B): MBB_CLOSING_FAST / Brake is closing fast
12(hex0C): MBB_WAIT_AFTER_KB / Wait for state closed after KB
13(hex0D): MBB_WAIT_ZERO_VOLT / Wait for zero voltage on ADC
14(hex0E): MBB_GO_REFRESHING / Do IGBT3 test with a Refresh
15(hex0F): MBB_REFRESHING / Check the result of the test
16(hex10): MBB_REFRESH / Refresh is complete
Values for 'brake_state' (bb):

00: BRAKE INIT
01: NO PARAMETERS / Brake parameters missing
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID

Causes and
1 Wrong parameter values Check parameter values of the
Actions
brake parameters: opening
voltage, holding voltage, AD
resolution for brake voltage
measurement (-> Parameter -
> Brake)
1556 MBB Close Timeout Current
This section describes the Travel Control Ext error MBB Close Timeout
Summary Current.
The brake does not close after removing the voltage to the brake
After the brake_close command is given to the brake module the
brakes are not closed within the maximum time. The maximum time is
defined by the PCT paramater 'KB_time'. Its min value is 1sec and
Current in brake circuit not zero when reference value for current in
brake circuit is set to zero.

bb: brake_state
cc: current reference applied to brake module
dd: voltage reference applied to brake module

check
10(hex0A): MBB_REFRESH / Refresh is complete

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID
This section describes the Travel Control Ext error MBB IGBT3 Fault.
Summary
The test of the power electronics (IGBT3) on MBBx board failed. This
Description IGBT3 test is triggered by the control software with every trip
preparation before opening the brake(s).
Testing: the error can be reprocued by disconnecting the plug on the

230VAC connector on the MBBx board.

bb: brake_state

check

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID

Causes and
1 Open brake circuit or faulty Check the electrical circuit from
Actions
brake module the cabinet to the brake(s)
or replace brake module
2 No AC supply voltage for Check the AC supply voltage
brake module MBBx for the brake module and the
crelated circuits.
1558 MBB Hardware Fault
This section describes the Travel Control Ext error MBB Hardware
Summary Fault.
Harware problem MBBx board

Description

bb: brake_state

check
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID
1559 MBB Current Difference
This section describes the Travel Control Ext error MBB Current
Summary Difference.
Maximum difference between the reference brake current and actual

Description current exceeded. The reference values for brake opening and holding
currents are defined by PCT parameters. The software checks he
difference between 'current ref' applied and the value of actual current
received from brake module. The maximum difference is: 'current_ref' /
3 where the value of current_ref is either opening_current or holding
current depending on the brake_state.

bb: brake_state

check

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID
1560 MBB Mains Not Off
This section describes the Travel Control Ext error MBB Mains Not Off.
Summary
AC power to MBB not turned off after deactivation of the brake. The
Description software expects the mains supply voltage to be turned off after the
brake has closed (standstill). The AC mains supply for the brake
module is turned off when safety circuit relays (RSK) are off.

bb: brake_state

check
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID

Causes and
1 Incorrect wiring of AC voltage Check wiring of AC supply
Actions
from TB to MBBx voltage to MBBx board
This section describes the Travel Control Ext error MBB IGBT1 Fault.
Summary
Test of power electronics on MBBx (IGBT1) failed. The IGBT1 test is

Description done before opening the brake(s).

bb: brake_state

check
00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID

Causes and
1 Faulty pcb Replace pcb MBBx
Actions
1562 MBB Voltage Difference
This section describes the Travel Control Ext error MBB Voltage
Summary Difference.
Maximum difference between the reference brake voltage and the

Description actual voltage exceeded. Reference values for brake opening and
holding voltages are defined by PCT parameters. For brake modules
MBBx (TX/TX2).
The software checks the difference between the 'voltage ref' applied
and the value of actual voltage received from brake module. The
maximum difference is: 'voltage_ref' / 3' where the value of the
voltage_ref is either opening_voltage or holding_voltage (PCT
parameter) depending on the actual brake_state. For magnetic brakes
the SW regulates the brake current and monitors the output voltage to
the brake coil. For Hydraulic brakes the SW regulates/sets the brake
voltage and monitors the current to the valve.

bb: brake_state

check

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID

Causes and
1 Wrong parameter setting of Check parameter values and
Actions
PCT parameter 'Opening required brake voltage. The
Voltage', 'Holding Voltage' or SW monitors the output
'AD Resolution for voltage voltage to the brake coil.
measuring'
2 Faulty pcb Check measured brake voltage
with CADI; replace pcb if
necessary.
1563 Shaft Door Opened Not Permitted
This section describes the Travel Control Ext error Shaft Door Opened
Summary Not Permitted.
A shaft door other than the one opening at car landing is opened. The
Description controller is blocked persistent. A manual reset is necessary to unblock
the elevator.
none
Extra Info

Source ID
1564 LUET Off at Floor
This section describes the Travel Control Ext error LUET Off at Floor.
Summary
The car stops at a floor and the control detects that the LUET signal is
Description OFF instead of ON . This means that the LUET signal has not the
correct status or is not available.
Without the LUET signal a manual evacuation is not possible.
Therefore the elevator is blocked in case of this failure.
Note: for SALSIS the LUET signal is wired to the control. Therefore the
control can check the availability of the signal at the floor.
None.
Extra Info
None.
Source ID

Causes and
1 The wire from the SALSIS Check wire and plugs. Replace
Actions
device to the control HW is or fix wire or plug.
broken.
2 SALSIS LUET output is defect. Measure LUET output of
SALSIS when car is at floor
level. Replace SALSIS in case
the output is defect.
1565 UET circuit failed
This section describes the Travel Control Ext error UET circuit failed.
Summary
This error is reported in case the elevator control detects that the UET
Description device did not bypass the section of the safety circuit. This check is
made when the elevator control activated the UET device at door-
preopening, releveling and flying start.
In case the elevator control detects this error, it blocks the elevator in
FATAL status.
None.
Extra Info
None.
Source ID

Causes and
1 The electrical connection from Fix the wiring or the plug of this
Actions
the UET device (e.g. SALSIS, circuit.
PHSIS) to the related section
of the safety circuit is broken.
1566 KTS/KTC Fault
This section describes the Travel Control Ext error KTS/KTC Fault.
Summary
The error is reported in case the software detects that the KTC or KTS
Description contact in the safety circuit does not close as expected. The monitor
checks the closed state of the KTC and KTS contact when the door
received a door lock command.
In case of unsuccessful check, the control performs a number of lock -
unlock cycles to recover the contact problem.
Note: This error is reported in case the control system can not
determine whether KTS or KTC is faulty (depending on hardware
design).
none
Extra Info

Source ID
1567 INSP cmd to ACUM Failure
This section describes the Travel Control Ext error INSP cmd to ACUM
Summary Failure.
The monitoring of the inspection speed and the unintended movement

Description is done via the ACUMNA device.
When an inspection trip is started (up/down button pressed) the
controller informs the ACUMNA device that enables the inspection
speed monitoring and disables the unintended movement detection.
The error is reported in the following cases:

A) the software detects a persistent mismatch between the state of the
up/down button on the inspection panel and the state of the inspection
switch:
when the up/down button is pressed for more than a pre-defined time
without the corresponding inspection active the elevator blocks
persistent at next destination.
remark: Short inadmissible activation of up/down button is done by
another monitor (MAINM).
B) The software compares the state of the up/down button with the
feedback of the same from the ACUMNA device:
when the up/down button state on the inspection panel is inconsistent
with up/down button feedback from the ACUMNA the elevator blocks
persistent at next destination.

0(hex) / 0(dec): Inadmissible move command (case A above))

1(hex) / 1(dec) mismatch move command between insp panel and
feedback ACUMNA (case B above)

Source ID
1568 KNE KPG bypass activated
This section describes the Travel Control Ext error KNE KPG bypass
Summary activated.
The switch JOKNEU to allow unlimited travel upwards in top of car

Description inspection is activated and bypassing of the safety contacts KNE-U
and KPG is active. For NA only (TX-R5). This is an info message.
none
Extra Info

Source ID
1570 Car Damping Device Activation Failure
This section describes the Travel Control Ext error Car Damping
Summary Device Activation Failure.
This error is reported in case the activation of the car damping device
Description (CDD) failed. The elevator control commands the activation of the CDD
and after maximum 2 seconds the CDD feedback shall indicate active
state.
This failure can have two reasons:

- Car damping device does not activate (no damping of car)
- Activation / deactivation feedback signal does not switch -> broken
wire condition
When the failure is detected, the elevator is blocked immediately. The

reason for this blocking is the critical case of a broken wire condition of
the feedback signal. For the permanent activation failure detection
(error 1628) the reliability of the feedback signal is essential. (This
behavior is because of the normally open contact of the CDD feedback
signal.)
none
Extra Info

Source ID

Causes and
1 CDD feedback signal has a Check CDD feedback signal
Actions
broken wire. contact and wiring to elevator
control according schematics.
Fix contact or wiring in case
the feedback signal does not
report activation and
deactivation of CDD.
2 CDD feedback signal switch Check switch logic of CDD
has wrong switch logic feedback signal and the
(normally closed instead of connector pin positions
normally open). according schematics.
3 CDD prop does not operate Check wiring to CDD soleonid
because soleonid or activation activation. Check if at CDD
circuit (PCB) is defect. activation the CDD soleonid
has correct voltage.
1571 Car Damping Device Deactivation
Failure
Summary Device Deactivation Failure.
This error is reported in case the deactivation of the car damping

Description device (CDD) fails. The elevator control commands the deactivation of
the CDD and after maximum 2 seconds the CDD feedback shall
indicate inactive state.
The error is reported the first time when it occurs. In case the
malfunction recovers but occurs several times a day, the error is
reported only once a day. In case the malfunction disapears for one
day, the error message is no more reported at this day.
Number of malfunctions (trips and re-levelings) count since the last

Extra Info reported error none

Source ID
1572 CLC Continuous Adjustment Exceeded
This section describes the Travel Control Ext error CLC Continuous
Summary Adjustment Exceeded.
This error is reported in case the automatic, continous zero load

Description calibration of the car load cell (CLC) has detected that the zero load
reference value has changed too much compared to the initial zero
load reference value. This might be caused by an bad sensor, which
has a too big signal deviation.
The limit for the deviation is >= 75kg or 10% of the nominal car load
when the nominal load is higher than 750kg.
The continous zero load calibration is made at every floor when the
elevator is in idle status. In case the failure is detected, the zero load
reference value is not changed at this floor.
The error message is just reported in case the problem remained for 5
days. The error is afterwards reported every 5th day, until the problem
recovers.
The elevator remains in operation.
Remark: See error 1541 for detection of left boxes or goods in the car.
8 digit hexadecimal number (ABCDEFGH)

Extra Info
AB (hex) : Floor position where error occured
CD (hex) : Not used
EFGH (hex) : Actual car load in kg measured at this floor

Source ID
Causes and
1 Guide rail force to car has Adjust mechanically the guide
Actions
changed (more or less force) rail at this floor(s). Perform
LMS learn travel and check
LMS hoistway analysis image
at the service interface.
2 Car / load sensor broken Change load sensor and
calibrate load sensor again
(incl. LMS learn travel for floor
related LMS adjustments).
3 Car / load sensor Check fixation of load sensor
disassembled and calibrate load sensor again
(incl. LMS learn travel for floor
related LMS adjustments).
1573 SI Verification Trip Failed
This section describes the Travel Control Ext error SI Verification Trip
Summary Failed.
This error is reported if at the SALSIS hoistway image learning

Description procedure the verification trip failed.
An error condition is given, when a floor magnet is more than 30 mm
away from the initially teached position in the SALSIS hoistway image.
A floor magnet could be moved away of its teached position or a floor
magnet could be removed at all.
When the control detects the moved (or the next floor magnet), the
elevator stops the verification trip with a ramp down stop.

Extra Info meaning per digit: ABCDEFGH
AB : Floor position number where the expected floor magnet was

moved or removed
C : 1 = detected magnet above expected position, 0 = detected magnet

below expected position
DEFGH : Distance of expected position and detected floor magnet

position (in mm)

Source ID

Causes and
1 Error distance in extra info is Move the floor magnet back to
Actions
small. A floor magnet is moved the original teached position
avay of its teached position. (distance see in extra info).
Repeat learning procedure with
verification trip.
2 Error distance in extra info is
large (about the floor distance).
A floor magnet was removed.
3 Place the missing floor magnet
at its original teached position.
Repeat the learning procedure
with the verification trip. If at
this new trial the error distance
is small, then repeat the action
1.
1574 Safety Circuit Bridged
This section describes the Travel Control Ext error Safety Circuit
Summary Bridged.
The safety circuit is found bridged permanently.

Description If the safety circuit tab T4 is off and the tabs T5 and T6 are on, a
bridging of the safety circuit is detected. The bridging can only be
detected, if the bridging contains the section of the door safety
contacts.
none
Extra Info

Source ID
1575 Brake Emergency Stop Warning Limit
Exceeded
This section describes the Travel Control Ext error Brake Emergency
Summary Stop Warning Limit Exceeded.
The monitoring of the brake emergency stop counter reports that the
Description elevator has reached the number of emergency stops as defiened for
the warning limit of the machine brake type. The warning limit is
defined in the order data (e.g. chip card).
The elevator remains available for normal operation.
A periodic check of the machine brake air gap is from now on required.
The machine brake has 2 units. The extra info indicates which machine
Extra Info brake unit has reached the brake emergency stop warning limit.
Note: The machine brake units can be replaced separately and
therefore each machine brake unit has its own counter value.
0x10 : Brake 1 hass exceeded the limit

0x02 : Brake 2 has exceeded the limit
0x12 : Brake 1 and brake 2 have exceeded the limit
ndef
Source ID
1576 Brake Emergency Stop Blocking Limit
Exceeded
Summary Stop Blocking Limit Exceeded.
The monitoring of the brake emergency stop counter reports that the
Description elevator has reached the number of emergency stops as defiened for
the blocking limit of the machine brake type. The warning limit is
defined in the order data (e.g. chip card).
The elevator is blocked for normal passenger operation.
Extra Info brake unit has reached the brake emergency stop blocking limit.
Note: The machine brake units can be replaced separately and
therefore each machine brake unit has its own counter value.
0x10 : Brake 1 hass exceeded the limit

0x02 : Brake 2 has exceeded the limit
0x12 : Brake 1 and brake 2 have exceeded the limit
ndef
Source ID
1577 Brake Emergency Stop Data - virgin
stor detected
Summary Stop Data - virgin stor detected.
A mismatch between the brake serial number keys is detected and one
Description storage is virgin. The controller copies the brake emergency stop data
from the non virgin storage to the virgin one.
Extra Info Details: 8 digit hex number (AABBCCDD)

Extra Info AA: ID of the brake (01 or 02)
BB: Not used
CC: not used
DD: 01: Copy data of master to backup
02: Copy data from backup to master
note: Backup is for example chip card
not used
Source ID
1578 Brake Emergency Stop Data - Storage
Mismatch
Summary Stop Data - Storage Mismatch.
A mismatch between the brake keys (serial numbers) is detected and

Description none of the storages is virgin. The elevator is blocked until the service
technician enters the brake key (serial number). The controller restores
the brake emergency stop data from the storage matching the brake
key to the other one.
Extra Info brake unit has mismatched data.
0x01 : Brake 1
0x02 : Brake 2
not used
Source ID
1579 Brake Emergency Stop - New Block
Limit Calculated
Summary Stop - New Block Limit Calculated.
A new brake emergency stop parameter value (warning limit or

Description blocking offset) in the order data (e.g. chip card) was detected and a
re-calculation of the "brake emergency stop blocking limit" was
performed by the elevator control.
The re-calculated "brake emergency stop blocking limit" is the initial
value derived from the "brake emergency stop warning limit" and the
"brake emergency stop blocking offset" of the order data.
Note: In case the re-calculated "brake emergency stop blocking limit" is

lower than the curent "brake emergency stop" counter value, the
elevator will block the passenger operation with automatic trips. In this
case the "machine brake air gap" value has to be measured and
entered in the elevator control service interface. With a valid "machine
air gap" value the "brake emergency stop blocking limit" can be
extended and the elevator can resume its operation.
The machine brake has 2 units. The extra info indicates the original
Extra Info "brake emergency stop blocking limit" of each unit before the re-
calculation.
0xABCD: Former limit of brake unit 1

0xEFGH: Former limit of brake unit 2
not used
Source ID
1580 Brake Emergency Stop - Undefined
Data
Summary Stop - Undefined Data.
The brake emergency stop counter brake keys (serial number) are not
Description defined in any storage. The elevator is blocked for normal passenger
operation until the fitter enters the machine brake key (serial number).
Extra Info brake unit has undefiend data.
0x01 : Brake 1
0x02 : Brake 2
not used
Source ID
1581 Brake Emergency Stop Data Store
recover Success
Summary Stop Data Store recover Success.
The brake emergency stop data storage mismatch is successfully

Description restored.
The extra info has the format 0xABCD:

Extra Info
A is the brake unit
01 : Brake 1
02 : Brake 2
B and C are not used
D is data transfer direction
1 (hex/dec) data restored from master to backup

2 (hex/dec) data restored from backup to master
3 (hex/dec) master and backup data merged
not used
Source ID
1582 Brake Emergency Stop Data Storage
Not Recover
Summary Stop Data Storage Not Recover.
The recovery of the brake emergency stop data storage mismatch was
Description not successful. The machine brake key (serial number) entered does
not match any existing ones.
Extra Info brake unit has not successful data recovery.
0x01 : Brake 1
0x02 : Brake 2
not used
Source ID
1583 Brake Emergency Stop Key Entered -
Initialized
Summary Stop Key Entered - Initialized.
This is an information that the brake emergency stop key (serial

Description number) has been entered and that the brake emergency stop counter
monitoring is now active.
The machine brake has 2 units. The extra info indicates for which
Extra Info machine brake the brake-key (serial number) was entered.
0x01 : Brake 1
0x02 : Brake 2
not used
Source ID
1584 Brake Emergency Stop Counter Values
Entered
Summary Stop Counter Values Entered.
This is an information that the brake emergency stop counter monitor

Description has been manually set with a new brake emergency stop count value.
The machine brake has 2 units. The extra info indicates for which
Extra Info machine brake unit the value was entered.
The format of the extra info is 0xABCD:
A is the brake unit

0x01 : Brake 1
0x02 : Brake 2
B is not used
CD is the entered emergency stop count value in hex
not used
Source ID
1585 Brake Emergency Stop - Air Gap Value
Exceeded
Summary Stop - Air Gap Value Exceeded.
This error is reported when the "machine brake air gap" which was
Description measured and entered to the elevator control by the service technician
is too big. The entered value is compared with the "machine brake
maximum air gap" limit, as set in the order data.
When the measured value exeeds the limit, the elevator is blocked for
normal passenger operation.
which machine brake unit has exceeded the "machine brake maximum
Extra Info air gap" limit.
The format of the extra info is ABCD:
A is brake 1 or 2
01 : Brake 1 has exceeded the limit
02 : Hbrake 2 has exceeded the limit
B not used
C is enterd air gap value in hex
D is max. air gap limit in hex (configured limit)
not used
Source ID
1586 Brake Emergency Stop - Air Gap
Entered
Summary Stop - Air Gap Entered.
This message is reported when the service technician has entered the
Description "machine brake air gap" which was measured at the machine brake.
The entered value is compared with the "machine brake maximum air
gap" limit, as set in the order data.
When the measured value is below this limit, the "brake emergency
stop blocking limit" is extended from the current brake emergency stop"
counter value plus the "brake emergency stop blocking offset".
which machine brake unit has exceeded the "machine brake maximum
Extra Info air gap" limit.
The format of the extra info is ABCD:
A is brake 1 or 2
01 : Brake 1 has exceeded the limit
02 : Hbrake 2 has exceeded the limit
B not used
C is enterd air gap value in hex (in micro meter)
D is not used
not used
Source ID
1587 Safety Circuit Overvoltage at Relay
Summary Overvoltage at Relay.
Safety circuit voltage at the relays (RSK/RSK1/RTS/RTC..) is too high.

Description In the event of a HW failure (e.g. malfunction of the voltage regulation)
the safety circuit power supply is switched off if the voltage at the
relays is too high. The monitored voltage level is 28 VDC. Applies for
control systems with regulated safety circuit voltage (e.g.: pcb SKS on
TX2).
The voltage at the relays (RSK/RSK1/RTS/RTC) is measured at the
coil and compared against the reference value. If the voltage limit is
exceeded the control will turn off the safety circuit voltage supply. No
information is available regarding the safety circuit channel where the
overvoltage was detected. The reset button DUEISK-A must be
pressed to restore the power for the safety circuit.
the software.
Format: 8 digit value YYZZZZZZ where:

Extra Info
YY: not used
ZZZZZZ: Car position (decimal value in mm) when the error occurred.
not used
Source ID
1588 Safety Circuit Undervoltage Output
Summary Undervoltage Output.
Safety circuit supply voltage is too low. In the event of a HW failure

Description (e.g. malfunction of the voltage regulation) the safety circuit power
supply is switched off if the supply voltage for the safety circuit is too
low. The monitored voltage level is 19 VDC. Applies for control
systems with regulated safety circuit voltage (pcb SKS on TX2).
The supply voltage for the safety circuit is measured and compared
against the reference value. If the voltage is too low compared to the
limit the control will turn off the safety circuit voltage supply. No
undervoltage was detected. The reset button DUEISK-A must be
the software.

Extra Info
YY: not used
not used
Source ID
1589 Safety Circuit Overvoltage Output
Summary Overvoltage Output.
Safety circuit supply voltage is too high. In the event of a HW failure

Description (e.g. malfunction of the voltage regulation) the safety circuit power
supply is switched off if the supply voltage for the safety circuit is too
high. The monitored voltage level is 60 VDC. Applies for control
systems with regulated safety circuit voltage (pcb SKS on TX2).
The supply voltage for the safety circuit is measured and compared
against the reference value. If the voltage is too high compared to the
limit the control will turn off the safety circuit voltage supply. No
undervoltage was detected. The reset button DUEISK-A must be

Extra Info
YY: not used
not used
Source ID
1590 Safety Circuit Overcurrent
Summary Overcurrent.
Safety circuit current is too high. In the event of a HW failure (e.g.

Description ground fault in the safety circuit) the safety circuit power supply is
switched off if the current in the safety circuit is too high. The current
limit is 300mA. Applies for control systems with regulated safety circuit
voltage (pcb SKS on TX2). The nominal current in the safety circuits is
defined by the coil resistance of the relays and the additional resistors
(TX2: 100mA). The current in the safety circuit is measured and
compared against the reference value. If the current is too high
compared to the limit the control will turn off the safety circuit voltage
supply. No information is available regarding the safety circuit channel
where the undervoltage was detected. The reset button DUEISK-A
must be pressed to restore the power for the safety circuit.
the software.

Extra Info
YY: not used
not used
Source ID
1591 Stop Override Relay 1
This section describes the Travel Control Ext error Stop Override
Summary Relay 1.
For A17.1 code (US and Canada) it is required that during Fire Recall
Description (JBF) the in car stop switch is not active. The control therefore includes
a relay RUEHC1 which jumps out the in car stop switch (COP) in the
safety circuit while the car is being recalled to the lobby. Travel Control
will report STOP_OVERRIDE1_FAULT if it detects the relay go on
(input: KUEHC1) when the car is not on fire recall service.
Comments: Not used.
Format: 8 digit value AABBBBBB where:

Extra Info
AA: not used
BBBBBB: Car position (decimal value in mm) when the error occurred.
not used
Source ID
1592 SI Hoistway Image Upload Failed
This section describes the Travel Control Ext error SI Hoistway Image
Summary Upload Failed.
This information is reported if at the hoistway image learning procedure

Description the upload of the hoistway image data from SALSIS failed.
none
Extra Info

Source ID
1593 Hoistway Access Guard Fault
This section describes the Travel Control Ext error Hoistway Access
Summary Guard Fault.
Applies for NA only.

Description
The monitoring of the relay used for hardware protection under
hoistway access operation indicates a problem on the hardware. The
error is reported when the “hoistway access hardware protection relay”
is not in the expected state during hoistway access operation. The
monitoring of the relay is only possible once the access enable switch
has been turned ON.
Monitoring of the relay:

Access enable switch is active and atleast one of the following inputs is
ON:
top access up or top access down or bottom access up or bottom
access down. Then the relay must be ON; if not then the relay has
failed to open. Error in log indicates relay failure, extra information
indicates the relay has failed open. Other INS and Normal operation
allowed after the error. SRM call must be made to inform Schindler
about the hw failure.
Access enable switch is active and none of the following inputs are
ON:
top access up/down, bottom access up/down. Then the relay (input)
must be OFF, if not OFF (ON) then the relay has failed to close. Error
in log indicates relay failure, extra information indicates the relay has
failed closed. Control does not allow hoistway access operation. Other
INS and Normal operation allowed after the error. SRM call must be
made to inform Schindler about the hw failure.
The monitoring is only enabled when if the input is configured.

0x00000000: Access hardware protection relay failed to be activated.
Extra Info 0x00000001: Access hardware protection relay failed to be
deactivated.

Source ID
1594 SI Communication OK

Summary OK.
The control detects that the communication to the CAN based shaft
Description info system (MoSIS / SALSIS) is reestablished. The control constantly
monitors the position messages recevied over the CAN bus. The
message is typically logged when the CAN bus reconnected (e.g. plug
of CAN bus cable plugged in). See also error 1512 SI Communication
Lost.
Extra Info

Source ID
1595 SI Communication Dead

Summary Dead.
The control detects that the communication to the CAN based shaft
Description info system (MoSIS / SALSIS) is dead. No communication to shaft info
system after communication lost for more than 30s. The software logs
the error in standstill and puts the control into FATAL status
(breakdown).
none
Extra Info

Source ID

Causes and
1 Bus cable not connected Check bus cable connections
Actions
in AS (MR) and OKR (Car)
1596 Overspeed KSE-U
This section describes the Travel Control Ext error Overspeed KSE-U.
Summary
Overspeed detected while car is inside the upper KSE zone.

Description
8 digit hex number: xAABBCCDD

Extra Info
AA: index number
01 Logged from 'monitor drive'. The monitoring is enabled for all trips
except manual trips when the lift is in KSE_TOP region.
02 Logged from 'Learn trip'. Applicable only for MX(no physical KSE
switch). Learn trip aborted because learn speed (V_LEARN) to high.
Trip curve does not allow to stop the car normally within a distance
equal to: FIN_LENGTH / 2 at the start of the trip.
BBCCDD: Actual Velocity in mm/sec in decimal

Source ID

Causes and
1 Incorrect KSE input signal Check KSE parameters (KSE
Actions
Distance). Repeat the learn
trip.
2 Wrong placement of KSE-U Check position of magnet
magnet
3 Faulty KSE switch Replace switch
4 Faulty input on IO interface Replace interface board
board (ASILOGx, ASIXx, etc)
1597 Overspeed KSE-D
This section describes the Travel Control Ext error Overspeed KSE-D.
Summary
Overspeed detected while car is inside the lower KSE zone.

Description
8 digit hex number: xAABBCCDD

Extra Info
AA: index number
01 Logged from 'monitor drive'. The monitoring is enabled for all trips
except manual trips when the lift is in KSE_BOTTOM region.
02 Logged from 'Learn trip'. Applicable only for MX(no physical KSE
switch). Learn trip aborted because learn speed (V_LEARN) to high.
Trip curve does not allow to stop the car normally within a distance
equal to: FIN_LENGTH / 2 at the start of the trip.
BBCCDD: Actual Velocity in mm/sec in decimal

Source ID

Causes and
1 Incorrect KSE input signal Check KSE parameters (KSE
Actions
Distance). Repeat the learn
trip.
2 Wrong placement of KSE-D Check position of the magnet
magnet
3 Faulty KSE switch Replace switch
4 Faulty input on IO interface Replace interface board
board (ASILOGx, ASIXx, etc)
1598 SI UET Command Lost
This section describes the Travel Control Ext error SI UET Command
Summary Lost.
This error is reported if the command to overbridge the door safety

Description contacts to the SI device (SALSIS(MoSis) is lost.
The control has send the overbridging command 3 times and no
acknowledge was received for these commands.
.
none
Extra Info

Source ID

Causes and
1 The communication to the SI Check proper connection and
Actions
device is connected, but the grounding of communication
telegrams are not successfully links to SI device
transmitted due to EMC (SALSIS(MoSis).
problems.
1599 Traction Loss
This section describes the Travel Control Ext error Traction Loss.
Summary
This error is reported when travel control detects loss of traction during
Description a trip. Travel control checks if the car no longer moves (no travel
distance from position tacho) while the inverter runs. Implemented for
NA code compliance A17.
Comment: underspeed monitoring is insufficient to detect a stalled car
none
Extra Info

Source ID
1600 JREC Switch Fault
This section describes the Travel Control Ext error JREC Switch Fault.
Summary
This error is reported when travel control detects conflicting states of

Description input signals JREC and JRECCK. For systems where 2 inputs are
forseen for a normally open and a normally closed contact of the switch
extra info format 0x0000aabb where:

Extra Info aa = Status of JREC switch
bb = Status of JRECCK input.

Source ID

Causes and
1 Faulty switch JREC Replace switch or panel
Actions
2 Wiring between switch and Correct wiring
interface board wrong or
broken
3 Input circuit on interface pcb Replace pcb
not working
1601 JRECC Switch Fault
This section describes the Travel Control Ext error JRECC Switch
Summary Fault.

Description input signals JRECC and JRECCCK. For systems where 2 inputs are
forseen for a normally open and a normally closed contact of the switch

Extra Info aa = Status of JRECC switch
bb = Status of JRECCCK input.

Source ID
1602 JRH Switch Fault
This section describes the Travel Control Ext error JRH Switch Fault.
Summary

Description input signals JRH and JRHCK. For systems where 2 inputs are forseen
for a normally open and a normally closed contact of the switch JRH
(Machine Room Inspection switch ).

Extra Info aa = Status of JRH input
bb = Status of JRHCK input

Source ID
1603 JACCEN Switch Fault
This section describes the Travel Control Ext error JACCEN Switch
Summary Fault.

Description input signals JACCEN and JACCENCK. For systems where 2 inputs
are forseen for a normally open and a normally closed contact of the
switch JACCEN (Hoistway Access Enable Switch).

Extra Info aa = Status of JACCEN input
bb = Status of JACCENCK input

Source ID
1604 JUEKTS Switch Fault
This section describes the Travel Control Ext error JUEKTS Switch
Summary Fault.

Description input signals JUEKTS and JUEKTSCK. For systems where 2 inputs
switch JUEKTS (KTS Bypass Switch).
extra info 0xaabbccdd :

Extra Info aa = status of ISKT3
bb = status of ISKT4
cc = Status of JUEKTS input
dd = Status of JUEKTSCK input

Source ID
1605 JUEKTC Switch Fault
This section describes the Travel Control Ext error JUEKTC Switch
Summary Fault.

Description input signals JUEKTC and JUEKTCCK. For systems where 2 inputs
switch JUEKTC (KTC Bypass Switch).
extra info 0xaabbccdd :

Extra Info aa = status of ISKT3
bb = status of ISKT4
cc = Status of JUEKTC input
dd = Status of JUEKTCCK input

Source ID
1606 MBB Current Difference Channel2
This section describes the Travel Control Ext error MBB Current
Summary Difference Channel2.
Maximum difference between the reference brake current and actual

Description current exceeded. The reference values for brake opening and holding
currents are defined by PCT parameters. The software checks he
difference between 'current ref' applied and the value of actual current
received from brake module. The maximum difference is: 'current_ref' /
3 where the value of current_ref is either opening_current or holding
current depending on the brake_state.

bb: brake_state

check

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID
1607 MBB Open Timeout Current Channel2
This section describes the Travel Control Ext error MBB Open Timeout
Summary Current Channel2.
The brake does not open after applying the set voltage to the brake
After the brake_open command is given to the brake module the
brakes are not opened within the maximum time. The maximum time is
defined by the PCT parameter 'KB_time'. Its min value is 1sec and
Possible reason: Insufficent current in brake circuit when reference
value for current in brake circuit applied by control.

bb: brake_state
cc: current reference applied to brake module (hex value)
dd: voltage reference applied to brake module (hex value)

check

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID
1608 MBB Close Timeout Current Chanel2
This section describes the Travel Control Ext error MBB Close Timeout
Summary Current Chanel2.
The brake does not close after removing the voltage to the brake
After the brake_close command is given to the brake module the
brakes are not closed within the maximum time. The maximum time is
defined by the PCT paramater 'KB_time'. Its min value is 1sec and
Current in brake circuit not zero when reference value for current in
brake circuit is set to zero.

bb: brake_state

check

00: BRAKE INIT
02: BRAKE CLOSED
03: BRAKE OPEN
04: BRAKE OPENING
05: BRAKE CLOSING

Source ID
1609 SI Configuration Mismatch
This section describes the Travel Control Ext error SI Configuration

Summary Mismatch.
The software detects mismatch for the number of learnt floors/stops

Description between SI and control. Occurs typically after replacing SI device
(MOSIS/SALSIS) or after exchange of the main controller board
(GCIOB) with incorrect configuration. The software makes the
comparison of the values during startup.
8 digit hex number: 0xSTUVWXYZ where:

Extra Info
Z=1: the total number of floors/stops on MOSIS/SALSIS does not
match the total floors on the control side.
Y=1: the position value of the lowest floor/stop learnt by
MOSIS/SALSIS is away from the lowest floor position on the control
side by more than 7mm.
X=1: the position value of the highest floor/stop learnt by
MOSIS/SALSIS is away from the highest floor position on the control
side by more than 7mm
Meaning of value 00000000 of the extra info:

The controller requests the values for
- total number of floors
- first floor position
- last floor position
from MOSIS/SALSIS but MOSIS/SALSIS does not reply within 2
seconds to the requests.
Rem: on previous SW release the message #127 was used for this
monitoring.

Source ID
Causes and
1 MOSIS exchanged Perform learn trip
Actions
2 Modified configuration Perform learn trip
(different number of stops)
3 Wrong configuration Correct configuration (PCT)
1610 Improve Flight Time Disabled
This section describes the Travel Control Ext error Improve Flight Time
Summary Disabled.
The software detects that "Impove Flight Time" feature is disabled.

Description
8 digit hex number: 0xABCDEFGH where:

Extra Info
H = 1, when door_zone not above 100mm
G = 1, when early brake is not set
F = 1, pre-indice not 0
E = 1, MOSIS software not up-to-date [earlier than release 4.8]
D = 1, disabled since there were more than 10 errors [related to this
feature] in the last 1000 trips.

Source ID
1611 Improve Flight Time Failed - Open SC
Summary Failed - Open SC.
The software detects that the SC is still open when trip was started
Description with Flight Time Improvement
Extra Info

Source ID
1612 Improve Flight Time Failed - Overtravel
Summary Failed - Overtravel.
The software detects that permited travel limit was exceeded when trip
Description was started with Flight Time Improvement
Extra Info

Source ID
1613 Improve Flight Time Failed - Locking
Withdrawn
Summary Failed - Locking Withdrawn.
The software detects that the locking signal was withdrawn when trip
Description was started with Flight Time Improvement
Extra Info

Source ID
1614 Overspeed Drive
This section describes the Travel Control Ext error Overspeed Drive.
Summary
The error is logged when the software detects that the actual speed of
Description the car [based on V_TACHO feedback from the inverter] exceeds the
maximum limit for a given car speed reference. The tolerance is
calculated as 6.25% of the speed reference value. The minimum speed
difference that will lead to an error is based on the trip type:
1. 0.2m/sec for Normal trips.
2. 0.1m/sec for RELEVEL or when at STANDSTILL.
3. 0.3m/sec for all other trips.
If the difference between the actual speed of the car and the speed
reference (velocity_ref) exceeds this calculated limit the trip is
interrupted with an emergency stop.
0: Overspeed detected with switch JMOF off

Extra Info 1: Overspeed detected with switch JMOF on
Source ID
1615 Underspeed Drive
This section describes the Travel Control Ext error Underspeed Drive.
Summary
Description the car [based on V_TACHO feedback from the inverter] is below a
minimum limit for a given car speed reference. The tolerance is

Source ID
1616 Overspeed Car
This section describes the Travel Control Ext error Overspeed Car.
Summary
Description the car [based on S_TACHO feedback from the inverter] exceeds the
maximum limit for a given car speed reference. The tolerance is

Source ID
1617 Underspeed Car
This section describes the Travel Control Ext error Underspeed Car.
Summary
Description the car [based on V_TACHO feedback from the inverter] is below a
minimum limit for a given car speed reference. The tolerance is

Source ID
1618 Speed Reference Limit Exceeded
This section describes the Travel Control Ext error Speed Reference
Summary Limit Exceeded.
The speed reference (velocitiy_ref) was outside the allowed limits

Description (min/max). If the value of the calculated speed reference (velocitiy
reference) exceeds the predefined limits (min/max) for the speed
reference the trip is interrupted with an emergency stop. The maximum
limit for the velocity reference applies to the car speed in the direction
the car shall travel. The values for the minimum limits apply when the
car moves in the opposite direction.
The predefined min/max limits are [mm/s]:
max velocity_ref for manual_trips: 630 + 20

min velocitiy_ref for manual trips: -100
max velocity_ref for montage trips: 500 + 15
min velocitiy_ref for montage trips: -100
max velocity_ref for learn trips: v_learn + 30
min velocity_ref for learn trips: -100
max velocity_ref for synch trips: v_synch + 30
min velocity_ref for synch trips: -300
max velocity_ref for normal trips: v_max
min velocity_ref for normal trips: -300
max velocity_ref for relevel trips: 300
min velocity_ref for relevel trips: -300
max velocity_ref for ramp trips: 350
min velocity_ref for ramp trips: -100
Extra Info
Source ID
1619 CLC Blocked Sensor Detected
This section describes the Travel Control Ext error CLC Blocked
Summary Sensor Detected.
This error is reported in case at a 2 sensor CLC device one of the

Description sensors does not change its measurement value after 3 trips. This is
an indication that the faulty sensor has a signal within the valid
frequency limits, but does not change the frequency when the other
sensor detects a load in the car.
01 (hex) : Sensor 1 does not change signal

Extra Info 02 (hex) : Sensor 2 does not change signal

Source ID
1620 SI PHNRU wrongly IN fin
This section describes the Travel Control Ext error SI PHNRU wrongly
Summary IN fin.
The photocell PHNR-U (PHS on some schematics) is IN-FIN at a

Description position it should be OUT-FIN.
This condition is supervised at the following times:

- when other photocell PHNRD enters the fin in the UP direction
(typically 185mm below the floor) arriving at the destination
- When the other photocell PHNRD leaves the fin in the DOWN
direction (Typically 185mm below the floor) at the start of a trip
- when other photocell PHNRD leaves the fin during releveling
See also error 1626 "PHNR-U Stuck"
If possible, the lift attempts to stop accurately at the floor without an

emergency stop (to avoid entrapment) using the one functioning
photocell. If the error is repeated, the lift is blocked.
R&D use only

Extra Info
R&D use only

Source ID

Causes and
1 The wire to PHNR-U (PHS) is Check wiring
Actions
broken.
2 The photocell PHNR-U doesn't Check wiring
have power
3 Damaged opto-isolator or input Check
circuit on control print ASILOGxx/ASIXxxx/GCIOxxx
boards
1621 SI PHNRU wrongly OUT fin
This section describes the Travel Control Ext error SI PHNRU wrongly
Summary OUT fin.
The photocell PHNR-U (PHS on some schematics) is OUT-FIN at a

Description position it should be IN-FIN.

- when other photocell PHNR-D enters the fin in the DOWN direction
(typically 15mm above the floor) arriving at the destination
- when other photocell PHNR-D leaves the fin during releveling
- At standstill at the end of a normal trip
See also error 1626 "PHNR-U Stuck"

R&D use only

Extra Info
R&D use only

Source ID

Causes and
Actions
shorted.
2 The photocell PHNR-U is not Check mechanical alignment of
aligned with the floor fin floor fin and SiV unit
boards
1622 SI PHNRD wrongly IN fin
This section describes the Travel Control Ext error SI PHNRD wrongly
Summary IN fin.
The photocell PHNR-D is IN-FIN at a position it should be OUT-FIN.

Description
- when other photocell PHNR-U enters the fin in the DOWN direction
(typically 185mm above the floor) arriving at the destination
- When the other photocell PHNR-D leaves the fin in the UPdirection
(Typically 185mm above the floor) at the start of a trip
- when other photocell PHNR-U leaves the fin during releveling
See also error 1627 "PHNR-D Stuck"

R&D use only

Extra Info
R&D use only

Source ID

Causes and
1 The wire to PHNR-d is broken. Check wiring
Actions
2 The photocell PHNR-D doesn't Check wiring
have power
boards
1623 SI PHNRD wrongly OUT fin
This section describes the Travel Control Ext error SI PHNRD wrongly
Summary OUT fin.
The photocell PHNR-D is OUT-FIN at a position it should be IN-FIN.

Description
- when other photocell PHNR-U enters the fin in the UP direction
(typically 15mm below the floor) arriving at the destination
- when other photocell PHNR-D leaves the fin during releveling
- At standstill at the end of a normal trip
See also error 1627 "PHNR-D Stuck"

R&D use only

Extra Info
R&D use only

Source ID

Causes and
1 The wire to PHNR-d is shorted. Check wiring
Actions
2 The photocell PHNR-D is not Check mechanical alignment of
aligned with the floor fin floor fin and SiV unit
boards
1624 SI PHNRU tolerance
This section describes the Travel Control Ext error SI PHNRU

Summary tolerance.
The photocell PHNR-U (PHS on some schematics) switches at a

Description position too far away (more than one fin-length, typially 200mm) from
its expected position.
This condition is supervised when PHNR-U goes 'OUT_FIN' at the

target floor during releveling or normal travel.
This error results in a synchronization travel.
This event was previously reported as '20 POSITION_LOSS' but with

ambiguous extra info.
R&D use only

Extra Info
R&D use only

Source ID
1625 SI PHNRD tolerance
This section describes the Travel Control Ext error SI PHNRD

Summary tolerance.
The photocell PHNR-D switches at a position too far away (more than
Description one fin-length, typially 200mm) from its expected position.
This condition is supervised when PHNR-D goes 'OUT_FIN' at the

target floor during releveling or normal travel.
This error results in a synchronization travel.
This event was previously reported as '20 POSITION_LOSS' but with

R&D use only

Extra Info
R&D use only

Source ID
1626 SI PHNRU stuck
This section describes the Travel Control Ext error SI PHNRU stuck.
Summary
The photocell PHNR-U (PHS on some schematics) doesn't switch at

Description all during normal travel.
During a normal trip, the number of transitions on this input is counted.

This condition is supervised at the end of the trip. If the input never
changes, this error is reported.
See also errors 1620,1621 "PHNRU wrongly IN,OUT fin" to help

identify the state of the stuck signal.
This event was previously reported as '64 PHS_BOUNCE' but with

R&D use only

Extra Info
R&D use only

Source ID

Causes and
Actions
broken or shorted.
boards
1627 SI PHNRD stuck
This section describes the Travel Control Ext error SI PHNRD stuck.
Summary
The photocell PHNR-D doesn't switch at all during normal travel

Description
See also errors 1622,1623 "PHNRD wrongly IN,OUT fin" to help

This event was previously reported as '65 PHNRD_BOUNCE' but with

R&D use only

Extra Info
R&D use only

Source ID

Causes and
1 The wire to PHNR-d is broken Check wiring
Actions
or shorted.
boards
1628 Car Damping Device Permanent
Activated
Summary Device Permanent Activated.
This error is reported in case the deactivation of the car damping

Description device (CDD) failed because the CDD is detected to be mechanically
or electrically permanent active (feedback contact reports activated
CDD).
The rule to detect a CDD permanent activation failure is as follows: In

case a CDD deactivation failure (1571) is detected, the CDD feedback
contact state is checked at the end of the next trip to a floor. In case
the CDD is not recovered at the end of this trip, this is rated as a CDD
permanent activation failure.
When the CDD permanent activation failure is detected, the elevator is

set to permanent fatal error state.
none
Extra Info

Source ID

Causes and
1 The hardware circuit of the Disconnect CDD from
Actions
CDD activation output is defect activation output signal. In
and causes the permanent case CDD remains in active
activation of the CDD. position, the CDD device is
defect. Otherwise the
electronics output circuit is
defect or the relay which
activates the CDD is defect.
1629 FC_Start_Failed
This section describes the Travel Control Ext error FC_Start_Failed.

Summary
Trip preparation aborted due to a negative acknowledge message from

Description inverter in response to a START command from the Control. Software
name of error message: FC_Start_Failed.
None.
Extra Info
Note:
A request has been placed to the drives' team to extend the protocol to
also transmit the reason why the START was acknowledged negatively
[one of the reasons could be an open safety circuit was detected at the
drives side]. This will be added when available.02(hex02):

Source ID
1630 FC_Preparation_Failed
This section describes the Travel Control Ext error

Summary FC_Preparation_Failed.
There is negative acknowledgement from the drive; to a

Description PREPARE_START command from the Control. The negative response
is as enlisted in the extra info.
1: 'Preparation False' message received from inverter in phase

Extra Info 'WAIT_CONTACTORS'
2: 'Preparation Wrong Trip Type' message received from inverter in
phase 'WAIT_CONTACTORS'
3: 'Preparation False' message received from inverter in phase
'ASK_FC_STATUS'
4: 'Preparation Wrong Trip Type' message received from inverter in
phase 'ASK_FC_STATUS'

Source ID
1631 Extensive Zero Speed Trip for Inverter
This section describes the Travel Control Ext error Extensive Zero
Summary Speed Trip for Inverter.
The elevator control keeps the car at position with 0 m/s speed trip for
Description more than 30 seconds. This can happen after a total breakdown of the
motor brake when a safety parking is required (error 138) and when
the door can not be closed due to an obstruction. The car is then kept
at the current position with the appropriate torque applied to the motor.
This warning indicates to the service organization that the drive inverter
IGBT has to be replaced due to a possible damage at the extensive 0
m/s trip.
none
Extra Info

Source ID

Causes and
1 The elevator has performed a The IGBT components of the
Actions
safety parking trip because of drive inverter has to be
a fatal breakdown of the motor replaced as a preventive
brake. The drive had to hold maintenance action. Ohterwise
the car at floor level for a long the IGBT may fail unexpected
time with 0 m/s speed because after this incident.
the door could not be closed
due to an obstacle or another
blockage. A 0 m/s speed for a
long time might cause partial
damage of drive inverter
components.
1632 SI PHNR fault
This section describes the Travel Control Ext error SI PHNR fault.
Summary
The photocells PHNRx doesn't switch at all during travel

Description
See also errors 1622,1623 "PHNRD wrongly IN,OUT fin" to help

R&D use only

Extra Info
R&D use only

Source ID
1633 SI Maximum Speed Exceeded
This section describes the Travel Control Ext error SI Maximum Speed
Summary Exceeded.
This error is logged, when the MoSIS / SALSIS has detected that the
Description speed has exceeded the maximum speed limit of the device.
SALSIS: Maximum speed is 11 m/s
MoSIS: maximum speed is 16 m/s
This error should never occur. Other monitors shall trip before such an
error is detected.
none
Extra Info
Source ID

Causes and
1 A internal malfunction in the Carefully analyze the overall
Actions
MoSIS/SALSIS device lead to system behavior before
a wrong speed measurement. exchange of the
MoSIS/SALSIS device.
1634 SI Maximum Teaching Speed Exceeded
This section describes the Travel Control Ext error SI Maximum

Summary Teaching Speed Exceeded.
This error is logged, when the MoSIS / SALSIS has detected that in
Description teaching / pre commissioned mode the speed has exceeded the
maximum teaching speed limit of 1 m/s.
none
Extra Info
Source ID

Causes and
1 MoSIS/SALSIS device is in pre Check and correct parameters
Actions
commissioning / teaching of traction diameter or speed
mode and the car is moving parameters related to manual
with higher speed as allowed. trips (e.g. top-of-car
inspection) or learn trip.
1635 SI Outside Learned Shaft
This section describes the Travel Control Ext error SI Outside Learned
Summary Shaft.
This error is logged, when the MoSIS / SALSIS has detected an

Description unknown position in normal device operation.
In this case the MoSIS/SALSIS device ereases its shaft image

information. A new teaching or learning of the device is required.
none
Extra Info
Source ID

Causes and
1 A MoSIS/SALSIS with same Execute the procedure to teach
Actions
commission number, but / learn the shaft image.
invalid shaft image was put to
the elevator.
1636 Sync Trip Aborted
This section describes the Travel Control Ext error Sync Trip Aborted.
Summary
This error is logged, when a sync trip is requried but is aborted or not
Description started.
The elevator shall travel to the nearest landing and open the door to
release passengers.
none
Extra Info
Source ID
1637 RSK ON standstill
This section describes the Travel Control Ext error RSK ON standstill.
Summary
The control detects that the safety chain relay contact is active (ON) in
Description standstill.
RSK or RSK1
Extra Info

Source ID
1638 RSK not ON start
This section describes the Travel Control Ext error RSK not ON start.
Summary
The control detects that the safety chain relay contact does not pick
Description (ON) during trip start as expected. The feedback contact of RSK does
not switch when starting a trip.
RSK or RSK1
Extra Info

Source ID
1639 RSK OFF Run
This section describes the Travel Control Ext error RSK OFF Run.
Summary
The control detects that a safety chain relay contact opened(OFF)

Description during a trip. The feedback contact is inactive during a trip indicating
that the RSK contact is not on.
RSK or RSK1
Extra Info

Source ID
1640 RSK not OFF stop
This section describes the Travel Control Ext error RSK not OFF stop.
Summary
The control detects that the safety chain relay contact does not open
Description (= OFF) at the end of a trip as expected. The auxiliary contact does not
switch when finishing a trip as expected indicating that the relay did not
drop after deactivation of the related output. The error may also
indicate a faulty output.
RSK or RSK1
Extra Info

Source ID
1641 SI Validation Failed
This section describes the Travel Control Ext error SI Validation Failed.
Summary
This error is logged, when the control was unable to complete the
Description validation of MoSIS / SALSIS.
This error does not indicate a missmatch in the configuration data.
none
Extra Info
Source ID
1999 MAX_EVENTS_EXT
This section describes the Travel Control Ext error

Summary MAX_EVENTS_EXT.
tbd
Description
Extra Info
Source ID
2001 2001
This section describes the 2000_2099_Load_Measurement error 2001.

Summary
tbd
Description
Extra Info
Source ID
2002 2002
This section describes the 2000_2099_Load_Measurement error 2002.

Summary
tbd
Description
Extra Info
Source ID
2100 No Error
This section describes the 2100_2299_MOSIS error No Error.

Summary
not used
Description
None.
Extra Info
n/a
Source ID
2101 Software Position
This section describes the 2100_2299_MOSIS error Software Position.

Summary
Position error detected by filter in MOSIS software.

Description This error is thrown if a position is read more than 1m away from last
position. This issue can be caused by tape or sensor faults.
Tape related error causes are position dependent. The error will
always occur on nearly the same position in the shaft. Further they can
be speed related. Mostly an error is detected with inspection speed,
but not with full speed.
Sensor related causes are independend from position. Mostly the error
occurs after a view millimeters of movement.
If this error occurs three times within 100 measures the emergency
state is taking place. A typical follow-up error is the 2106 (Position not
fit).
None.
Extra Info
n/a
Source ID

Causes and
1 misaligned Tape check and align tape
Actions
2 To huge gap between sensor adjust sensor
and tape
3 damaged sensor hardware replace MoSIS
4 MUCH ferromagnetic dirt (steel clean tape
swarfs and dust) on the tape
5 ferromagnetic parts like clean tape
washers on the tape
2103 Internal Floor Error
This section describes the 2100_2299_MOSIS error Internal Floor

Summary Error.
Internal floor error. Error detected either when:

Description
1. Error detected concerning the redundant storage of highest and
lowest floor; the floor RAMs is erased immediately.
2. Failed comparison between the RAM contents of channel A and B
The KNE will open immediately but the RAM is only erased if the
problem occurs more than 5 times to avoid false RAM erasing caused
by undetected communication errors.
None.
Extra Info
n/a
Source ID

Causes and
1 new software installed start learning trip
Actions
(at some releases the RAM (during learning trip the Erase-
format changes) ALL command is sent, which
triggers a formating of the
RAM)
2 disturned communication (e.g. check wiring, especially the
EMC) floorsensor grounding
3 hardware fail replace MoSIS
2104 Floors Erased Command
This section describes the 2100_2299_MOSIS error Floors Erased

Summary Command.
Floor positions erased because of a command from the control.

Description
None.
Extra Info
n/a
Source ID

Causes and
1 Erase-ALL command was sent -
Actions
via CAN.
(happens during
commisioning)
2105 RAM Channel AB Exchange
This section describes the 2100_2299_MOSIS error RAM Channel AB

Summary Exchange.
Communication error during exchange of floor-RAM-contents (UART0)

Description
None.
Extra Info
n/a
Source ID

Causes and
1 one channel dead (e.g. power- reset MoSIS
Actions
dip)
2 hardware failure replace MoSIS
3 communication disturbance check grounding of wiring,
MoSIS and the floor sensors
2106 Position AB not fit
This section describes the 2100_2299_MOSIS error Position AB not fit.

Summary
Values for car position on channel A and B are not within a distance of
Description 1m.
This error is mostly the counterpart to error 2101. One channel has the
error 2101 and the other has the error 2106.
So the causes are mostly the same.
None.
Extra Info
n/a
Source ID

Causes and
1 misaligned tape check and align tape
Actions
2 to huge gap between sensor adjust sensor
and tape
3 damaged sensor hardware replace MoSIS
4 MUCH ferromagnetic dirt (steel clean tape
swarfs or dust) on the tape
5 ferromagnetic parts like clean tape
washers on the tape
2107 Position Channel AB Exchange
This section describes the 2100_2299_MOSIS error Position Channel

Summary AB Exchange.
Communication error during exchange of possition (UART1)

Description
None.
Extra Info
n/a
Source ID

Causes and
1 one channel dead (e.g. power- reset
Actions
dip)
2 hardware failure replace MoSIS
3 communication disturbance check grounding of wiring,
(e.g. EMC) MoSIS and floor sensors
2108 floor RAM is erased
This section describes the 2100_2299_MOSIS error floor RAM is

Summary erased.
The floor RAM is erased in case of the corresponding CAN-command,

Description a strange power-up place (>20m away from known shaft) or to much
communication errors.
All these causes have there own error codes.
Additional there is only the request of one channel to delete the shaft
data.
None.
Extra Info
n/a
Source ID

Causes and
1 error 2104 refer to error 2104
Actions
6 hardware fail replace MoSIS
2109 RelayTest - Overbridging Pick
This section describes the 2100_2299_MOSIS error RelayTest -

Summary Overbridging Pick.
Relay-Test-Procedure
Description Overbridging- / Test-Relay failed to pick.
None.
Extra Info
n/a
Source ID

Causes and
1 broken hardware replace MoSIS
Actions
2110 Emergency-State
This section describes the 2100_2299_MOSIS error Emergency-State.

Summary
Device is in emergency- / error-state. refer to the other errors in the log

Description to find root cause.
None.
Extra Info
n/a
Source ID
2111 Strange Position - Floors erased
This section describes the 2100_2299_MOSIS error Strange Position -

Summary Floors erased.
Device is powered more than 20m out of known shaft.

Description This is not possible without swaping hoistways. So a replacement is
suspected an a learning trip is forced.
None.
Extra Info
n/a
Source ID

Causes and
1 power-up more than 20m out learning trip
Actions
of known shaft
2112 Position Warning
This section describes the 2100_2299_MOSIS error Position Warning.

Summary
Position sensor hardware is damaged.

Description This signal is created by the hardware of MoSIS and indicates a
malfunction in the sensor circuit.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2113 Software Version Mismatch
This section describes the 2100_2299_MOSIS error Software Version

Summary Mismatch.
The channels have not the same software version. This can cause
Description various communication errors.
None.
Extra Info
n/a
Source ID

Causes and
1 false software assembling replace MoSIS
Actions
2114 floor detection mismatch
This section describes the 2100_2299_MOSIS error floor detection

Summary mismatch.
The channels run an agreement statemachine to determine that the

Description detected floor is correct or not.
If channel B agrees and channel A not, than there is a communication
fault.
None.
Extra Info
n/a
Source ID

Causes and
1 communication error replace device
Actions
2 steel bracket for floor sensor replace bracket with one made
of aluminium
2115 Unintended Car Movement
This section describes the 2100_2299_MOSIS error Unintended Car

Summary Movement.
Car has moved mor than 100mm, while UET was active.
Description MoSIS assumes, that the doors are open while the UET is active. in
this case MoSIS acts as detection system for UCM and stops the
drive.
None.
Extra Info
n/a
Source ID

Causes and
1 false load measurement check and adjust load
Actions
measurement system
2 wrong drive parameter check and adjust drive
parameter
3 false enabling of UET during analyse start procedure of the
start of trip trip
2116 Speedfilter
This section describes the 2100_2299_MOSIS error Speedfilter.

Summary
The hardware speed filter indicates an error.

Description
None.
Extra Info
n/a
Source ID

Causes and
1 false position information replace MoSIS
Actions
(broken hardware)
2117 Learning Trip failed
This section describes the 2100_2299_MOSIS error Learning Trip

Summary failed.
At start of learning trip, the GC tells MoSIS how many floors should be
Description learned.
At the end of the learning trip a StopLearn command is sent via CAN. If
MoSIS does not have learned the requested amount of floors, it erases
the floor RAM and throws this error.
None.
Extra Info
n/a
Source ID

Causes and
1 abort learning trip by GC check for GC errors
Actions
repeat learning trip
2 floor magnet missed check the existence of all floor
magnets
Hint: The GC shaft image
should contain the learned
floors. This is the easiest way
to find the missing magnet, if
the position of all magnets is
known.
3 broken floor sensor (all replace floor sensor
front/upper or rear/lower stops
are missed)
4 misalignet floor magnet or check and correct positioning
sensor of floor sensor and floor
magnets
2118 ETSL Drop
This section describes the 2100_2299_MOSIS error ETSL Drop.

Summary
ETSL failed to drop/disengage.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
1 high resistance of contact reset MoSIS
2119 KNE Drop
This section describes the 2100_2299_MOSIS error KNE Drop.

Summary
KNE failed to drop/disengage.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
1 high resistant contact reset MoSIS
2120 UET Drop
This section describes the 2100_2299_MOSIS error UET Drop.

Summary
UET failed to drop/disengage.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
3 vibration due bad check guiding and rails
mechanicals
2121 Position Channel AB Communication
This section describes the 2100_2299_MOSIS error Position Channel

Summary AB Communication.
More then three position exchanges out of 100 have failed.

Description
None.
Extra Info
n/a
Source ID

Causes and
1 other channel dead (power- reset MoSIS
Actions
dip)
3 disturbance of communication check grounding of wiring,
(e.g.EMC) MoSIS and floor sensors
2122 Floor RAM Communication
This section describes the 2100_2299_MOSIS error Floor RAM

Summary Communication.
More then three RAM exchanges out of 100 have failed.

Description
None.
Extra Info
n/a
Source ID

Causes and
1 other channel dead (power- reset MoSIS
Actions
dip)
3 disturbance of communication check grounding of wiring,
(e.g. EMC) MoSIS and floor sensors
2123 RelayTest - KNE Pick
This section describes the 2100_2299_MOSIS error RelayTest - KNE

Summary Pick.
Description KNE-Relay failed to pick.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2124 RelayTest - ETSL Pick
This section describes the 2100_2299_MOSIS error RelayTest - ETSL

Summary Pick.
Description ETSL-Relay failed to pick.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2125 RelayTest - Overbridging Drop
This section describes the 2100_2299_MOSIS error RelayTest -

Summary Overbridging Drop.
Description Overbridging- / Test-Relay failed to drop
None.
Extra Info
n/a
Source ID

Causes and
Actions
2126 RelayTest - KNE Drop
This section describes the 2100_2299_MOSIS error RelayTest - KNE

Summary Drop.
Description KNE-Relay failed to drop
None.
Extra Info
n/a
Source ID

Causes and
Actions
2127 RelayTest - ETSL Drop
This section describes the 2100_2299_MOSIS error RelayTest - ETSL

Summary Drop.
Description ETSL-Relay failed to drop
None.
Extra Info
n/a
Source ID

Causes and
Actions
2128 ETSL Pick
This section describes the 2100_2299_MOSIS error ETSL Pick.

Summary
ETSL-Relay failed to pick

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2129 KNE Pick
This section describes the 2100_2299_MOSIS error KNE Pick.

Summary
KNE-Relay failed to pick

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2130 UET Pick
This section describes the 2100_2299_MOSIS error UET Pick.

Summary
UET-Relay failed to pick

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2131 Learn fail - speed
This section describes the 2100_2299_MOSIS error Learn fail - speed.

Summary
The learning trip is aborted due to high velocity.

Description The shaft image is erased.
The learning speed limit is 1m/s
None.
Extra Info
n/a
Source ID

Causes and
1 false travel control settings correct learn speed settings
Actions
drive->parameter->settings
2 false traction sheave diameter adjust traction sheave diameter
setting
2132 Learn fail - time out
This section describes the 2100_2299_MOSIS error Learn fail - time

Summary out.
The learning trip is aborted due to time out.

Description The shaft image is erased.
The maximum learning duration is 30 minutes.
None.
Extra Info
n/a
Source ID

Causes and
1 no confirmation of JLF or repeat learning trip
Actions
"measuring trip"
2 system trip start fail (drive, check GC-logs for start issues
breaks, doors)
3 break down during learning trip fix break down cause and
repeat the learning trip
2133 floor numbers mismatch
This section describes the 2100_2299_MOSIS error floor numbers

Summary mismatch.
The number of floors is exchanged periodically. This error is thrown, if

Description the number does not match between the channels.
None.
Extra Info
n/a
Source ID

Causes and
1 new MoSIS (never commissioning
Actions
commissioned)
2 communication disturbed check grounding of casing and
floorsensors
2134 floor mismatch - lowest
This section describes the 2100_2299_MOSIS error floor mismatch -

Summary lowest.
The lowest floor position does not match between the channels.
Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
commissioned)
floorsensors
2135 floor mismatch - highest

Summary highest.
The highest floor position does not match between the channels.
Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
commissioned)
floorsensors
2136 floor mismatch
This section describes the 2100_2299_MOSIS error floor mismatch.

Summary
A floor position does not match between the channels. The floor RAM
Description is exchanged periodically.
None.
Extra Info
n/a
Source ID

Causes and
Actions
commissioned)
floorsensors
2137 floor mismatch - channel B

Summary channel B.
Channel B does not difference between several floor data, because it

Description just responses to the request of channel A. It throws this error if the
received data, does not match with the own data.
None.
Extra Info
n/a
Source ID

Causes and
Actions
commissioned)
floorsensors
2138 stuck-at of the parallel communication
This section describes the 2100_2299_MOSIS error stuck-at of the

Summary parallel communication.
The relay status is communicatet parallel between the channels to

Description speed up reaction time. These wires are checked ruing startup for
stuck-at.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2148 CAN - Bus OFF
This section describes the 2100_2299_MOSIS error CAN - Bus OFF.

Summary
There are so many error frames on the bus, that the controller needs
Description to be reset.
This error indicates heavy bus communication problems.
None.
Extra Info
n/a
Source ID

Causes and
1 bad wiring check wiring
Actions
> twisted pair
> shield
2 wrong termination make shure that the resistance
of the Bus is 60 Ohm
> one 120 Ohm resistor at
each end of the bus (MoSIS
has one mounted)
> check EBI-CAN switch
settings
3 disturbance of communication - check shield and grounding
> EMC - remove unreleased nodes
> other nodes which send on
the same IDs
2149 CAN - ERROR
This section describes the 2100_2299_MOSIS error CAN - ERROR.

Summary
There is an error at the bus or CAN controller.

Description
None.
Extra Info
n/a
Source ID

Causes and
1 bad wiring check wiring
Actions
> twisted pair
> CAN-GND
> shield
2 no or wrong bus termination make shure that the bus
resistance is approx 60 Ohm
> one 120 Ohm resistor at
each end of the bus (MoSIS
has one mounted)
> check EBI-CAN switch
settings
3 disturbance of communication - check shields and grounding
> EMC - remove unreleased nodes
> other nodes, which are using
the same IDs
2150 CAN - Overrun
This section describes the 2100_2299_MOSIS error CAN - Overrun.

Summary
There are more messages received, than MoSIS can process.

Description In detail this error occurs if a new message overwrites an old one,
before it is removed from the receiving buffer.
This incident can be caused by broken wires. The message buffers of
the senders fills during interception. All these buffers are released,
when the bus is reconnected.
None.
Extra Info
n/a
Source ID

Causes and
1 temporary interception of bus check wiring
Actions
wires
2151 CAN - SYNC-Burst
This section describes the 2100_2299_MOSIS error CAN - SYNC-

Summary Burst.
SYNC-messages are sent faster than a period of 5ms. This is

Description interpreted as a burst. The burst messages are left unresponded.
None.
Extra Info
n/a
Source ID

Causes and
1 temporary interception of check wiring
Actions
wiring
2152 CAN - Node
This section describes the 2100_2299_MOSIS error CAN - Node.

Summary
An unspecified error at the MoSIS CAN controller has taken place.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2164 ETSL (dyn) closed before close
This section describes the 2100_2299_MOSIS error ETSL (dyn) closed

Summary before close.
The ETSL-Relay was closed before the close command was executed.
Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2165 KNE (dyn) closed before close
This section describes the 2100_2299_MOSIS error KNE (dyn) closed

The KNE-Relay was closed before the close command was executed.
Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2166 UET (dyn) closed before close
This section describes the 2100_2299_MOSIS error UET (dyn) closed

The UET-Relay was closed before the close command was executed.
Description
None.
Extra Info
n/a
Source ID

Causes and
1 high resistant contact reset moSIS
Actions
2167 Overbridging (dyn) closed before close
This section describes the 2100_2299_MOSIS error Overbridging

Summary (dyn) closed before close.
The Overbridging-Relay was closed before the close command was

Description executed.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2168 ETSL (dyn) close
This section describes the 2100_2299_MOSIS error ETSL (dyn) close.

Summary
The ETSL-Relay fails to close in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2169 KNE (dyn) close
This section describes the 2100_2299_MOSIS error KNE (dyn) close.

Summary
The KNE-Relay fails to close in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2170 UET (dyn) close
This section describes the 2100_2299_MOSIS error UET (dyn) close.

Summary
The UET-Relay fails to close in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2171 Overbridging (dyn) close

Summary (dyn) close.
The Overbridging-Relay fails to close in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2172 ETSL (dyn) open
This section describes the 2100_2299_MOSIS error ETSL (dyn) open.

Summary
The ETSL-Relay fails to open in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2173 KNE (dyn) open
This section describes the 2100_2299_MOSIS error KNE (dyn) open.

Summary
The KNE-Relay fails to open in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2174 UET (dyn) open
This section describes the 2100_2299_MOSIS error UET (dyn) open.

Summary
The UET-Relay fails to open in time.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2175 Overbridging (dyn) open

Summary (dyn) open.
The Overbridging-Relay fails to open in time.

Description
None.
Extra Info
n/a
Source ID
2176 ETSL (dyn) open before open
This section describes the 2100_2299_MOSIS error ETSL (dyn) open

Summary before open.
The ETSL-Relay is already open before the opening command is

None.
Extra Info
n/a
Source ID

Causes and
Actions
2177 KNE (dyn) open before open
This section describes the 2100_2299_MOSIS error KNE (dyn) open

The KNE-Relay is already open before the opening command is

None.
Extra Info
n/a
Source ID

Causes and
Actions
2178 UET (dyn) open before open
This section describes the 2100_2299_MOSIS error UET (dyn) open

The UET-Relay is already open before the opening command is

None.
Extra Info
n/a
Source ID

Causes and
Actions
2179 Overbridging (dyn) open before open

Summary (dyn) open before open.
The Overbridging-Relay is already open before the opening command

Description is executed.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2180 ETSL (static) open
This section describes the 2100_2299_MOSIS error ETSL (static)

Summary open.
The ETSL-Relay is detected as closed, but it should be open.

Description This static supervision does not cause an error mode.
None.
Extra Info
n/a
Source ID

Causes and
1 vibration - check rollers
Actions
- check guiderails
2181 KNE (static) open
This section describes the 2100_2299_MOSIS error KNE (static) open.

Summary
The KNE-Relay is detected as closed, but it should be open.

None.
Extra Info
n/a
Source ID

Causes and
Actions
- check guide rails
2182 UET (static) open
This section describes the 2100_2299_MOSIS error UET (static) open.

Summary
The UET-Relay is detected as closed, but it should be open.

None.
Extra Info
n/a
Source ID

Causes and
Actions
- check guide rails
2183 Overbridging (static) open

Summary (static) open.
The Overbridging-Relay is detected as closed, but it should be open.

None.
Extra Info
n/a
Source ID

Causes and
Actions
- check guide rails
2184 ETSL (static) close
This section describes the 2100_2299_MOSIS error ETSL (static)

Summary close.
The ETSL-Relay is detected as open, but it should be closed.

None.
Extra Info
n/a
Source ID

Causes and
Actions
- check guide rails
2185 KNE (static) close
This section describes the 2100_2299_MOSIS error KNE (static)

Summary close.
The KNE-Relay is detected as open, but it should be closed.

None.
Extra Info
n/a
Source ID

Causes and
1 vibration -check rollers
Actions
- check guide rails
2186 UET (static) close
This section describes the 2100_2299_MOSIS error UET (static) close.

Summary
The UET-Relay is detected as open, but it should be closed.

None.
Extra Info
n/a
Source ID

Causes and
Actions
- check guide rails
2187 Overbridging (static) close

Summary (static) close.
The Overbridging-Relay is detected as open, but it should be closed.

None.
Extra Info
n/a
Source ID

Causes and
Actions
- check guide rails
2188 ETSL startup
This section describes the 2100_2299_MOSIS error ETSL startup.

Summary
The ETSL-Relay is indicated as closed during startup.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2189 KNE startup
This section describes the 2100_2299_MOSIS error KNE startup.

Summary
The KNE-Relay is indicated as closed during startup.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2190 UET startup
This section describes the 2100_2299_MOSIS error UET startup.

Summary
The UET-Relay is indicated as closed during startup.

Description
None.
Extra Info
n/a
Source ID

Causes and message
Actions
2191 Overbridging startup

Summary startup.
The Overbridging-Relay is indicated as closed during startup.

Description
None.
Extra Info
n/a
Source ID

Causes and
Actions
2192 Relay closing statemachine
This section describes the 2100_2299_MOSIS error Relay closing

Summary statemachine.
The state variable of the closing state machine contains invalid values.
Description This indicates a CPU or memory fail.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2193 Relay opening statemachine
This section describes the 2100_2299_MOSIS error Relay opening

The state variable of the opening state machine contains invalid

Description values. This indicates a CPU or memory fail.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2194 Parameter - false relay request
This section describes the 2100_2299_MOSIS error Parameter - false

Summary relay request.
The request to operate a relay, points to an invalid relay. A CPU or

Description memory fail is suspected.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2195 Relay-Test statemachine
This section describes the 2100_2299_MOSIS error Relay-Test

The state variable of the relay test state machine contains invalid data.
Description A CPU or memory fault is suspected.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2196 Overbridging closed at test start

Summary closed at test start.
The Overbridging-Relay is detected as closed at the start of the relay

Description test. The Overbridging must be open at this time to ensure the
effectivity of the ETSL-Relay.
None.
Extra Info
n/a
Source ID

Causes and
Actions
2300 No Error
This section describes the 2300_2499_SALSIS error No Error.

Summary
not used
Description
None.
Extra Info
n/a
Source ID
2301 ETSL Relay Drop Fail
This section describes the 2300_2499_SALSIS error ETSL Relay Drop

Summary Fail.
ETSL relay failed to drop. SALSIS goes to emergency mode.

Description Either feedback contact does not conduct (oxydized contacts) or the
working contact is stuck in the closed position.
None.
Extra Info
n/a
Source ID
2302 KNE Relay Drop Fail
This section describes the 2300_2499_SALSIS error KNE Relay Drop

Summary Fail.
KNE relay failed to drop. SALSIS goes to emergency mode.

None.
Extra Info
n/a
Source ID
2303 UET Relay Drop Fail
This section describes the 2300_2499_SALSIS error UET Relay Drop

Summary Fail.
UET relay failed to drop. SALSIS goes to emergency mode.

None.
Extra Info
n/a
Source ID
5000 No Error
This section describes the 5000_5099_Remote_Monitoring error No

Summary Error.
Just reservation of ENUM space. Keep on state 'proposal'!

Description
Extra Info
Source ID

Causes and
1 The connection between the Check data connection
Actions
elevator control board and the
remote monitoring data
communication device (e.g.
modem) is faulty
2 Remote monitoring data Replace remote monitoring
communication device (e.g. data communication device
modem) defective
5002 No Physical Data Connection to
Control Center

Summary Physical Data Connection to Control Center.
The data connection from the elevator (remote monitoring data

Description communication device, e.g. modem) to the control center hasn't
physically established or was physically interrupted
EX_MODEM_NOT_IDLE = 1
Extra Info EX_MODEM_PORT_NOT_AVAILABLE = 2
EX_PPP_START_FAILED = 3
EX_PPP_CONNECT_TIMEOUT = 4
EX_PPP_CONNECT_ABORTED = 5
EX_NO_CONNECT_AFTER_RING = 6
EX_NO_IP_RECEIVED = 7
Source ID

Causes and
1 Connection physically Check data connection (e.g.
Actions
interrupted or bad phone line)
2 Data speed negotiation failed Check configuration (e.g.
(e.g. at modem) country code)
3 Authentication failure Check parameterization of
remote monitoring (e.g.
password)
5003 Data Line to Control Center Busy
This section describes the 5000_5099_Remote_Monitoring error Data

Summary Line to Control Center Busy.

physically established because the line was busy
Extra Info
Source ID

Causes and
1 Control center not able to Do nothing. Wait for next
Actions
answer call of elevator (e.g. calling attempt.
too busy)
5004 No Logical Data Connection to Control
Center

Summary Logical Data Connection to Control Center.

logically established or was logically interrupted
EX_UNSECURE_CONNECT_TIMEOUT = 1
Extra Info EX_UNSECURE_CONNECT_ABORT = 2
EX_NO_SSL_CLIENT_CONNECTED = 3
EX_SSL_CONNECT_TIMEOUT = 4
EX_SSL_CONNECT_ABORTED = 5
EX_PPP_ABORTED = 6
EX_SSL_ABORTED = 7
Source ID

Causes and
1 Bad oder wrong configured Check configuration (e.g.
Actions
phone line connection country code)
5005 Max Data Connection Attempts to
Control Center
This section describes the 5000_5099_Remote_Monitoring error Max

Summary Data Connection Attempts to Control Center.
There were several failed attempts (typically 5) from the elevator

Description control to establish the data connection to the control center. No further
attempts are performed within the next 24 hours. See previous logged
errors to get the reason of the problem.
Note, this mechanism prevents to get inadmissible connection costs at

data transmission by phone line.
Extra Info
Source ID
5006 Max Data Connection Time to Control
Center Exceede
This section describes the 5000_5099_Remote_Monitoring error Max

Summary Data Connection Time to Control Center Exceede.
The maximum connection time between the elevator (remote

Description monitoring data communication device, e.g. modem) to the control
center has exceeded. The connection is aborted.
Note, this mechanism prevents to get inadmissible connection costs at

data transmission by phone line.
EX_MAX_IDLE_TIME_EXCEEDED = 1
Extra Info MAX_CONNECT_TIME_EXCEEDED = 2
Source ID

Causes and
1 The max. idle time was Check configuration (e.g.
Actions
reached without sending or Maximum Idle Time RM to
receiving data RMCC)
2 The max. connect time was Check configuration (e.g.
reached Maximum Connect Time RM to
RMCC)
5007 Data Communication Device Dead

Summary Communication Device Dead.
The communication between the elevator control and the remote

Description monitoring data communication device (e.g. modem) has failed
Extra Info
Source ID

Causes and
1 The connection between the Check data connection
Actions
elevator control board and the
remote monitoring data
communication device (e.g.
modem) is faulty
2 Remote monitoring data Replace remote monitoring
communication device (e.g. data communication device
modem) defective
5008 Data Communication Device Alive

Summary Communication Device Alive.
The communication between the elevator control and the remote

Description monitoring data communication device (e.g. modem) has
reestablished.
Extra Info
Source ID
5009 Data Communication Device Faulty

Summary Communication Device Faulty.
The communication line sharing device has detected a failure of its

Description internal electronics.
Note, the telealarm device is still operable, but back-calls from the
control center to the telealarm or telemonitoring device are not possible
anymore.
EX_PROSLIC_FAILURE = 1
Extra Info
Source ID

Causes and
1 Device internal failure Replace the CLSD PCB
Actions
(communication line sharing
device)
8000 Alarm Error Base
This section describes the 8000_8099_Remote_Alarm error Alarm

Summary Error Base.
The alarm device is on the phone line for a alarm call (Device is
Description hooked off).
Extra Info
Source ID
8009 Alarm Device is Off Hook

Summary Device is Off Hook.
The alarm device is on the phone line for a alarm call (Device is
Description hooked off).
Extra Info
Source ID
8010 Alarm Device is On Hook

Summary Device is On Hook.
The alarm device has terminated a alarm call (Device is hooked on).
Description
The extra info shows some additional call information. The 8 digit
Extra Info hexadecimal number
(0xAABBCCDE) has the following meaning: (Hex values)
Value 'AA': The call reason can have the following values:
0x00 = UNKNOWN_CALL_REASON
0x01 = INCOMING_VOICE_CALL_REASON
0x02 = INCOMING_DATA_CALL_REASON
0x03 = PERIODIC_CALL_REASON
0x04 = MONITORING_INPUT_CALL_REASON
0x05 = BATTERY_MONITOR_CALL_REASON
0x06 = ALARM_CALL_REASON
0x07 = TEST_ALARM_CALL_REASON
0x08 = REMOTE_ALARM_CALL_REASON
0x09 = OUTGOING_DATA_CALL_REASON
0x0A = MPLEX_SWITCH_OVER_REASON
Value 'BB': The call disconnect reason can have the following values:
0x00 = UNKNOWN_DISC_REASON
0x01 = HUP_FROM_CS_REASON
0x02 = BUSY_TONE_REASON
0x03 = NO_LINE_AVAIL_REASON
0x04 = TOUT_DIALING_REASON
0x05 = TOUT_DCD_REASON
0x06 = DCD_OFF_REASON
0x07 = WDT_EXPIRED_REASON
0x08 = ECAR_DEATH_REASON
0x09 = PHONE_LIST_EMPTY_REASON
0x0A = ALR_SEQ_TERMINATED_REASON
0x0B = RINGING_PHASE_REASON
0x0C = ALARM_PHASE_REASON
0x0D = ALARM_WAIT_TO_START
0x0E = PSTN_CMD_ERROR_REASON
0x0F = NO_IDLE_STATE
Value 'CC': Shows the number of link disconnects since the last
powerup, a value of FF shows that at least 255 disconnects occurred
since the last power up
Value 'D' and 'E': Shows the link status of link 1 and link 2, it can have
the following values:
0x00-0x03 = the link quality where 3 is the best and 0 is the worst
0x0F = link physically disconnected
Source ID
9000 S_OUT_OF_SERVICE_OPERATION
This section describes the 9000_9999_Status error

Summary S_OUT_OF_SERVICE_OPERATION.
None.
Description
Bit-Mask 31...0
Extra Info
Bit 0-7: Service Id
None.
Source ID
9001 S_PASSENGER_TRAVEL_OPERATION

Summary S_PASSENGER_TRAVEL_OPERATION.
The elevator is in NORMAL passenger travel operation

Description
no additional info needed???

Extra Info
None.
Source ID
9002 S_INDEPENDENT_OPERATION

Summary S_INDEPENDENT_OPERATION.
The elevator is in independent service operation

Description
None.
Extra Info
None.
Source ID
9003 S_FIRE_OPERATION

Summary S_FIRE_OPERATION.
The elevator is in fire recall operation.

Description
Bit-Mask 31...0
Extra Info
Bit 0: State KBFH3
Bit 1: State KBFH2
Bit 2: State KBFH1
Bit 3: State JBF
Bit 4: State KBF
None.
Source ID
9004 S_FIREFIGHTER_OPERATION

Summary S_FIREFIGHTER_OPERATION.
The elevator is in firefighter operation

Description
Bit-Mask 31...0
Extra Info
Bit 0: State JBFF
Bit 1: State JNFF
None.
Source ID
9005 S_EMERGENCY_POWER_OPERATION

Summary S_EMERGENCY_POWER_OPERATION.
The elevator is emergency power operation

Description
None.
Extra Info
None.
Source ID
9006 S_EARTHQUAKE_OPERATION

Summary S_EARTHQUAKE_OPERATION.
The elevator is in earthquake recall operation

Description
None.
Extra Info
None.
Source ID
9007
S_EMERGENCY_MEDICAL_TECHNICIAN

Summary S_EMERGENCY_MEDICAL_TECHNICIAN.
The elevator is in medical technician operation. This operating mode is

Description used by the ambulance in order to get a needy person efficiently out of
the building (indepenedent operation).
None.
Extra Info
None.
Source ID
9009 S_WATER_IN_PIT_OPERATION

Summary S_WATER_IN_PIT_OPERATION.
The elevator is in recall operation due to water in the pit

Description
None.
Extra Info
None.
Source ID
9011
S_PASSENGER_TRAVEL_OPERATION_WITHOUT_LOAD_MONITOR

Summary S_PASSENGER_TRAVEL_OPERATION_WITHOUT_LOAD_MONITOR.
The elevator is in passenger travel operation (normal operation) but the car load measurement is disabled.
Description
None.
Extra Info
None.
Source ID
9012
S_PASSENGER_RELEASE_TRAVEL_OPERATION

Summary S_PASSENGER_RELEASE_TRAVEL_OPERATION.
Due to harmless technical defect the elevator operates is in a reduced

Description operation and releases all the passengers before it changes to breakdown
state.
None.
Extra Info
None.
Source ID
9014
S_BUILDING_EMERGENCY_POWER_RECALL

Summary S_BUILDING_EMERGENCY_POWER_RECALL.
The elevator is recalling to the predefined floor with building emergency

Description power.
None.
Extra Info
None.
Source ID
9015 S_PRIORITY_TRAVEL

Summary S_PRIORITY_TRAVEL.
The elevator performs a priority (exclusive) travel.

Description
None.
Extra Info
None.
Source ID
9016 S_HOSPITAL_EMERGENCY_TRAVEL

Summary S_HOSPITAL_EMERGENCY_TRAVEL.
The elevator performs hospital emergency travel.

Description
None.
Extra Info
None.
Source ID
9039 S_OVERLOAD_SERVICE

Summary S_OVERLOAD_SERVICE.
The elevator is not operating because the car is overloaded.

Description
None.
Extra Info
None.
Source ID
9044 S_OUT_OF_SERVICE_FROM_REMOTE

Summary S_OUT_OF_SERVICE_FROM_REMOTE.
The elevator is set out-of-service from remote (SAB)

Description
None.
Extra Info
None.
Source ID
9045
S_OUT_OF_SERVICE_STM_MONITORING_FAILURE

Summary S_OUT_OF_SERVICE_STM_MONITORING_FAILURE.
The elevator is blocked for automatic operation due to failure of the STM
Description insufficient residual strength monitoring.
None.
Extra Info
None.
Source ID
9050 S_SERVICE_TECHNICIAN_VISIT

Summary S_SERVICE_TECHNICIAN_VISIT.
The elevator is in service operation. Somebody (e.g. service

Description technician) is on site and performing some maintenance work. The
elevator is not available for the public.
Extra info indicates if service visit was turned on or off.

Extra Info
None.
Source ID
9051 S_INSTALLATION_TRAVEL

Summary S_INSTALLATION_TRAVEL.
The elevator is in installation travel operation (montage mode)

Description
None.
Extra Info
None.
Source ID
9070 S_ELEVATOR_RECOVERY

Summary S_ELEVATOR_RECOVERY.
AKA UNV: The elevator is recovering from a common failure at any

Description elevator component.
Bit-Mask 31...0
Extra Info
Bit 0-7: DriveState (byte number)
Bit 8: Drive Available (bool)
Bit 9: LMS State (bool)
Bit 10: DoorAvailable (bool)
Bit 11: LiftAvailable (bool)
None.
Source ID
9072
S_ELEVATOR_CAR_POSITION_RECOVERY

Summary S_ELEVATOR_CAR_POSITION_RECOVERY.
The elevator is recovering from a lost or unknown car position

Description (syncronization or correction trip)
Bit-Mask 31...0
Extra Info
Bit 0-7: TripType
None.
Source ID
9080 S_STOP_SWITCH

Summary S_STOP_SWITCH.
The elevator is stopped due to pressed (installation and maintenance)

Description stop switch
Bit-Mask 31...0
Extra Info
Bit 0: State JHSK
Bit 1: State JHSG
Bit 2: State JHM
Bit 3: State JHCT
Bit 4: State JHCC
Bit 5: State JHC1
Bit 6: State JHC
None.
Source ID
9098 S_ELEVATOR_BREAKDOWN

Summary S_ELEVATOR_BREAKDOWN.
AKA FATL: The elevator is blocked

Description
Bit-Mask 31...0
Extra Info
Bit 0-7: DriveState (byte number)
None.
Source ID
9200 S_SERVICE_CHANGE

Summary S_SERVICE_CHANGE.
The elevator switch to a new service state

Description
Bit-Mask 31...0
Extra Info
Bit 0-15: ActivationCondition
Bit 16-23: TriggerSignal
Bit 24-31: Service Id
None.
Source ID
9201 S_CLEAR_MAINTENANCE_MSG

Summary S_CLEAR_MAINTENANCE_MSG.
A maintenance message has been cleared from the notice list.

Description
Bit-Mask 31...0
Extra Info
Bit 0-31: Maintenance Message Id
None.
Source ID
Generic Information

Codigos de Error Miconic MX-GC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Codigos de Error Miconic MX-GC

Uploaded by

Copyright:

Available Formats

OPERATION: Errors

This section describes the Travel Control error No Event.

This section describes the Travel Control error NormalStop.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error ExceptionMC.

Exceptions of microprocessor. The system jumps to the exception

Only relevant to Miconic VX and TX4 (IVXVF board)

ID Possible causes of message Actions to be taken

This section describes the Travel Control error NoKSE_STDSTL.

La cabina se detiene en uno de los extremos del hueco y detecta que

ID Possible causes of message Actions to be taken

This section describes the Travel Control error InvldMovement.

Invalid movement. A movement of the car was detected while Travel

ID Possible causes of message Actions to be taken

This section describes the Travel Control error SH_on_STDSTL.

The contactor SH or SH1 is active in standstill.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error SB_on_STDSTL.

ID Possible causes of message Actions to be taken

ID Location Actions to be taken

This section describes the Travel Control error SH_Fault.

Los contactos auxiliares de SH / SH1 (o RH / RH1) se abrieron

ID Possible causes of message Actions to be taken

This section describes the Travel Control error SB_Fault.

El contacto auxiliar SB se abrió cuando la cabina se estaba

ID Possible causes of message Actions to be taken

ID Location Actions to be taken

This section describes the Travel Control error KB_Fault.

Los contactos de freno KB ó KB1 no conmutan adecuadamente. La

ID Possible causes of message Actions to be taken

ID Location Actions to be taken

This section describes the Travel Control error FC_Fault.

a) El variador de frecuencia solicitó una parada de emergencia.

Comentarios: El control de tracción monitoriza el contactor SH.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error FC_Block.

El estado del control de la tracción es "bloqueado"

ID Possible causes of message Actions to be taken

This section describes the Travel Control error DirectionErr.

The car moved more than 2.5 cm in the wrong direction.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error OverSpeed.

Si la diferencia entre la velocidad real de la cabina, calculada a partir

ID Possible causes of message Actions to be taken

ID Location Actions to be taken

This section describes the Travel Control error UnderSpeed.

Si la diferencia entre la velocidad real de la cabina, calculada a partir

ID Possible causes of message Actions to be taken

ID Location Actions to be taken

This section describes the Travel Control error NoTargetLow.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error NoTargetUp.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error OverSpeedKSE.

0: Overspeed detected with car in KSE zone.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error NoLowerKSE.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error NoUpperKSE.

ID Possible causes of message Actions to be taken

This section describes the Travel Control error PositionLost.

El error se produce cuando:

"- La cabina pasa por una posición de piso sin detectar la