RA-08h join problem

I’ve been trying to connect RA-08H module to TTN, TTS, …, so far unsuccessfully. I set module up correctly I think, AT commands return data that is correctly set on TTN or TTS, but module won’t join at all.

Below I attach log from serial, when trying to join.

I have a way to check local LoRaWAN gateway if it receives any signal at all from device with DEVEUI that my device is set with, but there is no signal received at all.

Tried firmware v1.3.4 and 1.4.0 that is on manufacuter’s web page. Same result. Frequency is set correctly for EU.

Does anyone have any additional suggestions what to try to make this work?

Thank you.

ASR6601:~# TX on freq 868500000 Hz at DR 5

Start to Join, nb_trials:1
RX on freq 868500000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

TX on freq 868100000 Hz at DR 5

Start to Join, nb_trials:1
RX on freq 868100000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

TX on freq 868500000 Hz at DR 5

Start to Join, nb_trials:1
RX on freq 868500000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

TX on freq 868100000 Hz at DR 2

Start to Join, nb_trials:1
RX on freq 868100000 Hz at DR 2

RX on freq 869525000 Hz at DR 0

Start to Join, nb_trials:1
TX on freq 868100000 Hz at DR 5

RX on freq 868100000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

TX on freq 868300000 Hz at DR 5

Start to Join, nb_trials:1
RX on freq 868300000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

TX on freq 868100000 Hz at DR 5

Start to Join, nb_trials:1
RX on freq 868100000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

TX on freq 868100000 Hz at DR 5

Start to Join, nb_trials:1
RX on freq 868100000 Hz at DR 5

RX on freq 869525000 Hz at DR 0

+CJOIN:FAIL

You use SF12 - DR 0 - for second RX window? Default is SF9 - DR3

SF12 for join RX2 is correct. For data the second windows spreading factor will be set by the join accept message.

What is the distance between the device and the gateway?

Sorry for the wrong info, so this setting is only for the uplinks, not for the join?
ttn-rx2-dr

Correct, Rx2 @ SF12 for JoinAccept is mandatory per spec. Rx2 for downlinks is configurable - Chirpstack allows setting a specific datarate even, TTS offers just SF12 or SF9 for uniformity.

1 Like

You haven’t provided wrong info, but you haven’t answered the really important question that the lead expert on the forum asked you, the one that solves these sorts of issues week in week out:

Search the forum on ‘range’ and you will see that it’s not an exact science.

The channel plan is best left to the recommended one but as described above, the join uses slightly different settings. This is normal.

Check your gateway whether it is EU868 or not.
ttn-rx2-dr

863-870Mhz (SF9 for RX2)

I am not the OP. :wink:

It is. Tried all EU versions too.

Range is not far, 500m air line distance max.

Direct line of sight or are there obstacles in the way.

Well there are some buildings, but not many, I live in a relatively small town where highest building is local castle :slight_smile:
Wouldn’t really say there are any significant obstacles in its way.

Can you see the gateway location from where the device is? If not could you test the device closer to the gateway? Half a kilometer can be out of range if there are obstacles in the way.

Also check topology as even a small rise in intermediate ground level, which may not be ovious when viewed at ground level, can present a huge mass of earth into the Freznel zone or even mask LOS completely killing any signal…local height of node and gw will impact that ofcourse.

OTAA Join request is on SF10. You may need to get close to LoRaWAN Gateway than expectation unless you get LOS. Increase your antenna length of your node might help. I used to hack my node to join request at SF12 with a 19 cm rubber antenna . My gateway also 19 cm. antenna length, installed 3 meters above the ground. I succussed join within 1 km radius.