@ApoorvThapliyal
Thank you again for the reply!
We are setting up a multi-robot system, so we are using ROS_LOCALHOST_ONLY=0.
For example, we want to set the ROS_DOMAIN_ID of drone 1 to 1 and the ROS_DOMAIN_ID of drone 2 to 2.
However, for both drones, PX4-related messages still appear under domain ID 0.
Have you tried this with two or more drones?

@Alex-Kushleyev Thank you for reverting back. I will go through the documentation. If I disable the shutter will it work with causing any issue with respect to FFC.
Also I would wish use any other thermal camera with usb camera support, can it be used for localisation through QVIO, I will be required to create a MIPI communication, right?

I will find some documentation regarding the feature tracker question.- looking forward for your response.

Hii @Alex-Kushleyev , Thankyou so much for your time...
Previously, I said 4 cameras are detected and working properly only with M0135 interposer not with M0084 flex cable and the screenshot above is taken while using M0084 flex cables that's why only 3 cameras are detected out of 4 and hires is not streaming.

@brandon You'll need to load SDK v1.6.x to get it.

@Nitin-Varma-Vegesna said in Repair:

My Starling 2 drone crashed, and a good amount of damage was done. The PCB board was cracked, and the GPS mount was broken, and I was wondering whether I should submit a Repair Merchandise Authorization, and generally how long does the entire process take from submit an RMA to receiving the drone back?

I submitted an RMA form, but I would still like to know how long the entire process takes generally please?

@Morten-Nissov you have the kernel variant 2.0.2, which works with M0188 and M0195 camera adapters, but not the adapters you are using. Please update your kernel to use 2.0.0, there are details in a recent question here : https://forum.modalai.com/topic/4975/hardware-configuration-for-2-m0014-tracking-1-m0169-pmd-tof-1-m0024-hires/7

Alex

Hi @cbay ,

I checked with the team - we have not tested using the second lepton plugged into either M0188 or M0195.

The voxl-lepton-server is not set up to handle two sensors. It would have to be the same process managing both sensors because the i2c communication to both would happen over the same i2c bus and the i2c switcher would need to control which sensor is actually being communicated with via i2c.

We have checked that we can control the i2c switcher, but that's about it. We have not needed to use the second lepton (yet).

If you wanted to try it, that would be a risk, but here are the steps:

plug in and test lepton in primary port unplug the primary lepton and plug it into secondary port update the voxl-lepton-server to control the i2c switcher to switch the i2c path to second port test the lepton plugged into second port *** main task *** update the voxl-lepton-server to manage two lepton sensors, switching the i2c communication path, when it is appropriate please note that during normal operation, the i2c communication with lepton is not needed, i believe we only use it if we need to reset the sensor

Alex

@zauberflote1 I updated my system to the latest SDK 1.6.2 but unfortunately when I am in the VIO tab in voxl-portal, nothing happens when I click on the little tv-icon. Is there anything I need to configure to display the camera overlay?

@Vinny Thanks for the info,

Just to be clear, I am not looking for the PCB design schematics, just a symbol per board showing all the inputs and outputs to the board as a whole which then could be used in a system wiring diagram. If not I can just go ahead and make them myself, as all the info for it is on your docs

@Colby-Howell You can save camera data onboard using voxl-logger, but it will take up a lot of storage very quickly and the voxl2 has < 64gb so be careful with that. If you're not trying to save raw frames and are okay with compression & artifacts you can stream it to a ground computer with voxl-streamer and save it there

For connecting to the drone the easiest (especially cause you don't have a ground radio) is wifi, you can just connect your drone to a somewhat powerful router, set a static IP and ssh in.

For autonomous navigation, the best way in my opinion is to talk to voxl-px4 through the uxrce-dds bridge (implemented on the voxl2 as voxl-microdds-agent) https://docs.px4.io/main/en/middleware/uxrce_dds

Hi @Pelle-Bredegg-Hermansen
I'll be happy to review your design.

I'll email you now to start the exchange.
Thanks!

@sja123 No, unfortunately, we do not currently support boot from SD card.

@magnetocircuit Yes, this is supported. In the config file for px4 /etc/modalai/voxl-px4.conf set ESC=VOXL2_IO_PWM_ESC.

@Aaron-Porter Hello there,

voxl-evaluate-vins is currently not used by the Autonomy team @ ModalAI, we opted for our new benchmark solution, a bit more consistent in terms of statistical rigor and better integration with voxl-portal. Still, when replaying logs for VINS, it is imperative that one replays them using the ION pipes, as our VINS solution is optimized for cl_mem ptrs. Note that when replaying ION pipes, it is recommend to stop camera-server before replaying -- as clean killing ION pipes via the voxl-replay args is currently being optimized. This should resolve the common segfaults experienced during the replay/benchmark operation itself.

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-benchmark-vio

Finally, I would recommend updating your VINS to the latest available tag on Gitlab

Hello @ApoorvThapliyal,

Yes, I am dragging the point up and panning the camera around to ensure it is roughly the same height as the drone. The line drawn for the path is pretty straight and at the correctly level. The drone just ends up flying down below the point after I have move it.