@Vinny thank you for the informative reply. Cheers

@daz_22 , thanks for sending the output of the spin script. Just to note, the RPMs are reported as ramping up to around 1000 (by the end of the printout) because during the initial phase (spin-up), the ESC operates in open loop mode, where it drives the motor but does not detect the actual speed. During spin-up the predicted RPM is printed, but it could be false, if the motor is stuck or not even attached. The closed-loop control starts after the smooth spin-up, where the true RPM is reported (however you did not provide those prints, but i suspect the ID0 would just try to restart based on the reported RPM). The MCU in the ESC channel 0 seems to be functional and communicating, so that is good. However, the motor not spinning is not good. From software side, everything looks normal. If you believe that the Starling 2 Max arrived with non-functional ESC / wiring (who knows?), you should submit an RMA request in order to correct the situation. modalai.com/rma . If you think the issue might have been caused due to a crash or something like that and you wish us to fix it, you may still submit the RMA request. Alternatively, you could disassemble the drone to gain access to the ESC and see if you can visually detect the issue with the ESC or wiring. Either ESC channel 0 or wiring seems faulty. Please let me know if you have any other questions. Alex

@wrossi17 Can you post a photo of your setup?

@bendraper I'm not sure if this is still an issue for you, but you need to get a SIM specifically for data from here: https://fi.google.com/data - After they ship it to you, you can activate it through your Google Fi account using the instructions/activation code that come with the SIM.

I grabbed the /usr/bin/quectel-CM from another VOXL2 on an older SDK (1.4.1) and swapped out the one that came with 1.5.0 and everything is working again...

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?