Skip to content

Sensor gateway

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: Stream (a timestamped recording) · type sensorgateway

What it is

A sensor gateway polled over Modbus TCP, or over HTTP. In the test estate there is one gateway per warehouse, reading the dock staging-area temperature probes. The connector reference is Telemetry.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typesensorgateway
Other spellings that resolvesensor, modbus, temperature, infrared, thermal, probe
Settingstransport, endpoint, unit_id, channels, collect_seconds, poll_interval_seconds, use_tls
Credentialstoken, api_key, password

The test connection

The test estate defines 3 connections of this type. The first is shown, and expected.json lists every one.

Dock staging probes WH-NORTH

SettingTest value
transportmodbus_tcp
endpoint[2001:db8:51::d8]:802
unit_id1
channels100:DOCK-NORTH-01,101:DOCK-NORTH-02,102:DOCK-NORTH-03
collect_seconds60
poll_interval_seconds900
use_tlstrue

This connection takes no credential: Modbus has no login of its own, so TLS is all the protocol offers. FACE refuses a Modbus/TCP connection without use_tls; Modbus over TLS listens on port 802.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Point the connection at a gateway that speaks Modbus/TCP over TLS (port 802), or one that serves its readings over https:// (transport https). Add one connection per unit in Settings › Integrations › Systems, with endpoint set to the gateway and the channels above. A plain Modbus/TCP gateway on port 502 is refused.
  2. The recording below holds the test estate’s register reads in polls.jsonl and the register layout in register_map.json. Open them next to expected.json to see what FACE builds from the polls.
  3. To watch the readings arrive, open Live sensors or Devices from the connection’s card on Ask.

What FACE finds

Modbus has no catalogue and carries no register map on the wire. The channels setting names what each register means.

DatasetKindDomainPrimary keyRowsFields
holding_registersmodbus_register_pollcold_chainnone727

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 1 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
dockholding_registers.channelcctv, excel, files, kafka, logisticsapi, postgres, whs, yms

It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.

See all connectors at once for the walkthrough across every source.

Download

Streams are dialled and held open, so their datasets are replay recordings under streams/sensorgateway/, not a zip. Download the files, and use them as described above.

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.