VOXL Dev Drones

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

PX4 Autonomy Developer Kit

Product related questions and answers

20
Topics

118
Posts

F

Since this model doesn't have a TOF sensor, what is the alternative to using voxl-mapper for autonomous flight?
Starling & Starling 2

Questions regarding the Sentinel VOXL 2 Development Drone

141
Topics

673
Posts

H

@Alex-Kushleyev : here is the output:
[ 206.798954] RTW: wlan0- hw port(0) mac_addr =00:c0:ca:b3:a6:e5 [ 206.801089] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00 [ 206.801105] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00 [ 215.356522] CAM_INFO: CAM-CRM: cam_req_mgr_process_flush_req: 2177 Last request id to flush is 5890 [ 215.356586] CAM_INFO: CAM-ISP: __cam_isp_ctx_flush_req_in_top_state: 3046 Last request id to flush is 5890 [ 215.356694] CAM_INFO: CAM-ISP: __cam_isp_ctx_flush_req_in_top_state: 3069 Stop HW complete. Reset HW next. [ 215.367444] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1117 CAM_STOP_DEV Success, sensor_id:0x356,sensor_slave_addr:0x30 [ 215.367450] CAM_INFO: CAM-CSIPHY: cam_csiphy_core_cfg: 982 STOP_DEV: CSIPHY_IDX: 0, Device_slot: 0, Datarate: 592000000, Settletime: 2800000000 [ 215.367473] CAM_INFO: CAM-ISP: cam_ife_mgr_release_hw: 4755 Release HW success ctx id: 2 [ 215.368902] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.79 [ 215.372057] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60 [ 215.372072] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.56 [ 215.372085] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58 [ 215.372128] CAM_INFO: CAM: cam_res_mgr_shared_pinctrl_put: 270 Need hold put this pinctrl [ 215.372143] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1047 CAM_RELEASE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x30 [ 216.395442] msm_vidc: err : 00000002: h264e: msm_comm_flush: Already in flush [ 216.508604] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1117 CAM_STOP_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34 [ 216.508616] CAM_INFO: CAM-CSIPHY: cam_csiphy_core_cfg: 982 STOP_DEV: CSIPHY_IDX: 1, Device_slot: 0, Datarate: 1500000000, Settletime: 2200000000 [ 216.515038] CAM_INFO: CAM-ISP: cam_ife_mgr_release_hw: 4755 Release HW success ctx id: 0 [ 216.515922] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79 [ 216.517960] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56 [ 216.517973] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60 [ 216.517986] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58 [ 216.518049] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1047 CAM_RELEASE_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34 [ 216.618202] CAM_INFO: CAM-CRM: cam_req_mgr_process_flush_req: 2177 Last request id to flush is 5927 [ 216.618268] CAM_INFO: CAM-ISP: __cam_isp_ctx_flush_req_in_top_state: 3046 Last request id to flush is 5927 [ 216.618374] CAM_INFO: CAM-ISP: __cam_isp_ctx_flush_req_in_top_state: 3069 Stop HW complete. Reset HW next. [ 216.621881] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1117 CAM_STOP_DEV Success, sensor_id:0x356,sensor_slave_addr:0x30 [ 216.621891] CAM_INFO: CAM-CSIPHY: cam_csiphy_core_cfg: 982 STOP_DEV: CSIPHY_IDX: 2, Device_slot: 0, Datarate: 592000000, Settletime: 2800000000 [ 216.628363] CAM_INFO: CAM-ISP: cam_ife_mgr_release_hw: 4755 Release HW success ctx id: 3 [ 216.629040] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79 [ 216.633125] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60 [ 216.633166] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.56 [ 216.633212] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59 [ 216.633667] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1047 CAM_RELEASE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x30 [ 216.687846] CAM_INFO: CAM-CRM: cam_req_mgr_process_flush_req: 2177 Last request id to flush is 5930 [ 216.687904] CAM_INFO: CAM-ISP: __cam_isp_ctx_flush_req_in_top_state: 3046 Last request id to flush is 5930 [ 216.687998] CAM_INFO: CAM-ISP: __cam_isp_ctx_flush_req_in_top_state: 3069 Stop HW complete. Reset HW next. [ 216.692371] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1117 CAM_STOP_DEV Success, sensor_id:0x356,sensor_slave_addr:0x30 [ 216.692383] CAM_INFO: CAM-CSIPHY: cam_csiphy_core_cfg: 982 STOP_DEV: CSIPHY_IDX: 0, Device_slot: 1, Datarate: 592000000, Settletime: 2800000000 [ 216.698841] CAM_INFO: CAM-ISP: cam_ife_mgr_release_hw: 4755 Release HW success ctx id: 1 [ 216.699769] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.79 [ 216.703840] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.60 [ 216.703886] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.56 [ 216.703919] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.58 [ 216.705006] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1047 CAM_RELEASE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x30 [ 216.712597] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30080 [ 216.721134] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died [ 216.761711] msm_vidc: high: 00000002: h264e: Closed video instance: ffffffeefdebe000 [ 216.761933] msm_vidc: high: 00000001: h264e: Closed video instance: ffffffef0e100000 [ 216.884653] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry [ 216.895769] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000] [ 216.906058] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully [ 216.906072] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM [ 216.906084] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM [ 216.929300] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58 [ 216.931458] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.56 [ 216.933569] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60 [ 216.933607] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79 [ 216.956534] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:0,slave_addr:0x30,sensor_id:0x356 [ 216.956636] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.79 [ 216.960823] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60 [ 216.960951] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.56 [ 216.961062] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58 [ 216.986327] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58 [ 216.986474] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60 [ 216.986534] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56 [ 216.986670] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79 [ 217.000967] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:1,slave_addr:0x34,sensor_id:0x577 [ 217.001068] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79 [ 217.003181] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56 [ 217.003308] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60 [ 217.003456] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58 [ 217.029376] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59 [ 217.031600] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.56 [ 217.033826] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60 [ 217.033928] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79 [ 217.057861] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:2,slave_addr:0x30,sensor_id:0x356 [ 217.058009] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79 [ 217.062570] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60 [ 217.062700] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.56 [ 217.062812] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59 [ 217.085707] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60 [ 217.087825] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59 [ 217.089993] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55 [ 217.092187] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79 [ 217.695551] RTW: wlan0- hw port(0) mac_addr =00:c0:ca:b3:a6:e5 [ 218.274338] msm_vidc: err : ffffffff: .....: DBLP Set: status 0 [ 218.624174] CAM_ERR: CAM-CCI: cam_cci_read: 1320 wait_for_completion_timeout rc = -110 FIFO buf_lvl: 0x0 [ 220.128139] CAM_ERR: CAM-CCI: cam_cci_flush_queue: 53 wait timeout [ 220.128236] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-110 [ 220.128248] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -110 [ 220.128262] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x2975: [ 220.130622] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79 [ 220.132521] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55 [ 220.132641] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60 [ 220.132787] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59 [ 220.160433] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.58 [ 220.163839] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.56 [ 220.166217] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.60 [ 220.166422] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.79 [ 220.191299] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:6,slave_addr:0x30,sensor_id:0x356 [ 220.191460] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.79 [ 220.195732] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.60 [ 220.195860] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.56 [ 220.195969] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.58 [ 220.255634] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died [ 229.072542] RTW: wlan0- hw port(0) mac_addr =00:c0:ca:b3:a6:e5
Let me know what else is needed. Thanks, Hector
Sentinel

