Elevator Telemetry Interface Planning: RS-485, CAN, Digital Inputs and Relay

The Robustel EV8100 Elevator Voice Gateway documents RS-232, RS-485, CAN, four wet digital inputs and one dry-contact relay alongside its voice functions. Planning starts by matching each required telemetry point to an electrically and logically documented interface; the presence of a connector does not reveal a lift controller proprietary protocol.

Select the Least Ambiguous Interface for Each Signal

Use a serial or CAN connection when the controller vendor supplies the electrical settings, message definition and permission to integrate. Use digital inputs for simple, independently defined states where the voltage range and common reference are understood. Reserve the relay for a documented handoff that remains safe if the gateway is unpowered or restarting.

Create a point list with source terminal, normal state, alarm state, debounce, timestamp owner, update rule and destination name. For bus data, add controller model and firmware, node address, baud rate, framing and timeout. For every point, state whether it is monitoring only or can influence equipment.

Bench-test invalid and changing states, not only normal operation. Disconnect the bus, swap one input state, restart the application and restore power. The receiving platform should distinguish stale, unknown and confirmed values rather than presenting the last value as current.

Name Every State, Including Unknown

A digital input may represent door open, breaker trip, pump run or a common alarm. Record active voltage, common reference, normal state, debounce, acceptable pulse width and what an open wire looks like. A binary value is only simple after those details are fixed.

For each relay, define normally open and normally closed behaviour, load type, maximum voltage/current and the external circuit it drives. Interposing relays may be required when the field load exceeds the gateway’s documented rating or needs different isolation.

Keep Alarms Separate From Safety

An edge gateway can collect an alarm and notify another system. It should not replace a certified safety relay, emergency-stop circuit or deterministic PLC unless the complete system is designed and approved for that function. Put this boundary on the wiring drawing and in the software requirement.

If a relay requests a reset or mode change, the PLC should retain interlocks and final authority. The gateway’s command should expire, be logged and be rejected when local conditions are unsafe.

Use a State Table Before Writing Logic

Condition	Input quality	Local indication	Relay behaviour	Upstream record
normal	valid	normal	approved resting state	periodic/changed state
alarm active	valid	alarm	defined handoff only	immediate event with timestamp
input open/invalid	bad or unknown	fault	fail-safe project state	diagnostic event
WAN unavailable	valid	local state remains visible	no unapproved change	buffer event for replay
gateway rebooting	unavailable	startup indication	documented de-energised state	restart and configuration event

This table forces the team to distinguish alarm condition from data-quality fault. Without it, a broken wire can be displayed as “everything normal.”

How the Robustel EV8100 Elevator Voice Gateway Supports Telemetry Interface Planning

The Robustel EV8100 Elevator Voice Gateway documents RS-232, RS-485 and CAN interfaces, four wet digital inputs and one dry-contact relay alongside its lift-voice role. That combination lets an OEM consolidate defined monitoring points with communications, provided the controller protocol and electrical behaviour are documented and tested.

The relay documentation gives electrical limits and contact terminals; it does not define the project circuit or load. Verify current, voltage, inductive-load protection, isolation, commoning and wiring rules. Use an interposing device where the field circuit requires it.

For serial and CAN integration, the controller vendor must provide the protocol contract or an approved integration path. Record message ownership, scaling, invalid values, update interval and the controller firmware against which the integration was tested. This prevents a physical connection from being mistaken for semantic compatibility.

Separate Local Alarm Continuity From Cloud Notification

Decide what happens when the WAN is unavailable. A local lamp, buzzer or relay handoff may continue if it is designed and tested, while cloud notification waits. Buffer the event with its original time and quality. On reconnection, send current state before or alongside the backlog so an old alarm does not obscure a live one.

Robustel’s IoT-enabled smart elevators application example places telemetry and remote operations around the Robustel EV8100 without blurring them into the emergency-voice path. It is a useful reference for deciding which status belongs locally, which travels northbound and which party owns the response.

Test Faults at the Terminal Block

Software simulation is not enough. Open and short the input as allowed by the design, remove the field supply, cycle gateway power and disconnect the WAN. Verify electrical state, application state, local indication and upstream records each time.

For relays, test a safe representative load and confirm the contact state through boot, application restart and loss of communications. Make sure a queued command cannot execute after its operational context has expired.

Record the fault signature as well as the expected result. A missing field supply, open input wire, failed application and lost WAN may all produce “no alarm” unless separate diagnostics exist. During acceptance, photograph or log the terminal state, gateway input, local application state and upstream event for each injected fault. That evidence gives support staff a way to isolate the physical layer before changing software that was behaving correctly.

Robustel’s PSTN replacement for elevator emergency phones application example shows the EV8100’s primary voice role within a wider lift installation. For a combined design, telemetry maintenance must be arranged so that application changes and controller tests do not compromise that voice service.

Select the EV8100 Interface From the Electrical Role

Choose RS-485 or CAN only when the lift-controller protocol is available and approved. Use wet digital inputs for defined voltage states and the dry relay for a bounded contact handoff within its documented rating. If the project needs more points, analogue channels or a different control role, keep that work in a separate controller or I/O system rather than stretching the EV8100 beyond its interface list.

Use Robustel RCMS platform for gateway operations, while the application records alarm state and the lift controller or safety system retains its own diagnostic evidence.

The Robustel EV8100 Quick Pitch video is a useful orientation for teams that need to see the voice and telemetry roles in one product before the detailed interface workshop.

よくある質問

Q1. What are digital inputs and outputs?

Digital inputs read discrete electrical states, while digital outputs drive defined on/off signals. Their voltage, current, isolation and common reference must match the connected circuit.

Q2. What is the difference between relay output and digital output?

A relay output uses physical contacts and can provide galvanic separation within its rating. A transistor or wet-contact digital output switches electronically and has different wiring and load limits. Check the exact product circuit.

Q3. What are relay outputs?

They are electrically operated contacts that can open or close an external circuit. The relay rating does not guarantee suitability for every load, especially inductive or higher-power equipment.

Q4. What are digital inputs and digital outputs in a PLC?

They are the PLC’s discrete field interfaces for reading switches and sensors and driving actuators or control handoffs. An edge gateway can exchange similar signals but should not automatically take over PLC control authority.

Q5. When is the Robustel EV8100 Elevator Voice Gateway a good telemetry-interface fit?

It fits when a lift project needs its documented RS-232, RS-485, CAN, four wet digital inputs and one dry relay alongside the EV8100 voice role. The controller protocol, electrical circuit and safe states still need project validation.

結論

The Robustel EV8100 Elevator Voice Gateway is a practical choice when a lift project needs documented voice connectivity and a defined set of serial, CAN, digital-input and relay telemetry interfaces in one managed device. Its relay is best treated as a bounded handoff within an approved control design, while the lift controller and safety system retain their own responsibilities.

Define unknown and power-off states, keep commands time-bounded, and test faults at the terminal block as well as in software. That discipline produces alarms operators can trust and control handoffs that fail predictably instead of becoming hidden automation.

When an alarm fails in service, start with the field circuit and work inward: voltage and common reference, terminal state, gateway input, application rule, output contact and upstream acknowledgement. A documented sequence is more valuable than a generic “reboot the gateway” instruction because it preserves the evidence needed to distinguish wiring, logic and communications faults.

Explore More Articles About Robustel Lift Connectivity

著者について

Robustel Editorial Team

The Robustel Editorial Team publishes practical articles on industrial connectivity, edge computing, LoRaWAN and device management, focusing on deployment considerations, technical limitations and long-term operation.