@tom It's okay, I managed to figure it out. Just had to change the RC protocol in the px4-conf file.

@Eric-Katzfey Awesome, thanks for the feedback!

@tom That did the trick, thanks for the help!

@Taka , as you are aware that this configuration is not supported, so you would be testing it at your own risk (in terms of drone flying normally after all the changes and potential issues with motor overheating). Electrically, Starling 2 is compatible with 3S. The entry point of power into Starling 2 is the mini ESC, which is rated for up to 4S Lipo. https://docs.modalai.com/voxl-mini-esc-datasheet/ Now, regarding the motor.. you would need to do a ESC motor calibration using the following procedure : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md?ref_type=heads (mainly update the battery voltage, test and update rpm limits, calibrate the feed forward (pwm_vs_rpm) curve, probably lower (a little bit) start-up power, confirm start up is smooth). You may also want to slightly lower the kp term (proportional term in the rpm controller, to account for increase in battery voltage, so that the controller does not become more aggressive). Maybe lower that from 100 to 66-75 or so. These should be the ESC params that are loaded on your ESC : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-params/D0014_starling_1504_3000kv_ms_props/D0014_starling_1504_3000kv_ms_props.xml?ref_type=heads . You can double check this using voxl-esc-verify-params.py script and then modify these params with your changes. The esc tools are already installed on voxl2 in /usr/share/modalai/voxl-esc-tools. The main issue you may see is if you apply full power to the motor continuously, it may overheat due to the fact that it was designed for 2S. However, you can artificially cap your maximum rpm (in esc params) to prevent the motor from going to higher rpms (and update your px4 params for max rpm accordingly). Depending on what you are trying to achieve, you will probably have to put some SW protection and prevent the motor from overheating. If you are OK with waiting for a few days, I can give the motor a spin at 3S and just confirm nothing BAD will happen. Alex

@paul-ammer If you aren't doing any VIO related flight you can disable voxl-qvio-server and voxl-imu-server. I believe you may still need voxl-vision-hub if you're communicating with a ground control station but not 100% positive on that, voxl-mavlink-server may be enough.

Hello @selina, Do you have any px4 logs from the original flight(s) which exhibited the flipping behavior? The logs contain the commanded and actual RPM (as well as many other things) and we can check what happened. If you don't have any sensitive information (gps location that you dont want to share, etc), you could upload the log to https://review.px4.io/ and that will give you some information and we will be able to grab that log and further analyze it to parse the custom ESC messages that standard px4 flight review does not support. Alex

@Beniamino-Pozzan Thank you so much for the info, I wanted to try it and realised foxy has no support and with Ubuntu 18.04 on voxl-2 it is not possible to use any other ROS-2 installations easily. I will use ros2 plugin by keeping microdds as default middleware. I hope newer ROS versions will be available for VOXL-2.

@groupo We also had this issue, but we had modified the sentinel and was found to be more due to vibrations https://discuss.px4.io/t/stopping-compass-mid-flight/42808

@Alex-Kushleyev Dear Alex, It's the M0025-002 high resolution camera. Perhaps the connection sodder was loose and it popped off real easily. In hindsight, perhaps it's not worth anyone's time. If you can provide any repair tricks that'd be neat otherwise I'll probably have to send a new order in. Best, Milton

@Cody , please double check the actual and desired roll / pitch / yaw values in the flight review. When the vehicle is level, then roll and pitch should be close to zero and desired roll/pitch will be zero as well if you don't touch RC sticks. If the attitude estimate is incorrect (for whatever reason) this can cause the vehicle to not be level during flight / take-off. Alex

@tom After flashing, I cannot connect to the QGC. After setting up the IP address, I try to connect via UDP using the IP and port 14550, this is what I get [image: 1740736258690-e032a3a6-32d8-4b3f-9f56-dba442f9aaa4-image.png] drone(connected) is the one not connecting to QGC.

The 3000mAh packs use Sony VTC60 LiIon cells and the 4000mAh packs use Amprius Silicon Anode cells

@ramp Yes you could still do HITL with a starling 2 max, would just require unplugging the ESC from the VOXL 2 and using that connector

@antenna-eng What hardware do you have connected to the VOXL 2 board? Cameras etc.

@Alex-Kushleyev Thank you for your response, it was the issue with the battery, May be my battery is damaged, when I provide external power source of 12 volt power supply, then it is working perfectly fine. Now I am able to access the portal and voxl2 as well. thank you

@starlinguser Thank you for your response, now my problem is resolved, I just used "voxl-configure-mpa --debug" and now everything is working fine. thank you