Android SDK Release Notes

Transcription

1 Android SDK Release Notes Release Date Highlights Mobile SDK is now available on our developer website. More information can be obtained from Github page. New product support: The upcoming Zenmuse X5R is supported by Mobile SDK The X5R functionality is the same as X5, except for additional interfaces to access SSD state is present. New firmware support: Mobile SDK supports the upcoming firmware versions for Osmo and Matrice 100. Mobile SDK is also compatible with the current firmware versions for these two products. Refer to Supported Firmwares section below. Other New Features A new callback CameraGeneratedNewMediaFileCallback is added to provide information of a generated media file, including the name, date created and the file size. A new class DJIAuxLink is added to provide signal quality of the remote controller to aircraft control link for aircraft products that use the WiFi video link (Phantom 3 Standard, Phantom 3 4k). A new method getdisplayname is added to DJICamera class to provide the currently connected camera string. A new method getcreateddate has been added to DJIMedia to access the creation date of the media. A string of format "YYYY-MM-DD hh:mm:ss" is returned. A new callback CameraUpdatedCurrentExposureValuesCallback now updates camera exposure values whenever they are changed. In automatic exposure modes, this gives the aperture, shutter and ISO values the camera is selecting, while in manual exposure mode, this gives the exposure compensation required for correct exposure.

2 Supported Products Products Cameras * Phantom 3 Standard, Advanced, 4K & Professional * Inspire 1, Inspire 1 Pro & Inspire 1 RAW * Matrice 100 * Osmo(With X3) * Lightbridge 2 with A2 * Focus * Phantom 3 Cameras * Zenmuse X3, X5, X5R Supported Firmwares Inspire 1: Inspire 1 Pro (X5 camera): Inspire 1 Raw (X5R camera): Upcoming Osmo: and the upcoming version Phantom 3 Professional & Advanced: Phantom 3 Standard: Phantom 3 4K: Matrice 100: and the upcoming version Lightbridge 2: Bug fixes Inaccurate Osmo gimbal push data: Calibration and axis stop status were previously inaccurate, and are now fixed in SDK debug logs shown: Debug logs are now removed and will no longer be shown on the console. Incorrect ultrasonic height: Ultrasonic height data was being pushed with units of decimeter. The units are now meters. Null pointer exception in stopconnectiontodjiproduct if no product connected: The implementation of stopconnectiontodjiproduct has been corrected to fix null pointer exceptions.

3 No callback after invoking rotategimbalbyangle : Callback for rotategimbalbyangle is now called. Interface Changes Deprecated property ismissionreadytoexecute in Mission Manager. Developers should check the status based on the result returned by the callback of preparemission. Remove base error from every sub error class. Now only the DJIError has the common error. The product models have been adjusted from Inspire1Pro to Inspire_1_Pro. Every model now has a method which can provide a UI ready product string. Known Issues CameraGeneratedNewMediaFileCallback might return incorrect information in Zenmuse X5 and X5R: The firmware for Zenmuse X5 and X5R does not fully support this callback in that the information returned by the methods getid(), getfilename(), getmediatype(), getcreateddate() of DJIMedia might not be accurate. java.lang.unsatisfiedlinkerror: This issue is related to the Android platform itself. In Android 6.0, Google fixed the problem where Dalvik was checking access rules incorrectly in previous versions. If the developers set the targetsdkversion to 23, they will get java.lang.unsatisfiedlinkerror. Workaround: Please set the targetsdkversion to 22. Phantom 3 Standard video lag: There will be some video lags using the Phantom 3 Standard if the DJI Go App and third party application are running at the same time. Workaround: Please ensure there is only one app running during your flight. Incorrect push data for waypoint mission: When the finishedaction property of the executing waypoint mission is DJIWaypointMissionFinishedGoFirstWaypoint, the targetwaypointindex in DJIWaypointMissionStatus is incorrect. Aircraft does not immediately RTH in Virtual Stick Mode when connection is lost: When Virtual Stick Mode is active, and return-to-home (RTH) is enabled (for when the connection breaks), the aircraft will wait until the battery is <15% before initiating RTH (assuming the connection isn't re-established before then). This will be addressed in the next Phantom/Inspire firmware release DJI. All Rights Reserved.

4 Android SDK 3.0 Release Notes Release Date Highlights After listening to feedback from the developers, Mobile SDK 3.0 has been re-architected and refactored from the ground up for ease of use and increased functionality. More information can be obtained from Github page. Simplified Object Model: Mobile SDK 3.0 has halved the number of classes from Mobile SDK 2.4.x while improving the functionality. It is designed with a scalable object model architecture that supports current and future DJI products. Mission Manager and Custom Missions: Mobile SDK 3.0 groups all higher order missions into MissionManager for easy access. In addition, a new CustomMission feature that allows developers to combine higher order missions into their own "Custom Mission" with just a few lines of code. Removed Developer Levels: All developers are now given full access to use flight control commands which were available only to Level 2 developers in Mobile SDK 2.4.x. WARNING Limited Backwards Compatibility: Although all the functionality of SDK 2.4.x is supported in SDK 3.0, due to the refactoring, this version is not drop-in compatible with SDK 2.4.x. Other New Features Support for Phantom 3 Standard, Phantom 3 4k, Inspire 1 Pro, Osmo, Lightbridge 2 + A2, Focus. Supported Products

5 Products Cameras * Phantom 3 Standard, Advanced, 4K & Professional * Inspire 1 & Inspire 1 Pro * Matrice 100 * OSMO * Lightbridge 2 with A2 * Focus * Phantom 3 Cameras * Zenmuse X3, X5 Note: Support for Phantom 2 Vision+ has been removed in Mobile SDK 3.0 Supported Firmwares Inspire 1: Inspire 1 Pro (X5 camera): Osmo: Phantom 3 Professional & Advanced: Phantom 3 Standard: Phantom 3 4K: TBD Matrice 100: Lightbridge 2: Known Issues Issue 1: Incorrect push data from Osmo Gimbal: The instance of Osmo Gimbal will push the flag for detecting whether gimbal has reached the limitation in three dimensions (pith, roll & yaw) to the callback. SDK will always return false for isattitudereset, iscalibrating, ispitchreachmax, isyawreachmax and isrollreachmax. Workaround: User could set up the DJIGimbal.setGimbalStateUpdateCallback() to obtain the attitude of the gimbal and compare them with the maximum and minimun of these three dimensions to verify whether the gimbal has reached the limitation.

6 Issue 2: New battery's SN error: If Users get the latest type of the Inspire 1 battery (TB84) and try to get its SN, they will get different SN everytime they invoke the getserialnumber() method in DJIBattery. Issue 3: In rare circumstances, gimbal might reset when the aircraft is executing a waypoint mission: The gimbal will rarely reset, return to center, when the aircraft is executing the waypoint mission. This might happen when the aircraft executes the move gimbal action in a waypoint. Workaround: Since it occurs rarely and if it indeed occurs, user could run the waypoint mission again. Issue 4: Incorrect result return in setlensfocustarget: It will always returns failed when users invoke the method setlensfocustarget in DJICamera. However, the camera setting will be changed successfully DJI. All Rights Reserved.