Skip to content

RFID readers

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 rfid

What it is

Fixed RFID readers at the docks. In the test estate there is one reader per dock, nine in all, reporting EPC tag reads. 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
Typerfid
Other spellings that resolveepc, llrp, tagreader
Settingsprotocol, endpoint, reader_id, antenna_ports, location, collect_seconds, max_reads, report_duplicates, use_tls
Credentialstoken, api_key, password

The test connection

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

Dock reader RDR-NORTH-01

SettingTest value
protocolllrp
endpointrfid-dock-north-01.quillmere.invalid:5084
reader_idRDR-NORTH-01
antenna_ports1,2,3,4
locationDOCK-NORTH-01
collect_seconds30
max_reads10000
report_duplicatesfalse
use_tlstrue

This connection takes no credential: LLRP has no login of its own, so TLS is all the protocol offers, and FACE refuses an LLRP connection without it.

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. Download tag_reports.jsonl from the recording below and serve it over HTTPS from a host FACE can reach, with a certificate FACE trusts. Each line is one tag report, and the connector reads newline-delimited JSON as well as a JSON array.
  2. Add a connection in Settings › Integrations › Systems with protocol set to https and endpoint set to the file’s URL, for example https://<host>:8084/tag_reports.jsonl. FACE refuses an http:// endpoint. The test estate’s own readers use LLRP: point an llrp connection with use_tls on at a reader you run to read it live.
  3. To watch the reads arrive, open Live sensors or Devices from the connection’s card on Ask.

What FACE finds

RFID has no catalogue. FACE collects reads for collect_seconds, and the reader’s location setting ties each read to a dock.

DatasetKindDomainPrimary keyRowsFields
tag_reportsllrp_ro_access_reportreceivingnone487

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 2 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
devicetag_reports.reader_idbigquery, cctv, databricks, files, gps, iot, kafka, mqtt, postgres, servicenow
epctag_reports.EPC_96logisticsapi

Evidence it holds for the planted anomalies:

  • ANOM-6, An RFID read with no matching ASN. streams/rfid/tag_reports.jsonl, look for 303400000051AEFF00000999.

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/rfid/, 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.