Scout MES reads data from supported CNC controls, robots, PLCs and other devices over your factory LAN. For CNC machines and PLCs this works with no electrical modifications. Machines without a CNC control are connected through our BIOS-IO-01 module. Below you can see what data Scout reads from each system. Most rows link to a connection guide.
Where the description says “configurable data”, we agree with you during deployment which signals, registers or fields to read. The data in the descriptions is available if the machine or device provides it; we check this with you before deployment.
Supported systems and protocols
| System / protocol | Type | Description | Guide |
|---|---|---|---|
| Beckhoff (TwinCAT) | Protocol | Configurable data: during deployment we specify the TwinCAT controller memory cells to read. | Details |
| BIOS-IO-01 | Other | Our module with digital inputs for machines without a CNC control: machine running, input states and pulse counters; part counter if a suitable signal is connected to the input. | |
| Bullmer | Other | Status (a new line in the file) and the program; the meaning of the other columns of the file is determined during deployment. | |
| Bystronic | Controller | Machine status: whether the machine is cutting and the control responds, mode (single, automatic or DNC) and the current program path. Production file: run status; other data is determined during deployment. | Details |
| Citizen | Controller | Status, mode, program number, feed rate and alarm text. Citizen machines with a Mitsubishi M70/M700 control use a separate communication library; with a Mitsubishi M800 control, data is read with the standard Mitsubishi protocol. | Details |
| cncGraF / InfoCAM | Controller | Status and mode. InfoCAM is the same application as cncGraF. | Details |
| CSV, SQL, XML, HTML | Protocol | Configurable data: during deployment we specify the columns of the CSV file or SQL database, the fields of the XML file or page, or the places on the machine’s HTML page. | |
| Delem | Controller | Whether production is running, and the program name. | Details |
| DMG MORI | Controller | Via MTConnect or directly from the machine’s control (Fanuc, Siemens Sinumerik or Mitsubishi). Via MTConnect: status, mode, program, part count, feed rate, feed override and alarms, if the machine’s MTConnect agent publishes them. Spindle data, tool and variables are determined during deployment. With a direct connection, the machine is handled like any machine with that control. | Details |
| Fanuc | Controller | Via FOCAS2 over Ethernet: status, mode, program name, part count, feed rate, feed override, spindle speed and load, tool, alarms with code and text, and macros. Spindle override is determined during deployment. Supported models: Series 0i-A, 0i-B, 0i-C, 0i-D, 0i-F (including 0i Mate-D and 0i Mate-F), 0i-PD, 0i-PF, 15, 15i, 16/18/21, 16i/18i/21i-A, 16i/18i/21i-B, 16i/18i-P, 16i-L, 16i/18i-W, 30i/31i/32i-A, 30i/31i/32i/35i-B, 30i/31i-P, 30i/31i-L, 31i-WA and 31i-WB, Power Mate i-H, Power Mate i-D and Power Motion i-A. | Details |
| Fanuc robots | Controller | Status, program name, line number, and selected inputs and stop signals. | Details |
| Haas | Controller | Haas CHC (RS232 and a LAN converter): status, mode, program name, part counters, spindle load, tool, alarm status (active / not active) and macros; spindle speed is determined during deployment. Haas NGC via MTConnect (setting 143): status, mode, program, part count, feed and spindle override and alarms, if the machine’s MTConnect agent publishes them; other data is determined during deployment. | Details |
| Heidenhain | Controller | iTNC 530: mode, program status and name, feed rate, feed and spindle override, spindle speed, tool, alarms with number and text, and PLC memory. TNC 620 and TNC 640: mode, status, feed rate, override, spindle speed, tool number and PLC memory. Part count is determined during deployment. | Details |
| HTTP (JSON) | Protocol | Configurable data: during deployment we specify the response fields from the machine’s page or API. An external system can also send messages to Scout itself. | Details |
| JDF / JMF | Protocol | Device status, job queue, job name and progress, and notifications. | Details |
| Kimla UDP | Controller | Lasers and CNC plotters with a Kimla control, data over the LAN (UDP): run status (start or stop), program name and alarms. | Details |
| Komax | Other | Production, sample and teach events with their time; which of them mean status, mode, program or count is determined during deployment. | |
| Mazak | Controller | Via MTConnect (the MTConnect option must be installed on the machine), for 640 (NEXUS, M, T, PRO), MATRIX, MATRIX2, SMART and Smooth controls, from both Mazak CNC machines and lasers: status, mode, program, feed rate, feed override and alarms, if the machine’s MTConnect agent publishes them. Part count, spindle data, tool and variables are determined during deployment. | Details |
| Mitsubishi | Controller | Cycle status (running, stopped or on hold), mode, program name, feed rate, spindle speed and load, tool, and control, PLC and operator alarms. | Details |
| Modbus TCP | Protocol | Configurable data: during deployment we specify the registers and binary signals to read. | Details |
| MQTT | Protocol | Configurable data: during deployment we specify the messages, usually in JSON. | Details |
| MTConnect | Protocol | Status, mode, program, feed rate, feed and spindle override, spindle speed and alarms, if the machine’s MTConnect agent publishes them. Part count, tool, spindle load and variables depend on the protocol version and are determined during deployment. | Details |
| OKUMA | Controller | Via MTConnect, for P100 Type II or newer, P200, P200A, P300 and P300S controls (the MTConnect Agent & Adapter package from the OKUMA App Store must be installed on the machine): status, mode, program, part count, feed rate, feed and spindle override, spindle speed and alarms, if the machine’s MTConnect agent publishes them. Spindle load, tool and variables are determined during deployment. | Details |
| Omron (FINS, C-Mode) | Protocol | Configurable data: during deployment we specify the controller registers (FINS or C-Mode). | Details |
| OPC UA, OPC DA (Classic) | Protocol | Configurable data: during deployment we specify the OPC UA or OPC DA signals to read. | Details |
| OSAI | Controller | Via the CNDEX communication library or, from OPENcontrol 3.2, also via SOAP/XML: status, mode, program name, feed rate, feed and spindle override, spindle speed, tool and the last error number. | Details |
| Program screenshot | Other | Running or idle, from the recognised state of the program window. | |
| Remmert | Other | Warehouse movements: time, from where, to where and which item. | |
| Rhotex | Other | Run status (running while printing), program name, job number, print number and progress percentage. | |
| Safan | Controller | Via Safan E-Control (the 2:42 E-Control Gateway option must be enabled on the machine): press mode and status, project name, part and stroke counters, validation messages, and material and drawing data. Alternatively through our BIOS-IO-01 module: machine running from the press pedal presses. | Details |
| Siemens Sinumerik | Controller | Sinumerik 828D and 840D sl, via S7 TCP or the OPC UA option: status, mode, program name, part count, feed override and tool. Other data, alarms and PLC variables are determined during deployment. | Details |
| Ping | Protocol | Only whether the device responds on the network. | |
| Siemens S7 (S7 TCP) | Protocol | Siemens S7-200, S7-300, S7-400, S7-1200/1500, LOGO! and similar. Configurable data: during deployment we specify the addresses in the S7 controller. Alarms and PLC variables are determined during deployment. S7-200/300/400 without an Ethernet module are connected through an S7 LAN adapter. | Details |
| PLC controllers | Other | How we connect PLCs: Beckhoff, Omron, Siemens S7 TCP (S7-200 to S7-1500 and LOGO!), Modbus TCP, OPC UA, OPC DA and MQTT. | Details |
| Teltonika | Other | Teltonika GSM telematics modules for mobile machines: device power state, module input states and travel speed (GPS). | Details |
| Trumpf Laser | Controller | Run status and program from the SQL database, or new lines of the CSV production file with their time. The Trumpf OSEON package may be required. | Details |
| KPZ, Radwag, SysTec scales | Other | KPZ: net weight and whether the reading is stable. Radwag and SysTec: weight, unit and measurement status. | |
| Yaskawa | Controller | Robot mode, whether it is running, job name, line and step, speed override and selected inputs. | Details |
| Zebra barcode readers | Other | The scanned barcode. | |
| Conventional and other machines | Other | Machines without a CNC control, connected through our BIOS-IO-01 module: machine running from an input signal, and a part counter if a suitable signal is connected. | Details |
How the connection works
Scout reads the data over your factory LAN, directly from the control, with no electrical modifications. The machine does not need internet access: SCT (Scout Configuration Tool) runs as Windows services on a computer in your network and sends the data to the Scout server over HTTPS, so you do not need to open any inbound ports. We install and configure SCT remotely. You prepare a Windows computer in the LAN and send us the list of machines (control type and IP address). Scout only reads data. It does not control machine motion.
For machines without a CNC control, see Legacy machine monitoring.
Frequently asked questions
Among others Fanuc, Heidenhain, Siemens Sinumerik, Haas, Mazak, OKUMA, DMG MORI, Mitsubishi, OSAI, Citizen, Delem, Safan and Bystronic, as well as machines with MTConnect. The table on this page shows what data Scout reads from each system.
Yes: Beckhoff, Omron, Siemens S7 (S7 TCP), and controllers that share data via Modbus TCP, OPC UA, OPC DA or MQTT. The data is configurable and agreed during deployment.
Write to us. During a free consultation we check which data Scout can read from your machine. Machines without a CNC control can be connected through our BIOS-IO-01 module.
We do, remotely. You prepare a Windows computer in your LAN and send us the list of machines; we install and configure SCT and connect the machines. To add a machine later, you write to us and we change the configuration remotely.
Talk to us
Not sure which data Scout can read from your machines? Talk to our expert during a free consultation.