For hires/tracking config C4, use J7 as shown in docs: https://docs.modalai.com/voxl2-camera-configs/#c-04-hires-and-tracking

@Darshit-Desai , if you don't have the emulator docker, the next best thing to do is to build the package right on target, using ./build.sh native option. please try.

you can see how the point cloud data is received in our voxl-mpa-tools : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-points.c . This is a very simple example, but you can use it to make your own application. this example shows how you can inspect 6DOF pose : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-pose.c (i believe you need voxl vision hub running for that)

@Alex-Kushleyev Thank you, appreciate the detailed response! (I completely missed this message, I thought I'd get a notification but I forgot to subscribe to notifications)

@jocacace13 PX4 sends out it's local position (as Mavlink LOCAL_POSITION_NED)

@19bpl At the very least you need to be able to ping the QGC computer from VOXL2 and VOXL2 from the QGC computer before attempting anything else.

@rohitpillai I would like to add that the auto-tune feature is not a turn-key fix all feature. you still need to tune filters, and do a bit of tuning yourself before initiating auto-tune. auto-tune gets you the last 20% of tuning, you have to do 80%. and even after that it still might need some adjusting based on how you want your UAV to fly

@Kashish-Garg-0 You might be able to find the raw lens parameters here The PMD libraries use those calibrations to adjust the point cloud data, so it may be corrected prior to being published as a depth map or point cloud. We have not used those lens parameters directly ourslves.

@Kris a 3 second delay is very likely on the client side with buffering, or network backup. RViz is not an optimal way to achieve low latency video as ROS typically sends an uncompressed, full frame. The QGC video display has much lower latency and uses a compress RTSP stream.

You can also dump frames or record a video , for example: voxl-record-video hires_large_encoded /data/vid1.h264 please note the resulting video may not be playable directly, but you can fix it using ffmpeg: ffmpeg -r 30 -i voxl-record-video.h264 -codec copy videofile.mp4 or play on your PC: ffplay voxl-record-video.h264 -framerate 30

@Eric-Katzfey Thank you so much for the information.

@Alex-Kushleyev Thank you! I'll look through the code a bit harder to make sure I'm not doing anything silly. I'll let you know if I have any more questions.

@Alex-Kushleyev Ohh. Yes please let me know how can I. I'm afraid I'll be needed spare parts for my research.

@Wei-Cui-0 @Eloi @SMRazaRizvi Hello, the cover form the Sentinel Flight Deck can be used interchangeably with the RB5 Flight Deck, as long as you are not using the ultrasonic sensors. Here is the link to the Sentinel CAD: https://storage.googleapis.com/modalai_public/modal_drawings/Sentinel_Drone_STEP.zip

@Bilal-Hussain , can you please clarify: "if it's possible to step up voltage." - what do you mean? which voltage? Regarding maximum current per motor, the mini ESC can output continuous current at least 10A per channel at 15-16V input battery voltage (we tested at 15A+ with direct cooling from the propellers). The mini ESC is recommended for small drones 300-500g range or small fpv drones (300g). Maximum input voltage is 16.8V (4S LiPo). This ESC is very small, so when you are building a new drone, you should conduct tests to monitor the ESC temperature which should to stay below 80C. If you are exceeding that and getting close to 100C, it is a bad sign. The ESC should be rated to operate at least 110C but if you are getting that hot, it is a sign that something is wrong (motors are drawing too much current for the ESC or insufficient cooling). We typically use the mini ESC in the drone designs that use less than 5A per motor during hover and may reach up to 15A per motor at full thrust for some time. The ESC reports temperature via UART feedback and it is available in PX4 esc status message. We will update the current specifications in the datasheet (https://docs.modalai.com/voxl-mini-esc-datasheet/) Alex

@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

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.