Apparent Errors By Anti Misuse Detection Or Special Functions; Troubleshooting At The Interface To External Components - Intec MLC 8000 Operating Manual

INTEC GmbH
Lift controller MLC 8000
22/12/2016
Operating manual V2.0
The big problem with duplicate node ID numbersin a CAN bus network is that the 2
modules with the same node ID number interfere with each other and thereby disturb
the entire bus. This may cause that other modules can no longer send messages. As a
result, error messages appear from modules that actually work correctly.
Mostly a duplicate node ID number can be diagnosed with the menu "hardware test". If
individual components are displayed partly as available, partly as absent, then this may
assign to a duplicate node number.
The node ID number can only be assigned freely to TSE, ESE and CBK - modules . In the
HSE and the FVE, the node number can not be changed. The assemblies PSE and ASE are
also simultaneously assigned to the appropriate function by assigning the node ID number.
The node number of a TSE or ESE board can be tested in the following way:
- Disconnect all other TSE or ESE modules from the bus
- Start menu "hardware test" and read number of TSE / ESE
Example: Hardware test TSE:
---*----
In the displayed example the TSE board has the node ID number 4.

4.11 Apparent errors by anti misuse detection or special functions

The lift controller MLC 8000 has a variety of functions to call-misuse detection. When
checking the lift controller it should therefore always take care that apparent errors can also
be the result of misuse detection or of a special function.
Example: The lift controller always accepts only one call, any more operated car command is
ignored.
Possible cause: The " Max.CC no ." parameter is set to 1 and thus limits the number of car
calls.

4.12 Troubleshooting at the interface to external components

External control components (eg frequency, door control units) which are not directly part of
the lift controller MLC 8000 can even recognize or cause errors, which are difficult to
diagnose. For example, the lift controller monitors the signal sequence of VVFF connected
via digital signals, while, conversely, the VVVF monitors the signal sequence of the lift
controller. This monitoring is carried out partly in millisecond range and therefore it is
sometimes difficult to understand what actually was the cause of an error message now.
To make it easier to detect errors, it is possible, to increase all monitoring times of the lift
controller several times so that it is possible to measure digital signals by multimeter before
all signals are switched off due to an elapsed monitoring time.
Example:
87/196