Posts made by Daniel Ryu

@Mastermind USB0 is the interface the VOXL2 + newer Microhard add-on boards use for communication, so eth0 may not show up if you're used to using that from VOXL1

Hello,

I'm trying to communicate via Serial communication on port J19 on the VOXL2. Currently I can open a port on the corresponding interface (/dev/ttyACM0) but I cannot read or write any data. This is how I currently wired my serial device to this port, do you have any recommendations or insight on I can open serial communication on this port?

I do not have any GPS or magnetometer connected to the drone at those ports.

The table contains the pins of the device I am connecting the J19 port, and the lines are the left are what pins on the J19 port I am connecting them to.
I also tried swapping the wire at pin 8 to pin 3, and pin 7 to pin 2 of the J19 port to try and take advantage of the GPS's communication lines, but this didn't work either.

Relevant link: https://docs.modalai.com/voxl2-connectors/#j19---external-sensors-2x-uart-2x-i2c

@Chad-Sweet Any update on this, as it has been about five months since then?

@Alex-Kushleyev What power supply do you use for calibrating the ESCs? We want to calibrate ours for a 4S Li-Ion battery for these motors, and are unsure of what power supply we should get.
Motor specs:

• Motor Dimension:Φ24.7mm x 13.2mm
• KV2600
  https://gitlab.com/voxl-public/flight-core-px4/voxl-esc/-/blob/master/tools/calibration.md

General QOL update: I automated a script using cron to ifconfig usb0 down and change the eth0 ip address to what I wanted using ifconfig eth0 <ip>. This only works if the script is run using sudo

@Alex-Kushleyev We want to both adjust the parameters for the ESCs, and also calibrate the ESCs feed-forward curve. Would that be these tools? https://gitlab.com/voxl-public/flight-core-px4/voxl-esc/-/blob/master/tools/calibration.md https://docs.modalai.com/modal-esc-px4-user-guide/#px4-params

@Alex-Kushleyev Is this the documentation for it? https://docs.modalai.com/modal-esc-px4-user-guide/. Or is it this documentation: https://docs.modalai.com/voxl2-esc-configs/

@Chad-Sweet Got it, thanks!

Hello,

I have a VOXL2 drone with ESCs inside, and the only guides I could find on calibrating ESCs were either for voxl1 or with exposed ESCs. Is there a way I can calibrate the ESCs from QGC on my voxl2 drone without having to take it apart to access the ESCs physically?

@Chad-Sweet I think that would work. Do you know if the same type of Microhard add-on would have exhibit the same symptoms with a VOXL1?

Hello,

I am flashing some newly purchased VOXL2 development kits when I ran into this issue when using a microhard. When voxl-configure-modem is run, it creates two interfaces that connect to the microhard: eth0 and usb0. The IPs that are set on both interfaces are random, and are not consistent between reboots of the voxl2 board. Additionally, when both are active, any connections to QGC from the board through the microhard is greatly slowed down. I would like to permanently set the ip address of one of the interfaces to be something that I can control, like how voxl-configure-modem used to do, as well as permanently delete the other interface since it is not required.

Things I have tried:
Editing /etc/network/interfaces and removing an interface. This does not prevent both interfaces from reappearing upon reboot

ifconfig eth0 down. eth0 sets itself back to "up" automatically within a few minutes, even without reboot.
ifconfig usb0 down. usb0 stays down when this command is run, but returns as up again upon the voxl2 board's reboot
ip addr del dev eth0. It returns the error:
sudo iw dev eth0 del. It returns the error

Here is what VOXL2 Version I'm running:

I did already try running apt-get update && apt-get upgrade

@Alex-Gardner Perfect, thanks!

Hi quick clarification question,

Is docker autorun supported on VOXL2? The service I saw is on the VOXL2's latest firmware, but the script itself (/etc/modalai/docker-autorun.sh) does not appear to exist. Wanting to confirm before I test anything, as we've had the VOXL2 be bricked before when testing VOXL1 capabilities on VOXl2.

https://docs.modalai.com/docker-on-voxl/#configuring-a-program-to-run-automatically-inside-a-docker-on-boot

@tom Any follow-up things I can try to troubleshoot this?

@Chad-Sweet got it, thanks

@Chad-Sweet Since this appears to be a hardware issue with the static discharge, would it be fixable?

Re: VOXL2 ADB not working

I am having a similar issue to this post, but instead of a Sentinel, its with the standalone voxl2 board. We can boot the board into fastboot and connect, but we cannot do any adb connections. When trying to reflash the board, we have the same message of "Waiting for adb" that never completes. The board has only power and the usbc connected to it, no cameras or anything else attached.

We previously were able to connect over adb, reflash, and access files on the board. I found an adjacent post that resembles what's occurring wtih the voxl2: https://android.stackexchange.com/questions/82059/adb-not-working-but-fastboot-is

Is it possible that this issue came from a static discharge on the board? When moving the board from one person to me while it was not powered, I felt a static pop when accepting the board. Could this be the cause of adb suddenly no longer working?

An additional note I forgot to mention: I also need to run "ifconfig usb0 down" but I only need to do that once, whereas I need to run "ifconfig eth0 down" every 5-10 seconds to regain internet connection over station mode

@tom I do not. If I do run voxl-configure-modem and reboot, I still have the same issue with eth0