Getting Badgerboard to work with TTN

End Devices (Nodes)
18

Sorry, I am not really using them.

I still had one running that I also used for this topic, so: not using any of the Badgerboard libraries. Looking into that device now:

  • It had somehow downgraded to SF12 (might be a TTN ADR issue?). Cycling its power made it go back to SF7.

    (My code was sending 8 bytes plus a 13 bytes LoRaWAN header, and used delay(5000) in the loop. On SF12, with a total 1483 ms airtime, it was only possible to transmit every 1190 seconds, almost 20 minutes. For SF7 with 57 ms airtime, transmitting was only possible every 49 seconds. These delays were caused by disabling 7 of the 8 default channels. This rightfully caused no_free_ch due to the very low maximum duty cycle of 0.125% for single channel nodes.)

  • Like mentioned above, when running on a mains adapter, the reported voltage level is always the exact same value (3.283 for this very board, and 3.325 for another one I tested earlier).

  • The temperature reading this one board gives is about 7 degrees Celcius too high at room temperature. (If not due to it being an onboard sensor, then maybe due to using different libraries; I did not compare to another Badgerboard.)

  • It does not work on battery packs that have some smart power management, as it draws too little current, making my battery packs switch off automatically :slight_smile:

Also, shame on me for not switching it off after I was done testing…

1 Like