Join Microchip RN2483 using ABP / Private

[Matthew Way]

I’m trying to connect some Microchip RN2483 LoRa modules using ABP / Private.

Are there any instructions on how to achieve this ?

[Jason Reiss]

http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/conduit-mlinux-lora-use-third-party-devices/

[Matthew Way]

I’m following the example as per your link.

I add the node manually;
node add 00000006 0011223344556677 0004A30B001A655F 2b7e151628aed2a6abf7158809cf4f3c 2b7e151628aed2a6abf7158809cf4f3c

I get the following error in the log file;

2:28:9:908|INFO| Parsing 1 rx packets
2:28:9:909|DEBUG| Received packet
================================
000   80 06 00 00 00 00 01 00
008   01 35 5b c2 e1 0e 20

2:28:9:910|DEBUG| Rx on 868100000, rssi: -59 snr: 72
2:28:9:910|DEBUG| Received frame: type: Confirmed Up
2:28:9:911|DEBUG| Packet received from Node 00:00:00:06  GW 00:80:00:00:00:00:a8:a6  (127.0.0.1)  Seq# 1
2:28:9:911|DEBUG| Set node active: 1
2:28:9:911|DEBUG| Expecting packet SeqNo: 00000001
2:28:9:911|DEBUG| Check for dup: 0001 == 0000
2:28:9:912|TRACE| Checking 00000001 sequence number
2:28:9:912|TRACE| AUTH KEY: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c
2:28:9:912|DEBUG| MIC Check: 052ec928 == c2e10e20
2:28:9:913|TRACE| Checking 00010001 sequence number
2:28:9:913|TRACE| AUTH KEY: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c
2:28:9:914|DEBUG| MIC Check: f4f4f333 == c2e10e20
2:28:9:914|TRACE| Checking 00020001 sequence number
2:28:9:914|TRACE| AUTH KEY: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c
2:28:9:915|DEBUG| MIC Check: 32fe3d5b == c2e10e20
2:28:9:915|TRACE| Checking 00030001 sequence number
2:28:9:915|TRACE| AUTH KEY: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c
2:28:9:916|DEBUG| MIC Check: a4309bd6 == c2e10e20
2:28:9:916|TRACE| Checking 00040001 sequence number
2:28:9:916|TRACE| AUTH KEY: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c
2:28:9:917|DEBUG| MIC Check: 022ce04f == c2e10e20
2:28:9:917|INFO| SeqNo: 00040001 PrevSeqNo: 00000000 Duplicate: no

2:28:9:917|INFO| Addr: 00:00:00:06 MIC Check: failed
2:28:9:918|WARNING| Dropping packet, Addr: 00:00:00:06 Duplicate: no
root@mtcdt:/var/log# 

What is a MIC check ?

[Matthew Way]

Here are the commands I’ve issued on the RN2483

sys reset
RN2483 0.9.5 Mar 24 2015 14:15:33
mac get band
868
mac set devaddr 00000006
ok
sys get hweui
0004A30B001A655F
mac set deveui 0004A30B001A655F
ok
mac set appeui 0011223344556677
ok
mac set nwkskey 1029384756AFBECD5647382910DACFEB
ok
mac set appskey 1029384756AFBECD5647382910DACFEB
ok
mac save
ok
mac join abp
ok
accepted
mac get status
0001
mac tx cnf 1 4142
ok

[Jason Reiss]

The session keys need to match on both sides.
The nwkskey is used to compute the MIC (message integrity check)
The appskey is used to encrypt the data

[Matthew Way]

Okay, I have it working now.

for reference I changed my node add command as follows.

node add 00000006 0011223344556677 0004A30B001A655F 1029384756AFBECD5647382910DACFEB 1029384756AFBECD5647382910DACFEB

Thanks for your help.

[abdul hakeem]

Hi Matthew ,

Please can you share the sample source ,which you used ?

Thanks in Advance .

[abdul hakeem]

Hi Matthew ,

Please can you share the sample source code ,which you used ?

Thanks in Advance .

[abdul hakeem]

Hi matthew ,

Please can you tell me what is the appeui and how you chooses (0011223344556677)
this id only and same what is nwskey,appkeys..on what based we can configure hexa numbers.

Thanks in Advance.

[Jason Reiss]

In the case of a private network the appeui can be chosen at random.
If you are using a public network or provider then the appeui may be assigned by them.

This forum also has lots of lora specific info
http://openlora.com/forum/viewtopic.php?f=15&t=796&p=1376&hilit=session+keys#p1376

[Matthew Way]

As Jason points out the appeui can be any number.
I only used 0011223344556677 because it was easy to count the number of digits.
In a production environment I would be more creative.

[abdul hakeem]

Thanks Matthew for you quick rply,

I have another question related to transmission,while transmitting the data from RN-2483 By using “mac tx uncnf 1 “(in while loop using ) It was successfully transmitiing “3” times i.e 3 times i am getting “mac_tx_ok” successfully when i am going transmit the data “4” time onward’s i am getting “no_free_ch”…Please tell me how can i resolve this problem….

Thanks in Advance….

[Jason Reiss]

The 868 band has transmission limited with duty-cycles set in frequency bands. You must wait for a channel to be free after the required time-off-air after transmission according to the ETSI regulations EN 300 220-2 v2.4.1

[mdot_dev aa]

I know this is an old thread but I just came across this problem right now.

Until now I was using a conduit AEP and a mdot unit. both worked like a charm.

NOw I have been asked to make the AEP unit to work with a microchip nr2483 unit. So I changed the network parameters to public, and following the values that Matthew Way posted a while ago, I was able to make both to work. Only I have one problem, I need to add the microchip unit though “nc -u localhost 6677” before AEP unit can receive any data.

How could I avoid to assign a devaddr. In fact, in a big network (one where I could add new devices every day) I can’t program every unit with a different devaddr in code. It is a tedious work to do that. I would want to use its internal mac (hweui) instead. But I tried to put it as devaddr and I got an error.

Is it possible to avoid having to add it to the conduit nc list? Could conduit just receive any frame which has the same appeui, nwkskey and appskey?

[Author]

Posts