LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

very slow printing process

I'm using labview 7.1, with the latest addon report generation toolkit.
i'm running a vi that test and collect data and save the data to word document  through bookmark, then it prints report to a printer.  The problem occurs here at the printing process.  the MS Word keep on the running the print to printer and no report is being print out. But if i close the MS Word and cancel printing, i reopen the saved report and select print then it prints the report fine.  I don't understand could it be because the cpu is too busy running the vi or is it something else, any suggestion?
0 Kudos
Message 1 of 5
(3,067 Views)
Hi locman,

It is difficult for me to tell what exactly is causing the problem without seeing exactly how you are coding your VI.  It is unlikely that the problem is due to the CPU being overutilized.  You can watch the CPU utilization using Windows Task Manager, which is available by going to Start >> Run, type in "taskmgr" (without the ""), and then click OK.  You can then switch to the performance tab and you will be able to see the CPU usage.

As for finding the cause of the problem, it would be very helpful if you could post a simple example that demonstrates the issue that you are encountering.  This would allow me to better troubleshoot and determine what exactly is causing this problem.
0 Kudos
Message 2 of 5
(3,039 Views)

sorry, i'm unable to upload the VIs so that you can see better because of its big in size.  The CPU utility shows that 100% of the cpu is being use, and i'm not running anything else other then VI.  Hope this help you understand the problem better.

0 Kudos
Message 3 of 5
(3,015 Views)


locman wrote:

sorry, i'm unable to upload the VIs so that you can see better because of its big in size.  The CPU utility shows that 100% of the cpu is being use, and i'm not running anything else other then VI.  Hope this help you understand the problem better.


Check for while loops containing no waits.
0 Kudos
Message 4 of 5
(3,011 Views)
the wait.vi make sense, but does it affect the real time side of the machine.
0 Kudos
Message 5 of 5
(2,998 Views)