<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://c4d.lias-lab.fr/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Acorde</id>
	<title>COMP4DRONES - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://c4d.lias-lab.fr/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Acorde"/>
	<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php/Special:Contributions/Acorde"/>
	<updated>2026-04-07T00:45:44Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.37.1</generator>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP3-15_2&amp;diff=1128</id>
		<title>WP3-15 2</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP3-15_2&amp;diff=1128"/>
		<updated>2023-03-14T12:33:18Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Detailed Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Geo-referenced Position and Attitude Estimation=&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP3-15_2&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Platform, Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Energy, Raw sensed data navigation messages of GNSS receivers, raw data from low-cost IMU and barometer&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation Sensor&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from GNSS receivers, low-cost INS and barometer&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position, Attitude and Velocity&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| Geo-referenced Position and Attitude Estimation System&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 5&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In COMP4DRONES, ACORDE is developing GLAD+, and outdoor geo-referencing system which abides to the “Geo-referenced Positioning and Attitude estimation system” block introduced in the COMP4DRONES architecture introduced, whose representation is reproduced in the following figure.&lt;br /&gt;
[[File:wp3-15_2_01.png|frame|center|Building block diagram for Geo-referenced Position and Attitude Estimation system block]]&lt;br /&gt;
&lt;br /&gt;
GLAD+ is The following figure shows a number of crucial enhancements tackled in COMP4DRONES .&lt;br /&gt;
&lt;br /&gt;
==Detailed Description==&lt;br /&gt;
&lt;br /&gt;
 GLAD+ is a significantly improved version of its predecessor GLAD (GNSS-based Low-Cost position and Attitude Determination system).&lt;br /&gt;
It is specifically oriented to provide drones quality navigation information (position, velocity and attitude) at a reduced cost in challenged outdoor scenarios. Drone scenarios expose position/attitude estimation systems to challenging conditions (e.g., shadows, more challenging dynamics than land-vehicles, calibration constraints), and stringent cost, size and weight requirements. As GLAD, GLAD+ is a “complete” solution from ACORDE, in the sense that ACORDE performs both application and platform design and development (including a COTS based HW design).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;imagemap&amp;gt;&lt;br /&gt;
File:ACO_GLAD_PLUS.png|thumb|800px|center|alt=ACORDE GLAD+ component| Enhancements performed to the ACORDE GLAD system in COMP4DRONES (click on them for more information)&lt;br /&gt;
rect 512 402 1443 519 [[WP4-16]]&lt;br /&gt;
rect 522 657 1449 763 [[WP5-11_ACO]]&lt;br /&gt;
&amp;lt;/imagemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 The above figure sums up the contributions and improvements in GLAD+, enabled by ACORDE activity in COMP4DRONES, taking GLAD as a baseline:&lt;br /&gt;
&lt;br /&gt;
* The design of and improved HW/SW platform for the navigation solutions (WP3-15_1). It includes a new HW platform with improved capabilities on GNSS receivers, and also the assessment of license-free real-time RTOS on top.&lt;br /&gt;
* Enhancement of the navigation software, for adapting it to the new platform and to apply algorithmic improvements, including the assessment of possible AI based improvements ([[WP4-16]]).&lt;br /&gt;
* Providing support of anti-jamming and anti-spoofing features ([[WP5-11_ACO]]).&lt;br /&gt;
* Providing an improved/extended interface for a smoother integration on drone systems (activity globally associated to WP3, with implications in WP4 and WP5).&lt;br /&gt;
&lt;br /&gt;
This page gives mostly details on the overal GLAD+ system, and on its SW/HW platform.&lt;br /&gt;
More details on other improvements also reachable by clicking the links to them (also on the clickable figure).&lt;br /&gt;
&lt;br /&gt;
In addition to a significant upgrade of its positioning products, in COMP4DRONES ACORDE is also aiming the improvement of its productivity on the modelling, design, implementation and validation procedures of these type of systems [[WP6-ESDE]].&lt;br /&gt;
&lt;br /&gt;
==Status after C4D==&lt;br /&gt;
&lt;br /&gt;
So far, ACORDE has advanced in parallel in all the afore mentioned tasks. The current advance can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* The new HW platform for GLAD+ has been designed and implemented (shown in Figure 66a). The new HW platform includes new low-cost GNSS receivers, with multi-constellation and anti-jamming and anti-spoofing capabilities.&lt;br /&gt;
* A custom Linux Real-Time port for the GLAD+ HW platform has been developed. This port relies on an updated u-boot, on buildroot-2020.02-LTS (generating a filesystem to be loaded as ramdisk), and on kernel-rt-4.19.59 (includes RT-PREEMT patch).&lt;br /&gt;
* In past GLAD development, a platform abstraction layer was developed in order to separate platform dependent code (e.g., threads creation, interruption management, POSIX calls, call to drivers). This layer has been already updated to cover RT-Linux target.&lt;br /&gt;
* A preliminary version of the driver for making available jamming and spoofing events has been already developed and tested.&lt;br /&gt;
* A logger system has been updated and sent together the GLAD+ HW/SW platform ACORDE to the drone integrator in construction use case (UC2-demo1). ACORDE generated documentation for integration and supported the integrator in what resulted a smooth and quick integration.&lt;br /&gt;
* The integrator performed flight tests. ACORDE supported the integrator with additional documentation (i.e., for operation and tests of the integration, and for indicating specific maneuvers to let validation tests cover as many working conditions as possible).&lt;br /&gt;
* With that information, ACORDE has done some preliminary evaluation of the current algorithms, and tested the potential of some improvements, i.e.., multi-constellation support. Algorithmic improvement is in progress.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_2_02.png|frame|center|New HW/SW platform for the ACORDE outdoor geo-referencing system and integration on a drone platform int he COMP4DRONES for the outdoor demo of the construction use case]]&lt;br /&gt;
&lt;br /&gt;
==Contribution and Improvements==&lt;br /&gt;
&lt;br /&gt;
GLAD+ is expected to bring important improvements or contributions that can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* More interoperability, given by the support of a Mavlink interface for providing the position estimates.&lt;br /&gt;
* Security features, enabled by the anti-jamming and anti-spoofing capabilities&lt;br /&gt;
* Lesser cost, a validated Linux-based port implementation means an important license cost saving with regard GLAD implementation.&lt;br /&gt;
* Better performance (higher resilience, precision, and integrity) of the positioning solution (including attitude).&lt;br /&gt;
* A proposal of smooth Mavlink extension to provide all attitude components, and to report jamming and spoofing events.&lt;br /&gt;
&lt;br /&gt;
In addition to the own improvements associated to GLAD+, ACORDE has gained useful knowhow for smoothly targeting fusion algorithms to different low-cost COTS receivers. &lt;br /&gt;
This enables ACORDE to provide low-cost positioning solutions with less dependency on COTS suppliers, of great importance as show by the COVID related lock down. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure below shows the boot of the custom RT Linux distribution developed by ACORDE for GLAD+ platform. As can be seen, the kernel boots in little bit more 3 seconds (time labels are relative to kernel start). Taking into account the bootloader (not shown in the capture) took around4-5s, it leads to ~8s for booting the position&amp;amp;attitude estimation application (actually, the boot process goes on to get Ethernet link ready and launching SSH services, however, they are used for configuration or debugging, and the position&amp;amp;attitude application is launched before triggering). Further tests were conducted. Different resolution timers (from 100 to 1000 Hz) were tested. Moreover, the latencies of the scheduler (context switches) were estimated under heavy workload conditions, relying on the “cyclictest” [31] and “hackbench” [32] standard Linux utilities. An average latency 41 us, with 72 us maximum latency was obtained. This is a key figure for tick timer setting. For instance, 20 context-switches per second would take 1.4ms max. overhead, and less than 1ms on average, which seems affordable for GLAD+ application margins. Further study with final GLAD+ firmware is still required though.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_2_03.png|frame|center|Some results of the activity on design and development of GLAD+ in COMP4DRONES]]&lt;br /&gt;
&lt;br /&gt;
Figure b) above shows the results of some preliminary analysis enabled by the data log from the integration tests of Dec. 2020. That test was performed in static conditions in front of the facilities of the integrator (FADA-CATEC). Specifically, Figure 67b) shows three stacked graphics with the three components of a “tail-head” baseline estimation, fundamental pre-processing for attitude estimation (heading and pitch components can be directly derived via a simple formula). The top one is a non-causal estimate, and thus only possible after offline post-processing, which is taken as a ground truth reference. Green colors reflect convergence of the ambiguity resolution algorithms (and thus resembles a precise estimate), while orange reflect no-convergence, and thus no-valid, in general, inaccurate estimate. The bottom graphic shows a “forward” (i.e., that can be computed in real-time) estimate of the baseline using only GPS constellation. As can be seen, most of the capture (97.9%) lacks convergence. The problem is related to the buildings around the drone at the capture time, which shadowed several satellites of the GPS constellation. The graphic on the middle, shows a forward estimate of the baseline using both GPS and Galileo constellations, as enabled by the GLAD+ HW/SW platform. This estimate gets the same 97.7% figure, but of convergence time, indeed very close to the 98.3% time achieved with non-causal processing.&lt;br /&gt;
&lt;br /&gt;
==Design and Implementation==&lt;br /&gt;
&lt;br /&gt;
As well as the significant improvements in low-cost position and attitude estimation  i.e., GLAD+, in COMP4DRONES, ACORDE has progressed towards a qualitative enhancement of its design procedures. See more details in [[WP6-ESDE]].&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP3-15_2&amp;diff=1127</id>
		<title>WP3-15 2</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP3-15_2&amp;diff=1127"/>
		<updated>2023-03-14T12:31:54Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Detailed Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Geo-referenced Position and Attitude Estimation=&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP3-15_2&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Platform, Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Energy, Raw sensed data navigation messages of GNSS receivers, raw data from low-cost IMU and barometer&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation Sensor&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from GNSS receivers, low-cost INS and barometer&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position, Attitude and Velocity&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| Geo-referenced Position and Attitude Estimation System&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 5&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In COMP4DRONES, ACORDE is developing GLAD+, and outdoor geo-referencing system which abides to the “Geo-referenced Positioning and Attitude estimation system” block introduced in the COMP4DRONES architecture introduced, whose representation is reproduced in the following figure.&lt;br /&gt;
