Errors SCH

Cadi GC Home Page
Document
OPERATION: How to Use
OPERATION: Parameters
OPERATION: Telegrams
OPERATION: Errors
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/default_en.htm[29.6.2010. 17:06:04]
Error Help - Main Index
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
1400...1499 VF
1500...1699 Travel Control Ext
5000...5099 5000_5099_Remote_Monitoring
INVENTIO AG This design and information is our intellectual property. It must without our written
Restrictions CH-6052 Hergiswil consent neither be copied in any way nor used for manufacturing nor communicated
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/default_en.htm[29.6.2010. 17:06:05]
Error Help - Group Index
0...149 Travel Control
No. Section
Contents
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/000_149_Travel_Control/default_en.htm[29.6.2010. 17:06:06]
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 No Start Ok
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 IVXVF_HW_Fault
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 MoSis_Error
0128 LOWER_KSE_LOW_SYNCH
0129 EQ_Midpoint_Fault
0130 PCT_Drive_Para
0131 MoSis_KNE_Fault
0132 MoSis_ETSL_Fault
0133 Inverter Para Not Accepted
0134 NTSD_Triggered
0135 DREC_DRH_button
0136 Safety Bypass
0137 JHCC_Pressed
0138 Brake Not Set
0139 Unintended Car Movement
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
to third parties.
150...199 Variodyn E
No. Section
Contents
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/150_199_Variodyn_E/default_en.htm[29.6.2010. 17:06:07]
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/150_199_Variodyn_E/default_en.htm[29.6.2010. 17:06:07]
200...299 Door Control
No. Section
Contents
0201 ConfigErr
0202 DoorOperErr
0203 ThermoDoorMot
0204 DoorRevDevErr
0205 DoorContrErr
0206 DoorBoltErr
0207 CloseSeqErr
0208 DoorDevErr
0209 DoorContact
0210 Lift Guardian
0211 COM_Busreconf
0240 SW-Warning
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/200_299_Door_Control/default_en.htm[29.6.2010. 17:06:07]
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/300_399_Varidor70_Door_Drive/default_en.htm[29.6.2010. 17:06:08]
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
to third parties.
400...599 Lift
No. Section
Contents
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 Reserve_Error_415
0420 SCT/PCT-Checksum
0421 Invalid Parameter Value
0422 FLASH Failure
0423 PCT define
0424 Parameter Missing
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/400_599_Lift/default_en.htm[29.6.2010. 17:06:09]
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
0450 Parameter Configuration Error
0451 IO Configuration Error
0452 SCT/PCT read error
0453 Timer Table Overflow
0454 SW-Warning54
0455 SW-Warning55
0456 SW-Warning56
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 SW-Warning75
0476 Fatal Error ON (Breakdown)
0477 Fatal Error OFF
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
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 Device Error
0508 WAD-Service
0509 Group Master Conflict
to third 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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/600_699_MC_PVF/default_en.htm[29.6.2010. 17:06:10]
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
to third 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 SGR/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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/700_739_MC_PVEC/default_en.htm[29.6.2010. 17:06:11]
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 Overtemperature Line Choke
0733 Mains current difference
0734 Mains Overcurrent
0735 Mains Interruption
0736 Mains Voltage out of range
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/700_739_MC_PVEC/default_en.htm[29.6.2010. 17:06:11]
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/740_799_Magnetek/default_en.htm[29.6.2010. 17:06:11]
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
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/740_799_Magnetek/default_en.htm[29.6.2010. 17:06:11]
800...899
800_899_Varidor35_Door_Drive
No. Section
Contents
0809 Wrong Motion Command Value
0812 Wrong Motion Direction
0818 No Heartbeat from Elevator Control
0821 Door Movement too Fast
to third parties.
900...999 IO
No. Section
Contents
0901 ConfigErr
0902 PIO Error
0903 IO Table Overflow
0904 IO_Missing
0905 COP Configuration Error
0906 Duplicate_BMK
0910 COM_Busreconf
0951 IO_Configuration_Error
0952 EEP_BurnProbl
0953 Deployment_Rule_Failure
0961 EEP_BurnProbl
0970 Timer Error
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/900_999_IO/default_en.htm[29.6.2010. 17:06:12]
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 IVXVF Reserve12
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1000_1199_CPU/default_en.htm[29.6.2010. 17:06:13]
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
to third parties.
1200...1249 LON
No. Section
Contents
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1200_1249_LON/default_en.htm[29.6.2010. 17:06:14]
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 LonErr44
1245 LonErr45
1246 LonErr46
1247 LonErr47
1248 LonErr48
1249 NodePowerFail
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1200_1249_LON/default_en.htm[29.6.2010. 17:06:14]
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
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1250_1299_BIO2/default_en.htm[29.6.2010. 17:06:14]
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1400_1499_VF/default_en.htm[29.6.2010. 17:06:15]
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
to third parties.
1500...1699 Travel Control Ext
No. Section
Contents
1501 Invalid Car Position
1502 Position Jump
1503 Defect_MoSis_Sensor
1504 Safety T6
1505 Invalid Floor Position during Trip
1506 Invalid Floor Position in Standstill
1507 Brake ON standstill
1508 Brake not ON start
1509 Brake OFF Run
1510 Brake not OFF stop
1511 Traction Media Broken
1512 SI Communication Lost
1513 SI UET Fault
1514 SI FLOOR 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 Info
1523 SI KNE Info
1524 CAN Sync Send
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1500_1699_Travel_Control_Ext/default_en.htm[29.6.2010. 17:06:16]
1525 CAN Controller

1526 ZSB Fault
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1500_1699_Travel_Control_Ext/default_en.htm[29.6.2010. 17:06:16]
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
to third parties.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/5000_5099_Remote_Monitoring/default_en.htm[29.6.2010. 17:06:16]
Error Help - 0001 NormalStop
0001 NormalStop
This section describes the Travel Control error NormalStop.

Summary
Normal termination of the trip. Note: The default event handling

Description code prevents this event being logged in CADI.
None.
Extra Info
None.
Source ID
ID Possible causes of Actions to be taken

Causes and message
Actions
1 None. No measure needed.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/000_149_Travel_Control/err_0001_en.htm[29.6.2010. 17:06:17]
Error Help - 0002 ExceptionMC
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.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 None. Report problem on hotline.
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.
Error Help - 0003 NoKSE_STDSTL
0003 NoKSE_STDSTL
This section describes the Travel Control error NoKSE_STDSTL.

Summary
The car stops at one of the shaft ends and detects that the KSE
Description signal does not correspond to the position calculated by the
distance tacho.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Incorrect parameter values Check that the physical
position of the KSE magnets in
the shaft is equal to the
value(s) of the parameters
'KSE_DISTANCE' and
'SHAFT_PARA.GAP_LENGTH'
(shaft parameters).
2 Incorrect magnet polarity Check the polarity of the
magnets.
3 The lowest KSE magnet is a
south.
4 The next magnet (lowest
magnet of the gap) is a north.
5 The uppermost magnet is a
south.
6 KSE Switch Check the KSE switch.
Error Help - 0003 NoKSE_STDSTL
7 Check the connection from the

KSE switch to the PCB.
Error Help - 0004 InvldMovement
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 message
Actions
1 Defective drive brake or bad Check the mechanical brake (
brake adjustment (brake Adjustment of brake ,
torque not sufficient to hold possible wear of brake lining
car at standstill) ). Brake 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.
Error Help - 0005 SH_on_STDSTL
0005 SH_on_STDSTL
This section describes the Travel Control error SH_on_STDSTL.

Summary
The contactor SH or SH1 is detected energised during standstill

Description phase.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check the auxiliary contacts
of SH, SH1 (RH and RH1 if
fitted)
2 SH or SH1 are operated by None.
hand
Error Help - 0006 SB_on_STDSTL
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
Description SB) activates the brake during standstill phase.
00 (hex)/ 0 (dec):,: RB fault (for MX-GC) :RB open before starting a

Extra Info trip
0C (hex)/12 (dec): MBB brake module: Brake open during standstill
(MBB_OPEN_STANDSTILL)
None.
Source ID

Causes and message
Actions
1 Bad connection/wiring of the Check the auxiliary contacts
feedback contact of 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.
Error Help - 0007 SH_Fault
0007 SH_Fault
This section describes the Travel Control error SH_Fault.

Summary
The auxiliary contacts of SH / SH1 (or RH / RH1) opened while the

Description car was moving.
Source-ID 104 (MONITOR)

Extra Info 1: SH and SH1 opened together (SH1 state is faulty)
3: SH and SH1 opened together (SH state is faulty)
5: RH and RH1 opened together (RH1 state is faulty)
8: RH and RH1 opened together (RH state is faulty)
Source-ID 114 (PREPARE_TRIP)

0: RTSC closed and Safety-chain open (old TX-Safety)
1: RTSC closed and Safety-chain closed (old TX-Safety)
2: RTSC not closed (old TX-Safety)
3: Safety-Chain open (MX2, MX5 , TX2_EU, TX2_NA, TX_NA,
TX_NA_A17_2000 .... safety)
4: Safety-Chain closed (MX2, MX5 , TX2_EU, TX2_NA, TX_NA,
TX_NA_A17_2000 .... safety)
5: SH-State is faulty on trip start, initiate shaking test (MX-Safety)
Identifies the file in the core software from where the message is
Source ID generated.
Refer to error 70 for the description.

Causes and message
Actions
1 Safety circuit open Check the safety circuit
2 Wrong parameter value If the error occurs when the
car is approaching the target
floor it may be caused by the
door pre-opening circuit.
Error Help - 0007 SH_Fault
Reduce value for parameter

MAX_DOOR_ZONE.
3 Bad wiring Check the auxiliary contact
wiring of SH, SH1 (RH, RH1)
Error Help - 0008 SB_Fault
0008 SB_Fault
This section describes the Travel Control error SB_Fault.

Summary
The SB auxiliary contact opened when the car was moving or an

Description error on brake module occurred (e.g. MBB)
with MBB:
Extra Info 01 (hex)/ 1 (dec): (MBB_TASK_CREATE_ERROR) = State
message
02 (hex)/ 2 (dec): (MBB_BUFFER_OVERFLOW_ERROR) = IO
message
03 (hex)/ 3 (dec): (MBB_INT_WRONG_MSG) = Unknown message
received
04 (hex)/ 4 (dec): (MBB_ZERO_MESSAGE) = Zero length message
sent
05 (hex)/ 5 (dec): (MBB_UNKNOWN_COMMAND) = Unknown
command received
06 (hex)/ 6 (dec): (MBB_KB_FAULT) = KB fault
07 (hex)/ 7 (dec): (MBB_KB1_FAULT) = KB1 fault
08 (hex)/ 8 (dec): (MBB_OPEN_TIMEOUT_CURRENT) = Open
timeout , no current
09 (hex)/ 9 (dec): (MBB_CLOSE_TIMEOUT_CURRENT) = Close
timeout, no 0 current
0A (hex)/10 (dec): (MBB_IGBT3_FAULT) = IGBT fault or other error
0B (hex)/11 (dec): (MBB_HW_FAULT) = Error on MBB HW
0C (hex)/12 (dec): (MBB_OPEN_STANDSTILL) = Brake open
during stanstill
0D (hex)/13 (dec): (MBB_CLOSED_RUNNING) = Brake closed
during trip
0E (hex)/14 (dec): (MBB_MBX_ERROR) = MBB mailbox error
0F (hex)/15 (dec): (MBB_MAX_MESSAGE_SIZE) = MBB too long
message size
10 (hex)/16 (dec): (MBB_CURRENT_DIFF_ERROR) = MBB current
difference error
11 (hex)/17 (dec): (MBB_MAINS_NOT_OFF) = Mains did not switch
Error Help - 0008 SB_Fault
off
12 (hex)/18 (dec): (MBB_IGBT1_FAULT) = IGBT1 check not O.K.
13 (hex)/19 (dec): (MBB_VOLTAGE_DIFF_ERROR) = MBB voltage
difference error
Brake Module MX:
14 (hex)/20 (dec): (MBB_KBR_FAULT) = RB fault (for MX-GC)
15 (hex)/21 (dec): (MBB_ZSB_FAULT) = Brake time relay fault (for
MX-GC)
None.
Source ID

Causes and message
Actions
1 Open safety circuit Check the safety circuit
2 Auxiliary contacts of SB/SB1 Check operation of auxiliary
not working contacts of SB/SB1.
3 Check wiring of auxiliary
contacts of SB/SB1
4 Relay RB not working Check operation of relay RB
5 Dust in the control cabinet or Remove dust
other difficult environmental
conditions causing
conductivity problems.
6 MBBx (extra info value Check the electrical circuit
x0000000A): Open brake from the cabinet to the
circuit or faulty brake module brake(s)
or replace brake module
7 MBBx (extra info value Check the electrical circuit
x00000010): Short circuit at from the cabinet to the
brake module output brake(s)
8 MBBx: No AC supply voltage Check supply voltage for the
for brake module brake module
Error Help - 0009 KB_Fault
0009 KB_Fault
This section describes the Travel Control error KB_Fault.

Summary
The brake contacts KB or KB1 do not switch properly. Travel Control

Description expects both KB and KB1 information. In case of only one KB
contact, check that there is a jumber on the connector to the PCB.
Comment: With gearless drives, check that the brake contacts work
properly, and that the brake power supply is ok; when the brake
opens, SB is operated first (full power supply to the brake) and just
afterwards the voltage reduction to the brake is activated (e.g.
SGRB or electronic brake module). The operation of the voltage
reduction is independent of the KB and KB1 status.
The brake has a certain time within which it must open; after this
time the contacts are checked. The brake contact(s) is a delicate
component in the control system. Make sure the contacts are well
fixed and clean. Consult the corresponding instruction to adjust the
brake contacts (experience shows, that probably the best
adjustment is to allow a gap of 1 mm between the contact and the
actuating element when the brake is closed).
with MBB:
Extra Info 01 (hex)/ 1 (dec): (MBB_TASK_CREATE_ERROR) = State
message
02 (hex)/ 2 (dec): (MBB_BUFFER_OVERFLOW_ERROR) = IO
message
03 (hex)/ 3 (dec): (MBB_INT_WRONG_MSG) = Unknown message
received
04 (hex)/ 4 (dec): (MBB_ZERO_MESSAGE) = Zero length message
sent
05 (hex)/ 5 (dec): (MBB_UNKNOWN_COMMAND) = Unknown
command received
06 (hex)/ 6 (dec): (MBB_KB_FAULT) = KB fault
07 (hex)/ 7 (dec): (MBB_KB1_FAULT) = KB1 fault
08 (hex)/ 8 (dec): (MBB_OPEN_TIMEOUT_CURRENT) = Open
timeout , no current
09 (hex)/ 9 (dec): (MBB_CLOSE_TIMEOUT_CURRENT) = Close
timeout, no 0 current
0A (hex)/10 (dec): (MBB_IGBT3_FAULT) = IGBT fault or other error
0B (hex)/11 (dec): (MBB_HW_FAULT) = Error on MBB HW
0C (hex)/12 (dec): (MBB_OPEN_STANDSTILL) = Brake open
during stanstill
0D (hex)/13 (dec): (MBB_CLOSED_RUNNING) = Brake closed
during trip
0E (hex)/14 (dec): (MBB_MBX_ERROR) = MBB mailbox error
0F (hex)/15 (dec): (MBB_MAX_MESSAGE_SIZE) = MBB too long
message size
10 (hex)/16 (dec): (MBB_CURRENT_DIFF_ERROR) = MBB current
difference error
11 (hex)/17 (dec): (MBB_MAINS_NOT_OFF) = Mains did not switch
off
12 (hex)/18 (dec): (MBB_IGBT1_FAULT) = IGBT1 check not O.K.
13 (hex)/19 (dec): (MBB_VOLTAGE_DIFF_ERROR) = MBB voltage
difference error
None.
Source ID

Causes and message
Actions
1 Defective brake contact(s) Check the brake 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.
brake
4 Observe the brake when it
opens.
5 Both sides of the brake
should open symmetrically.
6 Wrong parameter value for Check drive parameters
parameter 'KB feedback type' (settings) for correct brake
type.
Error Help - 0010 FC_Fault
0010 FC_Fault
This section describes the Travel Control error FC_Fault.

Summary
a) The frequency converter requested an emergency stop.

Description b) The control detected a communication problem to the frequency
converter.
Comments: The Motor Control monitors the contactor SH. When the
the safety circuit opens during a trip Motor Control may detect this
before Travel Control. So this event can also be caused by a safety
circuit problem. Please refer also to the error description for error
'SH_Fault'.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Drive internal problem Check the event log of Motor
Control for detailed
information.
2 Communication to frequency Check the wiring and plugs of
converter (temporarily) the connection cable between
interrupted the FC and the control.
Error Help - 0011 FC_Block
0011 FC_Block
This section describes the Travel Control error FC_Block.

Summary
Motor Control state is 'blocked'.

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Refer to Motor Control related
diagnostics
2 Variodyn E: BARMAG error Reset frequency converter. If
red LED on ER113 not successful, check internal
error-log of frequency
converter with a terminal
emulation.
Short Manual:
1. To start press 's' / 2. Press
'f' and read error (s. below) /
3. To quit, press F10 /
4. Reset frequency converter
again.
3 Internal frequency converter Possible Causes
error messages:
4 U_ZK < UZK_MIN Power net voltage too low.
Missing net phase.
Error Help - 0011 FC_Block
5 U_ZK > UZK_MIN Chopper resistor not

connected, wrong specificied
(Ohm) or defective. Improper
parameter setting.
6 I > I_MAX Defective freq. converter
VF20/30. Short-circuit or
ground-short on engine
wiring. Improper parameter
setting.
7 TIBR > 5 S Interface board does not reset
start signal. Check brake
function.
8 NET > OFF Malfunction of freq. converter
VF20/30.
9 KEINE IMPULSE Check tacho power supply
(Pin 1 and 2 on IG100-
connector). Defective
VF20/30 control board.
Slippage of tacho rope.
Defective tacho device.
10 ZEIT V K-FAHRT Instruction correction trip has
not been reset.
11 VBET < 1.15 x VKN/2 Value VKN set too high.
DELTA_U too low. Slippage
of tacho rope. Wiring defects.
Defective freq. Convert.
Mechanical defect on elevator
system.
12 VBET > 1.15 x VKN Value VKN set too low.
FC_MAX_R set too high.
MM_IMP set too high.
Mechanical defect on elevator
system.
13 TEMP > T_MAX Permanent exceeding of
nominal current. Cooling
blowers not connected or
defective. Air stream
restrained. Wrong direction of
rotation.
Error Help - 0012 DirectionErr
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 message
Actions
1 Incorrect load input Check the load measurement
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.
Error Help - 0013 OverSpeed
0013 OverSpeed
This section describes the Travel Control error OverSpeed.

Summary
The error is logged in the following cases:

Description
a) The software detects that the actual speed of the car exceeds the
maximum limit for the car speed. The software calculates the speed
limit based on the current speed reference value which is sent to the
inverter Vlim = f(Vref). If the difference between the actual speed of
the car and the speed reference (velocity_ref) exceeds the
calculated limit the trip is interrupted with an emergency stop. The
allowed speed difference is calculated as follows: 6.25% of the
actual reference speed; the minimum for the allowed speed
difference is 0.2m/s (applies also when the car is standing). The
actual speed value which is compared against the limit is either the
calculated speed from the car position encoder (s_tacho) or the
actual speed recevied from the inverter (v_tacho).
b) that the speed reference (velocitiy_ref) was outside the allowed

