# How do I connect my controller?

> First the route, then the brand. Start from what is already in your panel.

For integrators and panel builders. https://wertek.ai/integrators/controllers/

## How to read this page

- Every method and every brand row is a reference, according to the manufacturer's documentation linked in each row. “?” and “unverified” mean exactly that.
- Brand and model names are used only to identify the product; they belong to their owners.

## Why bring your customers

You already automated the machine. What is not your business is everything that comes after, so that your customer sees the equipment and keeps the history.

### What costs you today

- **You deliver the panel and the relationship ends.** With the provider access your customer grants you, the equipment stays in your own Assets list.
- **Warranty calls arrive without data: “it stopped, I do not know when”.** There is a trend and a history of what the PLC already measures. You see the readings inside the window your customer grants you.
- **A web screen, a database and a report built for each customer.** You do not build them: you map the signals to a template and the trend is already there.

### What your customer needs

- **To see the equipment without going to the site.** The last reading and the trend, in the browser of a phone.
- **Evidence of what happened and when.** History and trends, with CSV export.
- **That a finding becomes work.** An observation becomes a work order.
- **Not to be tied to one integrator.** The asset and its data are theirs; they grant your access and take it back.

[How the access works, step by step](https://wertek.ai/engineering/industry-4-0/#lend) · [What your customer gets, and the price](https://wertek.ai/integrators/iaes/)

## What it is for, and what it is not

> A reading every 300 seconds is for staying informed: notifications, history and trends. It is not an emergency response. Stopping, protecting and the immediate alarm stay with the PLC and the panel.

In every method the control stays in the PLC. Wertek AI only receives. If the internet goes down, the machine keeps working the same.

| Need | Who solves it |
| --- | --- |
| Stopping a pump, tripping a protection | The PLC and the interlocks of the panel. Local communication. |
| An alarm someone must attend within seconds | The local alarm of the panel (beacon, siren, HMI). |
| Seeing the trend and keeping the history of what the PLC already measures | Wertek AI. |

If something has to happen faster than the cadence, this connection is not the answer: local communication is.

## The five methods

The brands we reviewed come down to five methods. You choose one; the rest is the signal map.

### M1 · Serial with a gateway (Untested)

- **For whom:** The PLC or module only has RS-485 (Modbus RTU).
- **What is added to the panel:** A gateway with RS-485 that reaches the internet.
- **Status:** Untested.

**How it would be done**

- The PLC is the Modbus slave. A gateway polls it over RS-485 and sends the registers.
- Cellular gateway: the Teltonika TRB145 is the one with RS-485 (the TRB140 has Ethernet and no RS-485). It works as a Modbus RTU client (master). Its “Data to Server” takes Modbus as an input, with an add-on package installed from its Package Manager, and sends over HTTP with the TLS option, or over MQTT, as JSON, a custom format or a Lua script. It fits where the customer has no network.
- Or a device with Node-RED and a USB to RS-485 adapter: the Modbus node (node-red-contrib-modbus) reads, the IAES node sends.
- Teltonika straight to Wertek AI: possible on paper, with the Lua script format. Untested. The specific doubt: generating a unique identifier per reading and putting the time of the measurement, which the IAES envelope requires.

**Rows of the tables that point here:** Delta DVP (ES2, SS2) · LS Electric XGB · Kinco K2 · Schneider M221 · Schneider Zelio · Brainchild IO (IO-8AII, IO-8TC, IO-6RTD, IO-16DI…) · Advantech ADAM-4000

**Brand by brand, per the manufacturer**

| Brand and PLC | How it would be done |
| --- | --- |
| Siemens LOGO! | With the CIM communication module (RS-232, RS-485, RS-422). |
| Siemens S7-1200 | The CPU has no serial port: a CM 1241 module or a CB 1241 board (RS-485) adds it, as Modbus master or slave. |
| Allen-Bradley Micro800 | A serial port configured as Modbus RTU. |
| Finder OPTA | The versions with RS-485; the manufacturer publishes Modbus RTU tutorials. |
| Delta DVP (ES2, SS2) | Built-in RS-485; the catalogue gives master or slave, Modbus ASCII or RTU, for the SS2. Most of them have no Ethernet; the ES2-E and the SE do. |
| WAGO Compact Controller 100 | One RS-485 port with Modbus RTU. |
| Weidmüller u-control UC20-WL2000-IOT | The controller has no serial port: the UR20-1COM-232-485-422 module adds it, as Modbus RTU master (release notes). Done by us in the field, not a manufacturer statement: the registers are not read from Node-RED directly; a Modbus register map in the controller configuration ties them to tags, and the Node-RED of the controller uses those tags. |
| Kinco (K2, K5, K6) | K2: RS-485 ports with Modbus RTU, master or slave, per the manual. K6: two RS-485 ports, Modbus RTU or ASCII, master or slave, per its spec sheet. K5: unverified. |
| LS Electric XGB | RS-485 built into the CPU with Modbus RTU and ASCII; XBL-C41A modules for more ports. |
| Mitsubishi FX5U | Built-in RS-485 with Modbus RTU, master or slave. |
| Schneider M221 | Serial line with Modbus RTU. |
| AutomationDirect CLICK PLUS | It depends on the CPU. C2-03CPU: RS-485 built in. C2-01CPU: RS-232 only, so it needs a converter to RS-485. C2-02CPU: no serial port. |
| Unitronics UniStream | Modbus RTU through the RS-485 of the Modular CPU, or through a serial COM module ordered apart. The Built-in series lists Ethernet and USB, no serial port. |
| Schneider Zelio | With the SR3MBU01BD module (RS-485, Modbus), on the SR3 B…BD relays (24 V DC). |
| Eaton easyE4 | With the EASY-COM-RTU-M1 communication module. The base unit has Ethernet, so Modbus TCP is its natural route. |

**Sources:** [Teltonika, gateway families (which model has RS-485 or Ethernet)](<https://wiki.teltonika-networks.com/view/Teltonika_Networks_Gateways_Families>) · [Teltonika, TRB145 (the gateway with RS-485)](<https://wiki.teltonika-networks.com/view/TRB145>) · [Teltonika, TRB145 Data to Server](<https://wiki.teltonika-networks.com/view/TRB145_Data_to_Server>) · [Siemens, Modbus RTU on the S7-1200 (entry 47756141)](<https://support.industry.siemens.com/cs/document/47756141/>) · [Eaton easyE4, product cybersecurity guideline (MZ049001EN)](<https://es-assets.eaton.com/DOCUMENTATION/AWB_MANUALS/MZ049001EN.pdf>) · [Schneider, Zelio Logic catalogue (January 2022)](<https://download.se.com/files?p_Doc_Ref=DIA3ED2111202EN&target=new>) · [Kinco K6, spec sheet (copy hosted by a distributor)](<https://anaheimautomation.com/media/anaheim/literature/manuals/plc/L011958%20-%20KNC-PLC-K6%20Series%20Spec%20Sheet.pdf>) · [Weidmüller UC20-WL2000-IOT, release notes](<https://assets.dam.weidmueller.com/assets/api/dc161464-10dc-4f56-8675-8c2e857f445e/Original/UC20-WL2000-IOT_Release-Notes_1334990000.pdf>)

### M2 · Ethernet with Node-RED (Partly tested)

- **For whom:** The PLC has Ethernet: Modbus TCP, or the brand's own protocol (S7, EtherNet/IP).
- **What is added to the panel:** A small device with Node-RED on the panel network.
- **Status:** Node-RED → Wertek AI: tested. Reading the PLC: not tested.

**How it would be done**

- The PLC is a Modbus TCP server. On the same network, a device with Node-RED reads the registers at the cadence of the position (300 s by default) and sends them with the IAES node (node-red-contrib-iaes). Reference flow.
- If you already read your PLC in Node-RED, you only add the IAES node, paste the key and deploy.
- Node-RED also opens the brands' own protocols without going through Modbus: node-red-contrib-s7 for Siemens S7 controllers, node-red-contrib-cip-ethernet-ip for Allen-Bradley controllers over EtherNet/IP (Micro800: unverified). These nodes are third-party; we have not tested them.
- If the CPU has no Ethernet, the manufacturer's module: DVPEN01-SL (Delta SS2), XBL-EMTA (LS), SR3NET01BD (Zelio).

**Rows of the tables that point here:** Delta DVP-SE (12SE, 26SE) · LS Electric XGB · Kinco K2 · Siemens LOGO! 8 · Siemens S7-1200 · Eaton easyE4 · Schneider M221 · Schneider Zelio · Allen-Bradley Micro850 · Mitsubishi FX5U · AutomationDirect CLICK PLUS · Brainchild IO (IO-8AII, IO-8TC, IO-6RTD, IO-16DI…) · Advantech ADAM-6000 · Moxa ioLogik E1200

**Brand by brand, per the manufacturer**

| Brand and PLC | How it would be done |
| --- | --- |
| Eaton easyE4 | Modbus TCP server and client; the server has a read-only mode and a configurable port (firmware 2.30). |
| Siemens LOGO! 8 | Built-in Ethernet. Modbus TCP server and client on LOGO! 8 from the 8.FS4 series, per the system manual (edition 7/2022), which covers up to LOGO! 8.3; it does not name the 8.4: unverified for that one. The node node-red-contrib-s7 also carries notes for reading a LOGO! 8. |
| Siemens S7-1200 | Modbus TCP through program blocks (MB_SERVER, MB_CLIENT): the server block has to be programmed in the PLC. Or read it with the node node-red-contrib-s7, without the Modbus map; the documentation of the node asks to permit PUT/GET access in the CPU and to turn off optimized block access in the data blocks to be read. |
| Schneider M221 | Modbus TCP server, up to 8 clients. Only the TM221CE and TM221ME references have the Ethernet port. |
| Schneider Zelio | Ethernet module SR3NET01BD: Modbus TCP server, on the SR3 B…BD relays (24 V DC). Connection limit: not in what we read. |
| Allen-Bradley Micro850 | Modbus TCP server; the Micro850 L50E takes up to 16 simultaneous connections. Micro820: unverified. The node node-red-contrib-cip-ethernet-ip reads Allen-Bradley controllers over EtherNet/IP; its page names no model, so whether it reads the Micro800: unverified. |
| Delta DVP-SE (12SE, 26SE) | Built-in Ethernet with Modbus TCP. In the rest of the DVP series: the ES2-E version has Ethernet built in, and the SS2 takes the DVPEN01-SL module. AS series: the brochure shows Ethernet and two RS-485 on the AS300 and names Modbus TCP on its communication cards; on the CPU itself it says only Modbus. |
| WAGO Compact Controller 100 | Modbus TCP and UDP; two Ethernet ports. |
| Weidmüller u-control UC20-WL2000-IOT | Modbus TCP server, with its configuration screen in the web interface from firmware 1.13.0. This is the IOT model; the UC20-WL2000-AC is another product. |
| LS Electric XGB (XBC/XEC, U type) | The XBL-EMTA module is a Modbus TCP client and server. The catalogue lists Modbus TCP/IP on the Ethernet built into the U type; whether as server or client is not stated. |
| AutomationDirect CLICK PLUS | Modbus TCP client and server. C2-01CPU and C2-03CPU have Ethernet; C2-02CPU and C2-03CPU have Wi-Fi. |
| Unitronics UniStream | Modbus TCP. A PLC with a built-in screen. |
| Mitsubishi FX5U | Built-in Ethernet; Modbus TCP server (slave) and client (master), with CPU firmware 1.060 or later, per the manufacturer. |
| Kinco (K2, K6) | K2: only the K204ET has Ethernet, and it is a Modbus TCP server. K6: Modbus TCP client and server, per its spec sheet. K5: unverified. |
| Finder OPTA | Modbus TCP server or client; manufacturer tutorials. |
| Eaton easyE4 (JSON) | The community node node-red-contrib-easye4-json uses the JSON API of the easyE4 web server. |

**Sources:** [Siemens, Modbus/TCP between two S7-1200 CPUs (entry 83130159)](<https://support.industry.siemens.com/cs/document/83130159/>) · [Siemens, LOGO! system manual, edition 7/2022 (entry 109741041)](<https://support.industry.siemens.com/cs/document/109741041/>) · [node-red-contrib-s7 (Node-RED library)](<https://flows.nodered.org/node/node-red-contrib-s7>) · [node-red-contrib-cip-ethernet-ip (Node-RED library)](<https://flows.nodered.org/node/node-red-contrib-cip-ethernet-ip>) · [S7 and EtherNet/IP nodes in Node-RED (article by FlowFuse)](<https://flowfuse.com/blog/2023/06/node-red-as-a-no-code-ethernet_ip-to-s7-protocol-converter>) · [node-red-contrib-easye4-json (community package)](<https://flows.nodered.org/node/node-red-contrib-easye4-json>) · [Delta DVPEN01-SL manual (copy on a manuals site)](<https://www.manualsdir.com/manuals/78254/delta-dvpen01-sl.html?page=5>) · [Delta AS series brochure (copy hosted by a distributor)](<https://www.dicomp.com.br/downloads/materiais_apoio/datasheet/25735-1.pdf>) · [Kinco K6, spec sheet (copy hosted by a distributor)](<https://anaheimautomation.com/media/anaheim/literature/manuals/plc/L011958%20-%20KNC-PLC-K6%20Series%20Spec%20Sheet.pdf>)

### M3 · Node-RED inside the controller (Untested)

- **For whom:** The controller already runs Node-RED.
- **What is added to the panel:** Nothing.
- **Status:** Untested.

**How it would be done**

- The same as method 2, without the extra device: the IAES node would be installed in the Node-RED of the controller.

**Rows of the tables that point here:** WAGO Compact Controller 100 · Weidmüller u-control UC20-WL2000-IOT

**Brand by brand, per the manufacturer**

| Brand and PLC | How it would be done |
| --- | --- |
| WAGO Compact Controller 100 | Linux controller; the data sheet names Node-RED, Python and C++ as engineering tools. The IAES node would be installed in the Node-RED of the PLC. Untested. |
| Weidmüller u-control IoT (UC20-WL2000-IOT) | Node-RED comes from the factory in the controller, with a quick start guide from the manufacturer. Done by us in the field: reading Modbus through the register map, the tags and this Node-RED. From this Node-RED to Wertek AI: untested. Risk: the firmware notes we read cite Node-RED 1.1.2 (firmware 1.10.0, November 2020) and stop at firmware 1.13.1 (June 2021); our node was tested on 5.0.6. Whether it works there: untested. |

**Sources:** [WAGO Compact Controller 100 (751-9301), data sheet (copy hosted by a distributor)](<https://assets.cef.co.uk/downloads/pdg/wago_751-9301_datasheet/wago_751-9301_datasheet.pdf>) · [Weidmüller UC20-WL2000-IOT, release notes](<https://assets.dam.weidmueller.com/assets/api/dc161464-10dc-4f56-8675-8c2e857f445e/Original/UC20-WL2000-IOT_Release-Notes_1334990000.pdf>) · [Weidmüller, Node-RED quick start guide](<https://assets.dam.weidmueller.com/assets/api/945525f8-95e0-46e1-9d2d-0edd7e991118/Original/QuickstartGuide_IOT_NODE_RED.pdf>)

### M4 · MQTT with a translator in the cloud (Partly tested)

- **For whom:** The equipment publishes MQTT by itself.
- **What is added to the panel:** Nothing.
- **Status:** n8n → Wertek AI: tested. Equipment → MQTT: not tested.

**How it would be done**

- None of these devices speaks IAES from the factory: they publish in their own format. A translator is needed, and it can run in the cloud.
- Equipment → MQTT → a flow in n8n or Node-RED in the cloud → IAES event → Wertek AI.
- It needs a broker and someone to host the translator flow.

**Rows of the tables that point here:** Siemens S7-1200 · Eaton easyE4 · AutomationDirect CLICK PLUS · Unitronics UniStream · Finder OPTA · Advantech ADAM-6000 · Advantech WISE-4000 · Banner DXM700 · Balluff BCM + CMTK (BAV002N)

**Brand by brand, per the manufacturer**

| Brand and PLC | How it would be done |
| --- | --- |
| Siemens LOGO! 8.4 | The distributor note speaks of a preconfigured cloud or open MQTT. Not confirmed with Siemens: unverified. |
| Siemens LOGO! 9 | On sale from 1 April 2026, per Siemens; the CIM, CSM and CMK 2000 modules work with it. Modbus TCP and MQTT on LOGO! 9: unverified. |
| Eaton easyE4 | MQTT to a generic broker from firmware 2.40, per the Eaton release notes: publish and subscribe, with topics set by the user. |
| Siemens S7-1200 | MQTT client through the LMQTT library of Siemens; MQTT 3.1.1, and the connection can go over TLS. It needs CPU firmware V4.4 or later, per the Siemens documentation. |
| Finder OPTA | MQTT with TLS, per an Arduino tutorial that connects the Opta to AWS IoT Core. |
| WAGO Compact Controller 100 | MQTT, per the data sheet. |
| Weidmüller u-control IoT | The manufacturer publishes a note on MQTT from Node-RED. |
| Unitronics UniStream | MQTT client: it publishes and subscribes. |
| AutomationDirect CLICK PLUS | MQTT in the CPUs with Ethernet or Wi-Fi: it publishes and subscribes. MQTT over TLS is not in what we read. |
| Delta DVP, LS XGB, Kinco | We did not find MQTT in what we read: they go through Modbus RTU or Modbus TCP. |

**Sources:** [Weidmüller, MQTT from Node-RED](<https://assets.dam.weidmueller.com/assets/api/3a28b836-ea6d-450d-b47f-0879dc43b76d/Original/Temperature_Controller_with_MQTT_publisher_in_Node_RED.pdf>) · [Unitronics UniStream, MQTT](<https://www.unitronicsplc.com/Download/SoftwareHelp/%21UniLogicWebhelp2024/Communications/MQTT.htm>) · [Siemens, the SIMATIC controller as an MQTT client (entry 109748872)](<https://support.industry.siemens.com/cs/document/109748872/>) · [Eaton easyE4, firmware 2.40 release notes](<https://es-assets.eaton.com/AUTOMATION/DOWNLOAD/DOWNLOADCENTER/EASY/easyE-series/easyE4/ReleaseNotes/easyE4_FW_V240_MZ049013EN.pdf>) · [Arduino, Opta to AWS IoT Core over MQTT (tutorial)](<https://docs.arduino.cc/tutorials/opta/getting-started-with-aws-iot-core>) · [Siemens, press release on LOGO! 9](<https://press.siemens.com/global/en/node/7352>) · [Siemens, LOGO! communication modules (LOGO! 9)](<https://www.siemens.com/en-gb/products/logo/communication/>)

### M5 · Direct HTTPS (Untested)

- **For whom:** The equipment is programmable and has a web client.
- **What is added to the panel:** Nothing.
- **Status:** Untested.

**How it would be done**

- The program of the equipment builds the IAES event and sends it over HTTPS, without a translator.

**Rows of the tables that point here:** Siemens S7-1200 · Unitronics UniStream · Finder OPTA · Banner DXM700

**Brand by brand, per the manufacturer**

| Brand and PLC | How it would be done |
| --- | --- |
| Siemens S7-1200 | The LHTTP library of Siemens exchanges data with a web server over HTTP or HTTPS, with blocks for GET, POST and PUT. It needs CPU firmware V4.4 or later, per the Siemens documentation. Sending the IAES event with it: untested. |
| Finder OPTA | Programmable: it can send HTTP by itself. The manufacturer's tutorial uses plain HTTP and Wertek AI requires HTTPS. TLS is documented for MQTT; an HTTPS client is not in what we read. Untested. |
| Unitronics UniStream | REST client over HTTP or HTTPS. Whether it can send the IAES event directly: untested. |

**Sources:** [Finder OPTA, HTTP requests](<https://opta.findernet.com/es/tutorial/http-client>) · [Unitronics UniStream, REST API](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/REST_API.htm>) · [Siemens, communication libraries for S7-1500 and S7-1200: LHTTP, LMQTT (entry 109780503)](<https://support.industry.siemens.com/cs/document/109780503/>)

The last stretch is always the same: an IAES event to Wertek AI over HTTPS, with an ingest key (permission iaes.ingest). What you do per project is a table: this PLC register is this variable of the template.

## Which method fits my equipment

Reference table, according to each manufacturer's documentation.

✔ the manufacturer documents it · ➕ with the adapter named · ? unverified · — does not apply, or we did not find it in the documentation we read

<!-- tabla:marcas -->
| Brand and PLC | Modbus RTU | Modbus TCP | MQTT | HTTPS | Natural method | Source |
| --- | --- | --- | --- | --- | --- | --- |
| **Delta DVP (ES2, SS2)** | ✔ built-in RS-485 | ➕ SS2: DVPEN01-SL module, which the catalogue lists among the left-side modules. ES2: Ethernet comes in the ES2-E version | — | — | M1 | [Delta DVP series catalogue (copy hosted by a distributor)](<https://www.dicomp.com.br/downloads/materiais_apoio/datasheet/DVP-1.pdf>) · [Delta DVPEN01-SL manual (copy on a manuals site)](<https://www.manualsdir.com/manuals/78254/delta-dvpen01-sl.html?page=5>) |
| **Delta DVP-SE (12SE, 26SE)** | ✔ two RS-485 ports; one on the 26SE | ✔ built-in Ethernet | — | — | M2 | [Delta DVP series catalogue (copy hosted by a distributor)](<https://www.dicomp.com.br/downloads/materiais_apoio/datasheet/DVP-1.pdf>) |
| **LS Electric XGB** | ✔ built-in Cnet | ➕ XBL-EMTA module. The U type lists Modbus TCP/IP on its built-in Ethernet, per the catalogue; whether as server or client is not stated | — | — | M1 · M2 | [LS Electric XGB Cnet I/F user manual (copy hosted by a distributor, AutomationDirect)](<https://cdn.automationdirect.com/static/manuals/lselectric/xblcx1ausermanual.pdf>) · [LS Electric XBL-EMTA, cut sheet (distributor, AutomationDirect)](<https://cdn.automationdirect.com/static/specs/cutsheet/XBL-EMTA_cutsheet.pdf>) · [LS Electric XGB series catalogue, 2022 (copy hosted by a distributor)](<https://shop.tech-con.ro/media/catalog/product/pdf/./XGB%20Series_Catalog_EN_202205.pdf>) |
| **Kinco K2** | ✔ master or slave, per the manual | ✔ only the K204ET, as a server | — | — | M1 · M2 | [Kinco K2, user manual (copy hosted by a distributor)](<https://anaheimautomation.com/media/anaheim/files/manuals/plc/L011929_-_K204_PLC_User_Manual.pdf>) |
| **Siemens LOGO! 8** | ➕ CIM module | ✔ LOGO! 8 from the 8.FS4 series: server and client, per the 2022 system manual, which covers up to LOGO! 8.3. For 8.4: unverified | ? LOGO! 8.4: the distributor note speaks of a preconfigured cloud or open MQTT; not confirmed with Siemens | — | M2 | [Siemens, LOGO! communication](<https://www.siemens.com/es-mx/products/logo/communication/>) · [Siemens, LOGO! system manual, edition 7/2022 (entry 109741041)](<https://support.industry.siemens.com/cs/document/109741041/>) · [LOGO! 8.4, press note of a distributor (Mouser)](<https://www.mouser.pl/newsroom/publicrelations-siemens-logo-logic-modules-2024final>) |
| **Siemens S7-1200** | ➕ CM 1241 module or CB 1241 board | ✔ program block, or the S7 node | ✔ Siemens LMQTT library; CPU firmware V4.4 or later | ✔ Siemens LHTTP library; CPU firmware V4.4 or later | M2 · M4 · M5 | [Siemens, Modbus/TCP between two S7-1200 CPUs (entry 83130159)](<https://support.industry.siemens.com/cs/document/83130159/>) · [Siemens, Modbus RTU on the S7-1200 (entry 47756141)](<https://support.industry.siemens.com/cs/document/47756141/>) · [Siemens, the SIMATIC controller as an MQTT client (entry 109748872)](<https://support.industry.siemens.com/cs/document/109748872/>) · [Siemens, communication libraries for S7-1500 and S7-1200: LHTTP, LMQTT (entry 109780503)](<https://support.industry.siemens.com/cs/document/109780503/>) · [node-red-contrib-s7 (Node-RED library)](<https://flows.nodered.org/node/node-red-contrib-s7>) |
| **Eaton easyE4** | ➕ EASY-COM-RTU-M1 module | ✔ read-only server | ✔ generic broker from firmware 2.40 | — | M2 · M4 | [Eaton easyE4, firmware 2.30 release notes](<https://es-assets.eaton.com/AUTOMATION/DOWNLOAD/DOWNLOADCENTER/EASY/easyE-series/easyE4/ReleaseNotes/easyE4_FW_V230_MZ049013EN.pdf>) · [Eaton easyE4, firmware 2.40 release notes](<https://es-assets.eaton.com/AUTOMATION/DOWNLOAD/DOWNLOADCENTER/EASY/easyE-series/easyE4/ReleaseNotes/easyE4_FW_V240_MZ049013EN.pdf>) · [Eaton easyE4, product cybersecurity guideline (MZ049001EN)](<https://es-assets.eaton.com/DOCUMENTATION/AWB_MANUALS/MZ049001EN.pdf>) · [node-red-contrib-easye4-json (community package)](<https://flows.nodered.org/node/node-red-contrib-easye4-json>) |
| **Schneider M221** | ✔ serial line | ✔ only the TM221CE and TM221ME | — | — | M1 · M2 | [Schneider, the serial line of the M221](<https://www.se.com/us/en/faqs/FAQ000281640/>) · [Schneider, which M221 have Ethernet, and its protocols](<https://www.se.com/au/en/faqs/FA300797/>) · [Schneider, Modbus TCP connections of the M221](<https://www.se.com/us/en/faqs/FA307999>) |
| **Schneider Zelio** Both modules go on the SR3 B…BD relays (24 V DC). | ➕ SR3MBU01BD module | ➕ SR3NET01BD module, Modbus TCP server | — | — | M1 · M2 | [Schneider, Zelio Logic catalogue (January 2022)](<https://download.se.com/files?p_Doc_Ref=DIA3ED2111202EN&target=new>) · [Schneider, SR3NET01BD](<https://www.se.com/ar/es/product/SR3NET01BD/zelio-logic-mod-com-ethernet-p-srbd/>) |
| **Allen-Bradley Micro850** | ✔ serial port | ✔ server; up to 16 connections on the L50E | — | — | M2 | [Rockwell, Micro800 protocol support](<https://www.rockwellautomation.com/en-gb/docs/factorytalk-design-workbench/1-01-00/ftdw-help-ditamap/micro800-controller/micro800-instruction-set/messaging-instructions/communication-protocol-support.html>) |
| **Mitsubishi FX5U** | ✔ built-in RS-485, master or slave | ✔ server and client; firmware 1.060 or later | — | — | M2 | [Mitsubishi FX5U, MODBUS/TCP on the built-in Ethernet](<https://fa-faq.mitsubishielectric.com/faq/show/22302>) · [Mitsubishi, FX5 user manual for MODBUS communication (JY997D56101)](<https://dl.mitsubishielectric.com/dl/fa/document/manual/plcf/jy997d56101/jy997d56101h.pdf>) |
| **AutomationDirect CLICK PLUS** | ✔ C2-03CPU: RS-485. C2-01CPU: RS-232 only. C2-02CPU: no serial port | ✔ | ✔ publishes and subscribes | — | M2 · M4 | [AutomationDirect, CLICK PLUS user manual, chapter 4 (communications)](<https://cdn.automationdirect.com/static/manuals/c2userm/ch4.pdf>) · [AutomationDirect, CLICK PLUS CPUs, specifications](<https://cdn.automationdirect.com/static/specs/c20xcpu.pdf>) |
| **Unitronics UniStream** | ➕ the RS-485 of the Modular CPU, or a serial COM module | ✔ | ✔ | ✔ REST client, HTTP or HTTPS | M4 · M5 | [Unitronics UniStream, MODBUS](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/MODBUS.htm>) · [Unitronics UniStream, communication ports by series](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/Communications__COM_Ports_and_DataCom.htm>) · [Unitronics UniStream, MQTT](<https://www.unitronicsplc.com/Download/SoftwareHelp/%21UniLogicWebhelp2024/Communications/MQTT.htm>) · [Unitronics UniStream, REST API](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/REST_API.htm>) · [Unitronics UniLogic, release notes (REST)](<https://downloads.unitronicsplc.com/Sites/plc/Unilogic/UniLogic_Release_Notes.pdf>) |
| **Finder OPTA** | ✔ RS-485 versions | ✔ | ✔ with TLS, per an Arduino tutorial | ? the tutorial is an HTTP client; an HTTPS client is not in what we read | M4 · M5 | [Finder OPTA, HTTP requests](<https://opta.findernet.com/es/tutorial/http-client>) · [Finder OPTA, Modbus TCP](<https://opta.findernet.com/tutorial/modbus-tcp>) · [Finder OPTA, Modbus RTU over its RS-485 port](<https://opta.findernet.com/en/tutorial/serie7m-modbus-rtu>) · [Arduino, Opta to AWS IoT Core over MQTT (tutorial)](<https://docs.arduino.cc/tutorials/opta/getting-started-with-aws-iot-core>) |
| **WAGO Compact Controller 100** | ✔ | ✔ | ✔ | ✔ listed in the data sheet; sending from its Node-RED: untested | M3 | [WAGO Compact Controller 100 (751-9301), data sheet (copy hosted by a distributor)](<https://assets.cef.co.uk/downloads/pdg/wago_751-9301_datasheet/wago_751-9301_datasheet.pdf>) |
| **Weidmüller u-control UC20-WL2000-IOT** Done by us in the field, not a manufacturer statement: with the UR20-1COM module, a Modbus register map in the controller configuration ties the registers to tags, and the Node-RED of the controller uses those tags. From that Node-RED to Wertek AI: untested. | ➕ UR20-1COM-232-485-422 module, as Modbus RTU master | ✔ server | ✔ through Node-RED | ? through Node-RED; not in the documents linked | M3 | [Weidmüller UC20-WL2000-IOT, release notes](<https://assets.dam.weidmueller.com/assets/api/dc161464-10dc-4f56-8675-8c2e857f445e/Original/UC20-WL2000-IOT_Release-Notes_1334990000.pdf>) · [Weidmüller, Node-RED quick start guide](<https://assets.dam.weidmueller.com/assets/api/945525f8-95e0-46e1-9d2d-0edd7e991118/Original/QuickstartGuide_IOT_NODE_RED.pdf>) · [Weidmüller, MQTT from Node-RED](<https://assets.dam.weidmueller.com/assets/api/3a28b836-ea6d-450d-b47f-0879dc43b76d/Original/Temperature_Controller_with_MQTT_publisher_in_Node_RED.pdf>) |
<!-- /tabla:marcas -->

## Without a PLC: data-acquisition modules

The same five methods serve when there is no PLC, or when you do not want to touch the one that is there. The module reads the signal (4-20 mA, thermocouple, RTD, contact) and delivers it over one of the four protocols. It is the way to add a measurement to equipment that already works, without changing the existing control functions. (A 4-20 mA loop does not take another input “in parallel” without checking its load.)

✔ the manufacturer documents it · ➕ with the adapter named · ? unverified · — does not apply, or we did not find it in the documentation we read

<!-- tabla:modulos -->
| Module | Modbus RTU | Modbus TCP | MQTT | HTTPS | Natural method | Source |
| --- | --- | --- | --- | --- | --- | --- |
| **Brainchild IO (IO-8AII, IO-8TC, IO-6RTD, IO-16DI…)** | ✔ | ✔ “-E” versions (IO-8AIIS-E, IO-8TCS-E, IO-6RTD-E, IO-16DI-E) | — | — | M1 · M2 | [Brainchild, Modbus RTU I/O modules](<https://www.brainchildtw.com/shop/category/i-o-modules-modbus-i-o-modules-31>) · [Brainchild, Ethernet (Modbus TCP) I/O modules](<https://www.brainchildtw.com/shop/category/controllers-ethernet-modbus-i-o-modules-30>) |
| **Advantech ADAM-4000** | ✔ most models; some speak only ASCII: check the data sheet | — | — | — | M1 | [Advantech, RS-485 I/O modules (ADAM-4000/4100)](<https://www.advantech.com/en-eu/products/rs-485-i-o-modules-adam-4000-4100/sub_1-2mlkht>) · [Advantech ADAM-4050/4051/4052, data sheet](<https://advdownload.advantech.com.cn/productfile/PIS/ADAM-4050/file/ADAM-4050_4051_4052_DS(070523)20230712123034.pdf>) |
| **Advantech ADAM-6000** The versions with MQTT publish to a cloud without a gateway, per the data sheet. | — | ✔ | ✔ D version of the ADAM-6000, B version of the ADAM-6200; with TLS | ? RESTful API of the module; over HTTPS: not stated | M2 · M4 | [Advantech, Ethernet I/O modules (ADAM-6000, WISE-4000 LAN)](<https://www.advantech.com/en-eu/products/ethernet-i-o-modules-adam-6000-adam-6100-adam-6200-wise-4000-lan/sub_gf-5197>) · [Advantech ADAM-6000/6200/6300, data sheet](<https://advdownload.advantech.com/productfile/PIS/ADAM-6024/file/ADAM-60_62_63_DS(030926)20260310143942.pdf>) |
| **Advantech WISE-4000** For sites without cable. | — | ✔ | ✔ Wi-Fi model, per its data sheet; LAN model: unverified | ? RESTful API in JSON, and it can push to a server; over HTTPS: not stated | M4 | [Advantech, Ethernet I/O modules (ADAM-6000, WISE-4000 LAN)](<https://www.advantech.com/en-eu/products/ethernet-i-o-modules-adam-6000-adam-6100-adam-6200-wise-4000-lan/sub_gf-5197>) · [Advantech WISE-4050 (Wi-Fi), data sheet](<https://advdownload.advantech.com/productfile/PIS/WISE-4050/file/WISE-4050-B_DS(103024)20241030170231.pdf>) |
| **Moxa ioLogik E1200** Its active “push” works with Moxa's own MX-AOPC UA Server. | — | ✔ server | — | ? RESTful API of the module; over HTTPS: not stated | M2 | [Moxa ioLogik E1200, data sheet](<https://www.moxa.com/getmedia/7869edb4-38fb-4682-b809-909d1eb31e84/moxa-iologik-e1200-series-datasheet-v2.5.pdf>) |
| **Banner DXM700** Controller and gateway in one. | ✔ client or server | ✔ port 502 | ✔ per the comparison table | ✔ push to a web server; HTTPS per the data sheet | M4 · M5 | [Banner DXM700-B1/B2, data sheet (207893)](<https://info.bannerengineering.com/cs/groups/public/documents/literature/207893.pdf>) · [Banner DXM700-Bx, product manual (207894)](<https://info.bannerengineering.com/cs/groups/public/documents/literature/207894.pdf>) · [Banner, wireless controllers (comparison table)](<https://www.bannerengineering.com/us/en/products/wireless-sensor-networks/wireless-controllers.html>) |
| **Balluff BCM + CMTK (BAV002N)** IO-Link sensors; the CMTK is their gateway: four sensors, plus more through connected IO-Link masters. | — | — | ✔ the CMTK | ? the CMTK has a REST API; the brochure places “JSON and REST API” on the IO-Link master; over HTTPS: not stated | M4 | [Balluff, condition monitoring brochure](<https://assets.balluff.com/WebBinary1/LIT_BRO_CONDITION_MONITORING_EN_A23_DRW_956288_AA_000.pdf>) · [Balluff CMTK, user and developer documentation](<https://docs.balluff.com/cmtk/2.5.1/>) · [Balluff CMTK, overview of its REST endpoints](<https://docs.balluff.com/cmtk/2.5.1/dev_guide/api-documentation/01-overview/>) |
<!-- /tabla:modulos -->

IO-Link is not a fifth protocol: an IO-Link sensor goes out through its master, and what counts is what the master delivers (for example REST with JSON, MQTT, or a fieldbus such as EtherNet/IP or PROFINET; Modbus TCP only on some brands; per brand: unverified).

## Technical annex: what each method is made of

Each method combines two answers: over which protocol the data leaves, and where it is translated to IAES.

| Method | Acquisition protocol | Where it is translated |
| --- | --- | --- |
| M1 | Modbus RTU | A. Gateway (or B, with a USB to RS-485 adapter) |
| M2 | Modbus TCP, S7 or EtherNet/IP | B. Device with Node-RED in the panel |
| M3 | Whatever the controller's Node-RED reads | C. Inside the controller |
| M4 | MQTT | D. In the cloud |
| M5 | HTTPS | C. Inside the controller |

### The protocol (how the data leaves)

| Protocol | Physical interface | Who speaks it |
| --- | --- | --- |
| Modbus RTU | RS-485 | Most economical or older PLCs, and the serial acquisition modules. |
| Modbus TCP | Ethernet | Most PLCs with an Ethernet port. It is the common denominator. |
| The brand's own protocol | Ethernet | Siemens S7 (S7-1200, LOGO! 8) and EtherNet/IP (Allen-Bradley). They are not Modbus: they are read with their own Node-RED node. |
| MQTT | Ethernet or Wi-Fi | Newer PLCs and “IoT” modules that publish by themselves. |
| HTTPS | Ethernet | The few programmable devices with a web client. |

### The place (where it is translated to IAES)

| Place | What it is | What is added to the panel | Status |
| --- | --- | --- | --- |
| A. Gateway | A device that reads Modbus and reaches the internet (cellular or network). | The gateway | Untested |
| B. Device with Node-RED in the panel | An industrial PC or router that runs Node-RED with the IAES node. | That device | Node-RED → Wertek AI: tested; reading the PLC: not |
| C. Inside the controller itself | The PLC runs Node-RED, or its program builds the event. | Nothing | Untested |
| D. In the cloud | A flow in n8n or Node-RED receives the MQTT and translates it. | Nothing | n8n → Wertek AI: tested; PLC → MQTT: not |

### Which place serves which protocol

| Protocol | Possible places | Adapters and parts |
| --- | --- | --- |
| Modbus RTU | A, B | Gateway with RS-485 (Teltonika TRB145; the TRB140 has Ethernet and no RS-485), or a USB to RS-485 adapter with node-red-contrib-modbus. |
| Own protocol (S7, EtherNet/IP) | B | node-red-contrib-s7 for Siemens S7; node-red-contrib-cip-ethernet-ip for Allen-Bradley (Micro800: unverified). |
| Modbus TCP | A, B, C | node-red-contrib-modbus. If the CPU has no Ethernet, the manufacturer's module: DVPEN01-SL (Delta SS2), XBL-EMTA (LS), SR3NET01BD (Zelio). |
| MQTT | D | A broker and the translator flow. |
| HTTPS | C | Nothing: the equipment sends directly. |

## Next steps

- [The four steps to send the first reading](https://wertek.ai/integrators/): Free account, a designated point, an ingest key and one HTTP request.
- [What your customer gets, and the price](https://wertek.ai/integrators/iaes/): Trends, the app, maintenance, and the price per measurement point.
- [Your customer lends you their equipment](https://wertek.ai/engineering/industry-4-0/#lend): How provider access works: who grants it, what you see, when it ends.

## All the sources

- [Siemens, LOGO! communication](<https://www.siemens.com/es-mx/products/logo/communication/>)
- [Siemens, LOGO! system manual, edition 7/2022 (entry 109741041)](<https://support.industry.siemens.com/cs/document/109741041/>)
- [LOGO! 8.4, press note of a distributor (Mouser)](<https://www.mouser.pl/newsroom/publicrelations-siemens-logo-logic-modules-2024final>)
- [Siemens, press release on LOGO! 9](<https://press.siemens.com/global/en/node/7352>)
- [Siemens, LOGO! communication modules (LOGO! 9)](<https://www.siemens.com/en-gb/products/logo/communication/>)
- [Siemens, Modbus/TCP between two S7-1200 CPUs (entry 83130159)](<https://support.industry.siemens.com/cs/document/83130159/>)
- [Siemens, Modbus RTU on the S7-1200 (entry 47756141)](<https://support.industry.siemens.com/cs/document/47756141/>)
- [Siemens, the SIMATIC controller as an MQTT client (entry 109748872)](<https://support.industry.siemens.com/cs/document/109748872/>)
- [Siemens, communication libraries for S7-1500 and S7-1200: LHTTP, LMQTT (entry 109780503)](<https://support.industry.siemens.com/cs/document/109780503/>)
- [node-red-contrib-s7 (Node-RED library)](<https://flows.nodered.org/node/node-red-contrib-s7>)
- [node-red-contrib-cip-ethernet-ip (Node-RED library)](<https://flows.nodered.org/node/node-red-contrib-cip-ethernet-ip>)
- [S7 and EtherNet/IP nodes in Node-RED (article by FlowFuse)](<https://flowfuse.com/blog/2023/06/node-red-as-a-no-code-ethernet_ip-to-s7-protocol-converter>)
- [Eaton easyE4, firmware 2.30 release notes](<https://es-assets.eaton.com/AUTOMATION/DOWNLOAD/DOWNLOADCENTER/EASY/easyE-series/easyE4/ReleaseNotes/easyE4_FW_V230_MZ049013EN.pdf>)
- [Eaton easyE4, firmware 2.40 release notes](<https://es-assets.eaton.com/AUTOMATION/DOWNLOAD/DOWNLOADCENTER/EASY/easyE-series/easyE4/ReleaseNotes/easyE4_FW_V240_MZ049013EN.pdf>)
- [Eaton easyE4, product cybersecurity guideline (MZ049001EN)](<https://es-assets.eaton.com/DOCUMENTATION/AWB_MANUALS/MZ049001EN.pdf>)
- [node-red-contrib-easye4-json (community package)](<https://flows.nodered.org/node/node-red-contrib-easye4-json>)
- [Schneider, Modbus TCP connections of the M221](<https://www.se.com/us/en/faqs/FA307999>)
- [Schneider, the serial line of the M221](<https://www.se.com/us/en/faqs/FAQ000281640/>)
- [Schneider, which M221 have Ethernet, and its protocols](<https://www.se.com/au/en/faqs/FA300797/>)
- [Schneider, Zelio Logic catalogue (January 2022)](<https://download.se.com/files?p_Doc_Ref=DIA3ED2111202EN&target=new>)
- [Schneider, SR3NET01BD](<https://www.se.com/ar/es/product/SR3NET01BD/zelio-logic-mod-com-ethernet-p-srbd/>)
- [Rockwell, Micro800 protocol support](<https://www.rockwellautomation.com/en-gb/docs/factorytalk-design-workbench/1-01-00/ftdw-help-ditamap/micro800-controller/micro800-instruction-set/messaging-instructions/communication-protocol-support.html>)
- [Mitsubishi FX5U, MODBUS/TCP on the built-in Ethernet](<https://fa-faq.mitsubishielectric.com/faq/show/22302>)
- [Mitsubishi, FX5 user manual for MODBUS communication (JY997D56101)](<https://dl.mitsubishielectric.com/dl/fa/document/manual/plcf/jy997d56101/jy997d56101h.pdf>)
- [AutomationDirect, CLICK PLUS user manual, chapter 4 (communications)](<https://cdn.automationdirect.com/static/manuals/c2userm/ch4.pdf>)
- [AutomationDirect, CLICK PLUS CPUs, specifications](<https://cdn.automationdirect.com/static/specs/c20xcpu.pdf>)
- [Unitronics UniStream, MODBUS](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/MODBUS.htm>)
- [Unitronics UniStream, communication ports by series](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/Communications__COM_Ports_and_DataCom.htm>)
- [Unitronics UniStream, MQTT](<https://www.unitronicsplc.com/Download/SoftwareHelp/%21UniLogicWebhelp2024/Communications/MQTT.htm>)
- [Unitronics UniStream, REST API](<https://www.unitronicsplc.com/Download/SoftwareHelp/!UniLogicWebhelp2024/Communications/REST_API.htm>)
- [Unitronics UniLogic, release notes (REST)](<https://downloads.unitronicsplc.com/Sites/plc/Unilogic/UniLogic_Release_Notes.pdf>)
- [Finder OPTA, HTTP requests](<https://opta.findernet.com/es/tutorial/http-client>)
- [Finder OPTA, Modbus TCP](<https://opta.findernet.com/tutorial/modbus-tcp>)
- [Finder OPTA, Modbus RTU over its RS-485 port](<https://opta.findernet.com/en/tutorial/serie7m-modbus-rtu>)
- [Arduino, Opta to AWS IoT Core over MQTT (tutorial)](<https://docs.arduino.cc/tutorials/opta/getting-started-with-aws-iot-core>)
- [WAGO Compact Controller 100 (751-9301), data sheet (copy hosted by a distributor)](<https://assets.cef.co.uk/downloads/pdg/wago_751-9301_datasheet/wago_751-9301_datasheet.pdf>)
- [Weidmüller UC20-WL2000-IOT, release notes](<https://assets.dam.weidmueller.com/assets/api/dc161464-10dc-4f56-8675-8c2e857f445e/Original/UC20-WL2000-IOT_Release-Notes_1334990000.pdf>)
- [Weidmüller, Node-RED quick start guide](<https://assets.dam.weidmueller.com/assets/api/945525f8-95e0-46e1-9d2d-0edd7e991118/Original/QuickstartGuide_IOT_NODE_RED.pdf>)
- [Weidmüller, MQTT from Node-RED](<https://assets.dam.weidmueller.com/assets/api/3a28b836-ea6d-450d-b47f-0879dc43b76d/Original/Temperature_Controller_with_MQTT_publisher_in_Node_RED.pdf>)
- [Teltonika, TRB145 (the gateway with RS-485)](<https://wiki.teltonika-networks.com/view/TRB145>)
- [Teltonika, TRB145 Data to Server](<https://wiki.teltonika-networks.com/view/TRB145_Data_to_Server>)
- [Teltonika, gateway families (which model has RS-485 or Ethernet)](<https://wiki.teltonika-networks.com/view/Teltonika_Networks_Gateways_Families>)
- [LS Electric XGB Cnet I/F user manual (copy hosted by a distributor, AutomationDirect)](<https://cdn.automationdirect.com/static/manuals/lselectric/xblcx1ausermanual.pdf>)
- [LS Electric XBL-EMTA, cut sheet (distributor, AutomationDirect)](<https://cdn.automationdirect.com/static/specs/cutsheet/XBL-EMTA_cutsheet.pdf>)
- [LS Electric XGB series catalogue, 2022 (copy hosted by a distributor)](<https://shop.tech-con.ro/media/catalog/product/pdf/./XGB%20Series_Catalog_EN_202205.pdf>)
- [Kinco K2, user manual (copy hosted by a distributor)](<https://anaheimautomation.com/media/anaheim/files/manuals/plc/L011929_-_K204_PLC_User_Manual.pdf>)
- [Kinco K6, spec sheet (copy hosted by a distributor)](<https://anaheimautomation.com/media/anaheim/literature/manuals/plc/L011958%20-%20KNC-PLC-K6%20Series%20Spec%20Sheet.pdf>)
- [Delta DVP series catalogue (copy hosted by a distributor)](<https://www.dicomp.com.br/downloads/materiais_apoio/datasheet/DVP-1.pdf>)
- [Delta DVPEN01-SL manual (copy on a manuals site)](<https://www.manualsdir.com/manuals/78254/delta-dvpen01-sl.html?page=5>)
- [Delta AS series brochure (copy hosted by a distributor)](<https://www.dicomp.com.br/downloads/materiais_apoio/datasheet/25735-1.pdf>)
- [Advantech, Ethernet I/O modules (ADAM-6000, WISE-4000 LAN)](<https://www.advantech.com/en-eu/products/ethernet-i-o-modules-adam-6000-adam-6100-adam-6200-wise-4000-lan/sub_gf-5197>)
- [Advantech ADAM-6000/6200/6300, data sheet](<https://advdownload.advantech.com/productfile/PIS/ADAM-6024/file/ADAM-60_62_63_DS(030926)20260310143942.pdf>)
- [Advantech WISE-4050 (Wi-Fi), data sheet](<https://advdownload.advantech.com/productfile/PIS/WISE-4050/file/WISE-4050-B_DS(103024)20241030170231.pdf>)
- [Advantech, RS-485 I/O modules (ADAM-4000/4100)](<https://www.advantech.com/en-eu/products/rs-485-i-o-modules-adam-4000-4100/sub_1-2mlkht>)
- [Advantech ADAM-4050/4051/4052, data sheet](<https://advdownload.advantech.com.cn/productfile/PIS/ADAM-4050/file/ADAM-4050_4051_4052_DS(070523)20230712123034.pdf>)
- [Brainchild, Modbus RTU I/O modules](<https://www.brainchildtw.com/shop/category/i-o-modules-modbus-i-o-modules-31>)
- [Brainchild, Ethernet (Modbus TCP) I/O modules](<https://www.brainchildtw.com/shop/category/controllers-ethernet-modbus-i-o-modules-30>)
- [Moxa ioLogik E1200, data sheet](<https://www.moxa.com/getmedia/7869edb4-38fb-4682-b809-909d1eb31e84/moxa-iologik-e1200-series-datasheet-v2.5.pdf>)
- [Banner DXM700-B1/B2, data sheet (207893)](<https://info.bannerengineering.com/cs/groups/public/documents/literature/207893.pdf>)
- [Banner DXM700-Bx, product manual (207894)](<https://info.bannerengineering.com/cs/groups/public/documents/literature/207894.pdf>)
- [Banner, wireless controllers (comparison table)](<https://www.bannerengineering.com/us/en/products/wireless-sensor-networks/wireless-controllers.html>)
- [Balluff, condition monitoring brochure](<https://assets.balluff.com/WebBinary1/LIT_BRO_CONDITION_MONITORING_EN_A23_DRW_956288_AA_000.pdf>)
- [Balluff CMTK, user and developer documentation](<https://docs.balluff.com/cmtk/2.5.1/>)
- [Balluff CMTK, overview of its REST endpoints](<https://docs.balluff.com/cmtk/2.5.1/dev_guide/api-documentation/01-overview/>)
