Join Lora network via OTAA

[Kyle Zhang]

Hi,

I’m using conduit gateway with RN2483 module from microchip. From the protocol specification, the application eui and device eui should be specified in the join-request packet. Where can I find the application eui from the gateway?

Thanks,

[Jason Reiss]

The eui can be configured in /var/config/lora/lora-network-server.conf on the Conduit.

Refer to the following page for configuration options:
http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/conduit-mlinux-advance-lora-configuration/

[Kyle Zhang]

Hi,

Here is my lora-network-server.conf configuration:

{
	"udp": {"appPortUp": 1784, "appPortDown": 1786, "downstreamPort": 1782, "upstreamPort": 1780}, 
	"log": {"syslog": true, "path": "", "console": true, "level": 100}, 
	"whitelist": {"enabled": false, "devices": []}, 
	"addressRange": {"start": "00:00:00:01", "end": "FF:FF:FF:FE"}, 
	"db": "/var/run/lora/lora-net-server.db", 
	"mqtt": {"host": "127.0.0.1", "enabled": true, "port": 1883}, 
	"lora": {"rx1DatarateOffset": 0, "frequencyBand": 868, "nodeQueueSize": 16, "enabled": true, "rx2Datarate": 12, "frequencySubBand": 1, "maxTxPower": 26, "frequencyEU": 869500000}, 
	"network": {"key": "", "leasetime": 86400, "name": "GATEWAY1", "passphrase": "lorapass", "eui": "1122334455667788", "public": true},
	"msg": {"chan": 5, "datr": "SF7BW125", "freq": "868", "lsnr": "85", "modu": "LORA", "eui": "00:11:22:33:44:55:66:77", "payload": "hi rn2483"}
}

I set the appeui as “1122334455667788” and deveui as “0011223344556677” and the otaa join is always denied. What is wrong with this setting?

Is this network eui means appeui as mentioned in the protocol specification?

Thanks,

• This reply was modified 8 years, 6 months ago by Kyle Zhang.
• This reply was modified 8 years, 6 months ago by Kyle Zhang.

[Jason Reiss]

For OTAA you need to set the following info:

“network” : { “eui”: “1122334455667788”, “key”: “” }

You can remove the “name” and “passphrase” settings, they are there to generate network eui and key from a string. If set you can see the generated eui and key in the log on start of the network server.

On the device the network eui setting is AppEUI and network key is AppKey.

I the above json the network key setting is missing. This needs to match the AppKey on the device.

[Kyle Zhang]

Hi,
Thanks for your info.

Here is my configuration file:

{"udp": {"appPortUp": 1784, "appPortDown": 1786, "downstreamPort": 1782, "upstreamPort": 1780}, 
 "log": {"syslog": true, "path": "", "console": true, "level": 100}, 
 "whitelist": {"enabled": false, "devices": []}, 
 "addressRange": {"start": "00:00:00:01", "end": "FF:FF:FF:FE"}, 
 "db": "/var/run/lora/lora-net-server.db", 
 "mqtt": {"host": "127.0.0.1", "enabled": true, "port": 1883}, 
 "lora": {"rx1DatarateOffset": 0, "frequencyBand": 868, "nodeQueueSize": 16, "enabled": true, "rx2Datarate": 12, "frequencySubBand": 1, "maxTxPower": 26, "frequencyEU": 869500000}, 
 "network": {"key": "00-11-22-33-44-55-66-77-88-99-AA-BB-CC-DD-EE-FF", "leasetime": 86400, "eui": "1122334455667788", "public": true}}

And I login to gateway via ssh. There are two commands run in different console
1. tail -f /var/log/lora-pkt-fwd.log And I get:
##### 2015-10-26 13:53:27 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 1
# CRC_OK: 0.00%, CRC_FAIL: lgw_receive:1428: FIFO content: Pkts: 1 62 0 Stat: 5 Size: 17
lgw_receive:1443: [0 17]
Note: LoRa packet
lgw_send:1696: DEBUG: Tx pow_index 9, rf_power 14
59.6.66.dc.cf.fa.17.9.0.97.21.10.0.8.0.0.20.7c.90.d3.d6.40.bc.aa.99.fd.96.86.cb.96.cf.23.bb.68.88.33.65.1d.ea.9f.40.17.c.5e.4f.a7.4a.3a.d0.end
I seems already received and sent a reply back.
2. mosquitto_sub -t lora/+/+ -v And I get:
lora/00:04:a3:0b:00:1b:95:19/joined (null)

But still the RN2483 otaa join request get the result denied

What’s the format of the lgw_send message? What could be the error?

Thanks,

[Tom Decavele]

Hi,

did you try ‘mac join abp’ instead ?

My LoRa server crashes when sending a unconf message from the RN2483 …
Regards, Tom.

[Jason Reiss]

Tom,

Could you open a support case on support.multitech.com regarding the lora server crash and share your mote configuration to try to reproduce the error.
Network Address and keys used for ABP and commands used to enter mote into database?

Thanks,

Jason

[Frederik Vannieuwenborg]

Any update on this, I’m getting the same denied error on the RN2483?

Regards,
Frederik

[Jason Reiss]

I found this topic on the openlora forum regarding the RN2483.

https://openlora.com/forum/viewtopic.php?f=5&t=6

[Frederik Vannieuwenborg]

Jason, thx for the link.

They got it working with Loriot but not with the “native” lora server.

Regards,
Frederik

[Grzegorz Rudy]

You save wrong your conf file. Try:
“eui”: “00:11:22:33:44:55:66:77”,
“key”: “00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF”
I works

[wojtek t]

I have similar problem but with RN2903. ABP join works no problem but OTAA always times out. Basically, conduit indicates that successfully accepted join request, but RN2903 shows “denied”.

[Bryan Tran]

Hi Wojtek,

Below is what Microchip recommended:

Please ensure the Channels you are not using on the RN2903 are disabled using the “mac ch status <ch#> off” command. This should make sure the module does not try to communicate on one of those channels. (If you are using a full 64 channel solution; this should not be necessary.

Other off hand things to check would be the receive windows.

Thanks,

BT

[wojtek t]

Thanks Bryan,
This makes perfect sense, I will try tomorrow, however I already tried more than 8 times. Statistically, I should get lucky couple of times already…
I will report back.
BTW: my colleague has no problem with RN2983 which makes perfect sense…
WT

[wojtek t]

Confirmed, system with only one sub-band enabled works smoothly and as expected.
Thanks
WT

[Jose Navarro]

I can see that RN2903 says it has channels 0-71, leaving on 0-7 and turning off 8-71 will prevent data to be sent on channels where the Multiconnect conduit cannot listen to?

Regards
-Jose

[Author]

Posts