limits (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
If the limit for velocity reference is exceeded an additional SW
warning (error #70) is logged with the same time stamp and with the
extra info hex35A/dec858
0: speed calculated from position tacho (car) too high

Extra Info 1: actual speed from inverter too high with IMOF
2: actual speed from inverter too high
3: speed calculated from position tacho (car) too high with IMOF
other values: value of the velocity reference when it is above or
below the max. or min. limit

Causes and message
Actions
1 Incorrect parameter values Check the parameters both
on Travel Control and Motor
Control.
2 Incorrect tacho input from Check position tacho.
position tacho
3 Incorrect load value from load Check the load measurement
measuring system causing device and the load
wrong torque on machine parameters. These checks
should also be made if the
event occurs just at the
beginning of the trip.
4 Car moves faster than the Check if machine brake
detection speed limit while applies sufficient mechanical
the drive/motor is switched torque. Perform brake test
off. May be caused by loss of according to acceptance test
traction at standstill or manual instruction.
opening of the brake.
5 Excessive rope stretch (e.g. Adjust parameter for rope
ARAMID ropes). Position elongation.
control for car attempts to do

correction with a velocity
reference outside the limits.
Error Help - 0014 UnderSpeed
0014 UnderSpeed
This section describes the Travel Control error UnderSpeed.

Summary
If the difference between the actual speed of the car calculated from
Description the position encoder and the reference speed (velocity_ref) exceeds
the calculated limit (speed tolerance) the trip is interrupted with an
emergency stop. The allowed speed difference (tolerance) is
calculated as follows: 6.25% of the reference speed with a minimum
of 0.1m/s. The allowed speed difference is 0.1m/s up until a speed
of 1.6m/s.
The software detects that the actual speed of the car is below the
minimum limit for the car speed. The software calculates the speed
limit based on the current speed reference value which is sent to the
inverter Vlim = f(Vref). If the difference between the actual speed of
the car and the speed reference (velocity_ref) is below the
calculated limit the trip is interrupted with an emergency stop. The
allowed speed difference is calculated as follows: -6.25% of the
actual reference speed; the minimum for the allowed speed
difference is 0.2m/s. The actual speed value which is compared
against the limit is either the calculated speed from the car position
encoder (s_tacho) or the actual speed recevied from the inverter
(v_tacho).
0: speed calculated from position tacho (car) too low

Extra Info 1: actual speed from inverter too low with IMOF
2: actual speed from inverter too low
3: speed calculated from position tacho (car) too low with IMOF

Causes and message
Error Help - 0014 UnderSpeed
Actions
1 Incorrect parameter values Check the parameters both
on Travel Control and Motor
Control.
2 Incorrect tacho input from Check position tacho
position tacho
3 Incorrect load input Check the load measurement
device and the load
parameters. These checks
should also be made if the
event occurs just at the
beginning of the trip.
4 Speed reference value Check speed and
exceeds capabilites of the acceleration parameters.
inverter; the inverter is not
able to follow the trip curve.
5 Car or counterweight Make sure car and
machanically blocked counterweight can move in
guide rails.
6 Rope slip on tracton sheave Check correct balancing of
car/counterweight.
Error Help - 0015 NoTargetLow
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 message
Actions
1 Incorrect KSE signal Check KSE parameters and
magnets.
2 Please inform Ebikon if this
event appears
Error Help - 0016 NoTargetUp
0016 NoTargetUp
This section describes the Travel Control error NoTargetUp.

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

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

Summary
Overspeed detected while car is inside the upper or lower KSE

Description position (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 message
Actions
1 Incorrect KSE input Check KSE parameters and
position of magnets. Repeat
the learn trip.
2 Variodyn E: Improper Check KSE distance
parameter settings (frequency
converter) Check frequency
converter parameter values
Error Help - 0018 NoLowerKSE
0018 NoLowerKSE
This section describes the Travel Control error NoLowerKSE.

Summary
There was a discrepancy between the position of the lower KSE

Description switch 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 message
Actions
1 Wrong KSE parameter or Check the KSE parameters
faulty magnets and position of magnets in the
shaft. Execute new learn trip
after magnet was moved.
2 Check the position tacho.
Error Help - 0019 NoUpperKSE
0019 NoUpperKSE
This section describes the Travel Control error NoUpperKSE.

Summary
There was a discrepancy between the position of the upper KSE

Description switch 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 message
Actions
1 Wrong KSE parameter or Check the KSE parameters
faulty magnets and position of magnets in the
shaft. Execute new learn trip
after magnet was moved.
2 Check the position tacho.
Error Help - 0020 PositionLost
0020 PositionLost
This section describes the Travel Control error PositionLost.

Summary
Error occurs when:

Description
- the car passes a floor fin/magnet at a measured position more than
15cm off the reference position stored during the learn trip.
- the car passes a floor position without detecting a floor fin/magnet

at that floor position stored during learn trip.
- the car approaches a target floor without finding a floor fin/magnet

at that floor position stored during learn trip.
- the car is at a floor level and detects no floor fin/magnet.
Comments:
- Travel Control initiates a synchronisation trip after the error
occurrs. In case of incremental position tacho (IG) the car will make
a trip to the KSE position. In case of an absolute encoder-type
position tacho (AGSI) the car will go to the next floor level.
- If the car is standing at floor level and one of the photocells gives
an incorrect message OUT_FIN, Travel Control takes the photocell
information to be actual and assumes that the car is at the edge of
the fin and not at floor level. (This situation can occur in large
buildings with significant rope stretch, if the car is standing a long
time at the floor level). Travel Control overwrites the position and a
relevel_trip is started for a distance of 15mm. Since the car was at
level at the beginning of this trip the second photocell will go out of
the fin. Now both photocells are out of the fin, but Travel Control still
assumes the car is almost level, which is detected as a
POSITION_LOST.
0 (hex)/ 0 (dec): With the car at a floor level neither signal PHS nor
Extra Info PHNR_D is active ('IN_FIN'). 'OUT_FIN' transition of signal PHS
occurs later than expected.

1 (hex)/ 1 (dec): 'OUT_FIN' transition of signal PHNR_D occurs later
than expected.
2 (hex)/ 2 (dec): TX-GC2: Corrupted shaft info ==> Floor position /
MX-GC with AGSI: LUET did not switch while passing a floor.
3 (hex)/ 3 (dec): MX-GC/TX-GC: Corrupted shaft info ==> Floor
position
4 (hex)/ 4 (dec): TX-GC2: Corrupted shaft info ==> KSE-D /
Mismatch detected between the door zone information (KUET) and
the position value from the car position feedback device (AGSI/IGS).
The digital signal for the door zone from the shaft information
(LUET) is active but the car position value says the car is well
outside the door zone.
5 (hex)/ 5 (dec): MX-GC/TX-GC: Corrupted shaft info -> KSE-D
8 (hex)/ 8 (dec): TX-GC2: Corrupted shaft info -> KSE-U
9 (hex)/ 9 (dec): MX-GC/TX-GC: Corrupted shaft info -> KSE-U
A (hex)/ 10 (dec): Position of KSE-U magnet found more than 15cm
away from the position stored during the learn trip.
B (hex)/ 11 (dec): Position of KSE-D magnet found more than 15cm
away from the position stored during the learn trip.
C (hex)/ 12 (dec): While doing a synch trip KSE-D magnet switched
more than 15cm away from the position stored during the learn trip.
ndef
Source ID

Causes and message
Actions
1 Mechanical problem with the Check the position of the fins
shaft information. or magnets. Repeat the learn
trip.
2 Check the horizontal distance
between fins/magnets and
photocell/switch. Make sure
the clearance of the car is not
too big when the car is at floor
levels.
3 The position tacho (IG type or Check for mechanical slip on
AGSI type) is not working the position tacho.
properly.
4 Check that the tacho runs

smoothly.
5 Check the tacho rope and its
tension force, as well as the
two pulleys for the rope. The
groove of the tacho pulleys
has to be clean (especially for
IGS-200).
6 Wrong car position values Check car position value
from the car position tacho. shown on the SMLCD (or
UI1). Check for EMC
problems and refer to
explanations for extra info
values.
7 Problem with electrical Check the power supply for
interferences on the the photocells.
photocells (PHS / PHNR_D or
magnetic switches)
8 Check the ground connection
on top of the car and from the
machine room/control cabinet
to the car.
Error Help - 0021 HigherPrio
0021 HigherPrio
This section describes the Travel Control error HigherPrio.

Summary
This message is logged when the software detects the interruption

Description of a 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
Error Help - 0021 HigherPrio

9 (hex)/ 9 (dec): Running in RELEVEL_TRIP and
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 message
Actions
1 - None.
Error Help - 0022 MaskErased
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
Description deletes 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 message
Actions
1 Activation of special control Check why the control
mode or service. deleted the trip type mask
(VXT_STCMD_DRIVE
/VXT_TRIP_TYPE_MASK
)
Error Help - 0023 JHC_Pressed
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 message
Actions
1 None
Error Help - 0024 JHC1_Pressed
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 message
Actions
1 None
Error Help - 0025 JHSG_Pressed
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 message
Actions
1 None
Error Help - 0026 JHR_Pressed
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 message
Actions
1 None
Error Help - 0027 JHM_Pressed
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 message
Actions
1 None
Error Help - 0028 OverTempMotor
0028 OverTempMotor
This section describes the Travel Control error OverTempMotor.

Summary
The measured motor temperature exceeds the temperature limits

Description defined by the parameter 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
P_ANT_TEMP_OVERHEAT_MOTOR the overtemperature limit was
fix at 150°C (Check motor parameters 'supervision').
0(hex)/0(dec): The motor temperature is below the minimum limit of

Extra Info -10°C. The elevator remains blocked until the motor temperatur
rises above the minimum limit (fixed value)
1(hex)/1(dec): The motor temperature is above the maximum limit

defined by the parameter 'PCT_ANT_TEMP_OVERHEAT_MOTOR'.
The elevator remains blocked until the motor temperature drops
20°C below the maximum limit.
A(hex)/10(dez): 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 message
Actions
1 Incorrect or missing PT100 Check wiring of temperature
connection to the motor. measurement device.
2 Overtemperature due to Check the main supply
excessive current or defectice connection to the motor and
ventilation on the motor. the ground connection.
3 Check the motor windings for
short circuit on the motor
terminal box.
4 Check for correct parameter
values of Motor Control.
5 Check the motor ventilator.
Error Help - 0029 TripBlocked
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 message
Actions
1 Establish why the controller
wants to block the drive.
2 Check for active control
features e.g. fire service or
emergency power supply
controls.
Error Help - 0030 NewTripBlockd
0030 NewTripBlockd
This section describes the Travel Control error NewTripBlockd.

Summary
The controller sent a telegram to Travel Control blocking the

Description beginning 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 message
Actions
1 Establish why the controller
wants to block the drive.
2 Check for active control
features e.g. fire service or
emergency power supply
controls.
Error Help - 0031 PrepNewDest
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 message
Actions
1 None
Error Help - 0032 PrepClearDest
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 message
Actions
1 None
Error Help - 0033 RelvNewDest
0033 RelvNewDest
This section describes the Travel Control error RelvNewDest.

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

Description Note: 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 message
Actions
1 Check if the drive repeats the
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
while at rest. then normal. In that case this
event does not mean
abnormal operation.
Error Help - 0034 SH_Timeout
0034 SH_Timeout
This section describes the Travel Control error SH_Timeout.

Summary
During trip preparation the auxiliary contact of the contactor SH or

Description SH1 ( resp. RH or RH1 if fitted) failed to close. Trip preparation is
aborted.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Defect in control circuit of Check the wiring of the main
main contactor contactor including safety
circuit and triggering of
contactor from drive.
2 Faulty contactor Check the contacor (auxiliary
contact) and the wiring to the
pcb.
3 Timing problem Adjust the monitoring time for
the main contactor by
adjusting the parameter
'SH_DELAY' (drive internal
parameter)
Error Help - 0035 FC_Timeout
0035 FC_Timeout
This section describes the Travel Control error FC_Timeout.

Summary
When preparing a new trip, Travel Control requests the status of the
Description 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 is
divided into the following states (phase):
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
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
Extra Info trip preparation:
10(hex0A): 'Preparation False' message from inverter in phase

'WAIT_CONTACTORS'
20(hex14): 'Preparation Wrong Trip Type' message from inverter in
phase 'WAIT_CONTACTORS'
01(hex01): 'Preparation False' message from inverter in phase
'ASK_FC_STATUS'
21(hex15): 'Preparation Wrong Trip Type' message from inverter in
phase 'ASK_FC_STATUS'
02(hex02): Timeout occurred in phase 'ASK_FC_STATUS' because
no response from inverter
03(hex03): Timeout occurred in phase 'ACTIVATE_FC' because no
response from inverter
Error Help - 0035 FC_Timeout
Variodyn E: Distance covered away from start [mm].
None.
Source ID

Causes and message
Actions
1 Motor Control not ready for Check Motor Control.Check
new trip connection to Motor Control.
2 Incorrect parameter on Adjust the time that Travel
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.
Error Help - 0036 No Start Ok
0036 No Start Ok
This section describes the Travel Control error No Start Ok.

Summary
The trip preparation exceeds the maximum allowed time limit

Description defined 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.
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.
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.
Error Help - 0036 No Start Ok
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
Identifies the file in the core software where the error message is
Source ID generated from. This information gives a general hint about the
nature of the problem (see help text for error 70 for the identification
list of the source code file).
The extra information (see below) gives additional information about
the exact cause.

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

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

Description rest. Note: If the internal Travel Control call simulation is active, this
event appears periodically.
None.
Extra Info
None.
Source ID
Error Help - 0038 TargetLost
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 message
Actions
1 Incorrect parameters Check the parameter
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
Error Help - 0039 NoDirRelv
0039 NoDirRelv
This section describes the Travel Control error NoDirRelv.

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

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

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

Summary
For IG type position tacho:

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.
Comments: 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 type position tacho:
Trip will be aborted if learn trip is triggered outside door zone
magnet (KUET).
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Incorrect shaft information With IG type (incremental)
position tacho:
2 Check the KSE signal
(distance, polarity of magnet,
wiring).
3 Check wiring of PHS.
4 Check ground connection of
photocell PHS.
5 With AGSI (absolute encoder)
Error Help - 0040 NoPHS_Learn
type position tacho:

6 Check the KUET signal
(polarity of magnet, wiring).
Error Help - 0041 ErrTachoFact
0041 ErrTachoFact
This section describes the Travel Control error ErrTachoFact.

Summary
Missmatch detected between actual fin length and value defined

Description with 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 message
Actions
1 Incorrect parameter values Check the parameters
(shaft) 'tacho_factor' and 'fin_length'
(shaft_para).
Error Help - 0042 LowKSE_Low
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
Description KSE 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 message
Actions
1 PHS not connected Check the PHS signal. If PHS
is not connected this event
will occur (status of car
appears 'IN_FIN' constantly ).
2 Incorrect shaft information Check the KSE signal
wiring ).
3 Check that the PHS photocell
is working correctly and is
mounted in the right position.
Error Help - 0043 LowKSE_High
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
Description KSE 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 message
Actions
1 PHS not connected Check the PHS signal. If PHS
is not connected this event
will occur (status of car
appears 'IN_FIN' constantly ).
2 Incorrect shaft information Check the KSE signal
wiring ).
3 Check that the PHS photocell
is working correctly and is
mounted in the right position.
Error Help - 0044 UpperKSE
0044 UpperKSE
This section describes the Travel Control error UpperKSE.

Summary
Travel Control measures the distance between the beginning of

Description KSE gap (magnet north polarity) and the upper most floor. If it the
measured valued is more than the value given with the parameter
shaft_para.kse_distance the trip is aborted. The tolerance is +/- 5
cm.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Incorrect KSE Check position and polarity of
KSE magnets.
2 Distances and parameters Check distance between the
not equal two upper KSE magnets; it
has to match the value of
parameter 'GAP_LENGTH'.
Error Help - 0045 NoFloorTop
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 message
Actions
1 Check KSE distance and
polarity of magnet.
Error Help - 0046 ErrFloorTop
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

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.
Error Help - 0046 ErrFloorTop
3 PHS device not Check the horizontal distance

mounted properly between PHS photocell and the fin.
Error Help - 0047 ErrReleveling
0047 ErrReleveling
This section describes the Travel Control error ErrReleveling.

Summary
During a re-levelling trip the car drifts outside the re-levelling

Description tolerance of 75 mm
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check the Motor Control.
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 Try to increase the values for
during (un-) loading of car parameters J_RELEVEL,
A_RELEVEL, V_RELEVEL (
motion parameters ).
Error Help - 0048 InvldTripType
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.
Error Help - 0049 ErrFloorCTP
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.
Error Help - 0050 NoDistRelv
0050 NoDistRelv
This section describes the Travel Control error NoDistRelv.

Summary
The software detects that the car is outside the relevel zone defined
Description by 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).
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Wrong parameter values. Check the parameter for the
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'.
Error Help - 0051 ZeroParam
0051 ZeroParam
This section describes the Travel Control error ZeroParam.

Summary
A parameter used for the calculation of speed profiles is equal zero.

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check for zero parameters in
motion_para.
2 Call Ebikon.
Error Help - 0052 OverflowCTP
0052 OverflowCTP
This section describes the Travel Control error OverflowCTP.

Summary
The RAM area allocated for the calculation of the trip_plan is not
Description large 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 message
Actions
1 Increase the parameters
which 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
Error Help - 0053 NoSTR_Com
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 message
Actions
1 Check the hardware
connections.
2 Check the healthiness of the
lift bus members.
Error Help - 0054 PCT_Checksum
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.
Error Help - 0055 NoMCR_Com
0055 NoMCR_Com
This section describes the Travel Control error NoMCR_Com.

Summary
Communication with Motor Control PCB not established or lost.

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 No link between Travel Check if cable is connected to
Control and Motor Control pcb on Motor Control
(inverter) and Travel Control.
2 Check if pcb of Motor Control
is damaged.
3 Try to access the Motor
Control with CADI.
4 This will check the hardware
connection.
Error Help - 0056 CarNoStop
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 enough to
switch both contacts 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. 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.
None.
Extra Info
For internal use only

Source ID

Causes and message
Actions
1 Incorrect brake adjustment Verify brake action by
Error Help - 0056 CarNoStop
performing an emergency
stop at full speed in up
direction with empty car and
check if the car comes to rest
(the car should stop within
maximum 4 seconds). Use
brake test to measure
average deceleration rate
after emergency stop. Be
aware of possible rope slip on
traction sheave.
2 Incorrect parameter in Travel Check the value of parameter
Control 'MOVE_SHUTDOWN'
Error Help - 0057 MCR_NoStop
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 message
Actions
1 Check the serial link to Motor
Control (pcb).
2 Check the serial interface
board on Motor Control.
3 Incorrect parameter in Travel Check the value of parameter
Control 'FC_SHUTDOWN'
Error Help - 0058 SH_NoStop
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 message
Actions
1 Bad wiring Check the auxiliary contacts
of 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)
Error Help - 0058 SH_NoStop
Error Help - 0059 SingleReset
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 message
Actions
1 None.
Error Help - 0060 DoubleReset
0060 DoubleReset
This section describes the Travel Control error DoubleReset.

Summary
When two resets appears within 5 sec, the second one is logged as
Description a 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 message
Actions
1 None
Error Help - 0061 RSE1_Fault
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 message
Actions
1 Check the magnets for RSE1
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 message
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 message
Actions
Error Help - 0064 PHS_Fault
0064 PHS_Fault
This section describes the Travel Control error PHS_Fault.

Summary
The lower photocell (PHS) is not working properly.

Description Comments: The car left the fin but the PHS still reports IN_FIN, or
the car is at floor level and PHS still reports OUT_FIN, or two PHS
signals are received too close together which means that the PHS
signal is bouncing.
Comment: This error does not trigger an emergency stop. An error
detected during the trip is logged only when the car has stopped.
Therefore the trip-phase is always logged as STANDSTILL.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check the PHS connection
from the photocell to the PCB.
2 Check for undisturbed
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.
on top of the car and to the
Error Help - 0064 PHS_Fault
machine room.
Error Help - 0065 PHNR_D_Fault
0065 PHNR_D_Fault
This section describes the Travel Control error PHNR_D_Fault.

Summary
The upper photocell (PHNR_D) is not working properly.

Description Comments: The car left the fin but the PHNR_D still reports IN_FIN,
or the car is at floor level and PHNR_D still reports OUT_FIN, or two
PHNR_D signals are received too close together which means that
the PHNR_D signal is bouncing.
Comment: This error does not trigger an emergency stop. An error
detected during the trip is logged only when the car has stopped.
Therefore the trip-phase is always logged as STANDSTILL.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check the PHNR_D
connection from the photocell
to the PCB.
2 Check for undisturbed
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.
Error Help - 0065 PHNR_D_Fault
on top of the car and to the

machine room.
Error Help - 0066 NoGetAnswer
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 message
Actions
1 Check the controller
connection.
2 Check the controller.
Error Help - 0067 KUET_Fault
0067 KUET_Fault
This section describes the Travel Control error KUET_Fault.

Summary
The monitoring of the door bridging signals (feedback from relays

Description RUET and RUET1) indicates that they are not working properly. The
relays RUET and RUET1 are not switching in parallel, or RUET and
RUET1 are switching outside the door zone fin/magnet.
Comments: Both signals are transmitted via bus communication

from the car. The error does not trigger an emergency stop. An error
detected during a trip is logged only after the car has come to rest.
Therefore the trip-phase stored in the log always appears as
STANDSTILL.
This error is also generated on elevators with MOSIS system. For

detailed information about the error cause please refer to the
description of the extra information below. With MoSIS this error is
also logged when there there is a mismatch between the numbers of
floors learnt by MOSIS and by the control system.
The extra information value is a 8 digit hexadecimal number

Extra Info (0xABCDEFGH) and has to be converted/decoded into binary
format (each bit has a specific meaning).
Meaning of value 'GH' (Bit0 to Bit7):

0000 0001(bin) / 01(hex): Status of KUET and KUET1 are different
0000 0010(bin) / 02(hex): Enable UET false or outside a floor but
KUET or KUET1 is TRUE
0000 0011(bin) / 03(hex): Enable UET true and at floor but KUET or
KUET1 is FALSE
0000 0100(bin) / 04(hex): Status of KUET_20 and KUET1_20 are
different
0000 0101(bin) / 05(hex): Enable UET_20 false or outside a floor
but KUET_20 or KUET1_20 is TRUE
Additional diagnostics for MX only:
0000 0110(bin) / 06(hex): Car at floor without door on side1 but
IUET or IUET1 is true

0000 0111(bin) / 07(hex): Car at floor with door on side1 but IUET or
IUET1 is false
0000 1000(bin) / 08(hex): Car outside floor but IUET or IUET1 is
true
0000 1001(bin) / 09(hex): Car at floor without door on side20 but
IUET_20 or IUET1_20 is true
0000 1010(bin) / 0A(hex): Car at floor with door on side20 but
IUET_20 or IUET1_20 is false
0000 1011(bin) / 0B(hex): Car outside floor but IUET_20 or
IUET1_20 is true
Meaning of value 'F' (Bit8 to Bit11):

0000(bin) / 00(hex): 'KUET' false, 'KUET1' false, 'Enable UET' false
0001(bin) / 01(hex): 'KUET' true, 'KUET1' false, 'Enable UET' false
0010(bin) / 02(hex): 'KUET' false, 'KUET1' true, 'Enable UET' false
0011(bin) / 03(hex): 'KUET' true, 'KUET1' true, 'Enable UET' false
0100(bin) / 04(hex): 'KUET' false, 'KUET1' false, 'Enable UET' true
0101(bin) / 05(hex): 'KUET' true, 'KUET1' false, 'Enable UET' true
0110(bin) / 06(hex): 'KUET' false, 'KUET1' true, 'Enable UET' true
0111(bin) / 07(hex): 'KUET' true, 'KUET1' true, 'Enable UET' true
Meaning of value 'E' (Bit12 to Bit15): for TX only

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
Meaning of value 'D' (Bit16 to Bit19): for MX only

0000(bin) / 00(hex): 'IUET' false, 'IUET1' false, 'LUET' false
0001(bin) / 01(hex): 'IUET' true, 'IUET1' false, 'LUET' false
0010(bin) / 02(hex): 'IUET' false, 'IUET1' true, 'LUET' false
0011(bin) / 03(hex): 'IUET' true, 'IUET1' true, 'LUET' false
0100(bin) / 04(hex): 'IUET' false, 'IUET1' false, 'LUET' true
0101(bin) / 05(hex): 'IUET' true, 'IUET1' false, 'LUET' true
0110(bin) / 06(hex): 'IUET' false, 'IUET1' true, 'LUET' true
0111(bin) / 07(hex): 'IUET' true, 'IUET1' true, 'LUET' true
Meaning of value ‘AB’ (Bit24 to Bit31): for MoSIS only (bit decoding)
0000 0001(bin) / 01(hex): MoUET_RelaisFail is ON.
0000 0010(bin) / 02(hex): MoUET_WrongFloors is ON.
0000 0100(bin) / 04(hex): MoUET_reserve2 is ON.
0000 1000(bin) / 08(hex): MoUET_inLuet is ON.
0001 0000(bin) / 10(hex): MoUET_CmdOn is ON.

0010 0000(bin) / 20(hex): MoUET_inDoorZone is ON.
0100 0000(bin) / 40(hex): MoUET_v_below is ON.
1000 0000(bin) / 80(hex): MoUET_OK is ON.
Meaning of Value “CDEFGH” (Bit0 to Bit23): none (always '000000')
Example 1: Error 67 with extra info value h68000000 on a MoSIS
system
68 (Hex) / 01101000(bin): MoUET_inLuet and MoUET_inDoorZone
and MoUET_v_below are ON.
Example 2: Error 67 with extra info value h31000000 on a MOSIS
system:
31(Hex) / 00110001(bin): MoUET_RelaisFail and MoUET_CmdOn
and MoUET_inDoorZone are ON.
Refer to explanation for the extra info value

Source ID

Causes and message
Actions
1 Bad wiring on car Check the connection of the
RUET/RUET1 enable- and
feedback-signals to the car
interface board.
2 Check the wiring of the door
zone detection devices
(PHUET / KUET)
3 Bad environmental conditions Check photocell/magnet
(dirt, dust) in the hoistway switches on car for dirt.
4 Electrical problems Check the ground connection
on the car and the power
supply for the car interface
board and the door bridging
device (e.g. PHUET)
5 Communication problems Check the (LON) bus
between control cabinet and connection from the control
car cabinet to the car. Caution:
KUET error may indicate a
communication problem
caused by another LON node
(landings etc.)
6 Check for EMC problems

caused by Schindler or 3rd
party equipment (MX-GC:
refer to field information
No.291)
7 Configuration Check if number of floors and
shaft layout (front rear doors)
in configuration is matching
the floor vanes in the
hoistway.
MX-GC: Travel control
checks for each access is a
KUET vane is present for
front and/or rear side.
8 Mechanical problem with Check mounting of KUET
switches switches/fins
9 With MoSIS: MOSIS was Perform a learn trip.
replaced, e.g. from other
installation (learnt floors
mismatch)
Error Help - 0068 SGRB_Fault
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 message
Actions
1 Check the relay and its
auxiliary contacts
Error Help - 0069 SBNH_Fault
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 message
Actions
auxiliary contacts
Error Help - 0070 SW_Warning
0070 SW_Warning
This section describes the Travel Control error SW_Warning.

Summary
The software detected an abnormal situation which is not

Description considered to 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
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)
6A2(hex)/1698(dec): The VF has sent something wrong intentionally
or the message got corrupt.
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 message
Actions
1 Contact R&D department in
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.
Error Help - 0071 SW Error
0071 SW Error
This section describes the Travel Control error SW Error.

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

Description a 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
Extra Info trap 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 message
Actions
1 Contact R&D department in
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 software
specialist to detect the source
of the problem.
Error Help - 0072 Safety 110V
0072 Safety 110V
This section describes the Travel Control error Safety 110V.

Summary
This message was replaced with the message number 141 'Safety
Description T1' (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
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
supply is switched off if the output voltage is too high. The voltage
Error Help - 0072 Safety 110V

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 message
Actions
1 No supply voltage on the Check the power supply for
safety circuit the 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 Check the interface board and
board for safety circuit tap the connections to the safety
inputs circuit. Replace board if
necessary.
Error Help - 0073 Safety SPT
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 message
Actions
1 Open contact in safety circuit Check the corresponding
section in the safety circuit.
2 Bad wiring of contact(s) in Check wiring to and between
safety circuit contacts.
Error Help - 0073 Safety SPT
necessary.
Error Help - 0074 Safety KNE
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 message
Actions
Error Help - 0074 Safety KNE

necessary.
Error Help - 0075 Safety RTS
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
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
Error Help - 0075 Safety RTS
Causes and message

Actions
1 Bad landing door contact(s) Check switching of landing
KTS door contacts.
2 Bad wiring of landing door Check wiring to and between
contact(s) in safety circuit landing door contacts.
necessary.
Error Help - 0076 Safety End
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
Error Help - 0076 Safety End

Causes and message
Actions
1 Door contacts KTC Check switching of car door
contacts
2 Bad wiring of car door Check wiring to car door
contacts in safety circuit contacts
3 Door bridging circuit Check the door bridging
circuit
necessary.
Error Help - 0077 LM_PrintsErr
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.
Error Help - 0077 LM_PrintsErr
Source ID

Causes and message
Actions
1 Check the LMS device and
the 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
Error Help - 0078 LM_NoCommiss
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 message
Actions
1 Do the commissioning of the
load measuring device
according to the TK.
Error Help - 0079 Topt_Fault
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

Description properly. 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 message
Actions
1 Check TOPT.
Error Help - 0080 OverTempMCR
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 message
Actions
1 Check the frequency
converter for overtemperature
and check the temperature
sensors.
2 See also the event log in
Motor Control.
Error Help - 0081 TripV_Tacho
0081 TripV_Tacho
This section describes the Travel Control error TripV_Tacho.

Summary
The car position (distance) tacho failed during the trip. Travel
Description Control continues the trip to the nearest floor using the speed tacho
feedback from the inverter/motor control.
Comments: The speed tacho information is provided by Motor
Control as a handshake to each speed reference telegram (closed
loop). This information is used by Travel Control to calculate position
and speed of the car and to continue the current trip with the speed
tacho only. The car stops at the nearest floor; normal stopping
precision cannot be guaranteed. However the car will stop close
enough to the floor so that the door(s) can open normally for
passengers to leave the car.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Problem with the signal from Check the position tacho as
the position tacho well as its connection to the
interface PCB and the PCB
hardware.
2 Bad/broken wire between Check wiring
position tacho and control
cabinet
3 Faulty position tacho Replace position tacho
4 EMC problems Check for EMC interferences
Error Help - 0081 TripV_Tacho
caused by Schindler or 3rd

party equipment
Error Help - 0082 NoSupply12V
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 message
Actions
1 Check connection 12V.
2 Check emergency power
module.
Error Help - 0083 NoSupply24V
0083 NoSupply24V
This section describes the Travel Control error NoSupply24V.

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

Description PGO)
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 message
Actions
1 Check fuse 24V supply.
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
Error Help - 0084 DMS_Spoiled
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 message
Actions
1 Bad connection of strain Check the connection of the
gauge 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)
Error Help - 0085 LM_ComErr
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 message
Actions
1 Check the LMS device and
the bus connection to the
control cabinet
2 Incorrect baud rate TX4 only: Check the baud
rate adjustment on the pcb's.
Error Help - 0086 RUET_Fault
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 message
Actions
1 Check the relay RUET and
the connection of the
feedback contact to the
interface board.
2 Check if the related input of
the interface boad is broken.
Error Help - 0087 RTSC_Fault
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 message
Actions
1 Check the relay RTSC and
the connection of the
feedback contact to the pcb.
Error Help - 0088 TachoFault
0088 TachoFault
This section describes the Travel Control error TachoFault.

Summary
Major problem with the car position tacho. The position value read
Description 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.
0 (hex)/0 (dec): No signal (speed feedback) from position tacho