[[File:wp3-15_2_01.png|frame|center|Building block diagram for Geo-referenced Position and Attitude Estimation system block]]&lt;br /&gt;
&lt;br /&gt;
GLAD+ is The following figure shows a number of crucial enhancements tackled in COMP4DRONES .&lt;br /&gt;
&lt;br /&gt;
==Detailed Description==&lt;br /&gt;
&lt;br /&gt;
 GLAD+ is a significantly improved version of its predecessor GLAD (GNSS-based Low-Cost position and Attitude Determination system).&lt;br /&gt;
It is specifically oriented to provide drones quality navigation information (position, velocity and attitude) at a reduced cost in challenged outdoor scenarios. Drone scenarios expose position/attitude estimation systems to challenging conditions (e.g., shadows, more challenging dynamics than land-vehicles, calibration constraints), and stringent cost, size and weight requirements. As GLAD, GLAD+ is a “complete” solution from ACORDE, in the sense that ACORDE performs both application and platform design and development (including a COTS based HW design).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;imagemap&amp;gt;&lt;br /&gt;
File:ACO_GLAD_PLUS.png|thumb|800px|center|alt=ACORDE GLAD+ component| Enhancements performed to the ACORDE GLAD system in COMP4DRONES (click on them for more information)&lt;br /&gt;
rect 512 402 1443 519 [[WP4-16]]&lt;br /&gt;
rect 522 657 1449 763 [[WP5-11_ACO]]&lt;br /&gt;
&amp;lt;/imagemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 The above figure sums up the contributions and improvements in GLAD+, enabled by ACORDE activity in COMP4DRONES, taking GLAD as a baseline:&lt;br /&gt;
&lt;br /&gt;
* The design of and improved HW/SW platform for the navigation solutions (WP3-15_1). It includes a new HW platform with improved capabilities on GNSS receivers, and also the assessment of license-free real-time RTOS on top.&lt;br /&gt;
* Enhancement of the navigation software, for adapting it to the new platform and to apply algorithmic improvements, including the assessment of possible AI based improvements ([[WP4-16]]).&lt;br /&gt;
* Providing support of anti-jamming and anti-spoofing features ([[WP5-11-ACO]]).&lt;br /&gt;
* Providing an improved/extended interface for a smoother integration on drone systems (activity globally associated to WP3, with implications in WP4 and WP5).&lt;br /&gt;
&lt;br /&gt;
This page gives mostly details on the overal GLAD+ system, and on its SW/HW platform.&lt;br /&gt;
More details on other improvements also reachable by clicking the links to them (also on the clickable figure).&lt;br /&gt;
&lt;br /&gt;
In addition to a significant upgrade of its positioning products, in COMP4DRONES ACORDE is also aiming the improvement of its productivity on the modelling, design, implementation and validation procedures of these type of systems [[WP6-ESDE]].&lt;br /&gt;
&lt;br /&gt;
==Status after C4D==&lt;br /&gt;
&lt;br /&gt;
So far, ACORDE has advanced in parallel in all the afore mentioned tasks. The current advance can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* The new HW platform for GLAD+ has been designed and implemented (shown in Figure 66a). The new HW platform includes new low-cost GNSS receivers, with multi-constellation and anti-jamming and anti-spoofing capabilities.&lt;br /&gt;
* A custom Linux Real-Time port for the GLAD+ HW platform has been developed. This port relies on an updated u-boot, on buildroot-2020.02-LTS (generating a filesystem to be loaded as ramdisk), and on kernel-rt-4.19.59 (includes RT-PREEMT patch).&lt;br /&gt;
* In past GLAD development, a platform abstraction layer was developed in order to separate platform dependent code (e.g., threads creation, interruption management, POSIX calls, call to drivers). This layer has been already updated to cover RT-Linux target.&lt;br /&gt;
* A preliminary version of the driver for making available jamming and spoofing events has been already developed and tested.&lt;br /&gt;
* A logger system has been updated and sent together the GLAD+ HW/SW platform ACORDE to the drone integrator in construction use case (UC2-demo1). ACORDE generated documentation for integration and supported the integrator in what resulted a smooth and quick integration.&lt;br /&gt;
* The integrator performed flight tests. ACORDE supported the integrator with additional documentation (i.e., for operation and tests of the integration, and for indicating specific maneuvers to let validation tests cover as many working conditions as possible).&lt;br /&gt;
* With that information, ACORDE has done some preliminary evaluation of the current algorithms, and tested the potential of some improvements, i.e.., multi-constellation support. Algorithmic improvement is in progress.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_2_02.png|frame|center|New HW/SW platform for the ACORDE outdoor geo-referencing system and integration on a drone platform int he COMP4DRONES for the outdoor demo of the construction use case]]&lt;br /&gt;
&lt;br /&gt;
==Contribution and Improvements==&lt;br /&gt;
&lt;br /&gt;
GLAD+ is expected to bring important improvements or contributions that can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* More interoperability, given by the support of a Mavlink interface for providing the position estimates.&lt;br /&gt;
* Security features, enabled by the anti-jamming and anti-spoofing capabilities&lt;br /&gt;
* Lesser cost, a validated Linux-based port implementation means an important license cost saving with regard GLAD implementation.&lt;br /&gt;
* Better performance (higher resilience, precision, and integrity) of the positioning solution (including attitude).&lt;br /&gt;
* A proposal of smooth Mavlink extension to provide all attitude components, and to report jamming and spoofing events.&lt;br /&gt;
&lt;br /&gt;
In addition to the own improvements associated to GLAD+, ACORDE has gained useful knowhow for smoothly targeting fusion algorithms to different low-cost COTS receivers. &lt;br /&gt;
This enables ACORDE to provide low-cost positioning solutions with less dependency on COTS suppliers, of great importance as show by the COVID related lock down. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure below shows the boot of the custom RT Linux distribution developed by ACORDE for GLAD+ platform. As can be seen, the kernel boots in little bit more 3 seconds (time labels are relative to kernel start). Taking into account the bootloader (not shown in the capture) took around4-5s, it leads to ~8s for booting the position&amp;amp;attitude estimation application (actually, the boot process goes on to get Ethernet link ready and launching SSH services, however, they are used for configuration or debugging, and the position&amp;amp;attitude application is launched before triggering). Further tests were conducted. Different resolution timers (from 100 to 1000 Hz) were tested. Moreover, the latencies of the scheduler (context switches) were estimated under heavy workload conditions, relying on the “cyclictest” [31] and “hackbench” [32] standard Linux utilities. An average latency 41 us, with 72 us maximum latency was obtained. This is a key figure for tick timer setting. For instance, 20 context-switches per second would take 1.4ms max. overhead, and less than 1ms on average, which seems affordable for GLAD+ application margins. Further study with final GLAD+ firmware is still required though.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_2_03.png|frame|center|Some results of the activity on design and development of GLAD+ in COMP4DRONES]]&lt;br /&gt;
&lt;br /&gt;
Figure b) above shows the results of some preliminary analysis enabled by the data log from the integration tests of Dec. 2020. That test was performed in static conditions in front of the facilities of the integrator (FADA-CATEC). Specifically, Figure 67b) shows three stacked graphics with the three components of a “tail-head” baseline estimation, fundamental pre-processing for attitude estimation (heading and pitch components can be directly derived via a simple formula). The top one is a non-causal estimate, and thus only possible after offline post-processing, which is taken as a ground truth reference. Green colors reflect convergence of the ambiguity resolution algorithms (and thus resembles a precise estimate), while orange reflect no-convergence, and thus no-valid, in general, inaccurate estimate. The bottom graphic shows a “forward” (i.e., that can be computed in real-time) estimate of the baseline using only GPS constellation. As can be seen, most of the capture (97.9%) lacks convergence. The problem is related to the buildings around the drone at the capture time, which shadowed several satellites of the GPS constellation. The graphic on the middle, shows a forward estimate of the baseline using both GPS and Galileo constellations, as enabled by the GLAD+ HW/SW platform. This estimate gets the same 97.7% figure, but of convergence time, indeed very close to the 98.3% time achieved with non-causal processing.&lt;br /&gt;
&lt;br /&gt;
==Design and Implementation==&lt;br /&gt;
&lt;br /&gt;
As well as the significant improvements in low-cost position and attitude estimation  i.e., GLAD+, in COMP4DRONES, ACORDE has progressed towards a qualitative enhancement of its design procedures. See more details in [[WP6-ESDE]].&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1126</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1126"/>
		<updated>2023-03-14T12:26:53Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morphology and density of the anchor deployment, and on the base range accuracy.&lt;br /&gt;
A good example is what has been observed with autopositioning.&lt;br /&gt;
In the ACORDE IPS solution, autopositioning is a feature which enables anchors inside the tunnel to compute their own position from external or  already positioned anchors. &lt;br /&gt;
On Y axis, the positioning error is shown along time (x axis).&lt;br /&gt;
&lt;br /&gt;
In the figure below, each coloured graph line corresponds to the autopositioning error of one anchor for a naive deployment and using version 2 of anchors functionality.&lt;br /&gt;
In such deployment, there are three static external anchors, whose autopositionin errors correspond to he three 'foreground' in the graph.&lt;br /&gt;
These external anchor  are lmost perfectly positioned from the beginning. Figure shows the progressive autopositioning of the inner anchors.&lt;br /&gt;
The deeper the anchor (lines behind in the graph) the later the first autopositioning.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=600px heights=600px &amp;gt;&lt;br /&gt;
File: wp4_17_autopositioning_error0.png | ideal ranging conditions&lt;br /&gt;
File: wp4_17_autopositioning_error.png | realistic ranging errors (5cm)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Moreover, the figure also shows other expected effects, like growing errors with the depth in the tunnel.&lt;br /&gt;
More remarkably, the figure above also shows how the auto-positioning feature is impacted when realistic error range errors are considered.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1125</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1125"/>
		<updated>2023-03-14T12:25:51Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morphology and density of the anchor deployment, and on the base range accuracy.&lt;br /&gt;
