Sorry to hear that.

https://www.modalai.com/pages/rma

You can provide a link to this post when you submit it.

Hello Timothy,

Excellent! That is certainly possible to do.

1. Yes, with some configuration it can be compatible. You will need to reconfigure MPA from the C28 camera config to the C29 camera config.

2. They will need a new front camera bezel(M10001278), TOF safety shield(M10000537) and everything in MSU-M0178-1-01. Most of the hardware can be reused but as a precaution would also recommend QTY. 4 M10000884(M1.6X6 Screws) & QTY. 4 M10000882(M2.2X10 Screws).

If you would like to proceed with the purchase, please email contact@modalai.com with the contents above.

Regards.

Hello @RoyAzriel,

There are 4 blue LEDs on the ESC - is that what you are referring when you said "the 3 blue leds are blinking as always" ?

I am not sure what happened, but you should try the unbricking procedure for voxl2: https://docs.modalai.com/voxl2-unbricking/

Alex

@PatkirkMartin In order to toggle power via PX4 you can do the following:

Set GPIO_CTL_CH to the AUX channel you'd like to use for this feature, e.g., 3 for RC_MAP_AUX3.

Set the corresponding RC_MAP_AUX# to the button/switch you want to use. e.g. 10 for channel 10 on your RC transmitter.

@NikosMav Also, before changing anything can you capture a PX4 log and send that? From the adb command line you can use px4-logger on, wait a few seconds, then issue px4-logger off. You should see a log file somewhere in /data/px4/log. Perhaps to make sure it's the correct log delete all current logs before running this such that there is only one log file there.

@NikosMav Can you reinstall the SDK from scratch and verify that everything works properly? Was everything working before you changed the parameters?

@PatkirkMartin , I am looking into the command routing via PX4 for the on/off function.. stay tuned..

Hi @PatkirkMartin
If you have a more recent ESC with this 11 in the SKU, then the VTX regulator has been upgraded to 1A support.

We originally only did have 500-600mA support at the time before all the VTX units in the market went crazy with 2W+ output options.
If you need 600mA, I am confident this will work fine for you. We still publish the 500mA spec since we did sell a lot of the -1 unit with 500mA for the first year or so before we upgraded that part.
Hope that helps!

Hi @Julian ,

Thank you for the detailed report. It does look like there is a missing (or broken? hard to see) magnet in the motor, in which case the motor will not work properly and should be replaced. No further testing is needed, as this is most likely a manufacturing defect of the motor or a result of an impact.

If you believe that the motor was defective when you received the product, you should request a free replacement motor (submit an RMA form) . If the motor was damaged while testing, you can purchase a new motor.

The Starling 2 Max replacement parts can be found here : https://www.modalai.com/products/starling-2-max-replacement-parts (however i don't see just motors without a frame + motors kit, will double check..)

Alex

@NikosMav Well, try each command a few times. But I think that is enough to show that the IMU is generating the data, otherwise it would have printed "never published". When you are connected to QGC and you move the drone around do you see the horizon indicator on the main screen also moving around? That's another indication that IMU data is making it to QGC. How are you connecting to QGC? Is it over WiFi? You can do the gyro calibration directly on the drone from the command line. I would adb into the drone and disable voxl-px4 from running automatically with systemctl disable voxl-px4, then power cycling. Once that is done adb in and start voxl-px4 from the command line with voxl-px4 -d. Once it has finished the start script enter this command at the prompt: qshell commander calibrate gyro and see what it does. Don't forget when you are done with your testing to re-enable voxl-px4 with systemctl enable voxl-px4.