@riteshsharma you are welcome. If the current approach initializes and works fine (is able to allocate all the buffers), the performance should be stable. I am a bit surprised so many buffers are needed for the encoder, there is probably some other settings in our software to change that... However since it is actually working with 11 buffers, maybe there is no need for me to test / fix that. If you do encounter any other issues, let me know..

@Alex-Kushleyev

all is working now. Not sure what has changed but we are all set. Thank you for your help Alex!

Stefan

@tom After 8 hours of grueling coding: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/merge_requests/11

@Isaac-Stephan-Remy

I need you to still explain how you are sending data from the voxl2 to the parent computer - just because they are on the same wifi network doesn't mean that when you launch the ros2 node on the voxl2, and then run a ros2 topic list on your parent computer it will see those topics. There needs to be somewhere on your rpi or parent computer where you are probing the voxl2's ros2 instance whether you have sockets opened up, etc.

Can you confirm that the voxl2 instance of ros2 is locally publishing - aka adb shell into another terminal instance of the voxl2 while the voxl-mpa-to-ros2 is actively running and try doing a ros2 echo TOPIC to see if it streams just fine locally - if it isnt, then that is your issue right there. Which topics are you actively trying to listen to as well? Do you have all the required services running? AKA voxl-imu-server, voxl-qvio-server, voxl-camera-server, etc.

Can you post a screenshot of voxl-inspect-services

Zach

@Alex-Kushleyev No. This was a test for the RTK GPS. I'll try.

@Vinny Oh, thanks for the advice!

@modaltb Great to know. I needed at least 2.1 to get layer support for RAUC. Which I hope ModalAI will support RAUC or SWUpdate out of the box at some point. Or another framework for OTA updates.

@Riccardo-Franceschini We were not able to resolve this issue. However because our control stack is sending TRPY commands to mavros, this didn't come into play at all. The concern for us originated when the drone was taking off significantly higher than commanded. It turned out the propeller coefficients we received from ModalAI were insufficient.

Hi @andrea_seock
That set of connections does appear to be correct now.
Keep us posted!

@Moderator Perfect. Thanks.

@Ethan-Wu Not sure about Ethernet. UVC is specific to USB.

Hi @nickyblanch
Anytime.
yeah, we had quite a bit of cables and mods to get to FCv2, but we think it's worth it, and now much more aligned with Dronecode and present/future hardware we make.
FCv1 was a bit of a anomaly from it's early design inputs and constraints, so we do view FCv2 as much easier now to work with (if you are starting from scratch).

We do have on our roadmap a much more "standard" drone mounting pattern w/o changing any other functions, but that effort keeps moving to the right... haha

@wetherbeej oh, yes.. that would do it. I was just going to ask about that.

By the way we are working on some camera-specific tuning tuning files, should be coming soon. The default may result in image colors appearing a bit off. However, we don't have a tuning file ready for IMX678 just yet.

If the current image quality is of a big concern, please let me know.

@Alex-Kushleyev Alright, thanks.

@SMRazaRizvi Issue resolved.
I connected one of the camera ports in a wrong orientation.

@leonardo-Andrade-0 It should be possible. Have you seen this https://docs.px4.io/main/en/config/flight_mode.html?

@SMRazaRizvi We can only comment on what we have tested with and that is the Commando 8.

@Sravan-Parakala we have emailed you directly

If we are not able to resolve this soon, i would recommend replacing the ESC, you could then submit RMA form : https://www.modalai.com/pages/rma .

In majority of cases, the scanning script should find the ESC even if it is missing firmware or params, so I am slightly confused why this is happening. It could be a hardware issue on the ESC.

The ESC you have now is board version M0049, which is older than the current version of the ESC and is no longer in production. If you are going to request a replacement of the ESC, you will most likely receive M0134-1 which is just a newer revision (not really better or worse, the functionality is the same). https://www.modalai.com/products/voxl-esc

In order to rule our the RB5 UART issues, if you are open to continuing to debug, i would recommend making an adapter using a USB-to-serial adapter and Hirose DF13 6-pin connector, then you could use voxl-esc tools on a PC and there is more flexibility in debugging. Please let me know if you would like to explore this option.

@Darshit-Desai Hi Darshit, you will need to modify the code to support what you would like to achieve. If you'd like to mainline, we accept merge requests