Modu AI

Use cases

Which Modbus/AT industrial device use cases does Modu AI support?

Learn how Modu AI helps configure, diagnose, and trace Modbus RTU and AT-command workflows for serial gateways, IO modules, LoRa modules, and DTU/RTU devices.

Modu AI maps natural-language goals to confirmed serial, Modbus, or AT tool calls. Common tasks include reading status, changing addresses, adjusting serial settings, querying network state, and setting LoRa parameters.

Key facts

Typical devices
Serial gateways, IO modules, LoRa modules, and DTU/RTU devices
Typical reads
Coils, discrete inputs, holding registers, input registers, device IDs, and signal strength
Typical writes
Modbus slave address, coil state, register values, baud rate, LoRa channel, and keys
Safety model
Parameter checks, write confirmation, TX/RX frame records, and traces

IO module status reads and writes

For DI, DO, AI, and AO modules, Modu AI can use function codes, register addresses, and parameter boundaries from the manual to turn goals such as reading input status or turning on an output channel into Modbus tool calls. Write actions go through confirmation.

  • Read DI or DO status.
  • Read AI input registers.
  • Write one coil or multiple coils.
  • Write holding registers and keep response frames.

Serial settings and slave address configuration

Common deployment tasks include changing a Modbus slave address, baud rate, parity, or serial format. Modu AI checks the allowed range from the document before producing the intended action, reducing accidental writes.

AT commands and LoRa parameter setup

For AT-command devices, Modu AI can extract query commands, set commands, response formats, and parameter enums from manuals. This helps with device ID queries, signal-strength checks, network-registration checks, and LoRa channel, speed, address, or key configuration.

Frequently asked questions

Can it write registers directly?

Yes, but sensitive writes require confirmation by default. The action is shown before execution, and the low-level command is sent only after confirmation.

Does it support Modbus TCP?

The current focus is serial workflows and Modbus RTU. The site copy and tool chain are centered on serial connections, RTU frames, and AT-command devices.

What if document parsing fails?

Use a clearer PDF, image, or text source, or retry in Documents. The goal is to extract capabilities from evidence instead of guessing parameters.