@zauberflote1 said in voxl-open-vins-server How to Use, Overall Questions, ROS/ROS2 Findings: decision reduced the sampling jitter b Thank you for sharing your insights and great work!

@Harith-Dzikri I would definitely recommend Starling 2 for this application. You can see our opencv implementation here: https://gitlab.com/voxl-public/voxl-sdk/third-party/voxl-opencv

Hi @ctitus OK great! I am glad you picked that detail up! M0062 was a rather early design that we almost stopped making, so we never documented it nicely. But, there is so much demand for an RJ-45 that we decided to make a few more

@Shivam-Sehgal , I believe the TOF processing settings may have changed between SDK 1.1 and 1.3 (more noise filtering was added). In both cases, the ground is visible (although hard to see in the black image). In the 1.3.0 case, the other vehicle is not visible in TOF output, but there is less noise. Are you able to test the two SDK versions with some easy features for TOF sensor to pick up? Some large objects with simple geometry and some small objects. Alex

Hi @waqaskhan2000 , The M0173 was brought into our lineup to support our Starling2 product lines. We haven't released a reference drone (yet) using VOXL2 mini so the internal requirement to create one hasn't come up. We will likely create something similar but we don't have a timeline right now for that....

Hi @Janelletran , Because this board exposes pins directly from the 865 SIP, we make it kind of hard to find so folks know it will be easier to damage the VOXL2 product with this add on if you're not careful. This board: https://docs.modalai.com/voxl2-dev-test-board/ Has a hidden purchase link here: https://www.modalai.com/pages/beta-voxl-2-b2b-breakout-board Happy hacking!

@royb If you have another SOM sitting around it wouldn't hurt to try

@tom thank you for clarifying that.

@guyzoler Don't set a default gateway on the interface with a static IP.

@Alex-Kushleyev sounds good

@ijones2 This is great news! It looks like everything is functioning as expected so no need to go through the unbricking process at this point. It does appear that there is a fairly old SDK loaded on there so I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases" Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

@gitcoder You really shouldn't use ROS for this, especially when network bandwidth is limited. ROS and ROS 2 add significant network bandwidth both local to the device and over the network. If you really need it over ROS 2, you should use a compressimage sensor message. Here's some code we found through a search https://answers.ros.org/question/385599/how-to-publish-a-compressedimage-in-ros2-foxy/

Thank you for your help and hints Alex. We will definitely try to use voxl-streamer and modify it for VP8. Thank again, Milan

Nvm, solved, for some reason the voxl-vision-hub disappeared from the list, reinstall helped. Now I wonder why the ... it disappeared, but at least I'm unblocked.

@Stefan-Amundarain , It is always good to double check the firmware version of our ESCs and IO board (whichever you are using) so that you have control over the version that you are using and do not upgrade unless that is your intention or use outdated firmware. Typically when we release the new SDK we recommend updating ESC and IO board firmware because some features will require the update. However, if you just receive a new board, you probably want to upgrade it to the firmware version that you have already been using or version required by the sdk. Our voxl-esc tools (used for firmware update, checking) are used for IO board and ESC and make it easy to check and update firmware in an automated way to ensure you are running the firmware that you intended. If you need more help with this, please let me know. Alex

@jonathankampia Yes, both qmc5883l and ist8310 are supported now.

@groupo This code https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/mavlink_io.c?ref_type=heads#L156 sets up a pipe client to listen for Mavlink messages in the voxl-vision-hub application