OTAA denied using RN2483 + iC880A&RPi

End Devices (Nodes)
1

We’re trying to set up a new gateway in Varsseveld (Netherlands). The hardware used for the gateway is a RaspberryPi 3 with a ic880a concentrator board. I’m experience some problem when I try to connect a node (RN2483 dev kit from microchop) using Over the air activation (OTAA).

The gateway is configured using the new backend, I think the problem isn’t here. We’re using the following local_conf.json file.

{
  "gateway_conf": {
    "gateway_ID": "B827EBFFFECF29A7",
    "servers": [{
      "server_address": "router.eu.thethings.network",
      "serv_port_up": 1700,
      "serv_port_down": 1701,
      "serv_enabled": true
    }],
    "ref_latitude": 51.941649,
    "ref_longitude": 6.481048,
    "ref_altitude": 0,
    "contact_email": "b.knol@singa-bv.nl",
    "description": "ttn-ic880a"
  }
}

First I got my device unique identifier from the RN2483 module:

mac get deveui
0004A30B001B5FD7
sys get hweui
0004A30B001B5FD7

Then I created a application and registered a new device in it:

ttnctl.exe devices register 0004A30B001B5FD7
  INFO Generating random AppKey...
  INFO Registered device                        AppKey=2634943C13D15FE0A625F776A5F628FD DevEUI=0004A30B001B5FD7

Set all required parameters in the RN2384 module to perform a OTAA:

sys factoryRESET
RN2483 1.0.1 Dec 15 2015 09:38:09
mac set appkey 2634943C13D15FE0A625F776A5F628FD
ok
mac set appeui 70B3D57EDxxxxxxx
ok
mac save
ok

Join the network:

mac join otaa
ok
denied

The module attempted to join the network, but it was denied. Has anyone seen any issues like that? Or am I missing something? Any help is welcome!

My firmware version is ok according to this topic: https://www.thethingsnetwork.org/forum/t/otaa-with-rn2483-using-new-backend/1986

Thanks in advance.

Bart

2

Hi Bart
I think the problem lays in your Router config. “serv_port_down” is in the new Backend also 1700.
I have the same Gateway Setup with the same problem. After changing the portnumber otaa was OK. http://staging.thethingsnetwork.org/wiki/Backend/Connect/Gateway

Werner

1 Like
3

@wernern That sounds like a reasonable solution! I’ll try this monday when i’m back in the office where the gateway is located. Thanks so far!

Bart

4

Thanks @wernern, changing the serv_port_down did the trick!

Bart

5

Just for future readers: note that OTAA is only supported on staging, not on the old Croft environment. So make sure the gateway is using the staging environment.

1 Like
6

Attemptin the same thing. When I do

mac join otaa

I get

keys_not_init

What does that mean?

EDIT:

My code:

sendCmd("sys factoryRESET");
  sendCmd("mac set appkey 01020304050607080102030blablabla"); //same as in ttncl
  sendCmd("mac set appeui 70B3D57ED0000bla"); //same as ttncl

  
  sendCmd("mac save");
  sendCmd("mac join otaa");
7

mac set deveui … is missing

8

Thanks. Added it, now it gives ok.

EDIT:

But it gives me not_joined now

RN2483 0.9.5 Mar 24 2015 14:15:33
sys get hweui
0004A30B001B2bla
mac set deveui 0004A30B001B2bla
ok
mac set appkey 5BFB7D1B0B9287E0065986F7DCF53bla
ok
mac set appeui 70B3D57ED0000bla
ok
mac set adr off
ok
mac set rx2 3 869525bla
ok
mac save
ok
mac join otaa
ok
**mac tx uncnf 1 7B39387D**

** not_joined**
Done sending
denied
Done receiving
GOING IDLE

From datasheet:

not_joined: If network is not joined

But it says:

mac join otaa
ok

9

The ‘ok’ is just a confirmation that the ‘join’ operation is executed by the tranciever. After a few seconds (3-10) you get a ‘accepted’ when youre node succesfully joined the network or ‘denied’ when the join operation failed.

Maybe you could try to send a message by personal activation (ABP) using a AppSKey (application session key) and NwkSKey (network session key)?

10

Hello, i also have a problem with OTAA confirmation, and i dont know the right procedure for otaa
“gateway_ID”: “AA555A0000000000”,
/* Devices /
“gps”: true,
“beacon”: false,
“monitor”: false,
“upstream”: true,
“downstream”: true,
“ghoststream”: false,
“radiostream”: true,
“statusstream”: true,
/ node server /
“server_address”: “192.168.1.6”,
“serv_port_up”: 1235,
“serv_port_down”: 1235,
/ node servers for poly packet server (max 4) */
“servers”:
[ { “server_address”: “192.168.1.6”,
“serv_port_up”: 1235,
“serv_port_down”: 1235,
“serv_enabled”: true },
{ “server_address”: “iot.semtech.com”,
“serv_port_up”: 1680,
“serv_port_down”: 1680,
“serv_enabled”: true } ],

11

Hi guys.
I just read this thread because I want to use the OTAA mechanism with the RN2483. Did you manage to figure out how to do that?

12

I believe the OTAA join sequence for the TTN is buggy for the rn2483 with a firmware smaller then 1.0. (Yours is 0.9.5).

Maybe @jpmeijers can confirm this?

13

I am trying to connect OTAA with firmware 1.0.1:

print("mac set deveui "+devEUI+"\r\n");
print("mac set appeui "+appEUI+"\r\n");
print("mac set appkey "+appKey+"\r\n");
print("mac join otaa\r\n");

and the gateway I am trying to connect to is based on a Rpi+ic880a (iMST). local_conf.json file is:

"gateway_conf": 
{
  "gateway_ID": "XXXXXXXXXXXXXXX",
  "servers": [ { "server_address": "router.eu.thethings.network", 
                "serv_port_up": 1700,
                "serv_port_down": 1700, 
                "serv_enabled": true } ],
                "ref_latitude": XX.535859,
                "ref_longitude": XX.595651,
                "ref_altitude": 460,
                "contact_email": "jXXXXXXy@XXXXXXX.com",
                "description": "ttn-ic880a"
 }

But the module always returns denied a few seconds after mac join otaa. Any idea?

14

Hi All,

I’m experiencing the same issue. I have a RN2484 (fw version 1.0.1 Dec 15 2015) connecting to an iC880A-SPi with a RPi connecting to TTN production.

If I start up the RN module, set the app eui/keys etc and join the network, it is successful. I then TX 2 bytes of data every 60 seconds. The first 2-3 packets are TX’d OK. Then I get a “busy” and soon after that “no_free_ch”.

If I then restart the RN2483, the join results in a “denied” every time. Is there some way to determine why the module is denied?

15

I created my own LoRa network (Kerlink gateway, loraserver, …) and I had no problems with it. It was always joining it without problems. Now, I need to use the end node on the TTN network.

I have set the deveui, appeui and appkey and after I do ‘mac join otaa’ I’m always getting back ‘denied’.
I rechecked the entered values and they are 100% the same as defined in the TTN Console.
Is there anything else, that needs to be set in the RN2483 module in order to get it joined to the TTN network?

Was anyone able to get RN2483 to work with the TTN network?

I have no problems with using TTN network on my other end node device (B-L-072Z from STM).

16

You can run sys get ver on your RN2483. If it returns a version older than RN2483 1.0.1 Dec 15 2015 09:38:09, it’s likely that this is the problem.

17

I got no problem.

I even just restarted my RN2483 device just now to be sure. RN2483 has firmware V1.0.1

1 Like