In this activity, you will:
– Access to TPC Admin console.
– Register your device using DevEUI that you identified at Step6
Step 10 - Register device to TPC
In order to be able to receive and view the LoRaWAN® messages that you send with your device should be registered to TPC.
1
Please access to TPC from here
2
Please enter your TPC email and password to access admin functions.
3
Please click to ThingPark Admin console.
4
You now have access to the TPC control panel.
5
Please click to Devices at the left menu.
6
Please click to “Create” at the left menu.
7
Please select “Generic” at the left menu.
8
Please select LoRaWAN® 1.0.3 revA – class A at the dropdown list for Model field.
9
Please select CN779-787… at the dropdown* list for ISM Band field.
10
Give an arbitrary name to your EVB as Name field.
11
Enter the DevEUI of your device that had been viewed at STEP6.
In our case it is 34-38-34-35-34-38-34-35**
12
Please select Over-the-Air-Activation (OTAA) with local Join Server from the drop down list as Activation mode field.
13
Please enter 8 digit hex number at JoinEUI field. Please record that hex number which will be necessary at next step.
In our example, we used 00-00-00-00-00-00-00-00
14
Please enter 16 digit hex number at AppKey* field. Please record that hex number which will be necessary at next step.
In our example, we used:
34-38-34-35-65-37-92-15-00-00-00-00-00-00-00-00
14
Please select a connection from the drop down list as Connections** field. In our case, webHookForMKR1310 used.
15
Please select a connection from the drop down list as Connections** field. In our case, webHookForMKR1310 used.
16
Please click to CREATE button in order to complete provision of your Arduino MKR WAN 1301 device.
17
Now the device definition is created and INITIALIZATION means that TPC did not received any package from the device. So, it is quite normal.
In this step, you created the device definition for your Arduino MKR WAN 1310 device. Now, TPC is waiting for your LoRaWAN® messages to process and forward to the connection (i.e., webhook site) you defined.
*Please notice that AppKey should kept in a save environment and should not be share with anybody. As you can guess, AppKey shown above is not the real AppKey of the device definition.
** please notice that this DevEUI is not real , shown as an example.