Technology · Controllers · Connectivity

One connector layer across controller families.

Controllers differ in protocol, in what they expose and in how their variables are enumerated. Toleron isolates those differences in the connector layer and in a per-machine role mapping, so everything above it is brand-agnostic.

Controller families validated: 3
Paths: OPC UA · MTConnect · MQTT · sensors
Role mapping: Per machine, brand-agnostic

Validated in the lab

Controller	Machine	Path	Status
Siemens Sinumerik 840D sl	A.Haas Multigrind CB	OPC UA + alarm events + MQTT	Validated, live
Siemens Sinumerik 828D	Hanwha XD38II	OPC UA	Validated, live
Haas Next Generation Control	Haas TL-1	MTConnect	Validated, live
No controller	Ziersch surface grinder	Current clamp (CT-derived state)	Validated, live

Supported by protocol

Any controller exposing an OPC UA server (Heidenhain TNC with the OPC UA NC Server, Fanuc via OPC UA gateways, Mazak, Okuma and others), any MTConnect agent, and any MQTT publisher connects through the same three connectors. Controller profiles — how status codes and modes are classified — are configuration. We list a controller as validated only after we have measured its data end to end.

Read the specification

Enumerations are not guessable. The official controller documentation is consulted before a status code is trusted. That discipline is the difference between a dashboard that looks right and one that is right.

Go deeper

Platform