Topics created by taiwohazeez

Hello @taiwohazeez,

it seems your calibration pattern is significantly warped. It needs to be as straight as possible.

I personally like to perform calibration by displaying a pattern on an LCD screen (flat), which more or less guarantees it being straight. For a monocular calibration, the size of the box does not make any difference (no scale is recovered from the calibration). If you use that approach, then you actually have to move the camera as opposed to moving the pattern, unless you want to move the screen, which actually would be possible on a laptop. Watch out for reflections from screen and also sometimes setting manual exposure also helps (i won't go into detail how to do that here).

You could take your calibration sheet and glue it to a rigid flat surface, but even that can be tricky, since paper glue can cause wrinkles on paper, but those should not be as bad as the deformation seen in your screen shot.

Alex

@taiwohazeez ,

Please try the following after a fresh reboot:

voxl-inspect-cam tracking_down tracking_front tracking_rear tof_ir hires_small_color

Running voxl-inspect-cam -a can break the camera server because there are too many output streams to process. This used to be a good option in the past for a quick test, but with 5 cameras and ~25 streams this is becoming too heavy. In normal use cases, only one stream is used from each camera.

If you are just getting started, I would suggest updating your drone to at least SDK 1.5 or even 1.6, however you should still be able to get camera streams displayed in voxl-portal or using the limited voxl-inspect-cam command.

If you still cannot get this to work, please do the following to stop the background service for voxl-camera-server and run in in the foreground and past the output:

#stop the background service (it will restart after reboot) systemctl stop voxl-camera-server #run camera server in foreground voxl-camera-server

Alex

Hello @taiwohazeez ,

Thank you for sending updated images.

Just for sanity checking, please double check that the other tracking camera on your drone is in focus and does not have this issue.. (i assume that is true).

To me, it definitely looks likes either

damaged or dirty lens on the external lens surface damaged or dirty lens on the internal lens surface (the back surface of the lens) dirty surface of the camera sensor itself (inside the camera module)

If you are comfortable with unscrewing the lens completely and wiping it (front and back) with a new microfiber cloth (preferably long strand) and screw it back again to check if there is any improvement. Also, once you remove the lens, you can take a look at the sensor itself, any dirt or smudges should be very easy to detect because the surface of the camera sensor is very reflective and should be perfectly clean. I can't recommend cleaning the sensor itself on your own, since that would involve inserting something inside the camera module, which could lead to damage. Please dont keep the lens out of the lens holder for a long time (hours) as dust or dirt may get inside on the surface of the sensor (do not perform this procedure in a dusty environment).

Please reach out to https://www.modalai.com/pages/rma if you need further help to get this fixed / replaced.

Alex

@taiwohazeez Can you post a video of it trying to fly?

@Zachary-Lowell-0 Hi, let me explain what i meant by hovering mode. There is a 3-way toggle switch beside the kill switch in the transmitter (toggling down switches to position mode, toggling up switches to the autonomous mode, while toggling to the middle maintains the drone flight positioning. I have another drone that when the button is switched to the middle, it maintains the drone position (thats what i meant by hover mode). My other starling 2 drones maintains their positions when the switch is toggled to the middle position, but this particular starling 2 drone doesnt.

Detections is pertinent to voxl-tflite-server and onboard computer vision on yolo, NOT on april tags.

Hi @taiwohazeez,

The " /fmu/in" prefix is used for sending data to the autopilot - you're never going to receive data from the autopilot listening to that topic.

Look at the "/fmu/out" topics to see messages coming from the autopilot.

Best,
Ted

Hi @taiwohazeez,

That is the cable that powers the VOXL. I'm suggesting you leave that plugged in and disconnect everything else. I see you still have the VOXL 2 WiFi Add-on board connected. Disconnect that as well all the cameras on the bottom of the VOXL, ESC, and GPS.

Please have the VOXL powered off while you disconnect everything.

Let me know how it goes,
Ted

@tom @teddy-zaremba can you assist please? This is pretty urgent, I need to get this fixed. Also, the landing gears got broken, and I can't seem to be able to order new parts from the official website, is there a way I can go about it?
Looking forward to your response.
Thanks

@taiwohazeez The build flow should be like this:

cd voxl-mpa-to-ros2 git checkout dev git submodule update --init --recursive voxl-docker -i qrb5165-emulator ./install_build_deps.sh qrb5165 dev ./build.sh qrb5165 dev ./make_package.sh deb

@taiwohazeez Could you post the error and we can take a look?

Also here's an easier way of installing it if you just want to run this script on the voxl.

wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.5/binary-arm64/voxl-ros2-foxy_0.0.1_arm64.deb wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.5/binary-arm64/voxl-mpa-to-ros2_0.0.7_arm64.deb sudo dpkg -i voxl-ros2-foxy sudo dpkg -i voxl-mpa-to-ros2 voxl-configure-mpa-to-ros2

@taiwohazeez No problem, it would also be helpful to know what SDK version is loaded on your drone. You can check this with voxl-version