Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Connecting a SAM R34 SiP/SAM R34 Module LoRaWAN® End Device to a LoRaWAN Network Server
Two Methods for End-devices to Join a LoRaWAN® Network
Over-The-Air Activation (OTAA)
End-device transmits a Join Request to the application server containing:
Globally unique end-device identifier (DevEUI)
Join server Extended Unique Identifier (JoinEUI)/Application identifier (AppEUI), and
Authentication with Application key (AppKey)
End-device receives Join Accept from the application server
End-device authenticates Join Accept
End-device decrypts Join Accept
End-device extracts and stores Device Address (DevAddr)
End-device derives security keys:
Network Session Key (NwkSKey)
Application Session Key (AppSKey)
Activation by Personalization (ABP)
The following information is configured at production time:
Device Address (DevAddr)
Network Session Key (NwkSKey)
Application Session Key (AppSKey)
No over-the-air handshaking
Device is ready to communicate on the network without any additional procedure
In production, we recommend you use OTAA. OTAA is more reliable since the activation will be confirmed and more secure. Session keys are agreed upon with every activation. ABP can be used when doing demos or workshops.
If you need to work with Microchip Support staff directly, you can submit a technical support case. Keep in mind that many questions can be answered through our self-help resources, so this may not be your speediest option.
