3.2: Sscom
Features a timer to automatically send data at set intervals, which is useful for stress-testing device stability. Multi-Port Monitoring:
Users can define up to of custom commands. These are often stored in a side panel for quick-click sending, which is essential for repetitive tasks like: Sending AT commands to cellular or GPS modules. Triggering specific Modbus RTU registers. Simulating sensor data or heartbeat signals. 2. Checksum Automation sscom 3.2
The "3.2" version reached popularity because of several productivity-focused "EXT" (Extended) features: 1. Extended Commands (EXT) Features a timer to automatically send data at
If you are working with Modbus or raw binary, check the "Hex" box for both sending and receiving. 💡 Common Use Cases Triggering specific Modbus RTU registers
| Problem | Likely Cause | Solution | | :--- | :--- | :--- | | "Port open failed" | Port in use or driver issue | Close Arduino IDE/Cura. Reinstall CH340/FTDI driver. | | Garbage characters in window | Baud rate mismatch or incorrect data bits | Double-check device datasheet. Try 9600/8/N/1 then 115200. | | No data received | Wrong TX/RX wiring | Swap TX and RX lines on your adapter. Ensure common ground. | | SSCOM freezes on send | Flow control enabled accidentally | Set Flow Control to "None". | | Unable to send large files | Buffer overrun | Reduce "Send Interval (ms)" to 10-20ms or use hardware flow control. |
