Hi, The default framerate of 15 hz will limit the sensor to around 2-3 meters, lowering this to 5hz will allow you to see the full range of the sensor. As for the IR image, it's meant to help debug what the sensor sees, this isn't a normal camera with exposure/gain so the IR image will represent what the sensor actually sees, not necessarily in the most human-viewable format (Note that we often find the confidence image looks better to our eyes for demos).

@darwin-keem, It looks like voxl-mapper failed to reach your goal point, resulting in it sending over the partial trajectory it solved for viewing but not giving you the option to follow the path. You can try giving the RRT solver another second or so by increasing the rrt_max_runtime_nanoseconds param, and it should be able to fully plan to your endpoint. The path generation code has been rewritten and thoroughly optimized in the latest dev package, so if you are still having issues with this planner it may be worth checking out some of the updates on our dev repo.

https://forum.modalai.com/topic/1328/camera-servers-docker-build-royale-331-spectre-4-7 may have some answers for you on voxl-camera-server which is something ModalAI is working on WRT the build.

The camera server is working with another set of cameras after I reflashed the voxl 2. This might be a hardware issue. Thank you.

Hi, We've published an RB5 platform release that uses the entire VOXL SDK stack instead of the rb5 software suite. This supports using voxl-camera-server and voxl-streamer as you would on a voxl or voxl2. This release can be found here

Hi @Anton-Gereles , Can you please elaborate on your platform and specific problems you are having? I'm sure our Software team will want to know that to respond appropriately. That being said, our components and hardware elements are all at least rated for 0-70C, with many of them exceeding that. However, be mindful that is a non-condensing requirement. If you are operating in extremes (we have many customers that do), you need to be mindful of condensation risks. Rapid change in temp from a "room temp" building into an outdoor setting with high humidity and much colder temps (and especially vice versa) can create condensation. In these types of environments, you may need to provide some type of enclosure to protect the electronics against this build-up. Also, our products are not dust and particle ingress resistant as a default, again this would be something we leave our customers to define for their industrial/mechanical design requirements for an enclosure. Hope that helps and if you do provide more failure info, our SW team could respond. Thanks!

Hi, VOXL comes with FastCV installed, the 2 headers can be found in /usr/include/fastcv/ and the libs are in /usr/lib/ : voxl:/$ find /usr | grep fastcv /usr/include/fastcv /usr/include/fastcv/fastcv.h /usr/include/fastcv/fastcvExt.h /usr/lib/libfastcvadsp_stub.so /usr/lib/libfastcvopt.so /usr/lib/rfsa/adsp/libfastcvadsp.so /usr/lib/rfsa/adsp/libfastcvadsp_skel.so

Hi, You can definitely try it but the QVIO algorithm benefits A LOT from having a wide field of view on the camera and the hires cam has a fairly narrow field of view, especially when compared to the fisheye tracking camera. There are no hard restrictions to trying this but know that performance will almost certainly be worse.

@vivek-rk For anyone looking for a quick fix, you can use the voxl rtsp server for the hires only, for MPA support use the add-mpa-support branch

@Eric-Katzfey Yea... good thought... I'll look into that... Thx

@Ed-Sutter Hi Ed, I just now see you made two posts, so that other link along with this link is the bulk of what we have for showing the system level connections in a Voxl Flight Deck: https://docs.modalai.com/flight-deck-datasheet/#2d3d-drawings The Flight-deck exposes the ModalAI "Legacy" B2B (board to board) 60-pin connector which supports our modems, Microhard, and "debug" boards. All of those products support additional USB downstream ports so you can keep your primary USB to Voxl clear and open for ADB/Updates. https://www.modalai.com/products/voxl-debug-board-v2 https://www.modalai.com/products/voxl-lte?variant=32449203601459 https://www.modalai.com/products/voxl-microhard-modem-usb-hub Our schematics are not open hardware, but we do share a lot more than most. So if you need more info, please let me know. Thanks!

Hi, The same software stack runs on both VOXL and VOXL2, in which we have a voxl-mapper project for mapping/planning (though this is still firmly in beta and under active development by our team). The VOXL is capable of performing the mapping on its own, but the software stack is heavy and will take up a larger portion of the processing power on the weaker board. The VOXL2 is able to support more sensors and more processing, but with the obvious tradeoff of the higher price point. It'll be dependent on your use case which one you will want to use.

Please see email thread in progress, if possible let's use one channel for communications.

Hi, We've never tested QVIO on the hires cam, it's been extensively tuned for the fisheye tracking camera and benefits heavily from having a wide field of view. I suspect that this is where you issue originates. You are more than welcome to try this but you'll need to make sure that you've calibrated the hires camera and have defined accurate extrinsics between the camera and the IMU, but even with these done well it's likely to behave worse than the wide FOV tracking camera.

directly in the main folder or do i have to do it in the sub folder? @Eric-Katzfey