Hi
I have noticed that with lg01_pkt_fwd application, the downlink packets are delayed so much in gateway. When they are sent by LoRa transceiver, the RX1 window of de LoRaWAN node is expired, so the frames are lost. The JOIN_ACCEPT frame should be delayed 5 seconds, and the Network Server fix the correct time: JOIN_REQUEST frame arrive timestamp plus 5 seconds. The normal downlink frames should be delayed 1 second. But all of them are delayed with an additional time and it is dependant on SF (Spread Factor).
With SF7 downlink frames have an additional delay of 100ms and with SF12 additional delay about 1 or 2 seconds. I have demostrated this by monitoring the DIO0 signal of RFM95W in Dragino OLG01-N with an osciloscope.
Is there any bug in the time management of downlink frames?
Thank you,
Guillermo
Hi, guys
I have noticed that as well. Another point is that the report status show on log read is wrong. PUSH DATA acknowledge field doesn't change even if an ACK is sent by the server.
Thanks, Notopoloko
Hi I have noticed that with lg01_pkt_fwd application, the downlink packets are delayed so much in gateway. When they are sent by LoRa transceiver, the RX1 window of de LoRaWAN node is expired, so the frames are lost. The JOIN_ACCEPT frame should be delayed 5 seconds, and the Network Server fix the correct time: JOIN_REQUEST frame arrive timestamp plus 5 seconds. The normal downlink frames should be delayed 1 second. But all of them are delayed with an additional time and it is dependant on SF (Spread Factor). With SF7 downlink frames have an additional delay of 100ms and with SF12 additional delay about 1 or 2 seconds. I have demostrated this by monitoring the DIO0 signal of RFM95W in Dragino OLG01-N with an osciloscope. Is there any bug in the time management of downlink frames? Thank you, Guillermo