Skip to content
  • 0 Votes
    1 Posts
    12 Views
    No one has replied
  • Power issues at the initial startup

    Unsolved Development Drones
    3
    0 Votes
    3 Posts
    118 Views
    J
    One detail worth adding to Vinny's list: whether the desktop port can itself supply power. Plenty of USB-C ports, and PD chargers or cables, will push 5V or more into the board, and on designs where the battery input and USB input share a power path, that contention is a plausible place for heat to build near the connector. Mentioning it in the RMA may help them check the right area first.
  • M0022 PWM Breakout Board: 8-Channel Output Pinout

    Solved General Questions
    2
    1
    0 Votes
    2 Posts
    73 Views
    VinnyV
    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.
  • 0 Votes
    2 Posts
    69 Views
    Hector NevarezH
    Hi Ilan, Secure boot isn't something we've validated on VOXL 2 ourselves. To answer your questions, we did a one-off test: we re-signed the images from our flatbuild with a throwaway test key and checked that SecTools could sign and validate them. We haven't flashed re-signed images, booted them, or fused a board. Please treat the below as what we believe the path is, not a tested procedure. One caution before you blow any fuses: QFPROM fuses are one-time and can't be undone. A wrong key hash, OEM ID or Model ID, or any image in the boot chain signed with the wrong key, could permanently brick the board. We'd recommend flashing your signed images on an unfused board first and making sure everything boots and runs, then fusing a board for real. Unsigned boot images for the current VOXL 2 system image (XBL, TZ, devcfg, AOP, DSP and modem firmware, ABL), or a build path that produces them. You'll need to go to downloads.modalai.com to get the flatbuild for M0054-1. It's under downloads/Flat Builds/M0054(154)-1.zip. It has the boot images (XBL, TZ, devcfg, AOP, ABL), the DSP firmware (inside NON-HLOS.bin), and the firehose programmer. These images aren't unsigned. They're signed with Qualcomm's default SecTools test key, with OEM ID and Model ID set to 0x0000. We believe you can re-sign them with your own key rather than starting from unsigned images. In our test, SecTools replaced only the signature and the code stayed the same. A few images (TZ, QUP firmware, and part of XBL) also carry a Qualcomm production signature, and SecTools kept it when we re-signed. The OEM ID and Model ID used on VOXL 2, and any sec.dat or fuse settings you use or recommend. We don't sign the images with our own key. The flatbuild carries Qualcomm's default test signature with OEM ID and Model ID at 0x0000. We don't ship a sec.dat and don't blow any secure boot fuses, so we don't believe there's anything from our side you'd need to match. Whatever OEM ID and Model ID you choose should match between your fuse settings and the images you sign. A firehose programmer we can sign with our key, so fused units can still be flashed over EDL. Does the VOXL 2 flash flow (QDL, fastboot) work with a signed firehose? The firehose programmer is in the flatbuild as ufs/prog_firehose_ddr.elf, and we were able to re-sign it the same way as the other images. We haven't tested our flash flow on a fused board, so we can't say yet whether QDL or fastboot work there. Make sure you have a working signed firehose before you fuse, since that's likely your only way to recover a board over EDL. Are any QFPROM fuses blown on shipped units? No, we don't blow QFPROM fuses on shipped units. Does the current system image use ICE inline encryption (FBE) for /data? If yes, where are the keys held (TEE, RPMB)? No. /data isn't encrypted; it's a plain ext4 partition. The kernel has inline encryption support built in, but our image doesn't set it up, so there's no key storage to describe on our side. Does ABL support verified boot (AVB) for the kernel and root filesystem? Not at the moment. ABL has support for verified boot and dm-verity, but both are turned off in our build. The boot image has no AVB footer and the vbmeta partitions are empty, so ABL boots the kernel without checking it. Turning it on would mean rebuilding ABL with verified boot enabled and signing the boot image with your key. dm-verity also needs a read-only root filesystem, and VOXL 2's rootfs is read-write today, so that part would be a bigger change. Any known issues or guidance for secure boot on VOXL 2. The main one we expect is that PX4 on the DSP will likely stop working. VOXL 2 generates a per-device test signature at first boot so PX4 and our sensor code can run on the sensors DSP (SLPI). We don't expect test signatures to be accepted on a fused board, so those DSP libraries would need production signing before PX4 will load. Depending on the method, that may need a rebuilt SLPI firmware from our side, so please let us know before you fuse if you need PX4 running. Let me know if you have additional questions thanks!
  • 0 Votes
    2 Posts
    744 Views
    J
    Probably not fully out of the box. Starling 2 can support GPS-denied flight using VIO and onboard compute, but a sewer pipe adds low light, few visual features, tight clearance, and unreliable communications. Autonomous inspection would likely need a tuned SLAM/localization setup, obstacle sensing matched to the pipe profile, lighting, and a fail-safe flight plan. Test incrementally in a mock tunnel first. Check with ModalAI about the stock flight stack’s sensor and autonomy limits for your exact configuration.
  • FLIR Lepton on Starling 2 Max

    Unsolved Development Drones starling
    5
    0 Votes
    5 Posts
    661 Views
    Alex KushleyevA
    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.
  • 0 Votes
    10 Posts
    493 Views
    Y
    @Moderator Thank you very much for the clear answers on the prop guards, payload, and lead time. They were very helpful for our planning. Given the lead time (about 60 business days) and the need to design the payload mount ourselves, we have decided to start our indoor autonomous flight tests with a smaller drone that we can get right away. We may consider the Starling 2 Max again for a later phase. Thank you again to Eric, Tom, and the ModalAI team for your support.
  • Starling 2 Max – Using the AWUS036EACS in Japan (2.4 GHz only)

    Unsolved Development Drones
    5
    0 Votes
    5 Posts
    117 Views
    Y
    Hello, Thank you very much for your detailed reply, and for clarifying that our unit uses the M0213 (Sparrow) rather than the Alfa adapter. This was very helpful. We also appreciate you updating the setup steps and the M0213 page so quickly. The 2.4 GHz-only configuration and the FCC information are exactly what we needed. We will contact Bots Unlimited about the transmit power, Bluetooth and RF kill, and email contact@modalai.com with our order number for the official configuration documents. Thank you again for your support. Yuta Ohtani JDSC Inc.
  • 0 Votes
    3 Posts
    2k Views
    M
    for what it's worth, I believe I am seeing the phenomenon @adroneguy describes. if the exposed IMU surface is cooler than the IMU PCB side, I get significant negative drift on Z bias. It's the same effect whether I create the temperature gradient by loading the CPU heavily to warm up the PCB side, or if I use a fan to blow air across the IMU surface... the bias shifts in the same negative direction regardless of absolute temperature, then returns more positive when the gradient disappears. Tested this on the voxl2 mini, which has the same IMU TDK ICM-42688-P. -edit- I should say, I am still trying to work out what to do about it. The IMU sits in the void between the main board and the camera breakout, so I am going to try sealing the gaps between the two boards to avoid airflow through the gap... then hope that cooling the device with a fan on the RAM-side of the main board will be sufficient. This is not a recommendation at this point, just an idea I am going to try
  • 0 Votes
    10 Posts
    358 Views
    Alex KushleyevA
    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) [image: 1794804520158-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...
  • 0 Votes
    1 Posts
    51 Views
    No one has replied
  • 0 Votes
    3 Posts
    208 Views
    Alex KushleyevA
    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.
  • AR0144 Global Shutter Tracking Sensor Replacement Lenses

    Solved VOXL 2 and VOXL 2 Mini
    4
    0 Votes
    4 Posts
    300 Views
    Alex KushleyevA
    @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.
  • 0 Votes
    3 Posts
    115 Views
    Leon GurevichL
    @tom Hi Tom, thank you for the prompt response. It is much appreciated.
  • 0 Votes
    6 Posts
    271 Views
    VinnyV
    Hi @김다연 On that same page is this link [image: 1794541383152-a2f37d2d-c828-4f32-84f2-63440b85c7d7-image.jpeg] It should have all the info you need.
  • Bots Unlimited Wifi Crash

    Solved General Questions
    16
    -1 Votes
    16 Posts
    1k Views
    L
    Going to close this ticket out since it seems to have resolved the issue for the user
  • Configuring a iFlight Commando 8 radio transmitter

    Unsolved ESCs, Sensors and Accessories
    5
    0 Votes
    5 Posts
    536 Views
    Alex KushleyevA
    @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
  • 0 Votes
    7 Posts
    346 Views
    Alex KushleyevA
    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. [image: 1794462369745-68e2b39c-c885-4c17-aa24-ed28cb1c7da5-image-resized.jpeg]
  • Starling 2 px4 topic description document?

    Unsolved Development Drones
    2
    0 Votes
    2 Posts
    102 Views
    tomT
    Hi @kdeshmu2, the PX4 uORB message reference has a page per message with field descriptions and units where PX4 defines them: https://docs.px4.io/v1.18/en/msg_docs/ For the motor topics on Starling 2 (VOXL ESC), we added a table here: https://docs.modalai.com/voxl-px4-files/#logged-topic-contents In short: actuator_motors: motor commands from the control allocator, normalized 0 to 1 actuator_outputs: the same commands scaled by the voxl_esc driver to RPM, between VOXL_ESC_RPM_MIN and VOXL_ESC_RPM_MAX esc_status: ESC feedback per motor (measured RPM, voltage, current, temperature, power) The voxl_esc driver source is here if you want to see exactly how the outputs are produced: https://github.com/modalai/px4-firmware/tree/voxl-dev/src/drivers/actuators/voxl_esc
  • VOXL 2 IMX377/IMX412 support and configuration

    Unsolved VOXL 2 and VOXL 2 Mini voxl-2
    6
    0 Votes
    6 Posts
    1k Views
    tomT
    Hi @K.Stute, IMX377 never became a supported sensor on VOXL 2, and the M0026 IMX377 module is end of life. What is on the board today: The system image ships a sensor module driver for IMX377, but only for camera slot 3 (J7 upper, which is M0084 JU): /usr/share/modalai/chi-cdk/imx377/com.qti.sensormodule.imx377_3.bin voxl-camera-server has no imx377 sensor type, and none of the standard camera configs use it, so voxl-configure-cameras can't set it up. The sensor types the server accepts are listed in common_defs.h. If you want to experiment anyway: copy that bin into /usr/lib/camera, plug the camera into J7 upper, check dmesg for imx377 probe succeeded, then start from an IMX214 hires config on slot 3 and change the resolutions to match the IMX377. That is untested on VOXL 2 and we can't support it. For a 4K hires camera on VOXL 2 we recommend the IMX412 (M0107 or M0161). It has drivers for several slots and is used in the standard camera configs. See VOXL 2 Image Sensors and VOXL 2 Camera Configs.