Hello, I’m facing a problem with a RAK3172 WisBlock module. After a few days of operation, when the node is reset, the values that arrive at ChirpStack are all zeros. The only way to restore normal operation is to perform a ‘full erase’ and rewrite the firmware.
Note that fport is 0 and dr 2 when it happens to be displaying only 0 in chirpstack even with the firmware forcing sending on fport2, rewriting the firmware without doing the full erase it always remains 0. Only when I do the full erase and rewrite it does it work again. Has anyone encountered a similar problem or have any idea what might be causing this unexpected change to FPort 0 and the need for a ‘full erase’ to restore normal operation?
Messages sent on fPort 0 with a length of 0 happens when your payload is too large for the datarate.
Choose a higher datarate.
If your payload size can change between packets, choose a datarate for your largest payload and disable ADR.
In my personal experience, ADR can mess up things when payload sizes are changing for packets sent out. I experienced ADR forcing a change to a lower datarate based on small packets, and when a larger packet has to be sent, it didn’t fit into the allowed payload size anymore.
Another question, are you using RUI3 AT command firmware or a custom firmware based on RUI3 API?
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.