A good example is what has been observed with autopositioning.&lt;br /&gt;
In the ACORDE IPS solution, autopositioning is a feature which enables anchors inside the tunnel to compute their own position from external or  already positioned anchors. &lt;br /&gt;
On Y axis, the positioning error is shown along time (x axis).&lt;br /&gt;
&lt;br /&gt;
In the figure below, each coloured graph line corresponds to the autopositioning error of one anchor for a naive deployment and using version 2 of anchors functionality.&lt;br /&gt;
In such deployment, there are three static external anchors, whose autopositionin errors correspond to he three 'foreground' in the graph.&lt;br /&gt;
These external anchor  are lmost perfectly positioned from the beginning. Figure shows the progressive autopositioning of the inner anchors.&lt;br /&gt;
The deeper the anchor (lines behind in the graph) the later the first autopositioning.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=600px heights=600px &amp;gt;&lt;br /&gt;
File: wp4_17_autopositioning_error0.png | ideal ranging conditions&lt;br /&gt;
File: wp4_17_autopositioning_error.png | realistic ranging errors (5cm)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Moreover, the figure also shows other expected effects, like growing errors with the depth in the tunnel.&lt;br /&gt;
More remarkably, the figure above also shows how the auto-positioning feature is impacted when realistic error range errors are considered.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1124</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1124"/>
		<updated>2023-03-14T12:16:06Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morphology and density of the anchor deployment, and on the base range accuracy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=600px heights=600px &amp;gt;&lt;br /&gt;
File: wp4_17_autopositioning_error0.png | ideal ranging conditions&lt;br /&gt;
File: wp4_17_autopositioning_error.png | realistic ranging errors (5cm)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For instance, figure above shows how the auto-positioning feature of the anchors is impacted when realistic error range errors are considered, using version 2 of anchors functionality.&lt;br /&gt;
In the ACORDE IPS solution, autopositioning is a feature which enables anchors inside the tunnel to compute their own position from external or  already positioned anchors. &lt;br /&gt;
On Y axis, the positioning error is shown along time (x axis). In this figure, each coloured graph line correspondd to the error of one anchor in a deployment were the three former (foreground)&lt;br /&gt;
lines corresponde to external anchors (almost perfectly positioned from the beginning). What figure shows is the progressive autopositioning of anchors along time (the deeper the later).&lt;br /&gt;
Moreover, it also shows some growing errors with the depth in the tunnel, specially in the former times (while not all the anchors are available for autopositioning).&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_autopositioning_error0.png&amp;diff=1123</id>
		<title>File:Wp4 17 autopositioning error0.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_autopositioning_error0.png&amp;diff=1123"/>
		<updated>2023-03-14T12:15:03Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1122</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1122"/>
		<updated>2023-03-14T12:14:46Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morphology and density of the anchor deployment, and on the base range accuracy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=400px heights=400px &amp;gt;&lt;br /&gt;
File: wp4_17_autopositioning_error0.png | ideal ranging conditions&lt;br /&gt;
File: wp4_17_autopositioning_error.png | realistic ranging errors (5cm)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For instance, figure above shows how the auto-positioning feature of the anchors is impacted when realistic error range errors are considered, using version 2 of anchors functionality.&lt;br /&gt;
In the ACORDE IPS solution, autopositioning is a feature which enables anchors inside the tunnel to compute their own position from external or  already positioned anchors. &lt;br /&gt;
On Y axis, the positioning error is shown along time (x axis). In this figure, each coloured graph line correspondd to the error of one anchor in a deployment were the three former (foreground)&lt;br /&gt;
lines corresponde to external anchors (almost perfectly positioned from the beginning). What figure shows is the progressive autopositioning of anchors along time (the deeper the later).&lt;br /&gt;
Moreover, it also shows some growing errors with the depth in the tunnel, specially in the former times (while not all the anchors are available for autopositioning).&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1121</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1121"/>
		<updated>2023-03-14T12:14:10Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morphology and density of the anchor deployment, and on the base range accuracy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_autopositioning_error.png | ideal ranging conditions&lt;br /&gt;
File: wp4_17_rg2.png | realistic ranging errors (5cm)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For instance, figure above shows how the auto-positioning feature of the anchors is impacted when realistic error range errors are considered, using version 2 of anchors functionality.&lt;br /&gt;
In the ACORDE IPS solution, autopositioning is a feature which enables anchors inside the tunnel to compute their own position from external or  already positioned anchors. &lt;br /&gt;
On Y axis, the positioning error is shown along time (x axis). In this figure, each coloured graph line correspondd to the error of one anchor in a deployment were the three former (foreground)&lt;br /&gt;
lines corresponde to external anchors (almost perfectly positioned from the beginning). What figure shows is the progressive autopositioning of anchors along time (the deeper the later).&lt;br /&gt;
Moreover, it also shows some growing errors with the depth in the tunnel, specially in the former times (while not all the anchors are available for autopositioning).&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1120</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1120"/>
		<updated>2023-03-14T12:02:54Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morophology and density of the anchors, and on the base range accuracy.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_autopositioning_error.png|frame|center|Autopositioning error for v2 anchors functionality for realistic ranging errors]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_autopositioning_error.png&amp;diff=1119</id>
		<title>File:Wp4 17 autopositioning error.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_autopositioning_error.png&amp;diff=1119"/>
		<updated>2023-03-14T12:02:23Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1118</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1118"/>
		<updated>2023-03-14T12:02:10Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morophology and density of the anchors, and on the base range accuracy.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_autopositioning_error.png|frame|center|Autopositioning error for v2 anchors functionality for realistic ranging errors]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1117</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1117"/>
		<updated>2023-03-14T11:59:28Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance: Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, d) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_outdoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morophology and density of the anchors, and on the base range accuracy.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1116</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1116"/>
		<updated>2023-03-14T11:58:27Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance : Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance : Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, c) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4_17_oudoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morophology and density of the anchors, and on the base range accuracy.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1115</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1115"/>
		<updated>2023-03-14T11:57:52Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance : Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance : Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, c) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
Furthermore, several indoor and outdoor physical set ups for range maximum range and accuracy estimation were set up.&lt;br /&gt;
Following figure shows on of the outdoor set ups. For those set ups, two different ground truth references where used, namely RTK measurements (as shown on the right part), &lt;br /&gt;
and also laser meters (i.e., outdoor experiments were indeed used to observed limitations of the used laser meters). &lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_oudoor_meas.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In all the experiments reported the cm-level error was confirmed, being the std error below 15cm in all experiments (including the original ones with the evaluation kit hw platform and others without final calibration). Las indoor experiment (for distances between 4m and 15m) yield maximum 1.7cm std error, and 10.1cm maximum RMSE.&lt;br /&gt;
&lt;br /&gt;
With regard geo-positioning algorityms, by the formal end of the project they have been mostly tested by realying on IPS-MAF platform.&lt;br /&gt;
It has served to realise the high dependency with the morophology and density of the anchors, and on the base range accuracy.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_outdoor_meas.png&amp;diff=1114</id>
		<title>File:Wp4 17 outdoor meas.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_outdoor_meas.png&amp;diff=1114"/>
		<updated>2023-03-14T11:47:23Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1113</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1113"/>
		<updated>2023-03-14T11:44:03Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance : Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance : Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The a) scenario represents an ideal case and serves to show the analytical equivalence of the considered formulations.&lt;br /&gt;
The b) scenario shows that for an averave drift on a platform with crystal clocks, a minor reply time unbalance, will already mean a significant range error (0.5m at 10mm distance) for 'formula2'.&lt;br /&gt;
The c) scenario shows that considering a further, but quite feasible unbalance (100us), the error at 100m becomes 5m, yet 0.5m for 10m for 'formula2'. &lt;br /&gt;
Then, c) scenario shows that even under consideration of some already provided platform inprovements (TCXO clock), the aforementioned error magnitude for 'formula2' holds, while 'formula1' remains insensitive.&lt;br /&gt;
Therefore, the selection of the proper formulation ('formula1') is critical for error free range estimations.&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms)&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1112</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1112"/>
		<updated>2023-03-14T11:37:27Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
At the '''user application level''' the following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
At the &amp;quot;ranging layer&amp;quot;, as mentioned, ACORDE realised the importance on not only implementing, byt selecting and appropriate Two-Way Ranging (TWR) scheme.&lt;br /&gt;
The following figure shows how two different TWR formulations were evaluated for four scenarios accounting tow typical error sources:&lt;br /&gt;
&lt;br /&gt;
* The error frequency of both the initiator and responder clocks (Δfi, Δfr, in parts per million, PPM)&lt;br /&gt;
* The unbalancing on the reply times (Δt_reply). &lt;br /&gt;
&lt;br /&gt;
From these two error sources, four scenarios are defined:&lt;br /&gt;
 a) an ideal case: Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
 b) average crystal frequency drifts crystal and minor reply time unbalance: Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
 c) average crystal frequency drifts crystal and feasible unbalance : Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
 d) average TCXO frequency drifts crystal and feasible unbalance : Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | ideal case&lt;br /&gt;
File: wp4_17_rg2.png | average crystal frequency drifts crystal and minor reply time unbalance&lt;br /&gt;
File: wp4_17_rg3.png | average crystal frequency drifts crystal and feasible unbalance&lt;br /&gt;
File: wp4_17_rg4.png | average TCXO frequency drifts crystal and feasible unbalance&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms)&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1111</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1111"/>
		<updated>2023-03-14T10:32:56Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Validation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png | Δfi=0, Δfr=0, Δt_{reply}=0&lt;br /&gt;
File: wp4_17_rg2.png | Δfi=50PPM, Δfr=-50PPM, Δtreply=10µs&lt;br /&gt;
File: wp4_17_rg3.png | Δfi=50PPM, Δfr=-50PPM, Δtreply=100µs&lt;br /&gt;
File: wp4_17_rg4.png | Δfi=4PPM, Δfr=-4PPM, Δtreply=100µs&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1110</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1110"/>
		<updated>2023-03-14T10:15:07Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
