Hi everyone,
I am currently troubleshooting a remote setup using a Dragino RS485-LN connected to an ABB Energy Meter via Modbus RTU. The LoRaWAN connection itself is rock solid (great SNR and RSSI), but I keep getting constant Modbus timeouts (empty payloads in the uplink).
Here is what is currently working and configured:
Downlinks reach the device perfectly.
- I successfully configured the UART settings via TTN downlinks to match the ABB factory defaults: 19200 Baud, Even Parity, 1 Stop Bit.
- The Dragino acknowledges these settings by replying with “01” on FPort 2, so they are definitely saved in the flash memory.
- To speed up debugging, I temporarily changed the uplink interval to 60 seconds (“01 00 00 3C”), which also works flawlessly.
The Problem:
When I send a Modbus read command (for example: A8 01 06 01 03 50 00 00 04 FF for the total energy register), the Dragino schedules it, polls the meter, but the resulting uplink response has a completely empty payload (0 bytes). The meter is completely silent.
What I have already tried remotely:
- Function Codes: Tested both 03 (Read Holding) and 04 (Read Input). Both return empty.
- Slave IDs: Tested polling IDs 01, 02, and 03 on the off chance it was changed during installation. All return empty.
- Different Registers: Tested polling live voltage (Register 5B 00) instead of total energy (Register 50 00) to rule out the ABB “MidLock” feature (which blocks energy registers until a consumption of 1 kWh is reached). Still empty.
Crucial Limitation:
I currently have no physical access to the cabinet. I cannot attach a USB-RS485 sniffer right now, and I cannot physically swap the A/B data wires. I had the same problem for another device and it did not help swapping A/B.
Are there any specific Dragino configuration quirks, timing parameters, or ABB-specific Modbus settings that I might be overlooking from the remote side? Any suggestions on what else to look for in the TTN data stream would be highly appreciated.
Thanks in advance for any hints!