[Problem] DJI SDK-ROS Mavlink example

[wkyoun]

[Problem] DJI SDK-ROS Mavlink example

[pcler]

Does the IP and port of ground control station means those of the PC which is running Qgroundcontrol?

Yes. The target IP/port mean the ones of your PC that is running Qgroundcontrol Station. And the src port means the port of Onboard linux that you would like to communicate with the Qgroundcontrol Station. In the concrete, you can get target IP by checking the IP of your PC which is running Ogroundcontrol Station. And you can set target port by modifying the launch file that you mention, meanwhile input the same value on your Qgroundcontrol Station as the 4th point of https://github.com/dji-sdk/Onboard-SDK-ROS/blob/3.1/dji_sdk_dji2mav/README.md shows.

What's more, it is allowed that several stations connect to the same drone. That is how the indexes after "targetIp" "targetPort" "srcPort" come.

If the connection is fail, please double check whether the IP and port is correctly config. Then check out whether anything else blocks the port. Some firewalls may do so.

[pcler]

It would be better if you could show us more details about the failure, such as your launch file and your Qgroundcontrol station config. Thank you!

[lanyusea]

closed because we have updated all codes/docs about the onboard SDK to solve any possible problem.

please reopen the issue if you still suffer the same problem

[wkyoun]

wkyoun@wkyoun:~$ roslaunch dji_sdk_dji2mav dji2mav_bringup.launch

... logging to /home/wkyoun/.ros/log/e7964014-7499-11e6-85c9-00c2c6cf6a1b/roslaunch-wkyoun-    7686.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://192.168.43.124:36496/

SUMMARY
========

PARAMETERS
 * /dji2mav_bringup/srcPort1: 14555
 * /dji2mav_bringup/srcPort2: 14549
 * /dji2mav_bringup/targetIp1: 192.168.43.138
 * /dji2mav_bringup/targetIp2: 192.168.43.138
 * /dji2mav_bringup/targetPort1: 14550
 * /dji2mav_bringup/targetPort2: 14551
 * /rosdistro: indigo
 * /rosversion: 1.11.20

NODES
  /
    dji2mav_bringup (dji_sdk_dji2mav/dji2mav_bringup)

ROS_MASTER_URI=http://192.168.43.124:11311

core service [/rosout] found
process[dji2mav_bringup-1]: started with pid [7704]
[dji2mav] [INFO] Going to establish connection for Manager with index 0. The size of sender list is     set to 16, the size of send buf and recv buf are set to 512 and 4096...
[dji2mav] [INFO] Going to establish connection with 192.168.43.138:14550 using port 14555...
[dji2mav] [INFO] Attempt to connect to 192.168.43.138:14550 using local port 14555...
[dji2mav] [INFO] ...connection succeed.
[dji2mav] [INFO] ...succeed in establishing connection.
[dji2mav] [INFO] ...succeed in establishing connection for Manager 0.
[dji2mav] [INFO] Going to establish connection for Manager with index 1. The size of sender list is     set to 16, the size of send buf and recv buf are set to 512 and 4096...
[dji2mav] [INFO] Going to establish connection with 192.168.43.138:14551 using port 14549...
[dji2mav] [INFO] Attempt to connect to 192.168.43.138:14551 using local port 14549...
[dji2mav] [INFO] ...connection succeed.
[dji2mav] [INFO] ...succeed in establishing connection.
[dji2mav] [INFO] ...succeed in establishing connection for Manager 1.
[dji2mav] [INFO] Succeed in registering module heartbeat.
[dji2mav] [INFO] Succeed in registering module sensors.
[dji2mav] [INFO] Succeed in registering module waypoint.
[dji2mav] [INFO] Succeed in registering module hotpoint.
[dji2mav_bringup-1] process has died [pid 7704, exit code -11, cmd /home/wkyoun/catkin_ws/devel    /lib/dji_sdk_dji2mav/dji2mav_bringup __name:=dji2mav_bringup __log:=/home/wkyoun    /.ros/log/e7964014-7499-11e6-85c9-00c2c6cf6a1b/dji2mav_bringup-1.log].
log file: /home/wkyoun/.ros/log/e7964014-7499-11e6-85c9-00c2c6cf6a1b/dji2mav_bringup-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Warning: You have connected QGroundControl to a firmware flight stack which is only partially supported. If you are using the APM Flight Stack it is currently recommended to use Mission Planner, APM Planner or Tower as your ground control station.