The overall goal is just to get time synced between the Lidar and the VOXL2's IMU. Oddly enough, I was looking through the voxl-kernel for qrb5165 and the driver for PTP is there. Is the physical layer chip not able to support PTP? Where I see the driver in the Kernel: https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/tree/qrb5165-ubun1.0-14.1a/drivers/ptp?ref_type=heads

@garret Oh, nice! Glad it's working now!

@Gary-Holmgren you have saved at least one other person

@george-kollamkulam Where are you getting the image / ROS2 packages? Is this an image that ModalAI maintains? Just looking at the error, it seems like it can't find the yaml-cpp package. It could be that it's not installed correctly or something's wrong in your CMakeLists.txt. It looks like the yaml-cpp readme has some info for including it in your CMake project. If you're using camera_calibration_parsers from image common, it might be worth bringing the issue up there. Let me know if that helps, Ted

@ashwin This path should be on your host machine, in the modal-qdl repo's directory

Hello @Alex-Kushleyev @Eric-Katzfey I am looking to control the servo via PX4. Essentially, it will be a command either from the RC or GCS to open / close the servo motor. But, if that is infeasible, I can make it work via an API on the CPU / Linux on VOXL 2 to be controlled via SSH. Regards, Ashwin

RESOLVED for those who come after: it was indeed an ftdi cable issue. Keep in mind that MCBL-00091-1 USB to Serial UART Cable is not a proper cable (i tried two freshly out of the box, and none worked). Currently using this cable: https://www.amazon.sa/-/en/Moyina-Converter-Terminated-BeagleBone-Minnowboard/dp/B06ZYPLFNB

@Moderator oh I see, so to reduce overheating would it be recommended to use the default settings instead of limiting my process to cpu 4 to 7?

@tom i figured it out thank you

@Moderator This is appreciated, I had however already seen these docs. My issue is that though you have a 15cm extension that does not account for the orientation of the Voxl2 in relation to the sensor and location to mount them. due to this the 15cm connector is not long enough. Is there any advice on how we can extend these sensors beyond these lengths? Is there some shielding or other potential signal boosting we can do? Our goal is to eventually be able to position the sensors further away from the voxl2 as we want to use the hardware on much larger platforms where the rear sensors will need to be further than our current test development. TIA for any insight.

So something that I was seeing while testing this was having a bit of instability with Open VINS flying and altitude flying (Not Using VFC). I was seeing that voxl-open-vins-server stated that the IMU temperature was too high and kept resetting. After letting the VOXL2 cool down for a day I was able to have the Drone Fly in VFC mode but not sure how it flew compared to Position mode using VIO.

@Andrew-Martin You can check your camera calibration files with voxl-check-calibration If you see any missing I can likely locate them and send them over to you

@Jetson-Nano VOXL 2 does not have PWM out. You would need our IO expander board M0065 to bridge between UART and PWM. https://www.modalai.com/products/voxl2-io?variant=40610514206771

@Alex-Kushleyev Thank you for reverting back.