Hm - maybe some more context re RFN2483 version and commanding would be helpful… Here’s the output from my TTN-OTAA-arduino-example based code when joining:
Model: RN2483
Version: 1.0.3
Sending: mac set deveui xxxxxxxxxxxxxx41
Sending: mac set adr on
Model: RN2483
Version: 1.0.3
Sending: mac set deveui xxxxxxxxxxxxxx41
Sending: mac set adr on
Sending: mac set deveui xxxxxxxxxxxxxx41
Sending: mac set appeui xxxxxxxxxxxxxxB4
Sending: mac set appkey xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx63
Sending: mac save
Sending: mac set ch drrange 1 0 6
Sending: mac set ch dcycle 0 799
Sending: mac set ch dcycle 1 799
Sending: mac set ch dcycle 2 799
Sending: mac set ch dcycle 3 799
Sending: mac set ch freq 3 867100000
Sending: mac set ch drrange 3 0 5
Sending: mac set ch status 3 on
Sending: mac set ch dcycle 4 799
Sending: mac set ch freq 4 867300000
Sending: mac set ch drrange 4 0 5
Sending: mac set ch status 4 on
Sending: mac set ch dcycle 5 799
Sending: mac set ch freq 5 867500000
Sending: mac set ch drrange 5 0 5
Sending: mac set ch status 5 on
Sending: mac set ch dcycle 6 799
Sending: mac set ch freq 6 867700000
Sending: mac set ch drrange 6 0 5
Sending: mac set ch status 6 on
Sending: mac set ch dcycle 7 799
Sending: mac set ch freq 7 867900000
Sending: mac set ch drrange 7 0 5
Sending: mac set ch status 7 on
Sending: mac set pwridx 1
Sending: mac set retx 7
Sending: mac set dr 5
Sending: mac join otaa
Join accepted. Status: 00000421
DevAddr: xxxxxx7B
Sending: mac set linkchk 14400
I’ve modified the TTN library to not send mac set rx2 3 869525000 to the RN2483 during startup, following some discussions and bug-reports. I understand that TTN does NOT actually send using DR3 in RX2 during OTAA (in contrast to later!), and my node did indeed not join with high SFs before I removed that command from the startup sequence. However I understand that after joining using OTAA, the rx2 settings should be commanded by the network, so I think this should not affect ADR, should it?