Connectivity

Talks to your machines.

Eight industrial protocols ship in the product. Point MACHHUB at a PLC, a meter or a serial device, and the values land in your namespace as tags.

Start the trial See the editions

The protocols, by name

No gateway licence tier to buy, no per-protocol add-on. Every driver below is in every edition, including Edge.

OPC UA

None, Sign, or Sign and Encrypt
OPC UA
Modbus

TCP and RTU
Modbus
Serial

RS-232 and RS-485
Serial
MELSEC

Mitsubishi

MC protocol
MELSEC (Mitsubishi)
FINS

Omron
FINS (Omron)
MEWTOCOL

Panasonic
MEWTOCOL (Panasonic)
SIMATIC S7

Siemens

S7-200 over PPI, S7-300 to S7-1500 over S7comm
SIMATIC S7 (Siemens)
ADS / TwinCAT

Beckhoff
ADS / TwinCAT (Beckhoff)

Connecting more machines never costs more.

Drivers are not metered. The licence price follows the edition and the number of application domains, nothing else. See pricing.

Commissioning

Built for the cabinet, not the lab.

The PLC protocols run over TCP, UDP, Serial (RS-232/485). Serial links get the tooling that makes a first connection quick.

Line settings, detected

Scan a port and MACHHUB reports the baud rate, data bits, parity and stop bits. You do not guess them from a manual nobody kept.

Power-cycle a stuck port

Stop the adapters holding a USB serial port, re-enumerate the device and restart them. No reboot, no site visit.

Watch the line

A live TX and RX log stream shows what the device is actually sending while you commission it.

Once a site is running, one request returns the state of every data source in the domain, so a list view shows what is connected without checking each device in turn.

Flow logic

Node-RED, when you want it

Embedded on the node with MACHHUB nodes, so flow logic reads and writes the same tag tree as everything else. Use it for the awkward source that has no driver, for protocol conversion, or for logic you would rather draw than write.

It sits beside the drivers rather than in front of them. A PLC does not need a flow to reach the namespace.

@machhub-dev/node-red-nodes

Where data can come from

01 A native driver, for the eight protocols above.
02 Any MQTT publisher, straight into the built-in broker.
03 A Node-RED flow, for everything else.
04 A MySQL table, through Data Bridge.

All four land in the same namespace. The tag on a dashboard is the tag an application reads and the tag sent upstream.

Data Bridge

Keep the plant database in step.

Connect MACHHUB to the MySQL database your MES or ERP already reads, in both directions.

Both directions

Pollers read tables on a schedule and publish into the namespace. Writes go the other way, into the tables and columns you map.

Survives an outage

Outbound writes queue to a durable on-disk buffer that survives a restart, then drain in order when the database comes back.

Backfill on demand

Re-send a period from the historian as a paced job you can cancel. Rejected writes wait in a dead letter queue with the error kept.

Credentials stay sealed

Database credentials are sealed at rest and scrubbed from error output. The whole configuration exports and imports as JSON.

Run it before you talk to us.

Install MACHHUB, connect one machine, and see the tags arrive. The trial needs no licence key and no registration, and you can start it again as often as you like.

Start the trial Talk to us