What is the role of timestamp in downlink from server side and node Side both? Because My LoRa Mote does not contain any RTC (Real-time-clock) Hence we have removed all the rtc functionalities in our LoRa Mote. Is the RTC the reason for not receiving the downlink??..
Well, you need to know at what time the gateway must transmit the frame So when the gateway receives a frame it will give the network-server the timestamp when it was received. The network-server will add 1 second to that when emitting a downlink (given that the receive window is after 1 second).
See also: https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT#L135
So, to deal with the network latency issue during downlink between the gateway (has GPRS connection) and the network-server, is there another way other than purchasing a gateway running network-server on itself?
Any way of using gateway bridge for this purpose, any ideas?
How much latency do you see over the GPRS connection?
@bconway Thank you for your promt reply. Please find the screenshots from different gateways’ ping durations. For instance, one of them has 902 ms. on average.
Wish you a Merry Christmas and a happy, healthy and successful new year.
Yeah, that’s rough. The two most common options are to run a full stack locally and forward your data upstream in a less latency-sensitive fashion, or to the run the stack upstream of the gateway and adjust RX1 and RX2 windows on each device to work with the extended latency.