On TM88-1, the described safety-circuit indication appears as a yellow lift or an open-door icon, while an alarm condition is shown red with text. The basic indication reports that the monitored circuit has changed; optional voltage checks at defined points add diagnostic detail.
Why does the operator see a yellow lift or an open-door icon?
The display is the end of a signal path, not a direct view of every lift contact. TM88-1 is described as monitoring the safety circuit in its dispatch variants. Its lift is typically shown yellow or with an open-door pictogram; an alarm condition is shown red and accompanied by text. Confirm the exact color, icon, and message mapping on the installed operator display, because the description does not assign a specific screen message to every possible contact state.
Use the screen to establish what the dispatch system believes, then work toward the field signal. A yellow or open-door indication can direct the operator to a non-normal monitored state, but it does not by itself identify the contact that changed. Red with text communicates an alarm condition as configured; it does not prove that the dispatch system has identified the root cause.
| Operator display | What it tells you | Next check |
|---|---|---|
| Yellow lift or open-door pictogram | The displayed state is not the ordinary all-clear presentation; the installation description associates this display style with safety-circuit monitoring. | Read the mapped point state and compare it with the lift’s approved circuit diagram and current operating condition. |
| Red lift with text | An alarm condition is being presented. | Record the exact message and check whether the source point, controller state, and display text agree. |
| No change at the screen after a field condition changes | The problem may be in sensing, controller acquisition, communications, or screen binding. | Check each layer in order instead of treating the symptom as a single “tag fault.” |
Do not use a dispatch icon as a substitute for the lift’s safety circuit or its required protective behavior. The dispatch indication reports information; it does not establish that a lift is safe to operate or that the displayed cause is exhaustive.
What alarm must the commissioning test demonstrate?
The cited clause 13.6 is described as requiring signaling when the lift safety circuit operates. The related circuit scope is discussed with clause 6.4.7. Treat these references as the requirements to check against the rules and editions applicable to the installation, not as a conclusion that a particular display automatically satisfies them.
Turn the requirement into a testable acceptance statement before changing wiring or configuring the display: a controlled change in the monitored safety-circuit state must reach the dispatch endpoint and produce the agreed operator indication. If the project requires only circuit-actuation signaling, an aggregate input may be sufficient. If the operator must identify where the circuit opened, define the additional monitored points and their message mapping separately.
| Requirement | Commissioning evidence | What it does not prove |
|---|---|---|
| Signal safety-circuit actuation | A controlled circuit-state change produces the configured alarm at the dispatch display. | Which individual contact caused the change. |
| Identify a section of the circuit | Each additional measurement point changes the intended diagnostic state and text. | That every contact in the lift has a separate diagnostic point. |
| Show an operator-readable condition | Color, icon, and accompanying text match the approved alarm list. | That a vague or stale display label conveys the correct cause. |
Write the acceptance matrix with the lift state, expected signal at the monitoring point, controller or interface state, and expected screen text. Use the approved lift wiring diagram and the actual TM88-1 configuration to fill the values; no point addresses, voltage levels, or tag names are specified here. A test that checks only the display does not isolate a wiring or input fault, while a test that checks only the input does not prove the operator receives the alarm.
Where does the displayed status originate?
Trace a discrepancy from the operator screen back to the physical sensing point. For a typical monitoring path, a field contact or voltage condition is acquired by an interface, transmitted through the configured communications path, interpreted by the dispatch controller or application, and bound to a screen object. The actual TM88-1 installation may use different interfaces, so identify its configured path instead of assuming a specific board or driver.
| Layer | Typical symptom | Check |
|---|---|---|
| Field point or sensor | The physical condition changes but the electrical input does not. | Compare the point with the circuit drawing and measure only at approved test points using the specified method. |
| Input or controller | The signal reaches the interface but the reported state stays unchanged or is inverted. | Check the configured input, polarity or state convention, and controller indication against the project documentation. |
| Driver or communications path | Controller state is correct but the dispatch data is absent, stale, or delayed. | Check the configured connection, link status, and received point value at the next layer. |
| Tag binding and screen object | The received value is correct but the wrong icon, color, or text appears. | Check the binding, alarm mapping, and display state table for the affected object. |
This sequence separates a tag fault from a binding fault. If the incoming point value is wrong, the screen binding may be working correctly while the field, input, controller, or driver is at fault. If the incoming value is right but the screen is wrong, investigate the tag-to-object mapping and alarm presentation before revisiting field wiring.
Record the point identifier and the expected state at each boundary. Do not create substitute addresses or infer polarity from the color of an icon. The project drawings, configuration files, and installed interface documentation determine those values.
How much detail does the basic safety-circuit point provide?
An aggregate safety-circuit indication answers a limited question: did the monitored circuit state change? It does not inherently tell the dispatcher which component opened the circuit. This distinction matters when a display is expected to help staff locate a fault rather than simply report a non-normal condition.
The discussion identifies as an optional remote voltage probe for adding information from control points. The example is to route indications from points described as “after VL” and “after VK.” Those labels should remain tied to the project’s circuit drawing; the abbreviations are not expanded here, and their meaning must not be guessed from the display name.
Additional points only improve diagnosis when each point has a defined electrical meaning and a corresponding screen interpretation. For each one, document its exact terminal or drawing reference, expected value in normal and test states, controller input, and operator text. A label such as “after VK” without a drawing reference can produce an indication that is difficult to troubleshoot or maintain.
Use two levels of acceptance: first prove that the aggregate circuit signal operates; then, if fitted, prove each optional point independently under an approved test condition. If multiple points change together, the resulting display may still leave the technician unable to localize the cause.
How should you configure and test the alarm point?
Keep the physical point, controller state, transmitted value, tag, and display label in one traceable record. The exact terminal, data address, tag name, alarm priority, and voltage state depend on the installed configuration and must come from its approved drawings and configuration records.
- Identify the required safety-circuit indication and any optional diagnostic points. Confirm the applicable rule text and the lift-specific circuit diagram.
- Record the field point, interface input, controller representation, communications route, tag binding, and intended operator message. Mark any unknown mapping for resolution before the test.
- With the lift in a permitted baseline condition, compare the physical point, controller state, received point value, and display. Record the actual baseline rather than assuming a particular voltage or bit value.
- Use the approved controlled test method to change the monitored state. Do not bypass, defeat, or jumper a safety device as a substitute for a valid test.
- Observe each boundary in sequence: physical point, interface or controller, communications value, bound tag, and screen. Note the first boundary where the expected state is lost or changed.
- Restore the normal condition using the approved method. Confirm that each layer returns to its expected state and that the displayed alarm clears or changes according to the configured logic.
This procedure distinguishes a field fault from a display fault without presuming that the TM88-1 uses a particular controller or driver. If the input changes but the transmitted value does not, investigate the configured acquisition and communications path. If the transmitted value changes but the screen does not, verify binding and display logic. If the signal never changes at the field point, check the electrical circuit and test method before editing a tag.
Add the optional probe when operators or maintenance staff need information beyond the aggregate safety-circuit indication. Do not add diagnostic points simply to make a display look more detailed; every extra point creates another mapping and test obligation.
| Operational need | Monitoring choice | Commissioning implication |
|---|---|---|
| Report only that the safety circuit changed | Use the basic monitored circuit indication described for TM88-1. | Prove the circuit-state alarm reaches the display. |
| Distinguish circuit sections at defined points | Consider and the identified points, such as “after VL” and “after VK.” | Prove each point independently and use labels tied to the circuit drawing. |
| Identify an individual device or contact | Determine whether the circuit design exposes a separate signal for that device. | A voltage point alone may not identify an individual contact; confirm what the measurement can distinguish before promising that diagnostic. |
Before installation, confirm with the applicable product and lift documentation how the probe connects, what electrical conditions it can monitor, and how its output is acquired. Do not infer terminal numbers, isolation, voltage limits, or connection topology from the model name. During commissioning, compare the probe indication against the same controlled state changes used for the main circuit signal.
Which communications path should carry the indication?
TM88-1 is described with channel options ranging from fieldbus to Ethernet, as well as radio and GSM. That list identifies possible transport choices; it does not establish which path a particular installation uses, whether paths operate simultaneously, or whether they provide automatic redundancy. Capture the installed path and any fallback behavior in the commissioning record.
Choose and verify the communications path as part of the alarm chain. Confirm that the field state reaches the remote display over the configured connection, and distinguish a communication-loss or stale-data condition from a genuine safety-circuit change. The display must not leave an old all-clear value looking current after the connection has failed; verify the configured communication-status behavior at the operator interface.
- Identify the actual medium and connection between lift equipment and dispatch endpoint.
- Confirm normal point updates from the controller to the display using the installed configuration.
- Under a planned test condition, verify how loss and restoration of the communications path are presented. Do not mistake a link failure for a circuit-state alarm.
- Repeat the controlled safety-circuit indication test after communications have recovered, then confirm the display again tracks the current source state.
Where a project calls for alternate or combined paths, specify the switchover and alarm behavior explicitly and test them. The presence of several channel types in a product description is not evidence that a specific system has been configured to combine them.
What should be settled before expanding or mixing dispatch equipment?
Record compatibility at the interface level before replacing equipment or connecting systems from different manufacturers. Similar screen functions do not imply compatible field protocols, point maps, or controller interfaces. Confirm the interface and the exact information exchanged, including whether the receiving system can distinguish a circuit-state signal from a general lift alarm.
For an installation expected to expand, capture the current point list, communications method, spare or repair strategy, and the additional signals required for future lifts or devices. The source material identifies repair stock, channel choices, interoperability, ongoing function changes, reliability history, and cost as selection considerations. Translate those broad considerations into project checks rather than assuming a product comparison settles them.
| Project decision | Question to close | Evidence to retain |
|---|---|---|
| Interoperability | Can each system exchange the required point states and alarm text through a documented interface? | Interface description, point map, and a demonstrated end-to-end test. |
| Repair readiness | Which replaceable modules or parts must be available to restore monitoring? | Approved spare list and the replacement/return-to-service procedure. |
| Transport | Which communication path is installed, and what should the operator see if it fails? | Path diagram and a tested link-failure indication. |
| Expansion | Can additional lifts or diagnostic points be added without changing the meaning of existing alarms? | Capacity and point-mapping plan, with updated alarm text. |
Keep product capability, installed configuration, and demonstrated behavior separate in the project record. A feature listed for a product family is not proof that the feature is present in a particular panel or enabled in the software.
How do you prove the complete TM88-1 alarm path?
Close commissioning with one traceable end-to-end test for each required indication. A passing input check proves only the input; a passing display check using a forced software value proves only the downstream mapping. The required alarm is demonstrated only when a controlled change at the approved source point reaches the actual operator endpoint and returns correctly.
- Begin from the documented normal state and record the source point, controller state, received value, and operator display.
- Apply the approved test condition at the actual monitoring point, and record the state transition at every available boundary.
- Compare the final icon and text with the alarm acceptance matrix. Confirm that an aggregate indication is not presented as a component-level diagnosis unless a separate point supports that claim.
- Restore the source condition, confirm normal state recovery at every layer, and confirm the display clears or updates correctly.
- Repeat the sequence for each optional probe point and for any communications alternate path included in the project scope.
Retain the test record with the point map, screen text, measured or observed states, and any unresolved deviations. Commissioning is complete for the indication only after the source changes, the operator sees the correct mapped condition, and the restored source clears the displayed condition.
FAQ
Why does TM88-1 show a yellow lift or an open-door icon?
That is the described display style associated with safety-circuit monitoring. Check the configured point and the lift circuit diagram to determine what state the icon represents on the installed system.
Why does the screen show an alarm but not the failed contact?
An aggregate safety-circuit signal reports a circuit-state change, not necessarily the individual contact that caused it. Separate measurement points are needed for more detailed diagnosis.
is identified as an optional remote voltage probe for adding control-point information, including points described as after VL and after VK. Use it when the project needs those additional diagnostics and can map and test each point.
Why can the screen be wrong when the controller input is right?
The fault may be in communications, the received tag value, the tag-to-screen binding, or the display-state mapping. Compare the value at each layer to find the first point where it stops matching.
Why is a screen check alone not enough to verify the alarm?
A screen-only check does not prove that the field condition reaches the display. Change the approved source point, confirm the mapped alarm at the operator endpoint, then restore the source and verify that the display returns to normal.