Industrial Gateway Without Points Tables for PLC, CNC and SCADA Data

Most gateway projects start with a spreadsheet. Someone lists every tag: spindle load, cycle count, alarm word, coolant level. Each tag gets an address, a data type and a scaling rule. That spreadsheet is the point table, and building it is slow. It also breaks the moment a machine is swapped or a PLC program is updated.

An industrial gateway without points tables skips that spreadsheet step. Instead of you mapping each tag by hand, the gateway walks the controller itself, reads the exposed data model, and publishes what it finds. On a Siemens or Rockwell PLC this usually means browsing the symbol table or tag database. On a Fanuc or Siemens CNC it means reading the documented parameters and register blocks.

The trade-off is control. You get faster commissioning and less manual mapping. You give up some of the fine-grained naming and scaling you would get from a hand-built table. For a plant with dozens of mixed machines, that trade is usually worth it. For a single critical line with ten tags, a point table is still fine.

One thing does not change. You still need to know which data matters and where it lives. The gateway finds the tags, but it cannot tell you that axis drift on station 3 is the number your maintenance team actually watches.

A PLC exposes data in a few standard ways. Modbus TCP and RTU are still the most common. EtherNet/IP, PROFINET and OPC UA are common on newer lines. The gateway speaks these protocols natively, so it can open a session and read the controller's memory or symbol space directly.

CNC controls are a different problem. Fanuc, Siemens 840D, Mitsubishi and Heidenhain each publish data through their own interface. Some use FOCAS, some use OPC UA, some use a proprietary API. A gateway that handles CNC well will have a driver for each control family rather than a single generic adapter.

The sampling rate you can reach depends on the control, not the gateway. A PLC scan cycle of 10 ms will not give you 1 ms data no matter what the gateway spec sheet says. Match your sample rate to the physical process you are watching. Vibration and tool wear need fast sampling. OEE counters do not.

Watch the read load. Polling a controller hard can slow its own scan cycle. Good gateways let you set per-tag poll intervals and back off when the controller is busy.

SCADA is the layer above the gateway. It aggregates, displays and stores. It is not a data source in the same sense a PLC or CNC is. When people talk about SCADA data acquisition, they usually mean getting plant data into the SCADA historian or HMI.

A gateway without point tables fits this layer well. It publishes a self-describing data model, so a SCADA system with OPC UA or MQTT support can subscribe and discover tags on its own. No manual tag entry in the SCADA project.

SCADA is a poor fit for fast machine-level signals. Historians typically store on change or on a one-second or slower interval. If you need waveform data for a spindle or a servo, capture it at the gateway or controller and pass it up as a batch.

Keep the boundary clear. Gateway reads the machine. SCADA reads the gateway. Mixing the two roles is where most data acquisition projects get tangled.

A gateway is a small box, but it lives in a hard place. It mounts inside a control cabinet or on a machine frame. It sees vibration, chip dust, coolant mist and heat. The enclosure and the mounting hardware take that abuse so the electronics do not.

We machine gateway and edge-device enclosures in aluminium and stainless. Common grades are 6061-T6 for the body and 304 or 316L for washdown areas. Wall thickness usually lands between 1.5 mm and 3 mm depending on the drop and vibration spec.

Sealing matters more than wall thickness on a washdown cabinet. A machined groove for an O-ring gasket holds tolerance better than a folded sheet metal lip. We hold ±0.005 mm on critical sealing faces when the design calls for it.

Internal features carry the board. Standoffs, card guides and heat-sink pockets are milled into the same block, so the PCB sits flat and the thermal path to the case is short. DIN-rail clips, mounting ears and cable glands are cut in the same setup when the geometry allows.

For prototypes we run 5-axis on a single block and finish with bead blasting or anodizing. For production runs the same part moves to mill-turn or die casting, depending on volume. No minimum order quantity, so a one-off enclosure and a 10,000-part run use the same drawing.