Fatal LabVIEW communication errors with PCI-Step 4CX motion board

[LabVIEW-Guy]

I have a VI that continuously calls the "Read Per Axis H/W Status" VI for value motion control. This VI is called to check and see if any motion profiles are executing on a particular axis (1-4) of the motion board.

Sometimes, the error message "Data Read was not Axis #1 H/W Status. Execution Aborted" and the program will be terminated.

To get the software to run again I either must re-initialize the motion board from Measurement and Automation, or I must reboot the computer.

Does anybody have any suggestions as to why this might occur?

[Dustin_W]

The value motion driver uses a queue based processing system, meaning that it places commands on a queue, and the processor handles them in order, and places the results on another queue. One problem with this method is that it is easy to overflow the queue, especially as PCs get faster and faster. I would reccomend lowering the number of times you check the status of the axes. This should eliviate the problem.