Motion Control and Motor Drives

cancel
Showing results for 
Search instead for 
Did you mean: 

Data is intermittently "dropped" during the test, Troubleshooting help

I have an Labview 5.0 application that moves a servo motor from 0 - 45 degrees while collecting force data.  This test collects about 60 data points (normal operation). The data is dumped into a spreadsheet.  The problem is: In about 5 % of the runs, there are only  about 50 data points. When looking at the data some of the data points are simply missing.  Other than the data being missing, the data points that are there are the expected force values.
 
From what I can tell (this is program written by someone no longer at the company) the motor does a vector move using the rotation and velocity.  While the motor is rotating, the data is acquired at about 10 hertz..  When the data is "normal" the spreadsheet data has the rows increment at 0.75 degree intervals.  Whe the data is "dropped", there are increments of 1.7 to 3.4 degrees.  (Please excuse me if I am using the term "vector move " incorrectly,)
 
The system is about 7 years old and I was pulled in recently, so I don't have much hands on experience running the tests or the VI. (The symptom was described as "the data looks funny".)  I am told this is a recent phenomenom, but I no long term data that supports this theory.
 
Has anyone had experience where the data acqiusition is intermittent?
 
Would I be better off creating a new VI that :
 
Does not use a vector move. Instead, generates the specific stepper motor position (every .25 degrees?) .  The resulting data will have the force data for every motor increment. 
 
Thanks for your help.
 
 
0 Kudos
Message 1 of 3
(3,405 Views)

Hi,

I’m sorry that you are losing some data, there are a few things we should check to see what is causing the problem.  First what DAQ and Motion hardware are you using?  Have you changed any of your hardware from the time when the system was functioning properly? 

It would also be helpful to know if you are losing the data when the data is being acquired or when it is being written to the file.  To test this you can place an array indicator after the data is acquired, but before you write to the file. 

Something else that could be causing the problem is breakpoints.  Are you using any?  How are you sending them? 

It may be helpful to look at your code if you can attach a small portion of your code that reproduces the problem.

Keep me posted and hopefully we can find what is causing you to lose those data points.

Have a great day,

GG

0 Kudos
Message 2 of 3
(3,392 Views)

Hi Gavin,

Thanks for the tip on using the array.  I am hoping to find time later this week to give it a try.

As far as DAQ hardware goes, the system is using a PCI-MIO16xe10. I swapped out the DAQ board and I still have the problem.  I don't know the details of the motion control hardware, other than it us using a servo motor.

 

Thanks,

 

Bill

 

0 Kudos
Message 3 of 3
(3,381 Views)