@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

@Brian-LeCocq The Starling 2 is not intended to carry a payload. The Starling 2 Max can carry 500g payload

@Alex-Kushleyev said in Masking qVio: P5 160 120 255 ^@^@^@^@^@^@^ It is working now thanks. I have created mask in monochrome bmp and then used online tool to convert it into pgm but output had wrong header: P5 160 120 1 ^@^@^@^@^@^@^ I have used gimp now and exported with .pgm (binary) and it's working I put a preview mask on output image. [image: 1716379897238-d4604289-19d3-462f-99e3-89dcc788282c-image.png]

@Rowan-Dempster They've been released and are a part of the SDK but we just don't install them by default to save space. The .debs are onboard already and should install with an apt install In that context "blackisted" just means don't install by default.

@Matthew-Wellner , As we discussed offline, I am going to post the summary for the likely issue here: By setting "demag_timing: 1" in esc params, it enabled some experimental feature, which fails to work correctly above certain rpm. It prevents motor from spinning faster when more power is applied (above a certain rpm). You can see from plots above, the desired command for motor 4 (purple) goes higher, but actual rpm is flat lined around 5700rpm (black). Also the current jumps up significantly for motor 4 (black) when it hits that ceiling. For your motor, please disable this "feature" by setting demag_timing to 0. Depending on your current timing advance, we may keep that the same or increase slightly. After disabling demag_timing-> 0, i would recommend performing rpm step tests to make sure the de-syncs still do not happen. I am sorry about this, I will update documentation to not recommend using this feature. [image: 1716325132668-9ac17b56-3431-408e-bd34-a7006eeb55ef-image.png] zoomed in [image: 1716325145165-c12f7747-3523-416b-8467-f462ee7b7561-image.png] Alex

@viralp Behind the scenes "voxl-suite" is really just a meta package with dependencies on all of the debian packages in VOXL Suite. Therefore if any of the packages that voxl-suite depends on are modified (either removed or downgraded) then "voxl-suite" will no longer be installed. This includes the system image. Contained in the system image is another meta package called voxl2-system-image which is versioned the same as the System Image. Therefore if there is a system image / voxl-suite mismatch you will see the same effect. This isn't a major issue, it just means that you are straying from the exact package list defined by that version of VOXL Suite. If you would like to get to a known good state you download the latest SDK from our downloads page and install it with it's install.sh script

@leonardo-Andrade-0 For the case where you are using only GPS and MAG the parameters need to reflect that. SYS_HAS_GPS = 1, SYS_HAS_MAG = 1, EKF2_MAG_TYPE = 0.