TTOG still not listed as online

This has been going on for a minute but I’m just getting around to dealing with it. The TTOG seems to be properly configured, but it’s not showing up in my dashboard as on-line:

Log:
# CRC_OK: 0.00%# RF packets received by concentrator: 2
### [UPSTREAM] ###
##### 2020-09-14 18:22:20 GMT #####
JSON up: {"stat":{"time":"2020-09-14 18:21:50 GMT","lati":35.69402,"long":-78.77936,"alti":127,"rxnb":2,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":0}}
##### END #####
# GPS coordinates: latitude 35.69402, longitude -78.77936, altitude 127 m
# Valid time reference (age: 1 sec)
### [GPS] ###
# SX1301 time (PPS): 3642347496
### [JIT] ###
# BEACON rejected: 0
# BEACON sent so far: 2007
# BEACON queued: 2010
# TX errors: 0
# RF packets sent to concentrator: 0 (0 bytes)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# PULL_DATA sent: 3 (0.00% acknowledged)
### [DOWNSTREAM] ###
# PUSH_DATA acknowledged: 0.00%
# PUSH_DATA datagrams sent: 1 (155 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-09-14 18:21:50 GMT #####

And it looks to be configured correctly:
Screen Shot 2020-09-11 at 3.13.46 PM

but my console still shows:
Screen Shot 2020-09-14 at 2.31.03 PM

Any ideas??

There is an issue with the console being rather unreliable:

Use a device to uplink, check your gateway logs, look at the gateway console traffic, look at the device uplinks.

I have done this. Previously I had 2 gateways, so I powered the other one down (it was working fine, but was indoor-only) and once that one is powered off, I get no connections.

I’m basically trying to run a “Hello World” on an RPiZero. It was able to connect when the indoor gateway is on, but with that powered off, I get:

File "/usr/local/lib/python3.7/dist-packages/rak811/rak811.py", line 401, in join_otaa
raise Rak811EventError(status)
rak811.rak811.Rak811EventError: [Errno 6] Rx2 timeout

There is zero traffic in the gateway logs indicating even an attempt to connect by the client.

I guess this could be part of the problem :slight_smile:

PING us-west.thethings.network (13.66.229.235) 56(84) bytes of data.

--- us-west.thethings.network ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4004ms

whereas:

PING ttn.opennetworkinfrastructure.org (86.119.29.227) 56(84) bytes of data.
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=1 ttl=48 time=112 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=2 ttl=48 time=112 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=3 ttl=48 time=113 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=4 ttl=48 time=114 ms
64 bytes from ttn01.switch.ch (86.119.29.227): icmp_seq=5 ttl=48 time=124 ms

--- ttn.opennetworkinfrastructure.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 112.417/115.480/124.092/4.403 ms

The TTN back end NS’s are behind load balancers (AWS) so ping doesnt work, am afraid those results dont help you!

If the gateway logs do not list any valid LoRaWAN packets being received you should:

  1. Check the frequency plan. Is your gateway listening at the frequencies your node transmits?
  2. Check antenna connectors and cable and make sure you connected to right antenna to the right connector. TTOG has multiple connectors and you need to use the right one for the LoRaWAN antenna.
  3. Make sure to have the node antenna at least 12 feet away from the gateway antenna. Larger distance is better.