sourcethe catkin workspace. try with
rosrun dji_sdk_demo dji_sdk_client
1/F_SYNCand '0' at all other time instants. Sending the sync command also resets the free-running counter generating the timestamp.
Drone - Matrice 600
RC controller - DGI - GL 858A connected through LightBridge 2
Flight Controller - A3
OES - Intel NUC 5i5RYK running ROS
Mobile - iOS
Camera connected to Gimbal
We are trying to move the images captured from the Camera's SD card to the OES
The onboard SDK doesn't allow to transfer of images from camera to the OES but only allows it to control the camera and take pictures. We are able to download the images to the Mobile but we need to move the images to the OES file system. The only way I can communicate to the OES is through the mobile SDK which restricts me to send 100bytes of data in a 1kb/s connection. This will take forever to upload the images to the OES.. Is there any alternative solution for this?
@nithinreddygaddam the RC and Flight controller are not communicating over Wi-Fi, they are communicating over the proprietary 2.4GHz LightBridge 2 link. You should be okay setting up a parallel Wi-fi network, though as @amenonDJI said we do not test or support this kind of setup.
@chukcha2 the wi-fi connection being discussed is not in any way related to DJI SDK - you would basically use Wi-Fi to get both the OES and the mobile on the same network, and figure out a way to transfer files between them. Thus it could be any kind of data. You will have to either get a powerful Wi-fi AP (something like http://www.tp-link.com/en/products/details/cat-5039_CPE510.html) or bring the drone close to the RC at the times when you need to transfer data.
Also, check out OSDK 3.1.9, released last week. Adds a powerful new module - precision trajectory mission planning (uses advanced trajectory planning and control algorithms to execute geolocated trajectories). The precision trajectory feature has a slick interface for planning trajectories in the form of a SketchUp plugin that allows you to plan and visualize trajectories, and also observe the drone execute them in simulation. You can also import geo-located scenery to get a sense of the real execution of the trajectory. You can specify time intervals for pictures along the trajectory, and video can be captured as well.
Another thing we have added is the ability to record, in real time, Velodyne Puck LiDAR data into the popular LAS file format, standardized by the ASPRS and heavily used in the GIS, geo-informatics and surveying industries.
This release, as usual, comes with numerous additions and improvements to the core OSDK libraries - CMake support, Vagrant-based VMs for quick prototyping, threaded callbacks and camera/gimbal snippets in the Linux sample (as well as interfaces for all our new features) are just some of the additions to the SDK. Give it a spin! :smiley: