Well, I'm not going to spend too much time looking into your motor's documentation but the fact that it uses USB, and you're using a USB DAQ as secondary control, means that there are a few things you will want to consider.
The big one is that you need to remember that anything running under standard LabVIEW over USB is not going to be "real time". You won't be able to guarantee that you do anything with potentially close timing. So, as an example, if you have a limit switch that you read with your DAQ, and you want the motor to stop when it hits that switch, if you do that "stop" command using LabVIEW you have no guarantee that it will stop as soon as you had hoped. Maybe it will look like it works, but all it takes is your OS pausing LabVIEW briefly at a critical time and your motor has now gone past your limit switch and broke your whole setup.
So what you probably ought to do is set up the limit switches so that they are hardware-based. They either need to signal the motion controller to stop immediately (it looks like the controllers each have 4 digital inputs that might be usable for this?) or they need to cut power to the motor entirely when hit. Then add in a system that if the positive limit switch is pressed, the motor can only move in the negative direction.
I would recommend you get either a 3rd limit switch or an optical sensor and use that to establish a zero position. This would be somewhere in the middle of your setup instead of at the ends, so you could measure a zero position without running into the limit switches.
Have you got LabVIEW able to "talk" to your controllers at all yet?