Extra Info when starting 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)/1 (dec): During INSPECTION or RECALL trip the car is

allowed to move for a distance of 0.5m with a faulty car 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)/10 (dec): The position value read from the position tacho is
not in the shaft range. (Absolute encoder was disconnected during
manual trip.)
B (hex)/11 (dec): same as extra info value A(hex)
C (hex)/12 (dec): The position value read from the position tacho is
inspection trip in up direction.)
D (hex)/13 (dec): same as extra info value C(hex)
E (hex)/14 (dec): The position value read from the position tacho is
inspection trip in down direction.)
Error Help - 0088 TachoFault
F (hex)/15 (dec): 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)/16 (dec): 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 message
Actions
1 Bad connection/wiring of the Check the connection of the
car position tacho. position tacho to the control
(cable).
2 The position tacho is Check position tacho itself.
damaged.
3 Mechanical problems with car Check that the tacho runs
position encoder. smoothly.
4 Position tacho disconnected. Reconnect position tacho.
Error Help - 0089 TripTimeExp
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 trip based on the maximum speed
for the selected trip type and the maximum possible travel distance
(HQ) and uses the calculated value to monitor the trip (if the
maximum travel distance is not known the parameter
'MAX_TRIP_TIME' is used instead).
Extra info values in aabbccdd(hex) format are

Extra Info
aabb(hex): Runtime limit in seconds. To calculate the runtime limit
swap the hex. values for 'aa' and 'bb' ('bbaa') then convert to
decimal (see example below).
cc(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.
dd: The trip type of the trip for which the error is reported. Values
are:
Trip Type dd (value in Hex)
UNDEFINED_TRIP 00
INSPECTION_UP 01
INSPECTION_DOWN 02
RECALL_UP 03
RECALL_DOWN 04
Error Help - 0089 TripTimeExp
INSP_CAR_UP 05
INSP_CAR_DOWN 06
UPPER_ACCESS_UP 07
UPPER_ACCESS_DOWN 08
LOWER_ACCESS_UP 09
LOWER_ACCESS_DOWN 0A
LEARN_DRV 0B
SYNCH_DRV 0C
NORMAL_DRV 0D
RELEVEL_DRV 0E
NO_TRIP_DRV 0F
RAMP_UP_DRV 10
RAMP_DOWN_DRV 11
Example: Extra info = 2C01000B

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

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

Summary
In the US and Canada, Firefighter Service (JBF) includes a relay

Description which jumps out the stop switch inside the cab while the cars are
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
Error Help - 0091 SMPB_Fault
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 message
Actions
auxiliary contacts on Travel
Control.
Error Help - 0092 IVXVF_HW_Fault
0092 IVXVF_HW_Fault
This section describes the Travel Control error IVXVF_HW_Fault.

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

Description (uncontrolled activation of relays or bad status of inputs). Check
extra info for detailed description of possible cause.
See also error #135
0 (hex)/ 0 (dec): All relays controlled by Travel Control are active

Extra Info unintentionally
A (hex)/ 10 (dec): DRH-U button on the recall panel is pressed

without 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
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

JREC / DREC-D
16 (hex)/ 22 (dec) DREC-E button on the inspection panel is

JREC / DREC-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 must be released before a new trip is initiated.
18 (hex)/ 24 (dec) DREC-D button pressed for more than 30

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
32 (hex)/ 50 (dec): 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)/ 51 (dec): 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)/ 52 (dec): 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)/ 92 (dec): 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)/ 93 (dec): 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)/ 100 (dec): 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)/ 333 (dec): 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 message
Actions
1 Handling problem (wrong none
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 HW fault 1) Check wiring
2) Check function of I/Os'
(refer to extra info)
3) Replace the pcb (IVXVF /
GCIO) if necessary
4 Jumper in safety circuit Remove jumper
5 Extra info 14D (hex)/ 333 If ASIXA 33 PCBA, the
(dec): LDBCS plug in operation with LDBCS needs
BYPASS position and JRH that JRH is switched ON
switch not activated(only for before LDBCS plug is put on
MX-GC) BYPASS position
Error Help - 0093 AccessSwitch
0093 AccessSwitch
This section describes the Travel Control error AccessSwitch.

Summary
NA only: The Access relay is switched on and the selected trip type
Description is 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 message
Actions
1 Wrong parameter values Check the value for the
parameters 'UPPER
ACCESS FLOOR' and
'LOWEST FLOOR'.
2 Shaftinfo ACCESS Check the connection and the
wiring to the corresponding
pcb
Error Help - 0094 DoorLockFault
0094 DoorLockFault
This section describes the Travel Control error DoorLockFault.

Summary
The control checks if the door state (open) matches with the
Description information read from the safety circuit (KTS and KTC). The safety
circuit shows closed/locked shaft or car door (taps ISKT4 or ISKT5
on) while the door status is 'open'. With TX-GC2 the control can
detect whether a KTS opened on the front side or the rear side
because the contacts operate the relays RTS and 2RTS.
Together with this error a SW_Warning (error #70) may be logged
which provides additional information for diagnostics. For the
description of the extra information in the SW_Warning see
description here.
5(hex)/5(dec): Retiring cam (RCAM) activation error

Extra Info 6(hex)/6(dec): Retiring cam (RCAM) release error
28(hex)/40(dec): Monitor status of safety circuit (bridged contacts)
29(hex)/41(dec): Monitor status of safety circuit (bridged contacts)
2A(hex)/42(dec): Shaft Door Contact (KTS) bypassed
2B(hex)/43(dec): Car Door Contact (KTC) bypassed (KOREA)
940(hex)/2368(dec): Shaft Door Contact (KTS) bridged in safety
circuit
941(hex)/2369(dec): Car Door Contact (KTC) bridged in safety
circuit
942(hex)/2370(dec): Door side 1 open and inconsistend state of
KTC/KTS (TX-GC2)
943(hex)/2371(dec): Door side 2 open and inconsistend state of
KTC2/KTS2 (TX-GC2)
944(hex)/2372(dec): Door lock problem during trip preparation (TX-
GC2)
945(hex)/2373(dec): Door lock problem during trip preparation (MX-
GC/TX-GC)
Description of the extra information value for the message

SW_Warning (70) sent together with error'Door Lock Fault' with
extra info value 942(hex):
80(hex) /128(dec): Incorrect status of sdoor coil - coil of shaft door

lock relay (NA)
40(hex) /64(dec): Incorrect status of sdoor contact - contact of shaft
door lock relay (NA)
20(hex) /32(dec): Incorrect status of cdoor coil - coil of car door lock
relay (NA)
10(hex) /16(dec): Incorrect status of cdoor contact - contact of car
door lock relay (NA)
08(hex) /8(dec): Incorrect status of rtscon - shaft door safety 1 input
(EUAP)
04(hex) /4(dec): Incorrect status of rts1con - shaft door safety 2
input (EUAP)
02(hex) /2(dec): Incorrect status of rtccon - car door safety 1 input
(EUAP)
01(hex) /1(dec): Incorrect status of rtc1con - car door safety 2 input
(EUAP)
Description of the extra information value for the message

SW_Warning (70) sent together with error'Door Lock Fault' with
extra info value 943(hex):
80(hex) /128(dec): Incorrect status of sdoor_coil_20 - coil of shaft
door lock relay for rear door (NA)
40(hex) /64(dec): Incorrect status of sdoor_contact_20 - contact of
shaft door lock relay for rear door (NA)
20(hex) /32(dec): Incorrect status of cdoor_coil_20 - coil of car door
lock relay for rear door (NA)
10(hex) /16(dec): Incorrect status of cdoor_contact_20 - contact of
car door lock relay for rear door (NA)
08(hex) /8(dec): Incorrect status of rtscon_20 - rear shaft door safety
1 input (EUAP)
04(hex) /4(dec): Incorrect status of rts1con_20 - rear shaft door
safety 2 input (EUAP)
02(hex) /2(dec): Incorrect status of rtccon - car door safety 1 input
(EUAP)
01(hex) /1(dec): Incorrect status of rtc1con - Incorrect status of car
door safety 2 input (EUAP)
104(dec): Monitor
114(dec): Prepare trip

Causes and message
Actions
1 Problem with the door Check the door contacts and
contacts the wiring to the door
interface board.
2 Safety chain Check for jumpers in the
safety chain.
3
4
Error Help - 0095 ETSL_Overspeed
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. 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 message
Actions
1 Wrong parameter values Check the values for
parameters A2 (acceleration)
and A6 (deceleration).
2 Other drive system error Check the operation of the
drive system.
Error Help - 0096 ETSL_VaneError
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.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Wrong alignment between Check the alignment.
PHVKSE and vanes/metal
stripe.
2 Deformed or twisted metal Check the tension of the
stripe in the hoistway metal stripe.
3 A gap in the check track Cover the gap with something
without a measure vane in that interrupts IR-light. A
front of it. single 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
Error Help - 0096 ETSL_VaneError
cloth.
Error Help - 0097 ETSL_DeviceError
0097 ETSL_DeviceError
This section describes the Travel Control error ETSL_DeviceError.

Summary
Unsafe operating condition detected by the ETSL device (internal

Description error).
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Internal error of PHVKSE Cycle power (off/on) on the
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
Error Help - 0097 ETSL_DeviceError
etc.)
Error Help - 0098 COM_Busreconf
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 message
Actions
1 bus is faulty Check lift -, groupbus if all
links 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 order to determine the source
of 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.
Error Help - 0099 RSK_Fault
0099 RSK_Fault
This section describes the Travel Control error RSK_Fault.

Summary
Problem with feedback of relays RSK / RSK1 (malbehaviour of

Description relay).
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Faulty feedback contact of Check wiring and/or
the relays RSK / RSK1 functionality of relays RSK /
RSK1.
2 RSK/RSK1 does not drop off Replace relays RSK/RSK1 or
as expected pcb which holds the relays.
3 RSK/RSK1 does not turn on Check the safety circuit
during trip preparation as (ISKT4 & ISKT5).
expected
Error Help - 0100 RFE_Fault
0100 RFE_Fault
This section describes the Travel Control error RFE_Fault.

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

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

Causes and message
Actions
1 RFE is turned on and does Check the wiring and the
not pick up within 5 seconds functionality of RFE.
(Timeout)
2 Check all contacts/contactors
in the RFE circuit.
3 RFE does not turn off Check RSPFE.
4 TX4: Wrong parameter Check the Travel Control -
'System Type' Elevator parameter 'System
Type' (TX4 only).
Error Help - 0101 RTRT_Fault
0101 RTRT_Fault
This section describes the Travel Control error RTRT_Fault.

Summary
The software monitors the state of the relay RTRT (feedback

Description contact 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 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

Causes and message
Actions
1 Bad wiring of relay RTRT or Check the wiring and the
relay broken functionality of relay RTRT.
Error Help - 0102 RKUET_Fault
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 message
Actions
1 Malfunction of door bridging Check the operation of
RKUET.
2 Check KUET / KUET1 and
RUET / RUET1.
Error Help - 0103 HighSpeedStop
0103 HighSpeedStop
This section describes the Travel Control error HighSpeedStop.

Summary
For SSDC drives only: Emergency stop when the car was moving
Description with 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 message
Actions
1 none
Error Help - 0104 CDOOR Bypass
0104 CDOOR Bypass
This section describes the Travel Control error CDOOR Bypass.

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

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

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

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

None.
Extra Info
None.
Source ID

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

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

Causes and message
Actions
1 none
Error Help - 0107 Pit Oil Switch
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 message
Actions
1 Oil leakage check and fix
Error Help - 0108 Over Temperature Oil
0108 Over Temperature Oil
This section describes the Travel Control error Over Temperature

Summary Oil.
Oil temperature sensor reads above 55 degrees C. (Hydro only)

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 none
Error Help - 0109 KSE Failure
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 message
Actions
1 none
Error Help - 0110 Motor Overload
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 message
Actions
1 none
Error Help - 0111 No Floor Slowdown
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
Error Help - 0111 No Floor Slowdown

Causes and message
Actions
1 none
Error Help - 0112 Pressure Switch
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
Error Help - 0113 Thermistor Failure
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 message
Actions
1 Broken sensor replace sensor.
2 Low oil level refill oil.
Error Help - 0114 Anti Stall Failure
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 message
Actions
1 none
Error Help - 0115 Duty Cycle Regulation
0115 Duty Cycle Regulation
This section describes the Travel Control error Duty Cycle

Summary Regulation.
not used
Description
None
Extra Info
None.
Source ID

Causes and message
Actions
1 none
Error Help - 0116 KLU Fault
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.
Error Help - 0116 KLU Fault
None.
Source ID

Causes and message
Actions
1 none
Error Help - 0117 KLD Fault
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.
Error Help - 0117 KLD Fault
None.
Source ID

Causes and message
Actions
1 none
Error Help - 0118 NodeAlive
0118 NodeAlive
This section describes the Travel Control error NodeAlive.

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

Causes and message
Actions
1 none
Error Help - 0119 Node Dead
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 message
Actions
1 none
Error Help - 0120 Door Lock Failure
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.
Description (for Hydro only)
The extra info shows the floor number (not the floor name) the car
Extra Info was closest to when it happened.
None.
Source ID

Causes and message
Actions
1 none
Error Help - 0121 Switch Fault
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 ).
of JLB (hoistway door bypass switch ).
of 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
JREC (Top of Car Inspection switch ).
C Hex(12 Dec): The normally open and normally closed contacts of
JRECC (In Car Inspection switch ).
Error Help - 0121 Switch Fault
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
Error Help - 0122 KSE Fail 2
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 message
Actions
1 none
Error Help - 0123 EV Error
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
Error Help - 0123 EV Error
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 message
Actions
1 none
Error Help - 0124 EV Shutdown
0124 EV Shutdown
This section describes the Travel Control error EV Shutdown.

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

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 message
Actions
1 none
Error Help - 0125 EV Event
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. Replace Dynahyd software chip. Replace CRIPEV board.
None.
Source ID
Error Help - 0126 Wrong hardware
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
Error Help - 0127 MoSis_Error
0127 MoSis_Error
This section describes the Travel Control error MoSis_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 message
Actions
1 Wrong hardware Check hardware (interface
configuration (extra info: 0) boards)
2 Mismatch (extra info: 1) Do a learn/measuring trip.
Error Help - 0128 LOWER_KSE_LOW_SYNCH
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
Description trip,its 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 message
Actions
1 1. PHS not connected Check the PHS signal. If PHS
is not connected (always
IN_FIN) this event will
appear.
2 2. Incorrect shaft information Check the KSE signal
wiring).
Check that the PHS photocell
works properly and is
mechanically in the right
position.
Error Help - 0129 EQ_Midpoint_Fault
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 message
Actions
1 The lift has a collision switch Park the car where the car
(counterweight derailment and counterweight
switch) but the midpoint is not crossheads are even, and
set. The control will only use the "set EQ midpoint"
switch to automatic operation function on CADI or SMLCD.
after the midpoint is set and
valid.
Error Help - 0130 PCT_Drive_Para
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
Description current 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 message
Actions
1 A PCT has been downloaded Download PCT with correct
with a wrong parameter value or modifiy parameter to
value, 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.
Error Help - 0131 MoSis_KNE_Fault
0131 MoSis_KNE_Fault
This section describes the Travel Control error MoSis_KNE_Fault.

Summary
Message sent by MoSis together with status change of KNE relay.

Description
The extra information is a 8 digit code with the following meaning

Extra Info per digit:xSTUVWXYZ
S=0: KNE relay closed (normal)

S=1: KNE relay open (reason for opening see other digits)
T=_: RESERVED FOR FUTURE USE
U=1: KNE open because of detection of unintended car movement
V=1: MoSis nternal hardware or software error relating to the KNE.
Check the error-log (MoSis) for further info.
W=1: Relay test failure (KneRelayFail)
X=1: Car travelled past the end of the known shaft range
(StrangePlace). MoSis was never at this position before (past the
last floor).
Y=1: Travel past last known floor (Overtravel)
Z=1: Pre-commissioned state; no floors discovered (Precom)
None.
Source ID
Error Help - 0132 MoSis_ETSL_Fault
This section describes the Travel Control error MoSis_ETSL_Fault.

Summary
Message from MoSis together with status change of ETSL relay.

Description
The extra information is a 8 digit hexadecimal code with the

Extra Info following meaning per digit: STUVWXYZ
S=0: ETSL relay closed (normal)

S=1: ETSL relay open (reason for opening see other digits)
T=_: RESERVED FOR FUTURE USE
U=1: NTSD overspeed.
V=1: MoSis internal hardware or software error relating to the ETSL.
Check the error-log (MoSis) for further info.
W=1: Relay test failure (EtslRelayFail)
X=1: Commissioned speed exceeded (MaxSpeed).
Y=1: Pre-commissioned limit of 1m/s exceeded (1mps)
Z=1: Exceeded ETS/ETSL curve towards terminal (Curve)
None.
Source ID
Error Help - 0133 Inverter Para Not Accepted
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 message
Actions
1 Value of the drive parameter Check and correct the value
is out of range or incorrect. of the rejected parameter or
reinitialize the inverter.
Error Help - 0134 NTSD_Triggered
0134 NTSD_Triggered
This section describes the Travel Control error NTSD_Triggered.

Summary
This error is generated when the NTSD (normal terminal slowdown)

Description monitoring detects that the car speed is above the speed limit
calculated from the car position and the limiting deceleration rate
defined with the parameters A_NTSD [where parameter
'ETSL_TYPE' is set to 'MoSis_ETSL_NTSD']. When the NTSD is
triggered 2 times in 1000 trips, a warning is sent. 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 system is blocked
permanently. The total error count keeps accumulating until reset.
The error type reported is not dependant on time, but on the number
of trips that the elevator does.
None
Extra Info
None
Source ID

Causes and message
Actions
1 Elevator moves too fast Check the value of the
towards the shaft end (top or parameter 'A_NTSD'. The
bottom) value shall be between
0.8m/s2 and 1.4m/s2
Error Help - 0135 DREC_DRH_button
0135 DREC_DRH_button
This section describes the Travel Control error DREC_DRH_button.

Summary
The monitoring of inputs in Travel Control detects abnormal status

Description (bad status of inputs). Check extra info for detailed description of
possible 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

Extra Info without 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
14( hex)/20 (dec): DREC-U button on the inspection panel is

JREC / DREC-U
15 (hex)/21 (dec): DREC-D button on the inspection panel is

JREC / DREC-D
16 (hex)/22 (dec) DREC-E button on the inspection panel is pressed

without active inspection control JREC; check wiring of JREC /
DREC-E.
17 (hex)/23 (dec) DREC-U button pressed for more than 30

18 (hex)/24 (dec) DREC-D button pressed for more than 30

Error Help - 0135 DREC_DRH_button
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 message
Actions
1 Handling problem (wrong none
manipulation on recall- or
inspection panel)
Error Help - 0136 Safety Bypass
0136 Safety Bypass
This section describes the Travel Control error Safety Bypass.

Summary
Error detected by the monitoring for the bypass circuit of the safety
Description circuit. For Fire Recall and Firefighter Operation in Korea parts of
the safety circuit (pit, emergency exit, and door contacts) is bridged
by the control.
0x01: Status of relay RUESG does not match status of KUESG, or

Extra Info the feedback KUESG did not switch as expected within 2secs
tolerance.
0x02: Status of relay RUENA does not match status of KUENA, or
the feedback KUENA did not switch as expected within 2secs
tolerance.
0x03: Status of relay RUESG does not match status of KUETFF, or
the feedback KUETFF did not switch as expected within 2secs
tolerance.
0x04: status of KUETFF does not match the supplementary input
KUETFF1. Same for RUESG and RUENA.
None.
Source ID

Causes and message
Actions
1 Faulty interface Replace corresponding pcb
Error Help - 0137 JHCC_Pressed
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 message
Actions
1 None
Error Help - 0138 Brake Not Set
0138 Brake Not Set
This section describes the Travel Control error Brake Not Set.
Summary
After a normal (automatic) trip the brake does not close as expected
Description (status of KB contacts shows open brake) after the 'brake off'
command timeout following the 'SB off' command. In this critical
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). With closed doors the inverter is switched
off and the elevator is blocked permanently with fatal error. 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.
ndef
Extra Info
None.
Source ID

Causes and message
Actions
1 Brake does not close due to Check brake for correct
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
Error Help - 0139 Unintended Car Movement
0139 Unintended Car Movement
This section describes the Travel Control error Unintended Car

Summary Movement.
Mosis detects an unintended car movement. The unintended

Description movement detection device opens the safety circuit. 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 (Amendm.10) / Korean Code. (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.
not used
Extra Info
None.
Source ID

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

Summary
The safety circuit opened before the tap (ISKT4B) but after the
Description previous tap (ISKT4). This safety circuit tap is only available on
specific hardware (e.g. LONICK).
Extra Info
development only.
None.
Source ID

Causes and message
Actions
KTS door contacts.
3 Faulty input on interface Check the interface board
board for safety circuit tap (LONICK) and the
inputs connections to the safety
circuit. Replace board if
necessary.
Error Help - 0141 Safety T1
0141 Safety T1
This section describes the Travel Control error Safety T1.

Summary
The safety circuit opened before the first tap (ISKT1). Problem with
Description 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
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
supply is switched off if the output voltage is too low. The voltage
03: Safety circuit output voltage too high. In the event of a HW
supply is switched off if the output voltage is too high. The voltage
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 message
Actions
1 No supply on the safety Check the power supply for
circuit the safety circuit.
2 In case of regulated voltage
suppy: Reset short circuit
protection for safety circuit
supply.
3 Relais RKPH Check the phase control relay
RKPH (if available).
necessary.
0142 Safety T2

Summary
The safety circuit opened before the second tap (ISKT2) but after
Description the first tap (ISKT1).
Extra Info
development only.
None.
Source ID

Causes and message
Actions
necessary.
Error Help - 0143 Safety T2A
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
Description tap (ISKT1).
Extra Info
development only.
None.
Source ID

Causes and message
Actions
necessary.
0144 Safety T2B

Summary
Description previous tap (ISKT2A).
Extra Info
development only.
None.
Source ID

Causes and message
Actions
necessary.
0145 Safety T3

Summary
The safety circuit opened before the third tap (ISKT3) but after the
Description second tap (ISKT2).
Extra Info
below).

None.
Source ID

Causes and message
Actions
necessary.
0146 Safety T3A
This section describes the Travel Control error Safety T3A.

Summary
The safety circuit opened before the tap (ISKT3A) but after the
Description previous tap (ISKT2).
Comments: Downward safety circuit tap inputs (ISKT3B etc.) will not
Extra Info
below).

None.
Source ID

Causes and message
Actions
necessary.
0147 Safety T3B

Summary
Description previous tap (ISKT3A).
Extra Info
below).

None.
Source ID

Causes and message
Actions
necessary.
0148 Safety T4

Summary
Used for the monitoring of the landing door contacts KTS. The
Description safety circuit is open before the fourth tap (ISKT4) but after the third
tap (ISKT3). The message is logged if:
a) the safety circuit opens during a trip due to a landing door contact
(any) which opens unexpectedly.
b) the safety circuit does not close as expected after the door has
closed.
Comments: Downward safety circuit tap input (ISKT5) will not create
corresponding error message. Refer also to wiring diagram for
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 message

Actions
KTS door contacts KTS.
necessary.
0149 Safety T5

Summary
Used for the monitoring of the car door contact(s) KTC. The safety
Description circuit is open before the fifth tap (ISKT5) but after the fourth tap
(ISKT4). The message is logged if:
a) the safety circuit opens during a trip due to a car door contact
(front or rear) which opens unexpectedly.
closed.
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 message
Actions
1 Door contacts KTC Check switching of car door
contacts
2 Bad wiring of car door Check wiring to car door
contacts in safety circuit contacts
3 Door bridging circuit Check the door bridging
circuit
necessary.
Error Help - 0151 LearnTrip
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/150_199_Variodyn_E/err_0151_en.htm[29.6.2010. 17:07:26]
Error Help - 0152 CorrTrip
0152 CorrTrip
This section describes the Variodyn E error CorrTrip.

Summary
A correction trip has been started

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

Summary
A synchronisation trip has been started

None.
Extra Info
None.
Source ID
Error Help - 0154 KS_MagnetPos
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
Error Help - 0155 KSE_MagnetPos
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
Error Help - 0156 LearnMesProbl
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
Error Help - 0157 DeltaS_2BP
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 message
Actions
1 Possible error causes Actions to be taken
2 Inaccurate parameter setting Check frequency converter
(frequency converter) drive parameter
Error Help - 0158 SF_Fault
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 message
Actions
1 Open safety circuit Check safety circuit
2 Check auxiliary contacter of
SF and SF1
Error Help - 0159 NoBpReaction
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 message
Actions
1 Check wiring PGO-frequency
converter
2 Check frequency converter
ER113 module
Error Help - 0160 SK ErrorStart
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
Error Help - 0161 CarNotAtLevel
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 message
Actions
1 Inaccurate setting of Check frequency converter
frequency converter parameters
parameters
Error Help - 0162 CarOutOfFloor
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 message
Actions
1 Trip interruption caused by Check wiring PGO-frequency
frequency converter converter
Error Help - 0163 TargetFailure
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
Error Help - 0164 FC_ShortBrake
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 message
Actions
1 Inaccurate parameter setting Check (and adjust if
(frequency converter) necessary) frequency
converter parameter
Error Help - 0165 FC_StopSpeed
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 message
Actions
1 Malfunction of frequency Check wiring to frequency
converter converter
2
Error Help - 0166 SW_BlockPerm
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 message
Actions
1 Solve the problem and reset
the system
2 RAM data destroyed Double-reset PGO
3 ROM data destroyed Call EBI for software
replacement
4 Double-reset PGO
5
Error Help - 0167 LastBlockTime
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
Error Help - 0168 ShaftChecksum
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
Error Help - 0169 Supply24V
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
Error Help - 0170 FloorPrec
0170 FloorPrec
This section describes the Variodyn E error FloorPrec.

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

