Posts made by tom

@swickliff Interesting, have you had success with this hardware setup before?

@swickliff Can you post a picture of your setup?

@KnightHawk06 That is the source, yes.

@GlennTee yes that's what I meant. You'll have to git clone the repo instead of just downloading it in order for that to work

@GlennTee You'll want to run that outside of the docker container, before running voxl-docker

@KnightHawk06 With VOXL 2 different kernels enable different camera configurations. You'll want to flash the kernel that supports camera configs 1-25,

I recommend downloading the latest SDK from downloads.modalai.com, running ./install.sh and when asked the following:

Detected OS: Linux
Detected: M0054-1 (QRB5165M)
Detected: Config 1 w/ M0173 Breakout Board (Starling 2 Max, Starling 2, FPV V5)

=======================================================================================================
In order to support all of VOXL's camera configurations, specific drones require differing kernel images.
Please select your drone hardware to proceed with flashing the appropriate kernel image.
=======================================================================================================

PLEASE SELECT WHICH KERNEL TO FLASH
1. M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV V4 (D0008), D0010, PX4 Dev Kit (D0011)
2. M0054-1 -> QRB5165M w/ M0173 Camera Breakout Board, Starling 2 Max (D0012), Starling 2 (D0014), FPV V5 (D0008)

Select your choice from the options above
or press [Enter] to continue with current config: 

Choose option 1 for M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV V4 (D0008), D0010, PX4 Dev Kit (D0011)

@Jetson-Nano We have never used Microhard on windows but it's possible your firewall is blocking UDP data on that port

@pettertei I'd recommend filing an RMA and we can debug the issue: https://www.modalai.com/pages/rma

@Matthew-Wellner That isn't an error message. We manually set the cores voxl-camera-server is allowed to use in order to maximize performance

@GlennTee Thanks for the follow up!

@Jetson-Nano oh sorry I missed that you swapped to the M0173 + AR0144s, in that case you will have to recalibrate the cameras yourself as all I have is the original camera calibration which won't match your new setup

@GlennTee After a little research it seems that in newer vscode releases they dropped support for Ubuntu 18.04. I wonder if you can downgrade VSCode or use a different extension

@GlennTee Are you able to SSH onto the drone outside of VSCode?

@Jetson-Nano The serial number is likely located somewhere on the frame of the drone. Should be on a white sticker and have the form MXX00000XXX

@Jetson-Nano Is this a Starling 2 drone that you're using? If so, if you provide the serial number of the drone I can provide the calibration files. If not, you'll have to do the calibration yourself using a calibration card.

@h3robotics If the hardware is all good you should see the Sierra wireless device enumerate with lsusb and well as the network interface, wwan0 enumerate when you check ifconfig

@swickliff This is how the voxl-camera-server.conf file is generated, using these higher level config files (the following are the M0173 configs):

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/tree/master/misc_files/usr/share/modalai/voxl-camera-server/standard_configs/platform_config_1?ref_type=heads

These files live on target a /usr/share/modalai/voxl-camera-server/standard_configs/platform_config_1/

You can add a new custom config here and then setup the voxl-camera-server config file by running voxl-configure-cameras XX where XX is the camera config number you've chosen

@h3robotics It seems as though the modem itself is not being detected. Can you ensure that the add-on board is fully seated onto the VOXL and that both connectors are fully connected?

@KnightHawk06 You'll also want to add a -f to your voxl-calibrate-camera call for "fisheye"

@Jetson-Nano Yes, you can. You just need to make sure one is a "master" and one is a "slave"