Move Complete status missed

[Anonymous]

I am running a fairly complex measurement and control program which
employs several stepper motors (VB6, NI Motion Control Module V6 plus
Flex-7334 and 7344 PXI boards). The user interface requires that
several timers are employed to update user information screens. The
problem encountered is one of missed 'MoveComplete' events for one
drive where movement intervals are neccesarily small (short time
interval). I have tried using flex-config-mc-criteria but without
success. When all timers are switched off the MoveComplete event
occurs, however program operation requires that the majority of timers
stay on all the time. Can anyone advise a work around?

[dmp]

Please try the following test: In Measurement & Automation Explorer (MAX), go to Trajectory Settings and then to the Move Complete Criteria tab. Set the Deadband count to 1. This means that Move Complete will be set to true when the axis is within one count of the target position. See if this impacts your application. Also try increasing the Deadbound count, as well as controlling the axis from MAX when no Move Complete Criteria are specified.

Best regards,
Dawna P.
Applications Engineer
National Instruments

[Bromley]

Hi Dawna,

Yes I have tried the Deadband count option setting it to 1 (and larger values) but this does not solve the problem. As a further comment, I get a similar problem in relation to other missing AxisStateChanged events. My system looks for a Home opto state change (in the direction where the system does not stop at the Home position). Again in 95% of the cases I am notified of the change event; for the other 5% of the time the event is missed and the drive continues on finally hitting the limit switch. Any further suggestions would be appreciated.

Regards

Alan Cormier
Sira Technology Ltd