why my program can only run once?

[nym8629@yahoo.com.hk]

I have a program that is already run for a long period. The program will move a axis backward to find index to

set the zero position. But in these day, i don't know why it cannot find the index and the motor will be out of

control. After i used a new motor control card to replace the old one, i can run the peogram once. But when

i use the program again, it will have the same problem. I need to shutdown the computer first to run it again.

[nym8629@yahoo.com.hk]

Moreover, when i only control one axis, there will not be any problem at all. 

[GiGe]

Hi,

Are you able to perform a move in the Measurement and Automation Explorer (MAX)?  You can test two motors using 2d interactive in MAX.  If you are able to move there then we will need to take a look at your program.  Did you create the program in LabVIEW? 

If you are seeing the same behavior (the motor spinning out of control) when you are in MAX, then we will need to check the hardware set up. 

What motion card are you using?  What motion card were you using earlier when the system was working?  Did anything else change between the old working system and what you have now?

Keep me posted.

GG

[nym8629@yahoo.com.hk]

When running the 2D axis in MAX, there is no problem.

and the attached file is how i find the index.

and we find that if the motor cannot find the index,

the "Existing  X" will be decreasing,

although it is moving forward.

[nym8629@yahoo.com.hk]

Two motion cards are the same,PCI 7330

[GiGe]

Hi,

There are a few things that could be causing the problem.  To help narrow the problem down try running the program and then go into MAX under 1D interactive (Device and Interfaces>>NI Motion Devices>>PCI XXXX>>Interactive>>1D Interactive) to see if you are getting an error there.   Run the code in highlight execution, and then watch MAX to see where the error occurs.  Let us know what axis status lights go on/off and when it happens.  

Also if you could send a reduced sample of your code (one main VI that contains just enough sub vi’s to move the motor and then read it’s position) that still reproduces the same error then it would be easier to test here.  Let me know what you find out when you run the code in highlight execution.

Have a great day,

GG