@0x45 if you get it working and you would like to share your change, we can test and incorporate into the driver. That could potentially make it easier for you to not have to use a custom px4 build for your application.

@dlee , that is great to hear! Since lowering ESC kp and ki to zero helped, it may mean one of the several potential issues outside of ESC: the flight controller (gyro) is measuring too much vibration from propellers (is there vibration dampening in your design?) your attitude controller Derivative gain may be too high, causing the noisy gyro data to be amplified and sent to motors However, if the vehicle is flying well right now, perhaps you do not need to do anything else. Tuning down the ESC response acts as a low pass filter that filters out the noisy RPM commands.

@swickliff, if only 1 out of 4 LEDs is blinking, that is very strange. When power is applied to the ESC, the bootloader on each ESC channel should always start and blink the blue led fast for 1 second. after that, firmware execution starts. If LED is not blinking at first, then there is most likely some HW issue that prevents the ESCs from booting. I am surprised that one out of four LEDs is actually blinking. Our ESCs are all tested during production (including spinning), but if you think that you received the ESC in a non-working state (it was not damaged after receiving it), then you should submit an RMA form for a replacement. https://www.modalai.com/pages/rma

@Vinny Thanks for your quick reply. I have no idea what caused this problem. After the first flight i noticed a certain smell that could have been caused by the capacitor transcending into the shadow realm - but that is the only time I remember anything odd happening to the chip. Since the modem is used in combination with the voxl2 in a research project at my university I'm not the only one that had his hands on it. Thus i can not rule out that a device was connected backwards causing this whole mess. Thank you for your time!

@Vinny thank you so much for the thorough and punctual response! I will give this rework a shot per your instruction and report back if I have any issues.

@swickliff please submit a request at https://modalai.com/rma .

@tom Yes. I removed "," from the config file and it worked. Thanks

@Aaky, yes if you change the camera configuration, just follow the same process: copy correct sensorbin (with correct slot id) to /usr/lib/camera/ as previously discussed confirm the camera is detected using voxl-camera-server -l update camera config xml with correct camera ids - the camera id’s will start with zero and increment by 1 for each camera. The camera id assignment happens in order of the camera slot id. Slot id is mapped to the physical connector. You may want to remove unused sensorbins from /usr/lib/camera just to avoid any confusion. You can always get them back from /usr/share/modalai/chi-cdk

@Nick-Stroumtsos Moderator said in Power supply brownout w/ the Microhard Carrier USB Dongle @Nick-Stroumtsos Our carrier board design is a few years old, there's a good chance it won't meet this newer spec. That is correct, it is not going to be supported on this design. We designed for the 30dBm max power modes from several years ago as shown here: [image: 1708033819478-f1f632e6-b6ae-4764-9042-22ea4426fe05-image.png] We have a power consumption table in our tech docs that helps a user determine the limits for various modes: https://docs.modalai.com/microhard-add-on-datasheet/#power-consumption but nothing above 30dBm. We'd need new hardware for that. Sorry, but at least hopefully that explains the behaviors you are seeing.

@Darshit-Desai , yes, feel free to modify the code as you need for right now for your own testing. Once i have a chance, i will make the mode selection (long / short) and FPS more flexible. I hope this unblocked your work and you can move forward. Alex

@Alex-Kushleyev , I think that is plenty for now. We will order a couple and test them. Thanks a lot!

@Vinny , Thanks for the speedy response and for the recommendations. I will discuss the options with my team. That dongle sounds like a good alternative for this use case. Jacob

@MChehadeh yeah it is simply 1/1024. Powers of 2 for faster calculations Integral is scaled down a lot because it accumulates fast at 10khz update rate

@MChehadeh , thank you for being flexible

Hi @Jetson-Nano, we only support flashing the 915Mhz BetaFPV Nano Rx via voxl2. You will need to follow the instructions on the ELRS website to flash the 2.4G RX that you have, search on this quickstart page in the receivers section and follow the instructions for your particular rx. You can download the ELRS configurator which is the tool provided by ELRS for flashing transmitters and receivers. -Jacob

@Abdullah01 , the original issue was that ESC calibration was actually done without propellers mounted, you can see the current at 94% power was very small, 0.4A However, the script still produced the a0, a1, a2 parameters (which would have been wrong to use because calibration was done without a propeller..) The error at the end was a result of attempted plot - since voxl2 does not have a display attached, the plot failed. Since that version, we have transitioned to using plotly for plotting, and calibration plots are saved to disk in addition to attempt to plot it to display. The plot feature was updated after SDK 1.1.2 release, but you can get it directly from gitlab here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-tools/voxl-esc-calibrate.py (just get the whole voxl-esc repo from dev branch on your voxl2 and run the calibration procedure). Meanwhile, we will add additional checking of the calibration to catch the conditions that do not look like proper calibration (when propeller is not mounted, etc..).

@Jeremy-Frederick Can you try to lower the bitrate or resolution to see if it's a bandwidth issue? I understand that, in theory, the rendering software (VLC or QGC) shouldn't matter for your issue. But, it typically helps to see if there is a config that will work reliably and then push it from there.