Hey there, voxl-logger for openvins is only avaiable using a combination of raw flags, e.g. -c tracking_front -i imu_apps -r ov -r ov_extended -r ov_overlay Yes the -o option for odometry is not completed yet for openvins. That hsould get you the log data for openvins As for simulating camera stream failure, it's very likely any attempt to cover a camera will increase the exposure of that stream, and in some cases you will still see random features: for example, covering with a finger will still pick up features from your finger print. We're still actively improving voxl-feature-tracker and should have a new version available soon.

@Alex-Kushleyev Thanks for the help, as I was calibrating the ESCs I did notice those messages, which confused me as to why we weren't able to get that information in PX4. On Monday it suddenly just started working despite my changing nothing. Gotta love when things fix themselves

@Gary-Holmgren I'm also going to update the help text on that error in our deploy_to_voxl.sh template as the "ERROR neither dpkg nor opkg found on VOXL" is obviously not accurate

@Evan-D , based on the contents of /data/misc/wifi/hostapd.conf : # Maximum number of stations allowed in station table. New stations will be # rejected after the station table is full. IEEE 802.11 has a limit of 2007 # different association IDs, so this number should not be larger than that. # (default: 32) #max_num_sta=32 It is possible that after your device has seen 32 different clients, it cannot accept new ones. You can examine this config file and /usr/bin/voxl-wifi (which is used to set the device into the ap mode) and try to increase the number of stations. Alex

@Alex-Kushleyev I'll glue it back in place myself. Thanks!

@Gary-Holmgren , great! The transforms can be tricky sometimes especially with the added complexity of the image rotation in the camera… Alex

The diagrams may be helpful to explain the two options we proposed which do not require you to design any custom boards to plug into VOXL2. You will need to take care of interfacing to a GPIO board either using UART or USB. Option1: [image: 1717514293871-2399bf19-1422-471e-86e1-392817d383d3-image.png] Option2: [image: 1717514343432-b5ac8e69-0808-40fb-a288-11b4d34af5c6-image.png]

@藤田真也 , we do not have any examples for sending data to AWS, unfortunately. My recommendation is to start step by step and make sure you can do the following: install the latest SDK on your VOXL2 (https://docs.modalai.com/voxl-suite/) configure voxl-camera-server for your camera set up (https://docs.modalai.com/voxl2-camera-configs/) make sure you can see the camera images using voxl-portal (https://docs.modalai.com/voxl-portal/#voxl-portal) set up voxl-mpa-to-ros or voxl-mpa-to-ros2 based on your needs stream camera data via ROS to a different machine (local network or in the cloud). Please note that bandwidth requirement for uncompressed images will be high, so you might want to choose ROS to compress the images into jpegs before sending. after you become familiar with the standard work flow on VOXL, it should be straightforward for you send data to AWS (assuming you have experience with AWS). Alex

@Syed-Omair , I suggest that you try building opencv from source - the way we do it is shown here : https://gitlab.com/voxl-public/voxl-sdk/third-party/voxl-opencv/-/tree/add-python3-bindings/ -- this is a specific branch that enables python3 bindings. I actually have pre-build deb for this here. This was built and tested for VOXL2, but it should work on VOXL1 in a 64-bit ubuntu docker image. Just before installing the deb, please create the following directory: mkdir -p /usr/lib/python3.6/dist-packages/ this is the place where cv2.so will be copied for python to use. I fixed this on the branch but the deb was built some time ago and does not have this fix, so it will fail during install unless you create this folder. You should remove (or just don't install) other opencv packages before you install this one. Please try it out and let me know if it works for you. Also, if you want to build it yourself, you can see build.sh for build flags, etc. This is a somewhat stripped down version opencv. Building all of the components would indeed take hours on voxl. EDIT: the deb i provided may or may not work on VOXL1. The way it was built was actually on an ARM-based Mac inside a ubuntu arm docker, using native compiler flags. So i am not sure if it is compatible with armv8 or needs newer arch. However, you should give it a try. if the deb does not work for you, you can just try building this right on your VOXL1 inside docker using build.sh native option. Alex

@Eric-Katzfey From what I read in the forums, the M10 seem to be a very nice improvement to the M8N. It would be very nice if you can send them our way. Cudos to your team: They have already reached out to us with an RMA.

No @Matthew-Wellner , Our shipping dept is already done for the day and we missed UPS/FedEx drop-off times for next day delivery. I can't offer anything other than consolation that we've had some of our customers be amenable to a demo with non-NDAA compliant stuff with our assurance we have a plan to switch over (especially yours since it is available and in-hand, but just not working at the moment). I only wish I could probe your board remotely to help you figure this out... sorry.

@Moderator thanks for letting me know. I have a here 2 laying around. I'll just use that instead.

@Syed-Omair you can find the Dockerfiles in this repo https://gitlab.com/voxl-public/voxl-docker-images/roskinetic-docker from there you could try to modify the base file to see if you can get it to work. VOXL 1 runs an old Linux kernel, so there are likely going to be some limitations

@Alex-Kushleyev Hi Alex, you're right, I am using IMX214 as hires camera, If I set off the ae mode I should control the gain and shutterspeed in some way; If I set the ae mode on (ips or lme_msv) I would need to set the min and max gain, min and max shutterspeed, the desired msv and some parameters to control the speed of the adaptation is this possible? thank you so much

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.

@Stefan-Amundarain That's the correct QDL image for QRB5165. The next step would be to submit an RMA: https://www.modalai.com/pages/rma

@John-Racette Sign up for an account on the downloads page here: https://developer.modalai.com/signup Once you log in you will find the latest voxl-cross pre-built image (voxl-cross_v2.7.tgz) under the "Docker Images" section