Skip to main content
Skip table of contents

Anchor warnings & errors

Anchors have a few ways of informing us that they’re not working in the intended way.

  • There’s a LED on the anchor itself to signify any hardware/network faults.

  • The gateway and anchor communicate frequently to monitor for anything that’s suboptimal, and the gateway also monitors the anchor’s operation. These software related warnings can be seen in our RTLS setup application.

On this page, you’ll find an overview of these warnings and errors, and how to tackle them.

Anchor LED

Information about the anchor’s LED can be found on Mounting the anchors | Validating-the-anchors .

RTLS setup application

Both from the Visualization page in the web application and from the Anchor device management page you’ll be able to see any warning or error that an anchor might have. In the visualization the messages will be visible in the second column next to the anchor ID as seen in the example below:

In the Anchor device management page the same column can be found:

Software warnings overview

Below is a list of all the possible messages related to the anchor.

Level

Message

Icon

AC

Info

ERROR

Offline

The anchor is either disconnected or there's a hardware failure. Hardware failures are almost always related to cabling issues as every individual anchor is tested before it leaves our production facility. Swap the anchor with an anchor that is working correctly on an other cable to confirm (Replacing an anchor).

WARNING

Self test failed: %s

There are different component self tests in the anchor:

  • UWB

  • Network

  • External flash

  • Accelerometer

If one of these tests is failing, please contact us through http://support.pozyx.io.

WARNING

No coordinates

The anchor needs coordinates before it can participate in positioning. Add the anchor coordinates on the SetupAnchor Coordinates page. The anchor is not shown on the visualization.

WARNING

No TX sync packets

There are no sync packets being transmitted. Go to the SetupAnchor connectivity page and press the Capture UWB connectivity button, if this does not solve the issue please contact us through http://support.pozyx.io.

WARNING

No RX sync packets

There are no sync packets being transmitted. Go to the SetupAnchor connectivity page and press the Capture UWB connectivity button, if this does not solve the issue please contact us through http://support.pozyx.io.

WARNING

No sync packets

The anchor is not being synchronized with the other anchors. Go to the SetupAnchor connectivity page and press the Capture UWB connectivity button, if this does not solve the issue please contact us through http://support.pozyx.io.

WARNING

No TX packets

There are no network packets being transmitted by the anchor. Make sure to test or swap the cable to rule out errors related to defect cables.

WARNING

No RX packets

There are no network packets received by the anchor. Make sure to test or swap the cable to rule out errors related to defect cables.

WARNING

No network packets

There are no network packets being received from the anchor. This can happen when the anchor is not receiving UWB packets from any tags and when it is also not synchronizing.

WARNING

Only x% of network packets successful

There is loss on the network. Possible reasons for this include:

  • Interference on the cable

  • A cable which is too long

  • A cable which is worn out

  • The buffer of the switch is overflowing because it can not handle the amount of network packets

  • The buffer(s) of the first anchor(s) in a daisy chain is/are overflowing because the total amount of UWB packets captured by the anchors on that chain is too high and the first anchor(s) can not handle the throughput

INFO

Presence only

The anchor is used in presence only mode and will not take part in normal positioning.

INFO

Not in use

/

The anchor is toggled out of use through the web application. The anchor will not be shown on the visualization

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.