Description Inaccurate 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 message
Actions
1 Elevator system improperly Improve elevator adjustment
adjusted
2
Error Help - 0171 InvDrivePCT
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
Error Help - 0171 InvDrivePCT

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

Summary
Parameter values stored in the frequency converter (BARMAG

Description ER113) 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 message
Actions
1 Communication PGO Check RS232 connection
frequency converter not PGO frequency converter
successful/impossible
2 Communication PGO Perform double-reset on
frequency converter had been PGO and reset on frequency
interrupted converter, wait approx. 5
minutes (!)
Error Help - 0201 ConfigErr
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 message
Actions
1 Wrong position of ID switch Check switch setting and
on door-/car-interface board verify.
2 Configuration data not TX4: Check lift bus
received or data corrupted connection to controller.
3 Check if configuration data is
loaded on the controller.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/200_299_Door_Control/err_0201_en.htm[29.6.2010. 17:07:36]
Error Help - 0202 DoorOperErr
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.
01: KET-O and KET-S are active at the same time (illegal status)
Extra Info 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-
feedabck (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
None.
Source ID

Causes and message
Actions
1 Extra info 1,2,3 Check the door contacts KET-
O, KET-S and the related
wiring
2 Check if the end position can
be reached mechanically
3 Check for dirty door guides.
4 Extra info 4,5 Check the connections to the
Error Help - 0202 DoorOperErr
door drive
5 Replace the interface board
6 Extra info 6 Check the door drive board
and connections (fuse and
power supply).
7 Check the physical door parts
(V-belt)
8 Extra info 7 For manually-operated or
semi-automatic doors check if
the landing door is closed.
9 Check the landing door
contacts and wiring.
10 Extra info 8 Check if electrical phase
sequence is wrong.
11 Check if VST-O/VST-S or
wiring is mixed up
Error Help - 0203 ThermoDoorMot
0203 ThermoDoorMot
This section describes the Door Control error ThermoDoorMot.

Summary
Thermal protection device of the door motor indicates excessive

Description 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.
For door drives with inverter (e.g. IDD, SEMATIC) the error is
logged when the doorinverter is blocked due to a severe error
detected by the inverter software. In this situation the door is no
longer able to operate.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Jammed door / excessive Check the mechanical door
torque drive and the door for smooth
operation
2 Problem on door drive / Check the door inverter
inverter
Error Help - 0204 DoorRevDevErr
0204 DoorRevDevErr
This section describes the Door Control error DoorRevDevErr.

Summary
Door reversing device error. The error is generated by the door

Description control 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.
01: DT-O is permanently active.

Extra Info 02: RPHT is permanently active.
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 message
Actions
1 Damaged or badly adjusted Check the function of the
reversing device reversing device
2 Bad connection or faulty input Check the connection from
on interface board on car (e.g. the interface board to the
PIOC/ICE/TIC/LONIBV/LONIC reversing device. Replace
etc.) interface board.
Error Help - 0205 DoorContrErr
0205 DoorContrErr
This section describes the Door Control error DoorContrErr.

Summary
Door control error. The status of one of the 24VDC car interface
Description board 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 message
Actions
1 Defective output or short Check the wiring of the
circuit output.
2 Replace interface board on
car.
Error Help - 0206 DoorBoltErr
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 message
Actions
1 Locking contact not Check the locking mechanism
functioning and the locking contact.
2 Check the wiring of the
locking device (motor /
magnet).
Error Help - 0207 CloseSeqErr
0207 CloseSeqErr
This section describes the Door Control error CloseSeqErr.

Summary
Door close sequence error. The error is generated by the door

Description control 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.
meaning of value:
Extra Info 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 message
Actions
1 Damaged or badly adjusted Check the reversing devices.
reversing device
2 Bad connection or faulty input Check the connection from
on interface board on car (e.g. the interface board to the
PIOC/ICE/TIC/LONIBV/LONIC reversing device. Replace
etc.) interface board.
Error Help - 0208 DoorDevErr
0208 DoorDevErr
This section describes the Door Control error DoorDevErr.

Summary
Door device error. Door control malfunction. See extra info for
Description details.
Identifies the causing component:

Extra Info
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.
None.
Source ID

Causes and message
Actions
1 Faulty device Examine the device and
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.
5 Check wiring of JHCT.
6 Extra Info = 4 Check the power supply on
the door driver pcb (fuse).
7 Extra Info = 5 Check LON bus to door
interface board.
8 Check LON node and its
rotary switch settings.
Error Help - 0208 DoorDevErr
9 Check LON bus to other

nodes. (remove for test)
10 Check pcb EBLON.
Error Help - 0209 DoorContact
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.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Faulty RTS device Examine the device and if
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
Error Help - 0210 Lift Guardian
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
Description trip.
1 = the car light is off or flickers

Extra Info - Warning after 3 trips with car light flickering
- Error after 3 trips with the car light permanently off
2 = 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 message
Actions
1 Car light is defective Check the lamp, light network,
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

None.
Source ID

Causes and message
Actions
1 Bus is faulty Check lift-, groupbus; all
links 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

disappears.
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
supplier hotline or the VX-
Center.
Error Help - 0240 SW-Warning
0240 SW-Warning
This section describes the Door Control error SW-Warning.

Summary
The software detected an abnormal situation which is not

Description considered to 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 message
Actions
1 Various Contact the R&D department
in Ebikon if no details about
the cause of the message is
provided in the help here.
Please report all the values
logged in the error/event log.
Also include information about
the occurrence rate if
possible. These are clues for
Error Help - 0240 SW-Warning
the software specialist to

detect the source of the
problem.
2
Error Help - 0300 CTR_PAR_ACCESS
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 message
Actions
1 1. A parameter is not defined 1. Check the validity of
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/300_399_Varidor70_Door_Drive/err_0300_en.htm[29.6.2010. 17:07:42]
Error Help - 0300 CTR_PAR_ACCESS
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
Error Help - 0301 CTR_CALC
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 message
Actions
1 1. An Attempt to set an 2. Reset the door controller
unknown mode was done
Error Help - 0302 TRC_PAR_ACCESS
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 message
Actions
1 1. Parameter not defined or 1. Check validity of parameter
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.
Error Help - 0302 TRC_PAR_ACCESS
Error Help - 0303 TRC_POS_ERR
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 message
Actions
1 1. Referencing Not done 1. Power off and on the door
properly and do a referencing trip
2 2. Resolver is loosely cabled 1. Try reconnecting the cables
or 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
Error Help - 0303 TRC_POS_ERR
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
Error Help - 0304 TRC_CALC
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
Extra Info trip 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 message
Actions
1 Trip calculation fails Reboot the door
Error Help - 0305 OS_CYCLE_OVERRUN
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 message
Actions
1 CPU load exceeds 100% Inform EBI about the Problem
Error Help - 0306 PAR_NOVRAM_MISSING
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 message
Actions
1 1. No access to Flash 1. Reset the Door Controller
Memory 2. Change the Door Controller
PCB and boot the door again.
2 2. Flash Memory is gone bad 1. Reset the Door Controller
2. Change the Door Controller
PCB and boot the door again.
Error Help - 0307 HW_PAR_ACCESS
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

Extra Info motion. 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 message
Actions
1 1. Invalid Parameter Values 1. Check the valdity of the
parameters described in the
error description
2 2. Cannot Access Parameters 1. Reset the Door Controller
Error Help - 0307 HW_PAR_ACCESS
2. Replace the Door

Controller PCB
3 3. Flash is gone bad 1. Reset the Door Controller
2. Replace the Door
Controller PCB
Error Help - 0308 HW_POSITION
0308 HW_POSITION

Summary HW_POSITION.

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
Extra Info the 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 message
Actions
1 1. Current Position Counter 1. Check the drive motor
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
Error Help - 0309 HW_POSREF
0309 HW_POSREF

Summary HW_POSREF.

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 message
Actions
1 1. Position Sensor Unit cable 1. Check the cable for
is disconnected or loose damage.
2. Disconnect and Reconnect
the cable
2 2. Position Sensor Unit is 1. Replace Position Sensor
gone bad Unit
Error Help - 0310 HW_DRV_SERIOUS
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
Extra Info problem with the Drive Motor or the Drive Frequency
Convertor(Inverter)
This error is generated from the Drive

Source ID

Causes and message
Actions
1 1. Motor or frequency 1. Check the door drive
converter error system, motor and
mechancial parts
2. Reset the Door Controller
2 2. Overheating/overloading of 1. Refer to Cause/Action list
the door drive of DRIVE_OVER_TEMP
Error Help - 0311 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

Extra Info for a 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 message
Actions
1 1. Drive overload 1. If the overlaoding is not a
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
Error Help - 0311 DRIVE _OVER_TEMP
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
Error Help - 0312 HW_FLASH_READ
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 message
Actions
2. Change the Door Controller
PCB
Error Help - 0313 HW_FLASH_WRITE
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 message
Actions
2. Replace the Door
Controller PCB
Error Help - 0314 HW_WATCHDOG
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 message
Actions
1 1. Watchdog caused a reset, None
the reasons are explained in
the Error Description above
2 2. Errors in Peripheral units None
can cause seld resets to
reactivate the Peripherals
Error Help - 0315 IAC_MOD_UPD_FAIL
0315 IAC_MOD_UPD_FAIL

Summary IAC_MOD_UPD_FAIL.

Description Unable to update the Speed Mode in the Trip Curve Generator.
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.

Source ID This error is generated from only one location.

Causes and message
Actions
1 1. Invalid Door Mode in the 1. Check the debug logs
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"
Error Help - 0315 IAC_MOD_UPD_FAIL
is also accompanied with this

error, consider replacing the
door controller
Error Help - 0316 IAC_PAR_UPD_FAIL
0316 IAC_PAR_UPD_FAIL

Summary IAC_PAR_UPD_FAIL.

Description Unable to access the parameters in the IAC
motions
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

Source ID Modules

Causes and message
Actions
1 1. Paremeters not correct 1. Check validity of the
described parameters
2 1. Flash is not working 1. Reset the Door Controller
properly or gone bad 2. Replace Door Controller
Error Help - 0316 IAC_PAR_UPD_FAIL
Error Help - 0317 IAC_UNKNOWN_LEVEL
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

Extra Info SW 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 message
Actions
1 1. Unknown floor info a door 1. Check the debug logs
command 2. Reset the Door Controller
2 2. Incorrect LONV70 1. Connect CADI-GC to the
Firmware 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
Error Help - 0318 IAC_DOOR_TYPE_UNKNOWN
0318 IAC_DOOR_TYPE_UNKNOWN

Summary IAC_DOOR_TYPE_UNKNOWN.

Description Door type is not known/incorrect from the parameters.
motions
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 message
Actions
1 1. Incorrect Parameter 1. Check the parameters and
the actual door type
Error Help - 0319 IAC_CLUTCH_FAILURE
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 message
Actions
1 1. Too Less timeout value 1. Increase the timout value,
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
Error Help - 0319 IAC_CLUTCH_FAILURE
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
Error Help - 0320 ESTIMATED_CONSTRUCT_DATA
0320 ESTIMATED_CONSTRUCT_DATA

Summary ESTIMATED_CONSTRUCT_DATA.
Reserve
Description
None
Extra Info
None.
Source ID
Error Help - 0321 ESK_INTERNAL
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

Extra Info state. This is an internal SW error.
This error is generated from ESK State Machine

Source ID

Causes and message
Actions
1 1. Internal ESK SW error 1. Reset the Door Controller
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.
Error Help - 0322 ESK_PARAM_WRITE
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 message
Actions
2. Replace the Door
Controller 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
Error Help - 0323 ESK_PARAM_READ
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 message
Actions
2. Replace the Door
Controller 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
Error Help - 0324 ESK_COMMUNICATION_ERR
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 message
Actions
1 1. ESK HW is gone bad 1. Reset the Door Controller
2. Check the ESK HW
2 2. ESK Cables 1. Check the ESK Cables and
connectors
2. Consider Shielding the
cables for short circuits.
Error Help - 0325 VLON_INTERNAL
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

Extra Info create 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 message
Actions
1 1. LON Firmware not valid 1. Check the validity of the
LON Firmware version via
CADI GC
2. Update the LON Firmware
to valid version
2 2. LONV70 Card has gone 1. Reset the Door Controller
bad 2. Replace the LONV70 card
3 3. OS Problem with memory 1. Reset the Door Controller
Error Help - 0326 VLON_TRANSMIT
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

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

Source ID

Causes and message
Actions
1 1. Memory Problems wiht OS 1. Reset the Door Controller
2 2. LON Firmware is not 1. Check the validity of the
correct version of the LON firmware
on the LONV70 via CADI-GC
3 3. LONV70 Card is gone bad 1. Replace the LONV70 card
Error Help - 0327 VLON_RECEIVE
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 message
Actions
1 1. Memory Problems 1. Reset the Door Controller
2 1. LON Firmware is not OK 1. Check the validity of the
LON Firmwaer via CADI-GC
if required
3 2. LONV70 Card has gone 1. Replace the LONV70 Card
bad
Error Help - 0328 EMERGENCY
0328 EMERGENCY

Summary EMERGENCY.

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 message
Actions
1 1. Obstacle in the door way 1. Remove the obstacle in the
door way
2. Reset the Doot Controller
2 2. Refer to cause and action 1. Refer to cause and action
of Error HW_POS of Error HW_POS
Error Help - 0329 NORMAL_RESET
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 message
Actions
1 1. A reset had taken place None
Error Help - 0330 EST_LRACCU_OVERFL
0330 EST_LRACCU_OVERFL

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

Causes and message
Actions
1 has to be defined has to be defined
Error Help - 0331 BLOCKED_OPENING_DIRECTION
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

Extra Info the 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 message
Actions
1 1. Obstacle in the door ways 1. Remove the Obstacle in
the door way if any
2 2. Panels Jammed beacuse 1. Remove or clean the dirt in
of dirt on the panel gangway the panel gang way
Error Help - 0332 BLOCK_CLOSE_DIRECTION
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

Extra Info the 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 message
Actions
1 1. Obstacle in the door ways 1. Remove the Obstacle in
the door way if any
2 2. Panels Jammed beacuse 1. Remove or clean the dirt in
of dirt on the panel gangway the panel gang way
Error Help - 0333 SLV70_OBSTACLE_DETECT
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 message
Actions
1 1. Obstacle in the door ways 1. Remove the Obstacel from
during Self Learning the door ways and start Self
Learning again
Error Help - 0334 SLV70_RESULT_RANGE
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 message
Actions
1 1. Initial Mass 1. Provide the right initial
mass, the increments are in
increments of 100kg: 100 to
400 Kg
Error Help - 0335 IAC_CLUTCH_WARNING
0335 IAC_CLUTCH_WARNING

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

Causes and message
Actions
Error Help - 0336 DRIVE_OVER_TEMP_WARNING
0336 DRIVE_OVER_TEMP_WARNING

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

Causes and message
Actions
Error Help - 0337 HOLDING_FORCE_AT_CLOSED_POSITION
0337
HOLDING_FORCE_AT_CLOSED_POSITION

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

Causes message
and
Actions
Error Help - 0338 Reserve_8
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
Error Help - 0401 VCOM Node Connected
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.
Identification number of the VCOM node (8 digit hex. value

Extra Info xABCDEFGH).
Value of digits ABCDEF: information for R&D only

Value of digits GH: identification number of the VCOM node (pcb)
Values for VCOM node identification number:

Old encoding "VXT_SUBSYS_ID":
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" (logical address of the node):

file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/400_599_Lift/err_0401_en.htm[29.6.2010. 17:08:04]
Error Help - 0401 VCOM Node Connected
xD9 = E-Vision PC
xFA = SID Workstatoin (PC #1)
xF9 = SID Workstation (PC #2)
xF8 = Gateway Interface Board (GW)
xD1 = SID embedded Lift 1 (MBRD Print)
Example:
Extra info value = 0000E131: Controller of Elevator #3 connected to
VCOM
Extra info value = 0000E5FA: SID PC (#1) connected to VCOM
The values and the encoding of the extra info for TX4
(RS/IVXVF/SIOL) systems are not described here.
None.
Source ID

Causes and message
Actions
1 hardware fault, hardware If this message appears very
reset often without an obvious
reason, check the VCOM bus
connection and test the
corresponding VCOM node to
verify its operation; exchange
it if necessary.
Error Help - 0402 VCOM Node Disconnected
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

Description no 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.
Identification number of the VCOM node (8 digit hex. value

Extra Info xABCDEFGH).
Value of digits ABCDEF: information for R&D only

Value of digits GH: identification number of the VCOM node (pcb)
Values for VCOM node identification number:

Old encoding "VXT_SUBSYS_ID":
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
Error Help - 0402 VCOM Node Disconnected
xFA = SID Workstation (PC #1)

xF9 = SID Workstation (PC #2)
xF8 = Gateway Interface Board (GW)
Example:
Extra info value = 0000E131: Controller of Elevator #3 disconnected
from VCOM
Extra info value = 0000E5FA: SID PC (#1) disconnected from
VCOM
The values and the encoding of the extra info for TX4
(RS/IVXVF/SIOL) systems are not described here.
None.
Source ID

Causes and message
Actions
1 Either the VCOM bus If this message appears very
connection is interrupted or often without an obvious
the node/subsystem has reason, check the VCOM bus
been turned off. connection and test the
corresponding VCOM node to
verify its operation; exchange
it if necessary.
Error Help - 0403 PowerUp
0403 PowerUp
This section describes the Lift error PowerUp.

Summary
The CPU on the main control pcb reinitialises. Check log for CPU
Description error 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.
------------------------------------------------------------------
Error Help - 0403 PowerUp
Causes and message

Actions
1 Power up after internal Scan error log for reason of
problem (e.g. Watchdog, reset
Software exception handling)
2 External reason for power up Source Id contains
(e.g. reset button pressed, information about reason for
complete loss of power) power up
Error Help - 0404 Start Monitor Expired
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
Description trip was
not initiated within the predefined timeout after sending a trip
command.
Possible reasons are:
a) The doors refused to close or communication with the door(s)

was disrupted.
b) The drive refused to or could not travel or communication with the
drive was disrupted
c) The door(s) refused to lock or communication with the door(s)
was disrupted.
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 message
Actions
1 Faulty safety circuit Check the door contacts.
Error Help - 0404 Start Monitor Expired
2 Check the safety circuit.

3 Connection to subsystem lost Check the bus connection
and test corresponding
subsystem to verify its
operation and if necessary to
exchange it
Error Help - 0405 Permanent Active Call
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 message
Actions
1 Defective call button or button Check the call button.
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 message
Actions
1 Faulty EPROM or pcb. Change EPROMs/FLASH or
Lift Control Processor board.
If the problem can not be
solved contact the field
support hotline or the VX-
Center.
Error Help - 0407 COM Bus Stress
0407 COM Bus Stress
This section describes the Lift error COM Bus Stress.

Summary
COM_BUS_STRESSED. The communication System VCOM does

Description not 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 message
Actions
1 Bus is faulty Check lift -, groupbus if all
functional.
generated in a certain period order to determine the source
of time of the telegram flood and test
Error Help - 0407 COM Bus Stress

disappears.
Error Help - 0408 PIOL_ConfErr
0408 PIOL_ConfErr
This section describes the Lift error PIOL_ConfErr.

Summary
PIOL CONFIGURATION DATA ERROR.The PIOL 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 message
Actions
1 Configuration data not Check PROM.
received
Error Help - 0409 COM_Bus Reconfiguration
0409 COM_Bus Reconfiguration
This section describes the Lift error COM_Bus Reconfiguration.

Summary


None.
Source ID

Causes and message
Actions
1 Bus is faulty Check lift -, groupbus; all
functional.
Error Help - 0409 COM_Bus Reconfiguration

disappears.
addresses
and check if the
7 NOTE : If the problem still
Center.
Error Help - 0410 PIO-Error
0410 PIO-Error
This section describes the Lift 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 message
Actions
1 Check the indicated
components and if necessary
change them
described component
Error Help - 0411 ARA-Service
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
Error Help - 0412 KTHM-Service
0412 KTHM-Service
This section describes the Lift error KTHM-Service.

Summary
Overtemperature in machineroom detected.

Description
not used
Extra Info
ndef
Source ID

Causes and message
Actions
1 none
Error Help - 0413 TAB-Service
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).
The extra information is a 8 digit hex code (Example: x020E8903).

Extra Info The 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: xAABBCCDD

(refer to error 1209 'Missing Node' for the description of the Board Id
and the Board Type)
AA: Board Id
BB: Board Type
CC: Subnet id
DD: Node id
ndef
Source ID

Causes and message
Actions
1 Monitoring of critical I/O's check peripheral I/O boards (
detects missing I/O boards faulty or disconnected )
(nodes) on the user bus (LON
/ BIO2)
Error Help - 0414 SDU-Service
0414 SDU-Service
This section describes the Lift error SDU-Service.

Summary
Monitoring of rope stretch detects inadmissible/critical rope stretch

Description of suspension ropes.
ndef
Extra Info
ndef
Source ID
Error Help - 0415 Reserve_Error_415
This section describes the Lift error Reserve_Error_415.

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

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

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

Description SCT 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 message
Actions
1 During the checksum test of Examine the EEPROM.
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.
Error Help - 0421 Invalid Parameter Value
0421 Invalid Parameter Value
This section describes the Lift error Invalid Parameter Value.

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

Description out 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
Error Help - 0422 FLASH Failure
0422 FLASH Failure
This section describes the Lift error FLASH Failure.

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

Description or write access failed. Please check/replace the FLASH devices.
None.
Extra Info
None.
Source ID
Error Help - 0423 PCT define
0423 PCT define
This section describes the Lift error PCT define.

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

Description The 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
Error Help - 0424 Parameter Missing
0424 Parameter Missing
This section describes the Lift error Parameter Missing.

Summary
Software Error "PCT parameter not found". Indicates that the

Description software tried to access a missing parameter in the PCT.
Please contact the hotline of the supplier.
None.
Extra Info
None.
Source ID
Error Help - 0425 SCT/PCT write error
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-

Description Center, reliable operation is no longer guaranteed.
None.
Extra Info
None.
Source ID
Error Help - 0426 Wrong SBT Data
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
Error Help - 0427 Wrong SCT Data
0427 Wrong SCT Data
This section describes the Lift error Wrong SCT Data.

Summary
Software Error "invalid SCT data". Please contact the VX-Center,

Description reliable operation is no longer guaranteed.
None.
Extra Info
None.
Source ID
Error Help - 0428 End Monitor Expired
0428 End Monitor Expired
This section describes the Lift error End Monitor Expired.

Summary
After sending the start command (Start_OK) to the drive a timer is

Description started. When this timer is over and the trip not yet finished then this
message will be generated.
Number of retries during the same trip

Extra Info
Not important
Source ID

Causes and message
Actions
1 Check the safety circuit
2 Check the door contacts
Error Help - 0429 Chipcard general error
0429 Chipcard general error
This section describes the Lift error Chipcard general error.

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

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

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

Summary
-
Description
-
Extra Info
-
Source ID
Error Help - 0433 Chipcard not valid
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 message
Actions
1 Chip card data invalid or Order new chip card from
faulty chip card supplier.
Error Help - 0434 SCT Expansion
0434 SCT Expansion
This section describes the Lift error SCT Expansion.

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

Description the 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
Error Help - 0434 SCT Expansion

Causes and message
Actions
1 Too many services ordered. Verifiy oder data.
Error Help - 0435 Invalid SCT
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 message
Actions
1 Corrupted SCT or internal On elevator control which
error 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
Error Help - 0440 Invalid Parameter Access
0440 Invalid Parameter Access
This section describes the Lift error Invalid Parameter Access.

Summary
Software Warning "invalid_access_parameter".

Description
For source Id. = 16/17: Parameter group id. and parameter id. of
Extra Info parameter (hex)
Software task identifier or source code file identifier.

Source ID
Source Id. = 15(dec): 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. = 82(dec): BMK string not valid.
Error Help - 0441 Invalid Telegram Data
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
Error Help - 0442 Invalid Telegram Attribute
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

Description telegram.
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
Error Help - 0443 Invalid Telegram 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
Error Help - 0444 Invalid Telegram Group
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
Error Help - 0445 Invalid Lift Number
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 message
Actions
1 Wrong configuration data Order/correct configuration
(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

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0450 Parameter Configuration Error
0450 Parameter Configuration Error
This section describes the Lift error Parameter Configuration Error.

Summary
Sofware Warning "param_config_process_error"

Description
None.
Extra Info
None.
Source ID
Error Help - 0451 IO Configuration Error
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
Error Help - 0452 SCT/PCT read error
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
Error Help - 0453 Timer Table Overflow
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
Error Help - 0454 SW-Warning54
0454 SW-Warning54
This section describes the Lift error SW-Warning54.

Summary
Software Warning "totals_log_overflow"

Description
None.
Extra Info
None.
Source ID
0455 SW-Warning55

Summary
Software Warning "unknown_task_id in error handler"

Description
None.
Extra Info
None.
Source ID
0456 SW-Warning56

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
Error Help - 0460 VCOM Init
0460 VCOM Init
This section describes the Lift error VCOM Init.

Summary
Software Warning "VCOM_init"

Description
None.
Extra Info
None.
Source ID
Error Help - 0461 VCOM open
0461 VCOM open
This section describes the Lift error VCOM open.

Summary
Software Warning "VCOM_open"

Description
None.
Extra Info
None.
Source ID
Error Help - 0462 VCOM close
0462 VCOM close
This section describes the Lift error VCOM close.

Summary
Software Warning "VCOM_close"

Description
None.
Extra Info
None.
Source ID
Error Help - 0463 VCOM provide
0463 VCOM provide
This section describes the Lift error VCOM provide.

Summary
Software Warning "VCOM_provide"

Description
None.
Extra Info
None.
Source ID
Error Help - 0464 VCOM unprovide
0464 VCOM unprovide
This section describes the Lift error VCOM unprovide.

Summary
Software Warning "VCOM_unprovide"

Description
None.
Extra Info
None.
Source ID
Error Help - 0465 VCOM request
0465 VCOM request
This section describes the Lift error VCOM request.

Summary
Software Warning "VCOM_request"

Description
None.
Extra Info
None.
Source ID
Error Help - 0466 VCOM unrequest
0466 VCOM unrequest
This section describes the Lift error VCOM unrequest.

Summary
Software Warning "VCOM_unrequest"

Description
None.
Extra Info
None.
Source ID
Error Help - 0467 VCOM send
0467 VCOM send
This section describes the Lift error VCOM send.

Summary
Software Warning "VCOM_send"

Description
None.
Extra Info
None.
Source ID
Error Help - 0468 VCOM pend
0468 VCOM pend
This section describes the Lift error VCOM pend.

Summary
Software Warning "VCOM_pend"

Description
None.
Extra Info
None.
Source ID
Error Help - 0469 VCOM get
0469 VCOM get
This section describes the Lift error VCOM get.

Summary
Software Warning "VCOM_get"

Description
None.
Extra Info
None.
Source ID
Error Help - 0470 VCOM accept
0470 VCOM accept
This section describes the Lift error VCOM accept.

Summary
Software Warning "VCOM_accept"

Description
None.
Extra Info
None.
Source ID
Error Help - 0471 VCOM reply
0471 VCOM reply
This section describes the Lift error VCOM reply.

Summary
Software Warning "VCOM_reply"

Description
None.
Extra Info
None.
Source ID
Error Help - 0472 VCOM queue overflow
0472 VCOM queue overflow
This section describes the Lift error VCOM queue overflow.

Summary
Software Warning "VCOM_queue_full". A software-task received too

Description many messages in a short period of time, or is not responding.
IMPORTANT!
If the error keeps appearing during normal operation reliable
operation is no longer guaranteed. Immediately save the error log
and note the circumstances under which the error occurred. Contact
the 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.
queue_id from the VCOM_upcall VCOM_QUEUE_FULL:

Extra Info
x100000yy, yy=queue_id from the VCOM_upcall
Error Help - 0472 VCOM queue overflow
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 message
Actions
1 Problem with VCOM remove elevator control from
communication group communication and
check if error disappears.
Error Help - 0473 VCOM table full
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 message
Actions
Error Help - 0473 VCOM table full
1 Too many special telegrams Please contact the VX-

or special custom services Center.
configured in the PCT/SCT
2 Incorrect use of wildcards and Please contact the VX-
MYLIFT in the PCT Center.
3 Too many times the same Please contact the VX-
telegram is configured on Center.
multiple I/O boards in PCT.
4 Software problem. Please contact the VX-
Center.
Error Help - 0474 VCOM Comms Queue Full
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 SW-Warning75

Summary
Software Warning "Too much Bus reconfiguration"

Description
None.
Extra Info
None.
Source ID
Error Help - 0476 Fatal Error ON (Breakdown)
0476 Fatal Error ON (Breakdown)
This section describes the Lift error Fatal Error ON (Breakdown).

Summary
Message indicates activation of the Fatal service (elevator

Description breakdown) used to shutdown the elevator after a severe error
condition in a subsystem (drive, door etc.) is detected. With active
fatal service the elevator is no longer available for transport.
See value of extra information for further details about:

- predefined duration of 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 'GH'(Bit 0 to Bit 7):
0000 0000(bin)/00(hex) : Fatal Service with Permanent Blockage
0000 0001(bin)/01(hex) : Fatal Service with Short Blockage
0000 0101(bin)/05(hex) : Fatal Service with Long Blockage
0001 1110(bin)/1E(hex) : Fatal Service with Blockage from Door
Module (Permanent Blockage)
Value of 'EF'(Bit 8 to Bit 15) : Service Id. number of the Current

Service
For Example:
01(dec)/01(hex): Normal Service 'N'
10(dec)/0A(hex): Inspection Service 'INS'
14(dec)/OE(hex): Unavailable Service 'UNV'
27(Dec)/1B(hex): SAB Service
Value of 'CD' (Bit 16 to Bit 23): Value of Lower Byte of the error
number that caused the fatal service.
Value of 'AB' (Bit 24 to Bit 31): Value of Upper Byte of the error
Error Help - 0476 Fatal Error ON (Breakdown)
For Example: For Error number 300 (dec) ‘AB’ will be 01(hex) and
'CD' will be 2C(hex)
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 message
Actions
1 A error occurred which sets Please refer to the extra
the elevator to status 'fatal'. information of this message
This message itself is not an for the causing error.
error.
Error Help - 0477 Fatal Error OFF
0477 Fatal Error OFF
This section describes the Lift error Fatal Error OFF.

Summary
Message indicates deactivation of the Fatal service. See value of

Description extra information for further details about:
- Cause of fatal service reset (manual / time)

- 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 'GH'(Bit 0 to Bit 7): Fatal Reset cause
0000 0000(bin)/00(hex): Fatal service OFF after Reset Timer
expired
0000 0001(bin)/01(hex): Fatal service Off after Manual Reset
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(dec)/01(hex): Normal Service 'N'
10(dec)/0A(hex): Inspection Service 'INS'
14(dec)/OE(hex): Unavailable Service 'UNV'
27(Dec)/1B(hex): SAB Service
Value of 'CD' (Bit 16 to Bit 23): Value of Lower Byte of the error
Value of 'AB' (Bit 24 to Bit 31): Value of Upper Byte of the error
For Example: For Error number 300(dec) ‘AB’ will be 01(hex) and
'CD' will be 2C(hex)
Error Help - 0477 Fatal Error OFF
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 message
Actions
1 not applicable (the message
'Fatal Error OFF' is not an
error)
Error Help - 0478 OVERLAY failure
0478 OVERLAY failure
This section describes the Lift error OVERLAY failure.

Summary
The message indicates a status change of the overlay Master

Description and/or Slave PC (M10 overlay) detected by the control software.
This message is generated when the communication with the
Overlay Master/Slave PC (M10) 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 message
Actions
1 Failure of master or slave Check overlay PC and
overlay (PC) replace 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
Error Help - 0480 No Modem
0480 No Modem
This section describes the Lift error No Modem.

Summary
No Modem
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0481 Modem Present
0481 Modem Present
This section describes the Lift error Modem Present.

Summary
Modem present
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0482 Modem Calling
0482 Modem Calling
This section describes the Lift error Modem Calling.

Summary
Modem is dialing a telephone number.

Description
ndef
Extra Info
ndef
Source ID
Error Help - 0483 Modem Answering
0483 Modem Answering
This section describes the Lift error Modem Answering.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0484 Modem Online
0484 Modem Online
This section describes the Lift error Modem Online.

Summary
Modem is engaged in a call with another modem.

Description
ndef
Extra Info
ndef
Source ID
Error Help - 0485 Modem Error
0485 Modem Error
This section describes the Lift error Modem Error.

Summary
Modem cannot initiate a call because the telephone number

Description information from the PCT file is not valid
ndef
Extra Info
ndef
Source ID
Error Help - 0486 Modem Line Busy
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
ndef
Extra Info
ndef
Source ID
Error Help - 0487 Modem No Dialtone
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
ndef
Extra Info
ndef
Source ID
Error Help - 0488 Modem No Carrier
0488 Modem No Carrier
This section describes the Lift error Modem No Carrier.

Summary
Modem no carrier
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0489 Modem Delayed
0489 Modem Delayed
This section describes the Lift error Modem Delayed.

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0490 Table_Overflow
0490 Table_Overflow
This section describes the Lift error Table_Overflow.

Summary
Error 490 is no longer used. Please refer to error 903 'Table

Description Overflow'.
The software detects a table overflow in the IO handler or an

overflow 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
Error Help - 0491 User Level 3 disabled
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
Description ESM 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 message
Actions
1 normal action none
Error Help - 0492 User Level 3 reenabled
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

Description service 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 message
Actions
1 normal action none
Error Help - 0493 Low Building Sway Active
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
Error Help - 0494 Medium Building Sway Active
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
Error Help - 0495 High Building Sway Active
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
Error Help - 0496 Building Sway Deactivated
0496 Building Sway Deactivated
This section describes the Lift error Building Sway Deactivated.

Summary
Building Sway is deactivated

Description
None
Extra Info
Source ID

Summary
ndef
Description
ndef
Extra Info
ndef
Source ID
Error Help - 0498 Group 24VDC Fail
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
Error Help - 0499 Lift 24VDC Fail
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

Description warning '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
Error Help - 0500 12VDC Power Fail
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
Error Help - 0501 Battery Charging
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
Error Help - 0502 Battery Charge Low
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
Error Help - 0503 Battery Charge Very Low
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
Error Help - 0504 Battery Dead / Missing
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 day and after a
manual reset provided normal voltage supply
(Group24VDC/Lift24VDC to ASILOG/ASIX) is on.
None
Extra Info
None
Source ID

Causes and message
Actions
1 Battery not connected Check the wiring and
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
Error Help - 0505 Battery Charge Time Expired
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
Description occurs 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 message
Actions
1 Battery broken Replace the battery
Error Help - 0506 Battery Charge Low on PEBO
0506 Battery Charge Low on PEBO
This section describes the Lift error Battery Charge Low on PEBO.
Summary
Low battery charge on PEBO (manual evacuation device). The

Description elevator is shut down (FATAL service ) because it is not allowed to
run the elevator with insufficient battery charge.
None
Extra Info
None
Source ID
Error Help - 0507 Building Sway Device Error
0507 Building Sway Device Error
This section describes the Lift error Building Sway Device Error.
Summary
Building Sway Device has an error (ie the validity status = invalid)
Description
None
Extra Info
Source ID
Error Help - 0508 WAD-Service
0508 WAD-Service
This section describes the Lift error WAD-Service.

Summary
Water detection in pit active (input KWSG).

Description
not used
Extra Info
ndef
Source ID
Error Help - 0509 Group Master Conflict
0509 Group Master Conflict
This section describes the Lift error Group Master Conflict.

Summary
The master switching algorithm encountered an error determining

Description the 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.
not used
Extra Info
ndef
Source ID
Error Help - 0600 Attempt to start not allowed
0600 Attempt to start not allowed
This section describes the MC PVF error Attempt to start not

Summary allowed.
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 message
Actions
1 One of more of the following Check the corresponding
errors were detected: 626, error description.
627, 629, 630.
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/600_699_MC_PVF/err_0600_en.htm[29.6.2010. 17:08:54]
Error Help - 0601 Attempt to restart not allowed
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 message
Actions
1 Fatal error Check fatal error in log.
Error Help - 0602 Overtemperature
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 message
Actions
1 Overtemperature on the Check power transistors.
Inverter's heat sink.
2 Wrong wiring of the input Check wiring of the input
signal KTHVF signal KTHVF (X5.3)
3 Variodyn 35, 45, 70, 100/BR: Check brake chopper and
Malfunction of the Brake brake resistor
Chopper, Brake Resistor.
Error Help - 0603 SW warning
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 message
Actions
1 Absolutely wrong parameters Check parameters
2 Wrong program logic, run- Contact Ebikon, dept.
time failures R&D-DR.
Error Help - 0604 DL overvolt trigg
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

Description 10 ms during the trip by software.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Variodyn 35, 45, 70, 100/BR: Check Board TBR (VF70-94),
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.
Error Help - 0605 DL overvolt
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 message
Actions
1 See errror 604
2 Bad parameter Check parameter
udcl_upp_lim
Error Help - 0606 DC link undervoltage
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

Description produced. 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 message
Actions
1 The charge- or input- Check contactors and
contactor 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
Error Help - 0607 Control Hardware command wrong
0607 Control Hardware command

wrong
This section describes the MC PVF error Control Hardware

Summary command 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 message
Actions
time failures R&D-DR.
Error Help - 0608 Charging DC link failure
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 message
Actions
1 Input contactor or charge Check input or charge
contactor malfunction, in contactors (SGRW, SGR, see
which 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
problems, in which case this supply.
error appears together with
error 606
5 New AEG inverter (one
contactor), parallel inverter
Error Help - 0608 Charging DC link failure
(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
(with AEG): Bad Control tries to start a new trip
synchronisation with Travel while K2 is open, so the dc
Control, Error 608 as a link could 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 Check input or charge
Schindler converter: Input or contactors of the parallel
charge contactor malfunction, converter (SGRWx, SGRx,
in which case this error see warning log), check
appears together with auxiliary contacts and wiring
warning 644 or 645 ( 651 or (PCC X3.2, X3.4, ...).
652 / 658 or 659).
9 Wrong PVF parameters, See error 606 (first cause)
concerning input- and load-
contactor timing.
Error Help - 0609 Discharging DC link failure
0609 Discharging DC link failure
This section describes the MC PVF error Discharging DC link

Summary failure.
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 message
Actions
1 Input contactor or charge Check input and charge
contactor malfunction, in contactors SGRW, SGR.
which case this error appears
together with error 612 or
613.
2 Wrong feedback from one of Check auxiliary contacts on
these contactors. SGRW, SGR
Error Help - 0610 Current loop not OK
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 message
Actions
1 The feedback cable X1 bad Check feedback cable X1.
or 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".
Error Help - 0610 Current loop not OK
6 The cable X6, link from PVF

to the driver boards, bad or
wrong wired.
Error Help - 0611 Deactivate current loop failure
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
Description than 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 message
Actions
1 Contactor SH and /or Check contactor SH and
frequency converter failure Frequency converter
2 Interferences, bad shielding Check shielding of the LEM
of 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 check parallel converter
stand still. (same procedure as above).
Error Help - 0612 Input contactor failure
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 message
Actions
1 Input contactor failure Check contactor coil (SGR)
(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)
Error Help - 0612 Input contactor failure
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).
Error Help - 0613 Charge contactor failure
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 message
Actions
1 Charge contactor failure Check contactor coil
(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
Error Help - 0614 Current difference warning
0614 Current difference warning
This section describes the MC PVF error Current difference

Summary warning.
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 message
Actions
1 Interrupted IGBT driver Check error LEDs on the
signals due to any monitoring UKE2 board *)
function:
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 Check error LEDs on the
board detects an error (e.g. PWR board *)
bad front 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 Check LEM wiring
reaches its limits, too much connections
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 See warning log, if warning
connected: Failure of one of 47 / 55 / 63 stored, check
these converters could parallel converter.
produce an 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.
Error Help - 0615 SW encoder warning
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 message
Actions
1 Themotor is blocked, Check adjustment of brake.
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.
Error Help - 0616 Over current warning
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 message
Actions
1 The motor consumes to much Check machine and
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).
Error Help - 0617 Over speed warning
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 message
Actions
1 The brake is faulty. Check the brake.
2 Overspeed during trip: Must Check if no test trip was
not occur in normal performed.
installations.
Error Help - 0618 Start direction wrong
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 message
Actions
1 The motor leads-in or motor- Check motor direction
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
Error Help - 0619 Speed reference warning
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 message
Actions
1 Lost of communication. Check connection to Travel
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.
Error Help - 0620 Time control motor exceeded
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 message
Actions
1 Run-time problems. Contact Ebikon, dept.
R&D-DR.
Error Help - 0621 Receive uart failure
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

Description stops 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 message
Actions
1 Communication disturbance Check communication
or interference. between PVF & Travel
Control.
2 Check for interference.
3 Bad UART. Change PVF board if persists.
Error Help - 0622 Message source failure
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 message
Actions
1 See error 621.
Error Help - 0623 Message length failure
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 message
Actions
1 See error 621.
Error Help - 0624 Receive state wrong
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 message
Actions
time failures. R&D-DR.
Error Help - 0625 Transmit state wrong
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 message
Actions
time failures. R&D-DR.
Error Help - 0626 EPROM checksum failure
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 message
Actions
1 The previous contents of the Empty RAM (Check
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.
Error Help - 0627 RAM failure
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 message
Actions
1 RAM failure. Change RAM or board.
Error Help - 0628 Board battery failure
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
Description battery (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 message
Actions
1 Old or too long operated Replace battery or capacitor.
battery.
2 Check date on battery.
3 Wrong mounting or handling Check connections on PRUM
board.
4 Discharged through bad
packaging material.
Error Help - 0629 RAM checksum failure
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 message
Actions
1 The previous contents of the Empty RAM (as before).
RAM are not deleted before
exchanging EPROMs.
2 RAM failure. Change RAM or board.
Error Help - 0630 Watchdog failure
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 message
Actions
1 Watchdog IC failure or wrong Change board.
mounting
Error Help - 0631 Transmit failure
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 message
Actions
1 The communication line is Check communication cable
blocked. (X8)
2 Disturbance or interference. Check shielding
3 Travel Control not Could happen if Travel
responding. Control perfomes a reset
while PVF wants to send a
byte.
4 Bad UART Change board
Error Help - 0632 Open safety circuit
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
Description state 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 message
Actions
1 At the beginning of a trip, Check safety chain
motor contactors are switched
Error Help - 0632 Open safety circuit
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 Replace TOPT
and 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
contactors. (SF), (K2)
Error Help - 0633 HW encoder warning
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
Description are 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 message
Actions
1 Bad tacho electronic or tacho Check motor tacho, cable and
cable (connector is not connectors (PVF X9 and/or
inserted properly or damaged IG 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.
Error Help - 0634 Exception vector
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. If it is not possible to remove
the problem using the actions described below, contact Ebikon,
dept. R&D-DR.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Absolutely wrong parameters Check PVF parameters.
2 Check PVF CPU status log: If
the event zero divide is
stored, some parameters
must be wrong.
3 RAM not properly deleted Remove the two RAM (IC 76,
after a change ot the 77) at least for 10 sec. This is
software. absolutely necessary, if the
PVF SW (EPROMs) has been
Error Help - 0634 Exception vector
changed.
4 CPU or peripherals failure. Disturbance or interference.
Change PVF board.
5 Bad power supply (5V) Check UVVF or UKE2.
Error Help - 0635 Contactor time exceeded
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-

Description contactor, 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 message
Actions
1 Bad set of PVF parameters: Set these parameters to the
"t_char on / off", "t inp on / default value (0.2 sec.).
off" (higher than 10 sec.)
Error Help - 0636 Driver Print power failure
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 message
Actions
1 Bad power-supply board or Check UVVF or UKE2 ( VF35,
wiring. 45 ,70-95, 100/BR) board.
2 Bad driver board or wiring. Check wiring and supply of
PWR board (VF100, 140,
220)
Error Help - 0637 Overtemperature brake resistor
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 message
Actions
1 Variodyn 35, 45,70, 100/BR: Check brake chopper and
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 X4.9. signal KTHBR.
Error Help - 0638 FCR no start
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 message
Actions
1 No internal FCRclearance Check FCR error log
due 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
Error Help - 0639 FCR no stop
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 message
Actions
1 FCR problems Check FCR
PVF X4.5 (input)
3 Bad output wiring Check wiring connections
PVF X3.7
Error Help - 0640 FCR interrupt
0640 FCR interrupt
This section describes the MC PVF error FCR interrupt.

Summary
During trip, FCR stops running (cause see FCR error log). Only
Description active, if elevator parameter Inverter_Model is set to 15 (FCR).
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Bad mains, FCR overtemp, ... Check FCR error log
PVF X4.5
Error Help - 0641 External error
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 message
Actions
1 External device detects Check error LEDs on external
anerror device (normally UKE2 or
PWR board) *)
2 Safety circuit opens during Check Travel Control event
trip (produces normally 1 log, if there are safety circuit
Error Help - 0641 External error
warning) problems, compare times

(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 !
Error Help - 0642 PCC failure
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
Description not 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 message
Actions
1 Parallel controller not enabled Check bridges on PCC board
2 Wrong PVF parameter Check elevator para
Inverter_model
Error Help - 0643 Supply failure cc1
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 message
Actions
1 24V supply faulty or bad Check 24V input (PCC X1.2)
wiring
2 DC-DC converter on PCC Replace PCC board.
board is faulty
Error Help - 0644 Input contactor failure cc1
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 message
Actions
1 Input contactor failure Check contactor coil
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
Error Help - 0645 Charge contactor failure cc1
This section describes the MC PVF error Charge contactor failure

Summary cc1.
Charge contactor of the parallel converter (1_SGRW) not

Description responding 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 message
Actions
wiring PCC X3.4
3 Wrong wiring, no driver signal Check driver signal VSGRW
on PVFP X3.3
Error Help - 0646 DL overvolt trigg cc1
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 message
Actions
1 Variodyn 280 (Schindler): Check FCR
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
measurement PCC X3.9 and X3.10. Should
be UDCL/100
Error Help - 0647 Current difference warn cc1
This section describes the MC PVF error Current difference warn

Summary cc1.
1) Current difference on CC1 controller between actual and

Description reference 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 message
Actions
1 Interrupted current loop on Check IGBT, check error
CC1: IGBT short circuit LEDs on PWR board (only
(Variodyn 280) or any other AEG converter, VF 140 / 220)
monitoring function (Variodyn
100/140/220: overcurr.
overvolt, etc.) activated.
reaches its limits, too much connections CC1
current needed.
3 Wrong PVFP parameters Check parameters
4 Current difference error Check error log, if error
stored on PCC board during detected at the trip phase
stand 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

opened safety circuit and tries log 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
of 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
Error Help - 0648 Current loop failure cc1
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 message
Actions
1 The feedback cable X2 on
PCC board is bad or not
connected in its socket.
Error Help - 0649 Overtemperature cc1
This section describes the MC PVF error Overtemperature cc1.

Summary
Over temperature check has detected power transistors on

Description converter 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 message
Actions
1 Overtemperature on the heat Check power transistors.
sink of inverter CC1.
signal signal 1_KTHVF PCC X3.6)
Error Help - 0650 External error cc1
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 message
Actions
1 Converter CC1 detects an Check converter CC1 (AEG
error converter: see error LEDs on
PWR board)
(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 message
Actions
wiring
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 message
Actions
wiring PCC X?.?
PVFP X3.4

Summary cc2.

/220), the contactor feedback is not connected and this error should
None.
Extra Info
None.
Source ID

Causes and message
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 message
Actions
1 Variodyn 280 (Schindler): Check FCR
converter (FCR)
redundant.
measurement PCC X?.? and X?.?.
4 Should be UDCL/100

Summary cc2.

None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Interrupted current loop on Check IGBT, check error
CC2: IGBT short circuit LEDs on PWR board (only
100/140/220: overcurr.
overvoltage, etc.) activated.
current 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 message
Actions
1 The feedback cable X? on

Summary

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 message
Actions
signal 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
the current state of the converter CC2. Checked at trip start and
during trip.
None.
Extra Info
None.
Source ID

Causes and message
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 message
Actions
wiring
board is faulty
Summary

That applies only to theparallel operation with Schindler converters
/ 220), the contactorfeedback is not connected and this error should
None.
Extra Info
None.
Source ID

Causes and message
Actions
wiring PCC X?.?
PVFP X3.4

Summary cc3.

/220), the contactor feedback is not connected and this error should
None.
Extra Info
None.
Source ID

Causes and message
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 message
Actions
1 Variodyn 280(Schindler): Check FCR
converter (FCR)
redundant.
measurement PCC X?.? and X?.?. Should
be UDCL/100

Summary cc3.

None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Interrupted current loop Check IGBT, check error
onCC3: IGBT short circuit LEDs on PWR board (only
100/140/220: overcurr.
overvoltage, etc.) activated.
current 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 message
Actions
1 The feedback cable X? on

Summary

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 message
Actions
signal 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 the current state of the converter CC3. Checked at trip
start and during trip.
None.
Extra Info
None.
Source ID

Causes and message
Actions
PWR board)
(PCC X?.? or PWR X102.6 /
UKE2 X?.?)
LEDs on PWR boardParallel
on UKE2 board

under error 614 !
Error Help - 0667 Dummy 1
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
Error Help - 0700 Memory Failure
0700 Memory Failure
This section describes the MC PVEC error Memory Failure.

Summary
Incorrect memory access.

Description
1: error after reading from or writing to RAM

Extra Info 2: PLD not programmed (only for pcb PIOVEC)
None.
Source ID

Causes and message
Actions
1 Defective RAM on pcb PVEC Replace the pcb PVEC.
(Extra Info = 1)
2 PLD on PIOVEC not Replace the pcb PIOVEC or
programmed (Extra Info = 2) program its PLD
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/700_739_MC_PVEC/err_0700_en.htm[29.6.2010. 17:09:27]
Error Help - 0701 SW Warning
0701 SW Warning
This section describes the MC PVEC error SW Warning.

Summary
The software detected an exceptional behavior of either the software

Description or of the hardware. These events are stored in the warning log only
and never generate an error. Unless listed below the extra info
value can be decoded by developers of R&D-DR.
140: Power up, SW-Reset

Extra Info 143: Error state set to dead (inverter blocked permanent)
144: Warning log deleted
145: Error log deleted
171: HW watchdog
1xxx: Illegal parameter on inverter where 'xxx' is the inverter
parameter id (Comm Id) according to J41400465
None.
Source ID
Error Help - 0702 Communication Failure
0702 Communication Failure
This section describes the MC PVEC error Communication Failure.

Summary
Error on the serial communication link from the Motor Control to the
Description Travel Control.
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: CAN bus off (Parallel Converter)
11: CAN MSG to frame (Parallel Converter)
12: CAN frame to MSG (Parallel Converter)
13: CAN bus occupied (Parallel Converter)
14: No communication to master (Parallel Converter)
15: No communication to slaves (Parallel Converter)
17: No SSI communication (Parallel Converter)
20: CAN bus Warning (DriveBus)
21: CAN bus off (DriveBus)
22: CAN MSG to frame (DriveBus)
23: CAN frame to MSG (DriveBus)
24: CAN bus occupied (DriveBus)
30: I2C Bus not available
31: I2C operation error
32: I2C Bus Busy
None.
Source ID
Error Help - 0702 Communication Failure

Causes and message
Actions
1 Extra info 1 - 3: EMC Check whether all screen
problems or communication cables are correctly grounded
cable faulty
2 Check the connection
between the Motor Control
and the Travel Control.
3 Extra info 4 - 8 / 14 / 15: Report to R&D-DR
software problems
Error Help - 0703 Overcurrent Motor
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 fact.

Extra Info exceeded)
2: Unexpected change of motor torque
None.
Source ID

Causes and message
Actions
1 Brake that does not open or check brake
opens only partially
Error Help - 0703 Overcurrent Motor
2 Wrong parameters check parameters

3 Wrong dimensioning of drive check drive calculation
system (speed, acceleration, car
weight, rated load, etc.)
4 Wrong balancing check balancing of the
(counterweight) of the elevator
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 buffers.
trip 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
Error Help - 0704 Encoder Failure
0704 Encoder Failure
This section describes the MC PVEC error Encoder Failure.

Summary
The feedback signal from the motor encoder is missing. The

Description encoder failure signal is generated on the related control board (e.g.
PIOVECxx) and read by 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)
None.
Source ID

