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.
Qynetic Edge and its five machine adapters
Qynetic Edge
Qynetic Edge reads machine signals on the factory network, stores mapped events locally and forwards them to Qynetic over an outbound HTTPS connection.
OPC UA
Qynetic Edge polls selected OPC UA nodes on a machine or PLC. Each read includes a value, its quality status and the source timestamp when the server supplies one.
MTConnect
Qynetic Edge reads timestamped observations from an MTConnect agent and uses sequence numbers to resume collection. Execution state and part counts can feed OEE.
MQTT
Qynetic Edge subscribes to MQTT 3.1.1 topics at QoS 1. It can map JSON fields to measurements or counters and plain-text messages to state changes.
Modbus TCP
Qynetic Edge reads coils, discrete inputs, holding registers and input registers over Modbus TCP. The device’s register map gives each raw value its meaning.
CE / MELDAS M70
Qynetic Edge includes read-only CE profiles for Citizen L12 and L20E lathes with a Mitsubishi MELDAS M70 control. Each installation needs validation at the machine.
From machine signal to production event
Identify the source
Register the machine with the ID used on the shop floor. Confirm which signal reports its state, measurement or cumulative count.
Map the value
Define what each reading means, including units and any scaling. Check the result against the operator panel during a known cycle.
Keep the evidence
Edge records the source, observation time and source time when available. Diagnostics show unrecognised values and poor-quality readings.
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.