Hi, It looks like the data on that documentation page was erroneously copied over from a different platform, I'll update it shortly but in the future for QVIO needs this docs page is more actively maintained by the software team. For reference the commands in the voxl sdk for doing the things you asked about are voxl-inspect-qvio and voxl-configure-qvio. These are the standard formats for the commands in our SDK, so you can tab out voxl-inspect- or voxl-configure- to see all of the other things you can inspect or configure.

@Cristian-Adam The aircraft (M500) still does not connect to the WiFi at my office. Modal Devs and I are assuming my problem is related to the firewall settings IT set up at my work. Although I type the command correctly and the aircraft finds the wifi, it cannot connect and fails.

@tom Yeah I am on 0.9 platform release

Our team would greatly appreciate feedback about the motor over heating issue. Both our aircraft (two M500 platforms) have this issue. The high temperature has caused a failure and we are requesting guidance on understanding why the aircraft has this heating issue. Would a calibration of the system help fix an issue like this?

@yu-zhang Hi! I got quite confuse with this topic but, I would like to know. Did it work using the new Holybro motors with 920kv? I guess all the answers from Adrian were to get to make them work. I ask because it has been difficult to find the motors I need for the m500. Regards.

This functionality was added to voxl-mpa-to-ros in v0.2.2 and it seems you have some very old software on this drone. I recommend upgrading to the latest sdk by downloading and flashing the VOXL Platform 0.9 release from https://developer.modalai.com/

https://docs.modalai.com/voxl-logger/ I would try out the "-k" option

Wanted to update this by saying I experienced same issue, but I resolved this by disconnecting tracking camera that had been installed upside down. So, if anyone is reading this in the future....try disconnecting your cameras attached to the board

@mkwan Can you make a new thread with this issue and include the output of voxl-inspect-services -v

I have enabled voxl-tag-detector on boot, it did not help. I used systemctl enable voxl-tag-detector and in the **.service I used Restart=always .

Still need some troubleshooting on the logs I've posted if anyone in the team have some time. Cheers to all!

Seems to be an issue with QGC itself. The latest v4.2.3 I’m running is where it’s failing. If I revert back to the latest 4.1.* (4.1.7) it works.

@Adrian-Hidalgo All right, thanks. I will check them step by step, and hope it will be solved soon

@DarkKnightCH Use a flat tipped screwdriver or similar device to slowly pry it out. Take your time working both sides of the the Hirose connector. Take care as the pins can get bent if too much force is applied

Hi Jonathan, The underlying pipelines for the CV sensors are all delicately built and only support very specific resolutions. I'll update our documentation to better reflect this, but in general: The stereo pipeline can only do 30hz(for now, we're working on this) since it's very custom and the tracking camera can do 30,60,90, and 120hz. The hires camera is more standard and has more robust pipelines implemented to support more standard video stream configurations. As for the manual exposure/gain, have you set the auto exposure mode to "off", if not you're just setting up the starting point for the camera and the AE library will still perform it's usual duties. If you're still having issues after this let me know and we can dig through more of what you're seeing.

I think you'll need to create a new service that behaves like voxl-qvio-server ? That might be the easiest if you want to drop it. Maybe try copying qvio-server and modifying to publish mocap data?

That was actually a very good question. Any recommendations?

@modaltb I see. It's good to know the story If 22027 is the default one, it will be all right. To be honest, I didn't touch the CBRK_IO_SAFETY before, and it's a bit weird why it was automatically modified for some reason. Actually, I was trying to refresh a re-compiled 1.11.3-0.2.3 with my modification (increasing GPS log rate). So, I guess it might reset the value to 0 by PX4 default. Anyways, thanks so much!

@Alex-Gardner All right, thanks so much for that