DLOS8 Timestamp issue

Gateways Dragino Gateways
1

I installed my own gateway (a DLOS8) because the public one I used before was not always reachable. I then discovered that the gateway timestamp info returned in packets from end devices is wrong.
See below " “time”: “1980-01-06T00:00:50.543Z”,"
Any hint?

 "received_at": "2022-02-04T21:08:18.527118528Z",
    "uplink_message": {
      "session_key_id": "AX7F/1d5vUJHG+NEaPGDNQ==",
      "f_port": 2,
      "f_cnt": 53,
      "frm_payload": "y6kIhgF3AQhNf/8=",
      "decoded_payload": {
        "BatV": 2.985,
        "Bat_status": 3,
        "Ext_sensor": "Temperature Sensor",
        "Hum_SHT": 37.5,
        "TempC_DS": 21.25,
        "TempC_SHT": 21.82
      },
      "rx_metadata": [
        {
          "gateway_ids": {
            "gateway_id": "hb9iiu-jn36kl-73",
            "eui": "A844A1ABCF21116C"
          },
          "time": "1980-01-06T00:00:50.543Z",
          "timestamp": 113418667,
          "rssi": -71,
          "channel_rssi": -71,
          "snr": 9.8,
          "uplink_token": "Ch4KHAoQaGI5aWKLHMMIJzZrbC03MxIIqEBB//8hEWwQq8OKNhoMCMKr9o8GEIOgnpgBIPiHnsKm+gIqDAiy+9SWARDAi/aCAg==",
          "channel_index": 4
        }
      ],
2

Looks like the gateway is not able to reach a working NTP server. Is there a firewall between tha gateway and the internet blocking NTP traffic?

3

Good point Jac, thank you.
Nevertheless, checking the gateway log file, it seems that he gets the time properly, but is not broadcasting it.

Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ ################## Report at: 2022-02-05 14:58:04 UTC ##################
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ ### [UPSTREAM] ###
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # RF packets received by concentrator: 2
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # CRC_OK: 50.00%, CRC_FAIL: 50.00%, NO_CRC: 0.00%
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # RF packets forwarded: 1 (17 bytes)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # PUSH_DATA datagrams sent: 1 (248 bytes)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # PUSH_DATA acknowledged: 100.00%
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ ### [DOWNSTREAM] ###
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # PULL_DATA sent: 1 (100.00% acknowledged)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # PULL_RESP(onse) datagrams received: 1 (182 bytes)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # RF packets sent to concentrator: 2 (12 bytes)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # TX errors: 0
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # TX rejected (collision packet): 0.00% (req:509, rej:0)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # TX rejected (collision beacon): 0.00% (req:509, rej:0)
Sat Feb  5 15:58:04 2022 daemon.info lora_pkt_fwd[7994]: REPORT~ # TX rejected (too late): 0.00% (req:509, rej:0)```
4

Looks like at least syslog gets the right time. Might be a startup order thing that messes up the information obtained by the packet forwarder.
Just checked and my DLOS8 is forwarding packets with the right time at the gateway side.

 "time": "2022-02-06T17:13:06.187497Z"

As I don’t own active nodes near that gateway I have no means to check what arrives at the application.

5

What? You mean you’ve deployed a gateway without any personal benefit to yourself?

6

About ten of them. And there are another ten waiting for a location to provide more coverage for the community.

1 Like