I never get 0 even with no gate, anyone else see this. I’m in ABP mode.
OK
AT+NJS=1
OK
OK
I never get 0 even with no gate, anyone else see this. I’m in ABP mode.
OK
AT+NJS=1
OK
OK
Welcome to RAK forum @CForster , NJS has no meaning on ABP. There is no join procedure for ABP. NJS on my module also returns 1 each time I configure it to ABP. NJS only take effect on OTAA.
Thanks for the clarification. That matches what I suspected about NJS on ABP. One more point I want to be clear on: when using ABP, other than seeing EV_TXDONE, is there a way to actually confirm that a packet has been received by a gateway? My understanding is that EV_TXDONE just means the radio has transmitted, not that it was heard. In practice, would the only confirmation be receiving a downlink or checking the network server logs?
For context, the node was previously sending and receiving with the TTN server, but then it suddenly stopped.
Hi @CForster ,
The only way to have confirmation if the packet is received is using confirmed uplink.
EV_TXDONE is only there to indicate that the uplink transmission is already done. It indicates that RX1/RX2 delays are finished.
LoRaWAN, by design, is not for use cases that requires confirmed uplinks. This is not healthy for the network overall because confirmed uplinks requires downlinks from GW which uses its RF channel.
Unless if your nodes has long uplink interval like hours. You can probably use confirmed uplinks all the time. If not, the ideal approach is monitor your device connection using confirmed uplinks occasionally or using linkcheck ones in a while.