RobustelConnect. Compute. Create.
BUILD & VERIFY

Read your first sensor value.

Prepare and verify one read-only S6000U measurement in E2C Factory. Finish with a recorded point mapping, a fresh value and a recovery reference for your next experiment.

Applies to: EG5120 · S6000U · E2C FactoryReviewed: 29 October 2026Store guide v2 · match your installed release
FROM FIELD SIGNAL TO USEFUL DATARS-485 · Modbus RTU
Robustel S6000U multifunctional Modbus sensorS6000UModbus sensor data
Robustel EG5120 industrial edge computing gatewayEG5120Local processing & applications
ON THE GATEWAYE2C Factory

Collect, organise and visualise industrial data locally.

DEVICE OPERATIONSRCMS

Monitor and manage the gateway through an internet connection.

Connection diagram. Your quote confirms the hardware variant and included software and services.

Prepare the bench and the documents

  • EG5120 and S6000U, matched power supplies, an RS-485 cable and terminal assembly checked against both hardware manuals.
  • A computer connected to the gateway LAN, the actual gateway address and authorised sign-in access.
  • The sensor revision and its protocol/register document; the EG5120 firmware and E2C Factory version; the applicable software entitlement.

Use the development worksheets to record settings and evidence. Leave unknown addresses blank until the matching sensor document is available.

Choose the correct reference path

This workflow: S6000U → RS-485 / Modbus RTU → E2C Factory. The software manual documents Modbus RTU collection; the exact sensor point still comes from the S6000U protocol document.

E2C Factory quick start: the worked collection example uses a Modbus TCP source. Use it to understand installation and validation, not as the S6000U register or serial configuration.

Alternative S6000U example: the linked Node-RED/Blynk article uses serial-to-TCP mapping and a separate application. Its port and parsing instructions belong to that alternative path. Do not apply both collection setups to the same serial port.

  1. Record the starting configuration

    Record model, serial number, firmware, software version and sensor revision. Compare the installed E2C Factory release with its compatibility and licence information. Confirm access to the collection functions you intend to use and check the gateway clock before relying on timestamps. If software is not installed, complete the installation reference first.

  2. Check the connection before applying power

    Use the device manuals to identify sensor A, B, GND and VIN and the selected gateway serial terminals. Record the terminal-to-terminal wiring and power-supply ratings. Have the assembly checked before energising it; do not infer a pin assignment from wire colour.

    Configure the selected interface for RS-485 as required by the gateway manual. Confirm that a serial bridge or another polling application is not already using that port.

  3. Complete one point-map row

    Choose one documented read-only measurement. Record the slave address; baud rate, parity and stop bits; read function; register address and whether it is an offset or reference address; data type, byte order, scale and unit. Also record the source document and page or section.

    If any mapping field is unknown, stop at this completed preparation list and request the correct protocol document. A plausible number is not sufficient evidence of a correct register.

  4. Configure one device and one tag

    In the installed E2C Factory release, use Data Collection to add a Modbus RTU device with the selected serial interface and the documented settings. Add one read-only tag from the completed point map. Use a clear name that describes the measurement and location, and an agreed polling interval.

    Save and publish the collection configuration using the matching manual. Inspect the runtime result before adding more points or downstream functions.

  5. Verify the result and retain evidence

    • The intended device responds and the chosen tag has a valid result.
    • The displayed unit and converted value agree with the point map and an independent reference or known condition.
    • New samples arrive at the expected cadence; record collection time separately if the tag view does not expose a sample timestamp.
    • A controlled bench interruption is distinguishable from a fresh reading. Do not treat a retained numeric value as live data.

    Save a screenshot or short observation log, the mapping row and the supported configuration export. Record how to restore it. Your first-data task is complete when another engineer can identify the setup and understand why the value is trusted.

  6. Choose the next task

    Use the verified value for a local trend and alarm experiment or an MQTT handoff. Gateway management is a separate exercise: introduce RCMS.

Checks when something does not work

No response from the sensor

Check power, the terminal mapping, the selected serial port, port ownership, slave address and serial settings against the recorded setup. Inspect the collection diagnostic log available in your installed release. Change one setting at a time and record the result.

The value is present but has the wrong scale or sign

Recheck function code, address convention, data type, signedness, byte order and scaling. Compare the unconverted value with the protocol document before changing the conversion.

The value stops changing

A stable environment can produce a stable reading. Check sample timing and device status; observe a safe, known change or compare with an independent measurement. Do not heat, strike or otherwise stress the sensor to force a response.

Official technical references

E2C Factory software manual — collection and compatibility E2C Factory quick start — Modbus TCP worked example EG5120 hardware and firmware references Alternative Node-RED + Blynk sensor example — a different collection path