Thankyou Bill for the answer. It will be a few days before I start
this project but wanted to head off any problems I could prior to
starting it. Will there be any need for semaphores or other
synchronization methods to prevent collisions with these vi=92s at the
driver level?
Thanks again for
about but wonder if
you could do the same with the time zone. Then with the combination of
the DST value and the Time zone differences you could determine on
first read what adjustments are needed.
Hope this might help you.
Randall T.
this acquisition. I have used one 1162 in similar
applications but have not tried multiple 1162=92s in the same system.
I need to read these ports as quickly as possible so would prefer to
only configure the ports once then read continuously.
Any help will be appreciated.
Thanks
Randall T.
This is a good starting point. Take a look it may answer this question
and others that may come up later.
http://zone.ni.com/devzone/conceptd.nsf/webmain/6792BAB18242082786256DD7006B6416?opendocument
=932 the monitor command only works with netscape.
Monitor seems to work with IE 6 or at least somewhat. It works like
hitting refresh and using the snap command. It may work smoother on
Netscape but I don=92t have it to compare.
You could use the get queue status to return the array of elements in
the queue then search the array then if found remove the elements you
wish to remove. The flush queue could be used to remove all items from
the queue then index the new array of information back into the queue.
The flush queue
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
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
I have a memory leak problem with an application built under LabVIEW
6.0.2. I have found that the source of the problem lies within a loop
of code that runs every minute. It reads numbers from a remote data
socket
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
I don't remember the details, but the Alt key is tightly tied to
numerous behaviors on Windows. Either LV has started the menu walking
behavior and the events are pouring in, or I seem to remember some other
Alt key modified actions defined by Windows, sort of like Alt-tab, but
affecting
Ben [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
Hi Sean,
DI you really mean to say
Run your VI in highlight execution mode and monitor the CPU Usage.
?
Ben
Another cause for 100% CPU usage is pressing your ALT Key once.
Try this. Activate the Windows Task manager
Find your channel in the automation explorer where you set up your
virtual channels. Select properties for the channel configured for
temperature. You may specify the CJC Source select built in by using
the drop down box.
In the devices where your SCXI Chassis is listed, you will need to
make
Both of the modules you mentioned have built in cjc sensors. You
mentioned the 1303 terminal block then later called it a 1300. The
1303 should have a more accurate cjc reference than the 1300. I have
not used the 1112 but since it is designed specifically for
Thermocouple measurements they
Thanks, I have tolerated the auto selection tool but find myself
hitting the space and the tab constantly. I agree that it can be
handy. Yet often it is like dragging fingernails across a chalkboard.
In previous versions of LabVIEW it was possible to wire the connector
pane to the front panel items more efficiently than in version 7.
You could click the terminal on the connector pane then click an item
on the front panel then click another item on the front panel then
back to the connector
You might try increasing the rights of the user. I have not
experienced this problem or know why user rights should correct it but
other problems are corrected this way.
Perhaps reinstalling the video driver could correct this.
If you have corrected the problem I would be interested in knowing
You may set the options for LabVIEW to always use the decimal point.
On the menu select ToolsOptions Select the Front Panel Options.
Remove the check mark from the option, =93Use localized decimal point=94.
This option will take effect next time you start LabVIEW.
Note I am fairly certain that
If channel.vi can function as a top level VI or a sub VI is there any
changes in channel VI=92s state?
Does channel vi run as a parallel loop with the other while loops in
the main vi? Or is the channel vi placed inside the while loops in
main vi requiring the channel vi to run once as a sub vi
18 matches
Mail list logo
