Topics created by wilkinsaf

@wilkinsaf Thank you for posting your solution, very helpful!

@wilkinsaf Hahaha appreciate you sharing your expertise

If you could run camera server manually with additional debug prints (i.e. voxl-camera-server -d 0) and paste the output here, you'll be able to see more info about whats going on that'll make it easier to debug

It appears this happens when the sensors are not calibrated on the drone. voxl-vision-px4 picks up on sensor inconsistency and restarts PX4. So, calibrated the sensors. Looks better resolved

@Eric-Katzfey microhard addition

I'm not sure if you can have 2 slaves join the same network. From my understanding these modems only support 1 master and 1 slave

So, here is how we solved our issue. Even though EKF2 bitmask was set to only listen to GPS, heading still appeared to take VIO into consideration. After turning off VIO on VOXL we got MUCH better readings. Then, after we realized this, we changed out bitmask to 329 (which is in the instructions for flying outdoors without GPS here: https://docs.modalai.com/flying-without-gps/ So, our problem appears to be resolved right now. We just need to test repeatability for this solution

Perfect! I know how to run those. Thank you

@Matt-Turi @Chad-Sweet Sweeeettt. Thanks guys

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

@Eric-Katzfey Got it working about 50% of the time. It seems like most of the time it is just the uvc server trying to connect. I am going to see if I can create a service file around it. Maybe restarting on fail will get it to work with a bit of delay in between. A bandaid for the issue, but at least it will work

That is great to hear. Thanks @Alex-Gardner! I will update. I assumed I was on the latest as I had seen I was on factory bundle 1.0.1 and saw on this page: https://docs.modalai.com/downloads/ That the latest factory bundle was 1.0.1. Should I be paying attention to the system-image: ModalAI 3.2.0 When checking whether the system needs an update?

No problem at all, I'll get our docs updated so it's more clear, definitely not a rookie mistake, we should call it out!

Your video points to a bad camera configuration. The tracking camera cannot produce the resolution that VLC is receiving.

Yes, I realized I forgot to load the correct .params file before starting calibration. After selecting the one that disables gps and mag I had success. Thank you

Sorry for the late reply, were you able to fix this? Based on more recent posts maybe reloading the Flight Core Firmware fixed the issue?