On OLYMP installations, a dropped call, a floor-count jump, and an E7 after STOP can originate in different parts of the signal chain; read controller inputs and status transitions before changing parameters. Identify the controller and operating mode first, then follow the affected signal from its source through the controller to the display or motion output.
Does the controller match the lift and group configuration?
Read the controller marking, wiring diagram, lift configuration, and commissioning records. Distinguish the KLSM-based МСУ OLYMP from earlier equipment called Leader, and record whether the board is KLSM or KLSM2. A fault observation on one board or configuration does not automatically describe another.
The published configuration described for the KLSM-based system includes electric lifts with VF or two-speed (2SP) drives, passenger, hospital, or freight service, and a hoisting motor up to 22 kW. The stated speed range is 0.25–1.6 m/s. Group control is specified for up to six lifts with one or two call lines; the stated stop limits are up to 36 for collective-down service and up to 19 for collective operation in both directions. Supported door arrangements include automatic center-opening or telescopic doors and hinged car and landing doors. Use the exact project documentation to establish which combination is actually configured.
If the installed lift falls outside its recorded configuration, stop treating a dispatch or drive symptom as a tuning problem. Resolve the configuration and wiring questions with the manufacturer before proceeding. If the configuration matches, continue by reading the fault and state indications on that exact controller.
What do the controller status and fault readings show?
Use the supplied commissioning or service tool and the controller’s documentation to capture the displayed fault, active mode, and relevant input states before resetting or changing settings. Record whether the problem occurs in normal operation, inspection, or mounting mode, and whether it appears at power-up, at a start command, during travel, or after the car stops. That timing separates a missing command or interlock from a position-counting or group-dispatch problem.
E7 needs particular care: field reports describe it after STOP was pressed while the lift was in or entering inspection, but reports also differ on whether entering inspection first prevents the error. A response for KLSM2 recommended using car-top inspection rather than STOP; another described E7 after STOP even with inspection active. A separate diagnostic suggestion was to check rope slack, the tensioning arrangement, the terminal switch, and phase imbalance or grounding. These are checks to perform against the exact board instructions, not a single proven cause or a universal E7 definition.
One response associated a phase-imbalance check with parameter 06 and a value of 08. Verify the parameter label, units, board revision, and prescribed value in the documentation for the installed controller before changing it. If the fault follows a STOP or mode transition, preserve that sequence and inspect the mode and safety-input states next; if it coincides with travel or a floor mismatch, move to the position-sensor checks.
Does the call reach the controller from the correct station?
Press the affected call once, then observe its indicator and the corresponding controller or service-tool input. Check the signal at the button station and again where it enters the controller. If the station indicates a call but the controller input does not change, inspect the wiring, connector, address, and supply for that station before changing dispatch parameters. If the controller registers the call but the lift does not respond, continue to group status and operating-mode checks.
The cabin board description lists two eight-pin Wago connectors, X1 and X2, for up to 12 car-call buttons, the door-open and door-close buttons, and two key functions. For car calls 13–24 or 25–36, the described arrangement adds one or more remote stations in the car operating panel with the corresponding address. A missing high-floor command therefore calls for an address and remote-station check, not an assumption that those calls wire directly to the base cabin board.
One installation reported that command and landing-call buttons needed about one second of pressure before registering. Treat that as a version- and installation-specific observation: compare the input transition with the exact instructions rather than telling users to compensate for an input that never reaches the controller. If the call registers at the controller but drops from the display or fails to dispatch, check the group and call-line signals.
Do the call and display signals agree?
Compare the physical button state, controller input, group-call state, and displayed indication in that order. The table helps identify the next measurement; use the wiring diagram and service tool to locate the actual test point for the installed equipment.
| Signal | Source to read | Wrong-value symptom |
|---|---|---|
| Landing call | Landing button or remote station, then controller input and group-call state | Indicator lights and goes out without a dispatch, or the call does not appear at the controller |
| Car call | Cabin board X1/X2, or the addressed remote station for calls above 12 |
Call is not captured, especially at a high-floor station |
| IPU/IPD position input | Position-sensor transition at the controller during travel | Extra floor count, lost count, or direction-related position fault |
| Group-call line | Group board and the configured one- or two-line call arrangement | Call display disagrees with the car response, or paired cars behave abnormally |
| Load-weighing state | Weighing device output and controller input or displayed load state | Car calls are suppressed or the car waits with doors open despite a passenger |
| Supply and phase condition | Controller supply and phase-monitoring indication, measured against the equipment documentation | Reset, unstable start, or an E7 condition requiring electrical and mechanical checks |
The group-call protocol was described as combining four inputs into two call lines, and a field report raised interference on the traveling cable as a possible explanation for inconsistent displays. Do not infer that protocol activity is correct from a lit button alone: compare the controller and group indications. If an individual car captures calls correctly but the group signal or display does not, inspect group wiring and the group board before changing car-level settings.
Do IPU and IPD transitions match the car’s travel?
Observe each IPU and IPD transition with the service tool or documented indicators while an authorized technician tests the lift under the prescribed procedure. Compare the sequence with actual car travel and the expected floor count. A double transition can make the controller count an extra floor; a missing or intermittent transition can lose position information and lead to an incorrect direction or correction decision.
A field installation reported double triggering when the sensor-to-magnet distance was less than 20 mm. Increasing the distance stopped the extra count in that case. Use the 20 mm figure as a reported fault condition, not as a universal installation target; set sensor spacing to the manufacturer’s specification and inspect both the sensor and the traveling-cable conductors if the signal remains intermittent.
One nine-stop installation also stopped a downward-counting symptom after a jumper was installed between 2C5 and 2C6, but the report did not establish that as a standard repair. Do not copy a jumper change as a diagnostic shortcut. Check the exact schematic and have the manufacturer confirm any change that affects controller inputs; restore the specified circuit and verify every position input before returning the lift to service.
Does the direction and correction sequence follow the position inputs?
When the controller reports an incorrect direction or a car starts unexpectedly, read the active position inputs, direction state, and mode before moving or resetting the lift. Compare the input sequence with the actual car position and the correction procedure in the exact controller manual. A report described a disagreement between an instruction that called for correction in both directions and an observed installation that corrected only downward. Treat that as a commissioning discrepancy to resolve for the specific board and program, not as permission to remove or relocate a sensor.
Another report described a car starting upward after a landing door was opened and closed during an intervention while the car was traveling down. Other comments raised the terminal and position-zone conditions as relevant. An unexpected reversal or approach to a terminal is not a normal test result: stop the test, secure the equipment under the applicable lift procedure, and have an authorized technician trace door, terminal, and position inputs against the wiring diagram before further movement.
If the sensor transitions are correct but group behavior is wrong, move to the group test. If the controller’s count or direction changes without a matching input transition, resolve the sensor, wiring, and configuration path before considering a control parameter.
Does the load-weighing input explain car-call-only operation?
Read the weighing device’s actual output and the load state seen by the OLYMP controller. Do not assume a displayed or configured “15” means 15 kg. One installation using a Veda device with four load sensors had 90% and 110% functions but lacked a configured 15 kg point; a field report noted that the relevant threshold was expressed as a percentage. For a 400 kg rated load, 15% calculates to 60 kg (400 kg × 0.15 = 60 kg).
In the described behavior, the car responded to car calls when no passenger was detected, while a detected passenger caused it to remain at a floor with doors open awaiting a command. A suggested configuration used an LWX threshold of 60 kg for that 400 kg example. Confirm the rated capacity, load-device scaling, output state, and intended dispatch behavior for the actual lift before applying any value; do not copy 60 kg to another capacity or weighing system.
If the controller’s load input changes at the wrong threshold, correct the weighing-device calibration and interface according to its documentation, then verify both empty-car and loaded-car operation. If the load state is correct but cars in a pair chase, park, or lose calls together, investigate the group path rather than the load threshold.
Does the fault follow one car or the group board?
Compare the same call sequence on each car separately and then in the configured group, while observing each car’s mode and group-call state. The described system allows up to six cars and one or two call lines, so verify that the installed group arrangement matches the design. If a car miscounts or misses its own calls in standalone operation, trace its sensors and local inputs. If both cars work individually but the fault appears in group operation, focus on group wiring, addressing, call-line integrity, and the group board.
Reports include paired cars following one another, a call indicator extinguishing while cars continued moving, and a car repeatedly returning to one floor when its partner entered inspection. Those symptoms do not point to one shared cause. Record which car receives the call, whether the group indication changes, and how the cars’ modes change. A display that corrects itself after a restart is not proof of a repaired signal path; reproduce the call sequence and confirm stable operation before release.
Ask the manufacturer how the group is expected to behave when one controller or the group board is unavailable. The field descriptions raise the group board’s failure impact as a design question but do not define a fallback mode; do not promise independent group operation without verifying the project documentation.
Are supply, grounding, wiring, and moisture affecting the readings?
Measure supply conditions at the controller during idle and commanded starts, then compare them with the limits in the controller documentation. Inspect protective grounding, phase condition, connector seating, moisture, and the separation and routing of power conductors, 24 V circuits, and the 5 V protocol wiring. Do not adjust logic to compensate for a supply or wiring fault.
Field reports describe sensitivity to supply dips, moisture, and wiring errors, as well as concern about insufficient separation between power, 24 V, and 5 V protocol grounds. Other reports mention board regulators failing and phase imbalance or poor grounding being considered during an E7 investigation. These observations make electrical measurements and a physical inspection the next step when faults coincide with starts, resets, or inconsistent indicators. The reports do not provide a universal voltage tolerance, so read the actual supply limits and monitoring values from the equipment documentation.
Temporary construction power was raised as a risk to the controller. If the measured supply is unstable or out of specification, correct that condition before repeated commissioning runs. If the supply is sound but a specific input remains unstable, trace that circuit to its source and inspect the connectors and cable rather than replacing or reprogramming the controller without evidence.
Can the mounting or inspection procedure be verified safely?
Use only the controller’s specified mounting connector, inspection station, and wiring diagram. An installation procedure described for the KLSM system uses a removable connector with jumpers in place of the contactor-control connector X10; it routes the required control reference to the contactors for low-speed movement from the machine-room or car-top inspection station. The described sequence is to disconnect the main-board connectors, install the specified mounting connector, complete the mounting work, remove the mounting connector, reconnect the normal connectors, and then commission normal operation.
This is not a generic jumper recipe. The source procedure does not supply a pin-by-pin wiring map, and incorrectly bridging an input or contactor circuit can defeat intended control behavior. Use the manufacturer’s exact harness and diagram; do not improvise bridges or move the car from a makeshift connection. The mounting connector was reported as incompatible with MCS220 LCB II; use the correct equipment-specific procedure instead of assuming cross-compatibility. The described arrangement uses machine-room or car-top inspection controls rather than a handheld “mormyshka.”
- Before a test, record the exact board, mode, fault, car position, and observed input states.
- Test the affected signal at its source and at the controller, then compare the controller’s response with the documented sequence.
- Correct only the verified fault: station addressing or wiring, sensor spacing or connection, weighing-device calibration, group wiring, or supply condition.
- Restore the prescribed connectors and operating mode, then check the affected calls, floor counts, direction, displays, and group behavior under the approved commissioning procedure.
Do not release the lift if it reverses unexpectedly, approaches a terminal incorrectly, reports an unresolved fault, or behaves differently from the documented safety and inspection sequence. If the fault persists after the specified checks, preserve the service-tool readings and wiring/configuration details for the manufacturer.
Frequently asked questions about OLYMP troubleshooting
Can I use the same OLYMP settings on KLSM and KLSM2?
No. Identify the board and use its matching documentation; the E7 reports describe differing STOP and inspection behavior, so do not transfer a setting or diagnosis without checking the exact version.
Does an OLYMP call button need a one-second press?
One installation reported about one second before a button registered. Verify the controller input and the instructions for the installed version rather than treating that observation as a universal setting.
Can I connect car calls above floor 12 directly to the cabin board?
The described cabin board supports up to 12 car-call buttons on X1 and X2. Calls 13–24 or 25–36 use an addressed remote station in the car operating panel.
Does parameter 06 = 08 clear every OLYMP E7?
No. That value appeared in one phase-imbalance diagnostic suggestion. Confirm the parameter meaning and prescribed value for the installed controller before changing it, and inspect the fault’s actual mode and input sequence.
When should I stop troubleshooting and contact OLYMP support?
Stop and secure the lift if it moves unexpectedly, approaches a terminal, has an unresolved safety or position-input fault, or requires an undocumented jumper or parameter change. Send the manufacturer the board identification, configuration, fault and mode sequence, service-tool readings, and measured supply conditions so support can direct the next test.