==Validation==&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png |  fi=0, fr=0, treply=0&lt;br /&gt;
File: wp4_17_rg2.png | &lt;br /&gt;
File: wp4_17_rg3.png | &lt;br /&gt;
File: wp4_17_rg4.png | &lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1109</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1109"/>
		<updated>2023-03-14T10:14:20Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: wp4_17_rg1.png |  fi=0, fr=0, treply=0&lt;br /&gt;
File: wp4_17_rg2.png | &lt;br /&gt;
File: wp4_17_rg3.png | &lt;br /&gt;
File: wp4_17_rg4.png | &lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg4.png&amp;diff=1108</id>
		<title>File:Wp4 17 rg4.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg4.png&amp;diff=1108"/>
		<updated>2023-03-14T10:13:10Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg3.png&amp;diff=1107</id>
		<title>File:Wp4 17 rg3.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg3.png&amp;diff=1107"/>
		<updated>2023-03-14T10:12:41Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg2.png&amp;diff=1106</id>
		<title>File:Wp4 17 rg2.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg2.png&amp;diff=1106"/>
		<updated>2023-03-14T10:11:04Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg1.png&amp;diff=1105</id>
		<title>File:Wp4 17 rg1.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4_17_rg1.png&amp;diff=1105"/>
		<updated>2023-03-14T10:10:43Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1104</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1104"/>
		<updated>2023-03-14T10:10:13Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: WP4_17_rg1.png |  fi=0, fr=0, treply=0&lt;br /&gt;
File: WP4_17_rg2.png | &lt;br /&gt;
File: WP4_17_rg3.png | &lt;br /&gt;
File: WP4_17_rg4.png | &lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1103</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1103"/>
		<updated>2023-03-14T10:01:54Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1102</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1102"/>
		<updated>2023-03-14T09:59:49Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* A first version of CCM in place&lt;br /&gt;
* Selection and implementation of development of a TWR ranging scheme&lt;br /&gt;
* Development of two versions of positioning algorithms&lt;br /&gt;
* Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1101</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1101"/>
		<updated>2023-03-13T17:29:08Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
* CCM &lt;br /&gt;
•	Selection and implementation of development of ranging scheme&lt;br /&gt;
•	Development of two versions of positioning algorithms&lt;br /&gt;
•	Service for local and remote control, configuration and monitoring (CCM)&lt;br /&gt;
&lt;br /&gt;
The following figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;br /&gt;
&lt;br /&gt;
(TBC: comments on positioning algorithms, on ranging scheme)&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1100</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1100"/>
		<updated>2023-03-13T17:27:07Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The followinf figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1099</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1099"/>
		<updated>2023-03-13T17:26:54Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The followinf figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_02_03.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1098</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1098"/>
		<updated>2023-03-13T17:07:16Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Contributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
The efforts invested in WP4 for the uppers layers of the ACORDE IPS solution have been fruitful in the afore introduced layers. &lt;br /&gt;
&lt;br /&gt;
They can be sum up as follows:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The followinf figure provides an example where ACORDE validated the possibility to remotely configure, control and monitor the node.&lt;br /&gt;
[[File:wp4-17_02_03.png|frame|center|An example of remote configuration, control and monitoring (CCM) of an UWB node of the ACORDE IPS]]&lt;br /&gt;
In first place, a show command is issued to read the node status (monitoring). Then the position of the UWB anchor is manually configured, and then the node is reseted to ensure new configuration is applied (monitoring and control). Finally, a new show command is issued to check the effectivity of the CCM sequence.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4-17_02.png&amp;diff=1097</id>
		<title>File:Wp4-17 02.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4-17_02.png&amp;diff=1097"/>
		<updated>2023-03-13T17:01:24Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1096</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1096"/>
		<updated>2023-03-13T17:00:12Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Improvements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Contributions==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1095</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1095"/>
		<updated>2023-03-13T16:59:20Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
* '''Upper application layers''', in charge of I/O interfacing (e.g. support of Mavlink API) and configuration.&lt;br /&gt;
* '''geo-positioning''', which includes geo-positioning via trilateration and fusion techniques in general&lt;br /&gt;
* '''ranging''', in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1094</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1094"/>
		<updated>2023-03-13T16:57:13Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The layers addressed are: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Application: basically the geo-positioning, which includes trilateration, and fusion techniques in general&lt;br /&gt;
* ranging: in charge of computation of ranges derived from the time metrics derived from UWB message exchages&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1093</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1093"/>
		<updated>2023-03-13T16:47:25Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES, as described in the figure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1092</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1092"/>
		<updated>2023-03-13T16:47:02Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
The following figure shows the several software layers present on top of the HW anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution (IPS) addressed.&lt;br /&gt;
&lt;br /&gt;
The development of the ACORDE IPS has required actions and developments on all these layers. &lt;br /&gt;
Some of these layers have been tackled on other project WPs:&lt;br /&gt;
* BSP set up (in [[WP3)-15-1]], which includes drivers and RTOS adaptation/configuration&lt;br /&gt;
* Medium Access Control protocol (in [[WP5-19_ACO]]), where acorde has made specific innovation.&lt;br /&gt;
&lt;br /&gt;
The higher software levels of the soltions have been addressed in the context of the WP4 of COMP4RDRONES.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1091</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1091"/>
		<updated>2023-03-13T16:40:33Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Improvements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
Following figure shows the software layers of the anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution addressed in the context of the WP4 of COMP4RDRONES.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1090</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1090"/>
		<updated>2023-03-13T16:40:17Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
Following figure shows the software layers of the anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution addressed in the context of the WP4 of COMP4RDRONES.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp4-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp4-17_01.png&amp;diff=1089</id>
		<title>File:Wp4-17 01.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp4-17_01.png&amp;diff=1089"/>
		<updated>2023-03-13T16:39:34Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1088</id>
		<title>WP4-17</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP4-17&amp;diff=1088"/>
		<updated>2023-03-13T16:38:46Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Detailed Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anchor&amp;amp;Tag firmware of the Indoor Positioning System==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP4-17&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Indoor Positioning System anchor and tag platforms [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation data (position)&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver. RTK enabled positioning out of the tunnel. INS data (on the tag).	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| &lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
|   Parent Building block		|| [[WP3-15_1]]&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This page introduced the software developed for Indoor Positioning solution developed by ACORDE in COMP4DRONES.&lt;br /&gt;
It includes tag and anchor firmware (application and other underlying levels).&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
Following figure shows the software layers of the anchor&amp;amp;tag devices of the ACORDE Indoor Positioning Solution addressed in the context of the WP4 of COMP4RDRONES.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:wp5-17_01.png|frame|center|Software Layers addressed in WP4 of C4D]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Detailed description of Anchor and Tag software...&lt;br /&gt;
&lt;br /&gt;
TBC&lt;br /&gt;
[[File:wp3-15_1_03.png|frame|center|Some results at the current status of ACORDE IPS system development]]&lt;br /&gt;
&lt;br /&gt;
==Improvements==&lt;br /&gt;
&lt;br /&gt;
Anchor and tag algorithms are key for the performance of the ACORDE IPS solution for the special requirements and characteristics of indoor infrastructures and positioning requirements posed for the construction use case of COMP4DRONES:&lt;br /&gt;
&lt;br /&gt;
TBC&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1087</id>
		<title>WP3-15 1</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1087"/>
		<updated>2023-03-13T16:34:24Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Anchor at Tag platforms */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=UltraWideBand (UWB) based indoor positioning=&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP3-15_1&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Platform, Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Energy, Raw sensed data from UWB transceiver and IMU&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation Sensor&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver and low-cost INS	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| UWB-based indoor positioning system&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_01.png|frame|center|Building block diagram for WP3-15_1]]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