Causes and message
Actions
1 Encoder cable not connected Check the cable and its
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 Replace encoder cable and/or
encoder or encoder cable encoder
Error Help - 0705 Speed Difference
0705 Speed Difference
This section describes the MC PVEC error Speed Difference.

Summary
The difference between the speed reference value from travel

Description control 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).
1: underspeed
Extra Info 2: overspeed
3: speed control error
4: wrong sense of rotation detected during test 'sense of rotation'
(direction test for asynchronous motors)
5: emergency stop during adjust tacholess control test
None.
Source ID

Causes and message
Actions
1 Extra info 1 - 3: a) ensure the brakes do not
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: 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
Error Help - 0705 Speed Difference
defective
2 Extra info 4: tacho signals or change either tacho signals or
motor phases inverted (error motor phases or execute
detection immediately after direction test
trip start)
Error Help - 0706 Speed Ref Missing
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).
None.
Source ID

Causes and message
Actions
1 Interrupted transmission line Check serial communication
from Travel Control (e.g. pcb (cable and connection to
ASILOG/ASIX) to Motor pcb's)
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) Replace respective pcb
defective
Error Help - 0706 Speed Ref Missing
Error Help - 0707 SGRW Failure
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.
None.
Source ID

Causes and message
Actions
1 Wiring of control signal Check related wiring acc. to
VSGRW or of feedback signal wiring diagrams
SGRW broken or not
connected
2 Contactor SGRW faulty Check contactor SGRW
Error Help - 0707 SGRW Failure
3 PIOVEC/VARIOcon PCB replace PCB

