Posts made by DavideColetti

@Moderator
We did two flight tests inside our office in a luminous environment. Temperature seems to be lower while flying (around 60°C), and voxl-camera-server didn't stop. Yet, we could not do extensive tests because in both cases the px4 changed the flight mode from Position to Stabilize for visual failures. We attach a screenshot from QGC.!!

Greetings,
we're trying to use the Seeker drone with docker, ros and mavros.
We managed to get the position with /mavros/local_position/odom, but after a while x and y values are fixed to 0.0. Only the z receives updates.
We checked the services on the drone and voxl-camera-server was not running. This is a problem that we had for some time now without a solution.
We flashed the SDK 0.9.5 according to this post https://forum.modalai.com/topic/1272/mavlink-odometry-x-y-value-0/63 in case of a mismatch, but this problem seems to persist.
After an apparently random amount of time, voxl-camera-server stops running.
How can we solve this?

system-image: 4.0.0
kernel: #1 SMP PREEMPT Thu Oct 13 17:57:05 UTC 2022 3.18.71-perf
hw: VOXL
voxl-site: 0.9.5

We attach a pic of the services we're using during these tests.

The tracking camera calibration worked flawlessly after using the seeker in softAP mode, disabling the dfs-server and using the correct checkboard.
Stereo camera calibration was much harder, and after many attempts there was always a failure in the exstrinsics calibration.
We configured /etc/modalai/extrinsics.conf following this guide https://docs.modalai.com/configure-extrinsics/ .

We tried manual control with Position flight mode and it worked fine. After we tried two simple autonomous flights with mavsdk inside docker, mainly using the set_position_ned() method.
http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/plugins/offboard.html#mavsdk.offboard.Offboard.set_position_ned

First mission: arm the drone, take off 1m from the ground, move forward 1.8m and then land.
This one ended pretty badly, with a drone crash. Mission was not followed at all.
The environment was an office sufficiently illuminated, and the Seeker drone started from the position where it was turned on.

Second mission (simpler): arm the drone, take off 1m from the ground, land.
In this one the drone took off around 2.5m from the ground, and then landed with relatively high speed, hitting the ground.

I don't know if it can be an issue but in both tests dfs-server was disabled.

Thanks for the fast reply.

Version informations:

Voxl Portal. Tof Depth and Tof Ir are always missing:

Calibration with "voxl-calibrate-camera stereo -s 5x7 -l 0.038" command. This time froze at 0% :

Voxl-inspect-services after calibration gets stuck:

I don't know if it can be relevant but voxl-camera-server usually has a CPU usage around 16-20, even when not armed.

Greetings,

We purchased a Modalai Seeker drone for indoor navigation a couple of months ago.
Overall we encountered many problems related to the cameras:

• voxl-camera-server crashes after few minutes from the power on
• qvio often shows low quality, eventually with short fails
• camera calibration gets stuck around 60% of the calibration process on the voxl portal, resulting in a camera server crash. We were not able to complete the calibration once.
• using Position flight mode, the drone is generally stable, but occasionally it loses control and would
  crash without a fast reaction from the pilot to make it land "safely".
• we were not able to make the drone follow a simple path using voxl-mapper, even after many tries. It gets
  stuck midair as if it sees an invisible obstacle, or turns in another direction from the one planned and it stops.

All these tests were performed indoor in a sufficiently illuminated environment.
We tried a factory reset too, regenerating extrinsics and reconfiguring the px4, but all the problems persist.
Still impossible to calibrate.

We look forward to hearing from you.
Best regards,