Dear Vijay,
Your motor VI looks like it should work fine to move the motors once. If you incorporate a loop like I was talking about in my last post, I think you should be well on your way. The way I see it, you may want to implement a master/slave design pattern, or other
queued architecture in making your program dynamically update. You can explore some of these architectures by going to file»new from LabVIEW, and then browsing the different options.
The portion of your code that reads data from the joystick would be constantly updating in the master loop, and the code that send target positions and velocities out to your motors would be in the slave loop. You may run into trouble with the response time of your system with some queued architectures, because I would think the joystick position could update much faster than your motor positions, thus resulting in a backlog of positions waiting to be sent to you motors. If this were the case, you would see an ever increasing delay between the positions your commanded and the actual motor motion. There may be ways around this, like resetting the queue after it reaches a certain size, or limiting the loop rate for the loop that gets the joystick data.
Hope this helps!
~Nate
