@clange It is technically possible as Stinger is supported by the same VOXL SDK as all of our products. It would likely be a lot of software development to make it happen though

@tejasram The source code is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector. Perhaps try changing #define MAX_TAG_LOCATIONS 64 in locations.h.

@ggangmi What was the flight mode on takeoff and what did it unexpectedly change to? There should be logs in /data/px4/log. They may be incomplete or maybe even corrupted if the drone lost power in the crash but there should be something there. The logging starts when the drone is armed.

@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?

@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

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

Hi there, I would highly recommend upgrading to the latest SDK 1.6.2.

Q1: For voxl-vision-hub, openvins is just another [abstracted] VIO client, using the same MPA interface as QVIO. Thus, should work the same as QVIO.
Q2: There are no outstanding buffer conflicts between the 2 inputs in that SDK version. Though best to update to 1.6.2 as there have been numerous MPA improvements.

Q3: MAYBE ON GROUND, POSITION LOCK? is reporting that the barometer is reporting <1m and OVINS > 1m (-1 in NED space). It appears OVINS had a blow up, has recovered with a new origin in the local frame. Your output says it must have reseted in the ai/flying and hence the new local origin is above your landing point (fixed frame). Depending how you have PX4's EKF setup could lead to issues like the landing detector not working, or position error when running missions, hence why it's reported as a warning. Your output says it's at 0,0,-15 indicating OVINS restarted at ~15m up, but the PX4 baro says it's at 0. If outdoors, I recommend setting EKF2_HGT_REF = baro, if indoors, you'll need to reconcile a origin offset if VIO resets midair (qvio would require this as well) if using vio data directly waypoint manager (i.e. offboard waypoint mode or custom nav code)

Going forward if staying with 1.4.x,

edit /etc/modalai/voxl-open-vins-server.conf and change:
"en_vio_always_on": true, ssh into the drone and run voxl-vision-hub --debug_fixed_frame --debug_tag_cam --debug_odometry to compare values and see if there is a error in calculation possibly causing vision-hub to restart. move the drone around by hand, point it at a tag as needed and monitor the output from vision-hub. Should tell you where a possible conflict arises.

Hi @Tormod-Axelsson-Hagen
Our descriptions tell you all you might need to know to make your own power module:

2-6S tolerant (so VIN capable of up to ~25.2V+)

6A output at 5V

Current monitoring if you do not use our ESCs (our ESCs provide a current reading to keep PX4 and other autopilots happy and for accurate remaining battery %)

Connector format of your choosing but the Molex 4-pin MINI SPOX is the direct 1:1 for VOXL 2 https://www.digikey.com/en/products/detail/molex/0022057045/403343?s=N4IgTCBcDaIAxzGOBWA7HALCkBdAvkA

If you want to make this flexible for VOXL 2 Mini, make it capable of generating 3.8V and use the MOLEX MICRO ONE family of connectors https://www.digikey.com/en/products/detail/molex/2059720041/13235081?s=N4IgTCBcDa4AwFYCcB2Mc4BYCMIC6AvkA)

The rest is up to you based on your design intent and supply chain constraints and preferred vendors.
Hope this helped!

Hello,

This behavior sounds like turtle mode may be engaged. What are you using for a controller?

If it is a zorro blue the turtle mode switch is in the top left. As a general rule of thumb all switches should be away from you prior to arming. Controls have changed slightly since the guide on the docs page has been updated. I am working on updating them now. For now, please see the image on this forum post for current control mapping.

Hope this help,
Robbie

You can find the source code here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-logger/-/blob/master/tools/voxl-replay.cpp

@zaimin78 We no longer sell that module. We do have some in stock though if you reach out at https://modalai.com/contact we should be able to get you a custom order.

@Arsalan-Sheikh You can find a 3D STEP file here https://docs.modalai.com/starling-2-max-datasheet/

We aren't familiar with the Gazebo requirements so hopefully the STEP file gets you what you need