When mounting your tag, make sure that the UWB antenna of the tag is facing upwards if possible for optimal positioning accuracy.

The settings from our tags can be changed through our Device Configurator. It can be used to change the tag’s positioning protocol (TDOA or TWR), its ID, its UWB settings, and its positioning parameters such as update rate and more.

For Mini tags (now discontinued), Wearable tags, and Industrial tags this is done via NFC in combination with our NFC reader:

For Developer tags this is done via USB.

Download & Installation

The Pozyx Device Configurator is available for download from www.pozyx.io/products-and-services/device-configurator. More information about the installation is also available on this page.

Configuring your tag

After starting the Pozyx Device Configurator, connect the tag to your computer. The Developer tag can be connected with the provided USB data cable. The Mini tag, Wearable tag or Industrial tag should be placed on the NFC reader, which is connected with USB to your computer. The settings of your tag will become visible once the tag is correctly connected and USB/NFC is selected. The settings that you will see depend on the tag you're using.

Developer tag

Wearable tag

General

Here you can change the UWB ID of the tag. This ID will be used throughout our whole application stack, in the web application and in the MQTT stream.

You can also save your settings in a preset here. By saving your settings in a preset you can easily apply the same settings to a different tag. This saves all settings: UWB settings, Aloha TDOA settings, Accelerometer settings and Button configuration.

On the Developer tag you can also change the mode here: This tag can be used as Enterprise TDOA tag (which is probably the mode you need), as Enterprise TWR tag, as Creator tag, and as Creator anchor.

UWB settings

With these settings, you can change UWB related parameters such as the UWB channel, the data rate, the preamble length of the UWB transmission, the PRF (pulse repetition frequency) and the UWB transmission power. Changing these settings also requires a change of the settings in the gateway via the Pozyx web application as described in the UWB settings section to ensure that both the tags and the system are aligned.

The power of the tag should be selected high enough so that the surrounding anchors can receive the UWB packets from the tag. On the other hand, it is not always beneficial to use the highest available power, as higher power may also result in more reflections of the UWB signal. In an optimal configuration, minimal power is assigned that still results in good connection with the surrounding anchors.

Aloha TDOA settings

With these parameters, you can configure the update rate of the tag and control the variation. The update rate is the number of times per second a new positioning transmission is sent. One position transmission is called a ‘blink’. The variation is a parameter to reduce the possibility of packet collisions between multiple tags. Keeping this to 10 ms should be fine in most cases.

The Developer tag also has a payload field. By clicking on the select button you can add the sensor data from this tag in the MQTT packet. On our MQTT data structure page you can see how this data is sent. The following sensor data is available:

  • Acceleration
  • Gyro
  • Magnetic
  • Orientation
  • Quaternion
  • Linear acceleration
  • Gravity
  • Pressure
  • Max linear acceleration

Accelerometer settings

The Mini tag, Wearable tag and Industrial tag have an accelerometer, which's data is being sent in the TDOA blinks and can thus be read out in the MQTT stream. On our MQTT data structure page you can see how this data is sent. The acceleration is measured along 3-axis (so each accelerometer update is an array of 3 values) and is expressed in mg (milli-G's). The interval of the accelerometer is ± 2 g, which means that it can measure a maximum acceleration of + or - 2 g.

The update rate of the accelerometer is configured independently from the positioning update rate (= TDOA update rate), but we recommend that the TDOA update rate and the update rate of the accelerometer are roughly aligned as one TDOA blink can contain a maximum of 28 accelerometer measurements. This means that e.g. if we have an accelerometer update rate of 25 Hz and a TDOA update rate of 0.5 Hz, 50 measurements will need to be sent in one blink. If this situation occurs, the tag will throw away the first 22 measurements and only transmit the last 28 measurements.

If you don’t want to lose any accelerometer updates, make sure your update rates comply to the following formula: (Accelerometer update rate (Hz))/(TDOA update rate (Hz)) < 28

The accelerometer can also be used to control a sleep functionality. When the tag is sleeping it will decrease its update rate to save battery life. The sleep mode functionality is configurable by the following settings:

  • Sleep delay: the tag can only go into sleep mode if it is not moving for at least a number of blinks equal to the sleep delay.
  • The sleep threshold setting determines the amount of movement required for the tag to remain active.
  • Skipped blinks gives the number of blinks that will be left out and not sent when the tag is in sleep mode.

