Posts made by elfowl

@mkriesel I wonder if that is the reason why IMX678 product on modalai show as out-of-stock at the moment. I contacted FRAMOS and they told me that they did not develop the driver for the sensor but modalai probably did it themselves.

I understand that this might work for a development system. But it basically makes VOXL unusable for commercial / production use where you need to have a reliable way to build an update a system.
Just adding a software package/version not available on the current system is a nightmare (especially regarding dependencies) if you can't use a proper build systems (e.g. yocto/bitbake).

@Eric-Katzfey we got that now. Do you provide information on how to setup the build?

Any rough guidance here would be great. As you can see in the related posts there are quite a few others interested in this.

@Chad-Sweet or to ask in a different way: is it possible for VOXL2 users to influence the sensor behaviour at all or do we just have to wait for a potential announcement?

ModalAI team: any update on this?

If not, could you clarify it the VOXL2 platform is more intended as a prototype only thing and you expect users to move to custom RB5 solutions with custom hardware and tool-chains later? Obviously if no custom build is possible this severely restricts the platform capabilities for potential products.

I just saw in https://forum.modalai.com/topic/1695/could-we-enable-voxl-2-to-support-hires-camera-ov64b-by-install-driver-without-system-image-re-generated that a system image can only be created by the ModalAI team.

Can you elaborate a bit on why this is? And what kind of options there are to get around the problem?

@Chad-Sweet Thanks. Can you give me some idea on what this would involve? Does that require modifications on the voxl-camera-server, on the ov7251 driver, or something else?

@Chad-Sweet thanks. Is there also a datasheet doc for M0113?

I am interested in the following setup on VOXL2:

• 4 * IMX335 Cameras (IMVISIO-ML)
• 1 * OV7251 Camera
• 1 * OV64B Camera (FLIR Hadron 640R, OV64B via MIPI and thermal imager via USB3)

I tried to understand the Camera Configurations page (https://docs.modalai.com/voxl2-camera-configs/#image-sensor-configurations) but got a bit confused on what is possible and what is not (and why not).
So it is hard for me to gauge the feasibility of the above setup.

I am aware that IMX335 support is being worked on and OV64B compatibility is not advertised by modal ai.
But as it is compatible with the RB5 I guess it should be theoretically doable to get it to work with VOXL2?

Related posts to OV64B / Hadron 640R:

• https://forum.modalai.com/topic/2345/how-to-bring-up-new-camera-module
• https://forum.modalai.com/topic/1673/does-voxl-2-support-the-hadron-640r-dual-camera
• https://forum.modalai.com/topic/2074/connecting-flir-hadron-640r-camera-module?_=1688096441146

The datasheet for the OV7251 says "30,60,90Hz implemented on VOXL, sensor supports up to 120Hz".
But https://docs.modalai.com/voxl2-camera-configs/#image-sensor-configurations only mentions 640x480 @ 30 as supported setting. I ideally want to run the sensor at 120Hz. Can you clarify what frame rates are currently possible and what it would take to make it run at 120Hz on VOXL2?

The camera config page mentions both the OV7251 and the OV9282 as compatible sensors for tracking/stereo.
But the link to the OV9782 (https://docs.modalai.com/M0113/) is dead - I wonder if you have any comments on the sensor.
Is the OV7251 the preferred / better supported solution?

Where can I find more information on creating a custom expansion PCB for VOXL2 - in particular the mentioned add-on design package?

The link https://docs.modalai.com/voxl2-custom-expansion/ used in the docs does not work.

I would like to build a custom system image for VOXL2, as the on-system approach using apt-get is good for testing/dev but can't be used for deployment or even reproducible dev tests.

While the Kernel Build Guide works great to build the kernel, I was not able to build the system image.

I tried modifying the qrb5165-build .sh script to do a full "bitbake qti-ubuntu-robotics-image" (not only the kernel task).
But this resulted in a lot of errors. So I wonder if this is the right approach?