1. ModalAI Support Forum
  2. Ask your questions right here!

Subcategories

  • 155 Topics
    710 Posts
    Alex KushleyevA
    @astro_phil , I just tested your configuration on voxl2 mini ov7251 connected to M0135 JL imx214 connected to M0135 JU M0135 interposer connected to Voxl2 mini J7 cameras are connected to hardware camera slots 2 and 3 respectively This particular board is using an old SDK but it should not matter, kernel variant 2.0.0 hw platform: M0104 mach.var: 2.0.0 -------------------------------------------------------------------------------- voxl-suite: 1.3.3 voxl-camera-server -l DEBUG: Attempting to open the hal module DEBUG: SUCCESS: Camera module opened on attempt 0 DEBUG: ----------- Number of cameras: 2 DEBUG: Cam idx: 0, Cam slot: 2, Slave Address: 0x00E2, Sensor Id: 0x7750 DEBUG: Cam idx: 1, Cam slot: 3, Slave Address: 0x0020, Sensor Id: 0x0214 DEBUG: Note: This list comes from the HAL module and may not be indicative DEBUG: of configurations that have full pipelines DEBUG: Number of cameras: 2 dmesg: [ 209.617719] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully [ 209.648730] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59 [ 209.649003] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55 [ 209.649103] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60 [ 209.649137] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79 [ 209.666156] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x20,sensor_id:0x214 [ 209.666263] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79 [ 209.670389] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60 [ 209.670476] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55 [ 209.670541] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59 [ 209.688989] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59 [ 209.691170] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55 [ 209.693356] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60 [ 209.693454] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79 [ 209.717968] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index : 2538021044 [ 209.717979] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address : 0xE2 [ 209.717988] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x7750 [ 209.717997] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71 [ 209.718308] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 770 [Applying Alternative Address] : Probe : Alternate address updated [ 209.718543] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:2,slave_addr:0xe2,sensor_id:0x7750 I also tested the same configuration in J6: voxl-camera-server -l DEBUG: Attempting to open the hal module DEBUG: SUCCESS: Camera module opened on attempt 0 DEBUG: ----------- Number of cameras: 2 DEBUG: Cam idx: 0, Cam slot: 0, Slave Address: 0x00E2, Sensor Id: 0x7750 DEBUG: Cam idx: 1, Cam slot: 1, Slave Address: 0x0020, Sensor Id: 0x0214 DEBUG: Note: This list comes from the HAL module and may not be indicative DEBUG: of configurations that have full pipelines DEBUG: Number of cameras: 2 dmesg [ 216.996797] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully [ 217.029303] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58 [ 217.029395] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.55 [ 217.029484] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60 [ 217.029516] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79 [ 217.046069] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:1,slave_addr:0x20,sensor_id:0x214 [ 217.046191] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79 [ 217.050324] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60 [ 217.050407] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.55 [ 217.050470] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58 [ 217.069409] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58 [ 217.071541] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.55 [ 217.073710] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60 [ 217.073801] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79 [ 217.097221] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index : 390152372 [ 217.097229] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address : 0xE2 [ 217.097234] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x7750 [ 217.097239] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71 [ 217.097532] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 770 [Applying Alternative Address] : Probe : Alternate address updated [ 217.097747] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:0,slave_addr:0xe2,sensor_id:0x7750 By the way, i think the SDKs are now not including the imx214 driver for slot 1. If you need it, you can use the following drivers https://storage.googleapis.com/modalai_public/temp/imx214_test_bins/imx214_eis_drivers_20250815.zip for all camera slots. The only functional change of these drivers is that the maximum resolution of the sensor has been changed from 4208 x 3120 to 4196 x 3120 due to some optimizations in gpu-based debayering that require certain image width (long story, but you can still use this driver, just may need to adjust your camera server config so that you are not requesting impossible resolution). When you do your tests, please make sure you have the correct sensormodule id's for each camera in /usr/lib/camera . The slot number where the camera is physically plugged in has to match the index at the end of the sensormodule file name (before .bin). Alex

  • Do you have a great idea for our products you would like to see implemented?

    26 Topics
    89 Posts
    Andriy LomakinA
    Dear Sir or Madam, We are currently evaluating navigation technologies for UAV and robotic platforms operating in GNSS-denied and contested environments. In particular, we are interested in solutions capable of operating without GPS/GNSS and, where possible, without relying on active radio-frequency communication links. Could you please provide information on your relevant products, including: GNSS-denied navigation capability; GPS-independent positioning; visual-inertial odometry, SLAM, inertial or terrain/map-based navigation capabilities; operation in radio-silent mode; integration options with UAV autopilots such as PX4, ArduPilot or proprietary flight controllers; technical specifications; pricing indication; delivery terms for Europe; export-control or end-user restrictions, if applicable. We would be grateful if you could also indicate the most appropriate contact person or department for further technical and commercial discussion. Kind regards, Andriy Lomakin

  • Are you looking for a 3D model of one of our products?

    33 Topics
    86 Posts
    Alex KushleyevA
    @nl_vdi , if you log into developer.modalai.com, you will see the CAD models. the latest model we have is: D0012-4-V3-C28-M36-T7-K0-Starling2-Max-V3-20260317.step [image: 1781036132877-376bf0dd-494a-4bf1-8d92-1b2d91afb83d-image.png]
