Set up · How-to
Industrial I/O modules
Connect PLC and I/O modules directly or behind a gateway, and use their readings in rules.
Updated 11 Nov 20261 min read
All ThingsX IoT Core pages
- What ThingsX IoT Core does
- Quick start: connect your first device
- Key concepts
- Security and access
- Connect Wi-Fi and IoT devices
- BLE gateways, shelf labels and child devices
- LoRaWAN sensors and gateways
- Industrial I/O modules
- Device twins and state
- Send commands to devices
- Rules: react to device messages
- SDK and REST API
- Monitor your fleet and support customers
- Moving from another IoT platform
- From AWS IoT Core
- From Azure IoT Hub and other platforms
- Device can't connect
- Devices keep disconnecting or reconnecting
- Data isn't arriving or a rule doesn't fire
- Frequently asked questions
- Topics and limits reference
Industrial I/O (IIO) modules behave like other devices:
- Directly connected modules (with their own network connection) are like Wi-Fi devices: they get a certificate or password, publish telemetry and receive commands. See Connect Wi-Fi and IoT devices.
- Modules behind a gateway (for example on a fieldbus the gateway reads) are child devices with the gateway as their parent, like shelf labels. See BLE gateways and child devices.
Good practice
- Send counters as running totals (
door_cycles: 1281) rather than increments, so a lost message doesn't skew your numbers. - Put the site and asset in attributes (
site: DC-PUNE,dock: 3) so the Things list and rules can filter on them. - Use events for alarms (
{"type": "motor_overcurrent"}) and rules to route them to your maintenance system.
Was this page helpful?
Can't find what you need? Contact support or read about ThingsX IoT Core.