@Alex-Kushleyev Thank you so much for your response. It helped a lot.

@Igor , we just uploaded the emulator docker image, please see details in this post : https://forum.modalai.com/topic/5179/qrb5165-emulator-image-1-6

I tested the fix and snapshots work now, thank you very much!

@Anthony-Kang , we are looking into this. However, initial attempts to enable Intra Refresh on VOXL2 via the OMX api did not succeed either for h264 or h265. Also h265 does not work with fixed Macro Blocks (Coding Tree Units instead), so it seems the OMX structures for this param would not work with h265. Alex

@Alan_S The voxl-vtx repository is currently private, the source code for both voxl-vtx and voxl-vrx are contained within.

@Alex-Kushleyev Hi Alex, Thank you for the clarification. That makes sense regarding the accel parsing—agreed that a 4 LSB discrepancy on a 20-bit value is negligible compared to in-flight noise, but it’s good to see it will be corrected. Appreciate you taking the time to investigate and confirm. Igor

@ZuraNeb Perfect! Thank you!

If you're still having trouble getting that single sensor to initialize, double-check that your voxl-camera-server.conf file is strictly set to only enable that specific physical port. Sometimes the server tries to look for the default stereo pair and throws an error if it doesn't find both. It also helps to run voxl-inspect-cam -a just to see if the hardware is even being detected at the system level before diving deeper into the JSON settings.

@SKA , Most of the supported cameras (except for Boson, Hadron) have their reset signal connected to VOXL2, so when the cameras are not in use, they are shut down via the reset pin. This means that the camera modules may still get power, but they are shut down. There are many power rails and interposers - some power rails remain on all the time (5.0, 3.8V) and others may be shut down by PMIC when not in use. Different cameras use different power rails for their operation, so it is hard to answer this question without knowing the specific use case. Alex

Thank you for the quick reply. I will try doing as you instructed and post the results. Thank you. Kim

@fhaltmayer , unfortunately, we do not have any updates at this time. It looks like we may never release Ubuntu 20.04 for VOXL2 because it is a LOT of work to switch to a new major Ubuntu release and test + maintain everything. Additionally, even Ubuntu 20.04 is already relatively old, so we are trying to focus our efforts on more forward-looking software development with larger impact. Alex

Hi @Vinny Thank you for your reply! That's good news:) We are looking forward to it!

@SKA , I am not sure. please disable all streams except preview and try again. specifically disable: small_video large_video snapshot Double check to make sure: en_raw_preview: true en_preview: true en_misp : true It seems you have at least small_video enabled. What camera resolution are you requesting? (preview_width, preview_height) Alex

Hi @Alex-Kushleyev, sorry for the late reaction, it took some time before i could update to the new SDK (1.6). the system now works normally with the resolution 2704x1540, and downscaled to 1920x1080 for the MISP pipeline. Thanks for the help!

@bendraper Hello, I hope this quick clarification helps for warnings: CMake Policy warnings: OV internally (external dir in the repo) still uses boost and references an older cmake version -- it's a harmless warning for devs (as you are building from scratch) Yaml-cpp lib warnings: This is a third party dependency that gets compiled from scratch during the make/build process. We use C++ 17 but the library is based on an older C++ version; nevertheless, it compiles fine on C++ 17 with minor warnings. -- it's a harmless warning TrackOCL warning: ModalFlow is a core library written in C++ 17 that allows function call usage as done in TrackOCL, i.e., the narrowing conversion is harmless in this case. That being said, we are actively working on the dev branch, so all flight--impacting warnings are hopefully caught early. We currently have no flight-impacting warnings/bugs identified, but if you found one warning/bug that caught your attention, please feel free to share. All the best, ZBFT