When I started my project, I only had one stepper motor to operate and I wrote a successful sketch for operating the motor using a joystick, recording positions with buttons, and then recalling/returning to those positions with other buttons. I wrote this using the AccelStepper library and it works great! The thing is, the whole project has other peripherals and pretty much takes up the majority of the available GPIO pins.
I have another project very similar to my last one, but this one has multiple stepper motors. My question is, how can I implement a digital multiplexer with the AccelStepper library and motors? The multiplexers I've used in the past required me to write my commands with the multiplexer "instance???" in front of the command seperated by a dot (.). Example: pcf8575.digitalWrite(P1, HIGH); How do you do this when the AccelStepper has the runTo, run, etc. already incorporated?
Any help would be appreciated.
Thank you for your time.
Ron.
I have read "How to get the best out of this forum". Just to let you know, most people that post a question on this forum do so because they DON'T know everything. They do so with the assumption that those answering their questions are actually interested in helping people not only resolve their problem, but to also help them learn going forward. If you don't enjoy helping others and are annoyed answering questions, then please don't. Being snide and vague in your answers will only make people not want to visit this forum for help.
You didn't mention what particular information I left out. I re-read my post and don't recognize any missing information. My question was a pretty self-explanatory question:
"How can I implement a digital multiplexer with the AccelStepper library?"
In case that was confusing, then let me state it another way. I want to be able to attach multiple stepper motors to a controller using a multiplexer. Can this be done?
If anyone can help AND WANTS to help, your advise will be appreciated.
Ron.
Your post looks like deliberately avoiding every kind of specific information. Know that ever helper is a newbie to Your project. We don't stand behind You looking over Your shoulder.
The first thing You miss is obvious, the controller You use. There are some 20 different Arduinos varying from a MEGA with some 54 I/O pins down to others having a lots less, maybe only a few.
More unspecific mumble. How can anyone give precise answers to that?
How many?
What multiplexer? Datasheet.
No my friend, tune down Your voice if You expect any respect for Your project. Personally I've got better things to then spending time on Your attempts.
I apologize if I mis-read your intent on your first reply. The information I gave in my original post was there only as a "back story" to why I am asking what I'm asking. None of if has anything to do with my question except to offer an explanation as to WHY I posted the question.
My question still remains: Is there a way to use a multiplexer (no particular one, any multiplexer, or if you know of one that will work) to control multiple stepper motors (again, doesn't matter if it's two, three, ten, etc.) and still be able to use the AccelStepper library? The AccelStepper library in conjuction with a multiplexer is the root of my question.
Again, I apologize for any ill feelings. The information you are asking for doesn't matter because I'm leaving that up to the person that answers. I don't know what will work, so I'm not about to start the project expecting to use a multiplexer only to find out I can't. Hopefully this makes sense.
Thank you, Railroader. Unfortunately, the tutorial isn't using the AccelStepper library. I've searched google and duckduckgo for several days and haven't found anything yet.
Have you thought about using an i2c based stepper? You can daisy chain numerous steppers that way on the same bus.
Are you needing to run multiple motors together, or is it one motor at a time?
Your multiplexer will work, youre writing a high signal to a specific pin that essentially transers a signal, as long as you structure your code and circuit to match, youll be good.
I highly recommend checking out those i2c based drivers though if you have the means