One gateway
for diverse shop-floor equipment
Adapters for CNC machines, laser cutters, robots, PLCs and legacy machines with no network interface; up to 255 devices. Data is normalized at the edge and exposed through five northbound channels — HTTP, MQTT, MODBUS, direct database write and MCP — to your systems and AI tools.
Connectivity and data collection specifications
Current product capabilities. Sampling intervals depend on the equipment model and on-site verification.
CNC controls are verified per family across basic data, axis data, OEE monitoring, PLC, program transfer and tooling; the matrix is online
Up to 255 devices on one LAN per gateway
Wired networks: regular sampling configurable down to 100 ms; factory default 5000 ms
168 HTTP endpoints; 33 MCP read-only tools
Read / upload / download / delete / back up / bulk send; tool offset read-write
Resumes after a network drop; cleaning, conversion and mapping done in the gateway
InfluxDB · MySQL · SQL Server · PostgreSQL
Per-user keys plus an authorized-API allow-list; high-risk write endpoints disabled by default
Connection options
for modern and legacy equipment
Equipment varies in age, interfaces and protocols. The gateway uses direct protocol, PLC or IO connections to standardize data. Available data points depend on the equipment.
Protocol-connected machines
Controls with Ethernet and protocol support connect directly: state, program, position, feed, speed, load, tool number and alarms. Laser cutters add a laser-power task; robots (Fanuc, ABB) return joint coordinates and alarm logs.
PLC equipment
Registered as PLC machines; points are read by generic and MODBUS area addressing, with state and counts reconstructed in the gateway.
Legacy manual machines
External PLCs, IO and sensors collect signals; gateway data tasks convert these signals into machine state and part counts.
Standardize data at the gateway
to simplify application integration
The same “running” comes from different signals and different rules on different machines. Normalization happens at the edge; upstream systems receive consistent data definitions.
- 01 · Clean Bulk read, pick points by index, rename tags
- 02 · Convert Unit conversion, bit-level flags, status-code mapping
- 03 · Map alarms Raw alarm numbers translated into readable descriptions via a mapping table
- 04 · Expose Standard points delivered through five channels
Five integration options
for different application needs
Gateway interfaces are accessible locally and remotely through Bivrost Cloud. Each channel provides its supported operations. HTTP and MCP share authentication; read and write access depends on equipment capabilities and API authorization.
Planned MCP write tools and MQTT event notifications.
Write tools (monitoring thresholds, collection task control, machine registration) map one-to-one onto existing HTTP write endpoints; events push state changes, alarm raised/cleared and part-count increments over MQTT. They reuse the authorized-API allow-list, add write auditing and rate limits, and every write tool requires explicit confirmation. Delivered with a firmware update.
Control systems and data supported
Support for mainstream CNC controls across six data categories. Confirm the specific model and configuration during evaluation. Laser cutters, robots and PLCs connect by machine type and are not covered by this table.
- Basic data
- Output / alarms / state / mode / tool no. / program no.
- Axis data
- Feed / override / spindle speed / coordinates / spindle and servo load
- OEE monitoring
- Run / setup / idle / e-stop / off time · utilization
- PLC data
- Read and write any PLC address, macro variable or user parameter
- Program transfer
- Read / upload / download / back up / push in bulk
- Tool data
- Tool number / offset read-write / tool life
Your system not listed? Tell us the model →
If a gateway fails,
a standby takes over in about 15 seconds
Cluster failover (optional), also called hot standby: all gateways under one cloud platform share a standby pool (N+1). When a gateway fails as a whole, the platform assigns an idle standby to run under its identity; once the original is repaired and stable, it switches back automatically.
heartbeat timeout before a standby is assigned
switch-over (measured 14–17 s), excluding per-machine reconnects
stabilization window before automatic switch-back
Shared standby pool
A standby is not tied to one gateway. It is registered in the cloud platform’s pool and stands by for every gateway under that platform; all gateways are protected by default.
Takeover = identity switch
A standby does not collect while idle. On takeover it imports the failed gateway’s configuration snapshot and restarts under that identity; cloud and dashboard data sources follow automatically.
One takeover at a time
A standby covers one gateway at any moment. If every standby is busy, the platform alarms instead of switching, then takes over as soon as one is released.
Automatic switch-back
A repaired gateway comes back read-only with collection stopped, then switches back after the stabilization window; the standby returns to the pool.
Same-site N+1
The standby sits on the same shop-floor LAN and keeps collecting after takeover; interfaces and dashboards continue.
Off-site DR
The standby sits at another site. After takeover it serves configuration, queries and dashboards only; it cannot reach the original machines.
Multiple standbys
Register several standbys to cover several gateways failing at the same time.
- Historical and time-series data live on the cloud platform and are not copied between hosts; a standby collects from the moment it takes over.
- The part-program directory must be synchronised at the operations level, for example by a scheduled task mirroring it to a share on the standby.
- The local shop-floor address is unavailable after a whole-host failure; the guaranteed entry point is the cloud platform address. For a seamless local address, configure DNS or a virtual IP.
140 machines. None left as “later”
140 machines across the plant, most of them old or non-standard: CNC machines connected by protocol, forging presses and furnaces registered as PLC machines, legacy manual machines reconstructed from IO loops. All three paths output the same points, and plant-wide OEE had a complete definition for the first time.
Bivrost Cloud
The gateway hands data to Bivrost Cloud for monitoring, analytics, asset management and program transfer.
Cloud product pageDNC Pro
Program file I/O goes through the gateway; versioning, approval and six-stage controlled deployment live in DNC Pro.
DNC Pro product pageAI applications
Bivrost Factory AI, developer agents and general-purpose AI assistants read through the same interfaces and MCP.
Developers page One gateway is enough to evaluate.
No line-wide retrofit
Share equipment models, quantities and application requirements to help confirm the trial configuration, pricing and shipping arrangements.
If no message appeared, copy the text below and send it to contact@bivrost.cn.