FAQ
- 1 How can I find the IP address of my gateway?
- 2 How to reboot
- 3 How to shutdown
- 4 How do I know my µWiotys version ?
- 5 How do I know µWiotys is fully started?
- 6 Device update not done
- 7 I don’t see my device on the interface
- 8 How do I know my LoRaWAN device is started?
- 9 Modbus registry is not available
- 10 Measurement value is 0xFFFF
- 11 Floating point reading example
- 12 The timestamp value is incorrect
- 13 How to get µWiotys logs
How can I find the IP address of my gateway?
If the gateway is configured in DHCP, it might be tricky to find IP address to configure uWiotys.
On Windows
You can use Angry IP Scanner - the original IP scanner for Windows, Mac and Linux then filter on MAC ADDRESS and / or MAC VENDOR
On linux
sudo nmap -sn 192.168.1.0/24 | grep "GATEWAY_MAC_ADDR"
Replace 192.168.1.0
with the network IP.
How to reboot
For iFemtoCell or iStation:
With Web interface :
Administration → Gateway
- Picture of button
With Kerlink gateway button:
iFemtoCell: Press the reset button located on the side of the gateway.
iStation: Press once (JUST only once) the On/Off button.
Warning: an electric reboot can corrupt the update process
How to shutdown
To shutdown, simply unplug the gateway.
How do I know my µWiotys version ?
At the left bottom of the menu
How do I know µWiotys is fully started?
You will see a green check indication in the Dashboard.
Device update not done
Restart µWiotys, if it doesn’t work, contact us.
I don’t see my device on the interface
Restart µWiotys, if it doesn’t work, contact us.
How do I know my LoRaWAN device is started?
Check in your environment of the device and look at the “Events” menu to see if uplinks data are coming
Modbus registry is not available
If a Modbus registry isn't available, it can mean there is no Lora device configured at this slave address. Check out the Common table at registry 0x0001 to 0x0004 to make sure your slave is correctly configured. If you cannot read the devEui please check your µWiotys configuration file.
For measurement reading, please make sure you are checking the proper Modbus table. You can check the configured Wi6labs reference available in common table registry 0x0005.
Measurement value is 0xFFFF
The measurement Modbus registry will be configured to default value 0xFFFF (or 0x7FFF for signed) until a valid measurement payload is received. The join message will not be displayed in Modbus. When an uplink is received with no valid measurement (config payload, keep alive,...) the timestamp will be updated but not the measurement registry.
Floating point reading example
With Modbus Doctor, we want to read the value of the register 0x302D.
In order to get the right floating point's value (0.04174805
), we have to set Modbus Doctor's parameters to the following values:
Mode : HEXADECIMAL
Display mode : 32 bits float
Register : 302D h
Length : 02 h
Type : 3 Holding registers
Check "Swap bytes" box
The value we had in our example, was 0x3D2B0000
in hexadecimal and 0.04174805
in float.
The timestamp value is incorrect
The timestamp contains the date and time of the last uplink message for each slave, so it can take several minutes or hours to refresh depending of the Lora device uplink frequency.
The GW is automatically synchronized with NTP reference. Two NTP servers can be configured. When the GW is started it will automatically gets the time from NTP reference. If no NTP is available, the time of the last shutdown will be used.
How to get µWiotys logs
Coming soon…