psdk_ros2: [psdk_wrapper] DJI M30 doesn't connect

Hi,

Thank you very much for this work, it is very useful.

I would like to report an issue that I encountered while testing the node with the DJI M30. I have successfully tested the node with a DJI M300 RTK, but when I attempted the same test with the DJI M30, I encountered the following error:

[ERROR] [1698328649.170769950] [wrapper.psdk_wrapper_node]: DJI core could not be initiated. Error code is: 225

I am using DJI Assistant 2 for simulation HIL and DJI E-Port for the connection of the drone.

Could you please provide guidance on how to debug this error? Any assistance would be greatly appreciated.

Thank you for your support and for this valuable work.

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 33 (29 by maintainers)

Most upvoted comments

Hi @bitcurious, I’m glad that you managed to make it work. We will try to improve the documentation so that it gives some more details about the actual hardware connection, although this is always custom to each end user. But thanks for your feedback.

@stevedanomodolor @RPS98 @biancabnd After some trial and error, I discovered that the issue was with the USB port. After some adjustments, I was able to resolve the problem. Upon running lsusb, I obtained the following output:

- Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
- Bus 001 Device 005: ID 2ca3:001f DJI e1e

With this configuration, the camera module initialized successfully, and I started receiving data on the camera stream topic.

@stevedanomodolor Okay got it. Yes I’m using E-port development module and USB to TTL serial module as well.

So I have one question which link configuration from following one should use to get camera data as well if they are using E-port Development board and TTL module?

  1. use_only_uart
  2. use_uart_and_usb_bulk_device
  3. use_uart_and_network_device"

Depends on which configuration you decide to do. In the bulk/network configuration of the nvidia for example, you have the options to choose, enable_rndis of enable_bulk, with the rndis configuration for examples, you would use the network configuration with the correct ntwork interface based on your computer.

@RPS98 @bitcurious, We were able to connect both the M30 and M350 with camera streaming. The main problem most people encounter is mainly with the bulk/network configuration which is responsible for the camera streaming. The serial communication does not require any special configuration if you have the FTDI and follow the tutorial as stated in the tutorial from DJI https://developer.dji.com/doc/payload-sdk-tutorial/en/quick-start/quick-guide/jetson-nano.html.

If i may ask what computer are you using? @RPS98 ?

I used the connection setup from the tutorial you sent, with the Payload and TTL connections.

  • The serial connection (use_only_uart) works on all three models, M300, M30, and M350, allowing me to fly without camera streaming.
  • The Bulk connection (use_uart_and_usb_bulk_device) works with the M300, enabling camera streaming. However, it doesn’t work with the M30 and M350.
  • The network connection (se_uart_and_network_device) doesn’t work with any of the three.

I understand the issue is with configuration, not hardware, when using network connection. I’ve been conducting tests with my laptop (Ubuntu 22.04), successfully connecting with the M300 and detecting the network on the M350, but unable to initialize Camera Manager.

I plan to continue these tests with an Nvidia Jetson once it’s available.

Hi @biancabnd, The last tests I performed were with version v3.5 of the PSDK, and it didn’t work. Now, with the new release 1.0 and compatibility with PSDK v3.8, I plan to test its functionality again. I hope to do it in the coming weeks. I will inform you of the results. Thank you very much for your work!