Status

Date

Doc Version

Applicable

Confidentiality

RELEASED 

v1.0

WPE v1.6.0

PUBLIC



General Information

This document describes the content for Wirepas Positioning Engine (WPE) version v1.6.0. WPE is delivered as a Docker image, which is available to licensed customers.

The most important changes in this release are:

  • Improvements in the WPE configuration interface
  • Several bug fixes, including the fix for tags appearing in “diagonal rows”

Important Note

If WPE is not used with WNT, but instead accessed directly via WPE public API, the fix for the bug related to tags appearing in diagonal rows requires changes also in the client side to be effective. Please contact Wirepas for further details in this case.

Version Information

Current version

1.6.0

Previous version

1.5.0

Release date

Compatibility

The below table provide the compatibility matrix with WPE v1.6.0 release and other Wirepas components.

From WPE perspective following points are worth noting

  • WPE v1.6.0 is compatible only with WNT version 4.3.x and newer due to changes in WNT ↔︎ WPE internal API
  • WPE v1.6.0 shall be installed with Wirepas Service Installer version >= 4.3.0

Wirepas Positioning Engine

(WPE)

Wirepas Network Tool

(WNT)

Wirepas Mesh Firmware

 

Wirepas Mesh SDK

(SDK)

Linux Gateway

Wirepas MQTT Library

Wirepas Terminal

Version

v1.6.0

v4.3.0

v5.3.0.89

v1.4.0

v1.4.2

v1.0

v0.101

Release Date

12th Apr 2023

12th Apr 2023

7th Nov 2022

7th Nov 2022

7th Nov 2022

20th Apr 2021

11th Feb 2019

Compatibility

 

Wirepas Mesh Firmware

v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.0

v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.0

v5.3.0

v5.3.0

v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.0

v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.0

v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.0
 OTAP Operations are not supported in v5.x

Wirepas Mesh SDK

Positioning App

  • v4.0.0.0 (“old” application)
  • v5.0.0.0 (“old” application)
  • v1.2.0.2 (PosApp v1.2.0.x + PosLib v1.0.0)
  • v1.2.3.x (PosApp v1.2.3.x + PosLib v1.1.0)
  • v1.3.0.x (PosApp v1.3.0.x + PosLib v1.1.0)
  • v1.4.0.x (PosApp v1.4.0.x + PosLib v1.1.0)

-

v1.4.x

-

-

-

-

WNT

v4.3.0

-

v4.0.x, v4.1.x, v4.2.0, v4.3.0

-

v3.x, v4.0.x, v4.1.x, v4.2.0, v4.3.0

-

-

WPE

-

v1.6.0

v1.4.x, v1.5.0, v1.6.0

-

-

-

-

Linux Gateway

-

v1.4.x

v1.3.x (without OTAP v2)

v1.4.x (v1.4.2 if fragmentation is used)

-

-

v1.4.x

-

Wirepas Terminal

-

-

v0.101 -
 OTAP Operations are not supported

-

-

-

-

Enhancements

Summary

Description

Configuration interface improvements

The validation of the provided configurations (anchors, areas) is improved drastically. If an error is detected during the configuration, the given configuration is fully discarded and an error is returned.

Area matching performance improvement

The area matching logic is improved especially in the cases where there are lots of simple, e.g. rectangle shaped, areas.

More flexible runtime environment support

Extended configuration options for WPE services by allowing separate bind_address and service_address settings. This eases the reuse of services configuration in different kind of container runtime environments.

Bug Fixes and Known Issues

Bug Fixes

Following table lists the most relevant fixed issues.

Summary

Description

WPE calculated locations appear in diagonal rows

With large amounts of closely located tags, WPE seemed to locate some tags in diagonal rows. The root cause for the errors was the usage of too imprecise data types in the WPE APIs. Effectively, the usage of 32-bit floating point data types truncated the calculated location coordinate values so that the results seemed to have pattern with large data sets. The problem is fixed in a backward compatible manner by introducing new double precision floating point fields for node and area coordinates in configuration data and in locate results.

NOTE: The newly introduced lla_precise field must be explicitly taken into use in WPE Public API clients in order to be effective. Please contact Wirepas for further details if you are using WPE Public API.

Same measurement time reported for different packets

This error occurred when WPE was used with WNT. In some cases, the provided measurement time for two or more measurements was identical even thought the other available timing information suggested that those were different. The error was caused by incorrect usage of message timestamps when handling locate requests in batches in WNT → WPE interface.

WPE reconnection to MQTT works only once

When connected to MQTT (e.g. with WNT), WPE was able to reconnect to the MQTT broker after the first connection failure. After subsequent connection failures, e.g. due to broker restart, WPE needed to be restarted in order to reconnect. The problems were caused by faulty connection management at the WPE.

Known Issues

Please see Wirepas Positioning Errata [1] for known issues.

References

[1] Wirepas Positioning Errata

Revision History

Date

Version

Notes

v1.0

Initial Version Online

Legal Notice

Use of this document is strictly subject to Wirepas’ Terms of Use and Legal Notice.

Copyright © 2023 Wirepas Oy