yessss 6x9 and a white background both improved detection rate, not just latency. Thanks for your help!

It looks like configuration 28 is what you're looking for with the standard 3840x2160. That's the resolution I've tested the 214/377 sensors with.

@ShauliXtend said in Building a custom docker image with VOXL libs: on the VOXL itself you use 32bit libraries while the system is 64bit Yes, unfortunately the QVIO algorithm is proprietary to qualcomm, we don't even have the source, just the 32 bit binaries that they've provided. maybe there is a way to still use the 32bit file You'll need to compile a 32-bit program to use a 32-bit library, there's unfortunately no way around this without some sort of inter-process communication (hence our standalone qvio-server)

@Alex-Gardner So I guess I can't really do much to debug this (without knowing more about the proprietary implementation), true? Point being... if there is documentation you can share, I'll gladly dig into this.

Thanks for the hint @Alex-Gardner, I tried two separate modules on 3.3.0, 3.6.0, and 3.8.0 and they worked just fine, it is only with system image 4.0.0 and voxl-sdk 0.9 that neither one works which makes me conclude that it's not the sensor but something with the software. Also both modules works just fine when run by themselves, it is only in conjunction with other sensors like stereo/tof that the hires is causing issues.

@Chad-Sweet Thanks for your response. I apologise for the late response. As you correctly pointed out, we resolved the issue after a re-calibration of the front stereo pair in natural lighting and by further tuning the 'blur_size' and 'post_median_size' parameters in the DFS server config file. Now the data reflects actual physical obstacles quite reliably.

@Youngjoo-Kim J18 is the port normally used for the UART based ESC. It is connected to the DSP, not the Linux processor. You cannot directly access it from Linux. Why do you need to run Mavlink over a serial port? We support and recommend using UDP.

You should be using docs.modalai.com , the beta-docs are only published for specific, pre-release components. You cannot plug image sensors in where ever you like. You need to follow a supported configuration here: https://docs.modalai.com/voxl2-camera-configs/

Hi Chad, Thanks. One more question: Once new features are necessary during development or feasibility check, how to get ModalAI direct support? by contract or only through ModalAI forum? Best Regards, Dan

thanks for the suggestion, note added to hellocamera

Hi Jose, there's really not enough information for us to help here. What flight controller are you using? how are you connected? What did you change to get it into this state? that error implies you do not have GPS connected, or it is not outside to receive position information

You need to calibrate the thermal camera to generate the intrinsic. There is no off the shelf way to do this. You will need to create a to-scale checkerboard that the sensor can see

Modules such as Precision Landing in PX4 perform a indirect correction using relative camera coordinates translated to the global frame upon identification if the "tag/marker". I suggest you take a look into the Precision Landing module of px4 as an example in solving your problem. Of course that is using the IR markers available out there. Now we have internally modified that module for april tags in the landing case as well that will be available shortly. This method corrects the drone relative to actual ground truth (i..e the ARtag/IRTag), but does not correct the Global Frame position itself as its used as a relative offset to correct its setpoint position. That offset could be used to correct the global frame position itself (doesn't necessarily exist in PX4), but then again it would be better to transmit the actual GPS position of the tag to account for the curvature of the Earth, etc... and then calculate a proper offset.

I tried the link you provided,the ECS is not intalising and ardupilots firmware and voxl is not able to communicate with the px4. Also stats provided in voxl portal about px4 there is not available. Is it possible we meet on a call on any meeting platform, So that we can solve this issue easily? Thank you

Hi @Alex-Gardner I'm trying to accomplish the same thing as the OP but I'm running into some problems (my thread: https://forum.modalai.com/topic/1703/non-standard-camera-configuration-on-voxl-running-4-0-0-0-9-4). When connecting the stereo to J3 and hires to J4 voxl-camera-server -l outputs only two cameras which are the stereo, it does not recognize hires unless its on J2 but that has its own slew of problems which I've gone into more detail in my thread. Any help with this would be appreciated.

We don't have any experience with that package, sorry.

@Suvasis-Mukherjee said in MDK-M0117-1-01: I see D0-A,B, C which one corresponds to which pin mentioned above in the documentation pasted above? Hi Suvasis, Can you please clarify what you are referring to... I do not know what "D0-A,B,C" is to help you with this question. Thanks!!

@TasnimBas Glad we can help. Our team says this: "The injection molded plastics from the S500 frame are advertised as being glass-fiber reinforced nylon", so not sure if that helps you, but we do not have a material spec sheet to get the temp coefficients you are after. Maybe that description can get you close!

No, but there should be no difference to any other Debian system. I think if you Google it, you should find what you are looking for. From Google, I found this result which looks promising https://docs.ros.org/en/dashing/Installation/DDS-Implementations.html Obviously, we have not tried this

thank you.