Open kkishore9891 opened 2 months ago
Hi @kkishore9891, Thank you for the detailed description. As you mentioned, if you have been able to run successfully the DJI samples then the configuration should be the same to run the wrapper. A few things that I notice and advices I can give you:
uart2_device_name
" from link_config.json file.(ls -l /dev | grep ttyUSB)
. You could also monitor udev events to see if rules are applied (sudo udevadm monitor --environment --udev
)Having said this, we do not have an M3TD drone in house, so the wrapper has not been tested with this model. However, we think despite a few changes, the main functionalities of the wrapper should still work. Let us know what you find out, we will try to support you as much as we can.
Hello!
I am running the wrapper on my Matrice M3TD drone and I am getting the following error:
This is the link_config.json file:
This is the content of the hal_usb_bulk.h file in the PayloadSDK from which we could successfully run the DJI sample programs:
content of the hal_uart.h in the original PayloadSDK repo that we were using:
The contents of the file where udev rule is set:
Despite adding the udev rule and running
I'd like to know if the wrapper works on M3TD drone. Also I would like to assure you that all the hardware connections are correct and we have tested everything in our in house ROS2 PSDK wrapper which can subscribe thermal image feed, run waypoint missions etc. But we want to switch from our PayloadSDK ros2 wrapper to yours to ease our development.