Modbus Integration
Function path: SVE navigation bar → Result Integration → Modbus
Overview
The smart camera acts as a Modbus Master, writing AI inference results via TCP to the Coils or Holding Registers of the remote Modbus Slave. Suitable for interfacing with PLCs / gateways / HMIs — transmits only signal-level results (OK/NG status words), not images.
Integration Requirements
| Item | Requirement |
|---|---|
| Communication Mode | TCP (camera as Master); RTU requires serial slave support on the remote end |
| Slave Device | Modbus Slave accessible by the camera (PLC / gateway / slave simulator), with corresponding data areas enabled |
| IP Address | Slave IP (camera-reachable) |
| Port | Slave listening port (default 502, per actual slave configuration) |
| Slave ID | Slave station number (range 1~247) |
| Data Area | Coil / Holding Register, select based on what the slave supports |
| Address | Data area start address (range 0~65535, per actual slave) |
| Write Value | Coil: ON (0xFF00) / OFF (0x0000); Register: 0~65535 numeric value |
| Trigger Condition | Result is OK / Result is NG / Any result |
Basic Configuration on SVE
- Navigate to Result Integration → Modbus;
- Turn on the Modbus Integration switch;
- Fill in/select parameters:
| Parameter | Description |
|---|---|
| Communication Mode | TCP (default) / RTU |
| IP Address | Slave IP (required for TCP mode) |
| Port | Slave listening port (default 502, per actual slave) |
| Slave ID | Slave station number (1~247, default 1) |
| Data Area | Coil / Holding Register |
| Address | Data area address (0~65535, default 0) |
| Write Value | Coil: ON (0xFF00) / OFF (0x0000); Register: numeric value |
| Trigger Rule → Trigger Condition | Result is OK (default) / Result is NG / Any result |
- Click Save.
Note: The "Port", "Slave ID", and "Address" on SVE are parameters for writing to the remote slave and must match the actual slave configuration.
Basic Verification
Page Testing (Test Send)
After configuration, click Test Send and observe the "Debug Request" area on the right: a success response indicates the link is normal (successfully wrote to the slave's corresponding address).
Real Task Verification
- Trigger an AI inference that meets the trigger condition (e.g., result is NG);
- Check the slave's data area: use a slave debug tool / slave simulator (Comms panel) to read the configured address — value == camera's configured write value → Integration successful.
Common Issues
| Symptom | Troubleshooting |
|---|---|
| Camera connection failed/no response | Check if slave is started and listening on the configured port; IP/port/Slave ID matches the slave |
| Expected value not written | Trigger condition met (OK/NG/any result); write value matches slave data area format (Coil/Register) |
| Slave does not support this data area | Confirm slave has the corresponding Coil/Register data area enabled |
| RTU connection failed | Check serial port parameters (baud rate/parity/station number) match the remote slave |