Posts made by tom

@FIREBIRD Please reach out here: https://www.modalai.com/pages/contact-us

@jmltt Each microhard modem hosts a web server that can be accessed via it's IP address. You can see what data is available and can likely script a query for signal strength. (They may have an API but it's not something we've investigated)

@Jetson-Nano Are you able to ping from VOXL2 to the onboard Microhard board or the other Microhard board with the modules specified IPs? Usually 192.168.168.1 for master and 192.168.168.2 for slave

@Jetson-Nano See here how to set a static IP for microhard on the VOXL side: https://docs.modalai.com/microhard-add-on-manual/#software-setup

For the ground station side you'll have to manually assign an IP, like we do for Doodle modems here: https://docs.modalai.com/doodle-labs-user-guide/#ground-station-software-setup

@astro_phil What SDK version are you running? voxl-version

@astro_phil Make sure that voxl-px4 is not running while you're trying to talk to the ESC.

systemctl stop voxl-px4

@LR The 5G configuration on Starling 2 is a fairly new offering so there may not be fully representative docs live.

@LR When running through voxl-configure-modem you'll want to select em9191 not v2

@LR What do you see with lsusb -t and ifconfig

@kestrelsystemsbp Well you say you're using LORA which is not something starling ships with so I'm wondering if you put custom hardware on there

@kestrelsystemsbp Interesting, can you send the info of what receiver and transmitter you're using?

@kestrelsystemsbp Which transmitter / receiver combo are you using? It's possible the firmware was updated and it requires them to be re-bound

@bendraper I can't provide too much further help here as our hardware really just acts a bridge to the Sierra modem, you may have to check Sierra's docs to see if they have some debug commands to run

@kestrelsystemsbp You can download the SDK from downloads.modalai.com,

Untar it with tar -xzvf voxl2_SDK_1.3.5.tar.gz

cd voxl2_SDK_1.3.5

Install it with ./install.sh

Although if there isn't a specific reason you're on 1.3.5, I would recommend updating to 1.4.1

@bendraper 5G often requires a 4G link initially and then a handoff if 5G is available. You can use qmicli to query the modem to get further debug info

@Stefan-Amundarain First GPS lock takes a lot longer than subsequent locks. I'd recommend taking the GPS outside for 15 minutes or so for initial lock.

@paul-ammer If you aren't doing any VIO related flight you can disable voxl-qvio-server and voxl-imu-server. I believe you may still need voxl-vision-hub if you're communicating with a ground control station but not 100% positive on that, voxl-mavlink-server may be enough.

@AidanGallagher If you run voxl-camera-server -l you should be able to see a list of supported resolutions

@AidanGallagher If you want to try using the imx412-fpv sensor default settings you can modify the high level config file for whatever camera config you're using in /usr/share/modalai/voxl-camera-server/standard_configs/platform_config_* and change the sensor type from imx412 to imx412-fpv and run voxl-configure-cameras N where N is the camera config you're using

@kestrelsystemsbp Would also be helpful to see the contents of /usr/bin/voxl-px4-start