> 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-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices.md).

# Robots, Sensors & Shop Floor Devices

These guides describe how to read data from robots, sensors, power meters, and other shop floor devices and map it into an ISA-95 style MQTT topic hierarchy. The following guides are available:

| Guide                                                                                                                                                           | Connector                                                                           | Description                                                                  |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [Universal Robots Cobot](/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices/connecting-a-universal-robots-cobot.md)                           | [Modbus/TCP](/2-4-2/connectors/shop-floor-connectors/modbus-tcp.md)                 | Read robot mode, safety status, joint angles, and TCP position from a cobot. |
| [SICK RFID Sensor via SOPAS](/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices/connecting-and-integrating-a-sick-rfid-sensor-via-sopas.md)   | [SOPAS](/2-4-2/connectors/shop-floor-connectors/sopas.md)                           | Connect a SICK RFID sensor via the SOPAS protocol.                           |
| [ifm IO-Link Master](/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices/connecting-an-ifm-io-link-master.md)                                  | [HTTP/REST](/2-4-2/connectors/enterprise-connectors/http-rest.md)                   | Read IO-Link sensor data through the ifm IoT Core HTTP interface.            |
| [Siemens SENTRON PAC3200 Power Meter](/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices/connecting-a-siemens-sentron-pac3200-power-meter.md) | [Modbus/TCP](/2-4-2/connectors/shop-floor-connectors/modbus-tcp.md)                 | Read voltage, power, and energy measurements from a power meter.             |
| [Janitza UMG Power Analyzer](/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices/connecting-a-janitza-umg-power-analyzer.md)                   | [Modbus/TCP](/2-4-2/connectors/shop-floor-connectors/modbus-tcp.md)                 | Read power quality and energy measurements from a power analyzer.            |
| [WERMA Signal Towers](/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices/connecting-werma-signal-towers.md)                                   | [Werma WIN Ethernet](/2-4-2/connectors/shop-floor-connectors/werma-win-ethernet.md) | Read machine states from WERMA signal towers.                                |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybus.io/2-4-2/guides/machine-connectivity/robots-sensors-shop-floor-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.