This section of our documentation answers the most typical questions we are getting from our ThingPark Location customers.

  1. How do I report problems?
  1. Where can I find the reference for LED patterns, button press sequences, buzzer tones on micro tracker or smart badge?
    You can find all the sequences to follow in Key micro tracker commands and in Key smart badge commands.

  2. Where do I find certification documents?
    Abeeway trackers are certified with ATEX Zone II, FCC, EC, FCC, IC, TELEC. Certifications depend on the specific reference you have ordered. Certifications are always indicated on the product sticker. You can find all certification documents in Certification Documents (opens new window).

  3. Where do I find Abeeway product data sheets?
    The data sheets of different products is located in DataSheet (opens new window).

  4. How do I perform a firmware update of the trackers?
    Please refer to Firmware Update for more details.

  5. What are the steps to replace a faulty tracker?
    The RMA procedure and the associated form are described in RMA Procedure (opens new window).

  6. Are there preferred orientations or positioning for Abeeway trackers?
    Yes. Here are the instructions for all the trackers:

  1. Is there a How-To guide to integrate my tracker with a LoRaWAN® network server (Actility ThingPark, TTN/TTI, Senet, etc.)?
    Yes. You can follow Integrating a third-party network server.

  2. Is there a configuration tool for Abeeway trackers? Are there pre-cooked “typical” configurations for common use cases?
    Yes, you can see Abeeway Device Manager device configuration tab to select pre-defined profiles for most common use cases.

  3. Is there a way to estimate battery life for a given configuration?
    Yes, you can use Power Comsumption Estimation to estimate the battery lifetime of your trackers. However, be aware that this is an approximation under ideal conditions.

  4. How often should I charge my device?
    Only micro trackers and smart badges can be recharged. We recommend to periodically charge them at least once a month. To not damage the battery, they must not be left with a low or completely discharged battery for more than a month. The warranty is void if the battery has not been charged for a prolonged period.

  5. Can I use any USB charger?
    Yes, provided that you are certain that it has short-circuit protection, which is an essential security feature.

  6. My tracker resets very often. How do I know the root cause?
    You can look at the MCU Reset Cause in LoRaWAN® heartbeat uplinks. If the reset cause is 0x40, which means (System Request -application reset-), then one possible cause can be: There are lot of LoRaWAN® messages that the tracker is trying to send but there is lack of appropriate LoRaWAN® coverage. Then, if the LoRaWAN® MAC queue gets really full, the tracker will reset itself to be able to function properly. For more information about different reset causes and their explanation, see Abeeway Trackers Reference Guide.

  7. How do I debug the tracker over USB port?
    You can connect the tracker to USB port and interact with the tracker using serial terminal program like Tera term. You can find more information CLI Usage (opens new window).

  8. My geolocation keeps getting stopped from time to time. What could be the reason?
    There is temperature monitoring feature in the tracker, which if enabled in the tracker configuration results in disabling the geolocation when the temperature detected by the tracker is outside the range. The symptom of this is to receive Temperature Alert Event message. You can find more information about temperature monitoring here. Temperature monitoring can be disabled by setting the value of temperature_high = 255 and temperature_value=255 in the firmware. It can be easily be done using Abeeway Device Manager (Device Configuration tab) or by connecting the tracker over USB port with CLI.

  9. What is the behaviour of LoRaWAN join procedure of the trackers?
    The behaviour of Abeeway trackers during the LoRaWAN join process is described here