AppEUI == 0 definitely doesn't work (resolved: gateway bug) #760
Replies: 2 comments 1 reply
-
This is very curious. I connected a device to a RWC 5020B and confirmed that the compliance sketch with AppEUI == 0 works fine. (Also checked the uplink messages captured by the 5020B using @tanupoo's lorawan-parser, and everything was fine. So this is not an LMIC problem per se. Discussion continues at forum.mcci.io. |
Beta Was this translation helpful? Give feedback.
-
I tracked this down to a fault in the packet forwarder used on many of our MultiTech gateways. So it really didn't work, but it had nothing to do with the LMIC. Using MultiTech + basic station works; or using other gateways works. |
Beta Was this translation helpful? Give feedback.
-
I'm embarrassed to say that AppEUI == 0 causes Join requests to be silently skipped. The LMIC goes through all the motions (including
EV_TXSTART
) but the gateways don't see the uplinks. Using AppEUI == 1 (for example) works fine, all other things being equal.EV_TXSTART
is particularly odd, because that means it should have called the radio driver, and indeed we received a complete answer. It seems likely that the message is corrupted in some way.This is high prio to fix. For now, please use AppEUI == 1 with TTN V3.
Repro case was using Arduino LoRaWAN library but I think this is an LMIC problem.
Beta Was this translation helpful? Give feedback.
All reactions