In COMP4DRONES, ACORDE has tackled the design and developmentof of an Indoor Positioning System (IPS), as a solution for the challenges posed by the construction use case, demo tunnel (UC2-demo 2). ACORDE IPS can be considered a specific instantiation of the building block of C4D architecture shown above. ACORDE IPS is specifically oriented to serve reliable and precise geo-referenced position to a drone flying on a tunnel under construction. Such a drone is in charge of the capture of raw data for tunnel digitization, to be employed for Building Information Modelling or [https://en.wikipedia.org/wiki/Building_information_modeling &amp;quot;BIM&amp;quot;]. The objective of the ACORDE IPS is two-fold, i.e., to ensure a safe navigation along a planned path, and to optimize the accuracy of the navigation data synchronized with the data sensed for digitisalization(e.g.,  thermography or LIDAR), which can be exploited, for instance, for a faster offline digitalization. The specific environment and the usage scenario posed by the construction stakeholder (ACCIONA) and the drone integrator&amp;amp;operator (FADA-CATEC in C4D), configures a set of requirements in terms of cost of the solution, power consumption, size, weight, precision, and interface capabilities, which, added to the specific geometry of the indoor infrastructure, has lead ACORDE to a novel IPS solution, outlined the following  figure.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_02.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
The solution relies on a “tag node”, to be mounted on the drone, and to provide to it to the geo-reference position, based on a set of measured distances (called ranges) to a set of strategically deployed “anchor nodes”. Range estimation is based on a specific protocol of message exchanges on the Ultrawideband (UWB) spectrum. The tag integrates an INS, so that it can fuse INS information with UWB ranges, for providing a processed tag position. In addition, the tag can also provide at its output interface range data. A standard Mavlink interface supports the provision of these data to the drone navigation system.&lt;br /&gt;
The posed solution contributes improvements and innovations accounting the scenario and the current state of the art. ACORDE provides a vertical solution, covering the  design&amp;amp;implementation of the solution (anchor&amp;amp;tags platforms and their firmware). In addition, a specific design tool, IPS Modellign and Analysis Framework ([[WP6-21|IPS-MAF]]), has been developed, which allows to perform a more holistic and efficient analysis and design of this specific type of solutions. All this activity, has been comprised by technical packages WP3-WP6 in C4D, which can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* Design and implementation of anchor and tag platforms (including the required board support package (BSP) ([[WP3-15_1]]).&lt;br /&gt;
* Design and implementation of anchor and tag firmware, including the configuration, positioning algorithms and interfacing ([[WP4-17]]).&lt;br /&gt;
* Ensuring a robust and enriched communication among anchors, and among the tag (within the drone) and the anchors, for a more robust and improved positioning ([[WP5-19_ACO]]).&lt;br /&gt;
* Developing an Indoor Positioning System Modelling and Analysis Framework (IPS-MAF) for indoor structures, specifically tunnels ([[WP6-21|IPS-MAF]]).&lt;br /&gt;
* Providing at the tag a Mavlink [29] interface to support providing both processed positioning information, and “pre-processed” information (ranges) (WP3, WP4, and WP5).&lt;br /&gt;
&lt;br /&gt;
==Challenges and Contributions ==&lt;br /&gt;
&lt;br /&gt;
The stakeholder (ACCIONA) described the digitization scenario at a specific time slot where the construction 7days/24hours activity stopped for 1-2hours. At that time, it is possible to set up some “mobile” anchors, together with the “fixed” anchors, and later let the drone perform a pre-programmed digitization flight, where the tunnel under-construction can present some eventual obstacles (e.g., machines, signals). The posed scenario presents '''several challenges''' in relation to other existing real-time location systems:&lt;br /&gt;
&lt;br /&gt;
* The specific ''long geometry'' of the tunnel (which challenges UWB range estimation, the cost of the solution and the validity of conventional trilateration algorithms).&lt;br /&gt;
* Demand of features for a flexible and agile anchor deployment, which does not oblige surveyors to geo-positioning all anchors, especially mobile ones.&lt;br /&gt;
* Need to provide real-time, 3D geo-referenced positioning on the tag (while most solutions focus on 2D relative positioning, commonly computed on a ground platform which centralizes data from anchors).&lt;br /&gt;
* Cost and energy/power optimization (the latter important for fixed anchors)&lt;br /&gt;
* Need for system-level design tooling. The IPS is a complex system with many parameters and aspects (specific deployment, transmission powers, sensitivities, latencies of the ranging phases, algorithmic alternatives, etc) with potential significant impact on the overall performance. Means for facilitating a holistic design, accounting for those many different aspects at early design stage are required even for experienced designers in the field.&lt;br /&gt;
&lt;br /&gt;
The same scenario also presented the opportunity to exploit the fact that during digitization flight only one drone, i.e., one tag, needs to be serviced. The question is how to exploit this single-tag assumption for a safer flight and better digitalization.&lt;br /&gt;
&lt;br /&gt;
The ACORDE solution tackles these challenges and opportunities. So far, a number of '''contributions''' in comparison to other existing solutions are highlighted:&lt;br /&gt;
&lt;br /&gt;
* Customized, cost-effective anchor and tag platforms, specifically designed to cope with the computational needs (specially for tag) and energy/power efficiency needs (specially anchors).&lt;br /&gt;
* Novel MAC protocol called Asynchronous Tag trigger, Slotted Anchor response with Deterministic and Random Allocation (ATSA-DRA), specifically adapted to the single-tag assumption, that ensures deterministic latency, while optimizing the number of anchors in view.&lt;br /&gt;
* At application level, the solution enables geo-referenced, real-time 3D positioning. Moreover, the application overcomes the challenges of the tunnel geometry. A modified trilateration algorithm has been already developed which enables positioning in regions of limited anchors visibility (coverage) and poor dilution of precision (DOP), where a conventional least-squares based approach is not working. This is specifically required for enabling anchors auto-positioning at the initial phase.&lt;br /&gt;
* The development of IPS-MAF, is a qualitative step on ACORDE capabilities for tackling custom design of IPS systems for long indoor infrastructures (tunnels, mines, large pipes, …). It enables a newer system-level design flow (as explained in [[WP6-21]]), capable to reveal outcomes and aspects almost imposible to notice or tackle manually. &lt;br /&gt;
* The support of a Mavlink interface at the tag side, to provide both completely processed (e.g., position data) and partially processed (e.g., ranges). The latter enable the  ACORDE IPS to behave as a complementary positioning sub-system, whose outputs can be fused by integrators with other alternative sensor data. Moreover, ranges transfer is enabled via a “smooth” (in the form of dialect) Mavlink extension contributed by ACORDE in COMP4DRONES.&lt;br /&gt;
&lt;br /&gt;
==Anchor at Tag platforms==&lt;br /&gt;
In C4D ACORDE has performed a customized development for the anchor and tag platforms.&lt;br /&gt;
&lt;br /&gt;
On top of a base mother board design, the tag and the anchor platforms have been implemented. &lt;br /&gt;
Thanks to its I/O interfaces, the anchor platform supports the different types of anchor nodes defined for the solution, i.e.: &lt;br /&gt;
* an external ranging node&lt;br /&gt;
* an internal ranging node&lt;br /&gt;
* the Configuration, Control and Monitoring (CCM) node (this category can be applied to any of the previous&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_05b.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
For the same form factor, the base platform design brings several advantages in relation to devices found in the market:&lt;br /&gt;
* more estable clock&lt;br /&gt;
* LiPO connector&lt;br /&gt;
* better connectivity for configuration purposes&lt;br /&gt;
&lt;br /&gt;
Moreover, the tag platform adds a more powerful microcontroller, the possibility to add an INS for a powerful tag (capable to provide in real-time fused geo-location solution), and an SD card slot (e.g. to enableo local logging).&lt;br /&gt;
&lt;br /&gt;
Moreover, this development has provided ACORDE a strong technological base to further develop with greater flexibility the firmare of the positioning solution ([[WP4-17]]), &lt;br /&gt;
where much of the added value of the solution is concentrated.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1086</id>
		<title>WP3-15 1</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1086"/>
		<updated>2023-03-13T16:32:39Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Anchor at Tag platforms */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=UltraWideBand (UWB) based indoor positioning=&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP3-15_1&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Platform, Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Energy, Raw sensed data from UWB transceiver and IMU&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation Sensor&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver and low-cost INS	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| UWB-based indoor positioning system&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_01.png|frame|center|Building block diagram for WP3-15_1]]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
In COMP4DRONES, ACORDE has tackled the design and developmentof of an Indoor Positioning System (IPS), as a solution for the challenges posed by the construction use case, demo tunnel (UC2-demo 2). ACORDE IPS can be considered a specific instantiation of the building block of C4D architecture shown above. ACORDE IPS is specifically oriented to serve reliable and precise geo-referenced position to a drone flying on a tunnel under construction. Such a drone is in charge of the capture of raw data for tunnel digitization, to be employed for Building Information Modelling or [https://en.wikipedia.org/wiki/Building_information_modeling &amp;quot;BIM&amp;quot;]. The objective of the ACORDE IPS is two-fold, i.e., to ensure a safe navigation along a planned path, and to optimize the accuracy of the navigation data synchronized with the data sensed for digitisalization(e.g.,  thermography or LIDAR), which can be exploited, for instance, for a faster offline digitalization. The specific environment and the usage scenario posed by the construction stakeholder (ACCIONA) and the drone integrator&amp;amp;operator (FADA-CATEC in C4D), configures a set of requirements in terms of cost of the solution, power consumption, size, weight, precision, and interface capabilities, which, added to the specific geometry of the indoor infrastructure, has lead ACORDE to a novel IPS solution, outlined the following  figure.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_02.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
The solution relies on a “tag node”, to be mounted on the drone, and to provide to it to the geo-reference position, based on a set of measured distances (called ranges) to a set of strategically deployed “anchor nodes”. Range estimation is based on a specific protocol of message exchanges on the Ultrawideband (UWB) spectrum. The tag integrates an INS, so that it can fuse INS information with UWB ranges, for providing a processed tag position. In addition, the tag can also provide at its output interface range data. A standard Mavlink interface supports the provision of these data to the drone navigation system.&lt;br /&gt;
The posed solution contributes improvements and innovations accounting the scenario and the current state of the art. ACORDE provides a vertical solution, covering the  design&amp;amp;implementation of the solution (anchor&amp;amp;tags platforms and their firmware). In addition, a specific design tool, IPS Modellign and Analysis Framework ([[WP6-21|IPS-MAF]]), has been developed, which allows to perform a more holistic and efficient analysis and design of this specific type of solutions. All this activity, has been comprised by technical packages WP3-WP6 in C4D, which can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* Design and implementation of anchor and tag platforms (including the required board support package (BSP) ([[WP3-15_1]]).&lt;br /&gt;
* Design and implementation of anchor and tag firmware, including the configuration, positioning algorithms and interfacing ([[WP4-17]]).&lt;br /&gt;
* Ensuring a robust and enriched communication among anchors, and among the tag (within the drone) and the anchors, for a more robust and improved positioning ([[WP5-19_ACO]]).&lt;br /&gt;
* Developing an Indoor Positioning System Modelling and Analysis Framework (IPS-MAF) for indoor structures, specifically tunnels ([[WP6-21|IPS-MAF]]).&lt;br /&gt;
* Providing at the tag a Mavlink [29] interface to support providing both processed positioning information, and “pre-processed” information (ranges) (WP3, WP4, and WP5).&lt;br /&gt;
&lt;br /&gt;
==Challenges and Contributions ==&lt;br /&gt;
&lt;br /&gt;
The stakeholder (ACCIONA) described the digitization scenario at a specific time slot where the construction 7days/24hours activity stopped for 1-2hours. At that time, it is possible to set up some “mobile” anchors, together with the “fixed” anchors, and later let the drone perform a pre-programmed digitization flight, where the tunnel under-construction can present some eventual obstacles (e.g., machines, signals). The posed scenario presents '''several challenges''' in relation to other existing real-time location systems:&lt;br /&gt;
&lt;br /&gt;
* The specific ''long geometry'' of the tunnel (which challenges UWB range estimation, the cost of the solution and the validity of conventional trilateration algorithms).&lt;br /&gt;
* Demand of features for a flexible and agile anchor deployment, which does not oblige surveyors to geo-positioning all anchors, especially mobile ones.&lt;br /&gt;
* Need to provide real-time, 3D geo-referenced positioning on the tag (while most solutions focus on 2D relative positioning, commonly computed on a ground platform which centralizes data from anchors).&lt;br /&gt;
* Cost and energy/power optimization (the latter important for fixed anchors)&lt;br /&gt;
* Need for system-level design tooling. The IPS is a complex system with many parameters and aspects (specific deployment, transmission powers, sensitivities, latencies of the ranging phases, algorithmic alternatives, etc) with potential significant impact on the overall performance. Means for facilitating a holistic design, accounting for those many different aspects at early design stage are required even for experienced designers in the field.&lt;br /&gt;
&lt;br /&gt;
The same scenario also presented the opportunity to exploit the fact that during digitization flight only one drone, i.e., one tag, needs to be serviced. The question is how to exploit this single-tag assumption for a safer flight and better digitalization.&lt;br /&gt;
&lt;br /&gt;
The ACORDE solution tackles these challenges and opportunities. So far, a number of '''contributions''' in comparison to other existing solutions are highlighted:&lt;br /&gt;
&lt;br /&gt;
* Customized, cost-effective anchor and tag platforms, specifically designed to cope with the computational needs (specially for tag) and energy/power efficiency needs (specially anchors).&lt;br /&gt;
* Novel MAC protocol called Asynchronous Tag trigger, Slotted Anchor response with Deterministic and Random Allocation (ATSA-DRA), specifically adapted to the single-tag assumption, that ensures deterministic latency, while optimizing the number of anchors in view.&lt;br /&gt;
* At application level, the solution enables geo-referenced, real-time 3D positioning. Moreover, the application overcomes the challenges of the tunnel geometry. A modified trilateration algorithm has been already developed which enables positioning in regions of limited anchors visibility (coverage) and poor dilution of precision (DOP), where a conventional least-squares based approach is not working. This is specifically required for enabling anchors auto-positioning at the initial phase.&lt;br /&gt;
* The development of IPS-MAF, is a qualitative step on ACORDE capabilities for tackling custom design of IPS systems for long indoor infrastructures (tunnels, mines, large pipes, …). It enables a newer system-level design flow (as explained in [[WP6-21]]), capable to reveal outcomes and aspects almost imposible to notice or tackle manually. &lt;br /&gt;
* The support of a Mavlink interface at the tag side, to provide both completely processed (e.g., position data) and partially processed (e.g., ranges). The latter enable the  ACORDE IPS to behave as a complementary positioning sub-system, whose outputs can be fused by integrators with other alternative sensor data. Moreover, ranges transfer is enabled via a “smooth” (in the form of dialect) Mavlink extension contributed by ACORDE in COMP4DRONES.&lt;br /&gt;
&lt;br /&gt;
==Anchor at Tag platforms==&lt;br /&gt;
In C4D ACORDE has performed a customized development for the anchor and tag platforms.&lt;br /&gt;
&lt;br /&gt;
On top of a base mother board design, the tag and the anchor platforms have been implemented. &lt;br /&gt;
Thanks to its I/O interfaces, the anchor platform supports the different types of anchor nodes defined for the solution, i.e.: &lt;br /&gt;
- an external ranging node&lt;br /&gt;
- an internal ranging node&lt;br /&gt;
- the Configuration, Control and Monitoring (CCM) node (this category can be applied to any of the previous&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_05b.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
For the same form factor, the base platform design brings several advantages in relation to devices found in the market:&lt;br /&gt;
- more estable clock&lt;br /&gt;
- LiPO connector&lt;br /&gt;
- better connectivity for configuration purposes&lt;br /&gt;
&lt;br /&gt;
Moreover, the tag platform adds a more powerful microcontroller, the possibility to add an INS for a powerful tag (capable to provide in real-time fused geo-location solution), and an SD card slot (e.g. to enableo local logging).&lt;br /&gt;
&lt;br /&gt;
Moreover, this development has provided ACORDE a strong technological base to further develop with greater flexibility the firmare of the positioning solution ([[WP4-17]]), &lt;br /&gt;
where much of the added value of the solution is concentrated.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05b.png&amp;diff=1085</id>
		<title>File:Wp3-15 1 05b.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05b.png&amp;diff=1085"/>
		<updated>2023-03-13T16:26:09Z</updated>

		<summary type="html">&lt;p&gt;Acorde: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1084</id>
		<title>WP3-15 1</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1084"/>
		<updated>2023-03-13T16:24:57Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Anchor at Tag platforms */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=UltraWideBand (UWB) based indoor positioning=&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP3-15_1&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Platform, Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Energy, Raw sensed data from UWB transceiver and IMU&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation Sensor&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver and low-cost INS	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| UWB-based indoor positioning system&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_01.png|frame|center|Building block diagram for WP3-15_1]]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
In COMP4DRONES, ACORDE has tackled the design and developmentof of an Indoor Positioning System (IPS), as a solution for the challenges posed by the construction use case, demo tunnel (UC2-demo 2). ACORDE IPS can be considered a specific instantiation of the building block of C4D architecture shown above. ACORDE IPS is specifically oriented to serve reliable and precise geo-referenced position to a drone flying on a tunnel under construction. Such a drone is in charge of the capture of raw data for tunnel digitization, to be employed for Building Information Modelling or [https://en.wikipedia.org/wiki/Building_information_modeling &amp;quot;BIM&amp;quot;]. The objective of the ACORDE IPS is two-fold, i.e., to ensure a safe navigation along a planned path, and to optimize the accuracy of the navigation data synchronized with the data sensed for digitisalization(e.g.,  thermography or LIDAR), which can be exploited, for instance, for a faster offline digitalization. The specific environment and the usage scenario posed by the construction stakeholder (ACCIONA) and the drone integrator&amp;amp;operator (FADA-CATEC in C4D), configures a set of requirements in terms of cost of the solution, power consumption, size, weight, precision, and interface capabilities, which, added to the specific geometry of the indoor infrastructure, has lead ACORDE to a novel IPS solution, outlined the following  figure.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_02.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
The solution relies on a “tag node”, to be mounted on the drone, and to provide to it to the geo-reference position, based on a set of measured distances (called ranges) to a set of strategically deployed “anchor nodes”. Range estimation is based on a specific protocol of message exchanges on the Ultrawideband (UWB) spectrum. The tag integrates an INS, so that it can fuse INS information with UWB ranges, for providing a processed tag position. In addition, the tag can also provide at its output interface range data. A standard Mavlink interface supports the provision of these data to the drone navigation system.&lt;br /&gt;
The posed solution contributes improvements and innovations accounting the scenario and the current state of the art. ACORDE provides a vertical solution, covering the  design&amp;amp;implementation of the solution (anchor&amp;amp;tags platforms and their firmware). In addition, a specific design tool, IPS Modellign and Analysis Framework ([[WP6-21|IPS-MAF]]), has been developed, which allows to perform a more holistic and efficient analysis and design of this specific type of solutions. All this activity, has been comprised by technical packages WP3-WP6 in C4D, which can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* Design and implementation of anchor and tag platforms (including the required board support package (BSP) ([[WP3-15_1]]).&lt;br /&gt;
* Design and implementation of anchor and tag firmware, including the configuration, positioning algorithms and interfacing ([[WP4-17]]).&lt;br /&gt;
* Ensuring a robust and enriched communication among anchors, and among the tag (within the drone) and the anchors, for a more robust and improved positioning ([[WP5-19_ACO]]).&lt;br /&gt;
* Developing an Indoor Positioning System Modelling and Analysis Framework (IPS-MAF) for indoor structures, specifically tunnels ([[WP6-21|IPS-MAF]]).&lt;br /&gt;
* Providing at the tag a Mavlink [29] interface to support providing both processed positioning information, and “pre-processed” information (ranges) (WP3, WP4, and WP5).&lt;br /&gt;
&lt;br /&gt;
==Challenges and Contributions ==&lt;br /&gt;
&lt;br /&gt;
The stakeholder (ACCIONA) described the digitization scenario at a specific time slot where the construction 7days/24hours activity stopped for 1-2hours. At that time, it is possible to set up some “mobile” anchors, together with the “fixed” anchors, and later let the drone perform a pre-programmed digitization flight, where the tunnel under-construction can present some eventual obstacles (e.g., machines, signals). The posed scenario presents '''several challenges''' in relation to other existing real-time location systems:&lt;br /&gt;
&lt;br /&gt;
* The specific ''long geometry'' of the tunnel (which challenges UWB range estimation, the cost of the solution and the validity of conventional trilateration algorithms).&lt;br /&gt;
* Demand of features for a flexible and agile anchor deployment, which does not oblige surveyors to geo-positioning all anchors, especially mobile ones.&lt;br /&gt;
* Need to provide real-time, 3D geo-referenced positioning on the tag (while most solutions focus on 2D relative positioning, commonly computed on a ground platform which centralizes data from anchors).&lt;br /&gt;
* Cost and energy/power optimization (the latter important for fixed anchors)&lt;br /&gt;
* Need for system-level design tooling. The IPS is a complex system with many parameters and aspects (specific deployment, transmission powers, sensitivities, latencies of the ranging phases, algorithmic alternatives, etc) with potential significant impact on the overall performance. Means for facilitating a holistic design, accounting for those many different aspects at early design stage are required even for experienced designers in the field.&lt;br /&gt;
&lt;br /&gt;
The same scenario also presented the opportunity to exploit the fact that during digitization flight only one drone, i.e., one tag, needs to be serviced. The question is how to exploit this single-tag assumption for a safer flight and better digitalization.&lt;br /&gt;
&lt;br /&gt;
The ACORDE solution tackles these challenges and opportunities. So far, a number of '''contributions''' in comparison to other existing solutions are highlighted:&lt;br /&gt;
&lt;br /&gt;
* Customized, cost-effective anchor and tag platforms, specifically designed to cope with the computational needs (specially for tag) and energy/power efficiency needs (specially anchors).&lt;br /&gt;
* Novel MAC protocol called Asynchronous Tag trigger, Slotted Anchor response with Deterministic and Random Allocation (ATSA-DRA), specifically adapted to the single-tag assumption, that ensures deterministic latency, while optimizing the number of anchors in view.&lt;br /&gt;
* At application level, the solution enables geo-referenced, real-time 3D positioning. Moreover, the application overcomes the challenges of the tunnel geometry. A modified trilateration algorithm has been already developed which enables positioning in regions of limited anchors visibility (coverage) and poor dilution of precision (DOP), where a conventional least-squares based approach is not working. This is specifically required for enabling anchors auto-positioning at the initial phase.&lt;br /&gt;
* The development of IPS-MAF, is a qualitative step on ACORDE capabilities for tackling custom design of IPS systems for long indoor infrastructures (tunnels, mines, large pipes, …). It enables a newer system-level design flow (as explained in [[WP6-21]]), capable to reveal outcomes and aspects almost imposible to notice or tackle manually. &lt;br /&gt;
* The support of a Mavlink interface at the tag side, to provide both completely processed (e.g., position data) and partially processed (e.g., ranges). The latter enable the  ACORDE IPS to behave as a complementary positioning sub-system, whose outputs can be fused by integrators with other alternative sensor data. Moreover, ranges transfer is enabled via a “smooth” (in the form of dialect) Mavlink extension contributed by ACORDE in COMP4DRONES.&lt;br /&gt;
&lt;br /&gt;
==Anchor at Tag platforms==&lt;br /&gt;
In C4D ACORDE has performed a customized development for the anchor and tag platforms.&lt;br /&gt;
&lt;br /&gt;
On top of a base mother board design, the tag and the anchor platforms have been implemented. &lt;br /&gt;
The later, in turn supports the different types of anchor nodes defined for the solution. &lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_05b.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
For the same form factor, these  platforms have several benefits in relation to devices found in the market:&lt;br /&gt;
- more estable clock&lt;br /&gt;
- better connectivity for configuration purposes&lt;br /&gt;
- more powerful tag (capable to provide in real-time fused geo-location solution)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Moreover, this development has provided ACORDE a strong technological base to further develop with greater flexibility the firmare of the positioning solution ([[WP4-17]]), &lt;br /&gt;
where much of the added value of the solution is concentrated.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP6-21&amp;diff=1083</id>
		<title>WP6-21</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP6-21&amp;diff=1083"/>
		<updated>2023-03-13T16:22:13Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP6-21 (WP6-IPS-MAF)&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Tool&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Linux (or Windows+WSL), Libraries: PCL, Xerces, GeographicLib, Matplotlib&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Static and Dynamic (simulation based) of holistic model of Indoor Positioning System &lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| SystemC models of tag and anchor applications, XML-based description of the anchor deployment and other crucial parameters of the solution, of the configuration of the the analysis&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Static analysis outputs (Visibility, DOP, range for trcv configurations) and Dynamic analysis (accuracies, timing affected behaviour)&lt;br /&gt;
|-&lt;br /&gt;
|   C4D tooling		|| System-Level modelling and analysis&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 3&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
ACORDE IPS was motivated by the specific positioning needs and requirements for a drone flying on an large indoor scenario.&lt;br /&gt;
The need for considering different requirements, several aspects and levels of a Cyber-physical system (tunnel geometry, deployment of anchors, algorithms for 3D positioning, platform limitations, interfaces) made  early evident that a more holistic, model-based design was necessary.&lt;br /&gt;
It motivated the development of the '''IPS Modelling and Analysis Framework (IPS-MAF)''', which, as shown in the figure below, can be used from early design stages, to build up a holistic model of the IPS system. IPS-MAF can be used to analyse and decide key aspect at different levels of the indoor positioning system (deployment of the anchors, sensitivities and transmission powers, transmission frequencies, etc) while keeping a holistic view of the system.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_04.png|frame|center|IPS-MAF provides a qualitative step towards a holistic, model-based design of Indoor Positioning Solutions for long infrastructures]]&lt;br /&gt;
&lt;br /&gt;
That is, IPS-MAF enables a holistic model of the IPS, while integrating some functional actual pieces of the application, so in that sense it also enables to advance some part of the application development. Therefore IPS-MAF feeds the conventional platform development and embedded application development phases, where ACORDE has already long expertise. At the same time, the measurements and characterizations that can be derived and refined from platform and application development serve to feedback and polish the holistic model. Summing up, an extended system-level design flow has been enabled, after coupling IPS-MAF to conventional ACORDE development processes for platform development (which includes PCB design, mechanical design, drivers’ development, embedded application development) and application development (where ACORDE typically develops in C or C++, relying on some cross-development environment suited to a specific microcontroller).&lt;br /&gt;
&lt;br /&gt;
== IPS-MAF Architecture ==&lt;br /&gt;
&lt;br /&gt;
Following figure sketches the main architecture of IPS-MAF.&lt;br /&gt;
&lt;br /&gt;
[[File:ACORDE-IPS_MAF_Architecture.gif|800px]]&lt;br /&gt;
&lt;br /&gt;
IPS-MAF is composed by two main tools: &lt;br /&gt;
* The IPS-MAF Analyzer&lt;br /&gt;
* The IPS-MAF Visualizer&lt;br /&gt;
&lt;br /&gt;
=== IPS-MAF Analyzer ===&lt;br /&gt;
A main input to the IPS-MAF Analyzer is &amp;lt;u&amp;gt;a model of the anchor and tag applications&amp;lt;/u&amp;gt;. They are developed separately from the IPS-MAF tool as SystemC models. &lt;br /&gt;
This is convenient, as this description is very close to a final C/C++ implementation, while relying on a SystemC API enables a target independent and standard description.&lt;br /&gt;
Different application models can be separately developed and compiled and (dynamically) linked to the IPS-MAF Analysis tool. Such mapping is described in XML format.&lt;br /&gt;
&lt;br /&gt;
A set of XML files serves to specify such a mapping of tag and anchor applications, and other &amp;lt;u&amp;gt;main aspects&amp;lt;/u&amp;gt; (anchors deployment, tunnel geometry, main HW parameters like UWB transceivers configuration, tag dynamics) &amp;lt;u&amp;gt;of the IPS with large potential impact on performance&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
The analyses to be performed are also described in XML format.&lt;br /&gt;
&lt;br /&gt;
[[File:C4D_WP6_IPS_MAF_A_xml_deploy.png | 500px |center| Most input information is passed to IPS-MAF in XML format (anchors deployment in the image)]]&lt;br /&gt;
&lt;br /&gt;
The IPS-MAF Analyzer parses all this input information and links the tag and anchor application models and performs the described analyses. &lt;br /&gt;
Notice that, despite the dynamic, simulatio-based analysis relies on SystemC, none of the requested analysis requires any compilation. The IPS-MAF Analyizer can be seen (as is) a command line tool that reads some inputs and produce some outputs.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Static analysis&amp;lt;/u&amp;gt; comprise visibility of the anchors and [https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation) Dilution of Precision (DOP)] for any point of the infrastructure. It also comprises the analysis of the range  (and in general, of the link margin) for different configuration of transmitting and receiver configurations.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Dynamic analysis&amp;lt;/u&amp;gt; refers to the possibility to perform a simulation and extract out of it different type of metrics, such as estimated positions of the tag and anchors, and errors with regard to their real position.&lt;br /&gt;
&lt;br /&gt;
[[File:C4D_WP6_IPS_MAF_A_execution.png | 500px |center| Messages in console launched by IPS-MAF Analyzer]]&lt;br /&gt;
&lt;br /&gt;
Analysis configuration allows to select which specific outputs will be exported, in different formats (mostly, csv and KML for dynamic analysis). Some files are exported in other convenience formats (e.g., .pcd, png). All the outputs for a configured simulation are exported to an output folder, which can be controlled from the tool configuration too.&lt;br /&gt;
&lt;br /&gt;
=== IPS-MAF Visualizer ===&lt;br /&gt;
&lt;br /&gt;
The IPS-MAF Visualizer is a graphical front-end that takes as input the outputs produced by the IPS-MAF analyzer and show a 3D visualization of them. &lt;br /&gt;
It also uses some inputs to the IPS-MAF Analyzer (bypassed to the output folder), e.g. to visualize the tunnel model, anchors deployment, obstacles, flight plan.&lt;br /&gt;
&lt;br /&gt;
The IPS-MAF Visualizer supports the visualization of both, outputs of the static analyses, and of the dynamic analyses.&lt;br /&gt;
Following figures provide a &lt;br /&gt;
&lt;br /&gt;
Below, a sample of several types of visualizations of the static analysis outputs which can be performed with the IPS-MAF Visualizer are shown.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery  widths=300px heights=200px &amp;gt;&lt;br /&gt;
File: WP6_21_PDOP_analysis.png | PDOP analysis&lt;br /&gt;
File: WP6_21_HDOP_analysis.png | HDOP analysis&lt;br /&gt;
File: WP6_21_IPSMAF_obstacles.png | section visualization of PDOP analysis with obstacles in the tunnel&lt;br /&gt;
File: WP6_21_path_analysis.png | Analysis on flight plan (histogram visualization behind)&lt;br /&gt;
File: C4D_WP6_IPS_MAF_A_circle_section.png | HDOP analysis on a cicle section tunnel)&lt;br /&gt;
File: WP6_21_IPS_MAF_obstacle_shadow.png | Shadows revealed in VDOP analysis)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Status after C4D ==&lt;br /&gt;
&lt;br /&gt;
IPS-MAF is related to the ACORDE IPS, and its development has been triggered and done in the frame of/thanks to COMP4DRONES.&lt;br /&gt;
All the aforementioned features are supported with several demonstrative examples. &lt;br /&gt;
&lt;br /&gt;
It is remarkable that the outputs of the IPS-MAF simulations already served to detect issues when conventional least-squares algorithms were used, and to design and test the modified trilateration algorithm, even before the anchor or tag platforms were ready. IPS-MAF dynamic analysis revealed non-straightforward effects and outcomes as the one mentioned, difficult to advance with a manual analysis.&lt;br /&gt;
Similarly, for the static analysis. For instance, notice the “coverage” pattern in depending the type of DOP (PDOP vs HDOP) and the “shadow” provoked at the floor by obstacles oh the roof of the tunnel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Some demo videos will be made available before the end of the project.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05.png&amp;diff=1082</id>
		<title>File:Wp3-15 1 05.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05.png&amp;diff=1082"/>
		<updated>2023-03-13T16:19:49Z</updated>

		<summary type="html">&lt;p&gt;Acorde: Acorde reverted File:Wp3-15 1 05.png to an old version&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05.png&amp;diff=1081</id>
		<title>File:Wp3-15 1 05.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05.png&amp;diff=1081"/>
		<updated>2023-03-13T16:19:09Z</updated>

		<summary type="html">&lt;p&gt;Acorde: Acorde reverted File:Wp3-15 1 05.png to an old version&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1080</id>
		<title>WP3-15 1</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=WP3-15_1&amp;diff=1080"/>
		<updated>2023-03-13T16:15:36Z</updated>

		<summary type="html">&lt;p&gt;Acorde: /* Curent Status */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=UltraWideBand (UWB) based indoor positioning=&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  ID|| WP3-15_1&lt;br /&gt;
