@JoeC Sure. There is a configuration script at /etc/modalai/voxl-px4.conf that has some high level configuration values that affect how the startup script executes. The actual startup script now resides in /usr/bin. It is /usr/bin/voxl-px4-start. This is actually called from the higher level script /usr/bin/voxl-px4.

@Paola-Lim

You will need to follow directions from this page : https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

Tom suggested getting the SDK 1.1.3, so per instructions you should go to https://developer.modalai.com, log in, then click on Protected Downloads -> VOXL2 Platform Releases and download VOXL2 SDK 1.1.3 and follow the rest of instructions from "flashing voxl sdk" page

Alex

@tom That worked! thanks for the help

@muhammadbilal1

The batteries for Starling are standard Lithium Ion batteries (not Lithium Polymer). The recommended charging rate for Li-Ion batteries is 1C, so if the capacity is 3000mAh, the maximum charging rate is 3A. Charging at slower rates will extend the battery life (as is true for all batteries).

The maximum voltage is 4.2V. Please use a charger setting that specifically supports Li-Ion batteries. Most LiPo chargers also support Li-Ion batteries.

I will check how to proceed regarding the missing adapter.

@Aaky , we are working on resolving the GPS detection issue related to uart baud rate changes - if forcing the baud rate works reliably then just stick with that !

@Paola-Lim , have you tried voxl-inspect-cam -a (to see all camera stats) or alternatively voxl-inspect-cam cam0 which would be just for your specific camera name.

@Aaky Well, unfortunately it isn't obvious what is going wrong. You will have to start by disabling everything and when px4 comes up reliably start enabling things to find out the culprit.

@rdjarvis ,

The board is in eDL mode (emergency download). Can you please check that SW2 is off and if the issue is persists, provide serial number of voxl2 board, we will check test records.

Regarding enabling additional cameras, it is is not trivial and it would require a special kernel (because it would break the existing stereo camera support). Additionally, it would require a special interposer / cable in order to use a stereo pair with another camera on a single connector (this hardware does not exist now). At this time, we do not have plans to enable this functionality. As an option, you could potentially hook up a USB camera (will require an usb expansion adapter) to supplement existing cameras (using UVC interface), but we don't provide as much support for that option since that is 3rd party hardware and software.

Hi Rowan,

There is no one answer, it is entirely dependent on your circumstances. auto will be more conservative than perf. perf is intended to go as fast (and hot) as possible

@Jonathan-Davis said in Unable to run my own offboard node in starling 2:

offboard_mode

Check:
https://docs.modalai.com/mavros/#configure-voxl-vision-hub-localhost

offboard_mode - set to “off”. When offboard_mode is on, this enables voxl-vision-hub to command the drone to move, which we don’t want (we only want MAVROS to be sending movement commands)

@Moderator Yep, I got routing through the VOXL2 working. The problem was actually in my host and the device I was pinging. I would have to setup static routing on both devices. But I ended up using a NAT on the VOXL2

Thank you for the help!

@riteshsharma , based on changelog (https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/CHANGELOG) you can use voxl-camera-server package version 1.8.10 -- dowload it from here http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/.

Upgrading your SDK would also work as Tom suggested.

@Eric-Katzfey This sounds like perfect plan. I would implement this and get back for any queries. Thank you Eric!

@Aaky Unfortunately, we have not done any integration between PX4 and SPI devices on the apps processor. I would get an oscilloscope and see what is happening on the bus.

@Moderator Thank you. This clarifies everything.

@Aaky The Microhard board does not expose an apps processor UART but you could use a USB to UART adapter to connect to the Gimbal via one of the USB ports.