Topics created by John Nomikos

@John-Nomikos , 1.4 GB/s is certainly impossible for SD card write speed, so there is definitely some trickery going on here. Because VOXL2 has a lot of RAM, the cache can be substantial, but I thought that sync command would solve that issue, but apparently not.

In case of writing on top of an existing file, i believe this is a bad test case because as you are changing contents of an existing file (overwriting on top of existing data), the file system needs to be updated to remove references to old data and i think it can be a bit tricky in case of these unstructured overwriting with various block sizes, etc - so this is probably why that process is slower.

If you find a reliable way of testing the SD card write speed in the SD card slot, please let us know! I will play around with it as well.

Alex

@John-Nomikos Edit: I swapped SD card readers (the original was UHS-I, this one is now UHS-II) and now am seeing 150-200 MB/s for both hats. Speed difference was likely caused by the card reader and not the voxl2. Still weird that there was a speed difference, but oh well

@Alex-Kushleyev I tried on a fresh VOXL2 that I factory flashed with 1.3.3 and did not see the same issue. Was probably something caused by my setup (either in config or something else). I know that particular voxl2 had damage to one of the mipi ports too

I appreciate the help!

@Moderator Yep, I got routing through the VOXL2 working. The problem was actually in my host and the device I was pinging. I would have to setup static routing on both devices. But I ended up using a NAT on the VOXL2

Thank you for the help!

@John-Nomikos i see, yes, most likely due to:

/lib/systemd/system/multi-user.target.wants/adbd.service

That re-enables it after reboot..

Anyway, it looks like you found a workaround. Alternatively you could potentially remove that dependency from multi-user.target.wants/ but i have not tested that

@teddy-zaremba I was running 1.0 when I was experiencing this issue. I can speak for newer SDKs.

@John-Nomikos Can you enable debug output messages on voxl-streamer (Use -v 0) and post the output? Thanks!

@Vinny Side note: I'm slicing off the little retention nubs on every DF13 connector I own today. I would suggest anyone planning on doing a lot of detachment-insertions consider this. I really don't think DF13's were ever meant for a lot of In-Out especially in awkward placements. Long live GH 1.25's..

We will have to look into this, we don't have any good answer

Scratch that. We tested more in a GPS rich environment and are seeing similar yaw features.

This might just be an issue with the hardware pitch.

Will investigate level horizon in air calibration seen here: https://docs.modalai.com/calibrate-px4-horizon/

added note here: https://docs.modalai.com/microhard-add-on-manual/

35caac2f-8a47-4fa0-86c1-5bef5b249e25-image.png

Is that version of GPS module supported in the version of PX4 you are using? Is it wired properly to your flight controller as well?

I had the same issues but even with different lighting, I cannot get it to work. I managed to calibrate the tracking camera but not the stereo. Does anyone have any idea how I could try to fix this?

I have the same problem: The reprojection error is to large for the stereo cameras and the calibration fails.

I’m having the exact same problem, but I can’t connect to an Ethernet. Is there any other option for calibration? I’ve tried for 8 hours straight with no luck……