WM1302 -- TTN showing disconnected?

Products & Technology LoRa
#1

Good afternoon.
I used WM1302 wiki to connect my gateway to the TTN. My gateway is showing disconnected and has been. My RPI console shows the following. Notice GPS Warning…Can someone tell me

  1. I live in a rural area and am not sure if GPS is not getting found OR if I don’t have something configured correctly for the GPS. Can someone describe how to verify if I have everything set up correctly for GPS? I used the above wiki in the Interface Options section #4 and it looks correct.

  2. If I cannot get GPS signal will TTN show disconnected? Is there a way to over-ride this?

  3. My original beacon frequency in global_conf.json.sx1250.US915 was 869525000 which seemed odd given the board is a US spi 915MHz board so I changed this to 915000000…Is this a problem?

Thank you

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
^C
##### 2023-05-30 18:00:30 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 0
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 0 (0 bytes)
# PUSH_DATA datagrams sent: 1 (123 bytes)
# PUSH_DATA acknowledged: 0.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 1 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 528727802
# SX1302 counter (PPS):  0
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# Invalid time reference (age: 1685469630 sec)
# no valid GPS coordinates available yet
### Concentrator temperature: 42 C ###
##### END #####

INFO: End of upstream thread

INFO: End of JIT thread

INFO: End of validation thread
WARNING: [gps] could not get GPS time from GPS

INFO: End of GPS thread

INFO: End of downstream thread
INFO: GPS closed successfully
Closing SPI communication interface
INFO: concentrator stopped successfully
CoreCell reset through GPIO17...
SX1261 reset through GPIO17...
CoreCell power enable through GPIO18...
CoreCell ADC reset through GPIO13...
INFO: Exiting packet forwarder program
#2

Have you setup your RPI to update its time/date automatically from an NTP server on Internet ? It looks like from logs that your RPI doesn’t have a reliable time/date source (it can be supplied by the GPS if it works…)

#3

Hello Vincen…
I am not sure what you mean here?? I have setup the timezone, etc. in RPi and all looks good. I can use cat -n /dev/ttyS0 | more and see that my GPS signals look good (location is listed accurately here). Here is the latest that I see after running packet_forwarder. Notice it is different from last posting now that I have connected an antenna, BUT the results are the same that is TTN shows that the gateway is disconnected.

Any ideas?

Version: 2.1.0
*** SX1302 HAL library version info ***
Version: 2.1.0;
***
INFO: Little endian host
INFO: found configuration file global_conf.json.sx1250.US915, parsing it
INFO: global_conf.json.sx1250.US915 does contain a JSON object named SX130x_conf, parsing SX1302 parameters
INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0
INFO: antenna_gain 0 dBi
INFO: Configuring legacy timestamp
INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250
INFO: radio 0 enabled (type SX1250), center frequency 904300000, RSSI offset -215.399994, tx enabled 1, single input mode 0
INFO: radio 1 enabled (type SX1250), center frequency 905000000, RSSI offset -215.399994, tx enabled 0, single input mode 0
INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8, Explicit header
INFO: FSK channel 8 disabled
INFO: global_conf.json.sx1250.US915 does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to FFFFFFFFFFFFFFFF
INFO: server hostname or IP address is configured to "nam1.cloud.thethings.network"
INFO: upstream port is configured to "1700"
INFO: downstream port is configured to "1700"
INFO: downstream keep-alive interval is configured to 10 seconds
INFO: statistics display interval is configured to 30 seconds
INFO: upstream PUSH_DATA time-out is configured to 100 ms
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: GPS serial port path is configured to "/dev/ttyS0"
INFO: Reference latitude is configured to 0.000000 deg
INFO: Reference longitude is configured to 0.000000 deg
INFO: Reference altitude is configured to 0 meters
INFO: Beaconing period is configured to 0 seconds
INFO: Beaconing signal will be emitted at 923300000 Hz
INFO: Beaconing datarate is set to SF9
INFO: Beaconing modulation bandwidth is set to 125000Hz
INFO: Beaconing TX power is set to 14dBm
INFO: Beaconing information descriptor is set to 0
INFO: global_conf.json.sx1250.US915 does contain a JSON object named debug_conf, parsing debug parameters
INFO: got 2 debug reference payload
INFO: reference payload ID 0 is 0xCAFE1234
INFO: reference payload ID 1 is 0xCAFE2345
INFO: setting debug log file name to loragw_hal.log
INFO: [main] TTY port /dev/ttyS0 open for GPS synchronization
CoreCell reset through GPIO17...
SX1261 reset through GPIO17...
CoreCell power enable through GPIO18...
CoreCell ADC reset through GPIO13...
Opening SPI communication interface
Note: chip version is 0x10 (v1.0)
INFO: using legacy timestamp
INFO: LoRa Service modem: configuring preamble size to 8 symbols
ARB: dual demodulation disabled for all SF
INFO: found temperature sensor on port 0x39
INFO: [main] concentrator started, packet can now be received
INFO: concentrator EUI: 0x0016c001f151bc24
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 104 ms
INFO: [down] PULL_ACK received in 90 ms
INFO: [down] PULL_ACK received in 92 ms

##### 2023-05-31 12:39:35 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 0
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 0 (0 bytes)
# PUSH_DATA datagrams sent: 0 (0 bytes)
# PUSH_DATA acknowledged: 0.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 30725316
# SX1302 counter (PPS):  29799980
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# Valid time reference (age: 0 sec)
# no valid GPS coordinates available yet
### Concentrator temperature: 24 C ###
##### END #####
#4

Connected an antenna ? you speak of GPS I hope ? If you have run the gateway without Lora antenna attached to it you might have already damaged/destroyed the RF chipset in the gateway…
You have well configured at TTN the gateway with its ID ? Let it run few hours without interruption as sometimes first show-up of a new gw in TTN network is taking time :wink:

#5

Yes, sorry I meant GPS antenna…Ok I will let it run some time. Does TTN require the GPS signal to create a link to the gateway??

I have a Lora-E5 development board at this end. If I give the board the command AT+JOIN, it fails to connect to the gateway…Could there be something else I am missing to this puzzle?

#6

Nope, GPS is useless for TTN gateways :wink:

Wait for gateway to show up in TTN :wink:

#7

Hello Vincen…
Gateway is showing up!! Thank you. 1/2 way there.

Now for the Lora-E5 dev board.

I cannot seem to get it to join the network. I have verified the EUI on TTN matches my end device. I have copied and pasted the APPKEY, NWKSKEY and APPSKEY from TTN and used the AT+ commands on the device to set these. I have also set the US915 in an AT+ command. I have tried joining the network by trying both ABP and OTAA but both times the response from the device was Join Failed…

Can you tell me what I might be missing here?

#8

2 things there:
→ first check if it’s possible on the gw if it receives lora messages from the E5
→ second check in console of gw on TTN website to see if it receives messages from E5 (it’ll show up in console even if device not allowed/not properly setup for TTN :wink:

1 Like
#9

Well I don’t claim to know what happened but I just tried join again in OTAA and it works!! Eureka… :smile:

Thanks for all the support

#10

Congrats :+1: One thing that may be a problem sometimes: don’t keep your lora devices too near of gw when testing (typically on desk) because you can saturate the GW and prevents it to receive properly messages from device :wink:

#11

Understood…Thanks for the support…

1 Like