I just found out, that the voxl-dfs-server is disabled at default. So I run systemctl enable voxl-dfs-server and it worked fin.

@Troi said in Stereo camera does not appear in Camera Calibrator Overlay:

Hello, I am trying to calibrate the stereo camera using the instructions on the website (https://docs.modalai.com/calibrate-cameras/). I use the following command to start the calibration process:
voxl-calibrate-camera stereo -l 0.04 -s 4x7

I tried to view the calibration progress via the voxl-portal's Camera Calibrator Overlay. The Camera Calibrator Overlay option appears in the voxl-portal drop-down menu. However, the stereo view with overlay never appears.

When I try to exit camera calibration (via Ctrl + C), the program hangs and I have to exit the terminal to stop the program.

What should I do to solve the issue with the camera calibrator overlay and the stereo camera calibration?

I am having the same issue, any help will be appreciated. @Troi How did you resolve this?

@modaltb
I sent it for repair
You fond an issue with bad connexion on camera
I received it back
It is working OK

BUT
I have an other issue regarding connecting to ArduPilot

It seems it is having issue with MavLink Message :

voxl-mavlink-server[3036]: ERROR message magic number wrong #284
And it seems to reconnect under a different ID

f7f5c17a-561e-473f-8ddc-f930bc8f0b8a-image.png

Do you have a clue?
Do you want me to open a new issue so we can follow more efficiently ?

Regards

Hi @awagner
Electrically, yes.
Depending on your VoxlCam config, the port may be used by something else.
If you share a photo of your VoxlCam, we can help confirm.
These plug-in boards all use the same 60-pin B2B (J13) on Voxl/VoxlFlight, but if you need to maintain 4G LTE modem or Microhard functionality, that uses the same 60-pin, so you'd have to play swap games back and forth.

Yes, I have reviewed it. I observed through voxl-inspect-vibration that there is a significant amount of noise in the IMU (indicated by the red color). As a solution, I replaced the dampers, which helped to some extent. However, these phenomena still occur. Most of the IMU values are indicated in yellow color. Could this be the possible cause?

I noticed this information in the seeker drone spec, so I understand that you were referring to flying with GPS. In that case, what is the maximum height at which the QVIO can fly and still maintain stability?

@Moderator Thanks for your response. I didn't realize that the VOXL CAM is actually a combination of VOXL companion computer and camera module. My drone uses Pixhawk 6C autopilot, I have a companion computer connected to its TELEM2, now I am looking for tracking camera. If I use VOXL CAM, will the VOXL computer conflict with the computer that I am currently using? If not, which port can I connect VOXL CAM to? And what settings need to be made, do you have a manual/instruction for the setup?

@Anubhav

same issue here,

have you figured it out?

@serge I am also facing the same issue, did you solve it?

@AP123 voxl-rtsp is no longer supported and is not mentioned in that document, you need to use voxl-streamer

@fjksalf If the IP address of the VOXL is 192.168.1.1 then you need to execute export ROS_MASTER_URI=http://192.168.1.1:11311 on the Ubuntu system and then run rviz from the same terminal.

@Amber-Elaine-Parker It's missing a TF. After launching ROS Indigo on the VOXL, open a new bash and type:

rosrun tf static_transform_publisher 0 0 0 0 0 0 1 map world 10

This is enough to create the world frame and make the ToF sensor PointCloud2 message display on Rviz (if you select the world frame under global options in Rviz). However, it looks like the frame isn't oriented correctly in my case. Editing the parameters of this command might change the orientation of the new world frame.

I don't know enough about ROS/VOXL SDK to confidently call this an oversight by the ModalAI team, but there should definitely be a mention that this is required somewhere within the documentation.

@Connor-Fuhrman , I am not sure.

Please try to enable debug-level logging, so you may see some errors (both in your application) and voxl-streamer.

In your application you can add the following :

M_JournalSetLevel((M_JournalLevel) debugLevel);

example: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/src/main.cpp?ref_type=heads#L301

voxl-streamer already has this option, just need a command line option : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-streamer/-/blob/master/src/main.c?ref_type=heads#L383

@Moderator
Thanks for your quick reply.
I'm relieved to be sure.
Kind regards,

Hey @KMillzOG ,

This doesn't help with your core issue, but I have had success running the ROS2 docker images on RaspiOS on a pi: https://docs.ros.org/en/foxy/How-To-Guides/Installing-on-Raspberry-Pi.html If you're comfortable running your software inside a Docker container, that'll solve your problem. Conveniently, you can also build a docker file for ARM or for X86, so you can run the same software on a more traditional PC or inside a CI pipeline.

I also recently noticed that there is still an officially supported Ubuntu image for the Pi. I haven't tried it, but it might be another option. If you have a spare SD card, you could install ubuntu on the spare card, then see if that works for you. Then if it doesn't work you can just go back to the old SD card.

@Eric-Katzfey Thanks Eric, that makes sense!