Questions regarding the Sentinel VOXL 2 Development Drone

88
Topics

557
Posts

J

@Eric-Katzfey Awesome, thanks for the feedback!
VOXL m500 Reference Drone

108
Topics

571
Posts

M

Which Microhard units do you recommend for reliable integration with the VOXL m500 (both for the air unit and the ground unit)?

Could you provide a complete wiring map or diagram showing how to physically connect the Microhard modem to the VOXL board, including power supply details and which ports to use?
This will help us avoid trial-and-error and ensure correct setup.
Do you provide flash files or firmware for the Microhard air and ground units that are configured to work with the m500 out of the box?
If not, can you supply support through what’s needed to configure both units manually?
Do you provide documentation that explains how to access and configure the Microhard units via their IP interfaces?
Specifically, we’re looking for a step-by-step guide (PDF or otherwise) that shows how to:
Enter the Microhard configuration interface (e.g., IP address access) Set communication parameters and network settings Pair the air and ground units to establish a working link
Qualcomm Flight RB5 5G Drone

Discussion regarding Qualcomm Flight RB5 5G Drone

131
Topics

679
Posts

G

@mrawding good afternoon, i see that your topic is quite old, but I am struggling with px4 firmware build and was wondering if you ever managed to successfully build your px4 firmware ? If you have done it recently, I would appreciate a helping hand in this topic: https://forum.modalai.com/topic/4539/voxl2-hitl-sim-with-gazebo-in-docker-vtol-frame-support/13?_=1751379111988
Seeker

