-
Notifications
You must be signed in to change notification settings - Fork 7
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
add support for Phytron MCC-1/MCC-2 integrated stepper motor controllers, add I/O support for all Phytron controllers #8
Open
lrossa
wants to merge
15
commits into
epics-motor:master
Choose a base branch
from
lrossa:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
- update information about supported motor modules including maximum speed - update documentation - check axis number - add serial communication and optional autosave - reformat code
add license identifier add digital and analog I/O support add support for sending almost any command
lrossa
changed the title
add support for Phytron MCC-1/MCC-2 integrated stepper motor controllers
add support for Phytron MCC-1/MCC-2 integrated stepper motor controllers, add I/O support
Jan 13, 2025
lrossa
changed the title
add support for Phytron MCC-1/MCC-2 integrated stepper motor controllers, add I/O support
add support for Phytron MCC-1/MCC-2 integrated stepper motor controllers, add I/O support for all Phytron controllers
Jan 18, 2025
kmpeters
reviewed
Jan 22, 2025
…SREV,UREV A harmonic solution was presented by Mark Rivers, who pointed out that setting zero defaults for MRES,SREV,UREV requires to set MRES or UREV (and optional SREV). This needs only one file and this allows the user to decide, which field(s) should be used to initialize the motor.
@MarkRivers provided a harmonic solution using one Phytron_motor.db file and the last commit implements this idea. |
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.
I added support for Phytron MCC-1/MCC-2 controllers, which fit better for single
or dual axis applications. These use most of the command set as the phyMOTION,
but with a different address scheme. In this case, you should use the new
command
phytronCreateMCC
(instead ofphytronCreateController
)and the rest has the same interfaces.
This also adds support for analog I/O, digital I/O and direct commands.