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

Starling & Starling 2

Questions regarding the Sentinel VOXL 2 Development Drone

74
Topics

340
Posts

S

@Moderator Hi thank you for the link, may I check if the original 4921 green propellers are not supported anymore? And instead the DJI 4726 are the recommended replacement propellers? Also, would an ESC recalibration be necessary after the switch? Thanks.
Sentinel

Questions regarding the Sentinel VOXL 2 Development Drone

77
Topics

516
Posts

A

@AndriiHlyvko , Thank you! I will ask @Eric-Katzfey to review at his convenience.
VOXL m500 Reference Drone

104
Topics

562
Posts

S

Hello,

I’ve recently started working with the Modal AI M500 drone and am encountering issues while trying to build Docker images on the drone. Specifically, I am having trouble with both the Mavsdk and Mavsdk-Python images.

Issue 1: Pulling Docker Image
When attempting to pull the Python Docker image (modalai-public/voxl-mavsdk-python), I receive the following error:

Error: Status 405 trying to pull repository modalai-public/voxl-mavsdk-python: "v1 Registry API is disabled. If you are not explicitly using the v1 Registry API, it is possible your v2 image could not be found. Verify that your image is available, or retry with dockerd --disable-legacy-registry. See https://cloud.google.com/container-registry/docs/support/deprecation-notices"
Issue 2: Building Docker Image on Drone
I also tried building the Docker image directly on my computer while connected to the drone via ADB, but encountered this error:

Image: voxl-mavsdk-python:v1.1
Waiting for device...
Checking for docker support...
-> Docker support not detected, running docker support on target...
/bin/sh: voxl-configure-docker-support.sh: not found
Building image: voxl-mavsdk-python:v1.1
Dockerfile: 1 file pushed. 0.3 MB/s (802 bytes in 0.002s)
takeoff_and_land2.py: 1 file pushed. 0.4 MB/s (941 bytes in 0.002s)
offboard_position_ned2.py: 1 file pushed. 0.8 MB/s (2227 bytes in 0.003s)
start-mavsdk-server.sh: 1 file pushed. 0.0 MB/s (109 bytes in 0.007s)
Sending build context to Docker daemon 8.192 kB
Step 1 : FROM ubuntu:bionic
Pulling repository docker.io/library/ubuntu
Error: Status 410 trying to pull repository library/ubuntu: "<html>\r\n<head><title>410 Gone</title></head>\r\n<body>\r\n<center><h1>410 Gone</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n"
Additional Information
Docker Version: 1.9.0 on the VOXL
Drone Firmware Version: - I just updated it to the newest SDK version 1.2.
Could someone please assist me with these issues? Any guidance or suggestions would be greatly appreciated.

Thank you!
Qualcomm Flight RB5 5G Drone

Discussion regarding Qualcomm Flight RB5 5G Drone

120
Topics

649
Posts

S

@tom Hi Tom! To be honest I was not even aware this tool existed... super handy! So I played with the different EKF2_helpers and while the "Height estimate not stable" error was solved, I have two problems with the outdoor profiles that my application requires:
outdoor_gps_baro.params:
While the heading is correct in this profile, I get the error "local position estimate not valid". I checked that VIO is up and PX4 receives vehicle_odometry data. Therefore I cannot takeoff with this configuration. Additionally I get a warning that "GPS speed accuracy too low".
vio_gps_baro.params:
I can takeoff with position mode but I get the same "GPS speed accuracy too low" warning which does not allow me to trigger any autonomous PX4 functionality, which is crucial for my application. Even with 14 satellite lock, seems strange. Additionally the drone heading remains to be the local heading from the VIO initialization orientation, instead of the correct global heading. Is this intended?

Any ideas on how to solve these problems? I am more interested in the vio_gps_baro.params profile. Could it be a hardware issue with the GPS?

Best,

Milton
Seeker

Questions regarding the Seeker SLAM Development Drone

40
Topics

134
Posts

T

I'm trying to use rviz to view the pointcloud made by the seeker. I'm using these instructions: https://docs.modalai.com/seeker-user-guide-vio/

Upon running roslaunch voxl_mpa_to_ros voxl_mpa_to_ros.launch, I get this output:

... logging to /home/root/.ros/log/7c7e0f0e-1dda-11b2-a220-18473db1c84b/roslaunch-apq8096-21073.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://192.168.8.1:39686/
SUMMARY

PARAMETERS
/rosdistro: indigo /rosversion: 1.11.21
NODES
/
voxl_mpa_to_ros_node (voxl_mpa_to_ros/voxl_mpa_to_ros_node)

auto-starting new master
process[master]: started with pid [21092]
ROS_MASTER_URI=http://192.168.8.1:11311/

setting /run_id to 7c7e0f0e-1dda-11b2-a220-18473db1c84b
process[rosout-1]: started with pid [21105]
started core service [/rosout]
process[voxl_mpa_to_ros_node-2]: started with pid [21112]

MPA to ROS app is now running

Found new interface: qvio_overlay
Found new interface: stereo
Found new interface: tracking
Found new interface: imu0
Found new interface: imu1
Found new interface: voa_pc_out
Found new interface: qvio

No tof topic is produced by the node when running. What am I missing? Thanks in advance!

S

Are there any URDF for the dev drones>?

• • skl1g14

4

0
Votes

4
Posts

441
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

36
Views

No one has replied
Z

SWARM Drone Formation with Starling Drones

• • Zarrar

4

0
Votes

4
Posts

72
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

60
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

4

0
Votes

4
Posts

45
Views

T

@tom There is also another anomaly: voxl-inspect-battery shows voltage and current, but charge is listed as 0%. Is there some service that needs to be restarted/configured, like voxl-px4, in order to get a reading of the battery charge?

I also ran px4-listener battery_status which also doesn't seem right. The cells that came with the Starling MAX I believe are 7.2V (two 2s in series, so 4 cells total).
voxl2:/$ px4-listener battery_status TOPIC: battery_status battery_status timestamp: 1051478873 (0.067609 seconds ago) voltage_v: 5.76600 voltage_filtered_v: 5.76056 current_a: 1.00800 current_filtered_a: 0.96054 current_average_a: 3.40000 discharged_mah: 299.21326 remaining: 0.00000 scale: 1.30000 time_remaining_s: 0.00000 temperature: nan voltage_cell_v: [0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000] max_cell_voltage_delta: 0.00000 custom_faults: 0 average_power: 0.00000 available_energy: 0.00000 full_charge_capacity_wh: 0.00000 remaining_capacity_wh: 0.00000 design_capacity: 0.00000 nominal_voltage: 0.00000 capacity: 3950 cycle_count: 0 average_time_to_empty: 0 serial_number: 0 manufacture_date: 0 state_of_health: 0 max_error: 0 interface_error: 0 faults: 0 average_time_to_full: 0 over_discharge_count: 0 connected: True cell_count: 4 source: 0 priority: 0 id: 1 is_powering_off: False is_required: False warning: 3 mode: 0
Do I need to change the POWER_MANAGER in /etc/modalai/voxl-px4.conf from VOXLPM to NONE and restar the voxl-px4 service? The comments seem to indicate that we should be using NONE with the Mini-ESC 4 in1:
# POWER_MANAGER: # Tell PX4 which power manager to use. # Use NONE for ModalAI Mini-ESC since the ESC driver handles PM. # Use EXTERNAL when not using the ModalAI APM power manager to power the board # This also just disables the voxlpm driver, same as the NONE option # Options include: [VOXLPM, EXTERNAL, NONE]

1 / 1