Dear M.,
Thanks for attaching your MAX configuration and for the results of your testing. Everything seems fine with your setup in MAX from what I can see, so I decided to set up a test here. I was able to run the first tutorial (titled Heating a Semiconductor Wafer in a Furnace) without any problems here with a PCI-7344 Motion Controller, MID-7602 drive, and NI Motion Assistant 2.2.
Perhaps we can do some more troubleshooting in Motion Assistant:
What step exactly did your script get stuck on? If we know the expected behavior, then we can troubleshoot the actual behavior a bit better. For example:
Did your script make it past the reference move? If not, the continuous spinning makes it sound like it's just not finding the limit switch(s) it needs to move on to the next step.
But if it did make it to the straight line move, and just kept going past the position that you set, then something else is going wrong. You can check this by making sure you know the position setting and the mode (absolute or relative), and then looking at the Step Status tab during a move to see the Current position and velocity readouts. I would recommend using absolute position mode for your testing.
Did you set the velocity under the Move Constraints tab for all the different steps? I initially set just the first straight line move velocity and not the velocity on the reference move. After changing the velocity, click outside the tab (perhaps in the blank space under the add step button) and then go back and make sure Motion Assistant saved the value you set for the velocity. You should see a little dialog box flash momentarily, but really too quick to read, indicating that the script has been updated.
Does your motor move at the correct commanded velocity for a script that you create from scratch with just one move? Can you complete other types of moves than the one the script gets stuck on with the motor spinning indefinitely?
Hope this helps; please post back about how things progress.
Best Regards,
~Nate