DJI-Jerry on master
fix:reverse X and Y in download… Merge pull request #735 from DJ… (compare)
@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:
@allanm84 A USB->Serial converter will report that it is connected even if the UART end is left open. To avoid false positives, we have an additional check (validateSerialDevice) that looks at the broadcast data on the line. If it does not receive any data on the line it will return this error. In our tests, this check has proven to be quite robust.
A few questions: (a) What VM are you using? (b) Can you post a minicom log? I assume minicom is running on the same VM, is that right? (c) What baud rate are you trying comms at?
DJI_Version.h, but now seem to be stymied by not being able to activate without some sort of connection to DJI GO to rectify the
New deviceerror. Using Lightbridge was not among our RC options. I also have the A3 connected to DJI Assistant 2 running on Mac. I had seen some thread about it being possible using Assistant running on a PC. Is this true? Are there any other ways to activate without a Lightbridge?
sudo usermod -a -G dialout $USERcommand
Hi. I've been trying to perform the M100's onboardSDK sample activation (https://developer.dji.com/onboard-sdk/documentation/github-platform-docs/PureQT/README.html) using QT Creator for Windows but it's not working. I typed the ID and Key pair obtained from DJI and then I opened the COM without any problems and received the following message:
STATUS QtOnboardsdkPortDriver::init,line 35: port COM5 open success
STATUS QtOnboardsdkPortDriver::init,line 42: BaudRate: 230400
Then, according to the tutorial from the link above (Activation - 7th step) I should click on the "version" button, but when I do absolutely nothing happens. There's no error nor any response from the application.
Ignoring this step, when I click on the "Activate" button, I get the following ERROR:
ERROR DJI:nboardSDK::CoreAPI::activate,line 388: Please call getDroneVersion first.
However, I believe this error is due to the fact that when I click the "version" button, nothing happens.
Does anyone have any idea as to why it is not responding to the "version" request?