Log in to post
Load new posts
  • Aldo Castro FreireA

    No able to get LTE strength

    3
    0 Votes
    3 Posts
    575 Views
    tomT
    You can download the Sierra WP7610 AT command data sheet from here to check what AT commands are supported: https://source.sierrawireless.com/resources/airprime/software/airprime_wpx5xx_wp76xx_wp77xx_at_command_reference/
  • Pavel ArdashovP

    Flight Deck error after arm

    8
    0 Votes
    8 Posts
    1k Views
    Pavel ArdashovP
    @modaltb my FlightDeck have a barometer 3D printed cap. But it was not tight, there was a groove in it. Maybe it was planned? By completely closing the barometer, we fixed the problem.
  • J

    voxl-emulator won't start

    3
    1 Votes
    3 Posts
    910 Views
    J
    Update: I completely removed docker and voxl-docker from my system. I rebooted, reinstalled docker, and followed these steps to install voxl-docker. Now, I get a different error (same as here) : jared@jared-ubuntu:~/voxl-docker$ voxl-docker -i voxl-emulator -e "/bin/bash" launching image: voxl-emulator with the following command: docker run --rm -it --net=host --privileged -w /home/jared --volume=/dev/bus/usb:/dev/bus/usb -e LOCAL_USER_ID=0 -e LOCAL_USER_NAME=root -e LOCAL_GID=0 -v /home/jared/voxl-docker:/home/root:rw -w /home/root voxl-emulator /bin/bash standard_init_linux.go:228: exec user process caused: exec format error I followed the instructions at the link. The first two commands ran without any issues. I had to modify the last one to fit my architecture: sudo apt-get install qemu binfmt-support qemu-user-static docker run --rm --privileged multiarch/qemu-user-static --reset -p yes jared@jared-ubuntu:~/voxl-docker$ docker run --rm -t amd64/ubuntu uname -m Unable to find image 'amd64/ubuntu:latest' locally latest: Pulling from amd64/ubuntu 7b1a6ab2e44d: Pull complete Digest: sha256:7cc0576c7c0ec2384de5cbf245f41567e922aab1b075f3e8ad565f508032df17 Status: Downloaded newer image for amd64/ubuntu:latest x86_64 That worked. Now the voxl-emulator appears to work too: jared@jared-ubuntu:~/voxl-docker$ voxl-docker -i voxl-emulator -e "/bin/bash" launching image: voxl-emulator with the following command: docker run --rm -it --net=host --privileged -w /home/jared --volume=/dev/bus/usb:/dev/bus/usb -e LOCAL_USER_ID=0 -e LOCAL_USER_NAME=root -e LOCAL_GID=0 -v /home/jared/voxl-docker:/home/root:rw -w /home/root voxl-emulator /bin/bash + USER_ID=0 + USER_NAME=root + GID=0 + getent group 0 root:x:0: + echo 'Starting with UID : 0' Starting with UID : 0 + useradd --shell /bin/bash -u 0 -g 0 -o -c '' -M root useradd: user 'root' already exists + addgroup root users + export HOME=/home/root + HOME=/home/root + ls -ld /home/root drwxrwxr-x 8 james host_group 4096 Nov 1 21:45 /home/root + echo 'root ALL=(ALL) NOPASSWD: ALL' + ls -l /etc/sudoers.d/ total 8 -rw-r--r-- 1 root root 30 Nov 23 2020 james -rw-r--r-- 1 root root 29 Nov 1 22:26 root + cat /etc/sudoers.d/root root ALL=(ALL) NOPASSWD: ALL + chmod 777 /tmp + chmod 711 /usr/bin/sudo + chmod +s /usr/bin/sudo + ls -l /usr/local/bin/su-exec -rwxr-xr-x 1 root root 7660 Aug 14 2018 /usr/local/bin/su-exec + ls -l /bin/bash -rwxrwxrwx 1 root root 959344 Aug 12 2018 /bin/bash + echo 'exec /usr/local/bin/su-exec root /bin/bash' exec /usr/local/bin/su-exec root /bin/bash + exec /usr/local/bin/su-exec root /bin/bash bash-4.3#
  • R

    Python IDE on voxl ubuntu docker

    2
    0 Votes
    2 Posts
    306 Views
    Chad SweetC
    We do not have any experience with Python IDEs, sorry. There's no reason any IDE that supports remote debugging with Ubuntu wouldn't work. Check the Docker networking documentation if you run into any issues
  • J

    ESCs not "seeing" VOXL Flight FC

    6
    0 Votes
    6 Posts
    1k Views
    modaltbM
    Yes that shouldn’t be a problem.
  • J

    voxl-tflite-server not working on latest SW

    7
    0 Votes
    7 Posts
    1k Views
    J
    I already had voxl-utils v0.8.2 installed (see earlier post), so I did not update that. I downloaded voxl-tflite-server v0.1.6 from http://voxl-packages.modalai.com/dev/ and adb push'ed it to my voxl. I then installed it (opkg install ipk/voxl-tflite-server_0.1.6_202110292056.ipk) and rebooted my voxl. I saw the same behavior as before until I modified /etc/modalai/voxl-tflite-server.conf. Once I set "input_pipe": "/run/mpa/hires/" and restarted the voxl-tflite-server, it began to work! Thanks, @Matt-Turi, for helping me resolve this issue!
  • Jonathan JeffJ

    VIO FLİGHT

    10
    0 Votes
    10 Posts
    2k Views
    Cliff WongC
    Jonathan, if you have a log(ulog) that exhibits the pause would be great, as it'll show which module is causing the issue. Since you mention local_position, there could be multiple possibilities, especially if you're fusioning GPS and vio data. Based on one's setup, the local position NED calculation may use other sensors and not just vio. To briefly check if vio is the source of the problem, you can look at Odometry topic (directly coupled to voxl vio). If vio has an issue, you'll see the pause, it goto zero or freeze. If not, it's likely a PX4 tuning issue. Nonetheless the ulog will explain what is happening.
  • J

    docker fills up /data, prevents code from running

    11
    0 Votes
    11 Posts
    2k Views
    J
    Good to know -- thanks, Eric!
  • A

    Unable to unbrick ModalAI Voxl m500

    7
    0 Votes
    7 Posts
    1k Views
    A
    @Chad-Sweet I think we are all commenting on the wrong post here. The issue of this post was solved by connecting to the appropriate usb cable. However, @Roman-Rempel I guess you are having similar problem as in this post https://forum.modalai.com/topic/520/voxl-stuck-in-waiting-after-unbricking/3 ?
  • A

    Failed to start voxl-streamer

    4
    0 Votes
    4 Posts
    805 Views
    A
    Thanks for th quick reply. Highly appreciate it.
  • kasarrowtecK

    RTK (without Qgroundcontrol)

    6
    0 Votes
    6 Posts
    1k Views
    kasarrowtecK
    Thanks a lot Eric this definitely helps, will keep updated on progress.
  • J

    TOF Sensor placement affects Tracking Camera/qvio

    2
    0 Votes
    2 Posts
    528 Views
    ModeratorM
    The flashing from the TOF sensor is normal and should not effect VIO. See the documentation troubleshooting VIO, that should help with debugging https://docs.modalai.com/flying-with-vio/#troubleshooting-vio
  • wilkinsafW

    Hi-Res camera disconnect

    6
    0 Votes
    6 Posts
    682 Views
    wilkinsafW
    That is great to hear. Thanks @Alex-Gardner! I will update. I assumed I was on the latest as I had seen I was on factory bundle 1.0.1 and saw on this page: https://docs.modalai.com/downloads/ That the latest factory bundle was 1.0.1. [image: 1635187077739-32eb6578-ebff-4d43-b1ae-d2dc43d70f7e-image.png] Should I be paying attention to the system-image: ModalAI 3.2.0 When checking whether the system needs an update?
  • R

    ubuntu docker on voxl

    2
    0 Votes
    2 Posts
    424 Views
    Eric KatzfeyE
    @relevinsky Docker has some pretty good documentation. Have you looked at: https://docs.docker.com/engine/reference/run/#network-settings?
  • Daniel RyuD

    How to fly autonomously no gps

    2
    0 Votes
    2 Posts
    487 Views
    Chad SweetC
    Have you followed the tutorial at https://docs.modalai.com/mavros ?
  • Jonathan JeffJ

    VOXL GLOBAL SHUTTER CAMERA

    2
    0 Votes
    2 Posts
    551 Views
    modaltbM
    Hi @Jonathan-Jeff , Theoretically yes but there are limitations. Here's some information that might help in showing some possible options: https://docs.modalai.com/image-sensors/
  • kasarrowtecK

    Multi Stage Docker Builds

    3
    0 Votes
    3 Posts
    797 Views
    modaltbM
    I didn't know Docker had this feature, so thanks for that tip! Docker built on VOXL is running at version 1.9.0 and from some articles I read it looks like multistage build started in 17.06 (https://docs.docker.com/engine/release-notes/prior-releases/) So I don't believe this is supported.
  • A

    Flight Core part of VOXL Flight stopped responding

    4
    0 Votes
    4 Posts
    579 Views
    A
    Thank You for Your responses. Unfortunately Mission Planner doesn't see the device. I also tried via nuttx-shell, but voxl doesn't get any response from stm32, so it's probably a problem with the hardware.
  • wilkinsafW

    Ulog on Voxl Flight

    5
    0 Votes
    5 Posts
    585 Views
    modaltbM
    No problem at all, I'll get our docs updated so it's more clear, definitely not a rookie mistake, we should call it out!
  • Jonathan JeffJ

    This topic is deleted!

    1
    0 Votes
    1 Posts
    14 Views
    No one has replied