@KnightHawk06 , please upgrade your VOXL2 SDK, as you have very old release, you can get the latest SDK 1.4.0 and then configure your cameras.

https://docs.modalai.com/sdk-1.4-release-notes/

After installing latest SDK and configuring cameras, confirm via ADB shell that camera server is getting camera data:

#this test app will subscribe to all camera streams and report stream resolution, fps, etc #please note that this test can put unnecessary stress on the system because it will stream ALL the possible camera streams, so normally you would not run this test all the time voxl-inspect-cam -a

after that, if you want to view the camera stream using voxl-portal but you do not have internet connection, you can do that using adb port forwarding trick : https://docs.modalai.com/voxl-portal-via-adb/

Let us know if you have any other questions.

Alex

Hi @jcai ,

I am not sure about this one.. If a higher kernel version is required and the existing driver does not actually work, then maybe it is not a big surprise! 🙂

the kernel module is in the build, as specified in the config file here : https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/blob/qrb5165-ubun1.0-14.1a/arch/arm64/configs/vendor/kona-perf_defconfig#L328

Some info about the driver : https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/blob/qrb5165-ubun1.0-14.1a/arch/arm64/boot/dts/vendor/bindings/net/microchip,lan78xx.txt

You could try to pull source code from updated driver for this device from a newer kernel, drop it into the voxl2 kernel build and build the kernel with new driver. I think some users on this forum were able to do something similar with another device (not ethernet adapter).

Maybe try another ethernet adapter? 🙂

For example,

voxl2-mini:/$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 10000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=ax88179_178a, 5000M voxl2-mini:/$ ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full ... Speed: 1000Mb/s Duplex: Full ... voxl2-mini:/$ iperf -c <my desktop machine ip> ------------------------------------------------------------ Client connecting to <my desktop machine ip>, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local <my voxl2 local ip> port 52708 connected with <my desktop machine ip> port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 339 MBytes 284 Mbits/sec

Did not quite get 1 gig (about 300Mbit/s), maybe there is a bottleneck somewhere, but maybe that will work for you..

Alex

yes, that's the correct rotation matrix for a tag on the ground.

For a tag on the wall with a center 1m off the ground you can use:
"T_tag_wrt_fixed": [0, 0, -1],
"R_tag_to_fixed": [[0, 0, 1], [1, 0, 0], [0, 1, 0]]

The second video of this docs page walks you through the voxl-vision-hub command line args to help you debug relocalization.

@JP-Drone ,

Please try to upgrade to latest voxl-portal version from here : http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64//

I just tested on iphone displaying individual and multi view, it works. What camera feed are you selecting (name)?

The non "encoded" feeds are compressed to mjpeg format which should play on majority of browsers.

I will check regarding the video recording feature in voxl-portal.

Alex

@bendraper We use Google Fi data SIMs for all of our testing

@kham https://www.modalai.com/products/m10000045?_pos=1&_sid=0d63c4c00&_ss=r

@Darshit-Desai , In short,

the VOXL2 system image contains the main Linux OS that is built from open source components and it also contains open-source and closed-source components that are specific to Qualcomm hardware. Building the system image uses bitbake and a very long manifest which has a list of SW components, their exact version and source, as well as order in which the components should be built). you cannot use dd to back up and restore system partitions, as you may be able to do on a Raspberry Pi. Fastboot is the tool that is used to properly install the system partitions. voxl-suite is a collection of software that is installed on top of the base OS on VOXL2. For each SDK version, we also have a manifest of each component and version that should go into the SDK.

Can you clarify which deb files you mean in its always annoying to install the deb files one by one and revving up the versions -- are you updating SDK or installing your some other deb files?

It sounds like you may have per vehicle configuration (every set up is slightly different). You can differentiate the VOXL2 boards using the SoC serial number (cat /sys/devices/soc0/serial_number) and do your custom install based on the serial number. Basically you would have your own "manifest" of some type that may have common parts but also describe different settings for different boards (IP address, etc). You can maintain different bash files for each board and install them based on the serial number.

Alex

Are the failed batteries the white 3000mah Gaoneng packs or the black 4000mah Upgrade Energy Packs?

@Kessie Not exactly, but the important data to retain lives in /data/ or /data/modalai

The SDK flash will attempt to retain this partition, but in certain cases it requires a wipe.

I would take note of /data/modalai/sku.txt

as well as pull off any calibration files in /data/modalai, you can see if you have any onboard currently by running voxl-check-calibration

If you have this data saved you'll have no issue getting back to your previous state, I can help guide you through it if you run into any issues.

Hi @FIREBIRD
Our standard power module is the same for VOXL 2 and VOXL 2 Mini. We just change the voltage settings.
Here is the link and the best we have is a PCB step file for this design (board only, no cables):
https://docs.modalai.com/power-module-v3-datasheet/
097f087f-5854-4015-9c3d-391d5a13cb73-image.png
Hope this helps!
Thanks!

@jedeloya Can tolerate wind gusts of 15 m/s

https://docs.modalai.com/starling-2-max-datasheet/

@JoeAR_21 to correct VIO drift, voxl-vision-hub can correct using an AprilTag without any ROS involvement. If you just need to send the data to ROS for another purpose, you should extend voxl-mpa-to-ros to support tag detections

Source: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros/-/tree/master/catkin_ws/src/src/interfaces?ref_type=heads

We love incorporating merge requests if you do end up with something useful!

@nshahrestani , at this time we do not have another version of the CAD model to share - can you please try to use another tool to convert it for your needs?

Alex

@Gary-Holmgren Figured it out, I hope this helps others with a similar setup.

I didn't notice before but in the usr/bin/voxl-px4-start script there is a comment:

# qshell vl53l1x start -X -b 4

Which you can make or replace to change the DISTANCE_SENSOR condition to:

if [ "$DISTANCE_SENSOR" == "VL53L1X" ]; then # Make sure to set the parameter SENS_EN_VL53L1X to 1 qshell vl53l1x start -X -b 4 # qshell lightware_laser_serial start -d 7

Then you can change the voxl-px4-conf to:

DISTANCE_SENSOR=VL53L1X

After setting the relevant distance sensor / EKF2 params in QGC you should be able to restart voxl-px4 and the distance sensor will appear!

@Pete Starling 2 Max is probably easier to configure for this. You could mount the Doodle radio on the bottom. The M0151 is a good expansion board for this.

Hi @Peter-Milani
Yes, M0173 requires both J6 and J7 to operate as designed.
The uCoax connectors are from Hirose as documented here: https://docs.modalai.com/micro-coax-user-guide/

@Peter-Milani Hi Peter, it's not possible for us to answer comprehensively about NDAA compliance. We can answer country of origin questions though.

Our M0107, M0161, M0166 for instance are built by ModalAI in the USA
M0149 is built by a partner in Taiwan

@Samuel-Lehman If this is a UVC camera you may be able to use voxl-uvc-server in order to create an MPA pipe and have tflite server read from that pipe

It may take some slight tweaking to get voxl-uvc-server to support your specific camera

Hi @Gary-Holmgren. This is likely because you're running the build script from an x86 system (docker requires that you build on the same architecture as the base image, in this case arm64). You can solve that by cloning the repo onto the voxl and running build.sh from there.

Note: make sure your voxl has a wifi connection before running ./build.sh.