|-&lt;br /&gt;
|   Contributor	|| ACORDE&lt;br /&gt;
|-&lt;br /&gt;
|   Levels	|| Platform, Function&lt;br /&gt;
|-&lt;br /&gt;
|   Require	|| Energy, Raw sensed data from UWB transceiver and IMU&lt;br /&gt;
|-&lt;br /&gt;
|   Provide	|| Navigation Sensor&lt;br /&gt;
|-&lt;br /&gt;
|   Input	|| Raw sensed data from UWB transceiver and low-cost INS	&lt;br /&gt;
|-&lt;br /&gt;
|   Output	|| Position&lt;br /&gt;
|-&lt;br /&gt;
|   C4D building block		|| UWB-based indoor positioning system&lt;br /&gt;
|-&lt;br /&gt;
|   TRL		|| 4&lt;br /&gt;
|-&lt;br /&gt;
| Contact || fernando.herrera at acorde.com&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_01.png|frame|center|Building block diagram for WP3-15_1]]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
In COMP4DRONES, ACORDE has tackled the design and developmentof of an Indoor Positioning System (IPS), as a solution for the challenges posed by the construction use case, demo tunnel (UC2-demo 2). ACORDE IPS can be considered a specific instantiation of the building block of C4D architecture shown above. ACORDE IPS is specifically oriented to serve reliable and precise geo-referenced position to a drone flying on a tunnel under construction. Such a drone is in charge of the capture of raw data for tunnel digitization, to be employed for Building Information Modelling or [https://en.wikipedia.org/wiki/Building_information_modeling &amp;quot;BIM&amp;quot;]. The objective of the ACORDE IPS is two-fold, i.e., to ensure a safe navigation along a planned path, and to optimize the accuracy of the navigation data synchronized with the data sensed for digitisalization(e.g.,  thermography or LIDAR), which can be exploited, for instance, for a faster offline digitalization. The specific environment and the usage scenario posed by the construction stakeholder (ACCIONA) and the drone integrator&amp;amp;operator (FADA-CATEC in C4D), configures a set of requirements in terms of cost of the solution, power consumption, size, weight, precision, and interface capabilities, which, added to the specific geometry of the indoor infrastructure, has lead ACORDE to a novel IPS solution, outlined the following  figure.&lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_02.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
The solution relies on a “tag node”, to be mounted on the drone, and to provide to it to the geo-reference position, based on a set of measured distances (called ranges) to a set of strategically deployed “anchor nodes”. Range estimation is based on a specific protocol of message exchanges on the Ultrawideband (UWB) spectrum. The tag integrates an INS, so that it can fuse INS information with UWB ranges, for providing a processed tag position. In addition, the tag can also provide at its output interface range data. A standard Mavlink interface supports the provision of these data to the drone navigation system.&lt;br /&gt;
The posed solution contributes improvements and innovations accounting the scenario and the current state of the art. ACORDE provides a vertical solution, covering the  design&amp;amp;implementation of the solution (anchor&amp;amp;tags platforms and their firmware). In addition, a specific design tool, IPS Modellign and Analysis Framework ([[WP6-21|IPS-MAF]]), has been developed, which allows to perform a more holistic and efficient analysis and design of this specific type of solutions. All this activity, has been comprised by technical packages WP3-WP6 in C4D, which can be summarized as follows:&lt;br /&gt;
&lt;br /&gt;
* Design and implementation of anchor and tag platforms (including the required board support package (BSP) ([[WP3-15_1]]).&lt;br /&gt;
* Design and implementation of anchor and tag firmware, including the configuration, positioning algorithms and interfacing ([[WP4-17]]).&lt;br /&gt;
* Ensuring a robust and enriched communication among anchors, and among the tag (within the drone) and the anchors, for a more robust and improved positioning ([[WP5-19_ACO]]).&lt;br /&gt;
* Developing an Indoor Positioning System Modelling and Analysis Framework (IPS-MAF) for indoor structures, specifically tunnels ([[WP6-21|IPS-MAF]]).&lt;br /&gt;
* Providing at the tag a Mavlink [29] interface to support providing both processed positioning information, and “pre-processed” information (ranges) (WP3, WP4, and WP5).&lt;br /&gt;
&lt;br /&gt;
==Challenges and Contributions ==&lt;br /&gt;
&lt;br /&gt;
The stakeholder (ACCIONA) described the digitization scenario at a specific time slot where the construction 7days/24hours activity stopped for 1-2hours. At that time, it is possible to set up some “mobile” anchors, together with the “fixed” anchors, and later let the drone perform a pre-programmed digitization flight, where the tunnel under-construction can present some eventual obstacles (e.g., machines, signals). The posed scenario presents '''several challenges''' in relation to other existing real-time location systems:&lt;br /&gt;
&lt;br /&gt;
* The specific ''long geometry'' of the tunnel (which challenges UWB range estimation, the cost of the solution and the validity of conventional trilateration algorithms).&lt;br /&gt;
* Demand of features for a flexible and agile anchor deployment, which does not oblige surveyors to geo-positioning all anchors, especially mobile ones.&lt;br /&gt;
* Need to provide real-time, 3D geo-referenced positioning on the tag (while most solutions focus on 2D relative positioning, commonly computed on a ground platform which centralizes data from anchors).&lt;br /&gt;
* Cost and energy/power optimization (the latter important for fixed anchors)&lt;br /&gt;
* Need for system-level design tooling. The IPS is a complex system with many parameters and aspects (specific deployment, transmission powers, sensitivities, latencies of the ranging phases, algorithmic alternatives, etc) with potential significant impact on the overall performance. Means for facilitating a holistic design, accounting for those many different aspects at early design stage are required even for experienced designers in the field.&lt;br /&gt;
&lt;br /&gt;
The same scenario also presented the opportunity to exploit the fact that during digitization flight only one drone, i.e., one tag, needs to be serviced. The question is how to exploit this single-tag assumption for a safer flight and better digitalization.&lt;br /&gt;
&lt;br /&gt;
The ACORDE solution tackles these challenges and opportunities. So far, a number of '''contributions''' in comparison to other existing solutions are highlighted:&lt;br /&gt;
&lt;br /&gt;
* Customized, cost-effective anchor and tag platforms, specifically designed to cope with the computational needs (specially for tag) and energy/power efficiency needs (specially anchors).&lt;br /&gt;
* Novel MAC protocol called Asynchronous Tag trigger, Slotted Anchor response with Deterministic and Random Allocation (ATSA-DRA), specifically adapted to the single-tag assumption, that ensures deterministic latency, while optimizing the number of anchors in view.&lt;br /&gt;
* At application level, the solution enables geo-referenced, real-time 3D positioning. Moreover, the application overcomes the challenges of the tunnel geometry. A modified trilateration algorithm has been already developed which enables positioning in regions of limited anchors visibility (coverage) and poor dilution of precision (DOP), where a conventional least-squares based approach is not working. This is specifically required for enabling anchors auto-positioning at the initial phase.&lt;br /&gt;
* The development of IPS-MAF, is a qualitative step on ACORDE capabilities for tackling custom design of IPS systems for long indoor infrastructures (tunnels, mines, large pipes, …). It enables a newer system-level design flow (as explained in [[WP6-21]]), capable to reveal outcomes and aspects almost imposible to notice or tackle manually. &lt;br /&gt;
* The support of a Mavlink interface at the tag side, to provide both completely processed (e.g., position data) and partially processed (e.g., ranges). The latter enable the  ACORDE IPS to behave as a complementary positioning sub-system, whose outputs can be fused by integrators with other alternative sensor data. Moreover, ranges transfer is enabled via a “smooth” (in the form of dialect) Mavlink extension contributed by ACORDE in COMP4DRONES.&lt;br /&gt;
&lt;br /&gt;
==Anchor at Tag platforms==&lt;br /&gt;
In C4D ACORDE has performed a customized development for the anchor and tag platforms.&lt;br /&gt;
&lt;br /&gt;
On top of a base mother board design, the tag and the anchor platforms have been implemented. &lt;br /&gt;
The later, in turn supports the different types of anchor nodes defined for the solution. &lt;br /&gt;
&lt;br /&gt;
[[File:wp3-15_1_05.png|frame|center|Indoor Positioning System developed by ACORDE]]&lt;br /&gt;
&lt;br /&gt;
For the same form factor, these  platforms have several benefits in relation to devices found in the market:&lt;br /&gt;
- more estable clock&lt;br /&gt;
- better connectivity for configuration purposes&lt;br /&gt;
- more powerful tag (capable to provide in real-time fused geo-location solution)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Moreover, this development has provided ACORDE a strong technological base to further develop with greater flexibility the firmare of the positioning solution ([[WP4-17]]), &lt;br /&gt;
where much of the added value of the solution is concentrated.&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
	<entry>
		<id>https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05.png&amp;diff=1079</id>
		<title>File:Wp3-15 1 05.png</title>
		<link rel="alternate" type="text/html" href="https://c4d.lias-lab.fr/index.php?title=File:Wp3-15_1_05.png&amp;diff=1079"/>
		<updated>2023-03-13T16:14:50Z</updated>

		<summary type="html">&lt;p&gt;Acorde: Acorde uploaded a new version of File:Wp3-15 1 05.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Acorde</name></author>
	</entry>
</feed>