Ask your questions right here!

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Subcategories

Support Request Format for Best Results

155
Topics

710
Posts

A

@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
Feature Requests

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

26
Topics

89
Posts

A

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
3D Models

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

33
Topics

86
Posts

A

@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

376bf0dd-494a-4bf1-8d92-1b2d91afb83d-image.png

P

hires Camera for barcode

• • Prasobh P

2

0
Votes

2
Posts

360
Views

C

Have you looked at voxl-tag-detector?
T

Unstable Seeker after flashing

• • tomipi

6

0
Votes

6
Posts

870
Views

T

Thanks Chad. We did the calibration again with a better calibration target, and this fixed the problem.
A

How to: Seeker ESC calibration

• • alarm_hq

9

0
Votes

9
Posts

1358
Views

J

@alarm_hq said in How to: Seeker ESC calibration:

And if I've already made the "mistake" of reflashing px4 firmware, is the closed loop RPM control affected?

The ModalAI ESCs used on Seeker have their own firmware and settings stored on the ESC itself, independent from PX4 so your ESC is fine after changing PX4 firmware.
A

Seeker replacement props

• • alarm_hq

2

0
Votes

2
Posts

422
Views

?

Hey @alarm_hq! The props for the Seeker development drone can be found here.
M

Unable to run example TFlite model in emulator docker image

• • Michael Barrow

3

0
Votes

3
Posts

434
Views

M

Thanks, so what is the emulator for exactly? emulating native compilation? I am unclear of the emulator use case if it is not intended to emulate the voxl platform for application testing. Let me know, cheers!
M

This topic is deleted!

• • modaltb

2

0
Votes

2
Posts

3
Views
A

Voxl-mapper instructions

• • alarm_hq

2

0
Votes

2
Posts

490
Views

?

Hello @alarm_hq!
Please see the updated readme on voxl-mapper's dev branch for an overview guide of this package. As for the timestamp too new error, this error typically arises when there is a VIO blowup, and one way to prevent this is by ensuring that the tracking camera is correctly calibrated pre-flight. Also, please see the overview guide for instructions on viewing, as RVIZ is no longer utilized!
J

Change Pwm channel

• • John Mccarty

8

0
Votes

8
Posts

1304
Views

M

Alright! Thanks for the update, I'll likely use this post to get some updates to our docs, appreciate it!
D

Invalid local position

• • DillonAllen

30

0
Votes

30
Posts

9180
Views

A

I found the QGC
EKF2_AID_MASK parameter settings above (configuring to 280: Vision position fusion, vision yaw fusion, vision velocity fusion) to allow the seeker to enter position and off-board modes.

Prior to configuring, QGC was receiving VIO but was still unable to enter position mode as referenced here

To make the forum search engine happy: seeker position mode rejected
R

Setting up network interfaces

• • ryan_meagher

7

1
Votes

7
Posts

1858
Views

E

@Nirge You should use voxl-wifi for wlan0.
S

New image not installing waiting for fastboot

• • Shlok Agarwal

2

0
Votes

2
Posts

277
Views

T

@Shlok-Agarwal I assume you've taken a look at this page in our docs: https://docs.modalai.com/unbrick-voxl/

If not, give that a read through and it'll give you a bunch of good info.

Were you able to ADB into the VOXL before you started the flashing process?
J

TOF Sensor Range

• • jaredjohansen

1

0
Votes

1
Posts

438
Views

No one has replied
G

Hires Camera

• • gauravshukla914

1

0
Votes

1
Posts

407
Views

No one has replied
R

VOXL FLIGHT with Arducopter (Ardupilot)

• • relevinsky

3

0
Votes

3
Posts

436
Views

R

Thank you.
O

[Suggestion] Add fastboot device udev rule to "Setup ADB" tutorial

• • omer b

2

1
Votes

2
Posts

443
Views

M

@omer-b thanks!! Added:
5dc619fb-ca85-4b54-9d6a-e6e9c4567512-image.png
W

VOXL rebooting PX4

• • wilkinsaf

2

0
Votes

2
Posts

547
Views

W

It appears this happens when the sensors are not calibrated on the drone. voxl-vision-px4 picks up on sensor inconsistency and restarts PX4.

So, calibrated the sensors. Looks better

resolved
N

This topic is deleted!

• • NealMcFee-ms

1

0
Votes

1
Posts

7
Views

No one has replied
B

VOXL Deck Spacer Size

• • blakekrpec

3

0
Votes

3
Posts

422
Views

L

are you sure that this is the Vibration damper that you are using? cause your 3D cad model calls for a damper with different dimensions:
b6107c8a-e568-4839-99d0-4387f6c68533-image.png

please advise which damper are you using in your Voxl flight deck.
L

Which Vibration dampers are you using with the Voxl flight?

• • LANDY

2

0
Votes

2
Posts

378
Views

C

These are the dampeners we are using on VOXL Flight

The dampening may needed to be tuned for your flight platform though, and can definitely be different depending on flight dynamics. We have had a lot of success sticking a piece of foam between the plate and the frame.

https://www.amazon.com/gp/product/B073LPTHCL/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
S

setting up voxl-portal

• • Steve Arias

2

0
Votes

2
Posts

553
Views

?

@Steve-Arias,

Once you have voxl-portal started either via the command line or as a service, you can access the webserver on a device within the same network just by navigating to your voxl's IP address.

14 / 105

This topic is deleted!

This topic is deleted!