Skip to content

How does Qynetic collect machine data?

Qynetic Edge reads machine signals inside the factory network. Sources that already send events can use the Ingest API directly or through an existing Node-RED flow. Each event is linked to the machine that produced it.

From machine signal to production event

  1. Identify the source

    Register the machine with the ID used on the shop floor. Confirm which signal reports its state, measurement or cumulative count.

  2. Map the value

    Define what each reading means, including units and any scaling. Check the result against the operator panel during a known cycle.

  3. Keep the evidence

    Edge records the source, observation time and source time when available. Diagnostics show unrecognised values and poor-quality readings.

  4. Verify delivery

    Follow a known event from the local queue to its machine in Qynetic. A device heartbeat confirms connectivity. The accepted event confirms delivery.

Already using Node-RED?

A flow that already collects production data can send events to the Ingest API with a site token and the registered machine’s ID. Reusing the same event ID on a retry lets Qynetic recognise the duplicate.

Connecting an MES, ERP or inspection system

Start with a sample export or API response. Identify the order, part or machine it refers to and which fields the receiving module needs. The interface, permissions and mapping for an enterprise system require review for each installation.

Book a call about your factory

Tell us what you make and which machines you run, and we will walk through how Qynetic fits. If you would rather get news and early access, join the waitlist.