Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

Alex KushleyevA

Alex Kushleyev

@Alex Kushleyev
ModalAI Team
Unfollow Follow
About
Posts
2.3k
Topics
1
Shares
0
Groups
4
Followers
13
Following
0

Posts

Recent Best Controversial

  • FLIR Lepton on Starling 2 Max
    Alex KushleyevA Alex Kushleyev

    yes, you can purchase the FLIR Lepton 3.5 and insert directly into the available socket. You will need to remove the plastic cover, which is shown in the image above, unfortunately the screw for that is on the other side of the frame, so you will need to take off VOXL2 in order to access the screws for the lepton cover. The Lepton sensor has a keyed socket, so it will only go in one way and will snap in place. The plastic cover is designed to prevent the sensor from falling out of the socket, since it's mounted facing down.

    Development Drones starling

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    The address remap works on VOXL2 for two AR0144 with the same SID on the the same CCI bus. Need a custom kernel.

    VOXL2 Kernel: https://storage.googleapis.com/modalai_public/temp/ar0144/qti-ubuntu-robotics-image-m0054-boot-1.0.1-ar0144-remap.img (variant 1.0.1, built off 1. 8.10. (https://docs.modalai.com/voxl2-voxl2-mini-system-image/#1810)

    Latest AR0144_V2 drivers. 40 variants. (pdf doc inside) : https://storage.googleapis.com/modalai_public/temp/ar0144/ar0144_v2_qrb5165_20261115.zip . The doc has explanation for all sensormodules and additional details.

    M0173 R5 : install 0 ohm to enable FSYNC in camera 1 (J4)
    0047a3af-58cd-49db-9809-34b7cb7ffb25-image.jpeg

    Quick install guide:

    #all unsynced, 0x20 SID in slot 1
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_nosync_0.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_nosync_6.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_0x20_1.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_2.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_5.bin /usr/lib/camera/
    adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
    
    #all synced (M0173 + M0181 default with R5 fix), 0x20 SID in slot 1
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_0.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_6.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_0x20_1.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_2.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_5.bin /usr/lib/camera/
    adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
    
    #all sync'ed except for slot 1 (M0173 + M0181 default without R5 fix), 0x20 SID in slot 1
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_0.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_6.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_0x20_1.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_2.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_5.bin /usr/lib/camera/
    adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
    
    #all unsynced, all same SID, use SID remap (with new kernel)
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_remap_0.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_6.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_remap_1.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_2.bin /usr/lib/camera/
    adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_5.bin /usr/lib/camera/
    adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
    
    
    # Camera Server Config
    
    ## without boson
    camera-server-config-helper ar0144_0:ar0144:0 ar0144_1:ar0144:1 ar0144_2:ar0144:2 ar0144_3:ar0144:3 ar0144_4:ar0144:4
    
    ## with boson
    camera-server-config-helper ar0144_0:ar0144:0 ar0144_1:ar0144:1 ar0144_2:ar0144:2 ar0144_3:ar0144:4 ar0144_4:ar0144:5 boson:boson-fpv:3
    
    ## configure gpio fsync (set manually or run below):
    sed -E -i '/"fsync_en":/c\  "fsync_en": true,' /etc/modalai/voxl-camera-server.conf
    sed -E -i '/"fsync_gpio":/c\    "fsync_gpio":   109,' /etc/modalai/voxl-camera-server.conf
    
    
    # start camera server and inspect (dont inspect all possible streams, as it will load up the system
    voxl-camera-server
    voxl-inspect-cam ar0144_0 ar0144_1 ar0144_2 ar0144_3 ar0144_4 boson320
    
    

    Please note that the camera server replaces the AR0144 timestamps with the closest fsync time if fsync_en is set to true, even if the unsync'ed AR0144 sensormodule is used.

    Another note, if you are using voxl-portal in multi view, only 6 connections are supported by Chrome browser (may be others), so if you open 6 camera views at the same time, the other functionality in voxl-portal may stop working (so you can limit to 5 streams in multi-view).

    when you use the SID remap functionality, you can check dmesg, look for:

    [ 4733.137530] CAM_INFO: CAM-SENSOR: cam_sensor_addr_move: 477 slot 1: moved sensor 0x356 from 0x30 to 0x32
    [ 4733.137535] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1145 CAM_ACQUIRE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x32
    [ 4733.137602] CAM_INFO: CAM-SENSOR: cam_sensor_addr_drop_soft_reset: 501 slot 1: dropped soft reset 0x301a=0x959 to keep address 0x32
    ...
    [ 4733.457870] CAM_INFO: CAM-SENSOR: cam_sensor_addr_move: 477 slot 6: moved sensor 0x356 from 0x30 to 0x22
    [ 4733.457876] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1145 CAM_ACQUIRE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x22
    [ 4733.457937] CAM_INFO: CAM-SENSOR: cam_sensor_addr_drop_soft_reset: 501 slot 6: dropped soft reset 0x301a=0x959 to keep address 0x22
    

    Please test it out and let me know how it goes.. I suggest testing one change at a time. I suggest testing the latest voxl-camera-server from dev branch, even if you are on older SDK. May need to update several packages. if you just install via apt (from dev), it will update automatically:

    • change apt sources to dev : /etc/apt/sources.list.d/modalai.list : deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/
    • apt update
    • apt install voxl-camera-server

    if you view the ar0144_*_misp_grey streams, they are with Lens Shading Correction applied. We also have improved Auto Exposure coming shortly for AR0144.

    I don't think i forgot anything... 🙂

    VOXL 2 and VOXL 2 Mini

  • Starling 2 Max STEP file (SKU MRB-D0012-4-V4-C28-T8-M36) - cannot receive download portal verification email
    Alex KushleyevA Alex Kushleyev

    please see : https://forum.modalai.com/topic/5529/starling-2-max-v4-c29-current-assembly-step-cad-availability -- this has a link to the latest Starling 2 Max V4 but in C29 configuration. Does that work for you? We will see if we can make a C28 version as well.

    General Questions

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    The setup worked exactly as you described above in the table.

    All 5 AR0144 are running sync'ed, i installed R5 in M0173 in order to patch through the sync line to camera in slot 1 (which also uses the alt slave id 0x20). The camera plugged into slot 1 has the resistor swap to make it 0x20. I have not tested the software SID remap, that will be next.

    I only have Boson320 at the moment, so that's what I tested, but Boson640 will work just as well. Lepton and Boson can run concurrently, so we have 7 cameras there.

    No frame losses, sync works
    0aa853c5-db42-49d3-8a31-3fabfba7d57a-image.jpeg

    output of voxl-inspect-cpu while running voxl-inspect-cam for the 7 streams (no voxl-portal).
    06e3510f-cc0b-43bd-8865-f70fdc087bbe-image.jpeg

    Do you have all the hardware needed to try this? if you just have M0173 without the resistor fix, you can run cam 1 without sync just for initial test.

    Alex

    VOXL 2 and VOXL 2 Mini

  • AR0144 Global Shutter Tracking Sensor Replacement Lenses
    Alex KushleyevA Alex Kushleyev

    @mrawding , just to follow up on my suggestion regarding trying different lenses. If you cannot find a standalone lens option, consider an option of buying another camera module (like a OV5640 designed for ESP32 or similar) and using a lens from that. I can see that there are many options with different lenses and they look like M7 thread. You can try extracting the lens from that camera (may need to dissolve the glue that holds the lens in the threads) and test it on AR0144. The AR0144 has 1/4" sensor size and max CRA of 28 degrees.

    VOXL 2 and VOXL 2 Mini

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    hi @박민솔 , thank you for clarifying

    A few follow up items:

    • The software-based slave id remap will work across camera server restarts because the Kernel will remap the ids during every camera power on. the cameras are powered on one at a time, so there is no race condition, so their slave ids can be remapped right after power on. If camera server is shut down and restarted, the Kernel will do this procedure again.
    • I am not sure if the change will make it into the SDK. The change should not affect any other camera including AR0144 in the standard modes of operation, but this would need to be tested. I will check with the team after testing.
    • Sure, the modified AR0144 is good as a fallback

    AR0144 vs IMX412

    • Please keep in mind that AR0144, even though is wide angle, has a significant lens shading, making the image at the edges harder to use. We do have LSC (lens shading correction) in our camera server, but there is loss of quality at the edges
    • if you do overlap of AR0144 cameras for 360 views, you will have to do LSC so that the seams are not obvious. You probably have thought of that, just wanted to make sure
    • Synchronization: we are experimenting with hardware-based and software-based sync of hires cameras, so that may be an option in the near future to sync IMX412 to the same pulse that AR0144 is using for sync.
    • rolling shutter effects. yes, that is a valid concern. by the way, we have been working on EIS with rolling shutter compensation that may be interesting for you to consider for the future. This is IMX412. Hand-held test with lots of shaking : https://www.youtube.com/watch?v=3Yh9mOs0apo
    • in any case let's continue with the 5x AR0144, i hope to do some testing later today.

    We are out of stock of Color AR0144, and there is currently no plan to make more, unfortunately, due to low demand.

    Alex

    VOXL 2 and VOXL 2 Mini

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    @박민솔 , i also wanted to double check. Is there a reason why you want 5x AR0144 and not a combination of AR0144 and IMX412? IMX412 is a very nice camera and has a good lens and provides much higher resoution image (up to 4040x3040). Is it the extra weight or rolling shutter the reason to choose all AR0144 ?

    VOXL 2 and VOXL 2 Mini

  • Configuring a iFlight Commando 8 radio transmitter
    Alex KushleyevA Alex Kushleyev

    @juancho248

    Sorry for the delay, please see the answers below:

    @juancho248 said:

    Which Starling 2 Max configuration provides the most suitable high-resolution RGB cameras for our application?

    All versions of Starling 2 Max come with dual IMX412 cameras (one front-facing, one down-facing).

    @juancho248 said:

    Is the C29 configuration currently supported, and what are its camera and depth-sensing capabilities?

    yes, c29 is supported. Note that TOF (depth sensor) does not work outdoors due to sunlight

    @juancho248 said:

    Can the RGB cameras be configured for downward-facing image acquisition?

    The rear IMX412 is already down-facing. The front camera is forward-facing, so you would need to make modification to make it down-facing

    @juancho248 said:

    Can the platform capture full-resolution still images programmatically, rather than only video frames?

    Yes, you can capture full resolution images, including RAW10 , which can be processed offline for best results. Processed YUV also supported.

    @juancho248 said:

    What camera controls are available through the SDK, including exposure, gain, image format, resolution, and capture timing?

    exposure, gain can be changed in real time. resolution can only be changed before camera server is started, but we support multiple streams with multiple resolutions (so you could have one full resolution stream for sparse captures and lower resolution for video feed). SW zoom is also available for processed images (YUV and video).

    @juancho248 said:

    Can captured images be associated with timestamps and available vehicle pose or localization metadata?

    yes, each image has metadata, including timestamp, exposure, gain. The timestamp is using linux monotonic time, which can be correlated with other data sources that are logged with same time source.

    @juancho248 said:

    What onboard storage options and image-transfer interfaces are supported?

    built-in storage (EMMC 120GB split into two partitions, typically at least 80-90GB free on a fresh system install - dont remember the exact number). you could support USB-based storage as well. Transfer images can be done using the USB / ADB interfrace. The adb itself is slow (<5MB/s) but a usb-ethernet can be enabled on the same USB connection, that is typically ~35MB/s transfers. If you use wifi on the drone, that is also an option. wifi speed depends on typical factors.

    @juancho248 said:

    Can images be stored locally during a mission and transferred after landing without requiring continuous Internet connectivity?

    Yes, as long as you don't run out of local storage. Note that RAW10 images from IMX412 at full resolution (4040x3040) are about 15MB each. YUV of the same resolution are 18MB each. You can also compress them to JPG on voxl2.

    Please let us know if you have any other questions of if I missed anything.

    Alex

    ESCs, Sensors and Accessories

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    Hi @박민솔 ,

    There is a way to change the AR0144 slave address in software (after camera hardware reset) so that to identical modules can coexist on the same CCI bus. In short, since the sensors are powered on one by one, during the AR0144 power on, the slave address can be changed (by the kernel) from the default address (0x30) to a new value, so that the camera no longer responds to the default value. So, the two conflicting AR0144 sensors would have their slave addresses changed to a different non-default value, then used as usual.

    We already tested this in another setup, but I am going to test this feature. A kernel change is required, but it is not significant. This would simplify things if it works. However, we do have the modified AR0144 cameras to order if you still wanted to go that route.

    VOXL 2 and VOXL 2 Mini

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    Alright, i will try to get this done by end of this week.

    A few notes:

    • Lepton and Boson can actually run together, so i will try that (since Lepton uses SPI, not MIPI protocol)
    • I will be testing with M0173 with resistor fix due to availability on my end
    • M0153 note about Voxl2 J7 is outdated. It works on Voxl2 J8 as well, in fact M0181 best fits into J8 and mounting hole aligns, see image below voxl2_m0181_j8.jpg
    • Boson and AR0144 have different CCI slave addresses, so they will not conflict
    • i will double check how to purchace the ALT address AR0144
    • will try to release the AR0144 drivers at the same time as i test, hopefully by end of this week
    VOXL 2 and VOXL 2 Mini

  • Starling 2 Max V4/C29: current assembly STEP / CAD availability
    Alex KushleyevA Alex Kushleyev

    Hello @elvis-bicharri ,

    Please take a look at the updated Starling 2 Max C29 V4 model : https://storage.googleapis.com/modalai_public/modal_drawings/MRB/D0012-Starling-2-Max-C29-V4-20261112.STEP

    You should be able to see all the sub assemblies and parts labeled now. Also, the model size (MB) is reduced.

    Please let us know if you need anything else.

    68e2b39c-c885-4c17-aa24-ed28cb1c7da5-image.jpeg

    Design Reviews and 3D Models

  • Starling 2 Max V4/C29: current assembly STEP / CAD availability
    Alex KushleyevA Alex Kushleyev

    @elvis-bicharri ,

    • This is the TOF module that is used in Starling 2 Max. https://docs.modalai.com/M0178/ The old (A65) version is obsolete and is no longer sold / used.

    • Based on knowledge of what the sensor looks like, you should be able to extract the measurements you need. Please let us know if you are still having issues.

    • Yes, the CAD posted above is C29 camera package, which includes the hi-res camera, tracking camera and TOF sensor all facing forward (tri-cam forward-facing setup)

    • Yes, the TOF sensor is oriented vertically and the FOV is rotated, so narrow FOV is horizonta : 86x106 degrees

    We are double checking the CAD model to make sure this is the correct V4 model, but i believe the above answers are still correct. The camera mount has not really changed between the revisions.

    We will get back to you soon.

    Alex

    Design Reviews and 3D Models

  • Boson 640 + Sterling 2 Max
    Alex KushleyevA Alex Kushleyev

    Hi @chris-pagnotta , yes it will work using M0181 adapter (provided in the kit) connected to VOXL2 J8.

    Please let me know if you need more details.

    Alex

    Development Drones

  • AR0144 Global Shutter Tracking Sensor Replacement Lenses
    Alex KushleyevA Alex Kushleyev

    Hi @mrawding , sorry for the delay.

    Unfortunately, we do not offer narrower FOV lenses for AR0144. You could try to find M7 thread lenses from 3rd party sources.

    It is probably easier to find a new lens than to make an adapter for a 3rd party camera module.. would be impossible for us to support it.

    Alex

    VOXL 2 and VOXL 2 Mini

  • M0155 GPIO 109 Sync Output and IR/EO Camera Synchronization
    Alex KushleyevA Alex Kushleyev

    Currently, none of the Thermal cameras (Boson) we support use hardware synchronization. The same is true for the EO cameras (IMX412, IMX664, etc).

    Only AR0144 cameras are currently enabled with sync input and correct sensormodule for the camera needs to be selected (either _combo or _fsin). Sorry this is a bit vague, not sure how detailed we need to discuss here.

    Also, please note that you cannot connect a thermal camera (Boson) via M0155 - this adapter is only for EO cameras. there is a difference in pinout and voltages provided. Please see https://www.modalai.com/products/m0155, it lists supported cameras.

    If you let us know what functionality you are trying to achieve, we can provide more guidance. Please describe all the cameras that you want to connect and which should by sync'ed. Is it only one EO or one IR (which)?

    Alex

    VOXL 2 and VOXL 2 Mini

  • VOXL 2 Mini: supported M0166 + M0161 camera and ranging configuration
    Alex KushleyevA Alex Kushleyev

    Hello @ישראל-בן-שלמה ,

    Sorry for the delay in the response. Please see below:

    @ישראל-בן-שלמה said:

    Can two M0166 no-IR cameras facing different directions be used by the supported VIO software, alongside simultaneous M0161 EO capture? Does VIO use both tracking cameras, or only one?

    Yes, our voxl-open-vins-server used multiple tracking cameras, if available. this is default in several of our setups. Besides that, M0161 can be used for video streaming and capture. We are also working on integrating rolling shutter cameras for VIO.

    @ישראל-בן-שלמה said:

    What carrier, ports and cable part numbers support this combination? Please point us to the applicable SDK version and camera/VIO configuration.

    Your configuration (2x AR0144, 1x IMX664) is C33 (see https://docs.modalai.com/M0195/). So you will need:

    • VOXL2 Mini
    • M0195 (M0188 would work too for this configuration). Main difference between them is that M0195 has support for a thermal sensor (e.g. Boson)
    • 2x M0166 + ucoax cable
    • 1x M0161 + ucoax cable

    If you are starting fresh, you should use latest released SDK. I will double check..

    @ישראל-בן-שלמה said:

    We’re also considering upward/downward ranging and one or two forward multizone ToF sensors. Which ModalAI modules and simultaneous connections are supported with the above camera configuration?

    Will check

    @ישראל-בן-שלמה said:

    Are board/cable weights and mechanical drawings available for the required parts?

    yes, you can find the weight and 3D files:
    https://docs.modalai.com/M0166/
    https://docs.modalai.com/M0186/
    https://docs.modalai.com/M0188/
    (any thing else? let us know we can fill in the missing info)

    VOXL 2 and VOXL 2 Mini

  • Feasibility check: 5x M0166 (AR0144) tracking cameras on a single VOXL 2
    Alex KushleyevA Alex Kushleyev

    Hello @박민솔 ,

    Your analysis is spot on. Let me provide answers to your questions:

    @박민솔 said:

    Is this layout supported, or at least expected to work, with the M0173 kernel config (platform config 1)? In particular, is sensor ID 5 (J8 upper) enabled in that kernel and usable with an AR0144 through M0172 J2U?

    Yes, this layout should work. For platform config , J8U slot is enabled for either full 4-lane hi-res camera or a tracking camera is just fine. M0172 or M0181 can be used (upper slot for both) and both patch through the common sync signal (GPIO 109 from voxl2).

    @박민솔 said:

    Is an alt-address (0x20) sensormodule for slot 1 included in the current SDK, or only in the zip shared in topic 5010? Is there an alt-address + fsin variant?

    we will include into the SDK / camera server (the sensormodules will be maintained here https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/tree/master/chi-cdk/qrb5165 ) and shipped with SDK soon.

    @박민솔 said:

    Frame sync: can all five cameras be synchronized on GPIO 109? Is the sync line routed to M0172 J2U, and does M0173 J4 (ID1) need any resistor changes (similar to R10/R11 on M0188)? Is an ar0144_fsin_5 sensormodule available?

    sync is routed to M0172 JU and M0181 JU. However, M0173 J4 (ID1) is missing a resistor (R5) connecting the sync to the camera. Note that M0226 has this resistor installed : https://docs.modalai.com/M0226/#image-sensor-synchronization. We will make fsin sensormodules available for all IDs. If you need to enable M0173, we can provide location of R5 for manual installation.

    @박민솔 said:

    Can ModalAI supply an M0166 with the alternate slave address pre-configured, so we don't have to modify the module ourselves and void the warranty?

    Depends on how many you need. We have a small quantity in stock.

    @박민솔 said:

    Are there known throughput limits (CSI / ISP / camera server CPU) for 5x AR0144 at 1280x800 @ 30 fps on VOXL 2?
    No limits that would prevent you from running 5x AR0144 at 1280x800 30fps. Up to 7 cameras is possible on voxl2, but unfortunately the limit is in the available interposer combinations - in this config two other slots are taken by TOF / Thermal camera (TOF has a different connector and Thermal cameras have different ucoax pinout, incompatible with regular cameras).

    This should be pretty quick to test, let me know if you want me to run the test, I can do it later this week.

    Any other questions?

    Alex

    VOXL 2 and VOXL 2 Mini

  • Design review for a 4.5 kg VOXL 2 quad with M0138 on 12-inch props
    Alex KushleyevA Alex Kushleyev

    @jake_eizy , I ran a quick model to predict the currents and ESC loss for the 12x6 prop. our database did not have the exact model for this prop, so there was a predicted model and an actual modal published by APC. I hope this helps.

    I can also provide some more details on best practices for testing new motors / props to reduce the chance of a failure while bench testing. I may be able to put that together into updated test scripts that we already have.

    Alex

    3110_10x5_15x6_prop_compare.png

    Design Reviews and 3D Models

  • Design review for a 4.5 kg VOXL 2 quad with M0138 on 12-inch props
    Alex KushleyevA Alex Kushleyev

    @jake_eizy , thank you for clarifying your estimated current draw. I think this changes things for the better.

    1. I no longer think that this is a risky configuration, but heat management is still very important. You will have to test to figure out exactly what to do because a lot depends on available air flow.
    2. See below plot from our sim, which matches the actual bus current from tests very closely. Based on the model, ESC power dissipation will be about 4-4.5W per motor at 4.5kg total weight (let's say 16-18W total for the 4-in-1 ESC). Also see below a 1 min hover test with 3110 motor, 10x5 propeller. The total weight is 3850g. it seems around 30 deg C ESC temperature rise at hover.

    3110_10x5_m0138_6s_model.png

    cc0caf8b-9e93-45b1-8002-1d72552f8fbe-image.jpeg

    1. Extra capacitance may not be required. I would recommend bench testing ESC response and quality (noise in actual reported rpm) with and without extra capacitor. For example, on our older ESC (M0134-6), we were recommending adding an extra cap for 6S applications. You would see noise in current measurements and also unstable RPM (wandering), as you can see in plot below, which suggests noisy zero crossing detection. RPM itself is not noisy because it is filtered. Also in this test, two motors were with propeller and two without. We can get some more debug info, if needed to see how noisy the zero crossing detection is.

    M0134-6 without cap (6s voltage)
    m0134-6_no_cap.png

    M0134-6 with cap (6s voltage)
    m0134-6_with_cap.png

    1. "Is there a starting value for max_rpm_delta you'd suggest for a 12-inch prop?" - you would have to test it yourself. The trade-off is current spike (and battery sag) vs ESC response time. The more you cap, the smoother the system is but it will respond slower, resulting in sluggish RPM control -> sluggish attitude control -> sluggish position control.
    Design Reviews and 3D Models

  • Design review for a 4.5 kg VOXL 2 quad with M0138 on 12-inch props
    Alex KushleyevA Alex Kushleyev

    Hello @jake_eizy ,

    I will try to answer the ESC-related questions.

    • The mosfets in M0138 ESC are rated for 100A+ continuous (each mosfet), so that is not going to be a limitation here.
    • At hover, for your application, we are talking about almost 2kW of power flowing through the ESC board and even at 2% efficiency, the ESC would dissipate 40W. I don't have the exact efficiency numbers, but it should be somewhere in that ballpark.
    • We have tested M0138 ESC with similar motors (3110 and 3115) with 10-inch props, drawing 80-85A during a very fast flight and the ESC temps were good (below 75C). The M0138 reports two temps from the MCU itself (the higher reading) and two board temps from separate temperature sensors.
      c1f2c969-2dd1-442e-a26d-9639a927f4fa-image.jpeg
    • in your case, the current draw will be 80A at hover, which means much less ambient air flow, compared to fast flight and your peak current draw will be almost double that.
    • We have done short continuous tests for about 120A total (24V) and there were no issues, but the ESC required a significant amount of air cooling
    • your application would push the M0138 ESC about 1.75x of what we have successfully tested in flight (in terms of total current through the ESC).
    • my main concern would be thermal management and secondary concern is that additional bulk capacitance may be required via external capacitors (relatively easy to add to the ESC power pads). another thing to check is integrity of UART communication (packet loss) due to high transients (our tools allow to check that).
    • The M0138 board does sense total current only, so no software current limiting (per ESC channel) is available. The max_rpm_delta term in the RPM controller serves the purpose of limiting the current during transition, as it limits the maximum rpm that is used to to compute the error term in the controller. Max rpm delta translates to some max voltage delta (Vbatt * duty cycle) and that, in turn, translate into max current during the rpm transition. This is what we have right now in terms of software limits on current spikes.
    • the 12-inch propeller is just fine. the diameter does not matter, but the load on the motor does. You would need to do basic motor tuning, as described here (we can help with that as well) : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md

    In summary, i would say that this would be a potentially doable but quite risky goal to achieve (80A continuous, 150A peak) . Would definitely need heat spreaders on both sides of the ESC board and a lot of airflow. the 4-in-1 ESC, being central to the vehicle, could be hard to get enough airflow, compared to single ESCs mounted on the arms, right under the propeller air flow (or in that area). Individual ESCs would not only have more thermal mass, board area, but also would have access to significant air flow. Also, any time you try to push the limits, you should start testing lower loads and build confidence that your set up is working properly and check everything along the way, including board temps, noise on commanded motor rpms (which can significantly add to the motor and ESC heating up). Unfortunately, we do not offer single ESCs, only 4-in-1.

    I hope that answers your ESC questions. My colleague should follow up with other answers.

    Alex

    Design Reviews and 3D Models
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups