Quote:
Originally Posted by stinglikeabee
I think you need to spell out your requirements for us before darting to solutions. Response between command and execution, sensors, motor specs, etc. all need to be identified. Identify the objective and a threshold for each requirement.
Will you be incorporating feedback sensors for positioning?
I think you'll do OK on this forum, but cnczone.com might have a lot more insight.
I can see where you may need real-time if you have some modeling in the loop to perform the next motion of the system. If you are just executing a set path in a loop-type method, then I don't see it being a requirement.
I'd recommend you dive into Arduino. It's easy and most of the coding work is probably done for you already. The ArduBlock software may even be sufficient for you.
Here are some basic Arduino links to give you an idea:
http://bildr.org/2012/11/big-easy-driver-arduino/
http://arduino.cc/en/Tutorial/MotorKnob
I would recommend looking at larger CNC-type stepper drivers - you can find some on eBay. You can use the Arduino board to send the command to the controller. All of these solutions require an external power supply.
If you are set using the NI solution, an external stepper driver shouldn't be too bad to hook up. You will need to generate a signal that can be interpreted by the driver. This goes back to your original methodology, and makes things seemingly simpler for you. If this is the case, you would have to find stepper drivers that can be controlled similar to the Arduino and build the code in LabVIEW.
I hope this helps you out. |
Yes, it's been very helpful. Thanks again.
Let's see. More about what I need:
1) There won't be any feedback as long as I'm not missing very many steps. Open loop.
2) Steppers: besides the amp rating to get a ballpark torque generated, I don't have anything spec'd out. Seems like all of the cheapest motors or motor drivers/controllers have been bi polar.
3) Command/response: This might not be what you have in mind, but I really only need the position of all of the steppers to be coordinated, as I'm essentially 'weaving' on a somewhat cylindrical surface with some fiber (carbon, glass, etc.) So, the speed of the motors isn't as important as long as it isn't
so slow that it takes days to make something. Maybe a revolution every second or two would be nice. I know that accelerating the steppers too much can cause missed steps so I don't want that. I was planning on using chopper drives to further minimize step loss, since they aren't hard to get.
Also, I don't need the steppers to necessarily respond in a certain amount of time-I just need to get the path of the payout eye that I want and also relative to the paths of other payout eyes.
Maybe you had more specific things you were wondering about as far as command/response goes?
I definitely don't have my heart set on NI. I just already have Labview and a DAQ card, so that was the first architecture I was looking at. But, besides that route, they are literally 10X too expensive for my budget!