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

[FR] Interfacing with closed loop stepper #12496

Open
alexxy opened this issue Nov 20, 2018 · 7 comments
Open

[FR] Interfacing with closed loop stepper #12496

alexxy opened this issue Nov 20, 2018 · 7 comments
Labels
C: Motion T: Feature Request Features requested by users.

Comments

@alexxy
Copy link
Contributor

alexxy commented Nov 20, 2018

What is the best way to interface with closed loop stepper motor?

Currently I working on simple design for closed loop stepper comntroller that can be very cheap but will its work. So basicaly it is stm32 mcu with tmc motor driver and magnetic encoder. So the main question is interface between control board and comntroller. Ideas?

@comps
Copy link
Contributor

comps commented Nov 20, 2018

See #11772 and the discussion in it.

@alexxy
Copy link
Contributor Author

alexxy commented Nov 20, 2018

Good point. But idea is to make motor controller board to all of position control thing.

@paukstelis
Copy link

There have been some discussion.
#11113

@alexxy
Copy link
Contributor Author

alexxy commented Apr 22, 2019

Its not user support question. I'm developing board similar to nano zero or machaduino. So I rise question about interfacing with Marlin.

So possibilityes are:

  • step/dir/enable interface + additional pin to report that movement done
  • step/dir/enable interface + spi or i2c
  • can bus to rule em all
  • i2c to controll everything
  • spi to control everything

Or any other suggestions? I think in case of using closed-loop drives marlin need some kind of feedback to know if movement finished or not, or it get an error.

I tested encoder resolution and stability: its ~0.02 degree (for example for 200 steps/rev stepper with 16 microstep we need ~0.1125 degree, so resolution is enough for 64-128 microsteps... )

@alexxy
Copy link
Contributor Author

alexxy commented Apr 24, 2019

I now implementing interface in that way

  1. closed-loop board exposes step, dir, enable pins that are translated into step dir enable of driver
  2. closed-loop board exposes additional two pins: ready and error that are used for reporting status
  3. closed-loop board exposes spi for driver configuration (as well as uart)

@crazyp1g
Copy link

@alexxy
Why not consider like that TMC 4361 and TMC5160

@InsanityAutomation
Copy link
Contributor

No, there is still plenty to be done around closed loop steppers. I just got a couple in 2 days ago to start playing with. The TMC motion controllers above would be hugely beneficial as well.

@shitcreek shitcreek added the T: Development Makefiles, PlatformIO, Python scripts, etc. label Jul 17, 2019
@boelle boelle added the T: Feature Request Features requested by users. label Jul 21, 2019
@boelle boelle changed the title Interfacing with closed loop stepper [FR] Interfacing with closed loop stepper Jul 21, 2019
@boelle boelle removed the T: Development Makefiles, PlatformIO, Python scripts, etc. label Jul 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Motion T: Feature Request Features requested by users.
Projects
None yet
Development

No branches or pull requests

8 participants