UniCT-ARSLab/LWN-Simulator

Timestamp

Opened this issue · 4 comments

guy426 commented

Time of messages is always year 1980..

Can you give more details about the environment? to reproduce the situation

guy426 commented

My network server is Chirpstack
This is an example of decoded packet:
{"tst":"2023-09-27T10:57:15.161510+0200","topic":"application/9e548d1d-37cb-43fc-8231-25bfe45508f3/device/685b00ff4c1f9511/event/up","qos":0,"retain":0,"payloadlen":1436,"payload":{"deduplicationId":"a7fed1c4-6243-44af-9310-f3f4e3e3eb00","time":"1980-01-21T23:17:20.234+00:00","deviceInfo":{"tenantId":"52f14cd4-c6f1-4fbd-8f87-4025e1d49242","tenantName":"ChirpStack","applicationId":"9e548d1d-37cb-43fc-8231-25bfe45508f3","applicationName":"counter","deviceProfileId":"408f84b7-f359-4995-8fb7-1a70f0f12f85","deviceProfileName":"device_profile","deviceName":"dev3","devEui":"685b00ff4c1f9511","deviceClassEnabled":"CLASS_A","tags":{}},"devAddr":"010da236","adr":true,"dr":0,"fCnt":183,"fPort":1,"confirmed":false,"data":"dGVzdDMgMjAgc2Vjb25kaQ==","object":{"cmd":"test3 20 secondi"},"rxInfo":[{"gatewayId":"285bd82c7d76e7e1","uplinkId":50925,"time":"2023-09-27T08:57:14+00:00","timeSinceGpsEpoch":"1379840.234s","rssi":-60,"snr":7,"channel":1,"location":{"latitude":43.735555660125584,"longitude":10.95216751098633,"source":"GPS"},"context":"ZRPuag==","metadata":{"region_config_id":"eu868","region_common_name":"EU868"},"crcStatus":"CRC_OK"},{"gatewayId":"4645c2a5de7dfb99","uplinkId":58674,"time":"2023-09-27T08:57:14+00:00","timeSinceGpsEpoch":"1379840.234s","rssi":-60,"snr":7,"channel":1,"location":{"latitude":43.724019581115016,"longitude":10.949935913085939,"source":"GPS"},"context":"ZRPuag==","metadata":{"region_config_id":"eu868","region_common_name":"EU868"},"crcStatus":"CRC_OK"}],"txInfo":{"frequency":868300000,"modulation":{"lora":{"bandwidth":125000,"spreadingFactor":12,"codeRate":"CR_4_5"}}}}}

ok the problem could be the forwarder because the new protocol requires a valid GPS to bring the timestamp, I will investigate on this

I can confirm this issue.
The field timeSinceGpsEpoch contains a bad value, not corresponding to the time field