time field empty when no GPS present
Closed this issue · 2 comments
Looking at the PROTOCOL
Lines 133 to 135 in d0226ea
And then at the code
packet_forwarder/lora_pkt_fwd/src/lora_pkt_fwd.c
Lines 1609 to 1637 in d0226ea
time
should contain an ISO time, irrelevant if the gateway is GPS synced or not. Maybe it's NTP synced, and the should be good enough to indicate at what time a packet was received.
tmms
should contain the GPS timestamp in case a GPS is present.
tmst
contains the concentrator clock counter value used to schedule downlinks accurately.
My opinion is that this line
packet_forwarder/lora_pkt_fwd/src/lora_pkt_fwd.c
Line 1613 in d0226ea
should be removed.
I was expecting to see the time field being added when fake_gps
is enabled, but that does not seem to work.
Fake GPS off (metadata from TTN):
{
"gtw_id":"eui-60c5a8fffeXXXXXX",
"timestamp":11257844,
"time":"",
"channel":5,
"rssi":-38,
"snr":9.5,
"rf_chain":0
}
Fake GPS on:
{
"gtw_id":"eui-60c5a8fffeXXXXXX",
"timestamp":600364156,
"time":"",
"channel":5,
"rssi":-38,
"snr":9,
"rf_chain":0,
"latitude":"<REDACTED>",
"longitude":"<REDACTED>",
"altitude":190
}
Thank you for your inquiry.
Customers are encouraged to submit technical questions via our dedicated support portal at https://semtech.force.com/ldp/ldp_support.
We invite all users to visit the LoRa Developer Portal Forum at https://forum.lora-developers.semtech.com and to join the thriving LoRa development community!