Modbus RTU (RS-485) Meets AI: How to Connect Industrial Devices to ASI Biont Without Coding

Why Integrate Modbus RTU (RS-485) with an AI Agent?

Modbus RTU over RS-485 is the backbone of industrial automation — used in PLCs, VFDs, sensors, and actuators. However, extracting data or controlling these devices traditionally requires programming (Python, C#) and dedicated SCADA systems. ASI Biont eliminates that barrier: you simply describe your Modbus device in a chat, and the AI agent writes the integration code on the fly. This means engineers, technologists, and even plant managers can set up real-time monitoring, predictive alerts, and remote control without writing a single line of code manually.

How ASI Biont Connects to Modbus RTU Devices

ASI Biont supports Modbus RTU (RS-485) through the Hardware Bridge — a lightweight Python script (bridge.py) that runs on your local Windows/Linux/macOS machine. The bridge connects to ASI Biont’s cloud via WebSocket (the only communication channel). When you ask the AI to read a register, it uses the industrial_command tool with protocol='serial' and command='serial_write_and_read'. The bridge then sends the Modbus RTU frame (hex string) to the COM port via pyserial and returns the response.

Key parameters you must provide:
- COM port (e.g., COM3 on Windows, /dev/ttyUSB0 on Linux)
- Baud rate (9600 is common for Modbus RTU)
- Modbus slave ID (1–247)
- Register address and function code (03 – read holding registers, 06 – write single register)

Real-World Use Case: Monitoring Temperature on a Production Line

Imagine a Modbus RTU temperature transmitter (e.g., with a PT100 sensor) connected to an RS-485 USB converter. You want the AI to:
1. Read the temperature every 10 minutes
2. Log it to a CSV file
3. Send a Telegram alert if the temperature exceeds 85°C

Step 1: Set Up the Hardware Bridge

1. Download bridge.py from the ASI Biont dashboard (Devices → Create API Key → Download bridge).
2. Install dependencies: pip install pyserial requests websockets
3. Run: python bridge.py --token=YOUR_API_KEY --ports=COM3 --baud 9600

Step 2: Ask the AI in Chat

User: "Connect to Modbus RTU device on COM3, baud 9600, slave ID 1. Read holding register 0 (temperature) every 10 minutes. If value > 850 (tenths of °C, so 85.0°C), send a Telegram alert to my bot with chat ID 123456789. Log all readings to temperature_log.csv."

Step 3: AI Generates the Integration Code (executed in sandbox)

import paho.mqtt.client as mqtt
import csv
import time
from datetime import datetime

# Configuration
TELEGRAM_BOT_TOKEN = "YOUR_BOT_TOKEN"
TELEGRAM_CHAT_ID = "123456789"

# Function to read Modbus register via bridge
def read_temperature():
    # This is a placeholder — actual command sent via industrial_command
    # AI will use the 'serial_write_and_read' command with the Modbus RTU frame
    pass

# Main loop (simplified for 30-second sandbox timeout)
# In reality, AI would set up a scheduled task
print("Temperature monitoring started. AI will check every 10 minutes.")

Note: The AI doesn't run infinite loops; it sets up a cron-like trigger on the server that calls the industrial_command periodically.

Step 4: AI Executes the Command

The AI sends the following to the bridge:

industrial_command(
    protocol='serial',
    command='serial_write_and_read',
    params={
        'port': 'COM3',
        'baudrate': 9600,
        'data': '010300000001840a'  # Modbus RTU frame: slave 1, function 03, start addr 0, length 1, CRC
    }
)

Bridge replies with the raw bytes (e.g., 0103020D4FB9A3). AI decodes the temperature: 0x0D4F = 3407 / 10 = 34.1°C.

Why This Matters: No Coding, No SCADA

Traditional Modbus integration requires:
- A programming language (Python, C#)
- Libraries like pymodbus or libmodbus
- A scheduler or background service
- Telegram API integration

With ASI Biont, the AI does all of this in seconds. You just describe your device and goal. The agent handles Modbus frame construction, CRC calculation, error handling, and data logging.

Other Scenarios You Can Automate

Potential Pitfalls to Avoid

• Wrong baud rate or parity: Modbus RTU defaults to 9600, 8, N, 1. Verify with your device manual.
• Slave ID mismatch: Ensure the slave ID in the Modbus frame matches the device.
• Cable length: RS-485 max distance is ~1200 meters; use proper termination resistors (120 Ω) for long runs.
• CRC errors: The AI calculates CRC-16 (Modbus) automatically, but if your device uses a variant (e.g., PLC), specify it in the chat.
• Bus contention: Only one master (your bridge) should be on the RS-485 bus. Disconnect other masters during testing.

Conclusion

Connecting Modbus RTU (RS-485) devices to an AI agent like ASI Biont transforms industrial data into actionable insights — without traditional programming. Whether you're monitoring motor temperatures, controlling pumps, or logging energy consumption, the AI handles the complexity. You just describe what you need, and it writes the integration code on the spot.

Ready to try it? Head over to asibiont.com and connect your Modbus device today — no coding required.