Topics created by bendraper

I just pushed two updates to a branch of voxl-streamer:

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-streamer/-/commits/enable-h265-encode add option to use h265 encoder for non-encoded input frames (use either command line option -e h265 or --encoder h265 or in voxl-streamer.conf file "encoder": "h264" switch the h264 profile from baseline to main which allows using CABAC coding, which has better compression properties than default CAVLC at some expense of HW encoder usage (negligible) and potential additional cpu usage on decoding side. However, this will definitely be better for low bandwidth streaming. h265 uses CABAC coding as the only option.

It seems like it's working well, but not much testing has been done so far..

Alex

I want to add that M0125 is no longer being manufactured and we use M0151 as a direct substitute going forward. I'll try to have our product folks clarify the website for that.

@Vinny Extremely useful. Thanks Vinny!

After having some issues with a static IP on the VOXL2 Mini above it ended up being an issue with being on the wrong subnet for the host computer to communicate.

We ended up fixing the issue by changing the subnet for the host computer once we changed the IP on the VOXL2 Mini.

e.g VOXL2 Mini IP of 192.168.144.15 will require a host computer on the same subnet e.g. 192.168.144.98.

@Vinny Thanks Vinny for looking into this! I'm going to do some bench tests knowing this and will let you know how it goes!

@Vinny Thanks for this info this is super helpful. I 100% agree about the last thing you said and if I can use the ModalAI power adapter then I definitely will. I got the 7.4V spec by assuming nominal 2S battery voltage to nominal 6S, which was probably a bad assumption. Even so, a 2S battery from dead to full charge is typically 6.4V to 8.4V so I figured 5V input was probably not sufficient for the power module as it was not in the range of 2S to 6S. Seems like this may not be the case though which is excellent

@bendraper Yes, definitely

I tried on a different voxl2 with voxl-suite: 1.2.0 installed
the other one had voxl-suite 1.1.3 installed.

Not sure if that makes a difference....or if the configuration of the voxl2 was different.....

Either way if you are facing the same issue try SDK 1.2.0

Are static IPs over Ethernet supported?

@tom Hey Tom. So I tried doing it in WSL but I can only get as far as this screen

70ade761-ae41-450c-9670-1b5c8eaec823-image.png

After hitting that last prompt, it just hangs there indefinitely. Obviously since you haven't tried this method I don't expect there to be a solution, but I was wondering if this is a symptom of something you've seen before that may help in debugging further. If I cancel the flash the Voxl does not get bricked and I can use it as normal on the old SDK. There's also no LED indicators that may suggest its getting flash and obviously no visual indicators in the console that it's getting flashed so I don't think its getting very far in the flash process.

Hi @bendraper ,
Sorry for the confusion, we can make that clearer.
It's trying to say that you can connect peripheral devices to Voxl2.
So, maybe Instead of
"Use this board to integrate USB 3 peripheral devices..."
we can change it to say
"Use this board to connect USB 3 peripheral devices..."
Would that help in your opinion?
Thanks and apologies if that created confusion.

@Chad-Sweet That seems to have done the trick! Thanks

@bendraper in other words, what factors/scripts affect the generation of that conf file?

@Dobry-Kolacz I think I'm getting close. Im pretty consistently getting a reprojection error ~0.6 at this point so still have yet to successfully calibrate stereo extrinsics. Tried new stereo cams, refocusing, different lighting, different scales of checkerboards, but can't get sub 0.5

Have you used an oscilloscope to probe the line from the flight controller to VOXL2 to make sure the flight controller is sending data at the correct baudrate? Also note that the logic level of that UART connector on M0125 is 3.3V, I'm not sure if that matches the expected logic level of the port you are using on the CubeOrange.

Also note PX4 requires some serial port configuration. We normally use mavlink channel 1 with the Telem2 port on our flight core set to 921600 and 'onboard' mode. This translates to the following px4 param settings, note that yours will most likely be different due to using a different flight controller in a different configuration.

MAV_1_CONFIG 102
MAV_1_FORWARD 0
MAV_1_MODE 2
MAV_1_RATE 0
SER_TEL2_BAUD 921600

@Adrian-Hidalgo I redesigned the mounting piece for the cameras, used new refocused cameras, and fixed some errors in my general camera extrinsics file (although I'm not sure that last one is related)