Status | Date | Doc Version | Applicable | Confidentiality |
RELEASED | v1.0 | WPE v1.7.0 | PUBLIC |
General Information
This document describes the content for Wirepas Positioning Engine (WPE) version v1.7.0 release. WPE is delivered as a Docker image, which is available to licensed customers.
The most important changes in this release are:
- Updated base ubuntu image, including Python 3.10
- Bug fixes, including the fix for area deletion problems with multiple networks
- Optional support for lightweight anchor location checking
Version Information
Current version | 1.7.0 |
Previous version | 1.6.0 |
Release date |
Compatibility
The below table provide the compatibility matrix with WPE v1.7.0 release and other Wirepas components.
From WPE perspective following points are worth noting
- WPE v1.7.0 is compatible only with WNT version 4.3.x and newer, but it recommended to be used with WNT 4.4.x or newer due to the new features introduced via WNT ↔︎ WPE internal API
- WPE v1.7.0 shall be installed with Wirepas Service Installer version 4.4.x
Wirepas Positioning Engine (WPE) | Wirepas Network Tool (WNT) | ||
Version | v1.7.0 | v4.4.0 | |
Release Date | 22nd Dec 2023 | 22nd Dec 2023 | |
Compatibility
| Wirepas Mesh Firmware | v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.x, v5.4.x | v4.0.x, v5.0.x, v5.1.x, v5.2.x, v5.3.x, v5.4.x |
Wirepas Mesh SDK | Positioning App
| - | |
WNT | v4.3.x, v4.4.x | - | |
WPE | - | v1.6.x, v1.7.x | |
Linux Gateway | - | v1.4.x v1.3.x (without OTAP v2) |
Enhancements
Summary | Description |
3rd party dependency updates | Updated container base image to Ubuntu 22.04 LTS version with Python 3.10 (end of life Oct’2026), |
Optional support for estimating anchor locations for configuration integrity checks | If enabled, WPE calculates anchor location from a measurement message originating from an anchor node (“opportunistic scan” anchor mode). The anchor location is returned in a separate field, |
Bug Fixes and Known Issues
Bug Fixes
Following table lists the most relevant fixed issues.
Summary | Description |
Area deletion does not work correctly if there are multiple networks configured into WPE | Area / zone matching functionality in WPE might get broken in cases where multiple networks are configured for WPE by adding anchors or areas that are linked to different networks. If area deletion is called in such case without specifying the network (as done by WNT), the area management within WPE gets out of sync, causing exception inside WPE. The issue is fixed by improving the handling of the “global” and network specific areas. |
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 © 2024 Wirepas Oy