Hello Modal AI team,
The error I get went flashing a new SDK
error: insufficient permissions for device: user in plugdev group; are your udev rules wrong?
See [http://developer.android.com/tools/device.html] for more information
When I run adb devices:
List of devices attached
a0d316ec no permissions (user in plugdev group; are your udev rules wrong?); see [http://developer.android.com/tools/device.html]
Do you know what I should do?
@Alex-Kushleyev Hi Alex, would these commands work with the M0134 Variant as well?
@Eric-Katzfey when using the voxl-send-esc-pwm-cmd do you know how I would be able to trigger the VREF Pin on the ESC 4-in-1?
I have tried running:
sudo voxl-send-esc-pwm-cmd -p 12 -w 2201
sudo voxl-send-esc-pwm-cmd -p 11 -w 2000
and when I measure the voltage from that wire I get ~0.01V which I presume to be noise.
Is there something that I am missing?
I am looking to produce a 5V Rail.
I am trying to run voxl-vision-hub and that requires voxl-qvio-server to be running. However, when I start it, it says one of its internal libraries (libvoxl_common_config.so) cannot be run since it is a 64-bit library. Then, I realized that the voxl-qvio-server package I have is 32-bit while all the other packages are 64-bit. I tried to reinstall voxl-qvio-server from the newest VOXL2 SDK Platform release, but that one is still 32-bit even though the DEB file is labeled arm64. Does anyone know how to solve this issue?
@Eric-Katzfey I figured out that I did not need it for my project, Thank you thought!
@Eric-Katzfey Thank you I got this helped a lot! I was able to get it working with root access!
Did you try running
voxl-configure-rangefinders?
Yes I have, and these are the outputs:
voxl2:/$ voxl-configure-rangefinders
missing required argument
Start wizard with prompts:
voxl-configure-rangefinders
Shortcut configuration arguments for scripted setup.
factory_enable will reset the config file to factory defaults
before enabling the service.
voxl-configure-rangefinders disable
voxl-configure-rangefinders 1_on_m0141
voxl-configure-rangefinders 1_downward_on_m0141
voxl-configure-rangefinders 4_on_m0141
voxl-configure-rangefinders 1_downward_on_m0173
voxl-configure-rangefinders enable
1_downward_on_m0141 is for a downward sensor, this enables mavlink
broadcast to the autopilot as a landing sensor
show this help message:
voxl-configure-rangefinders help
is there a certain option I should select?
Hello Modal AI team,
I am trying to enable and run voxl-io-server. I was successfully able to enable it but when starting the system, it would not run. I ran into this error when I asked for its status
voxl2:/$ systemctl status voxl-io-server
● voxl-io-server.service - voxl-io-server
Loaded: loaded (/usr/bin/voxl-io-server; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2025-07-14 14:19:26 UTC; 25ms ago
Process: 2571 ExecStart=/usr/bin/voxl-io-server (code=exited, status=255)
Main PID: 2571 (code=exited, status=255)
Jul 14 14:19:26 m0054 systemd[1]: Started voxl-io-server.
Jul 14 14:19:26 m0054 voxl-io-server[2571]: no config file found, please run voxl-configure-rangefinders
Jul 14 14:19:26 m0054 systemd[1]: voxl-io-server.service: Main process exited, code=exited, status=255/n/a
Jul 14 14:19:26 m0054 systemd[1]: voxl-io-server.service: Failed with result 'exit-code'.
@Eric-Katzfey How can I control those PWM signals? Since at the moment I am not reading anything from any of the pins.
@Eric-Katzfey Correct me if I am wrong, but doesn't the ESC only have enough motor outputs for each of the propellers? So to add another PWM signal I need to either use a GPIO pin or the expansion voxl2 IO board
@Eric-Katzfey I’m trying to control the gripper using a Python script running in a Docker container on Linux. My plan is to use pymavlink to listen for remote controller commands, like a specific channel input, and then trigger the gripper based on that input. So I think it's not integrated directly as a PX4 driver; it’s more of a companion application running alongside PX4 that reacts to MAVLink messages in real time.
@tonygurney I am also using a ghost atto as my receiver
@Eric-Katzfey I am looking to attach a gripper to the drone
Hello ModalAI Team,
I was wondering if you have a specific guide or documentation on how to install the VOXL IO on the Sentinel drone. I’ve run into a couple of issues regarding available QUP ports:
The QUP2 port (J18) is currently occupied by the ESC.
The QUP7 (J16) port has its RX line already in use by the receiver for my remote controller. Pin 11 is already being used.
Given this setup, am I expected to remove the ESC and rewire the motors to the VOXL IO? Or is there an alternate recommended configuration for integrating the VOXL IO on the Sentinel platform?
Any guidance or examples you could provide would be greatly appreciated.
Hello ModalAI Team,
I’m currently trying to test the output of GPIO pin 46 on the VOXL and haven’t seen any voltage change using a multimeter.
Here’s what I’ve tried so far:
echo 1 > /sys/class/gpio/gpio1146/value
echo 0 > /sys/class/gpio/gpio1146/value
I also tried using the VOXL utility commands:
voxl-gpio -w 46 1 and voxl-gpio -w 46 0
I have also check that the pin was set output
In all cases, there was no measurable voltage change observed on my multimeter.
Is there something I may be missing in the configuration, or is there an initialization step required for GPIO 46?
Thank you for your help!
Re: GPIO numbering
In this example @Viswanadh-Chegu is able to find the offset for for J8 pin 12 but how would you do that for all the other connectors that might have gpio pins?
I am specifically looking for J10 pin 6 but nonetheless I would like to learn the methodology