This repository was archived by the owner on Aug 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
Readme: Update 'coav-control' instructions #134
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -43,15 +43,31 @@ Compile code samples | WITH_SAMPLES | OFF | |
| This method is recommended for those who want to use 'coav-control' on an Intel | ||
| Aero Drone. | ||
|
|
||
| A Yocto layer containing recipes to build and install coav-control can be found on | ||
| the repository under the folder 'meta-coav'. This layer can be easily added to | ||
| to the image build by following the steps described by Intel Aero documentation | ||
| [here](https://github.com/intel-aero/meta-intel-aero/wiki/Developing-on-Intel-Aero). | ||
|
|
||
| The recipe install the 'coav-control' utility tool as well an init script that runs | ||
| the tool on start-up. You can change it's behavior by editing the script file at | ||
| any point of the process that seems convenient to you (custom branch, custom recipe | ||
| or changing the file on the drone itself). | ||
| 'coav-control' utility tool comes installed on Intel Aero image since version 1.4. | ||
| Its life cycle is controlled by a Systemd service that *won't* be enabled | ||
| by default. To start the tool, issue the following from the drone's shell: | ||
|
|
||
| ``` | ||
| systemctl start coav-control.service | ||
| ``` | ||
|
|
||
| You can change its behavior to execute your desired combination of Detection and | ||
| Avoidance Strategy by editing the service file and restarting the service: | ||
|
|
||
| ``` | ||
| systemctl restart coav-control.service | ||
| ``` | ||
|
|
||
| If you want that to start 'coav-control' automatically on boot, use the following: | ||
|
|
||
| ``` | ||
| systemctl enable coav-control.service | ||
| ``` | ||
|
|
||
| We also provide a reference of a Yocto layer with recipes to build and install | ||
| 'libcoav' and 'coav-control' on this repository under the folder 'meta-coav'. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. meta-coav was removed due to code rot (it was already rotten). I mean, we can revisit this in future, as there's the a plan of refactoring meta-intel-aero and create a meta-drones or something like that, for things that are not Aero specific. |
||
| This is just a reference and aims to make it easier for others to embed this | ||
| project on a Yocto build if they don't want to use the layer provided by Intel Aero. | ||
|
|
||
| ### Method 2 - Compile and Install yourself ### | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if it's a safe thing to recommend. I'd either remove or add 'use at your own risk'