Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DC site] Roadmap Page #5

Open
biapalmeiro opened this issue Jul 20, 2017 · 6 comments
Open

[DC site] Roadmap Page #5

biapalmeiro opened this issue Jul 20, 2017 · 6 comments
Assignees

Comments

@biapalmeiro
Copy link
Contributor

Hi Bia (&Ramon)

Ramon has managed to generate a roadmap page: https://www.dronecode.org/roadmap/. When he's done with the content I'll give it a basic edit for appearance/matching our style. I have put a link to this in menu under Platform.

I could use your advice/help on how to best include this in the Platform page on dronecode. It doesn't fit into the existing structure, which is about what the platform is, and where its resources are. I was thinking perhaps plonk it front and centre???:

Inline image 1

What do you think?

Cheers

@biapalmeiro
Copy link
Contributor Author

Platform section of the Dronecode website, we need to have a breakdown of the parts of our platform that we can point people to:

Full document: https://docs.google.com/document/d/19O-IfTYOr10-FN6fLIY7QyrJZxs7nfhRhNNGpSH9krU/edit

Cloud:
Internet data services, used both for airspace integration and operator compliance verification and for processing of data gathered by the UAS.
Global Comms:
The wireless link(s) between the drone and/or GCS and Internet data services, usually a cellular or WiFi network.
GCS:
Ground Control Station -- the operator’s software interface. An application, running on a mobile device such as a tablet or laptop computer, that allows the operator to monitor and control operations.
Local Comms:
The wireless link(s) between the operator and the UAS. Typically a peer-to-peer connection, but may have a cellular network fall-back for redundancy.
FC:
The Flight Controller on the vehicle. It controls the vehicle’s flight, including both stability and navigation, and runs other flight-critical applications

CC:
The Linux-based Companion Computer on the vehicle. It typically controls the vehicle’s higher-level functions, including sense-and-avoid, localization, UTM and payload management.

@biapalmeiro
Copy link
Contributor Author

platformdiagram

@hamishwillee
Copy link

FWIW,

  1. Love having a diagram.
  2. Looks like drone info goes to the cloud via the GCS. Assume this is correct/intentional?
  3. I would update the legend as below:
    • CC to Companion Computer (CC)
    • FC to Flight Controller (FC)
    • Ground Control Station to Ground Control Station (GCS)
  4. Is "UAS" the standard now? I still see UAV far more often.
  5. Text updates:
    - Cloud: Internet data services, used for airspace integration, operator compliance verification, and for processing of data gathered by the UAS.
  • Global Comms: I would put the last clause in brackets, this is a matter of personal taste - ie "The wireless link(s) between the drone and/or GCS and Internet data services (usually a cellular or WiFi network). "
    - GCS: Ground Control Station. - I would remove the first sentence "the operator’s software interface."
    - CC: - What is "UTM"?

@mrpollo
Copy link

mrpollo commented Aug 30, 2017

@biapalmeiro can you please share the source for this file?

@biapalmeiro
Copy link
Contributor Author

Sure, @mrpollo. Here it goes!
platform.zip

@hamishwillee
Copy link

@mrpollo Please don't add that image without talking to me (and make sure the comments are addressed).

I like the diagram but it doesn't actually map very well as a tool for finding information and relevant projects - which is the way that the platform page is designed. Upshot if you dump this into Platform page (say) without thought it may not be effective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants