> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/guides/machine-connectivity/plcs-industrial-controllers.md).

# PLCs & Industrial Controllers

Guides for connecting PLCs and industrial controllers such as Siemens SIMATIC S7, Allen-Bradley ControlLogix, and Beckhoff TwinCAT.

These guides describe how to read data from programmable logic controllers (PLCs) and industrial controllers and map it into an ISA-95 style MQTT topic hierarchy. The following guides are available:

| Guide                                                                                                                                                   | Connector                                                                 | Description                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| [Siemens S7 Device](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-and-integrating-a-siemens-s7-device.md)                   | [S7](/2-6-1/connectors/shop-floor-connectors/siemens-simatic-s7.md)       | Integrate SIMATIC S7 PLCs for industrial data exchange.                    |
| [SIMATIC S7-1500 via S7+](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-a-simatic-s7-1500-via-s7-plus.md)                   | [S7+](/2-6-1/connectors/shop-floor-connectors/siemens-simatic-s7-plus.md) | Read data with symbolic addressing, including optimized data blocks.       |
| [Allen-Bradley ControlLogix PLC](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-an-allen-bradley-controllogix-plc.md)        | [EtherNet/IP](/2-6-1/connectors/shop-floor-connectors/ethernet-ip.md)     | Read controller and program tags from a ControlLogix PLC.                  |
| [Schneider Modicon M580 PLC](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-a-schneider-modicon-m580-plc.md)                 | [Modbus/TCP](/2-6-1/connectors/shop-floor-connectors/modbus-tcp.md)       | Read located variables from a Modicon M580 PLC.                            |
| [WAGO PFC200 Controller](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-a-wago-pfc200-controller.md)                         | [Modbus/TCP](/2-6-1/connectors/shop-floor-connectors/modbus-tcp.md)       | Map PLC variables to Modbus registers in CODESYS and read them.            |
| [Phoenix Contact PLCnext Controller](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-a-phoenix-contact-plcnext-controller.md) | [OPC UA](/2-6-1/connectors/shop-floor-connectors/opc-ua/opc-ua-client.md) | Read data through the built-in OPC UA server of the controller.            |
| [Beckhoff TwinCAT System](/2-6-1/guides/machine-connectivity/plcs-industrial-controllers/connecting-a-beckhoff-twincat-system.md)                       | [OPC UA](/2-6-1/connectors/shop-floor-connectors/opc-ua/opc-ua-client.md) | Read data from a TwinCAT 3 PLC through the TwinCAT OPC UA Server (TF6100). |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/guides/machine-connectivity/plcs-industrial-controllers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.