I connected the LIDAR Lite 3 to the AERO. And when checking in QGC, The topic DISTANCE_SENSOR is there and working normal except some noise.
I then ran the following commands from the terminal:
systemctl enable aero-optical-flow
systemctl status aero-optical-flow
and received the picture attached.
When looking in QGC on the widget QGroundControl>Widgets>MAVLink Inspector> ,
There is no topic named OPTICAL_FLOW_RAD.
the output of this command : get_aero_version.py is the second picture attached.
How can I fix my problem? In fact, I have two Aero Drones, and one is using PX4flow, so the second one should be equipped with Lidar as I excepted.
Thank you for your interest in the Intel Aero drone.
Your request has been received and is currently being investigated.
We will get back to you as soon as possible.
but I found that when I reboot my drone, optical flow works well. However then I shutdown it just for a full battery, and then power on, I got the same result as yesterday.
That's to say, sometimes it works but sometimes not.
And so I wondered, How on earth could I make it well?
Please try updating your Bios again, and also, from your first screenshot it look like the flight controller firmware shows as unknown.
Please flash your flight controller following these steps and then try again the optical flow:
Also make sure to follow the steps on Github for the optical flow and let me know what specific step are you having trouble with.
Hope this helps.
The bios version has recently been updated.
Please follow the steps here in order to update your Bios with the latest version:
When I update my BIOS, I get an error shown below. It seems that rpm can not use directly on ubuntu. So the command should be change as:
$: sudo dpkg -i
Is it that?
Is there any special parameters need to be added?
That is indeed correct, you need to convert it to a deb package using alien, although, you need to install the .16 package not the .13 one.
Download the latest bios from here: https://downloadcenter.intel.com/download/27399/Intel-Aero-Platform-for-UAVs-Installation-Files?v=t
and run this command:
sudo alien -d -i .rpm
Then you can run the aero-bios-update command and reboot your drone.
Thank you for bringing this to our attention. We will take steps to correct the documentation.
I'm not able to see the link you sent me.
If the error you are talking about has something to do with the architecture, you can follow these steps:
You need to modify the control file.
sudo alien -g package-name.rpm (this will generate a folder with the package contents) cd package-dir/ sudo nano debian/control
Now change the architecture (
i386 in my case) to be the one you need. For example, I added the
amd64 archicture and this is how the line ended up:
Architecture: i386, amd64
sudo debian/rules binary
This will produce the
Yes. the error I got was about the architecture. I found that you are talking about this issue:
And I did all you suggest there and got the same result with Coline.
As for FC firmware, so Must I reinstall ubuntu on my drone? you know, this means that I have to do all steps including installing some packages and so on. It is not difficult but time consuming.
Thank you for you help.
I understand it's time consuming, that's why I'm only suggesting this as a last resort.
Can you please provide me some screenshots with the output of this command:
sudo dpkg -i package-name.deb
and also the output when you try to flash the FC firmware?
In order to flash my BIOS, I followed these steps:
1. sudo alien -g aero-bios-01.00.16-r1.corei7_64.rpm
cd aero-bios-01.00.16/ (this step generated two folders, aero-bios-01.00.16 and aero-bios-01.00.16)
sudo gedit debian/control
sudo debian/rules binary
but I can't find .deb anywhere in the aero-bios-01.00.16 folder or the dir of home. So I try:
rpm2cpio aero-bios-01.00.16-r1.corei7_64.rpm | cpio -idmv
sudo mv BIOSUPDATE.fv /boot (also sudo cp /boot/BIOSUPDATE.fv /boot/efi/)
but when I reboot, the aero-get-version.py still returns Aero-01.00.13.
The output of flashing FC firmware is shown in the pictures.