faulty
Error Help - 0708 SGR/SH Failure
0708 SGR/SH Failure
This section describes the MC PVEC error SGR/SH Failure.

Summary
Control or auxiliary feedback of contactor SGR/SH faulty.

Description
Meaning of extra info value:

Extra Info 1: SGR/SH contact not ON when VSGR is ON
2: SGR/SH contact not OFF when VSGR 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): SGR/SH switches not ON when VSGR is ON during
preparation for a trip
1(1+0): SGR/SH is not ON when VSGR is ON during a trip
2(2+0): SGR/ SH switches not OFF when VSGR is OFF at end of
trip
2(2+0): SGR/SH contact not OFF when VSGR is OFF. Mains
separation in standstill when DC link is charged.
None.
Source ID

Causes and message
Actions
1 Wiring of control signal VSGR Check related wiring acc. to
or of feedback signal SGR/SH wiring diagrams
broken or not connected
2 Contactor SGR/SH faulty Check contactor SGR/SH
3 TX-GC: the safety circuit Check safety circuit and total
opens during a trip or a test error log
Error Help - 0708 SGR/SH Failure
(extra info values 1 or 5)

4 PIOVEC/VARIOcon PCB replace PCB
faulty
5 Known problem in VecSys Update VecSys software to
software. version 2.14 (or higher)
Error Help - 0709 Safety Circuit
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).
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 The safety circuit opened Check safety circuit and logs
during a trip or a test. The of other subsystems (total
safety circuit may have been error 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
Error Help - 0709 Safety Circuit
converter.
Error Help - 0710 FCR Not Ready
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
None.
Source ID

Causes and message
Actions
1 check FCR error log
Error Help - 0711 Overcurrent Inverter
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
None.
Source ID

Causes and message
Actions
Error Help - 0711 Overcurrent Inverter
1 Malfunction of current Check cables from SKiiP or

measurement from LEMs
2 IGBTS faulty Replace power unit
3 Incorrect inverter or motor Check parameters, use
parameters settings
4 Short circuit
Error Help - 0712 Power Electronic Failure
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
x02(Bitmask Bit 1): Error in phase V / VF11BR: supply voltage error
x04(Bitmask Bit 2): Error in phase W
x08(Bitmask Bit 3): 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
None.
Source ID

Causes and message
Actions
1 Cable from power unit broken check cable and connectors
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
Error Help - 0712 Power Electronic Failure
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)
8 For extra info value=5:
overcurrent / short circuit
Error Help - 0713 Current Difference
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.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Interrupted transmission of Check cables
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 If the error occurs at the end
of the acceleration phase: of the acceleration phase:
faulty dimensioning of drive reduce the nominal speed
system
5 Modernization: wrong motor
wiring
Error Help - 0714 Current Not Zero
0714 Current Not Zero
This section describes the MC PVEC error Current Not Zero.

Summary
Motor current not zero at standstill

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Current measurement faulty Check cables, LEM
2 Power assembly faulty Replace power unit
Error Help - 0715 Current Sum Failure
0715 Current Sum Failure
This section describes the MC PVEC error Current Sum Failure.

Summary
Sum of motor phase currents is not zero.

Description The error is generated when the current sum exceeds 30 % of the
inverter nominal current.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Short circuit between phase Check wiring and motor
and ground on the motor side
2 Current measurement faulty Check cables, LEM
(EMC)
Error Help - 0716 Overtemp HS Trigger
0716 Overtemp HS Trigger
This section describes the MC PVEC error Overtemp HS Trigger.

Summary
The overtemperature trigger on the heatsink is active.

Description
Extra Info higher:
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
None.
Source ID

Causes and message
Actions
1 Fan faulty Check fan
2 Cable from klixon broken or Check cable
not connected
3 Temperature of machine
room too high
4 Faulty dimensioning of drive
system
Error Help - 0717 Overtemp HS Limit
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

Description available) exceeded. (See supervisor parameter INV_TEMP_LIM --
> parameter description).
A trip must be terminated by the Travel Control on the next floor.
1: overtemperature of heatsink
Extra Info 2: no temperature signal from heatsink
3: overtemperature of brake chopper
4: no temperature signal from brake chopper
11: Overtemperature phase U
12: Overtemperature phase V
13: Overtemperature phase W
21: No temperature signal from heatsink phase U
22: No temperature signal from heatsink phase V
23: No temperature signal from heatsink phase W
None.
Source ID

Causes and message
Actions
2 Cable from heatsink broken Check cable
or not connected
room too high
4 Faulty dimensioning of drive
system
Error Help - 0718 DCL Overvoltage Trigger
0718 DCL Overvoltage Trigger
This section describes the MC PVEC error DCL Overvoltage

Summary Trigger.
Overvoltage in DC link.
Description The overvoltage trigger signal is generated on the control print
(PIOVECxx) and read by software, the voltage level is at about 875
V.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Diode bridge at the input of Check brake resistor
DC link:malfunction of the
brake chopper or brake
resistor
2 Line converter at the input of Check line converter
DC link (VF120 -
VF280):malfunction of line
converter
Error Help - 0719 DCL Overvoltage
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 stand still.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Overvoltage in mains Check mains
2 Parameter wrong Check the parameter Udcl
Upp Lim Idle
DC link (VF120 - VF280):
malfunction of line converter
Error Help - 0720 DCL Undervoltage
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.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Undervoltage in mains Check mains
2 Parameter wrong Check the parameters Udcl
Low Lim Idle and Udcl Low
Lim Ride
3 Defective diode bridge Replace power unit
DC link (VF120 -
VF280):malfunction of line
converter
Error Help - 0721 DCL Unsymmetric Voltage
0721 DCL Unsymmetric Voltage
This section describes the MC PVEC error DCL Unsymmetric

Summary Voltage.
DC link voltage not symmetric

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 DC link capacitor faulty Replace it
Error Help - 0722 DCL Charging Time
0722 DCL Charging Time
This section describes the MC PVEC error DCL Charging Time.

Summary
Maximum DC link charging time exceeded.

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Undervoltage in mains Check mains
2 Parameter wrong Check the supervisor
parameter Udcl Low Lim Idle
3 Defective diode bridge Replace power unit
Error Help - 0723 DCL Discharging Time
0723 DCL Discharging Time
This section describes the MC PVEC error DCL Discharging Time.

Summary
Maximum DC link discharging time exceeded.

Description
1: discharging time exceeded

Extra Info 2: leakage current to large
None.
Source ID
Error Help - 0724 Power Supply
0724 Power Supply
This section describes the MC PVEC error Power Supply.

Summary
Power supply faulty

Description
1: 24V supply faulty

Extra Info 2: 15V or 5V supply faulty
None.
Source ID

Causes and message
Actions
1 Check power supply
Error Help - 0725 Overtemp KTHBR
0725 Overtemp KTHBR
This section describes the MC PVEC error Overtemp KTHBR.

Summary
Overtemperature on the brake chopper resistor (detected with

Description PT100 / KTJ84 / KTHBR).
1: Overtemperature of BR (detected with klixon KTHBR)

Extra Info 2: No temperature signal from sensor BR / open
3: Shortcut of sensor BR
4: No feedback from FAN (converters with VARIOcon / VIP only)
None.
Source ID

Causes and message
Actions
2 Cable from sensor (klixon) Check cable
broken or not connected
room too high
4 Wrong dimensioning of drive Verify drive calculation
system
Error Help - 0726 Overtemp MH
0726 Overtemp MH
This section describes the MC PVEC error Overtemp MH.

Summary
Overtemperature of the hoisting motor (detected with PT100 /

Description KTJ84).
1: Overtemperature of MH
Extra Info 2: No temperature signal from MH / open
3: Shortcut of sensor MH
None.
Source ID

Causes and message
Actions
1 MH fan faulty check fan
2 THMH cable MH broken or check cable
not connected
room too high
4 Wrong dimensioning of drive Verify drive calculation
system
Error Help - 0727 HW failure
0727 HW failure
This section describes the MC PVEC error HW failure.

Summary
HW failure of converter detected.

Description
Meaning of extra info value for Yaskawa inverter:

Extra Info 1: for further details see Yaskawa documentation CPF04
2: for further details see Yaskawa documentation CPF05
For VARIOSys parallel inverter the extra info value uses the
following bitmask indicating SSI communication problems:
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
None.
Source ID

Causes and message
Actions
1 Yaskawa: faulty inverter refer to Yaskawa
hardware documentation for details
Error Help - 0727 HW failure
2 VARIOSys parallel inverter: Check SSI wiring of VIP3

SSI communication board
interrupted
3 VARIOSys parallel inverter: Check grounding connections
Disturbance on SSI (screws) of VIP3 board and
connection shielding of SSI
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
Error Help - 0728 Phase failure
0728 Phase failure
This section describes the MC PVEC error Phase failure.

Summary
Hardware failure output phase (Yaskawa only).

Description
0: for further details see Yaskawa documentation LF

Extra Info 1: for further details see Yaskawa documentation SE1
2: for further details see Yaskawa documentation SE2
None.
Source ID

Causes and message
Actions
1 faulty inverter hardware refer to Yaskawa
documentation
Error Help - 0729 Fan failure
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)
PF91 converters
1: no feedback of VFVE-CO (motor converter fan)
4: no feedback of VFVE-FCR (line resistor fan)
None.
Source ID
Error Help - 0730 FCM failure
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
None.
Source ID
Error Help - 0731 FCM overtemperature
0731 FCM overtemperature
This section describes the MC PVEC error FCM overtemperature.

Summary
Overtemperature of the field control module (FCM)

Description
None
Extra Info
None.
Source ID
Error Help - 0732 Overtemperature Line Choke
0732 Overtemperature Line Choke
This section describes the MC PVEC error Overtemperature Line

Summary Choke.
Overtemperature of the line choke (Vario LC error)

Description
None
Extra Info
None.
Source ID
Error Help - 0733 Mains current difference
0733 Mains current difference
This section describes the MC PVEC error Mains current difference.

Summary
Current difference mains supply (VarioLC). Extra info per phase.

Description
Phase
Extra Info
None.
Source ID
Error Help - 0734 Mains Overcurrent
0734 Mains Overcurrent
This section describes the MC PVEC error Mains Overcurrent.

Summary
Overcurrent mains supply (VarioLC). Extra info per phase.

Description
Phase
Extra Info
None.
Source ID
Error Help - 0735 Mains Interruption
0735 Mains Interruption
This section describes the MC PVEC error Mains Interruption.

Summary
Interruption on Mains Supply (VarioLC). Extra info per phase.

Description
Phase
Extra Info
None.
Source ID
Error Help - 0736 Mains Voltage out of range
0736 Mains Voltage out of range
This section describes the MC PVEC error Mains Voltage out of

Summary range.
Mains Supply out of range(VarioLC).

Description 'Mains undervoltage', 'Mains overvoltage' / 'Mains frequency wrong'
are distinguished by the extra info value. Also the phase is
distinguished by the extra info. The errors have the same effect;
therefore they are combined in one.
Phase
Extra Info
None.
Source ID
Error Help - 0740 Overspeed
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/740_799_Magnetek/err_0740_en.htm[29.6.2010. 17:09:45]
Error Help - 0741 Tach Loss
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 message
Actions
1 The motor encoder Check for broken wires or a
installation may be broken loose coupling.
2 The motor encoder may be Check if motor moves
broken
3 Replace Encoder
Error Help - 0742 Reverse Tach
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 message
Actions
1 If the motor is running the Swap the A and A~ wires.
correct direction
2 If the motor is running the Check the armature and
wrong direction motor field connections.
Error Help - 0743 not_a_number
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 message
Actions
1 Problem with Magnetek Try replacing PROMS U39
software and U40 on the drive.
2 Unknown cause Inform field engineer
Error Help - 0744 overflow
0744 overflow
This section describes the Magnetek error overflow.

Summary
Magnetek error 101

None.
Extra Info
None.
Source ID

Causes and message
Actions
Error Help - 0745 underflow
0745 underflow
This section describes the Magnetek error underflow.

Summary
Magnetek error 102

None.
Extra Info
None.
Source ID

Causes and message
Actions
Error Help - 0746 divide by zero
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 message
Actions
Error Help - 0747 Motor overload
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 message
Actions
1 a) Something dragging / Check for problems in the
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
Error Help - 0748 Motor field overcurrent
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 message
Actions
1 Short in winding or wiring Check the motor field current
2 Bad supply Replace field regulator board
if necessary
Error Help - 0749 Contactor fault
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 message
Actions
1 The output contactor did not Check coil wiring
pick
2 The monitoring circuit is Check auxillary contact
broken connected to TB1-7
Error Help - 0750 1 minute full field
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 message
Actions
1 Check the parameter System
Type of travel controller
Error Help - 0751 Open armature circuit
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
Error Help - 0752 safety circuit
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 message
Actions
1 Check for a jumper
2 Check that both relays drop
out properly
Error Help - 0753 PAC fault
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 message
Actions
1 Check that the acceleration
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.
Error Help - 0754 DCU CEMF fault
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 message
Actions
1 Check that the actual voltage
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.
Error Help - 0755 PCU CEMF fault
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 message
Actions
1 Check that the actual voltage
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.
Error Help - 0756 PCU reset
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
Error Help - 0757 loop fault
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 message
Actions
1 Check contactor
2 Check auxilliary contact
connected to drive.
Error Help - 0758 IST fault
0758 IST fault
This section describes the Magnetek error IST fault.

Summary
Magnetek error 901

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check for short circuit in the
motor armature circuit
2 Check tuning of current
regulator
Error Help - 0759 Power supply
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 message
Actions
1 Check for short in wiring to
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).
Error Help - 0760 Line synch
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 message
Actions
1 Check for loose connections
on input mainline wiring
2 Check for dips on mainline
voltage.
3 Check voltage divider on
Armature Interface board
Error Help - 0761 Low line
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 message
Actions
1 Check for dips in input
mainline voltage
2 Check for blown input fuse
3 Check taps on isolation
transformer
Error Help - 0762 Field loss
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 message
Actions
1 Check wiring
2 Check input fuses
3 Check that the feed to the
motor field supply has the
same phase sequence as the
main power
Error Help - 0763 DCU failure
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 message
Actions
1 DCU microprocessor failure Replace main processor
board in drive
Error Help - 0764 Bad thermistor
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 message
Actions
1 Thermistor on drive heat sink Check wiring and resistance
is open or shorted of thermistor (normally around
200 k at 25 C)
2 The actual temperature is
way out of range
Error Help - 0765 High temperature
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 message
Actions
1 Check machine room ambient
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
Error Help - 0766 Exessive ripple
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 message
Actions
1 Check for loose connections
in 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
Error Help - 0767 Blown fuse
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 message
Actions
1 Check input fuses
2 Check mainline fuses
3 Check for loose connnections
in power circuit
4 Check SCRs
Error Help - 0768 shorted doubler
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 message
Actions
1 Replace SCR (or multi-SCR
doubler pack)
Error Help - 0769 Open SCR
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
Error Help - 0770 bad parameter
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
Error Help - 0771 Forcing fault
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
Error Help - 0772 AV feedback reversed
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 message
Actions
1 Check that themotor is turning
the correct direction. If it is,
reverse the armature voltage
feedback wires (TB5-1, TB5-
2).
Error Help - 0773 Parameter too high
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 message
Actions
1 The supervisor parameter Adjust the parameter
current_limit is set too high
Error Help - 0774 Parameter out of range
This section describes the Magnetek error Parameter out of range.

Summary
Magnetek error 919

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 The elevator parameter Adjust the parameter
Nominal_AC is set too high or
too low
Error Help - 0775 Parameter out of range
This section describes the Magnetek error Parameter out of range.

Summary
Magnetek error 921

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 The motor parameter Adjust the parameter
Rated_armature_voltage is
too high or too low
Error Help - 0776 Bridge fault
0776 Bridge fault
This section describes the Magnetek error Bridge fault.

Summary
Magnetek error 921

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check connector J14
2 Check power-range-selector
resistor on TB6
3 Replace Armature interface
board or drive control board
Error Help - 0777 parameter out of range
This section describes the Magnetek error parameter out of range.

Summary
Magnetek error 922

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 The parameter Inform field Engineer, since
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 message
Actions
1 The motor parameter Adjust the parameter
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 message
Actions
1 The parameter Check the parameter setting
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
Error Help - 0780 Field supply fault
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 message
Actions
1 Check connector J13
2 Replace the motor field
supply board
3 Replace the drive control
board
Error Help - 0781 PCU software fault
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 message
Actions
1 The software in the PCU Replace proms
(U13, U14) reset
unexpectedly or is an
incompatible version
Error Help - 0809 Wrong Motion Command Value
0809 Wrong Motion Command Value
This section describes the 800_899_Varidor35_Door_Drive error

Summary Wrong Motion Command Value.
This Error is sent if Door Drive has received a DOOR MOTION

Description command (DOOR_MOTION_CMD message) but can not interpret
its detail command (e.g. open)
not available
Extra Info
not applicable
Source ID
Error Help - 0812 Wrong Motion Direction
0812 Wrong Motion Direction

Summary Wrong Motion Direction.
Inconsistency between the required door movement and the door

Description position 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.
not available
Extra Info
not applicable
Source ID
Error Help - 0818 No Heartbeat from Elevator Control
0818 No Heartbeat from Elevator

Control
This section describes the 800_899_Varidor35_Door_Drive error No

Summary Heartbeat from Elevator Control.
No Heartbeat and 'COMMUNICATION BIT' from EC

Description
not available
Extra Info
not applicable
Source ID
Error Help - 0821 Door Movement too Fast
0821 Door Movement too Fast

Summary Door Movement too Fast.
Transition from closed to open state (or vice versa) has occurred in
Description a time smaller than the minimum expected.
not available
Extra Info
not applicable
Source ID
Error Help - 0901 ConfigErr
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 message
Actions
1 Pcb 'PIOG' ID switch not set Check ID switch on PIOG.
correctly.
2 Configuration data not Check group bus connection.
received
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/900_999_IO/err_0901_en.htm[29.6.2010. 17:10:06]
Error Help - 0902 PIO Error
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 message
Actions
1 Check the indicated
components and if necessary
change them
described component
Error Help - 0903 IO Table Overflow
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 message
Actions
1 Wrong configuration section Check PCT
in PCT
2 Configuration out of range Check application limits
3 Problem in software with table Report to R&D Ebikon
limits
Error Help - 0904 IO_Missing
0904 IO_Missing
This section describes the IO error IO_Missing.

Summary
During startup the elevator control checks if IO's which are required
Description for 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 message
Actions
1 Error in PCT (for TX-GC, TX- Correct error in IO
M10, TXR5) configuration section of the
PCT
2 Harware problem with Replace interface board
hardware interface pcb for
related IO (see extra info
value)
Error Help - 0905 COP Configuration Error
0905 COP Configuration Error
This section describes the IO error COP Configuration Error.

Summary
Wrong configuration of COP node (LONCOP or LONCPI). Number

Description of 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 message
Actions
1 Problem with hardware Check COP interface board
and connections of connected
boards (NWxxx)
Error Help - 0906 Duplicate_BMK
0906 Duplicate_BMK
This section describes the IO error Duplicate_BMK.

Summary
If the same critical BMK is configured more than once on the same
Description lift then the error will be logged. In case the software finds a
unallowed duplicate entry in the IO database (e.g. for a critical input)
an error will be logged for each entry. 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).
Identifies the board type of the bus node on which the same BMKs
Extra Info are configured. xABCDEFGH (8 digit hex number) where:
A: is the sequence number of the entry in the internal IO database

B: Identifies the IO Domain
CD: Node type
EF: Higher byte of Node ID
GH: Lower byte of Node ID
Identification numbers of the sequence number (A):

1: means the error is for first found node entry in the IO database
2: means the error is for the other node
Identification numbers of the IO Domains (B):

1 for IO_DOMAIN_LOCAL
2 for IO_DOMAIN_LON
3 for IO_DOMAIN_BIO2
4 for IO_DOMAIN_CAN (Not in used yet)
For explanation of the LON node types please refer to the

description of error 1209.
Identification numbers ob BIO bus node types:

