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

Hey Adrian, thanks for the reply! Chad also replied this morning affirming the inverted image in the portal is normal. I was afraid to fly it until I could confirm that. On the SIM, like I said in the other post, after inserting the new EIOT SIM I ordered and A: Killing the voxl modem service temporarily then B: booting up and killing the WiFi then running the shell script to configure the modem with the new custom APN for the new sim (which, by the way, is running on the same ATT network as the prepaid ATT phone sim I was trying to use.. it has to be the provisioning on the carrier side that keeps it from working in the modem) thus making the WWAN gateway the default gateway, I can now get a response to any ping I throw at the internet through the wan. I believe the issue with the SIM card socket that makes me have to take things apart to get the sim to actually click into place properly has to do with board "tweakage" or flexing just enough to make the rather delicate sim card locking mechanism bind. You know the board is basically held in position by the two corner silicone grommets and the B2B connector... it doesn't have any kind of screws or standoffs holding it precisely where you want it against the frame. It's just kind of sandwiched in there. if you were to continue to develop the product, I'd look into screwing it down,, Anyway, now that I have a working SIM, all I have to do is keep it active and hopefully never take the Voxl Cam apart again!

@tangotoo You can see the specs here: https://docs.modalai.com/sentinel-functional-description/

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

Thank you very much I'll try that

@Sam-Kiley We don't use the RB5 SDK anymore so haven't had experience with that specific version of quectel-CM is quite some time. We have a lot of customers using 5G via. voxl-modem on the latest VOXL SDK without issues.

Hi, This is all down to the VIO algorithm. You'd be able to make major tweaks if you're postprocessing the data after, like detecting a reset and continuing from the last valid position (we do this in vvpx4), but changing the px4 params or other fusion techniques that only use the same sensors as the initial vio algorithm will likely not yield any improvements. As for improving the vio algorithm itself, the QVIO's mvVISLAM package is proprietary code(even to us, we don't have the source) that we usually quote at 2% error over distance, which seems to match the test you've run here (you've flown a bit under 10 meters and it looks like you've drifted ~0.15-0.2 meters. We've been working on and experimenting with other algorithms internally, but don't have a hard date on when these will be fully tested/published. It's worth mentioning that most of our experimentation with these is to attempt to open-source our solution and add support for other features (like multiple cameras) but that generally the 2% error is considered very good especially in real-world environments. The 2 main things you can do out of the box to ensure that your VIO is working as best it can are ensuring that it has accurate camera and imu calibrations, and that your extrinsics file is accurate.

Please review the External UDP Mavlink Connection documentation

Everything looks good, gave it a glance and a quick test, it's been merged to our dev and staging branches in v0.4.2 and will be in the next release, thanks!

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

Vinny! You're the man! Good news but a little backround first. I've been building drones for a long time, but I come from the "Other side" using a windows box to configure APMs then Pixhawks with Arducopter using Mission Planner. When I got this thing, I literally built an Ubuntu workstation just to talk to it. I'm an old guy that used to live on the DOS commandl line, but I really have to hone my Linux skills (almost nonexistent..) for this project. Outside of the Arduino IDE and some ancient BASIC, I'm no coder, but I understand microcontrollers, serial, I2C, CAN etc pretty well because I come from an industrial automation background. (Amazon Fulfillment Center Controls lead configuring Cognex and Sick every day..) I figured out the serial ports. (I was using the freaking asterisk in the QGC parameter search box like a typical DOS jockey!) I found that in the 1.11.3 firmware the serial parameters are bit masks and numeric with no real reference for me, but in the latest PX4 release they have a dropdown and real names and values, so I loaded it, changed TELEM1 to 921k and Mavlink mode 2 (offboard), saved the params, then loaded your 1.11.3 custom version back up and restored the params. Done deal. Now I just need the level shifters I ordered today and I can try it out. BTW I also ordered two connector kits, one with a pile of GH 1.25's and the other with a pile of DF13's. I've been meaning to get them for a while cause' I have a huge collection of parts that just don't quite match up and also because I wear my super-re-pinner badge proudly! I'll let you guys know how the level shifters work. I ordered two types, one with multiple mosfets and one with the TXS0108E chip so I can see what works best when it goes back together. Thanks for your prompt and helpful reply!

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.

Discussion moved to https://forum.modalai.com/topic/1647/voxl-streamer-does-not-handle-teardown-request-signal-correctly/4

Thanks, Adrian! I will look into building two batteries with Sony VTC6 cells.

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