@Federico-Wyrwal , thank you for the reply. More debugging would be needed to figure out the root cause and it looks like you already submitted an RMA for the inspection / repair, so we will take care of it. Thank you.
Hi @Nate-The-great
Please do not delay any of your efforts or programs in anticipation of a VOXL 3 platform.
Our development roadmap is company confidential, but you can imagine we are working on many new and exciting things. One of the goals we have is to minimize disruptions should someone wish to "upgrade" platforms in the future. Similar to how we transitioned from VOXL to VOXL 2 by keeping mounting patterns the same, expansion compatibility (J13 -> J3), and plug-in board and sensor compatibility (M0048, M0030, M0084 & M0135 Camera adapters, etc), we would mimic that approach, but strive to make it even more seamless than before.
Therefore, there is very little to no risk to your system if you start developing on VOXL 2 today.
Out of curiosity, does the properly configured Boson work with original hardware + the CCI workaround in the kernel? It would be helpful for us to have that information for debugging.
Please send back the non-working adapters when you get a chance.
@Alex-Kushleyev Thank you so much. Now the camera is working. Previously, during the installation, I selected a second option of continuing the installation process with the option to keep the same configuration, which was wrong decision. It did not gave me an option to choose my drone name before. But, now that i selected the first option that give questions along the way, i was able to select the correct options for my drone as shown in picture below.
e5761ce3-3a28-4d66-b2dd-eed62fffdf42-Screenshot 2025-09-04 160830.png
Hi @jonathankampia
Hate to hand you off but this is out of my realm now.... I think @tom is more suited for helping on this front if we are sure it is no longer a HW issue.