Hi everyone,
I’ve been building a desktop tool called ModScan Community for working with Modbus RTU/TCP devices, and I wanted to share it here to get feedback from people who deal with real-world setups.
It’s released as open-source under AGPLv3.
The idea came from frustration when debugging Modbus systems in the field — often switching between tools just to scan devices, read/write registers, and monitor behavior.
Current capabilities:
- Modbus RTU and Modbus TCP
- Slave ID / device scanning
- Read (FC01 / FC02 / FC03 / FC04)
- Write (FC05 / FC06 / FC15 / FC16)
- Sequential polling (to avoid RS485 collisions)
- CSV export for logs/data
- Topology / graph view
- Project save/load
- Cross-platform desktop (Windows / macOS / Linux)
I’m trying to make something that fits actual field workflows better — especially for PLC, RS485, and industrial IoT setups.
I’d really appreciate feedback from anyone working with:
- PLCs
- ESP32 + RS485
- Energy meters
- Sensor gateways
- Industrial commissioning / troubleshooting
A few things I’m specifically unsure about:
- Does this workflow align with how you debug Modbus devices?
- What features are missing for real-world usage?
- What edge cases tend to break tools like this?
- What safety measures should exist before allowing write operations?
If anyone’s interested, I can share the repo in the comments.
Any feedback is appreciated — especially critical ones.