Industrial Data Gateways

Field protocols behave badly; the gateway is where that gets handled, with buffering that survives a dropped link.

Protocol translation and edge buffering between plant-floor buses and the systems upstream — designed to lose no data when the link goes down.

Industrial gateway protocol bridgeField protocols in, one normalised model out. The buffer matters because the uplink will drop and the plant does not stop when it does.Modbus RTURS-485MQTTbroker · TLSGatewayone data modelunits · scalingCAN · CAN FDJ1939 · CANopenREST · historiannorth-boundOPC UAEthernetStore and forwardsurvives a drop

Scope

What we do

  • Protocol bridging: Modbus RTU/TCP, OPC UA, CAN/CAN FD, PROFINET, EtherCAT to MQTT or a REST endpoint.
  • Store-and-forward buffering over intermittent cellular or radio links, with ordering and timestamps preserved.
  • Normalisation of multi-vendor field devices onto one upstream data model.
  • Edge pre-processing — aggregation, rate limiting, alarm logic — to cut backhaul.
  • Remote configuration and OTA update of deployed gateways.
  • Condition- and remote-monitoring pipelines end to end, sensor to dashboard.

Typical stack

  • modbus
  • opc-ua
  • can-fd
  • profinet
  • ethercat
  • mqtt
  • rs-485
  • ota-updates
  • cellular-iot
  • lorawan

Standards worked to

Applicable standards are agreed at the start of a programme and written into the scope. Certificates we hold are shared on request.

Talk to an engineer

Ask about this capability directly — the person who answers has shipped it.