Haas machine monitoring, native over MTConnect
Every Haas built on the NGC control since 2016 already runs an MTConnect agent — no adapter to buy, no software to install. ThingConnect reads it directly, the same read-only way it reads every MTConnect source.
NGC: MTConnect that's already running
Haas's Next Generation Control (NGC), shipping since 2016, is the rare case in machine-tool connectivity where the builder didn't just license a protocol — they shipped the agent live, on the machine, by default. There's no separate adapter to install and no option to purchase: the MTConnect agent runs on the control's own network interface as soon as the machine is on the network.
Internally, the NGC's MTConnect adapter feeds data to the agent over port 5051 on the machine itself — an implementation detail that doesn't matter to a client, since the agent is what a monitoring system actually talks to.
How ThingConnect reads it
| Step | What happens |
|---|---|
| Network the machine | An Ethernet cable from the NGC control to the plant network — most shops already have this for remote DNC or Haas Connect. |
| Verify the agent | Browse to http://<machine-ip>:8082/current from the plant network — a returned XML document confirms the agent is live and reachable. |
| The gateway reads it | Our gateway polls the agent's XML stream over port 8082 and turns it into the same live floor view, OEE, and downtime data every other connection type feeds. |
Port note: 8082 is dedicated to the MTConnect agent — it's separate from the range (9090–9999) the Haas control uses internally, so reading it doesn't collide with anything else running on the machine's network stack.
Pre-NGC Haas machines
Haas machines built before the NGC transition run the older "classic" control, which has no built-in MTConnect agent. Those machines aren't excluded from the dashboard — they connect through a third-party MTConnect adapter where one fits the shop's setup, or through digital I/O where it doesn't, with the same honest labeling on connection depth as every other legacy control on a mixed floor.
Questions
Frequently asked questions
If it's an NGC-generation control — the Next Generation Control Haas introduced in 2016, identifiable by its widescreen interface — yes, the MTConnect agent is already running with nothing to install. Machines on the older, pre-NGC classic control don't have it and need a third-party adapter instead.
From any computer on the same network as the machine, browse to http://<machine-ip>:8082/current. If an XML document comes back with the machine's current data items, the agent is up and reachable. We do this check per machine during the fleet survey rather than assuming NGC always means reachable — firewall rules and network segmentation vary by plant.
No — 8082 is the MTConnect agent's own dedicated HTTP port, separate from the ports (9090–9999 and others) the Haas control itself uses internally. Reading from it is a standard HTTP GET against an XML endpoint; it doesn't touch the control panel, the running program, or machine parameters.
They don't have a Haas-built MTConnect agent, but that doesn't mean they're unreachable — third-party MTConnect adapters exist for classic-control Haas machines, and where that's not practical, a digital I/O connection covers the gap so the whole fleet still lands on one dashboard.