Third-Party device ABP join
- This topic has 2 replies, 2 voices, and was last updated 9 years ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: mLinux Model › Third-Party device ABP join
I try this third-party device abp join.
On device,
char DEVICE_EUI[] = "0102030405060708";
char DEVICE_ADDR[] = "05060708";
char NWK_SESSION_KEY[] = "01020304050607080910111213141516";
char APP_SESSION_KEY[] = "01010101010101010101010101010101";
On Log,
"network" : {
"eui" : "fb25bf0b4c6db07c",
"key" : "37a1ec8c179b82a93f68059a1be4c4eb",
"leasetime" : 0,
"name" : "YOUR-NETWORK-NAME",
"passphrase" : "YOUR-NETWORK-PASSPHRASE",
"public" : true
}
And i try
lora-query -a 00000001 A fb25bf0b4c6db07c 0102030405060708 01020304050607080910111213141516 01010101010101010101010101010101
When i check node list(lora-query -n), adding node is done.
But device doesn’t join the ABP.
Address on each side must match.
char DEVICE_ADDR[] = “05060708”;
lora-query -a 05060708 A …
thanks for help.
I try to modify lora config for matching each side.
So on Log,
"network" : {
"eui" : "1112131415161718",
"key" : "01010101010101010101010101010101",
"leasetime" : 0,
"public" : true
},
On device,
char DEVICE_EUI[] = "0102030405060708";
char DEVICE_ADDR[] = "05060708";
char NWK_SESSION_KEY[] = "01020304050607080910111213141516";
char APP_SESSION_KEY[] = "01010101010101010101010101010101";
and i try
lora-query -a 05060708 A 1112131415161718 0102030405060708 01020304050607080910111213141516 01010101010101010101010101010101
but still bevice cannot join abp.
On “http://www.multitech.net/developer/software/lora/lora-network-server/”,
--node-add (a) : add node
usage: --node-add <NODE-ADDR> [CLASS] <APP-EUI> <DEV-EUI> ([APP-KEY] | [NET-SKEY] [APP-SKEY])
Is the eui on Log same with ‘<APP-UEI>’?
And the key is [APP-SKEY]?
If Adding node is correct, is there next step to communicate with end-device, not just adding node?