LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Processor goes to 100 %

Try this. Activate the Windows Task manager so you can see the
processor usage then make your version 7.0 application the active
window.

Press the ALT Key down and release it.

This will cause the processor to go to 100% and stay there. Press the
key again and your processor will return to normal speed.

Holding the Shift key or the CTRL key down will drive up the processor
speed also. Releasing these keys will allow the processor to return to
normal speed.

This also happens if you just have your development version of LabVIEW
7 open with no projects open.

> Does this present a problem for your applications if a user presses the ALT key then decides not to hit TAB or any other hot key combination possible?
The user has just sent the processor t
o 100% and left. Will the
application bog down? Will your control process stop? Will the datalog
file continue to work at the expected rate?

Again is this a problem? Any thoughts?

Randall
0 Kudos
Message 1 of 5
(2,830 Views)
Hello Randall

You are right, it happens also on my machine, Dell 1.5GHz, LV7, W2k.

You can see that when you press ALT and release it, the proc goes 100%
and the menu is activated. On the processes page you can see that it
is the LabVIEW which takes 99% of proc.
When you press ALT again the menu is desactivated and proc goes idle.
The same happens when you click anywhere else.
It looks like it has something to do with the menu.

But you have a good point, what happens when cont. data acquisition is
required?

regards
Pawel
0 Kudos
Message 2 of 5
(2,830 Views)
Hi all,
the same problem happens with LV6, but NOT with LV6.1.
I did some very preliminary test, and it seems it does not affect the
performance of a running vi; although the CPU usage jumps to 100%.
Probably because the menu handling runs in a low priority thread.
I will do some deeper test when I have spare time.
Alberto
0 Kudos
Message 3 of 5
(2,830 Views)
Hi,

You can make the VI without a menu, or you can disable menu tracking before
yuo start logging, and enable it when finished. But it's a kludge...

Regards,

Wiebe.

"pawel" wrote in message
news:5065000000050000005E5C0100-1075935269000@exchange.ni.com...
> Hello Randall
>
> You are right, it happens also on my machine, Dell 1.5GHz, LV7, W2k.
>
> You can see that when you press ALT and release it, the proc goes 100%
> and the menu is activated. On the processes page you can see that it
> is the LabVIEW which takes 99% of proc.
> When you press ALT again the menu is desactivated and proc goes idle.
> The same happens when you click anywhere else.
> It looks like it has something to do with the menu.
>
> But you have a good point, what happe
ns when cont. data acquisition is
> required?
>
> regards
> Pawel
0 Kudos
Message 4 of 5
(2,830 Views)
The default users menu will cause the processor to go to 100 % when
the alt key is pressed. With a special runtime menu for some reason if
the menu drops down the processor speed drops but if the menu is
highlighted it goes to 100%.

If there are no performance hits perhaps I over reacted. I first
noticed this when I noticed the windows pages not updating as fast if
my hand was resting on the CTRL Key when in the development mode.
Later when I saw the ALT key sent the processor up to 100% I decided
to stay with 6.1 until the problem was corrected.

I was told in October this was to be corrected with the next release.
I have had two updates with the subscription service and this was not
fixed. If I understand correctly it has been fixed but we will n
ot
receive it until the next full version release.

If Alberto is right this may be why they have not sent out a patch for
this. I found this curious that it didn't seem to be that important.
Any time the processor stays at a 100% usage it usually makes me think
somthing is wrong.

Thanks.
0 Kudos
Message 5 of 5
(2,830 Views)