Trackerd no success on joining

End Devices (Nodes)
,
1

Hi there, I bought a Dragino trackerD to hopefully have a better start with TTN and do some range mapping etc. While its open hardware, this device comes ready-to-use, but I don’t get it to sucessfully join the network.

I followed the instructions and quickstart guide but get no events on the TTN console.
grafik
I know that here is coverage and I also used different locations that have even better coverage … The LoraWan Ver. 1.0.3 is selected, as well as SF12 frequency plan

The tracker gets stuck in a join loop:

[19:54:45:961] rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)␍␊
[19:54:45:961] configsip: 188777542, SPIWP:0xee␍␊
[19:54:45:961] clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00␍␊
[19:54:46:061] mode:DIO, clock div:1␍␊
[19:54:46:061] load:0x3fff0030,len:1284␍␊
[19:54:46:061] load:0x40078000,len:12836␍␊
[19:54:46:061] load:0x40080400,len:3032␍␊
[19:54:46:061] entry 0x400805e4␍␊
[19:54:46:463] Wakeup was not caused by deep sleep: 0␍␊
[19:54:46:463] TrackerD ,v1.4.7␍␊
[19:54:46:463] EU868␍␊
[19:54:47:984] TDC:1200000␍␊
[19:54:47:984] BAT:4002 mV␍␊
[19:54:47:984] Packet queued␍␊
[19:54:47:984] 97256: EV_JOINING␍␊
[19:54:52:848] 401404: EV_TXSTART␍␊
[19:54:53:054] 413932: TXMODE, freq=868500000, len=23, SF=7, BW=125, CR=4/5, IH=0␍␊
[19:54:58:118] start single rx: now-rxtime: 4␍␊
[19:54:58:118] 730183: RXMODE_SINGLE, freq=868500000, SF=7, BW=125, CR=4/5, IH=0␍␊
[19:54:58:118] rxtimeout: entry: 730708 rxtime: 730172 entry-rxtime: 536 now-entry: 6 rxtime-txend: 312375␍␊
[19:54:59:116] start single rx: now-rxtime: 4␍␊
[19:54:59:116] 792682: RXMODE_SINGLE, freq=869525000, SF=12, BW=125, CR=4/5, IH=0␍␊
[19:54:59:348] rxtimeout: entry: 807033 rxtime: 792672 entry-rxtime: 14361 now-entry: 5 rxtime-txend: 374875␍␊
[19:54:59:348] 807055: EV_JOIN_TXCOMPLETE: no JoinAccept␍␊
[19:56:04:005] 4848724: EV_TXSTART␍␊
[19:56:04:212] 4861303: TXMODE, freq=868100000, len=23, SF=7, BW=125, CR=4/5, IH=0␍␊
[19:56:09:276] start single rx: now-rxtime: 4␍␊
[19:56:09:276] 5177554: RXMODE_SINGLE, freq=868100000, SF=7, BW=125, CR=4/5, IH=0␍␊
[19:56:09:276] rxtimeout: entry: 5178078 rxtime: 5177543 entry-rxtime: 535 now-entry: 6 rxtime-txend: 312375␍␊
[19:56:10:274] start single rx: now-rxtime: 4␍␊
[19:56:10:274] 5240053: RXMODE_SINGLE, freq=869525000, SF=12, BW=125, CR=4/5, IH=0␍␊
[19:56:10:506] rxtimeout: entry: 5254403 rxtime: 5240043 entry-rxtime: 14360 now-entry: 5 rxtime-txend: 374875␍␊
[19:56:10:506] 5254425: EV_JOIN_TXCOMPLETE: no JoinAccept␍␊
[19:57:14:361] 9245964: EV_TXSTART␍␊
[19:57:14:567] 9258491: TXMODE, freq=868300000, len=23, SF=7, BW=125, CR=4/5, IH=0␍␊
[19:57:19:631] start single rx: now-rxtime: 3␍␊
[19:57:19:631] 9574741: RXMODE_SINGLE, freq=868300000, SF=7, BW=125, CR=4/5, IH=0␍␊
[19:57:19:631] rxtimeout: entry: 9575266 rxtime: 9574731 entry-rxtime: 535 now-entry: 6 rxtime-txend: 312375␍␊
[19:57:20:629] start single rx: now-rxtime: 3␍␊
[19:57:20:629] 9637241: RXMODE_SINGLE, freq=869525000, SF=12, BW=125, CR=4/5, IH=0␍␊
[19:57:20:861] rxtimeout: entry: 9651590 rxtime: 9637231 entry-rxtime: 14359 now-entry: 5 rxtime-txend: 374875␍␊
[19:57:20:861] 9651612: EV_JOIN_TXCOMPLETE: no JoinAccept␍␊

I already doublechecked DevEUI / JoinEUI / App Key (copied from logger terminal itself) and re-created the node setup manually and as wizzard.
I read different posts on the tracker, but have no idea what causes the issue. Some mention that downlink timing is ciritcal, but is it wise to tweak it manually?

2

Not the one marked “recommended for TTN” then, for use on TTN networks, by TTN gateways and devices that wish to use TTN

No human can ever know this, pigeons maybe, but RF truth is between your device and a gateway.

There is also the issue of if the gateway you think you are in range of is actually on.

Search the forum, almost everyone that starts with LoRaWAN ends up with their own gateway as it’s the only way to know your device is configured & transmitting OK.

3

You are right, there is nothing like true confidence :wink:
In my case the gateway close to me went offline a few days ago. More confusing it is listed at our dashboard but API calls reveal that it is offline.

So moving trough the city with the original SF12 settings worked fine, but not at my home :laughing:

4

Welcome to the club!

Would be worth changing to SF9 plan to get the best of TTN

5

@huegelfunk and for TTN infrastructure to deliver its best. Moving up each SF step is ~2x time on air so your SF12 requests are ~8x longer than those of us at SF9, and as GW cannot listen when Txing you are denying service to others in a somewhat un-community friendly manner! Please change :wink: