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

add support for Phytron MCC-1/MCC-2 integrated stepper motor controllers, add I/O support for all Phytron controllers #8

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

lrossa
Copy link
Contributor

@lrossa lrossa commented Dec 12, 2024

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 of phytronCreateController)
and the rest has the same interfaces.
This also adds support for analog I/O, digital I/O and direct commands.

add license identifier
add digital and analog I/O support
add support for sending almost any command
@lrossa 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
Copy link
Contributor Author

lrossa commented Jan 13, 2025

@kmpeters
I made some improvements to this support module.
Please have a look to this pull request and give feedback.
This pull request could even close the issue #5.

@lrossa 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
…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.
@lrossa
Copy link
Contributor Author

lrossa commented Jan 25, 2025

@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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants