RFID readers
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 | |
|---|---|
| Type | rfid |
| Other spellings that resolve | epc, llrp, tagreader |
| Settings | protocol, endpoint, reader_id, antenna_ports, location, collect_seconds, max_reads, report_duplicates, use_tls |
| Credentials | token, 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
| Setting | Test value |
|---|---|
protocol | llrp |
endpoint | rfid-dock-north-01.quillmere.invalid:5084 |
reader_id | RDR-NORTH-01 |
antenna_ports | 1,2,3,4 |
location | DOCK-NORTH-01 |
collect_seconds | 30 |
max_reads | 10000 |
report_duplicates | false |
use_tls | true |
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.
- Download
tag_reports.jsonlfrom 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. - Add a connection in Settings › Integrations › Systems with
protocolset tohttpsandendpointset to the file’s URL, for examplehttps://<host>:8084/tag_reports.jsonl. FACE refuses anhttp://endpoint. The test estate’s own readers use LLRP: point anllrpconnection withuse_tlson at a reader you run to read it live. - 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.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
tag_reports | llrp_ro_access_report | receiving | none | 48 | 7 |
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 entity | Fields here | Also in |
|---|---|---|
| device | tag_reports.reader_id | bigquery, cctv, databricks, files, gps, iot, kafka, mqtt, postgres, servicenow |
| epc | tag_reports.EPC_96 | logisticsapi |
Evidence it holds for the planted anomalies:
- ANOM-6, An RFID read with no matching ASN.
streams/rfid/tag_reports.jsonl, look for303400000051AEFF00000999.
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.