@wilkinsaf

A color AR0144 exists, but there is no current integration readily available

@Tamas-Pal-0 This seems like this might be a pid issue. PID issues causes unstable flight making the camera useless since it is all over the place

Would you be able to upload a ulog file to https://review.px4.io/ and post the link here so we can review?

My fault. Found a small tear in the ribbon for the stereo cameras

RESOLVED

Wanted to update this by saying I experienced same issue, but I resolved this by disconnecting tracking camera that had been installed upside down. So, if anyone is reading this in the future....try disconnecting your cameras attached to the board

I think these documentation pages are the same.

https://docs.modalai.com/voxl-cross/
https://docs.modalai.com/voxl-emulator/
https://docs.modalai.com/voxl-emulator/

Not huge deal, but thought I would post ticket to track

@tom Damn.... welp... that would explain what's going on.
Back to the ModalAI store. Thanks for confirmation Tom

Hello,

We have a UAV we would like to fly indoors and outdoors without landing during that transition.
I know that there is support for EKF2 GPS/VIO "fusion" using 329 as the EKF2_AID_MASK in PX4
Link to tutorial

We were thinking of manually changing the EKF2 bitmask when we fly indoors or outdoors.

My question is, are there any software/features available that would more easily support switching from GPS to VIO? Want to make sure I am not redoing work before I start.

Thank you

https://www.loom.com/share/8b4c948fb3794e7da8fec4c054bf0247

they are actually .cpp files that generate the config file
config_defaults.cpp

Can confirm ordering and installing a new one fixed our issue

@tom

It was a massive lift on my end. Many changes as you can see from the pull request. Years of development

I get this error: "[muorb] [ekf2] resetQuatStateYaw called:"

I know that this is expected behavior as the UAV stops listening to the compass and uses GPS for heading. My question is to the background of this, as I would LIKE to use the compass.

1. Was this done as the power consumption from the motors messes up the heading of the UAV
2. If the answer to #1 was yes, I am curious if we could do a compass power compensation: https://docs.px4.io/main/en/advanced_config/compass_power_compensation, or if this was already tried and didnt work
3. If we can not listen to the compass at all, I am wondering if there is a recommended way to disable the compass prearm check so that when we land in position mode, and go to takeoff again, the pre-arm checks dont yell at us that our compass is missing. - I know we can program something ourselves, but want to see if there is a recommended way that you guys have looked into. Just dont want to duplicate work.

Any advice would be much welcomed, and thank you for your assistance!

Some logs as well with high rate logging turned on:
https://review.px4.io/plot_app?log=ea8fad6d-1e00-4441-a70b-2726c6e8501b
https://review.px4.io/plot_app?log=fc2f0d95-0ef7-434d-88b2-1b1d8e0243d5

Update fix

Replace defaults.parm with upstream version: https://github.com/ArduPilot/ardupilot/blob/ee1e4bbf74061760826b17464383d63c1a11924c/Tools/Frame_params/ModalAI/Starling2Max.parm
Rename Starling2Max.parm to defaults.parm in /data/APM
Edit SERIAL3_BAUD=9 (in defaults.parm)
Edit GPS1_TYPE=2 (in defaults.parm)
Remove *.stg files in /data/APM
Reboot and power off the voxl2 multiple times, checking the gps driver

@wilkinsaf

I did the following and was able to get it

1. installed arducopter 4.7
2. disabled serial2_option for mavlink forward
3. configured compass
4. configured acceleromter
5. turned off GPS_AUTO_CONFIG
6. set SERIAL3_BAUD to 115200

https://www.loom.com/share/b96c3edd2286477ea294ddbd262dc31e

We are seeing some oddness when it comes to running Ardupilot on the Starling 2 Max.

We are unable to get really any GPS satellites, and the driver seems to be acting a bit weird.

1. We are able to get this working fine on PX4 - we run this pretty consistently. So, doesn't point to wiring

2. We tried Arducopter 4.6.3, 4.7, and 4.8 - we had the best luck on 4.7. But, even on that version weird things happen - like GPS_RAW_INT showing up with a lat and lon, but showing no visible satellite:

3. when indoors, only v_acc is updating...which feels odd: https://www.loom.com/share/3379c1aafcd74c95aa65e7f3af09a488

Any thoughts / ideas on where to look would be super. Thanks!

@Matt69

1. A UBEC was used for the servo connections, and they SHOULD NOT be powered from the board. We will update that drawing, thank you for pointing that out

2. As this was a first time build we did create that custom cable to deliver power to the airspeed sensor. We will make a note for that in the layout

Appreciate you pointing these things out so we can make those adjustments!

If anyone has run into this again,

ensure you update your /etc/modalai/voxl-tag-detector.conf to the tracking camera pipe you would like to do the april tag detection on.

the "tracking" has gotten update to "tracking_down" or "tracking_front"

@tom Thank you @tom

I have created some software that runs on the voxl.

I used the VOXL-CROSS template here: https://gitlab.com/voxl-public/voxl-sdk/voxl-cross-template

for all of my projects.

Now, I would like to have a CICD run that pulls them down and wraps them in my own SDK if you will.

I was curious if there is a recommended way to do this. I understand VOXL-SDK is built with CICD in mind. Is there a template I can use to do the same.

@tom

Choose Option 1 if you DO NOT have the camera board attached

Choose Option 2 if you are using the camera board