0x00: SLOP2 /*BIO1 Node*/
0x02: SLOPM2 /*BIO1 Node used for first tests with BIO2*/
Error Help - 0906 Duplicate_BMK
0x03: SLOPM22 /*BIO1 Node used for first tests with BIO2*/
0x04: SLIN2 /*BIO1 Node*/
0x05: SLOPB1 /*BIO1 Node*/
0x07: SLOPSASB1 /*BIO1 Node*/
0x08: SLOPSASB2 /*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*/
0x17: SLOPM52 /*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
Identification number of SW task (IOC_TASK_ID)

Source ID
0910 COM_Busreconf
This section describes the IO error COM_Busreconf.

Summary


None.
Source ID

Causes and message
Actions
1 Bus is faulty Check lift -, groupbus: all
functional.
connected with the bus.

disappears.
addresses
and check if the
Center.
Error Help - 0951 IO_Configuration_Error
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)
x02000200: Problem retrieving information from BMK name

Extra Info x02aabbcc: Invalid entry in PCT section PCT_INPUT_OUTPUT
(aa:node_id; bb:ioType;cc:pinID )
xdddddddd: Problem reading PCT (dddddddd: subsys_id)
None.
Source ID

Causes and message
Actions
1 Incorrect IO configuration in Check/correct PCT
PCT (TX-GC/TX-R5)
2 Incorrect configuration of Verify correct configuration of
peripheral IO interface boards configurable IO interface
boards.
Error Help - 0952 EEP_BurnProbl
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 message
Actions
1 Call EBI for EEPROM
replacement (new
configuration)
Error Help - 0953 Deployment_Rule_Failure
0953 Deployment_Rule_Failure
This section describes the IO error Deployment_Rule_Failure.

Summary
Software detects wrong system configuration based on the

Description deployment rules.
Mod. 18.02.2004 New error Id. (old Id. 971)
1: Error_Bus_Architecture. Incorrect bus architecture type set in

Extra Info PCT. 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 message
Actions
1 Wrong or missing hardware Remove inappropriate
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
Error Help - 0953 Deployment_Rule_Failure
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.
Error Help - 0961 EEP_BurnProbl
0961 EEP_BurnProbl
This section describes the IO error EEP_BurnProbl.

Summary
refer to description for error number 952.

Description
None.
Extra Info
None.
Source ID
Error Help - 0970 Timer Error
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 message
Actions
1 Internal software error Use other software version
and report exact error
message.
Error Help - 1000 Bus Error
1000 Bus Error
This section describes the CPU error Bus Error.

Summary
The CPU attempted to read/write to a memory address that does

Description not exist, or the ~BERR signal was asserted to the CPU.
TX5/HX: On TX5, 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
Program counter before the fault

Extra Info
None.
Source ID

Causes and message
Actions
1 Save all error and event logs
and report to supplier hotline
or R&D
2 EMC problems Check for strong EMC source
in the building.
higher voltage cables, for
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1000_1199_CPU/err_1000_en.htm[29.6.2010. 17:10:13]
Error Help - 1000 Bus Error
example, the power supply

cables of the brake.
4 Make sure that the pcb's
are properly done.
5 Check all of the ground and
mass connections in the
cabinet
6 Defective PCB Replace PCB
Error Help - 1001 Address Error
1001 Address Error
This section describes the CPU error Address Error.

Summary
The CPU attempted to read/write data at an odd address.

Description TX5/HX: On the 68360 (68020 and higher), this can only happen
when attempting to fetch an instruction at an odd address.
Misaligned data is allowed.

Extra Info
None.
Source ID
Error Help - 1002 Illegal Instruction
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. Other instructions
are reserved by Motorola for future 68XXX family processors.
Return Program counter after the fault

Extra Info
None.
Source ID
Error Help - 1003 Zero Divide
1003 Zero Divide
This section describes the CPU error Zero Divide.

Summary
A division by 0 has been encountered by the CPU.

Description

Extra Info
None.
Source ID
Error Help - 1004 CHK Instruction
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
Error Help - 1005 TRAPV Instruction
1005 TRAPV Instruction
This section describes the CPU error TRAPV Instruction.

Summary
Overflow exception detected by the FTRAPcc, TRAPcc, TRAPV of

Description the CPU.

Extra Info
None.
Source ID
Error Help - 1006 Privilege Violation
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.
TX5/HX: On TX5 and Miconic HX, all task-level software executes in
User Mode, while the multitasking operating system and device
drivers execute in Supervisor mode.

Extra Info
None.
Source ID
Error Help - 1007 TRACE
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
Error Help - 1008 Uninitialized Int Vect
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
Error Help - 1009 Spurious Interrupt
1009 Spurious Interrupt
This section describes the CPU error Spurious Interrupt.

Summary
A CPU interrupt acknowledge cycle terminates in a bus-error, due to

Description a glitch on the IRQ line, or incorrectly configured system integration
logic.

Extra Info
None.
Source ID
Error Help - 1010 TRAP Instruction
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
Error Help - 1011 User Interrupt Vector
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
Error Help - 1012 IVXVF Reserve12
1012 IVXVF Reserve12
This section describes the CPU error IVXVF Reserve12.

Summary
Reserved for IVXVF CPU log

Description
None.
Extra Info
None.
Source ID
Error Help - 1013 Task Create
1013 Task Create
This section describes the CPU error Task Create.

Summary
The operating system failed to create a task/thread. This can result

Description in unreliable behavior.
Task number of the task which the operating system failed to create.
Extra Info
Reg_TaskID [dec.53]
Source ID
Error Help - 1014 Queue create
1014 Queue create
This section describes the CPU error Queue create.

Summary
The operating system failed to create a queue for the application.

Description This can result in unreliable behavior.
None.
Extra Info
None.
Source ID
Error Help - 1015 Operating system RTEMS
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.
This is the type indicator and is dependent upon the source of the
Extra Info 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
Identifies the API (application program interface) responsible for the

Source ID fatal or internal error.
0: INTERNAL_ERROR_CORE
1: INTERNAL_ERROR_RTEMS_API
2: INTERNAL_ERROR_POSIX_API
Error Help - 1015 Operating system RTEMS
3: INTERNAL_ERROR_ITRON_API

Causes and message
Actions
1 Faulty processor board Replace processor board of
control
2 Error in software Download other version of
software (this error should not
occur on a released version)
Error Help - 1016 New Config Reset
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

Extra Info reset (For R&D internal use)
Task identification number (depends on the SW version; for R&D

Source ID internal use)

Causes and message
Actions
1 none
Error Help - 1017 Event Handler Reset
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
Description to "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
Extra Info reset (For R&D internal use)


Causes and message
Actions
1 none
Error Help - 1018 Appl. Requested Reset
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
Extra Info R&D internal use)


Causes and message
Actions
1 none
Error Help - 1019 Memory Allocation Failure
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

Description space.
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 message
Actions
1 CADI-GC VCOM If CADI-GC is connected,
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 Check SW release notes for
long time. known problems and update
SW if proposed.
Error Help - 1020 Line1010 Instruction Emulation
This section describes the CPU error Line1010 Instruction

Summary Emulation.
The CPU tried to execute a unimplemented instruction, opcodes

Description A000-AFFF. These instructions are reserved for user expansion of
the instruction set.

Extra Info
None.
Source ID
Error Help - 1021 Line1111 Instruction Emulation
This section describes the CPU error Line1111 Instruction

Summary Emulation.
The CPU tried to execute a unimplemented instruction, opcodes

Description F000-FFFF. These instructions are reserved for user expansion of
the instruction set.

Extra Info
None.
Source ID
Error Help - 1022 HW Breakpoint
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
Error Help - 1023 FP protocol violation
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
Error Help - 1024 Format error
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
Error Help - 1025 Reserved interrupt
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
Error Help - 1026 Autovector 1
1026 Autovector 1
This section describes the CPU error Autovector 1.

Summary
The CPU was interrupted by a external device connected to IRQ1,

Description but the Exception Vector Table has not been initialized by the
device driver for that device.

Extra Info
None.
Source ID
1027 Autovector 2

Summary

TX5-ASILOG, HX-CRIPHNA: IRQ2 is reserved in the GC Hardware
Spec for future use on ASILOG or CRIPHNA, but not connected.

Extra Info
None.
Source ID
1028 Autovector 3

Summary

TX5-ASILOG, HX-CRIPHNA: IRQ3 is connected to Slot 1 (Closest
to GCIO360)

Extra Info
None.
Source ID
1029 Autovector 4

Summary

TX5-ASILOG, HX-CRIPHNA: IRQ4 is connected to Slot 2 (Slot 1 is
closest to GCIO360)

Extra Info
None.
Source ID
1030 Autovector 5

Summary

IRQ5 is used on GCIO360 for the Tacho Interface

Extra Info
None.
Source ID
1031 Autovector 6

Summary

TX5-ASILOG: IRQ6 is connected to Slot 3 (Slot 1 is closest to
GCIO360)
HX-CRIPHNA: IRQ6 is connected to the Embedded LON channel
(Buried Slot 3)

Extra Info
None.
Source ID
1032 Autovector 7

Summary

IRQ7 is the Non-maskable-Interrupt on GCIO360, but is not
connected.

Extra Info
None.
Source ID
Error Help - 1033 FP Reserved
1033 FP Reserved
This section describes the CPU error FP Reserved.

Summary
The floating-point coprocessor (68881, 68882 or built-in) informed

Description the CPU of an exception condition (Catch-all).

Extra Info
None.
Source ID
Error Help - 1034 FP Br Unord
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

Description set on unordered condition. This corresponds to the ‚BSUN bit in the
FPU exception byte.

Extra Info
None.
Source ID
Error Help - 1035 FP Inexact Result
1035 FP Inexact Result
This section describes the CPU error FP Inexact Result.

Summary
The floating-point coprocessor informed the CPU of an inexact

Description result condition.

Extra Info
None.
Source ID
Error Help - 1036 FP Div Zero
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

Description zero condition. This corresponds to the ‚DZ bit in the FPU exception
byte.

Extra Info
None.
Source ID
Error Help - 1037 FP Underflow
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
Error Help - 1038 FP Operand Error
1038 FP Operand Error
This section describes the CPU error FP Operand Error.

Summary
The floating-point coprocessor informed the CPU of an Operand

Description Error condition. This corresponds to the ‚OPERR bit in the FPU
exception byte.

Extra Info
None.
Source ID
Error Help - 1039 FP Overflow
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
Error Help - 1040 FP Signaling NAN
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-

Description Number condition.

Extra Info
None.
Source ID
Error Help - 1041 FP Unimplemented DataType
1041 FP Unimplemented DataType
This section describes the CPU error FP Unimplemented DataType.

Summary
The floating-point coprocessor informed the CPU of an

Description unimplemented 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
Error Help - 1042 MMU Reserved
1042 MMU Reserved
This section describes the CPU error MMU Reserved.

Summary
The Memory Management Unit (68851 or built-in) informed the CPU

Description of an exception condition (Catch-all).

Extra Info
None.
Source ID
Error Help - 1043 MMU Config error
1043 MMU Config error
This section describes the CPU error MMU Config error.

Summary
The Memory Management Unit informed the CPU of an

Description Configuration Error condition.

Extra Info
None.
Source ID
Error Help - 1044 MMU Illegal Operation
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
Error Help - 1045 MMU Access Level Violation
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

Description Level Violation condition.

Extra Info
None.
Source ID
Error Help - 1046 TPU Interrupt
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
Error Help - 1047 SCI Interrupt
1047 SCI Interrupt
This section describes the CPU error SCI Interrupt.

Summary
The Serial Communication Interface interrupted the CPU but there

Description was no installed interrupt handler.

Extra Info
None.
Source ID
Error Help - 1048 SPI Interrupt
1048 SPI Interrupt
This section describes the CPU error SPI Interrupt.

Summary
The Serial Peripheral Interface interrupted the CPU but there was
Description no installed interrupt handler.

Extra Info
None.
Source ID
Error Help - 1049 CPM Interrupt
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
Error Help - 1049 CPM Interrupt
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
Error Help - 1050 External H Reset
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
Error Help - 1051 PowerUpReset
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
Error Help - 1052 Watchdog Reset
1052 Watchdog Reset
This section describes the CPU error Watchdog Reset.

Summary
The CPU was reset by the hardware watchdog. This indicates that
Description the 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
Error Help - 1053 DoubleBusFaultReset
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
Error Help - 1054 ClockLossReset
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
Error Help - 1055 External S-Reset
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.
None.
Extra Info
None.
Source ID
Error Help - 1056 BErr Released Write
This section describes the CPU error BErr Released Write.

Summary
The 32-bit Motorola 68020, 68360 and newer processors may still
Description be 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.

Extra Info
None.
Source ID
Error Help - 1057 BErr Prefetch
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
Error Help - 1058 BErr Operand Read
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
Error Help - 1059 BErr Operand Write
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
Error Help - 1060 BErr MoveMultiple
This section describes the CPU error BErr MoveMultiple.

Summary
The CPU was reset due to a Bus Error while reading or writing
Description multiple 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
Error Help - 1061 BErr Exception Processing
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
Error Help - 1062 Dead Task
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
Description within 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 message
Actions
1 report problem immediately
Error Help - 1063 Group24vFail
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
Error Help - 1064 Lift24vFail
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
Error Help - 1065 12vPowerFail
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
Error Help - 1066 BatteryCharging
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
Error Help - 1067 BatteryLow50
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
Error Help - 1068 BatteryLow25
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
Error Help - 1069 BatteryDeadOrMissing
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 message
Actions
1 Check the wiring and
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
Error Help - 1070 LiftIdSwitchInvalid
1070 LiftIdSwitchInvalid
This section describes the CPU error LiftIdSwitchInvalid.

Summary
The lift-ID switch is set incorrectly

Description TX5/HX Note: The LiftID switch (On CRIP or ASILOG) is checked 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, otherwise the default setting
LiftID=1 is used instead.
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Check that the switch setting
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 ASILOG or CRIP
board
Error Help - 1071 MissingEB
1071 MissingEB
This section describes the CPU error MissingEB.

Summary
A required EB (Expansion Board) is missing

Description 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
Error Help - 1072 Saved Registers
1072 Saved Registers
This section describes the CPU error Saved Registers.

Summary
This error is reported along with another CPU error to provide extra
Description information as to the circumstances of the error. See the actual error
for more details. Only the registers most useful to locating the error
are saved.
Should the error occur on an installation immediately save the error
log and contact the VX-Center or the R&D hotline.
Value of the register.

Extra Info
Identification number of the register which was saved (R&D internal

Source ID use).
Error Help - 1073 ManualDoubleReset
1073 ManualDoubleReset
This section describes the CPU error ManualDoubleReset.

Summary
The CPU was reset because the reset button was pressed twice.
Description One 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
Error Help - 1074 Init NVRAM
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 message
Actions
1 none
Error Help - 1075 Bad_SIMM Memory
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
Error Help - 1076 CPLD_Programmed
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 message
Actions
1 1. The CPLD is blank, i.e. not none
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 none
is an older version.
Error Help - 1076 CPLD_Programmed
Error Help - 1077 OS Fault
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
Error Help - 1078 OS Restriction Failure
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

Description prohibited in 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
Error Help - 1079 Appl Restriction Failure
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
Error Help - 1080 BKPT BGND
1080 BKPT BGND
This section describes the CPU error BKPT BGND.

Summary
The CPU was reset due to a permanent breakpoint or "assert()"

Description within 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
Error Help - 1081 Page Fault on Instruction Fetch
1081 Page Fault on Instruction Fetch
This section describes the CPU error Page Fault on Instruction

Summary Fetch.
TLB miss on instruction fetch (MMU)

Description
Extra Info
none
Source ID
Error Help - 1082 Page Fault on Operand Read
1082 Page Fault on Operand Read
This section describes the CPU error Page Fault on Operand Read.
Summary
TLB miss on data read (MMU)

Description
Extra Info
none
Source ID
Error Help - 1083 Page Fault on Operand Write
1083 Page Fault on Operand Write
This section describes the CPU error Page Fault on Operand Write.
Summary
TLB miss on data write (MMU)

Description
Extra Info
none
Source ID
Error Help - 1084 Bus Error Read Protection
1084 Bus Error Read Protection
This section describes the CPU error Bus Error Read Protection.
Summary
Error on attempted read or RMW to protected space

Description
Extra Info
none
Source ID
Error Help - 1085 Bus Error Write Protection
1085 Bus Error Write Protection
This section describes the CPU error Bus Error Write Protection.
Summary
Error on attempted write to protected space

Description
Extra Info
none
Source ID
Error Help - 1086 Bus Tenure
1086 Bus Tenure
This section describes the CPU error Bus Tenure.

Summary
CPU-Bus arbiter/bus monitor timeout or other error

Description
Extra Info
none
Source ID
Error Help - 1201 PowerUpReset
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 message
Actions
1 The main disconnect was No action required
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 Check for loose wiring
the SIO
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1200_1249_LON/err_1201_en.htm[29.6.2010. 17:10:51]
Error Help - 1202 Exception68332
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 message
Actions
1 Save error logs and report to
supplier hotline or R&D
2 EMC problems Close the AS1 cabinet doors.
3 Check for strong EMC source
in the building.
5 Make sure that the SIO
are properly done.
cabinet
Error Help - 1202 Exception68332
7 Defective SIO board Replace SIO board.

8 Software failure Save error logs and report to
Error Help - 1203 ExtReset
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 message
Actions
1 RESET button pressed No action required
2 EMC problems Close the AS1 cabinet doors.
3 Check for strong EMC source
in the building.
5 Make sure that the SIO
are properly done.
cabinet
7 Voltage monitor Check +24V supply voltage
Error Help - 1203 ExtReset
8 Check for loose wiring

Error Help - 1204 DeadTask
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 message
Actions
2 Excessive VX bus traffic Check VCOM diagnostics
3 Excessive LON bus traffic Save error logs and report to
Error Help - 1205 WdogReset
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 message
Actions
2 Excessive VX bus traffic Check VCOM diagnostics
3 Excessive LON bus traffic Save error logs and report to
Error Help - 1206 MysteryReset
1206 MysteryReset
This section describes the LON error MysteryReset.

Summary
Generated when the SIOL or SIOG is reset for an unknown or

Description unlisted reason. (SIOL/SIOG ONLY)
TX5 reports CPU errors 1000 ... 1100 instead.
Reset cause ID
Extra Info
SIOL or SIOG
Source ID

Causes and message
Actions
Error Help - 1207 NiInitFail
1207 NiInitFail
This section describes the LON error NiInitFail.

Summary
Generated when the SIOL / SIOG software could not initialize the
Description LON 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 message
Actions
3 Defective EBLON board (for Replace EBLON board.
controls with LON bus e.g.
TX5)
Error Help - 1208 NewNodeFound
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
Error Help - 1209 Missing Node
1209 Missing Node
This section describes the LON error Missing Node.

Summary
Generated when a previously running node is missing on the LON

Description network 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).
Comment: A node will only be considered missing if it is listed 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 ("p_type"). The last 4
digits (yyyy) show the Node Id. ("p_id")
The "p_type" defines which type of node is affected (see the list
below).
The "p_id" defines the location-ID of the node, typically set by a
local dipswitch, or configured through the M10-keypad.
Examples:
10010002: LON channel 1, Node type=01, ID=02. (LONIO,
dipswitch=02. See list below for p-type)

10030004: LON channel 1, Node type=03, ID=04. (LFT-DPI,
dipswitch=04.)
Meaning of values for "p_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
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 message
Actions
1 No power at fixture or I/O Check power LED's and
board power wiring.
2 Damaged or defective fixture Replace damaged fixture or
or I/O board I/O board and repeat LON
freeze command if necessary.
Error Help - 1210 NiErrLogged
1210 NiErrLogged
This section describes the LON error NiErrLogged.

Summary
Generated when the LON network interface processor has logged

Description an error. the errors are defined by Echelon.
None.
Extra Info
None.
Source ID

Causes and message
Actions
supplier hotline.
2 Defective board Replace SIO or EBLON
board.
3 Unauthorized equipment Remove unauthorized
connected to LON bus equipment.
Error Help - 1211 NodeErrLogged
1211 NodeErrLogged
This section describes the LON error NodeErrLogged.

Summary
Generated when a node on the LON network has logged an error.

Description The errors are defined by Echelon.

Extra Info
None.
Source ID

Causes and message
Actions
1 Damaged or defective fixture Replace damaged fixture or
or I/O board I/O board.
2 Software failure Save error logs and call
EBI/RAND
Error Help - 1212 SvcPinEvent
1212 SvcPinEvent
This section describes the LON error SvcPinEvent.

Summary
This event is logged in normal operation when a mechanic presses

Description a 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
Error Help - 1213 NiReset
1213 NiReset
This section describes the LON error NiReset.

Summary
Generated when a reset occured on the LON network interface

Description hardware. This could be caused by an incoming message, power up
or an watchdog reset on the LON network interface hardware.
TX5/HX: Reported by the the LON network driver when the
EBLON1 or EBLON2 resets unexpectedly.
None.
Extra Info
None.
Source ID

Causes and message
Actions
board.
supplier hotline.
Error Help - 1214 DupLocID
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 message
Actions
1 Two fixtures of the same type Make sure every LON fixture
have same dipswitch setting has the correct setting.
Error Help - 1215 NiErrCounter
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 message
Actions
1 Communication errors Save error logs and call
EBI/RAND
Error Help - 1216 DiffCksGP_Konf
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 message
Actions
1 First power-up None
2 A new PCT was downloaded None
to RS
3 Download Configuration None
command
4 Software on SIO replaced None
Error Help - 1217 DiffCksIO_Konfl
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 message
Actions
1 First power-up None
2 A new PCT was downloaded None
to RS
3 Download Configuration None
command
4 Software on SIO replaced None
Error Help - 1218 TmoCksGP_Konf
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 message
Actions
1 Incorrect or corrupted PCT Download a correct
configuration file.
2 Error on RS Save error logs and call
EBI/RAND
Error Help - 1219 TmoDatGP_Konf
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.
the same lift.
SIOL: not used

SIOL or SIOG
Source ID

Causes and message
Actions
configuration file.
EBI/RAND
Error Help - 1220 TmoCksIO_Konf
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.
the same lift.
SIOL: not used

SIOL or SIOG
Source ID

Causes and message
Actions
configuration file.
EBI/RAND
Error Help - 1221 TmoDatIO_Konf
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.
the same lift.
SIOL: not used

SIOL or SIOG
Source ID

Causes and message
Actions
configuration file.
EBI/RAND
Error Help - 1222 DnLdGP_Konf
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 message
Actions
configuration file.
EBI/RAND
Error Help - 1223 DnLdIO_KOnf
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 message
Actions
configuration file.
EBI/RAND
Error Help - 1224 CksErrGP_Konf
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 message
Actions
configuration file.
EBI/RAND
Error Help - 1225 CksErrIO_Konf
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 message
Actions
configuration file.
EBI/RAND
Error Help - 1226 DoubleReset
1226 DoubleReset
This section describes the LON error DoubleReset.

Summary
Generated when SIOL or SIOG is double reset by the mechanic.

Description The configuration tables are cleared, and the configuration is loaded
again from the RS.
None.
Extra Info
None.
Source ID
Error Help - 1227 HWisLCTRL
1227 HWisLCTRL
This section describes the LON error HWisLCTRL.

Summary
Generated when SIOL or SIOG detects it is running on the wrong

Description HW type.
None.
Extra Info
None.
Source ID
Error Help - 1228 NiNoInAppBuf
1228 NiNoInAppBuf
This section describes the LON error NiNoInAppBuf.

Summary
Generated when the Application Buffers in the Network Interface (

Description MIP 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 message
Actions
board.
Error Help - 1229 NiNoInNetBuf
1229 NiNoInNetBuf
This section describes the LON error NiNoInNetBuf.

Summary
Generated when the Network 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 message
Actions
board.
supplier hotline.
Error Help - 1230 PmipNoOutQ
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 message
Actions
interface board.
Replace motherboard with
LON bus interface.
supplier hotline.
Error Help - 1231 PmipIqOverflow
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 message
Actions
board.
supplier hotline.
Error Help - 1232 SubsystemStart
1232 SubsystemStart
This section describes the LON error SubsystemStart.

Summary
VCOM on SIOL/SIOG detected another print on group-bus or lift-

Description bus 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
Error Help - 1233 SybsystemDead
1233 SybsystemDead
This section describes the LON error SybsystemDead.

Summary
VCOM on SIOL/SIOG detected another print on group-bus or lift-

Description bus 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 message
Actions
1 Noise on group- or lift-bus Check bus terminations,
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.
Error Help - 1234 VcomUpcall
1234 VcomUpcall
This section describes the LON error VcomUpcall.

Summary
VCOM on SIOL/SIOG detected an abnormal condition. This is

Description usually 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 message
Actions
1 Noise on group- or lift-bus Check bus terminations,
plugged in firmly.
3 Other defective board on Replace/remove other boards
isolate problem.
supplier hotline.
Error Help - 1234 VcomUpcall
Error Help - 1235 KonfWipe
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
Error Help - 1236 CadiReset
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
Error Help - 1237 VcomAllDied
1237 VcomAllDied
This section describes the LON error VcomAllDied.

Summary
Generated when SIOL or SIOG is detects all other subsystems

Description dead, and resets itself to try to restore communication
A110DEAD
Extra Info
None.
Source ID

Causes and message
Actions
1 Noise on Group or Lift-bus Check bus terminations,
plugged in firmly.
3 Other defective board on Replace/remove other board
isolate problem.
supplier hotline.
Error Help - 1238 KonfTableFull
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
Error Help - 1239 TelTrap
1239 TelTrap
This section describes the LON error TelTrap.

Summary
Generated when SIOL or SIOG detects a Group Input pin change,

Description for 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
Error Help - 1240 LonDistQFull
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
Error Help - 1241 LonPupXON
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
Error Help - 1242 LonDownNACK
1242 LonDownNACK
This section describes the LON error LonDownNACK.

Summary
Too many messages were sent at the same time to the LON
Description interface, and there was no more space on the Neuron chip to
allocate a buffer. The Neuron replied 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.
None.
Extra Info
None.
Source ID
Error Help - 1243 FreezeFailed
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
Error Help - 1244 LonErr44
1244 LonErr44
This section describes the LON error LonErr44.

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
1245 LonErr45

Summary
To be defined.
future use by LON
None.
Extra Info
None.
Source ID
1246 LonErr46

Summary
To be defined.
future use by LON
None.
Extra Info
None.
Source ID
1247 LonErr47

Summary
To be defined.
future use by LON
None.
Extra Info
None.
Source ID
1248 LonErr48

Summary
To be defined.
future use by LON
None.
Extra Info
None.
Source ID
Error Help - 1249 NodePowerFail
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

Extra Info to description for error number 1209 for encoding information of
extra info value.
None.
Source ID

Causes and message
Actions
1 Low voltage on LON node Check voltage on node.
board.
Error Help - 1250 BIO2_ISR_Initialisation_Error
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

Description BIO2 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 message
Actions
1 Defective hardware Replace hardware
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1250_1299_BIO2/err_1250_en.htm[29.6.2010. 17:11:14]
Error Help - 1251 BIO2_ISR_Buffering_Error
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
Error Help - 1252 BIO2_ISR_Queueing_Error
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 =

Extra Info Output queue usage

06 = Input queue is full
07 = Output queue is full
Task Id.
Source ID
Error Help - 1253 BIO2_ISR_Communication_Error
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

Description driver 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
Error Help - 1254 BIO2_ISR_Busmaster_Error
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
Error Help - 1255 BIO2_spare
1255 BIO2_spare
This section describes the BIO2 error BIO2_spare.

Summary
None
Description
None
Extra Info
None.
Source ID
Error Help - 1256 BIO2_Reserve_1256
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
Error Help - 1260 BIO2 Queue Failure
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

Description defind 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
Error Help - 1261 BIO2 Requestor Failure
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
Error Help - 1262 BIO2 Dispatcher Failure
1262 BIO2 Dispatcher Failure
This section describes the BIO2 error BIO2 Dispatcher Failure.

Summary
An error occurred according to the BIO2 dispatcher. While

Description dispatching 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
Error Help - 1263 BIO2 Missing Node
1263 BIO2 Missing Node
This section describes the BIO2 error BIO2 Missing Node.

Summary
A node is missing on the BIO2 bus. There is a BIO2 node that has
Description been recognised and does not response any more.
A BIO2 node does not response when it is scanned (node without
critical IO) or it does not send the heartbeat signal any more (node
with critical IO). It is possible that the missing node is defect, so it
has to be exchanged by a new one. It also is possible that the
missing node has been reteached. That means the node is actually
working correct but the host can not receive any answers from the
old address of the node. The host can not tell wheter a new node is
installed or if an old one has been re-teached. In this case you have
to make a freeze.
0x0000yyxx
Extra Info
xx = access side (01 = front side/02 = rear side)
yy = floor number
Task Id.
Source ID

Causes and message
Actions
1 No communication to BIO2 Check BIO2 node board on
board related floor
2 Loss of supply on BIO2 board Check BIO2 node board on
related floor
3 Re-teach of BIO2 node Execute freeze command
after verification of function of
node.
4 Faulty hardware (BIO2 board) Replace boar.
Error Help - 1263 BIO2 Missing Node
Error Help - 1264 BIO2 Node Alive Again
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

Description bus is detected alive again.
0x0000yyxx: xx = floor number / yy = access side

Extra Info
Task Id.
Source ID
Error Help - 1265 BIO2 No_Address_Left
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
Description that 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 message
Actions
1 Too many teach in's. Restart System
Error Help - 1266 BIO2 Unsupported_Protocol
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 message
Actions
1 BIO2 node with incompatible Remove the board (BIO2
version. node) from the bus because it
is not supported by the
control.
Error Help - 1267 BIO2 Multiple Node on address
1267 BIO2 Multiple Node on address
This section describes the BIO2 error BIO2 Multiple Node on

Summary address.
Two or more nodes with the same node address are or were
Description detected (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 message
Actions
1 Repeat teach-in for both BIO2
nodes
Error Help - 1268 BIO2 Multiple BIOGIO 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
Description detected 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
Error Help - 1401 SW_Event
1401 SW_Event
This section describes the VF error SW_Event.

Summary
General software event

Description
Normal operation event

Extra Info
None.
Source ID
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1400_1499_VF/err_1401_en.htm[29.6.2010. 17:11:22]
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
Error Help - 1404 VarOutOfRange
1404 VarOutOfRange
This section describes the VF error VarOutOfRange.

Summary
Exceeded range for parameter value

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 RAM data destroyed Double-reset PGO
2 ROM data destroyed Call EBI for software
replacement
Error Help - 1405 JHC_Pressed
1405 JHC_Pressed
This section describes the VF error JHC_Pressed.

Summary
Stop button JHC pressed

Description

Extra Info
None.
Source ID
Error Help - 1406 JHM_Pressed
1406 JHM_Pressed
This section describes the VF error JHM_Pressed.

Summary
Stop button JHM pressed

Description

Extra Info
None.
Source ID
Error Help - 1407 JHSG_Pressed
1407 JHSG_Pressed
This section describes the VF error JHSG_Pressed.

Summary
Stop button JHSG pressed

Description

Extra Info
None.
Source ID
Error Help - 1408 Supply24V_OFF
1408 Supply24V_OFF
This section describes the VF error Supply24V_OFF.

Summary
No 24V supply
Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Missing or defective 24V Check 24V supply
supply
2 Missing WD (resistor-diode) Install appropriate device
device on the brake (electro- properly
magnetical interferences)
3 Net power failure
Error Help - 1409 DriveLocked
1409 DriveLocked
This section describes the VF error DriveLocked.

Summary
Drive has been blocked by control

Description

Extra Info
None.
Source ID
Error Help - 1410 UnknownFloor
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 message
Actions
1 Number of learnt floors does Check Selector Translation
not correspond with PCT Table
Error Help - 1411 SF_Fault
1411 SF_Fault
This section describes the VF error SF_Fault.

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

Causes and message
Actions
SF and SF1
Error Help - 1412 SF1_Fault
1412 SF1_Fault
This section describes the VF error SF1_Fault.

Summary
SF1 relay error

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
SF and SF1
1413 KB_Fault
This section describes the VF error KB_Fault.

Summary
KB contacter error
Description The brake contacts KB or KB1 do not switch properly.
Software expects both KB and KB1 information
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Defective brake contacts Check contact adjustment
2 Malfunction of mechanical Check the brake
brake
3 Observe the brake during
opening - both sides should
open symmetrically
Error Help - 1414 ShaftChecksum
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
Error Help - 1415 StartFailed
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 message
Actions
1 BARMAG error ® red LED on Perform reset on BARMAG
ER113 ER113
2 Open safety circuit (after- Check door contacts
effect)
Error Help - 1416 TargetFailure
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
Error Help - 1417 CarNotAtLevel
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 message
Actions
1 Inaccurate setting of Check BARMAG parameters
BARMAG parameters
Error Help - 1418 CarOutOfFloor
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 message
Actions
1 Trip interruption caused by Check wiring PGO-BARMAG
BARMAG
Error Help - 1419 KSE_Int_Fail
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
Error Help - 1420 KS_MagnetPos
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
Error Help - 1421 KSE_MagnetPos
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
Error Help - 1422 KS_Bounce
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
Error Help - 1423 KSE_Bounce
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
Error Help - 1424 SynchFailed
1424 SynchFailed
This section describes the VF error SynchFailed.

Summary
Unsuccessful synchronisation trip

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 KS on bottom floor not found Check KSE distance
2 Check KS magnet
3 After-effect of a previous Check system for previous
error errors
Error Help - 1425 IO_NotPresent
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 message
Actions
1 Destroyed ROM data Call EBI for software
replacement
Error Help - 1426 VF_Notstop
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 message
Actions
1 Improper connection PGO- Check connection PGO-
BARMAG BARMAG
Error Help - 1427 DeltaS_2BP
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 message
Actions
1 Possible error causes Actions to be taken
2 Inaccurate parameter setting Check BARMAG drive
(BARMAG) parameter (CADI/SMLCD)
Error Help - 1428 TEL_Request
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
Error Help - 1429 TEL_Provide
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
Error Help - 1430 TEL_Reply
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
Error Help - 1431 TEL_Get
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
Error Help - 1432 TEL_ReadQueue
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
Error Help - 1433 TEL_VCOMopen
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
Error Help - 1434 Unknown_TEL
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
Error Help - 1435 No_ANT_PCT (Not Used)
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
Error Help - 1436 No_VF20_PCT
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 message
Actions
1 Wrong PCT for the concerned Change PEROM with a
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 message
Actions
1 Engine temperature too high Elevator system will recover
by itself under normal
circumstances. Otherwise, put
the elevator temporarily out of
service
2 Missing temperatur element Check installation
KD150
Error Help - 1438 NoIncrement
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 tacho Check tacho and wiring
Error Help - 1439 InvldMovement
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 message
Actions
1 Improper parameter settings Check BARMAG parameter
(BARMAG) values (CADI/SMLCD)
Error Help - 1441 OverSpeedKSE
1441 OverSpeedKSE
This section describes the VF error OverSpeedKSE.

Summary
Speed exceeded in shaft end

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Improper parameter settings Check BARMAG parameter
(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
Error Help - 1443 DirNotAllowed
1443 DirNotAllowed
This section describes the VF error DirNotAllowed.

Summary
Wrong direction in shaft end

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 Manual trip on cabin roof in Reset ® Synchronization trip
wrong direction in shaft end
area
2 If still necessary, perform a
learn trip
Error Help - 1444 PosLost_Tacho
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 message
Actions
1 Reset ® Synchronization trip
learn trip
Error Help - 1445 PosLost_KS
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 message
Actions
learn trip
Error Help - 1446 PosLost_KSE
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 message
Actions
learn trip
Error Help - 1447 FloorPrec
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 message
Actions
1 Elevator system improperly Improve elevator adjustment
adjusted
Error Help - 1448 RSK_Fault
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 message
Actions
RSK and RSK1
Error Help - 1449 RSK1_Fault
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 message
Actions
RSK and RSK1
Error Help - 1450 TIF_WriteErr
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
Error Help - 1451 TIF_ReadErr
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
Error Help - 1452 NoStartOK
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
Error Help - 1453 SK ErrorStart
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
Error Help - 1454 SK ErrorRun
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
Error Help - 1455 SynchTrip
1455 SynchTrip
This section describes the VF error SynchTrip.

Summary
A synchronisation trip has been started

Description
Extra Info
None.
Source ID
Error Help - 1456 LearnTrip
1456 LearnTrip
This section describes the VF error LearnTrip.

Summary
A learn trip has been started

Description
Extra Info
None.
Source ID
Error Help - 1457 CorrTrip
1457 CorrTrip
This section describes the VF error CorrTrip.

Summary
A correction trip has been started

Description
Extra Info
None.
Source ID
Error Help - 1458 Inv_VF20_PCT
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.
Error Help - 1458 Inv_VF20_PCT
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 message
Actions
1 Parameter value wrongly set Adjust appropriate parameter
in PCT with CADI/SMLCD
2 PCT structure invalid (one or Replace PCT (Perform a
more parameters missing) PCT-download with CADI or
change PEROM)
Error Help - 1459 Inv_BMG_Param
1459 Inv_BMG_Param
This section describes the VF error Inv_BMG_Param.

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

Description not 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 message
Actions
1 Communication PGO - Check RS232 connection
BARMAG not PGO - BARMAG
successful/impossible
2 Communication PGO - Perform double-reset on
BARMAG had been PGO and reset on BARMAG,
interrupted wait approx. 5 minutes (!)
Error Help - 1460 LastBlockTime
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
Error Help - 1461 LearnFailed
1461 LearnFailed
This section describes the VF error LearnFailed.

Summary
Unsuccessful learn trip

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
1 After-effect of a previous Check system for previous
error errors
Error Help - 1462 LearnMesProbl
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
Error Help - 1463 TEL_Send
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
Error Help - 1464 NoBpReaction
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 message
Actions
1 Check wiring PGO-BARMAG
2 Check BARMAG ER113
module
Error Help - 1465 Jump_Tacho
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
Error Help - 1466 SK_Bridging
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 message
Actions
1 Malfunction of door bridging Check relays VRKUET and
KUET/KUET1
Error Help - 1467 PosLost_IUET
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 message
Actions
1 Reset PGO, then perform a
Learn Trip
Error Help - 1468 Supply24VOn
1468 Supply24VOn
This section describes the VF error Supply24VOn.

Summary
24V supply activated

Description
Extra Info
None.
Source ID
Error Help - 1469 VF20_Blocked
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 message
Actions
1 Reset BARMAG. If not
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
Error Help - 1470 Safety110V
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
Error Help - 1471 SafetySPT
1471 SafetySPT
This section describes the VF error SafetySPT.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
Error Help - 1472 SafetyKNE
1472 SafetyKNE
This section describes the VF error SafetyKNE.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
Error Help - 1473 SafetyRTS
1473 SafetyRTS
This section describes the VF error SafetyRTS.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
Error Help - 1474 SafetyEnd
1474 SafetyEnd
This section describes the VF error SafetyEnd.

Summary

Description
None.
Extra Info
None.
Source ID

Causes and message
Actions
Error Help - 1475 SW_BlockPerm
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 message
Actions
1 Solve the problem and reset
the system
Error Help - 1476 DataDestroyed
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
Error Help - 1477 VF_StartError
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 message
Actions
(BARMAG) necessary) BARMAG
parameter with CADI/SMLCD
Error Help - 1478 VF_ShortBrake
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 message
Actions
(BARMAG) necessary) BARMAG
parameter with CADI/SMLCD
Error Help - 1479 VF_StopSpeed
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
Error Help - 1501 Invalid Car Position
1501 Invalid Car Position
This section describes the Travel Control Ext error Invalid Car
Summary Position.
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 when the car
position is unknown and during a 'sync trip' .
Actual car position (decimal value in [mm]) when the error occurred.
Extra Info
Identification number of the source code file

Source ID

Causes and message
Actions
1 Car position encoder was Do a learn trip
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/1500_1699_Travel_Control_Ext/err_1501_en.htm[29.6.2010. 17:11:59]
Error Help - 1502 Position Jump
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

Description two 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 calcualtes wrong a
false floor position 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
Idnetification number of source file

Source ID

Causes and message
Actions
1 EMC problems with car Check wiring of car position
position encoder (absolute encoder
encoder)
2 Faulty car position encoder Replace encoder
3 Faulty wiring of car position Check wiring and connectors
encoder
Error Help - 1503 Defect_MoSis_Sensor
1503 Defect_MoSis_Sensor
This section describes the Travel Control Ext error

Summary Defect_MoSis_Sensor.
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 message
Actions
1 Sensors made of steel Change sensor to Aluminium
causes problems of detection type.
at low 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.
closed.
Refer also to wiring diagram for contacts causing the error.
Extra Info
development only.
Identification number of source file

Source ID

Causes and message
Actions
1 Bad landing door lock
contact(s) KV
Error Help - 1505 Invalid Floor Position during Trip
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

Description when:
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 message
Actions
1 Missing floor magnet or floor Check the hardware in the
vane (KUET/KUET2). hoistway.
2 Faulty input on interface Check/replace the interface
Error Help - 1505 Invalid Floor Position during Trip
board for KUET/KUET2. board.

3 Mechanical problem with Check fixation of vane(s).
fixation of floor vane.
Error Help - 1506 Invalid Floor Position in Standstill
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

Description when:
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 message
Actions
1 Missing floor magnet or floor Check the hardware in the
vane (KUET/KUET2). hoistway.
2 Faulty input on interface Check/replace the interface
Error Help - 1506 Invalid Floor Position in Standstill
board for KUET/KUET2. board.

3 Mechanical problem with Check fixation of vane(s).
fixation of floor vane.
Error Help - 1507 Brake ON standstill
1507 Brake ON standstill
This section describes the Travel Control Ext error Brake ON

Summary standstill.
The control detects that a brake is released (ON) in standstill. A

Description brake 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

Extra Info hexadecimal number (0xABCDEFGH) has the following meaning:
Value 'A': Internal state of brake control (brake_state) 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': not used

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
Error Help - 1507 Brake ON standstill

Causes and message
Actions
1 Faulty brake contact(s) KBx Check the function of the
brake contacts.
3 Mechanical problem on the Check the brake. Observe the
brake brake when it opens. Both
sides of the brake should
open symmetrically.
type.
5 Faulty input on the interface Verifiy faulty input and
board for the KB inputs replace board
(ASILOG, ASIX . .etc).
Error Help - 1508 Brake not ON start
1508 Brake not ON start
This section describes the Travel Control Ext error Brake not ON
Summary start.
The control detects that the brake does not open (open = ON)
Description during 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.


The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'B': not used

0]
0]
else 0]
0]
Idnetification number of source file

Source ID
Error Help - 1508 Brake not ON start

Causes and message
Actions
brake contacts.
open symmetrically.
type.
Error Help - 1509 Brake OFF Run
1509 Brake OFF Run
This section describes the Travel Control Ext error Brake OFF Run.
Summary
The control detects that a brake is closed (OFF) during a trip. A

Description brake contact KB is inactive during a trip indicating that the
respective brake (lever) is not in the open position.


The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'B': not used

0]
0]
else 0]
0]

Source ID
Error Help - 1509 Brake OFF Run

Causes and message
Actions
brake contacts.
open symmetrically.
type.
Error Help - 1510 Brake not OFF stop
1510 Brake not OFF stop
This section describes the Travel Control Ext error Brake not OFF
Summary stop.
The control detects that the brake does not close (closed = OFF) at
Description the 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.


The values are:
0: BRAKE_INIT
2: BRAKE_CLOSED
3: BRAKE_OPEN
4: BRAKE_OPENING
5: BRAKE_CLOSING
Value 'B': not used

0]
0]
else 0]
0]

Source ID
Error Help - 1510 Brake not OFF stop

Causes and message
Actions
brake contacts.
open symmetrically.
type.
Error Help - 1511 Traction Media Broken
1511 Traction Media Broken
This section describes the Travel Control Ext error Traction Media
Summary Broken.
The control detected a broken traction media.

Description
Extra Info

Source ID

Causes and message
Actions
1 Failure of electrical wiring of Check the wiring and input,
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 Check for a slack or broken
or is broken traction media, repair or
replace as required
Error Help - 1512 SI Communication Lost
1512 SI Communication Lost
This section describes the Travel Control Ext error SI

Summary Communication Lost.
The control detects a lost communication to the CAN based shaft

Description info system(MoSIS / SALSIS)
Extra Info

Source ID
Error Help - 1513 SI UET Fault
1513 SI UET Fault
This section describes the Travel Control Ext error SI UET 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.

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
Error Help - 1514 SI FLOOR Fault
1514 SI FLOOR Fault
This section describes the Travel Control Ext error SI FLOOR Fault.
Summary
This error is logged if the MoSIS reports an error condition related

Description to the floor sensor function of MoSIS. The extra info describes the
message sent by MoSis 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
Error Help - 1515 SI Internal Log
1515 SI Internal Log
This section describes the Travel Control Ext error SI Internal Log.
Summary
This error is reported if MoSIS logs an entry in its internal error log.
Description An internal error is usually reported together with one or more of the
following errors:
0131 MoSis_KNE_Fault .
1513 MoSis_UET_Fault
1514 MoSis_FLOOR_Fault
The message contains the contents of the MoSIS internal error log

Extra Info following meaning per digit: S00000YY
S: Channel number of MoSIS that reports the error. There are 2

channels (1,2) for redundancy.
YY= MoSIS internal ID of the error being logged (Hexadecimal):

Error Numbers:
enum / Name / Meaning
$00 / NoError / No error/warning or info to report
$01 / SoftwPosErr / Software plausibility check failed
$02 / HardwPosErr / Hardware plausibility check failed
$03 / ERR_INTERNAL_FLOOR_ERR / An error ocurred during
comparison between the RAM-contents of channel A and B. KNE
will open, but the floor - RAMS will only be erased if this error keeps
remaining ( 5 errors without 1000 OKs).
$04 / FloorRAMsErasedCmd / Floor positions have been erased
due to a ConfigCommand
$05 / RAMABexchErr / Communication error between channel A
and B when exchanging the RAMs content
$06 / PosABdoNotFit / Difference of Position of channel A and B is
greater than 100mm
Error Help - 1515 SI Internal Log
$07 / PosExchErr / Communication error between channel A and B

when exchanging absolute position
$08 / FloorsErasedCausedByB / Floor positions of A have been
erased due to B erased its floor positions
$09 / RelaisTestFail / Relais Test every 12 h failed
$0A / EmergencyMeasureOrRelais / MoSiS detected too much
Errors; it is in emergency state. None of the relais will open until new
power up
Power to MoSIS must be switched off (JH) and then on again to
clear this error
$0B / ERR_FLOORS_ERASED_STRANGE / When MoSIS has
confirmed its Position in every channel of its own and between the
two channals after power up - to do this its is necccassary MoSIS
moved minimum 4mm after power up - and it recognises it is on a
strange place, it will erase the floor-rams.)
Rem: powering up in precommisioned state will allways cause this
error
$0C / WARNING_MEASURING_SYSTEM / Measuring-System-
Hardware gave a warning
$0D / ERR_VERSIONS_AB_NOT_FIT / Software-Versions of
channal A and B do not fit
$0E / ERR_FLOOR_AGREEMENT / Floor position from B does not
fit the floor position from A
$0F / ERR_UNINTENDED / MoSIS is in emergency_state due to
unintended car movement detection
$10 / ERR_SPEED_FILTER / speed-filter failed
$11–7F / … / Reserved for additional errors (Allocated sequentially)
$80-FF / … / Reserved for SW warnings and info’s for development
use…etc. (Not reported to CADI)

Source ID
Error Help - 1516 No Target Lower KSE Slowdown
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
Description active) and no target (stop) is set in Travel Control logic.
Extra Info

Source ID
Error Help - 1517 No Target Upper KSE Slowdown
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
Description active) and no target (stop) is set in Travel Control logic.
Extra Info

Source ID
Error Help - 1518 JNH active
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
Error Help - 1519 Bypass Plug Conflict
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
Error Help - 1520 Door Bypass Recall
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
Error Help - 1521 SI Teach-in Mode
1521 SI Teach-in Mode
This section describes the Travel Control Ext error SI Teach-in

Summary Mode.
Preparation for learn trip aborted because SALSIS is in teach-in

Description mode.
not used
Extra Info

Source ID
Error Help - 1522 SI ETSL Info
1522 SI ETSL Info
This section describes the Travel Control Ext error SI ETSL Info.
Summary

Description to the ETSL function of MoSIS. The extra info describes the
message sent by MoSis together with the status change of floor
sensor.
copy paste-----
Extra Info The extra information is a 8 digit hexadecimal code with the
following meaning per digit: ABCDEFGH
tbd

Source ID
Error Help - 1523 SI KNE Info
1523 SI KNE Info
This section describes the Travel Control Ext error SI KNE Info.
Summary

Description to the KNE function of MoSIS.

Extra Info following meaning per digit: ABCDEFGH
tbd
Identification number of source file (software)

Source ID
Error Help - 1524 CAN Sync Send
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

Description message.

not used

Source ID
Error Help - 1525 CAN Controller
1525 CAN Controller
This section describes the Travel Control Ext error CAN Controller.
Summary
tbd
Description

not used

Source ID
Error Help - 1526 ZSB Fault
1526 ZSB Fault
This section describes the Travel Control Ext error ZSB Fault.
Summary
Error on brake control (MX control). The software monitors the

Description status of the input KZSB (feedback signal of the relay ZSB on the
brake module).
if the contact is picked up, and is detected during preparation of the

trip, then the extra info = 1 [i.e. the status of the contact]
if the error is reported during a trip, it is because the ZSB contact
dropped during a trip.

Extra Info following meaning per digit (ABCDEFGH). Decoding of the value:
H: Status of the ZSB contact

00000001: KZSB on
00000001: KZSB off

Source ID
Error Help - 5000 No Error
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 message
Actions
1 The connection between the Check data connection
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
file:///D:/Arhiva/Certus/Liftovi%20Dokumentacija/CADY%20Errors/errors/5000_5099_Remote_Monitoring/err_5000_en.htm[29.6.2010. 17:12:11]
Error Help - 5002 No Physical Data Connection to Control Center
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 message
Actions
1 Connection physically Check data connection (e.g.
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)
Error Help - 5003 Data Line to Control Center Busy
5003 Data Line to Control Center

Busy
This section describes the 5000_5099_Remote_Monitoring error

Summary Data Line to Control Center Busy.

physically established because the line was busy
Extra Info
Source ID

Causes and message
Actions
1 Control center not able to Do nothing. Wait for next
answer call of elevator (e.g. calling attempt.
too busy)
Error Help - 5004 No Logical Data Connection to Control Center
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 message
Actions
1 Bad oder wrong configured Check configuration (e.g.
phone line connection country code)
Error Help - 5005 Max Data Connection Attempts to Control Center
5005 Max Data Connection Attempts

to Control Center

Summary Max 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
Error Help - 5006 Max Data Connection Time to Control Center Exceede
5006 Max Data Connection Time to

Control Center Exceede

Summary Max 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 message
Actions
1 The max. idle time was Check configuration (e.g.
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)
Error Help - 5007 Data Communication Device Dead
5007 Data Communication Device

Dead

Summary Data 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 message
Actions
1 The connection between the Check data connection
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
Error Help - 5008 Data Communication Device Alive

Alive

Summary Data 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
Error Help - 5009 Data Communication Device Faulty

Faulty

Summary Data 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 message
Actions
1 Device internal failure Replace the CLSD PCB
(communication line sharing
device)

Errors SCH

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

Errors SCH

Uploaded by

Copyright:

Available Formats

Cadi GC Home Page

0...149 Travel Control

0112 Pressure Switch

0140 Safety T4B

200...299 Door Control

300...399 Varidor70 Door Drive

0425 SCT/PCT write error

0483 Modem Answering

0624 Receive state wrong

0653 Charge contactor failure cc2

0724 Power Supply

0764 Bad thermistor

1024 Format error

1082 Page Fault on Operand Read

1500...1699 Travel Control Ext

1525 CAN Controller

This section describes the Travel Control error NormalStop.

Normal termination of the trip. Note: The default event handling

ID Possible causes of Actions to be taken

This section describes the Travel Control error ExceptionMC.

Exceptions of microprocessor. The system jumps to the exception

ID Possible causes of Actions to be taken

connections in the cabinet

This section describes the Travel Control error NoKSE_STDSTL.

ID Possible causes of Actions to be taken

7 Check the connection from the

This section describes the Travel Control error InvldMovement.

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

ID Possible causes of Actions to be taken

This section describes the Travel Control error SH_on_STDSTL.

The contactor SH or SH1 is detected energised during standstill

ID Possible causes of Actions to be taken

This section describes the Travel Control error SB_on_STDSTL.

00 (hex)/ 0 (dec):,: RB fault (for MX-GC) :RB open before starting a

ID Possible causes of Actions to be taken

This section describes the Travel Control error SH_Fault.

The auxiliary contacts of SH / SH1 (or RH / RH1) opened while the

Source-ID 104 (MONITOR)

Source-ID 114 (PREPARE_TRIP)

ID Possible causes of Actions to be taken

Reduce value for parameter

This section describes the Travel Control error SB_Fault.

The SB auxiliary contact opened when the car was moving or an

ID Possible causes of Actions to be taken

This section describes the Travel Control error KB_Fault.

The brake contacts KB or KB1 do not switch properly. Travel Control

ID Possible causes of Actions to be taken

This section describes the Travel Control error FC_Fault.

a) The frequency converter requested an emergency stop.

ID Possible causes of Actions to be taken

This section describes the Travel Control error FC_Block.

Motor Control state is 'blocked'.

ID Possible causes of Actions to be taken

5 U_ZK > UZK_MIN Chopper resistor not

This section describes the Travel Control error DirectionErr.

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

ID Possible causes of Actions to be taken

This section describes the Travel Control error OverSpeed.

The error is logged in the following cases:

b) that the speed reference (velocitiy_ref) was outside the allowed

max velocity_ref for relevel trips: 300

0: speed calculated from position tacho (car) too high

ID Possible causes of Actions to be taken