Machine Integrations

The CNC and machine-tool brands ThingConnect connects to

Two paths cover every brand below: a native, controller-specific integration where we've built one, and the open industrial protocols already covered on this site everywhere else. Both land on the same dashboard — the initials badges are placeholders, not a signal either way about which path a brand uses, see each card's own copy for that.

Book a demo Request a pilot deployment

Controller brands

FANUC

Our deepest integration — native, read-only over FOCAS: machine state, part counts, cycle times, alarms, programs, and spindle load, direct from the control.

See the FANUC connection →

Brother

Brother Speedio CNCs connect over OPC UA — the open industrial protocol their newer controls expose, read the same secure, read-only way as everything else on OPC UA.

See how OPC UA connects →

Siemens

SINUMERIK controls run OPC UA natively — Siemens' own “Access MyMachine / OPC UA” server ships on SINUMERIK ONE, 840D sl, and 828D, and Siemens is a lead OPC Foundation contributor behind the umati machine-tool companion spec. MTConnect needs a third-party adapter here, not a Siemens-built one.

See the Siemens connection →

Haas

Every Haas NGC-generation control (2016 onward) runs MTConnect natively — the agent is live on port 8082 with nothing to install, Haas's own official path onto the dashboard. Pre-NGC controls need a third-party adapter instead.

See the Haas connection →

Mazak

Mazak's own SmartBox reads MAZATROL and Smooth-control machines over MTConnect natively — a Mazak-built device, not a third-party bridge. The current SmartBox 2.0 adds MQTT and OPC UA alongside it.

See the Mazak connection →

Okuma

Any OSP-P control (P200/P300 and newer) is MTConnect-ready using Okuma's own adapter, distributed through its OSP App Store. Newer OSP-P500M/P700A controls add a factory OPC UA server too, but MTConnect is the one confirmed across the wider OSP-P line.

See the Okuma connection →

Mitsubishi

Mitsubishi publishes its own MTConnect adapter and agent — the NC Machine Tool Connector — for the M700/M70, M700V/E70, and M800/M80/E80 control series. We couldn't confirm native OPC UA on the CNC side from official documentation, so that claim stays off this card.

See the Mitsubishi connection →

Heidenhain

TNC 640-class controls take Heidenhain's own OPC UA NC Server as an add-on option, built to the OPC Foundation's companion-specification template. Older controls without it — iTNC 530, TNC 320 — fall back to Heidenhain's proprietary DNC interface instead.

See the Heidenhain connection →

Industrial protocols

The open standards behind every brand above that doesn't have a dedicated integration — and behind quite a bit of the ancillary equipment around the machines too.

MTConnect

The machine-tool industry's open, read-only standard. Where a builder ships an MTConnect agent, the gateway reads it — one format across brands.

OPC UA

Industrial automation's common language, with security built in — the path Brother and other newer controls, PLCs, and ancillary equipment use.

Modbus

The long-standing serial/TCP standard for meters, drives, and sensors — read directly, or bridged from RS485 through our own converters.

What is Modbus →

MQTT

A lightweight publish-subscribe protocol built for constrained, unreliable connections — our own RS485-to-WiFi converter speaks it natively for devices with no network stack of their own.

Don't see your brand?

Fleets are mixed, and control generations vary even within one brand. Send us your machine list and we'll tell you, machine by machine, how each one connects — the fleet survey is part of every pilot, before anything is quoted. See the industrial protocols we support above, or digital I/O for machines whose controls can't speak to a network at all.

See your brand's connection live, on your control generation

Book a demo Request a pilot deployment