Versions Compared

Old Version 4

changes.mady.by.user Tobias Kaupat

Saved on

compared with

New Version Current

changes.mady.by.user Tobias Kaupat

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The device is not connecting and no remote error analysis is possible.
Local access to the device is required.

DeviceIndicationMeaning / Causes
All
  • Green LED Flashes every few seconds
  • Indicates a reboot Cycle
  • SIM Card not connected?
  • Hardware error?
  • Local Configuration error (remote updates are validated!)
  • Local Firmware Update error (remote updates are validated!)
  • Battery low / brownout
wMbus Gateway
  • After Reset the Blue LED does flash for ~3 minutes
  • Mobile connection cannot be established
All Battery Devices
  • No green LED light after Reset
  • Battery empty
  • Hardware error


Note
titleFurther Error Analysis

Log from device can indicate the cause

...

  • Contact Lobaro with a description of the defects, type and number of devices. We will issue an Retour document and number.
  • Ship devices without batteries. Else a fee for shipping dangerous goods must be applied.


LoRaWAN Join fails

To find the reason for a missing / failing Join Request check the following information:

  • What LNS is used?
  • Is the device registered with the correct LoRaWAN Version (mostly 1.0.2 for Lobaro Devices)
  • Is the device configured to use LoRaWAN v1.0 (v1.1 use should be avoided since it's not certified)
  • Are all Device parameters correct in the LNS: DevEUI, JoinEUI (aka AppEUI), AppKey
  • Is there a possibility to trace the Join request on LoRaWAN Gateway Level?
  • Does the Server states any Errors when receiving the Join Request
  • Is there any error indication inside the device log?
    • e.g. "hw error for tx data up"