Questions regarding the Seeker SLAM Development Drone

41
Topics

141
Posts

A

@Cody , please double check the actual and desired roll / pitch / yaw values in the flight review. When the vehicle is level, then roll and pitch should be close to zero and desired roll/pitch will be zero as well if you don't touch RC sticks.

If the attitude estimate is incorrect (for whatever reason) this can cause the vehicle to not be level during flight / take-off.

Alex

S

Are there any URDF for the dev drones>?

• • skl1g14

4

0
Votes

4
Posts

1131
Views

S

@skl1g14
in case anyone looking for URDF for m500 drone, i have it here
https://github.com/UoSM-CIRG/CAD-Files/tree/master/drone_dev_kit/catkin_ws/src/display_model/description/m500_urdf/urdf
Z

Mesh Network in Wifi FOR SWARM OF DRONES

• • Zarrar

1

0
Votes

1
Posts

181
Views

No one has replied
Z

SWARM Drone Formation with Starling Drones

• • Zarrar

4

0
Votes

4
Posts

375
Views

E

@Zarrar By "doing it on your own" we mean that we have not done the work to enable any of these features. You would need to do that. And since we have not done that work we cannot answer your specific questions on how to do it. But that is the beauty of the Starling drone. It is an open platform for doing exactly this kind of development work. We would love to hear how you are able to use the Starling for SWARM Formation!
Z

Equipment Requirements Hardware

• • Zarrar

4

0
Votes

4
Posts

334
Views

Z

@Eric-Katzfey Dear Moderator, I am a Drones Engnineer fimiliar with Python, C,C++, PX4 and QGC, Kindly tell me which hardware modems and radios are required in order to develop the SWARM Drones formation and Mesh Networking, I am new to Starling Platforms and Need help
T

Starling MAX

• • Thomas Eiszler

6

0
Votes

6
Posts

389
Views

A

@Thomas-Eiszler , As long as you dont actually have the APM connected, having the power manager driver enabled in PX4 will not conflict with the mini ESC also reporting battery_status. This is because even though the APM driver in PX4 will attempt to start, it will fail to find the actual hardware device (via i2c probe) and will exit the driver. However, it is best to disable the power manager (APM) driver.

Starling 2 MAX uses two 2-cell packs in series, so it is a 4-cell pack.

when you run voxl-esc spin test, it should report voltage reported by each ESC. Does that match the actual battery voltage or is it also wrong (as is reported in your battery_status ?

Alex
T

Starling 2 vs Sentinel

• • tauhidcse

11

0
Votes

11
Posts

403
Views

T

@tom Sounds good. Thanks for making me familiar with your platform. I will get a quote soon and purchase one starling 2 max.
M

Urgent Assistance Needed: Voxl2 and portal access issue in my starling 2 modalai drone

• • muhammad kazim 0

3

0
Votes

3
Posts

157
Views

M

@Alex-Kushleyev Thank you for your response, it was the issue with the battery, May be my battery is damaged, when I provide external power source of 12 volt power supply, then it is working perfectly fine. Now I am able to access the portal and voxl2 as well. thank you

1 / 1