@Moderator Thank you for your reply but I am able reach only the files of latest version of Starling from the datasheet and I need the CAD files of the one below if you have it:
I notice with auto exposure params if you are overexposing the image the lighter features stand out even more if there are darker areas in the image (since it's a mean sample value) but this could lead to issues with quality. Underexposing the image you end up getting dark images if there is a window or other large light source in the camera frame, resulting again in quality issues.
Yes, you're on the right track with running them as independent services with systemctl. You'll likely notice that they do all read from the same conf file and so what I'd recommend here is modifying the source code to point to a different config file location for each. I can help you find the section of relevant code if needed. This will give you different services with different configuration files. You've also correctly guessed here that you'll need all to publish to different output pipes so that they aren't overwriting each other.
Hi @Bilal-Hussain
You are certainly veering away from the intended use cases and design goals of VOXL 2 Mini, and instead we'd recommend you look at VOXL 2 so you can use add-on boards such as Eric mentioned like Microhard or a 4G/5G solution.
Modem performance with various base stations is operator/carrier dependent and nothing we can control nor provide metrics on. VOXL 2 can interface with many modems, so I think you might want to first do some modem analysis to see what modem solution will work for your intended use case and constraints.
From there we can help you determine which platform (VOXL 2 or VOXL 2 Mini) can work with your modem and carrier network of choice.
@lccarter it doesn't look like your aftermarket power module supports voltage and current monitoring in the same way as ours does. Our APM has an i2c voltage and current monitor built in.
@Dawid-Mościcki Perhaps you can ask the QGC development team for some help in narrowing down what is causing QGC to crash. If you think there is a missing parameter then in your /usr/bin/voxl-px4-start script add a new line to touch the parameter so that QGC will see it. (e.g. param touch SDLOG_MODE)
I reflashed firmware and reconfigured drone manually (not using automatic scripts which platform detection) and problem vanished. Probably there is something wrong with detecting actual drone version in those automated scripts.