Thank you for contacting Intel Customer Support.
In order to understand your issue better, could you please answer a few questions?
Where did you fly the drone? What were the surroundings?
What distance were you from the drone?
we fly the drone indoor in an empty part of a factory hall. The floor below the UAV is even and neither shiny nor too light-absorbing.
But we face spikes in the measured distance also in different surroundings and independent of the current flight altitude. That's why we think the problem might be electromagnetic interferences in the wiring or on the peripheral connector board?
During the test I were standing between 2 or 3 meters away from the drone.
Thank you for your message.
Could you also tell me what firmware/software version are you using?
Are you following this guide: https://docs.px4.io/en/flight_controller/intel_aero.html ?
What is the output of the command get_aero_version.py ?
yes, I was following this guide.
Currenty the the px4 1.7.1 stable build is installed on the FCU.
The output of "$ get_aero_version.py" is:
BIOS_VERSION = Aero-01.00.13
OS_VERSION = Ubuntu 16.04.3 LTS"
AIRMAP_VERSION = unkown
FPGA_VERSION = 0xc2
AeroFC firmware version = unkown
Unfortunately, we don't have the sensor to run tests on it.
Are you able to test the sensor on Yocto software release 1.6.1?
In the guide you are following it is mentioned that it needs version 1.6.0 or later.
yes we still have spikes in the measurement data when connecting the LidarLite to the I2C pins of the telemetry port.
As we don't want to use Yocto on the Aero Compute Board I didn't test the sensor with the latest Yocto release.
Instead we connected the Lidar to a custom Cortex-M4 PCB and stream the measurement data from the PCB to the Aero Computation Board.
This solustion works well and without any spikes.