How to connect a Microchip LoRa modem to a Multitech mLinux conduit
Tagged: activation, non-multitech modem, personalization
- This topic has 9 replies, 3 voices, and was last updated 7 years, 12 months ago by Jason Reiss.
-
AuthorPosts
-
April 19, 2016 at 10:19 am #12191Louis CroisezParticipant
Hello,
I am currently playing with connecting some Mdots with my LoRa Multitech gateway, and all is coherent.
I own also a Microchip LoRa modem, driven by an Arduino-like board.
In this Arduino sketch, I must enter a network key and an application key, which I don’t know.
Could you give me a way to know these keys?
I tried to do this on the Conduit:$ lora-query --node-config xx:xx:xx:xx
which returns me following parameters:
Net Addr
Dev EUI
Class
App EUI
AppKey
Net Session Key
Data Session KeyThe “AppKey” seems to be always the same, so I suppose this is the application key that I need to know. But The “Net Session Key” parameter is changing on each JOIN of the Mdot.
Where could I find the Network key that I need ?April 19, 2016 at 10:26 am #12192Jason ReissKeymasterIt should be the AppEUI and AppKey settings from an already joined mote.
AppEUI – NetworkEUI
AppKey – NetworkKeyYou can also get them from the network server process
> nc -u localhost 6677
configThese will be generated from Network Name and Passphrase on startup.
Otherwise these values could be provided in hex format if desired.See “network” { “eui”: “”, “key”: “” }
April 20, 2016 at 3:42 am #12210Louis CroisezParticipantI am reading chapter 6.3 from LoRaWAN standards, and I try to understand it well.
As concern my LoRa+Arduino case, I must enter two 512bit keys. I suppose that it is in fact the NwkSKey and the AppSKey, two sessions keys which are the result of the {DevEUI/AppEUI/AppKey} personalization.This means that I have to do something on my gateway to produce a new couple of {NwkSKey/AppSKey}, that should “register”, or “activate” my new device.
I must do this by hand because the Microchip device does not share the same API like other Multitech systems.
But the question is: how can I activate my new device by hand?
April 20, 2016 at 3:44 am #12211Louis CroisezParticipantsorry, my mistake: do not read 512bit keys, but 128bit keys instead.
April 20, 2016 at 9:32 am #12214Bryan TranModeratorHi Louis,
Have you seen this link – http://www.multitech.net/developer/forums/topic/join-issue-with-microchip-lora-radio-rn2903/
Thank you,
BT
April 20, 2016 at 9:53 am #12215Louis CroisezParticipantHello Bryan,
thank you very much for answering me.I just read the post you mentioned.
Just a last question:
is it absolutely required to configure network[“public”]=true, for RN2483 module to join and emit successfully?April 20, 2016 at 11:40 am #12221Bryan TranModeratorHi Louis,
You do need to set it to true.
Thank you,
BT
May 10, 2016 at 10:18 am #12444Louis CroisezParticipantI wonder what is the actual impact of this network[“public”]=true parameter?
Does this mean that the LoRa communication is not fully encrypted?
What is changed in the LoRa communication when putting this param to true?May 10, 2016 at 10:34 am #12445Bryan TranModeratorMay 10, 2016 at 10:36 am #12446Jason ReissKeymasterThe public network setting is documented on these pages.
http://www.multitech.net/developer/software/lora/introduction-to-lora/
-
AuthorPosts
- You must be logged in to reply to this topic.