For example, if the tag has an update rate of 10 Hz (10 blinks per second), a sleep delay of 25 blinks, skipped blinks equals 50 and the threshold is set to 150 mg; the tag will go to sleep if the tag did not reach the 150 mg threshold during 25 blinks (2.5 seconds). When in sleep mode, the tag will only send a blink every 50 blinks (every 5 seconds). If at any time the tag experiences movement higher than the threshold, the sleep delay counter is reset to 0 and the tag will resume updating at the configured update rate (10 Hz).

Button configuration

The Interactive edition of the Wearable tag has a button that can be used to:

  • Turn it on and off
  • Cycle between states
  • Send out events

With the Pozyx Device Configurator you can customize this behavior to best suit your needs. Press the Edit settings button to get started.

After pressing the Edit Settings button you have the option to select one of the preconfigured button configurations in the Actions field:

  • Off (LEDs on): When you select this button configuration the button will be disabled but the LED will still blink to indicate that the tag is powered on.
  • Off (LEDs off): When you select this button configuration the button will be disabled and the LED will no longer blink. You won't have an indication about whether the tag is powered on or off.
  • Default: See the Action Configurator section for information about the default button behavior.

You can also change the button behavior completely by pressing the Configure Actions button. When you click on this button you will get a pop up in which you can create a new button configuration. More information about this screen can be found below in the Action Configurator section.

After configuring the button behavior you'll need to press the save button:

Give it a name:

And then select your new configuration on the main screen and click Apply:

Action configurator

By default the button behavior will be configured as follows:

  • Long pressing the button will turn the tag on/off.
  • Short pressing the button will send out an event (with ID 0).
    This event is visible in the MQTT stream, more on that below.
  • Double pressing the button will put the tag in the next state and also send out an event (with ID 1).
    This state and event will also be visible in the MQTT stream, more on that below as well.

Long / short / double pressing is defined as:

CommandDescription
Long pressPress and hold the button for 3 seconds
Single pressPush the button for less than 1 second
Double pressPush the button twice in half a second
Action: Transmit event only

This action will send out an event with the ID you specify.

The event ID and the timestamp of a click can be found in the MQTT stream under tagDataevents:

"events": [
  {
    "type": 0,
    "timestamp": 1615930179.1052644
  },
  {
    "type": 0,
    "timestamp": 1615930179.827918
  },
  {
    "type": 0,
    "timestamp": 1615930180.628115
  }
]
JS

The events array will hold the last 3 events and each event will be sent for 255 blinks (unless it's pushed out of the array sooner by more recent events). The event ID can be found in the type field.

See our MQTT data structure page to see the complete data structure of an MQTT packet.

Action: Cycle state + event

This action will not only send out an event as described above but will also change the state of the tag.

A tag can cycle between 2 or 3 states, depending on how you configure it (# States), and its state information can be found in the MQTT stream under tagData status. By assigning different event IDs to different actions (e.g. event ID 0 to a short press and event ID 1 to a double press) you can capture the timestamp of when a state change has occurred:

"status": "2",
"events": [
  {
    "type": 1,
    "timestamp": 1615930179.1052644
  },
  {
    "type": 0,
    "timestamp": 1615930179.827918
  },
  {
    "type": 0,
    "timestamp": 1615930180.628115
  }
]
JS

See our MQTT data structure page to see the complete data structure of an MQTT packet.

LED behavior

Depending on the button configuration the following table gives the LEDs behavior per action:


DescriptionActionLED behavior
Long pressPower onGreen LED lights up for 1 second
Power offRed LED lights up for 1 second
Single pressTransmit event onlyGreen LED blinks 1 time
Double pressTransmit event onlyGreen LED blinks 2 times
Single/Double pressCycle state + eventColor of the state gets blinked.
State 1: Green
State 2: Blue
State 3: Red


By default, the LED will blink once per second, and the color of the LED will indicate the current state.

Battery impact


The default settings provide the best battery life. Changing to a lower data rate or to a longer preamble length will result in a higher power consumption. The same is true for a higher TDOA update rate, the use of TWR and accelerometer update rate; the more updates that are sent the more the tag will use its battery capacity. Disabling the LED to blink every second will also slightly improve the battery life.