@Ben-Linne : Thanks for the excellent instructions. Worked perfectly first shot. betaFPV is back to normal and binds to the radio controller ! Best regards, Hector

@jbiscan21 said in Standoffs part: standoffs You can find them here: https://www.modalai.com/products/starling-2-max-replacement-parts?variant=66893548028208

@wilkinsaf You can disable compass with SYS_HAS_MAG = 0 and EKF2_MAG_TYPE = 5. But if you enable it and it isn't healthy you won't be able to arm. Power compensation may work, it depends on your particular drone model and use case.

Good tip. For anyone testing without the GPS module attached, setting SYS_HAS_MAG=0 and EKF2_MAG_TYPE=5 seems to be the key part since the compass is on the GPS board. I was also looking at some compass-related references on 123compass.org while trying to understand the magnetometer side of it.

These are the propellers that were used for that drone https://www.getfpv.com/lumenier-6x4-slow-flyer-propeller-set-of-4-clear.html

@chinlee5 Which drone do you have? Which versions of software are you using? Are those messages appearing on QGC? Also, do not try to arm the drone or fly the drone while attached to a power supply. Only use a battery for that. If you take the drone outside with a full view to the sky so that GPS can acquire satellites do the messages go away?

@jbiscan21 , sorry i am surprised that we don't have a photo of the Starling 2 Max with the TOF mounted. Please see below. The TOF sensor is oriented vertically on the front face, right next to the front hires and tracking cameras. If you need to mount the sensor somewhere else, you can use an available extension flex (it only works for the TOF V2 sensor) : https://www.modalai.com/products/msu-m0170 [image: 1778622060259-82033d14-9ca0-4a39-8963-1bc405ee5d09-image.png]

@Moderator Why is it not plug in play? I found the spot to connect to the board but configuring the SKU based on C29 did not work. Also, the connector seems really short so I am curious how the C29 config looks.

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.