I've made great progress. I have finally started getting my brain rapped around this VOXL. Funny it's so complicated. I was able to cut the cord. Remove the usb cable that is. I focused on understanding the VOXL wifi and understanding softap and logging into via wifi, This allowed me to get some imagery to the browser utility. I went down the list of utilities then inspect tools in technical docs on the website. This allowed me to get a bigger picture of the components. I have logged my experience and will post a work flow I follow to get up and running. I'm still working on the 4g connection but reading the VPN stuff and working with the instructions makes more sense now I have gotten the wifi configured . I have it configured but qgc is still not connecting I understand it's hard to ask for technical support with such complexity. I just believe it's worth the investment in time because this is a real solution and the voxl2 will be eaiser to work with now I have a grasp of the voxl. I hope to be flying my custom designed 3d printed drone soon.

@Chad-Sweet I have GPS mounted over VoxlCam hardware with distance of approximately 10 cms. I also tried moving GPS towards backside similar to seeker but still I wasn't able to get fix. I have waited for an hour to get fix but still facing issues. Do I need to configure GPS module by any chance with u-center : https://www.u-blox.com/en/product/u-center ? As far as electromagnetic interference is concerned I don't think there is anything in very close vicinity of GPS.

This rx: 0.000 kB/s instance 2 tells me it's not getting any data from VOXL.... This is the connection that provides that link: [image: 1662047065492-c24bf1be-8000-458a-9380-a633cdb51ab3-image.png] Can you confirm that this connection is in place? You have px4_uart_bus: 5 px4_uart_baudrate: 921600 For voxl-mavlink-server which is correct. 5 = BLSP5 = J12 on VOXL1. It's configured for 921600. Your Flight Core is configured correctly too. So the last thing I would think to do is to probe with an oscilliscope if possible on that connector I pointed out and see if you have bi-directional data.

Hi, The bugfix for this is in VOXL SDK 0.8 and newer. If for some reason you need to change the imu that qvio uses from the default configured by voxl-configure-mpa then you can edit the config file /etc/modalai/voxl-qvio-server.conf manually or use one of the shortcut command line arguments listed in the voxl-configure-qvio --help text such as: voxl-configure-qvio factory_enable_imu0 voxl-configure-qvio factory_enable_imu1 Hope this helps, James

Hi, It looks like your network is the issue here for the blurry image. Voxl-portal will compress images when it detects a poor network connection, and you can see that in the debug stats it's only able to pass through 40% quality image.

@Alex-Gardner I installed the 0.8 on the voxl, and mow I'm trying to configure the voxl flight deck for a new drone, but it seems to not work at all. I chose the frame type and once applying the modification, the system restart as normal. Once restarted, it ask again to chose the frame type, it doesn't keep the previous settings. Have you any idea what can be?

@張為超 Great, glad to hear it is working for you now!

I’m having the exact same problem, but I can’t connect to an Ethernet. Is there any other option for calibration? I’ve tried for 8 hours straight with no luck……

@tom I don't see wwan0 interface after doing ifconfig so couldn't ping google.com as well.

@Alex-Gardner Thank you for your help

it's not possible for a flight controller to have PID parameters for an unknown drone. Every drone has different tuning parameters. We sell the VOXL m500, pre-tuned and flight tested, just for this purpose.

@Moderator I just tried running those instructions for VOXL1 build, but have an issue downloading the manifest package from codeaurora. I posted an issue here about it. Please let me know if there is an update!

I've figured out why. My original MPC_LAND_SPEED and MPC_Z_VEL_MAX_DN were 0.6 and 0.5 respectively. Thanks to the following chunk of code from MulticopterLandDetector.cpp, descend_vel_sp will never be true. if (_flag_control_climb_rate_enabled) { vehicle_local_position_setpoint_s vehicle_local_position_setpoint; if (_vehicle_local_position_setpoint_sub.update(&vehicle_local_position_setpoint)) { // setpoints can briefly be NAN to signal resets, TODO: fix in multicopter position controller const bool descend_vel_sp = PX4_ISFINITE(vehicle_local_position_setpoint.vz) && (vehicle_local_position_setpoint.vz >= land_speed_threshold); Had to increase MPC_Z_VEL_MAX_DN and that solved my problem

@Chad-Sweet What is the "basic drone bring up process"? I can fly it in manual mode, it's not easy to fly, but I felt like its more due to my skill level as its behavior from virtual joystick was somewhat similar to when I tried virtual joystick with your RB5 drone. It does drift noticeably. I think this drift is excessive but again, I'm not sure if it's an issue with the drone or my skill level using virtual joystick. It didn't seem to respond to virtual joystick inputs in position mode but I didn't extensively enough test that mode. I'll test that mode again and see what happens.

The best place to start would be try to reinstall the Flight Core firmware. It sounds like the VOXL side of things is OK. The most common failure mode for Flight Core is plugging USB into the R/C port. Any chance that happened?

@ryan-langlois1 We will definitely continue to support PX4 on VOXL 2. But we are also very interested in getting a port of ArduPilot going on VOXL 2 and have had some preliminary meetings with the ArduPilot community to start the process. But we cannot offer a timeline at this point.