TTOG not receiving node signals

awentzel · December 16, 2019, 9:36pm

I am having trouble getting my TTOG set up. I followed the things network instructions for setup, and it is currently running software version opdk-1.01.09. However, when I start up my nodes (the things uno), they are unable to connect to the gateway. Occasionally I will see a join request on the gateway on TTN, but the node seems to never receive the accept signal back. I have used the node with the things network gateway with no problems, and I’m wondering if there are certain frequencies or spread factors that the node has to be sending and receiving on for the TTOG to pick it up. Below is the log from the node (with the EUIs removed), and then the log from the gateway.

[details=Click to see the full logs]
```text
Initializing...
-- STATUS
EUI: 
Battery: 3283
AppEUI:
DevEUI:
Data Rate: 3
RX Delay 1: 1000
RX Delay 2: 2000
-- JOIN
Model: RN2903
Version: 0.9.8
Sending: mac set deveui
Sending: mac set adr off
Sending: mac set deveui 
Sending: mac set appeui 
Sending: mac set appkey 
Sending: mac save
Sending: mac set ch status 0 off
Sending: mac set ch status 1 off
Sending: mac set ch status 2 off
Sending: mac set ch status 3 off
Sending: mac set ch status 4 off
Sending: mac set ch status 5 off
Sending: mac set ch status 6 off
Sending: mac set ch status 7 off
Sending: mac set ch status 8 on
Sending: mac set ch drrange 8 0 3
Sending: mac set ch status 9 on
Sending: mac set ch drrange 9 0 3
Sending: mac set ch status 10 on
Sending: mac set ch drrange 10 0 3
Sending: mac set ch status 11 on
Sending: mac set ch drrange 11 0 3
Sending: mac set ch status 12 on
Sending: mac set ch drrange 12 0 3
Sending: mac set ch status 13 on
Sending: mac set ch drrange 13 0 3
Sending: mac set ch status 14 on
Sending: mac set ch drrange 14 0 3
Sending: mac set ch status 15 on
Sending: mac set ch drrange 15 0 3
Sending: mac set ch status 16 off
Sending: mac set ch status 17 off
Sending: mac set ch status 18 off
Sending: mac set ch status 19 off
Sending: mac set ch status 20 off
Sending: mac set ch status 21 off
Sending: mac set ch status 22 off
Sending: mac set ch status 23 off
Sending: mac set ch status 24 off
Sending: mac set ch status 25 off
Sending: mac set ch status 26 off
Sending: mac set ch status 27 off
Sending: mac set ch status 28 off
Sending: mac set ch status 29 off
Sending: mac set ch status 30 off
Sending: mac set ch status 31 off
Sending: mac set ch status 32 off
Sending: mac set ch status 33 off
Sending: mac set ch status 34 off
Sending: mac set ch status 35 off
Sending: mac set ch status 36 off
Sending: mac set ch status 37 off
Sending: mac set ch status 38 off
Sending: mac set ch status 39 off
Sending: mac set ch status 40 off
Sending: mac set ch status 41 off
Sending: mac set ch status 42 off
Sending: mac set ch status 43 off
Sending: mac set ch status 44 off
Sending: mac set ch status 45 off
Sending: mac set ch status 46 off
Sending: mac set ch status 47 off
Sending: mac set ch status 48 off
Sending: mac set ch status 49 off
Sending: mac set ch status 50 off
Sending: mac set ch status 51 off
Sending: mac set ch status 52 off
Sending: mac set ch status 53 off
Sending: mac set ch status 54 off
Sending: mac set ch status 55 off
Sending: mac set ch status 56 off
Sending: mac set ch status 57 off
Sending: mac set ch status 58 off
Sending: mac set ch status 59 off
Sending: mac set ch status 60 off
Sending: mac set ch status 61 off
Sending: mac set ch status 62 off
Sending: mac set ch status 63 off
Sending: mac set ch status 64 off
Sending: mac set ch status 65 on
Sending: mac set ch status 66 off
Sending: mac set ch status 67 off
Sending: mac set ch status 68 off
Sending: mac set ch status 69 off
Sending: mac set ch status 70 off
Sending: mac set ch status 71 off
Sending: mac set pwridx 5
Sending: mac set retx 7
Sending: mac set dr 3
Sending: mac join otaa
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa
Join not accepted: denied
Check your coverage, keys and backend status.

[/details]

Click to see the full logs

INFO: [up] PUSH_ACKJSON up: {"stat":{"time":"2019-12-16 21:08:13 GMT","lati":42.12570,"long":-88.00133,"alti":264,"rxnb":1,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}
##### END #####
# GPS coordinates: latitude 42.12570, longitude -88.00133, altitude 264 m
# Valid time reference (age: 1 sec)
### [GPS] ###
# SX1301 time (PPS): 2390627609
### [JIT] ###
# BEACON rejected: 0
# BEACON sent so far: 50
# BEACON queued: 54
# TX rejected (too early): 0.00% (req:1, rej:0)
# TX rejected (too late): 0.00% (req:1, rej:0)
# TX rejected (collision beacon): 0.00% (req:1, rej:0)
# TX rejected (collision packet): 0.00% (req:1, rej:0)
# TX errors: 0
# RF packets sent to concentrator: 0 (0 bytes)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# PULL_DATA sent: 3 (100.00% acknowledged)
### [DOWNSTREAM] ###
# PUSH_DATA acknowledged: 100.00%
# PUSH_DATA datagrams sent: 1 (157 bytes)
# RF packets forwarded: 0 (0 bytes)
# CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
# RF packets received by concentrator: 1
### [UPSTREAM] ###
##### 2019-12-16 21:08:13 GMT #####
WARNING: [gps] GPS out of sync, keeping previous time reference
INFO: [down] PULL_ACK received in 58 ms
WARNING: [gps] GPS out of sync, keeping previous time reference
INFO: [down] PULL_ACK received in 58 ms
WARNING: [gps] GPS out of sync, keeping previous time reference
WARNING: [gps] GPS out of sync, keeping previous time reference
INFO: [down] PULL_ACK received in 58 ms
WARNING: [gps] GPS out of sync, keeping previous time reference
INFO: [up] PUSH_ACK received in 60 ms
JSON up: {"stat":{"time":"2019-12-16 21:07:43 GMT","lati":42.12566,"long":-.00128,"alti":263,"rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}
##### END #####
# GPS coordinates: latitude 42.12566, longitude -88.00128, altitude 263 m
# Valid time reference (age: 1 sec)
### [GPS] ###
# SX1301 time (PPS): 2367628269
### [JIT] ###
# BEACON rejected: 0
# BEACON sent so far: 50
# BEACON queued: 54
# TX rejected (too early): 0.00% (req:1, rej:0)
# TX rejected (too late): 0.00% (req:1, rej:0)
# TX rejected (collision beacon): 0.00% (req:1, rej:0)
# TX rejected (collision packet): 0.00% (req:1, rej:0)
# TX errors: 0
# RF packets sent to concentrator: 0 (0 bytes)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# PULL_DATA sent: 3 (100.00% acknowledged)
### [DOWNSTREAM] ###
# PUSH_DATA acknowledged: 100.00%
# PUSH_DATA datagrams sent: 1 (157 bytes)
# RF packets forwarded: 0 (0 bytes)
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets received by concentrator: 0
### [UPSTREAM] ###
##### 2019-12-16 21:07:43 GMT #####

cslorabox · December 16, 2019, 9:52pm

Nodes don’t connect to gateways.

To the extent that there is a “connection” at all, ie, a join - accept cycle, that is a connection to the network servers made through the gateway. But not with it.

Occasionally I will see a join request on the gateway on TTN, but the node seems to never receive the accept signal back.

Details of these would be key.

Your logs don’t show details of any actual transmissions or attempts to receive in the downlink window.

Your gateway log doesn’t show any packets being received

BEACON sent so far: 50

This seems a bit odd however. TTN nodes don’t usually make use of gateway beacons, so it’s probably not productive to be sending them even if being GPS enabled makes it possible to do so.

It shouldn’t be frequently causing a problem, it just seems an unnecessary use of spectrum and intermittent distraction from the task of being a gateway.

obaeyens · December 16, 2019, 9:55pm

I am all new to things, but is there not a limit in amount of data every nod can send per day?
Like 30 seconds per day?

I don’t know who this limit is enforced, I don’t think you can prevent the node to transmit but the gateway could prevent to even listen and record the node.

Maybe you ran out of transmissions per day?

cslorabox · December 16, 2019, 9:57pm

It isn’t enforced unless the node’s own firmware does so. But the logs indicate the node transmitted, they just lack any detail even of basic things like frequency.

I don’t think you can prevent the node to transmit but the gateway could prevent to even listen and record the node.

No, it really can’t. A gateway doesn’t even have a very good way to know which node is transmitting (especially for a join request). Gateways really play no role in the protocol at all - that’s exclusively the business of the node and servers.

awentzel · December 16, 2019, 10:01pm

Here are the logs on the gateway from TTN. But looking at my device, it never receives the accept.
ttog

JOIN REQUEST:

Click to see the full logs

{
  "gw_id": "eui-000080029c40f58a",
  "payload": "AOhZAtB+1bNwwgYiAAujBADjClR8ZDU=",
  "dev_eui": "",
  "lora": {
    "spreading_factor": 10,
    "bandwidth": 125,
    "air_time": 370688000
  },
  "coding_rate": "4/5",
  "timestamp": "2019-12-16T21:54:20.110Z",
  "rssi": -94,
  "snr": -7,
  "app_eui": "70B3D57ED00259E8",
  "frequency": 902300000
}


JOIN ACCEPT:

Click to see the full logs

{
  "gw_id": "eui-000080029c40f58a",
  "payload": "ICNP/BlqKggrJYdZhS6Xw58=",
  "lora": {
    "spreading_factor": 10,
    "bandwidth": 500,
    "air_time": 82432000
  },
  "coding_rate": "4/5",
  "timestamp": "2019-12-16T21:54:24.111Z",
  "frequency": 923300000
}

cslorabox · December 16, 2019, 10:05pm

Does your gateway log show that it transmitted this join request? If not does TTN show that it was routed to your gateway or to some other?

It would be really useful if you could make the node produce more meaningful logs, particular with regard to receive windows. You have both the advantage that a lot of the LoRaWAN implementation is buried in the RN2403 where it should “just work” but also the disadvantage that you have less visibility into details if it doesn’t.

Watching the gateway logs may be the most useful.

An interesting difference in behavior is that this gateway seems to be running in terms of GPS times, vs. raw local counter times. That would exercise different pathways through code and could thus hit different bugs, I wonder if there’s a way to disable the GPS and make it time downlinks vs uplinks based on the raw counter instead.

awentzel · December 16, 2019, 10:26pm

This seems to be the relevant log from the gateway. I can also just unplug the gps, it’s not really necessary for the application.

Click to see the full logs


##### 2019-12-16 22:01:13 GMT #####
INFO: [down] PULL_ACK received in 57 ms
INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
INFO: unsupported RF power for TX - 20 => use 21 instead
JSON down: {"txpk":{"imme":false,"tmst":1265470652,"freq":925.7,"rfch":0,"powe":20,"modu":"LORA","datr":"SF10BW500","codr":"4/5","ipol":true,"size":17,"ncrc":true,"data":"IORId1HNpU8Z39UdpbXNsTs="}}

INFO: [down] PULL_RESP received  - token[24:81] :)
INFO: [down] PULL_ACK received in 58 ms

JSON up: {"rxpk":[{"tmst":1260470652,"time":"2019-12-16T22:00:50.810613Z","tmms":1260568850810,"chan":4,"rfch":1,"freq":903.100000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-5.2,"lsnr_min":-9.5,"lsnr_max":-3.5,"rssi":-97,"size":23,"data":"AOhZAtB+1bNwwgYiAAujBACARJr9llw="}]}

INFO: Received pkt from mote: D00259E8 (fcnt=46037)
INFO: [down] PULL_ACK received in 58 ms
WARNING: [gps] GPS out of sync, keeping previous time reference
JSON up: {"stat":{"time":"2019-12-16 22:00:43 GMT","lati":42.12537,"long":-88.00127,"alti":222,"rxnb":5,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":1}}

##### END #####

awentzel · December 17, 2019, 9:56pm

Figured it out. The TTOG by default only listens on 9 channels(0-7 as the 125kHz ones and 65 as the 500kHz one), which didn’t match up with the channels that the node was sending on, so all I had to do was switch it to listening on the correct channels. Dumb mistake, but that’s what it usually is. Thanks for your help!

cslorabox · December 18, 2019, 4:16am

How come your TTN gateway and gateway onboard logs show frequencies belonging to channels in the 9-15 range then?

Did these come from a different gateway?

kaycee · January 30, 2020, 2:30pm

I have a similar problem. I have sensors from 3 different sources (the things uno, the things NODE, and adafruit feather), that all forward traffic to TTN via the things indoor gateway.
I also have a TTOG that i tried to install. The TTOG shows up on TTN console as active, but shows no traffic at all. It is running the same firmware as you list opdk-1.01.09. I am NOT an expert with radios nor routers, so all help is appreciated. I ordered the TTOG and the TTIG at the same time and I don’t understand why one is forwarding traffic and the other is not.

awentzel · January 30, 2020, 3:03pm

Hi Kaycee. Here’s the problem I was having. My TTOG was listening/sending on different frequencies than my things uno was sending. When you plug in the uno, the serial output should list all 71 channels and whether they are on or off. For me, the uno has channels 8-15 turned on for uplink, and 65 on for downlink. For US, the frequencies are listed here: https://www.baranidesign.com/faq-articles/2019/4/23/lorawan-usa-frequencies-channels-and-sub-bands-for-iot-devices (you can see 8-15 is sub-band 2). Then in the TTOG, I changed the frequency settings to match those channels. For the uplink sub-band 2, the frequency starts at 903.9 and increments by 200KHz to 905.3MHz. I was only using unos, so they were all sending on those channels.

kaycee · January 30, 2020, 3:57pm

Thanks very much, i’ll take a look at that. I’m trying to figure out how to connect and talk to the TTIG so i can see why it is working with all these different nodes. I just used the minimum setup/config that The Things Network publishes on their pages for these 2 gateways. So for the TTIG i just used the browser based GUI config, it took all of about 2 minutes and it’s forwarding all sensors through TTN and onto my node-red server. Should i start a separate thread?

cslorabox · January 30, 2020, 5:12pm

That is correct for the US.

That’s a bit of confusion. Channel 65 is a wideband uplink channel.

RX1 Downlink channels are separately defined and chosen algorithmically ie, the downlink channel number is the the uplink channel number modulo 8.

cslorabox · January 30, 2020, 5:16pm

That’s not really necessary. In the gateway’s traffic page on TTN you can (if you are the owner) see the various frequencies it is receiving nodes on. Those should of course be the standard 2nd 900 MHz sub-band.

What you might check is if the global_conf.json in your TTOG is correct. Someone alleged this was wrong, but then posted logs showing it actually receiving on the correct frequencies, so it doesn’t seem all that established that it might be wrong, unless you’ve bought a box built for a different frequency band entirely, like EU868.

Probably what you should do is get into the TTOG and examine the packet forwarder logs - it’s possible the packet forwarder isn’t even running.

kaycee · January 30, 2020, 5:53pm

Thanks again.
I have all nodes off except TheThingsNODE for now. It is reporting via the TTIG on frequencies ranging from 903.3 - 905.3 the past few minutes. I can see the packet forwarder logs, but I’m not sure how to check if everything is normal. It does not seem to have the GPS running. If i power cycle i get a lot of startup info, as the log online does not store much. I don’t see anywhere on the gui login where I can go into command mode. I have tried ssh to the unit ip address, but no luck. How do i get to the global_conf.json file?

kaycee · January 30, 2020, 6:12pm

The TTOG radio settings central frequency was set 9026, so just as a guess i changed it to 9043 as that seems the middle of what the NODE was using via the TTIG. Then i rebooted the TTOG.
Finally the TTN gateway overview shows 2 received messages, 0 transmitted. under the traffic tab it shows one message from the NODE. I have tried to send more messages, but now we are back to nothing new showing up on the traffic tab.


`INFO: JSON up: {"stat":{"time":"2020-01-30 17:57:37 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580407057 sec)

### [GPS] ###

# SX1301 time (PPS): 182572847

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 100.00%

# PUSH_DATA datagrams sent: 1 (113 bytes)

# RF packets forwarded: 0 (0 bytes)

# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 0

### [UPSTREAM] ###

##### 2020-01-30 17:57:37 GMT #####



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 34 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 37 ms

WARNING: [gps] could not get GPS time from GPS

INFO: [up] PUSH_ACK received in 36 ms

JSON up: {"stat":{"time":"2020-01-30 17:57:07 GMT","rxnb":2,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580407027 sec)

### [GPS] ###

# SX1301 time (PPS): 182572847

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 100.00%

# PUSH_DATA datagrams sent: 1 (113 bytes)

# RF packets forwarded: 0 (0 bytes)

# CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 2

### [UPSTREAM] ###

##### 2020-01-30 17:57:07 GMT #####





INFO: Enabling GPS mode for concentrator's counter.

INFO: host/sx1301 time offset=(1580406845s:39737µs) - drift=-1631µs

INFO: Disabling GPS mode for concentrator's counter...



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

INFO: [up] PUSH_ACK received in 35 ms

JSON up: {"stat":{"time":"2020-01-30 17:56:37 GMT","rxnb":1,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580406997 sec)

### [GPS] ###

# SX1301 time (PPS): 122570855

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 100.00%

# PUSH_DATA datagrams sent: 1 (113 bytes)

# RF packets forwarded: 0 (0 bytes)

# CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 1

### [UPSTREAM] ###

##### 2020-01-30 17:56:37 GMT #####



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

INFO: [up] PUSH_ACK received in 36 ms

JSON up: {"stat":{"time":"2020-01-30 17:56:07 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580406967 sec)

### [GPS] ###

# SX1301 time (PPS): 122570855

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 100.00%

# PUSH_DATA datagrams sent: 1 (113 bytes)

# RF packets forwarded: 0 (0 bytes)

# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 0

### [UPSTREAM] ###

##### 2020-01-30 17:56:07 GMT #####





INFO: Enabling GPS mode for concentrator's counter.

INFO: host/sx1301 time offset=(1580406845s:41368µs) - drift=-30514µs

INFO: Disabling GPS mode for concentrator's counter...



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

INFO: [up] PUSH_ACK received in 37 ms

JSON up: {"stat":{"time":"2020-01-30 17:55:37 GMT","rxnb":2,"rxok":1,"rxfw":1,"ackr":100.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580406937 sec)

### [GPS] ###

# SX1301 time (PPS): 62539850

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 100.00%

# PUSH_DATA datagrams sent: 2 (346 bytes)

# RF packets forwarded: 1 (19 bytes)

# CRC_OK: 50.00%, CRC_FAIL: 50.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 2

### [UPSTREAM] ###

##### 2020-01-30 17:55:37 GMT #####



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [up] PUSH_ACK received in 37 ms

JSON up: {"rxpk":[{"tmst":63109395,"chan":1,"rfch":0,"freq":904.200000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":-4.2,"lsnr_min":-9.8,"lsnr_max":-2.5,"rssi":-79,"size":19,"data":"QBIuAiYADQACyC5XAPCzEfAPjw=="}]}



INFO: Received pkt from mote: 26022E12 (fcnt=13)



WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

INFO: [up] PUSH_ACK received in 35 ms

JSON up: {"stat":{"time":"2020-01-30 17:55:07 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580406907 sec)

### [GPS] ###

# SX1301 time (PPS): 62539850



INFO: Enabling GPS mode for concentrator's counter.

INFO: host/sx1301 time offset=(1580406845s:71882µs) - drift=-30581µs

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 100.00%

# PUSH_DATA datagrams sent: 1 (111 bytes)

# RF packets forwarded: 0 (0 bytes)

# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 0

### [UPSTREAM] ###

##### 2020-01-30 17:55:07 GMT #####



INFO: Disabling GPS mode for concentrator's counter...



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 34 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

INFO: [up] PUSH_ACK received in 36 ms

JSON up: {"stat":{"time":"2020-01-30 17:54:37 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":0}}



##### END #####

# no valid GPS coordinates available yet

# Invalid time reference (age: 1580406877 sec)

### [GPS] ###

# SX1301 time (PPS): 2508551

### [JIT] ###

# BEACON rejected: 0

# BEACON sent so far: 0

# BEACON queued: 0

# TX errors: 0

# RF packets sent to concentrator: 0 (0 bytes)

# PULL_RESP(onse) datagrams received: 0 (0 bytes)

# PULL_DATA sent: 3 (100.00% acknowledged)

### [DOWNSTREAM] ###

# PUSH_DATA acknowledged: 0.00%

# PUSH_DATA datagrams sent: 0 (0 bytes)

# RF packets forwarded: 0 (0 bytes)

# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

# RF packets received by concentrator: 0

### [UPSTREAM] ###

##### 2020-01-30 17:54:37 GMT #####



WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 34 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 33 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

INFO: [down] PULL_ACK received in 36 ms

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS

WARNING: [gps] could not get GPS time from GPS



INFO: Enabling GPS mode for concentrator's counter.

INFO: host/sx1301 time offset=(1580406845s:102463µs) - drift=614095231µs

INFO: Disabling GPS mode for concentrator's counter...



INFO: [main] concentrator started, packet can now be received

INFO: FPGA supported features: [TX filter]  [Spectral Scan]  [LBT] 

INFO: [main] TTY port /dev/ttyS3 open for GPS synchronization

INFO: Beaconing information descriptor is set to 0

INFO: Beaconing TX power is set to 14dBm

INFO: Beaconing modulation bandwidth is set to 500000Hz

INFO: Beaconing datarate is set to SF12

INFO: Beaconing channel frequency step is set to 600000Hz

INFO: Beaconing channel number is set to 8

INFO: Beaconing signal will be emitted at 923300000 Hz

INFO: Beaconing period is configured to 128 seconds

INFO: Reference altitude is configured to 0 meters

INFO: Reference longitude is configured to 0.000000 deg

INFO: Reference latitude is configured to 0.000000 deg

INFO: GPS serial port path is configured to "/dev/ttyS3"

INFO: packets received with no CRC will NOT be forwarded

INFO: packets received with a CRC error will NOT be forwarded

INFO: packets received with a valid CRC will be forwarded

INFO: upstream PUSH_DATA time-out is configured to 100 ms

INFO: statistics display interval is configured to 30 seconds

INFO: downstream keep-alive interval is configured to 10 seconds

INFO: downstream port is configured to "1700"

INFO: upstream port is configured to "1700"

INFO: server hostname or IP address is configured to "router.us.thethings.network"

INFO: /app/cfg/global_conf_0.json does contain a JSON object named gateway_conf, parsing gateway parameters

INFO: FSK channel 8 disabled

INFO: Lora standard channel 8 disabled

INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 3>  radio 0, IF 300000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 2>  radio 0, IF 100000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 1>  radio 0, IF -100000 Hz, 125 kHz bw, SF 7 to 12

INFO: Lora multi-SF channel 0>  radio 0, IF -300000 Hz, 125 kHz bw, SF 7 to 12

INFO: radio 1 enabled (type SX1257), center frequency 903400000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0

INFO: radio 0 enabled (type SX1257), center frequency 904300000, RSSI offset -166.000000, tx enabled 1, tx_notch_freq 129000

INFO: Configuring TX LUT with 16 indexes

INFO: antenna_gain 2 dBi

INFO: LBT is disabled

INFO: lorawan_public 1, clksrc 1

INFO: /app/cfg/global_conf_0.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters

INFO: found global configuration file /app/cfg/global_conf_0.json, parsing it

INFO: Use SPI dev : /dev/spidev0.0

INFO: gateway MAC address is configured as 000080029C2B29C9

INFO: Little endian host

***

Version: 5.0.1;

*** Lora concentrator HAL library version info ***

Version: 4.0.1

*** Beacon Packet Forwarder for Lora Gateway ***

`

kaycee · January 30, 2020, 6:13pm

I know all the guru’s are at the conference, but i have an update.
I just looked at the logs on TTN console and the logs for the TTOG are showing 3 out of 4 sensors checking in VERY randomly over 4-5 hours. But all 4 sensors are reporting very regularly via the TTIG. One sensor every 5 minutes, the others every 30 seconds.

So, i still have something not configured correctly and I’m not sure what to look for. The only change so far has been to change the TTOG ‘center frequency’ from 9026 to 9043.

everhamme · March 7, 2020, 12:19pm

The channel offsets become important too… did you modify those? Also whether each channel is assigned to radio 0 or 1.

gglemke · March 31, 2020, 1:55pm

Hi @awentzel,

Would you mind taking a screenshot of your settings that fixed this? We have the same issue you reported and would be so grateful for your input.

Thanks so much,
Grant