NKE Hub'O, Начало работы

Страница: 14 / 14

Hub’O: Getting started
All Rights Reserved – nke Watteco® Hub’O: Description of the exchanges with the Server
Page 14 of 14
For each end-device, on the first line can be seen the last 4 bytes of the end-device devEUI. On the
second line, can be seen the last RSSI level, converted to a rating on 10.
To go to the next end-device, please press shortly the user button. Each time a press is detected, the
next end-device is displayed. When the last end-device is displayed, on the next press, Hub’O will
loop back to the first one. To get out of the list, please wait for 30 seconds without pressing the
button.
To get more information about Hub’O IHM, please refers to the IHM description document:
- “Description_IHM_Hub_O_VX_X.pdf”
6.2 F
IRST END
-
DEVICE CONFIGURATION
By default, nke Watteco devices are configured to send “unconfirmed” frames to the LoRaWAN
network, in order to be compatible with all the private/public existing networks.
However, inside a LoraWAN network managed by Hub’O, it is strongly adviced to set this
configuration to “confirmed” frames.
In order to do that, the distant server should send an end-device configuration file to Hub’O after
each new association on the network. To configure the end-device to send “confirmed” frames, the
following frame needs to be sent on FPort
125: 1105800400000801 .
For more details about end-devices configurations with Hub’O, please see:

“ Hub'O_Server_Exchanges_Description_X_X.pdf”
For more details about the frame allowing to configure the type of message send by the nke Watteco
end-devices, please refers to:
http://support.nke-watteco.com/lorawan-cluster/#Messagetype