APPEUI location in mLinux Conduit
- This topic has 3 replies, 3 voices, and was last updated 8 years ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: mLinux Model › APPEUI location in mLinux Conduit
Hello
I referred (http://www.multitech.net/developer/software/lora/getting-started-with-lora-conduit-mlinux/) to to set up the MultiTech Conduit, copied the configuration file to /var/config/lora/lora-network-server.config and modified the network name to a string say “test network”.
Now I would want to add an end device (mDot) manually (ABP). For that, per (http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/conduit-mlinux-lora-use-third-party-devices/) I need to add the APPEUI entry in the “lora-query -a” command. Per my understanding this would get derived from the network name “test network” in to a 16 bytes long hex number.
Where can I get this value in my mLinux conduit? Without the APPEUI the node cannot be added manually. I know it can be done via OTAA but my requirement is to use it via ABP.
thanks,
For an ABP connected device the AppEUI will not be used so it can be set to any value.
The easiest way to get AppEUI from a network name is on an mDot.
Set the network name
> AT+NI=1,test network
Read back the value to show the EUI
> AT+NI
How is AppEUI created and/or assigned? We can see one in the LoRa JSON record but not sure where it comes from. We tried converting it from hex to text but the result is indecipherable/seems meaningless.
When a network name is provided, the AppEUI is created by preforming crc64 to get a 64-bit EUI.
Otherwise the 64-bit value can be used directly in mDot and Conduit as AppEUI.