Draft
Conversation
Member
Author
|
This implements the functionality described in #230 |
Member
Author
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

This adds the modifications to the asynMotorController and asynMotorAxis base classes to support position compare output (PCO). This is a feature supported by a number of controllers to output pulses at specific distance intervals over a specified window while the motor moves. The Aerotech, Newport XPS, Galil, and ACSMotion controllers support this capability.
To use this feature drivers need to implement the virtual function asynMotorAxis::enablePCO.
The Aerotech Automation1 driver currently implements this on its add_position_compare_output branch.