Thank you very much @alex-kushleyev

Thank you! Ordering now

@sjt277 , I am sorry this happened to you. In order to help evaluate the issue, can you please post photos of both sides of the M0138 ESC board (high resolution, please, you could share a link if the forum does not accept it). Also please point out in the picture which component is getting hot. Also, since you are using a power supply, it should provide the current draw when you attempt to power on the ESC. Please let us know the voltage and current reading on the power supply and whether it is changing. Did the ESC work at first (spinning motors) and then stopped working at some point? Please note that testing ESCs using a power supply often lead to permanent damage due to regenerative spikes when the motor is braking (causing over-voltage). https://docs.modalai.com/voxl-escs/faq/#unboxing-and-testing-new-standalone-esc Alex

We have added the pinouts here: https://docs.modalai.com/M0155/

@patkirkmartin , so sorry for the delay. We are ready to proceed with sharing the source code for M0065 board and I just wanted to double check that you are still interested. Please let me know and we will get this going right away. If you use our APM, it will provide power for VOXL2 and the APM also includes voltage and total current sensing and has PX4 support for that. The information is delivered to px4 via I2C. If ModalAI ESCs are used, such as M0129 (mini esc) or M0138 (larger / racing ESC), they both provide power for VOXL and measure voltage and total current and provide this information to PX4 via telemetry via UART. Alex

@tom thank you

Thanks for the detailed report. A few notes based on what's in the log: The missing intrinsics files are not the cause of the abort — those ERROR in json_from_yaml, failed to open file / tracking_front_intrinsics.yml warnings are expected if you haven't run camera calibration yet, and voxl-camera-server falls back to default intrinsics. That's noise, not the crash. The actual "Aborted" with no further message is what we need to isolate. The docs' Debugging Camera Issues page is the right starting point for this class of failure, but the excerpt we have doesn't show the specific abort signature you're hitting, so I don't want to guess at root cause here. Can you get us: dmesg output right after the crash (look for a segfault/kernel oops around the same timestamp) Whether there's a core dump generated (check /data/core* or wherever core dumps land on your image) — if so, a backtrace via gdb would tell us exactly which line aborts Run voxl-camera-server under gdb directly (gdb --args voxl-camera-server, then run, then bt once it aborts) — this is the fastest way to get a real stack trace instead of guessing The "works after a couple of systemctl restart calls" behavior strongly suggests a race/init-order issue rather than a config problem — since your config itself (both the custom_camera_config.txt and generated voxl-camera-server.conf) looks structurally correct for two independent ar0144 cameras. One thing worth double checking: you're using ar0144-fsin-combo on J6_LOWER_COMBO1 for tracking_down, but I don't see a J6_LOWER_COMBO1_NAME2 or combo-mode field set — since this is a combo slot, confirm whether that flex is truly running in single-sensor mode. If the combo detection is flaky on init (i.e. it doesn't always see the second physical sensor consistently), that could cause a transient failure on cold start that clears on restart. Please also confirm which mach.var / carrier board (M0054) revision and whether tracking_down is on a combo flex physically wired for single-sensor use — a photo of the flex connection would help us rule out a physical/timing issue on that port.

@chiu-pk The LED status is good, this receiver should be recoverable assuming the wiring is correct. Could the M0184 firmware update have caused the receiver to lose its previous binding/configuration? Yes some updates will unbind the receiver. If you want to put the receiver back in bind mode and voxl-elrs doesn't work, hold the button for 5 seconds and it should enter bind mode indicated by the led status rapid double blink Is it expected that voxl-elrs ping gets no response while the receiver is waiting for binding? voxl-elrs ping should work in both cases, but to be sure try to bind and see if it works Is there a recommended recovery/reflash or reconfiguration procedure for the M0184 in this situation? Try to get voxl-elrs working if possible, if not then using the expresslrs configurator pointed to our custom fork of ELRS with a USB serial adapter that supports 420000 baud will allow you to update https://docs.modalai.com/elrs-configurator/

Hi @moderator The operating range is 2-6S input VBAT. We currently have no plans for >6S at this time on the ESCs. The 40V is a part rating which gives margin for safe operating limits, transient immunity, or other electrical effects. This is documented to instill confidence in our users that we selected quality parts capable of handling various conditions outside of nominal such as back-EMF, energy dumps, incorrect wiring, or severe transients. We are keeping tabs on the trends in this market and will ascertain for future products if increased operating points are warranted broadly. I do see up to 8S is becoming more popular, but it will increase size and cost of products to enable that capability. Thanks!

Could you post a log of the drone flip?

@MattK This is a generalized question but did your Starling Max 2 come with a ToF?

What i meant was that sometimes, depending on the frame design, the orientation of the cameras may change slightly over time. This can happen as the plastics can change shape due to exposure to heat, sunlight, humidity (depends on the plastics), bumps and crashes, etc. Additionally, there has been some research showing that the camera + lens intrinsics change over time / temperature, especially if the lenses are made of plastic (which is the case in our old OV7251-based fisheye modules, which use plastic lenses - although we have not characterized them vs temperature). It is possible to use stiffer and more stable materials (metals, carbon fiber) to ensure that the sensor mounting remains consistent over time. I hope that answers your questions. Alex

@Alex-Kushleyev Hey Alex. Thanks for this input. I will incorporate your feedback as we continue initial motor testing and let you know if we need further guidance. Much appreciated!

What is the physical connection between the Optical flow unit and the FC? Is it a UART? Which optical flow unit are you using?

Hi @awagner Apologies for the delayed response. It looks like this post slipped through during our recent forum and documentation site refactor. Are you still experiencing issues with your M0041-4? A few clarifying questions will help: When you mention "that is dead too", can you please clarify what exactly is no longer working? The M0041-4 power module, the VOXL 2 Mini, your power supply, or some combination of the three? Can you share more details about your ESC, make, model, and how the battery pads are connected to the power module? A photo of your wiring connections would be very helpful here. On the spark at plug-in: direct battery connection is the standard way to power up a drone, so that in itself is not unexpected. The spark on connection is not uncommon with a 6S pack due to charge balancing and inrush transient at the moment of contact (especially with our FPV ESC with near 1,000uF of capacitance). That said, we do include protection on the M0041-4 for this reason, so something unusual may have happened in your specific setup, which is why we'd like to see the connections. As a general note, we typically see XT-30 used up to 4S and XT-60 up to 6S. Running 6S on an XT-30 is outside the more common usage pattern and worth flagging as a potential factor. We had some folks mistake a 4S ESC for 6S due to exactly that on early Stinger models. We've since remedied that. One practical note: depending on what has failed, a replacement power module may be a faster and cheaper path than a full debug effort. That said, we do want to help you identify the root cause so this does not repeat. Replacing hardware without understanding the failure just puts the next module at the same risk. Let us know and share photos if you can. Again, sorry for the long delayed response. Thanks!

We do not support DSHOT when using Voxl2 + IO Expander board. However, OneShot125 is supported (though you would need to re-build voxl-px4 pakage and change the following scale factor : https://github.com/modalai/px4-firmware/blob/voxl-dev/src/drivers/voxl2_io/voxl2_io.hpp#L133) -- set MIXER_OUTPUT_TO_CMD_SCALE = 125 instead of 1000. This would reduce the actuator latency by 1-2ms (as long as the ESC supports OneShot125).

@vinny @alex-kushleyev @tom Thanks for the input guys! Happy to report it is all working as intended. Much appreciated.