LoRaWAN Network Server setup
Figure :
I
mport devices
A new window is displayed in order to import a CSV
fi
le with all devices to be imported:
Figure :
I
mport CSV
fi
le
Regarding the CSV
fi
le format, you must start from the exported CSV
fi
le from the SCM. Please refer to
section for further information on how to export this CSV
fi
le which includes all
nodes OTAA credentials needed for direct batch import. Then, you must keep in mind that Actility needs more
information to be included in that CSV
fi
le. The CSV to be imported must follow the next format
(15 columns).
The CSV
fi
le for
’
N
’
devices must respect the next format:
CREATE_OTAA,<DevEUI_1>,,<DevProfile>,<AppEUI_1>,<AppKey_1>,,,<AS_profile_ID>,<ConnectivityPlan>,<name>,,,,,
CREATE_OTAA,<DevEUI_2>,,<DevProfile>,<AppEUI_2>,<AppKey_2>,,,<AS_profile_ID>,<ConnectivityPlan>,<name>,,,,,
CREATE_OTAA,<DevEUI_3>,,<DevProfile>,<AppEUI_3>,<AppKey_3>,,,<AS_profile_ID>,<ConnectivityPlan>,<name>,,,,,
...
CREATE_OTAA,<DevEUI_N>,,<DevProfile>,<AppEUI_N>,<AppKey_N>,,,<AS_profile_ID>,<ConnectivityPlan>,<name>,,,,,
Where:
‚
CREATE_OTAA
: Should always be the same in order to import the devices using OTAA join mode.
‚
<DevEU
I
>
: This is the Device EU
I
exported from Libelium SCM CSV
fi
le. Should not be changed.
‚
<DevPro
fi
le>
: This
fi
eld is related to the LoRaWAN region of the node. Possibilities depending on the version:
-
LoRaWAN EU863-870: LORA/GenericA.1.0.2a_ETS
I
_Rx2-SF12
-
LoRaWAN US902-928: LORA/GenericA.1.0.2a_FCC_Rx2-SF12
-
LoRaWAN
I
N865-867: LORA/GenericA.1revB_
I
N865_Rx2-SF12
-
LoRaWAN AU915-928: LORA/GenericA.1revB_AU915_Rx2-SF12
-
LoRaWAN AS923: LORA/GenericA.1_AS923_Rx2-SF10
‚
<AppEU
I
>
: This is the Application EU
I
exported from Libelium SCM CSV
fi
le. Should not be changed.
‚
<AppKey>
: This is the Application Key exported from Libelium SCM CSV
fi
le. Should not be changed.
‚
<AS_pro
fi
le_
I
D>
: This is Actility
’
s "AS routing pro
fi
le
I
D" which belongs to each customer
’
s account.
I
t can be
read from the pro
fi
le when it is
fi
rst created.
‚
<ConnectivityPlan>
: This must be set as "dev-cs/testing".
‚
<name>
: Name of each device (optional).
Example for some Smart Parking EU nodes (LoRaWAN EU863-870). Let
’
s assume TWA_123 was the "AS routing
pro
fi
le
I
D" given by Actility for our application:
- 57 -
v7.5
Summary of Contents for Waspmote Smart Parking v2
Page 1: ......
Page 92: ...LoRaWAN Network Server setup Figure Check In to DeviceHQ 91 v7 5 ...
Page 135: ...Deployment and installation Figure Final section of the anchor and screw 134 v7 5 ...
Page 143: ...Safety Guides 11 Safety Guides 11 1 Smart Parking Chemical Fixing Cartridge 142 v7 5 ...
Page 144: ...Safety Guides 143 v7 5 ...
Page 145: ...Safety Guides 144 v7 5 ...
Page 146: ...Safety Guides 145 v7 5 ...
Page 147: ...Safety Guides 146 v7 5 ...
Page 148: ...Safety Guides 147 v7 5 ...
Page 149: ...Safety Guides 148 v7 5 ...
Page 150: ...Safety Guides 149 v7 5 ...
Page 151: ...Safety Guides 150 v7 5 ...
Page 152: ...Safety Guides 151 v7 5 ...
Page 153: ...Safety Guides 152 v7 5 ...
Page 154: ...Safety Guides 153 v7 5 ...