@19bpl At the very least you need to be able to ping the QGC computer from VOXL2 and VOXL2 from the QGC computer before attempting anything else.

@Kashish-Garg-0 It's possible your board has a QSM8250 (M0054-2) instead of a QRB5165 (M0054-1), see here for the diffs: https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2

If that is the case then you will have to QDL using a different build, which you can download from downloads.modalai.com, look for M0054-2 Starling QDL Image 1.7.4 2024-02-09-1.7.4-M0054-2.zip under the "All" category

@Vinny Thanks for the help on this I really appreciate it. I'll take a look.

@Zachary-Lowell-0

Hello! I was able to reinstall 1.3.5 and that somehow fixed it! I am not going to question it lol.

Now I'm trying to find out how to install voxl-mapper and I can't find documentation for it. I am flying the drone inside a test lab. Today when I was flying it around the room, the drone was not mapping anything. The 2D/3D map was blank when I went to plan a point. I think it's blank because I am missing voxl-mapper especially since I have camera-server, vision hub, voxl-px4 and qvio enabled/running. All I have seen is that I have to change "offboard_mode": "trajectory", in order to plan a point on the map and have the drone fly to it.

Is there any documentation on getting voxl-mapper and planning a point?

@garret Here's the source code for our branch of Gazebo: https://github.com/modalai/PX4-SITL_gazebo-classic/tree/voxl-dev

@emarcphera Huh, interesting. Okay, thanks for posting the update!

@Aldo-Castro-Freire thanks for the feedback, do you mind sharing the openVPN Client and Server versions you ended up using that worked?

We've tested using server v2.4.8, voxl-vpn (v2.1.3 inside that), and OpenVPN Connect ver 3.2.2 on Adroid.

Sounds good, thanks!

I reran the calibration outdoors with gps signal and far from any metal. I also raised the drone to be ~3-4' from the metal turntable below it. This improved the calibration quite a bit and the drone is not drifting as much as before. However, there still seems to be more drift in the VIO than there was when I first received the drone. I still don't have the PWM_MIN parameter that the docs say I should check for the assure the PX4 parameters loaded properly. I see that this parameter is in the custom2.params file, but the note in the document says it turns off the gps.

Can you please explain the steps you go through during your calibration process? Should I also be loading this custom2.params file? If so, does that mean that gps is not used when in VIO (no sensor fusion etc)?

Solution: sometimes when just binding the RC controller, the inputs aren't shown. Make sure to restart drone after rebinding. Additionally, I've found different controllers have different lever/switch inputs, so its good to use QGC to look for the responsive switches and assign the ones you want accordingly

@Daniel-Ryu

I figured. We just wanted to double check that this was the case. Thank you!

last question :
I could not see the point cloud with stereo , but since I need it to indoor solution, I will use tof anyway.

I using the drone without any GPS module (don't need it)
but I could not to change from manual to mission nor off board.

when I change the gps to rc transmitter (first option) I was able to get move to mission
but only left stick worked (up down rotate) the second stick won't work (forward and rotation)

is there a way to move to mission without gps module?

Please see email thread in progress, if possible let's use one channel for communications.

WOW what a great thread, so on time for me Thanks Kris

No. I don't have any other voxl.
Yes, it's properly installed. I had previously worked with the same ADB installation. Suddenly, it stopped responding. I also tried with two other machines with proper ADB installations. It showed the same problem (no device found).

@Ansel-Misfeldt

FW update feature is working in QGC daily build starting today, no change needed on flight core v2.

23df224f-21ae-4469-b90e-bb255be91ab0-image.png

hi @suvasis

#test voxl-esc tools cd /home/root/voxl-esc/tools ./voxl-esc-scan.py #perform ESC testing / calibration #...

this was just a place holder for any testing you want to do with the voxl-esc tools.

#when done, restore original libpx4.so cd /usr/lib/rfsa/adsp rm libpx4.so cp libpx4.so.bak libpx4.so systemctl enable voxl-px4 reboot

This part restores the PX4 functionality, because in order to use voxl-esc tools on VOXL2, the instructions told you to disable PX4 while using voxl-esc tools. Soon we will not require disabling PX4 to use voxl-esc tools, but currently you have to do it.

Please note that we just made some updated to the voxl-esc tools and directory structure has slightly changed. Also, you no longer have to download the binary tools package and add it to the voxl-esc/tools directory. Please see an example params file here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-params/old/esc_params_modalai_4_in_1_revb.xml

@Eric-Katzfey said in QGC sensors - compass remains red:

t isn't being specified correctly. It's kind of hard to tell in the picture but, at a minimum, the board is rotated 180 degrees. So it's the IMU rotation that needs to be set.

yes, the board is rotated 180 degrees. So, how do I set the rotation of the IMU to 180 degrees? is it in the same config file?

I rotate it 180 degrees as shown below

AAAA.png

@Moderator Hello - sorry if this isn't needed, but I put some settings/configs from one of the drones a couple messages up. If you could recommend other settings to look at to help get telemetry flowing between FCv2 and VOXL, it would be much appreciated. I'm happy to provide other settings/configs, just let me know what is helpful.

Thanks,

Jay

@Alex-Kushleyev Thank you very much for the solution, I fix it and it works. : )