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

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
.

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

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

https://docs.modalai.com/voxl-logger/

I would try out the "-k" option

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/

@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.

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?

@tom Yeah I am on 0.9 platform release

@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.

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.

Please review the External UDP Mavlink Connection documentation

You need to be outdoors, with clear visibility to the sky, to receive GPS

Hello,
This is third time I do this, because the questions I did are a very important issue and my company and I want to solve what happened during the flight. So if you have any answer to the questions I did 27 days ago please respond them.
Gonzalo

@Chad-Sweet said in Running MAVSDK directly on M500 and Python update:

The Docker is 64-bit, so the code that runs inside is usually faster than the code that runs outside of the Docker

Oh, that's interesting, thanks for the insight. I'll share with the others, and let you know how it all goes.

flight Core v1 is what is found on VOXL Flight

We don't have a guide on our own, but Google should have plenty of guides and examples

You'll need to add your own post processing function in this area of the code

Here is Google's guide on how to postprocess tflite data
https://www.tensorflow.org/lite/inference_with_metadata/lite_support

@Chad-Sweet Thanks. So it sounds like a full re-flash is probably the best check to re-install base software (I'm not aware of any modifications, but came onto the project after it started) and check that connection. If the issue persists with both units, kick off an RMA?

Appreciate all your help.