|
使用服务器M1-1-2-1查看到的所有故障记录，所有事件类别分为I/W/F/E I | | | | | | | | | |
| Elite - Visible only in the ALL Menu Event Trace |
故障代码 | | | | | | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | Different addresses found for “mirrored I/Os” (e.g. IO0032 and IO3000) Check all level- and opening-related I/Os | | | | | LV1 和LV2 信号错误未得到 L V1 和 LV2 信号 |
| | | | lv1 and lv2 edge was missed |
| | | | System was reset by Elite Service expert |
| | | | Time was changed using SVT function |
| | | | Time was adjusted for summer time |
| | | | Time was adjusted for winter time |
| | | | Time has not yet been set |
| | | | The external watchdog caused a reset |
| | | | |
| | | | |
| | | | Sending car bus CAN message failed |
| | | | Publishing car bus CAN message failed |
| | | | Disturbances on the car CAN bus have been detected. Check termination, wiring, shielding |
| | | | Group bus CAN messages cannot be sent |
| | | | |
| | | | Sending group bus CAN message failed |
| | | | Publishing group bus CAN message failed |
| | | | Disturbances on the group CAN bus have been detected. Check termination, wiring, shielding |
| | | | Gateway communication failure | | | | | The real time clock was corrupted and has now been reset to 01.01.2004. Use M-1-3-8-1 to set the correct date/time |
| | | | Time synchronization between NMS and Controller greater than 1h |
|
0039 | | | Numerical division by 0 during ZKIP au- thentication |
| | | | No CAN communication to CARIO board (i.e. TOCB, COPG, CSPB) Check CAN termination, wiring | | | | | The GECB time was adjusted by the RTC |
| | | | Some parameters are out of range Use M-3-2 to set the default values |
| Operational Control Sub System |
| | | | 由于驱动错误，OCSS 不可用。NAV 这个模式通常同样会发Th在检修NIS 之后和寻址COR 启动之 前。 |
| | | | 处于 EPO 时电梯不能运行；恢复后容许电梯运行。 | NU (017) NUSD (018) NUSG (019) | | | | 电梯门不能关，超时保护（丢失DCL,DFC,DW 信号时出现） | | | | | | | | | | | | 在设定的时间内，电梯不能响应呼梯信号超时保护（例如：当有人用手长时间挡住门时） | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | |
| | | | The light within the car has failed. |
| | | | The elevator is overloaded for more than 30 seconds. |
| | | | The elevator is full for more than 30 sec- onds. |
| | | | The elevator is attempting to correct posi- tion for more than 2 minutes. |
| | | | The elevator is initializing after a power on for more than 2 minutes. |
| | | | The elevator is performing a park run for more than 2 minutes. |
| | | | The elevator is performing wildcar opera- tion for more than 5 minutes. |
| | | | The elevator is in NOR operation for more than 5 minutes. Could be the result of a stuck reversal device. |
| | | | Automatic Rescue Operation was activat- ed due to a power failure or via OFT test menu. |
| | | | One of the following features is pro- grammed in the E2PROM but not yet en- abled by Service Panel: EFO EPO CLR HBP Use “Startup-Enable Features” to acti- vate these features. | EFO-POS EPO- POS IO1000 CLR HBP-POS | | | | The elevator is in NAV mode for more than 30 seconds. This event is only logged when the system is in NAV mode and no OOS Blockage is detected for 30 seconds.. |
| | | | Wheel Chair Door Close Button contact permanent active | | | | | Rear Wheel Chair Door Close Button contact permanent active | | | | | Detected Earthquake Flash from external system |
| | | | EQO restart condition active, but not ar- rived to the nearest floor within 4 minute 10 sec. |
| | | | EQO restart condition active with high- gal, but not run to the nearest floor within 10 sec. |
| | | | Started EQAR after EQO operation with just low-gal active |
| | | | EQAR aborted by causes like EFO or EFS active, PFO active, other earthquake sensor active except for low-gal, discon- nected remote service under defined condition which EQAR allowed with re- mote service connection | | | | | EQAR start was not permitted by drive for 60 sec after completion EQO general operation. |
| | | | Allowed to return to normal operation af- ter completion of temporary serviceable check thru floor-to-floor, top to bottom and bottom-to-floor running. |
| | | | No maintenance since EQAR for defined time | | | | | | | | | | Selected events (max: 3) by SVT is de- tected for pre-determined time. | |
|
|
|
| RfsEvC-T RfsEvxGr RfsEvxId RfsEvOpx | Motion Control Sub System |
| | | | Drive set the position invalid, resulting in COR run |
| | | | 修正寻址运行（在NIS，NAV 恢复正常后）复位运行 |
| | | | |
| | | | |
| | | | | | | | | 由于 SE 信号丢失，电梯不能运行→可以检查门的安全链触点 |
| | | | OTS input has been activated | | | | | no hoistway signals have been detected during Fast Run (missing DZ) | | | | | duration of Slow Run is longer than 3P- time (i.e. no stop signal has been detect- ed) | | | | | duration of Rescue Run is longer than 3P-time (i.e. no stop signal has been de- tected) | | | | | 门区信号丢失,直到电梯停止也未能找到信号停车时DZ 信号丢失 | | | | | |
| | | | |
| | | | 驱动器准备好了运行时发Th错误(例如:缺少了称重信息时) |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | 驱动器报告了一个急停故障(可以查看 MCB 的故障记录)查看变频器故障 |
| | | | |
| | | | |
| | | | It was detected that the drive was stopped while it was supposed to run (so called “Running but Idle lockup”). To avoid a blockage, a correction run is initiated. | | | | | 抱闸继电器 1TH 未接通,驱动器电力断电降温钢带检测 连至 ITH 的 DBR 触点打开，变频器关闭并冷却热敏开关 |
| | | | |
| | | | |
| | | | 110V 交流供电中断 5 秒以上报错缺少110电压或者电压低于110V |
| | | | --> see description for blinking message |
| | | | Power supply (110VAC) died and came back before complete power down |
| | | | 下减速开关1LS 和 下减速开关2LS 信号同时被激活(检查涉及到此位置的供电线路) |
| | | | € see description for blinking message ‘ACD Fault!” | | | | | 一些RSL 的 I/O 接口被设定为 00-0 和 01-0。 当前只有一个 I/O 接口被检测了.(TCI 的 I/O 是 691,确保此接口为一个有效地址)IO 地址不正确，不允许设置为 00-0 和 01-0 检修IO地址 | | | | | Indicates that ADO is enabled and the conditions were met to begin an ADO run, but the DriveSpeedCheck signal did not toggle on this run Check CAN bus connection | | | | | The UCM relay is stuck. Check hardware See also Feature Setup Description. 轿厢意外移动 | | | | | | | | | | Unintended Car Movement (leaving the door zone with open doors under motor) was detected by the GECB or by the Drive or both.轿厢意外移动 For more information, see the Feature Setup Description. | | | | | Advanced Brake Lift was aborted be- cause the door was not fully closed 10 seconds after the brake was lifted. | | | | | The OVF20 has started its Learn Run. | | | | | |
| | | | |
| | | | The TES or PES button was pushed without seeing a prior “/DW in FR” or “/DW in SR” event. If a prior “/DW in FR” or “/DW in SR” event is seen, then that would be an indication of the normal pro- cedure to enter the hoistway, so is not reported. |
| | | | The DW signal is missing for 5 minutes, but no HAD and no DTC was detected. |
| | | | The DFC signal is missing for 5 minutes, but no HAD and no DTC was detected. |
| | | | | | | | | | | | | | The input 2nd Start Enable opened (e.g. active BID). |
| | | | |
|
0246 | | | |
| | | | |
| | | | |
| | | | |
| | | | | | | | | When the drive overheat signal is re- ceived from Drive thru CAN bus. Check GDCB events | | | | | CAN communication fault between GECB and UCM board Check CAN line between GECB and UCM board | | | | | When the inconsistency is detected for front SO relay Check SO relay for front door Check IO FDZ(1195), FSO(1197) and CHK_SO(1196) | | | | | |
| | | | An error occurred during releveling on a system with EN-required UCM. Further relevel runs will be prevented at the floor where the problem occurred. Relevel runs will be re-enabled when the car moves to another floor. | | | | | The ET_S1-4 expectation message from the Drive was not received for 3 seconds. check CAN-wiring check CAN-LEDs | PX2.1=4 or 5 ET_P1(1257) ET_P2(1258) ET_S1(1259) ET_S2(1260) ET_P3(1261) ET_P4(1262) ET_S3(1263) ET_S4(1264) | | | | ETSD with reed switch monitor function has detected a problem. This is the case if the ET_P1-4 signals do not match their expected value in a doorzone, or if the ET_S1-4 signals do not match their ex- pected values during the run, or if the configuration of the parameters and Ios is inconsistent. check relays check configuration and Ios See subcode ‘x’ for details | PX2.1=4 or 5 ET_P1(1257) ET_P2(1258) ET_S1(1259) ET_S2(1260) ET_P3(1261) ET_P4(1262) ET_S3(1263) ET_S4(1264) | | | | The safety chain opened between DFC and UIB/DIB within the first step ETSD zone, as indicated by ET_P1 and ET_P2. verify Drive ETSD settings, “ETP Spe %DutySpe” and “ETP2 Spe %Duty” verify ET_P1-4 sensor adjustment | PX2.1=4 or 5 ET_P1(1257) ET_P2(1258) ET_S1(1259) ET_S2(1260) ET_P3(1261) ET_P4(1262) ET_S3(1263) ET_S4(1264) | | | | The ASCB-controlled relays, ET_S2 and/or ET_S4 switch open too late during acceleration in comparison to the GECB- controlled relays, ET_S1 and/or ET_S3. readjust ASCB settings | PX2.1=4 or 5 ET_P1(1257) ET_P2(1258) ET_S1(1259) ET_S2(1260) ET_P3(1261) ET_P4(1262) ET_S3(1263) ET_S4(1264) | | | | 8LS2 input was activated Note: Hydraulic controllers only |
| | | | PLS1 input has been activated | | | | | motorized valve got stuck |
| | | | UIS & DIS have been detected without DZ. This happens when one of LV relays is defect. | | | | | The LCB_IIC detected a fault at the 3- line-power-supply (i.e. phases missing or turned) | | | | | The brake current (hydro: valve current) was missing during run. | | | | | LSVF-W reported an error (Drive Not Ready) | DRV_TYP=102 C-TYPE (see MCB) | | | | During deceleration the speed of the car was too high to perform ADO or Relevel- ing. Therefore ADO and RLV are not al- lowed any more | | | LSVF-W -ON | | LSVF-W has been powered on | | | | | OVF10 announced a drive problem by switching off the OP signal. Look into Event Logging on OVF10. | |
0271 | | | BTI result is no good at every 3rd trial. |
| | | | BTI result is good at 3rd trial. |
| | | | BTI is not available or aborted. |
| | | | The UCM Safety Valve (RSL output SVC 1304) cannot block the downward move- ment. It could be a wiring failure near the RSL i/o’s 1304 – 1307. | | | | | Physical address of additional front PRS input for COR rescue is invalid or ab- normally detected at the inter-floor or the unnecessary landing. | | | | | Physical address of additional rear PRS input for COR rescue is invalid or abnor- mally detected at the inter-floor or the unnecessary landing. | | | | | The safety chain opened at MD/AES dur- ing a run while accelerating or at constant velocity. | | | | | The safety chain opened at MD/AES dur- ing a run while decelerating. | | | | | The MD/AES signal is missing for 5 minutes, but no HAD and no DTC was detected. | | | | | Motor Protection Device was active | | | | | The safety chain opened at SC_OUT dur- ing a run while accelerating or at constant velocity. | | | | | The safety chain opened at SC_OUT dur- ing a run while decelerating. | | | | | The safety chain stayed open at SC_OUT for longer than 5 seconds. In Low Overhead Installations (OHLOW), check KS contact | | | | | The safety chain opened between DFC and SC_OUT within the first step ETSD zone, as indicated by ET_P1 and ET_P2. verify Drive ETSD settings, “ETP Spe %DutySpe” and “ETP2 Spe %Duty” verify ET_P1-4 sensor adjustment | LVA PX2.1=4 or 5ET_P1(1257) ET_P2(1258) ET_S1(1259) ET_S2(1260) ET_P3(1261) ET_P4(1262) ET_S3(1263) ET_S4(1264) | | | | During MRO, a rescue run into the heavy directino was started (Penthouse Rescue) | | | | | The brake switch relay is stuck see description for blinking message 'BSR/RR Flt' | | | | | Too many consecutive correction runs occured. After 4-5 unsuccessfull correc- tion runs, the GECB prevents futher runs. Check 1LV/2LV sensors Check parameter DZ-TYP |
| | | | Power supply is dead for 5 seconds. This event is logged when only the 48VDC is dead and also when the controller is powered off. |
| | | | Power supply (48VDC) died and came back before complete power down |
|
注:删除单个故障：服务器 GO ON 或者 GO BACK 选中将要删除的故障 SHIFT(蓝健) + 1 (ON) 然后 SHFIT + CLEAR (ENTER) 当前单个故障删除 新版本有 M1-1-2-7菜单,代替了SHIFT（蓝健）+UP（2 ）
|
发表于 2023-11-28 21:38
提升卡
置顶卡
变色卡
千斤顶