I forgot to post the resolution, oops. It was indeed turtle mode. That channel was not mapped on my remote, and I ended up having to adjust the relevant PX4 parameters to disable turtle mode entirely. Thank you for the assistance!

Update fix Replace defaults.parm with upstream version: https://github.com/ArduPilot/ardupilot/blob/ee1e4bbf74061760826b17464383d63c1a11924c/Tools/Frame_params/ModalAI/Starling2Max.parm Rename Starling2Max.parm to defaults.parm in /data/APM Edit SERIAL3_BAUD=9 (in defaults.parm) Edit GPS1_TYPE=2 (in defaults.parm) Remove *.stg files in /data/APM Reboot and power off the voxl2 multiple times, checking the gps driver

With M0195, C34 is the camera configuration that you would need. See https://docs.modalai.com/M0195/#support-camera-configs

@minhthinh The params are in our voxl-px4-params repo. For example: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.13/Platforms/M500_FCV2.params?ref_type=heads

@Aniruddha , we currently do not have an option to order this via our online shop, but you have some other options: email us using contact form and request a custom order of those parts : https://www.modalai.com/pages/contact-us download the CAD model (https://developer.modalai.com/asset) and 3D print the part(s) yourself or order them to be printed. We use MJF material for these parts. Sorry for the inconvenience. We will look into making the spare part ordering process easier. Alex

@Aniruddha On QGC, do the Parameters ever fully load? The reason I am asking is because if the connection to the GCS is not fast enough or strong enough for QGC to fully download the parameters then the other tabs like sensors and actuators in QGC will not appear. Which is why you are having an issue doing the level horizon from QGC. I know that QGC is seeing the video feed meaning you are connected, is the Green bar going across the full length of the fly view bar on QGC?

@RyanH , from the spin log above, i can only tell that the motor attempts to spin up but re-starts after the open-loop sinusoidal spinup is done and the ESC detects that the motor is not spinning. You should try to clear the debris by spinning the motor by hand first (or use compressed air) and then use the test script to spin for longer periods of time without propeller (changing speeds, etc). You could use a spin step command to automate increasing and decreasing spin speed (without rpm control, since it's not needed): ./voxl-esc-spin-step.py --id 0 --step-delay 2.5 --step-frequency 1 --power 20 --step-amplitude 30 Alex

@tom Thank you!

@Alex-Kushleyev I reached out to Travis last week. I'll bump you here if I don't hear back this week.

@Roy-Azriel , the description of Starling 2 Max states that it uses VOXL2, as well as lists other major components and options for camera configurations : https://www.modalai.com/products/starling-2-max?variant=48216084087088 Please let us know what Lidar you are considering adding. Alex

@aheyne , please send us a message via contact form. We don't sell this part separately as a product, but will help you with a replacement. You will need the M0177 flex cable (as the print states on the cable). https://www.modalai.com/pages/contact-us Alex

we just posted an update on this topic, please see https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines .

@colombe-ai , please see https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines

@qubotics-admin First you need to determine the version of PX4 running. With ssh or adb you can run the following at the command line: px4-ver all. You will see PX4 version and Vendor version. So, for example, for px4 version 1.14.0 and vendor version 8.134.3 then you would checkout the tag v1.14.0-8.134.3-dev from the repo to see that commit.

@ey , please send us a request via http://www.modalai.com/pages/contact-us Alex

@Maxwell-Schaefer Thanks for your reply. Is this step also applicable for the BetaFPV Nano RX? Should this also used ModalAI's firmware repo? Or will this use BetaFPV's? I did look into trying to flash the Nano RX initially, but stopped short of doing it as the physical RX itself did not have a BetaFPV silkscreen on it, so I assumed that it might be using a different firmware from the stock BetaFPV Are you able to advise on the other queries regarding the new wifi adapter board?

@Vinny Perfect, thanks!

@Leo-Allesch , if you are talking about VSLAM, which stands for Visual Simultaneous Localization and Mapping, then this is a sub-class of SLAM which uses only cameras (and often IMUs, then it is VISLAM). VSLAM and VISLAM usually generate and maintain a sparse map of 3D features (points), which is used for self localization. If you want to be able to detect a target, and you have your 3D pose from VIO (VIO = VISLAM), then you can either triangulate the target location or get it's location from a single frame if you know the size of the target (such as April tag, etc). Then you can transform the coordinate of the tag from the camera frame into your "world" (VIO) coordinates. The depth sensor would allow you to build a more detailed 3D map / point cloud using the 3D pose output from the VIO algorithm (or just using a depth sensor, which may be more complicated). You can also build a dense 3D map using camera only (and IMU), but that typically requires a lot more computation than using a depth sensor. You don't necessarily need a depth sensor for identifying the position of a specific target that is easily detected by a camera. There is a lot of research material you can find on these topics, please look into it deeper and let us know if you have specific questions about using VOXL2 hardware and software. Alex