browse
Here is the important checklist to follow if you have trouble to connect LoraWAN equipment :
-
Verify AppEUI, DevEUI, and AppKey
The same AppEUI, DevEUI and AppKey stored in the end device should be provisioned onto the console.
In case of mistaken values, the activation of the device stays inoperative.
-
Repeat JOIN process
When an End Device communicates with the network server to perform the activation process, this process is called Join Procedure.
It may happen that something went wrong during the join-request message or join-accept message transmission to activate the end device.
If you see X in "Last Value" fields of your device in the console, restart the join procedure.
Join process is specific to each Lorawan end device supplier. This information is available in technical documentation.
-
Appropriate Class Type
All LoRaWAN end-devices support Class A, although Class C could be included on your device.
If your device use a different class than Class A, you may verify the class configured in your device, in Advanced Tab :
-
Check Codec used to communicate
Codec is use to decode the payload from the sensor. You may have the incorrect codec to decode the uplinks/downlinks from your device.
Please corroborate the codecID selected on the console with the Codec of your end-device.
-
Verify Frequency
LoRaWAN uses a proprietary spread spectrum modulation, so the frequency must match with your device. The correct frequency allows to transmit the data correctly in the network :
|
In case that you continue having problems to configured your LoraWAN end-device, please contact us : Wattsense Support |
Comments
0 comments
Please sign in to leave a comment.