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

ModalAI Forum

Veteran

Private

Posts


  • Various Questions Regarding Starling 2 MAX
    ModeratorM Moderator

    Hi NECAM,

    Thank you for your interest in the Starling 2 MAX. Here is what we can share now, along with the items we're still collecting.

    1. Battery volumetric energy density

    The Starling 2 MAX battery is a 2S1P lithium-ion pack (7.2 V nominal, 5.0 Ah, about 36 Wh) built from Amprius SA124 21700 cells.

    • Pack: approximately 540 Wh/L. This is based on the pack's outer dimensions of about 71 × 43 × 22 mm, with the lead wires and connector excluded.
    • Cell: Amprius specifies the SA124 at about 690 Wh/L and about 260 Wh/kg (at C/5).

    2. Safety standards and certifications

    • Cell (Amprius SA124): Amprius's published technical datasheet lists UN 38.3, IEC 62133, PSE, CE and BIS. We're requesting the certificate and report numbers.
    • Battery pack: We're requesting the UN 38.3 test summary, the SDS, and any pack-level IEC, UL or PSE certificates from our pack supplier.
    • Aircraft: The Starling 2 MAX is a development kit, built with the intention of being modified by the user. It is not certified as a finished end product to IEC, UL/EN or JIS standards. Any certification required for your final application would apply to the system as you configure and deploy it.

    3. Product liability (PL) labeling

    The shipping package is labeled with the appropriate lithium-ion battery markings. Because the Starling 2 MAX is a development kit, no additional PL labeling is applied to the aircraft.

    We'll update this thread as the battery documents come in. Starling 2 MAX documentation is available at https://docs.modalai.com.

    Best regards,
    ModalAI

    General Questions

  • M0187 Lepton Adapter Board – Purchase Inquiry and Delivery to South Korea
    tomT tom

    @김다연 please email sales@modalai.com directly and they can address all of your questions.

    General Questions

  • M0022 PWM Breakout Board: 8-Channel Output Pinout
    VinnyV Vinny

    Hi,

    Yes, each column is one channel. The full pinout is now in the VOXL 2 IO datasheet, under J1. For the M0022 Rev A:

    Rows

    • The row nearest the 10-pin J1 connector (silkscreen S) carries the PWM signals.
    • The middle row is not connected.
    • The row at the far board edge (silkscreen G) is ground.

    Columns

    The silkscreen numbers the columns 1 to 8. With the silkscreen readable and J1 toward you, column 1 is on the left, at the same end as J1 pin 1. Column n carries PWM channel n from VOXL 2 IO J1:

    Column S row Middle row G row VOXL 2 IO J1 pin
    1 PWM CH1 Not connected GND 2
    2 PWM CH2 Not connected GND 3
    3 PWM CH3 Not connected GND 4
    4 PWM CH4 Not connected GND 5
    5 PWM CH5 Not connected GND 6
    6 PWM CH6 Not connected GND 7
    7 PWM CH7 Not connected GND 8
    8 PWM CH8 Not connected GND 9

    Power and ground

    • All eight G-row pins are tied together and to J1 pin 10 (GND).
    • There is no power rail on the header. VOXL 2 IO J1 pin 1 (5P0V_BOOST) reaches the M0022 connector but is not connected on the board, and the middle row is not connected to anything.
    • Power your ESCs or servos from their own supply. 5P0V_BOOST is a low-power reference only and must not power ESCs or servos: VOXL 2 IO datasheet, J1.
    General Questions

  • Power issues at the initial startup
    VinnyV Vinny

    Hi @mmirtaba,

    Sorry for the slow reply. Disconnecting the USB-C cable and the batteries right away was the right call.

    Please do not power the drone again, from the batteries or from USB. Open an RMA here and reference order 8701: https://www.modalai.com/pages/rma

    Every Starling 2 Max is flight tested before it ships. So we can start looking into it before the unit arrives, please reply here with:

    • Photos of the drone, including any part that looks discolored or damaged
    • Where the heat and the smell seemed to come from, if you noticed
    • Which port on the drone the USB-C cable was plugged into, and what it connected to on the desktop (a USB-C port, or a USB-A port through an adapter)
    • Which operating system the desktop runs, and what "searching for the required drivers" involved (for example a Windows pop-up, Device Manager, or downloading something)
    • Roughly how long the drone was running on batteries before you plugged in the USB-C cable
    • Roughly how long after plugging in the cable you noticed the smell
    Development Drones

  • 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

  • Starling 2 Max – Using the AWUS036EACS in Japan (2.4 GHz only)
    tomT tom

    Hi Yuta,

    Thanks for checking the unit, and sorry for the confusion. Your unit's -M36 option is the M0213 VOXL 2 Wifi Addon (Bots Unlimited SP-01-100 "Sparrow"), not the Alfa adapter.

    2.4 GHz-only operation: Yes, the same procedure applies, with different interface names. The M0213 creates uap0 for SoftAP and mlan0 for Station, and can run both at once. In SoftAP mode, "voxl-wifi softap <ssid> <password>" writes hw_mode=g and channel=6 to /data/misc/wifi/hostapd.conf with interface=uap0; add country_code=JP to that file. For Station mode the file is /etc/wpa_supplicant/wpa_supplicant-mlan0.conf; add country=JP and the 2.4 GHz freq_list there, then restart wpa_supplicant@mlan0. If you do not need Station mode, leave it disabled. We added the M0213 interface names to the setup steps: https://docs.modalai.com/voxl-2-wifi-setup/#regional-settings-and-24-ghz-only-operation

    FCC certification: The FCC grant for FCC ID 2BPPF-SP01 was issued on September 24, 2025. Our M0213 page still said "pending"; it is now corrected: https://docs.modalai.com/m0213/

    Transmit power, Bluetooth, and RF kill: These depend on the Sparrow module's driver and firmware, so Bots Unlimited is the best source for the default transmit power, how to cap it at 23 dBm or less persistently, whether the Bluetooth radio can transmit, and how to use the hardware RF kill. You can reach them here: https://botsunlimited.com/contact/

    Hardware configuration: For official documentation of the configuration shipped on your order, please email contact@modalai.com with your order number.

    Development Drones

  • Starling 2 Max – Using the AWUS036EACS in Japan (2.4 GHz only)
    tomT tom

    Hi Yuta,

    1. 2.4 GHz-only operation: Yes. Note that units ship configured as a 5 GHz SoftAP on channel 149, so configure the unit before the adapter is ever powered in Japan: unplug the WiFi adapter, connect over adb, set up 2.4 GHz mode, then plug the adapter back in. In SoftAP mode, "voxl-wifi softap <ssid> <password>" writes hw_mode=g and channel=6 to /data/misc/wifi/hostapd.conf, and the voxl-softap service starts hostapd from that file at every boot. Also set country_code=JP in that file. In Station mode, add "country=JP" and a 2.4 GHz "freq_list" to /etc/wpa_supplicant/wpa_supplicant-wlan0.conf so wpa_supplicant does not scan or associate on 5 GHz. Both files persist across reboots, but running voxl-wifi again regenerates them, so re-apply the edits after any voxl-wifi command. The exact steps are here: https://docs.modalai.com/voxl-2-wifi-setup/#regional-settings-and-24-ghz-only-operation

    2. Maximum transmit power: Alfa specifies 17 dBm (about 50 mW) typical output power with a 2 dBi antenna, which is below 200 mW without any software limit.

    3. FCC ID: You are correct, 2AB878811 is the AWUS036ACS grant, and that row on our WiFi Setup page was wrong (it also listed the wrong chipset). The AWUS036EACS uses the Realtek RTL8821CU. We have corrected the WiFi Setup page and the Starling 2 Max datasheet. For the AWUS036EACS grant itself, please confirm the FCC ID with Alfa Network directly, since they hold the certification.

    4. Bluetooth: The adapter is a WiFi and Bluetooth combo, but the VOXL 2 kernel does not include the btusb driver or the Realtek Bluetooth firmware. The Bluetooth radio is never initialized and no Bluetooth interface exists on the Starling 2 Max.

    Development Drones

  • 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

Member List

Eric KatzfeyE Eric Katzfey
tomT tom
Chad SweetC Chad Sweet
modaltbM modaltb
VinnyV Vinny
ModeratorM Moderator
Zachary Lowell 0Z Zachary Lowell 0
wilkinsafW wilkinsaf
Jetson NanoJ Jetson Nano
Alex KushleyevA Alex Kushleyev
  • Login

  • Don't have an account? Register

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