Dev Team

Hi Rui,

A few things..

• there have been a few updates in SNAV (mainly to support our new ESC, nothing major). Please use the latest release in https://developer.modalai.com/asset : snav-modalai_1.4.1_8x96.ipk
• in order to run SNAV, you ineed to install imu_app package opkg install imu_app. This may remove some package like voxl-imu-server, since they can't run at the same time. imu_app package provides access to an older version of IMU server, which is used to pass imu data between SNAV and CPU applications (like vio, etc). you can also download the ipk from http://voxl-packages.modalai.com/stable/imu_app_0.0.6.ipk and run opkg install imu_app_0.0.6.ipk
• in order to install the latest snav ipk, you need to modify /etc/opkg/opkg.conf (commend out the line at the bottom src/gz stable http://voxl-packages.modalai.com/stable . If you don't do this, then the package config will override your new ipk with another package modalai-vl and pull it from the package repo. However it so happens that latest SNAV is not a part of modalai-vl package..
• after you install the latest snav ipk, you can change opkg.conf back to normal.
• the rest of SNAV install should work the same as before..
• if you don't want to use latest SNAV, you don't have to, you can just use your existing version and install the imu app and SNAV should work.

Hope this helps.

Alex

There could also be a break in one of the cable lines (they can bend gently but should not be folded to an angle)

It's also possible that your extension cables are plugged in backwards, 90% of that output is reading the config file at /etc/modalai/voxl-camera-server.conf. The critical part is the

----------- Number of cameras: 0

This is the response from the driver when we asked how many cameras it sees, it will often refuse to open any of them if any of the lines are incorrect, could you show a picture of you cable setup?

You have all of the cameras indicated there plugged in (hires, stereo, tracking)?

You can run it with:

systemctl start voxl-camera-server

If it is enabled but not running though that means that it crashed on startup (or you stopped it). If you didn't manually stop it that means it encountered an error which is usually due to a bad camera connector causing the driver to throw an error. If you start it and it still shows up as stopped afterwards could you run it manually with:

voxl-camera-server -d 0

and paste the output here

Is voxl-camera-server running? You can check with

voxl-inspect-services

So now you can run it with any of the configuration options specified in that file such as:

voxl-streamer -c tracking

for tracking or

voxl-streamer -c stereo

for the stereo cameras

Hey @Thomas-MacNamara,

Sorry for the lag, I'm new to the USB gadget, but here's some flags found on VOXL from our standard kernel, from adb shell zcat /proc/config.gz

# CONFIG_USB_DWC3_GADGET is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
CONFIG_USB_GADGET_DEBUG_FILES=y
CONFIG_USB_GADGET_DEBUG_FS=y
CONFIG_USB_GADGET_VBUS_DRAW=500
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=4
# CONFIG_USB_GADGET_XILINX is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_MIDI_GADGET is not set

I'm guessing the actually functionality isn't there though?

@Chuck-Bokath Are you using an LTE v1 or v2 modem? Are you using voxl-modem in order to connect to the network?

If you are referring to 5G NR connections, you should see some information in the next 2 months. Sign up for the newsletter at the bottom of modalai.com and we'll be sharing details there.