Nono-Gateway with PyTrack+LoPy4 not seen

Gateways
1

Disclaimer: New to the whole LoRa (2 weeks only)…

I setup the above gateway and as far as I understand it is waiting for a LoRa node to connect:

Gateway ID: b’807D3AFFFE935E98’
[ 909.443] Starting LoRaWAN nano gateway with id: b’807D3AFFFE935E98’
[ 913.766] WiFi connected to: SoftDev
[ 913.770] Syncing time with pool.ntp.org …
[ 913.926] RTC NTP sync complete
[ 913.939] Opening UDP socket to router.eu.thethings.network (52.169.76.203) port 1700…
[ 913.951] Setting up the LoRa radio at 903.9001 Mhz using SF10BW125
[ 913.960] LoRaWAN nano gateway online
[ 913.965] You may now press ENTER to enter the REPL
[ 914.111] Push ack
[ 939.122] Pull ack
[ 964.113] Pull ack
[ 974.120] Push ack
[ 989.145] Pull ack

I also have a client that I ran after I ran my Nano-Gateway, and it says that it is not connected to the LoRaWAN network yet…and I have no idea why…

Uploading project (main folder)…
Not safe booting, disabled in settings
Uploading to /flash…
Reading file status
[1/1] Writing file main.py (5kb)
Upload done, resetting board…
OKets Jun 8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff8028,len:8
load:0x3fff8030,len:1728
load:0x4009fa00,len:0
load:0x4009fa00,len:14612
entry 0x400a059c
Connected to Wifi

sub_cb callback is set

settimeout is set

Connected to MQTT Broker

Subscribing to messages from MQTT Broker
Subscription to dwm/position is done

Issuing Join request to LoRaWAN…

Client Node: Not joined LoRaWAN yet…
Client Node: Not joined LoRaWAN yet…
Client Node: Not joined LoRaWAN yet…
Client Node: Not joined LoRaWAN yet…

The node is based partially on mqtt example (which works fine) and then LoRa connection code from OTAA example and gateway from lorawan-nano-gateway code.

How can I find out what am I doing wrong?

Just to mention: the nearest gateway from me that shows on TTN map is 5+ miles away and the area is suburb and hilly…so I do not expect my nano-gateway will connect to it…(waiting for real gateway to arrive soon).

2

misspelling in the title is always an indicator :upside_down_face:

3

Appreciate that Its possible there in no one in the TTN forum that has working knowledge of the code produced for the LoPy product.

Is the Nano gateway a single channel Gateway ? If so it is not compliant with TTN requirements and this could be a cause of your connection issues.

4

Apologies for incorrect title…
I am trying to figure out why LoPy4 node is not connecting to Nano-Gateway.
As I mentioned, I do not expect Nano-Gateway to show in TTN due to long distance (5+ miles of hilly area) to the nearest working gateway in my area…

It looked to me the right place to ask, but if I am in the wrong place - any idea where can I get help?

5

In the absense of a reply in here, you could try the Pycom\LoPy forums, the LoPy hardware and the code for gateway and node is presumably thier product.

The Nano-Gateway is presumably not a standard or compliant TTN gateway, so it may not behave as a proper one, it or the nodes may require a special setup.