This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
workgroup:dronecodesdk:start [2017/08/08 11:21] Shakthi Prashanth [===== Drone application features (spread across above categories) available in iOS/Android: =====] |
workgroup:dronecodesdk:start [2017/12/19 15:34] (current) Anitha Suresh |
||
---|---|---|---|
Line 54: | Line 54: | ||
| | Cloud API Support | No | No | No | No | No | | | | Cloud API Support | No | No | No | No | No | | ||
- | **SDK WG Meeting Minutes - July 18th** | + | ** SDK WG Bi-Weekly Meeting Minutes ** |
+ | * [[https://docs.google.com/document/d/1mB5oppWv0FhtbP1K-nmdEI_ppzdnrPPujSw0w2xv3dI/edit|21 Nov, 2017]] | ||
+ | * [[https://docs.google.com/document/d/1oyI8lIHmhKF7c5HzAbOsvbpJctG7FvaO_5yZ-1aefxQ/edit|07 Nov, 2017]] | ||
+ | * [[https://docs.google.com/document/d/1qmmbpal6k8QYL2jGSRdpB1owIw9LU56EREuezfQbzN4/edit|24 Oct, 2017]] | ||
+ | * [[https://docs.google.com/document/d/1U9x3kXiVatU1mROoVJy9SqbaMYGc1Wac4KmfRRlfixw/edit#heading=h.qj4hb1qx76h8|10 Oct, 2017]] | ||
+ | * [[https://docs.google.com/document/d/1bLb713cIZmntQ7euiAizAwnqGYcb5x0yP6_vpYx6rIM/edit|29 Aug, 2017]] | ||
+ | * [[https://docs.google.com/document/d/1DfUB-QJuXzB__5Uf5KwamKMyf_SYuZdWp53ldMTcZCA|18 Jul, 2017]] | ||
- | * Considering the current options available for SDK, we have two options for dronecode SDK – AirLib, DroneLink | ||
- | * Licenses: AirLib – MIT; DroneLink – BSD 3 | ||
- | * Presented the comparison for both AirLib and Dronelink from app developer’s perspective (included sample as well) – This included architectural discussion too | ||
- | * Unordered List ItemLorenz suggested for more use-case level discussion | ||
- | o Lorenz - to share the User stories (PX4 user's feedback) | ||
- | o Anitha – has requested UX team to share the user's feedback on SDK expectations perspective, which would be shared by July 26th | ||
- | * Unordered List ItemDroneserver - > Lorenz mentioned AirLib had some assumption to go with this architecture, which needs more discussion. Need to get some details about his view on this case. | ||
- | * Unordered List ItemDiscussed purpose of RPC in Airlib. As per Microsoft developer it is required to make application code independent of vehicle (Simulator or actual vehicle with any flight controller). | ||
- | * Above purpose can be achieved even without RPC by having abstract base class in SDK. | ||
- | Lorenz mentioned about DJI SDK, Currently DJI is leading market. So try to recreate the same user experience that DJI is providing - all SDK variants (mobile, onboard). | ||
- | -> DJI SDK has been considered as one our reference SDKs during comparative analysis. | ||
- | | ||
- | **Next steps:** | ||
- | |||
- | * Explore towards usage of Cloud SDK | ||
- | * Current gaps in supporting Cloud APIs/requirements in the SDKs we are considering | ||
- | * Planning to run apps on the real platforms, as we have only run on simulators for now | ||
**SDK WG - June 20th** | **SDK WG - June 20th** | ||
Line 92: | Line 81: | ||
* Mavlink library is ported to CPP. With this object oriented approach - makes easy to have pack/unpack function for each MAVlink message | * Mavlink library is ported to CPP. With this object oriented approach - makes easy to have pack/unpack function for each MAVlink message | ||
* Allows apps to configure drone connection parameters; so apps can choose which drone it wanna talk to. | * Allows apps to configure drone connection parameters; so apps can choose which drone it wanna talk to. | ||
- | * msr::airlib::takeoff(float limit) takes altitude param; so every takeoff can be tuned. | ||
-> DroneLink - > CPP Library provided by PX4 (Julian) | -> DroneLink - > CPP Library provided by PX4 (Julian) | ||
Line 103: | Line 91: | ||
* Auto detects the tool chain on the current platform | * Auto detects the tool chain on the current platform | ||
* Uses discovery model so that apps binds to a well-known port used by MAVROS (14540).(Author mentioned this as part of code that either this SDK or mavros can be used) | * Uses discovery model so that apps binds to a well-known port used by MAVROS (14540).(Author mentioned this as part of code that either this SDK or mavros can be used) | ||
- | * DroneLink::Action::takeoff() doesn't take altitude as parameter, rather it uses altitude set by default. | ||
| | ||
Line 153: | Line 140: | ||
===== Current Status: ===== | ===== Current Status: ===== | ||
- | * DroneLink is choosen as Dronecode SDK | + | * DroneLink is chosen as Dronecode SDK and is renamed as **DroneCore** with the necessary architectural changes to suit the purpose. |
- | * Brainstorming the Intuitive, On-demand and compelling applications for the user - In progress. | + | * Brainstorming the Intuitive, On-demand and compelling applications for the user - Ongoing and WIP |
===== App features Categories ===== | ===== App features Categories ===== |