This repository was archived by the owner on Dec 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/pm 527 cpp client side odrive first setup #4
Merged
Conversation
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
…ese with proper CMakeLists.txt and package.xml. The CMakeLists.txt and package.xml hold the configurations to communicate with the Odrive over the USB connection
…erial connection in order to communicate with the odrive. It also has a march_odrive.json which has some general configuration and gives the operator basic knowledge on how to use the configuration file. The enums can be used to translate data for and to the odrive.
… start the odrive properly. The odrive_msg.msg is later used to publish data from the odrive into a rostopic. The odrive.cpp has a general main which connects to an odrive with specified serial number and starts a loop
…research into feature/PM-527-cpp-client-side-odrive
It uses the odrive_endpoint in order to communicate over the usb connection. The utils remain unused but will be integrated later on.
…tional dependecies
…library combination for the libusb-1.0
… libusb-1.0 in the include directories.
…onfiguration. These are used in a test file which is located in the test folder
Also reformatted the OdriveEndpoint class to be better readable.
…p-client-side-odrive
…oltage is read and published to a topic
…to the odrive_interface_test.cpp
Roelemans
suggested changes
Jul 29, 2020
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.
Looks good! (though I don't 100% understand everything 😅).
…axis specific parameters.
Roelemans
suggested changes
Aug 8, 2020
Roelemans
approved these changes
Aug 12, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes PM-527
Description
With this PR it should be possible to control the Odrive using CPP-code and later on ROS control. It is based on the native communication protocol which is also used by the official odrivetool shell. This is accomplished by writing a usb driver to send and receive data over the TX/RX communication line of the odrive.
Within this PR a basic program is included to publish data from the Odrive to a ROS topic to generaly display the usage and functionalities of the program. The Json file consists of the default configurations which are set during the startup sequence.
Changes