Join Lora network via OTAA With RN2483
Home › Forums › Conduit: AEP Model › Join Lora network via OTAA With RN2483
- This topic has 9 replies, 3 voices, and was last updated 9 years ago by
Asier Galech.
-
AuthorPosts
-
April 25, 2016 at 10:51 am #12272
Asier Galech
ParticipantHi,
I’m using conduit gateway AEP with the RN2483 module from microchip. I’ve defined the NetworkEUI and Network key correctly in the gateway. Also, I’ve added the node with the command “node add [DevAddr] [Class] [DevEUI] [AppEUI] [AppKey]”.In RN2483 I’ve executed the following commands:
mac set devaddr 00000002 mac set deveui 0004a30b001b266a mac set appeui yyyyyyyyyyyyyyyy mac set appkey yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy radio set crc on mac save mac join otaa
RN2483 shows the message “denied”.
Upon looking at the log node-red, I’ve seen that the gateway responds “Send Join Accepted”:
Apr 25 16:06:46 mtcdt user.info lora-network-server: Parsing 1 rx packets Apr 25 16:06:46 mtcdt user.info lora-network-server: Received join request Apr 25 16:06:46 mtcdt user.info lora-network-server: Device found in DB, assigning address: 2 Apr 25 16:06:46 mtcdt user.info lora-network-server: Queue join response 33 bytes Apr 25 16:06:46 mtcdt user.info lora-network-server: Send Join Accept - EUI: 00:04:a3:0b:00:1b:26:6a ADDR: 00000002 Apr 25 16:06:46 mtcdt user.info lora-network-server: Schedule TX Time on air: 81 ms Apr 25 16:06:46 mtcdt user.info lora-network-server: Using RX window 2 : 00:00:00:02 Apr 25 16:06:48 mtcdt user.info lora-network-server: Frame transmitted to 00:00:00:02 via GW (00:80:00:00:00:00:aa:84 Chan LC3 127.0.0.1:51581) Seq# 2 Apr 25 16:06:48 mtcdt user.info lora-network-server: Band: 2 Time off air: 18100 ms Apr 25 16:06:48 mtcdt user.info lora-network-server: Transmit message 207 bytes
Thanks
AsierApril 26, 2016 at 9:35 am #12277Bryan Tran
ModeratorHi Asier,
Have you tried to activate it using manual mode ? Instruction is at the following link:
Thanks,
BT
April 26, 2016 at 10:47 am #12278Asier Galech
ParticipantHi Bryan,
Yes, I’ve followed these instructions. With the Join AEP, it worked correctly but with Join OTAA it still returns “denied”
Thanks
Asier
April 26, 2016 at 3:05 pm #12279Bryan Tran
ModeratorAsier,
1. Do you have ‘public’ mode enable on the Conduit ? Also, can you ssh into the Conduit and issue the following command:
/opt/lora/lora-network-server –version
If it is not at 1.0.8, please upgrade them.
Please, make sure you have download a correct file for your model.
2. What is the value return when you issue the command – ‘radio get freq’
3. Also, if you web into the device and go to Lora Network server -> Network server log -> Select TRACE. Click on ‘Submit’ button. Then ssh into the Conduit and issue the following command:
tail -f /var/log/messages | grep lora
This will get you more debug messages.
Thank you,
BT
April 27, 2016 at 3:23 am #12282Asier Galech
ParticipantHi,
1. Public mode is enabled. The version wasn’t 1.0.8. I upgraded it but the Join OTAA still return “denied”.
Upon looking at the log lora-network, I’ve seen that the gateway responds “Send Join Accepted”:
8:2:12:267|TRACE| MQTT message: lora/00-04-a3-0b-00-1b-26-6a/packet_recv 8:2:12:271|TRACE| SQL query = SELECT address FROM nodes WHERE deveui = "0004a30b001b266a"; 8:2:12:273|TRACE| SQL query = UPDATE nodes SET jointime = "2016-04-27T08:02:12Z" WHERE address = "00000002 " 8:2:12:277|TRACE| SQL query = UPDATE packets SET port = 123, seqno = 0, gateway = "008000000000aa84", time = "2016-04-27T08:02:12Z", microseconds = 233807, rssi = -25, channel = 2, lsnr_cB = 68, spread = 12, modu lationbandwidth = 125, data = "4e" WHERE node = "00000002" 8:2:12:281|TRACE| SQL query = UPDATE nodes SET lastuppacketid = 1, lastmessagems = 1234467 WHERE address = "00000002"; 8:2:12:284|TRACE| SQL query = UPDATE gateways SET lastuppacketid = 1 WHERE address = "008000000000aa84"; 8:2:12:288|DEBUG| getTimeOnAirMs dr: 12 bw: 0 pl: 8 sz: 32 toa: 1810 8:2:12:288|INFO| Send Join Accept - EUI: 00-04-a3-0b-00-1b-26-6a ADDR: 00000002 8:2:12:289|INFO| Schedule TX Time on air: 1820 ms 8:2:12:289|DEBUG| BestGatewayChannel::scheduleAt 565986 1820 868500000 8:2:12:289|DEBUG| 0 : 00:80:00:00:00:00:aa:84 8:2:12:290|DEBUG| now: 561288 8:2:12:290|DEBUG| time: 565986 duration: 1820 freq: 868500000 8:2:12:291|DEBUG| returning 00:80:00:00:00:00:aa:84 8:2:12:291|DEBUG| Scheduling for Rx Window 1 00:00:00:02 8:2:12:291|DEBUG| Send MQTT message 8:2:12:292|DEBUG| UDP message: lora/00-04-a3-0b-00-1b-26-6a/joined 8:2:12:292|DEBUG| UDP port: 1784 8:2:12:294|WARNING| Recv'd frame failed CRC check 8:2:12:294|WARNING| Recv'd frame failed CRC check 8:2:12:294|WARNING| Recv'd frame failed CRC check 8:2:12:295|DEBUG| Mosquitto command received 'packet_recv' 8:2:12:296|TRACE| Unknown command 'packet_recv 8:2:12:333|TRACE| Published message: 6 8:2:12:372|TRACE| MQTT message: lora/00-04-a3-0b-00-1b-26-6a/joined 8:2:12:373|TRACE| SQL query = SELECT address FROM nodes WHERE deveui = "0004a30b001b266a"; 8:2:12:374|DEBUG| Mosquitto command received 'joined' 8:2:12:375|TRACE| Unknown command 'joined 8:2:13:243|TRACE| Parse downstream message 12 bytes 8:2:13:244|TRACE| Gateway 00:80:00:00:00:00:aa:84 seen IP address 127.0.0.1:37369 8:2:16:996|DEBUG| is frame ready? 8:2:16:997|DEBUG| App Queue Length: 1 8:2:16:997|DEBUG| BestGateway: 8000000000aa84 8:2:16:997|DEBUG| Start 8:2:16:998|INFO| Frame transmitted to 00:00:00:02 via GW (00:80:00:00:00:00:aa:84 Chan LC3 127.0.0.1:37369 ) Seq# 0 8:2:16:998|TRACE| SQL query = UPDATE nodes SET lastdownmsgseqno = 0 WHERE address = "00000002"; 8:2:17:1|DEBUG| App Data Queue: 1 front size: 33 available: 242 8:2:17:2|DEBUG| check if front is join request 33 bytes 8:2:17:4|DEBUG| Start 8:2:17:5|TRACE| App Data Queue - Join Popped 8:2:17:6|DEBUG| Transmitted Frame data ================================ 000 20 d9 60 4d 35 c2 06 6a 008 58 3d a4 bd 9b 58 18 24 010 4e c1 59 33 f9 94 f7 c4 018 57 70 87 29 d1 33 0f d7 020 80 8:2:17:7|DEBUG| rx1Offset: 0 rx1Datarate: 12 8:2:17:8|DEBUG| Use JoinResponse Window Time 8:2:17:21|DEBUG| JSON tx: { "txpk" : { "codr" : "4/5", "data" : "INlgTTXCBmpYPaS9m1gYJE7BWTP5lPfEV3CHKdEzD9eA", "datr" : "SF12BW125", "freq" : 868.5, "ipol" : true, "modu" : "LORA", "ncrc" : false, "powe" : 11, "rfch" : 0, "size" : 33, "tmst" : 517418140 } } 8:2:17:23|DEBUG| Band: 1 DutyCycle: 416142 8:2:17:23|DEBUG| getTimeOnAirMs dr: 12 bw: 0 pl: 8 sz: 33 toa: 1810 8:2:17:24|INFO| Band: 1 Time off air: 181000 ms 8:2:17:24|INFO| Transmit UDP message to Gateway 195 bytes 8:2:17:25|DEBUG| Send on socket 199 bytes, payload len: 195 8:2:17:42|DEBUG| Set node active: 0 8:2:17:45|DEBUG| Send MQTT message 8:2:17:45|DEBUG| UDP message: lora/00-04-a3-0b-00-1b-26-6a/packet_sent {"codr":"4/5","data":"INlgTTXCBmpYP aS9m1gYJE7BWTP5lPfEV3CHKdEzD9eA","datr":"SF12BW125","freq":868.5,"ipol":true,"modu":"LORA","ncrc":false,"p owe":11,"rfch":0,"size":33,"tmst":517418140} 8:2:17:46|DEBUG| UDP port: 1784
2. The command ‘radio get freq’ returns the value ‘869500000’
Thanks
AsierApril 27, 2016 at 9:43 am #12291Bryan Tran
ModeratorHi Asier,
Could you please issue the following command to the RN2483:
radio set freq 868500000
And see if it helps ?
Thank you,
BT
April 27, 2016 at 10:30 am #12292Asier Galech
ParticipantHi Bryam,
The same problem in applying the command.
Thanks
Asier
April 27, 2016 at 10:52 am #12293Bryan Tran
ModeratorAsier,
Can you check with Microchip to see if they have any latest firmware and see if it helps ? I am using the following firmware version:
sys factoryRESET <–I did a factoryRESET
RN2483 0.9.6rc1 Jul 20 2015 10:55:21
radio get freq
868100000
mac get appeui
0000000000000000
mac set deveui
invalid_param
mac get deveui
0000000000000000
mac set deveui 0204A30B001A53B2
ok
mac get deveui
0204A30B001A53B2
mac set appeui 3bf9679dd12993ae <–YOUR-NETWORK-NAME3
ok
mac get appeui
3BF9679DD12993AE
mac set appkey e9b99fe1c9ba8d3efa562eb1ac02c331 <–YOUR-NETWORK-PASSPHRASE3
ok
mac get appkey
invalid_param
radio set crc on
ok
mac save
ok
radio get freq
868100000 <–May be try with 868100000 and see if it helps ?
mac join otaa
ok
accepted
mac join otaa
ok
accepted
mac join otaa
ok
accepted
and it is working fine for me.
Thank you,
BT
April 28, 2016 at 11:41 am #12323Lawrence Griffiths
ParticipantYou have to be on latest RN2483 firmware to get OTAA.
I have tested with customer who is using OTAA.
We have also tested downlink to RN2483 all workin.May 2, 2016 at 2:55 am #12363Asier Galech
ParticipantHi,
With the latest RN2483 firmware, OTAA worked correctly.
Thanks
Asier
-
AuthorPosts
- You must be logged in to reply to this topic.