LoRaWAN Nano-Gateway
-
Has anyone been able to get the nano-gateway working with a LoPy4 and The Things Network? I want to verify that it's possible -- I'm losing faith the more I try and read posts on this forum.
-
@cooper Hi, do you remember which firmware version did you use?, I am having issues with downlinks that I did not have before (too many looses), thanks
-
@cooper Yes, the ticks_... call has been changed. You have to use a script which uses ticks_cpu() instead of ticks_us().
-
@robert-hh it was the nano-gateway script
-
@cooper Just for interest: which code change are you tal
king about, the firmware or the nano-gateway script?
-
@robert-hh I finally got it working. The latest code changes from the development team seamed to help. Thank you for your help, you're a saint -- your messages on many posts helped me a lot.
Btw I'm in the US (to answer your question)
-
This post is deleted!
-
@cooper Yes, it's possible. It works best if you use ABP. Using OTAA works not well, because the LoPy4 with the Nano-Gateway script does not meet the timing requirements of LORaWan. It simply cannot send the downlink messages at the right time. Using a slower data rate would relax the timing requirements. So try to use SF12BW125 for the first tests. This has to be changed in the scripts of both the gateway and the nodes. Beware, that for the gateway the setting SFxBWy is used, for the Node it's the Data rate. Example:
# for EU868 LORA_FREQUENCY = 868100000 LORA_GW_DR = "SF12BW125" # DR_0 LORA_NODE_DR = 0I have made a version which tries to compensate for the timing lag, but with LoPy4 this also does not work at SF7BW125.
The version is here: https://github.com/robert-hh/pycom-libraries/tree/nanogateway/examples/lorawan-nano-gateway
b.t.w.: In which region are you located?
