Also don't forget that for each 'Obtain Queue' you use, you must use a 'Release Queue'
function. The queue reference will remain open unless you release it as many times as
you obtained it.
Ed
-Original Message-
From: [EMAIL PROTECTED] on behalf of Dominic Lavoie
Sent: Tue
I've had problems when installing NI driver discs on a PXI chassis
(Win2K) using a USB cd drive. It seems the windows autoplay feature
causes problems, though I've never been not able to open the drive.
Usually after I swap CDs, the installation just hangs and I have to
eject the CD, then close it
You could try searching the Info-LabVIEW archives at
http://www.searchview.net/
This site automatically archives the messages so they can searched. It
has everything back to 1991.
Ed
Edwin O. Dickens - Certified LabVIEW Developer
DISTek
As far as I know, making a subvi reentrant would have no performance
difference over having multiple VIs with different names. Maybe an app
eng could verify this.
Each time a reentrant VI is called from a new location in the code, it
creates a separate area for it in LabVIEWs dataspace, the same
Simple answer is yes, you would need copies of the subvis also.
LabVIEW can only have one copy of a certain named VI in memory at a
time.
Unless...
You make the VI Reentrant. Setting a VI to reentrant causes LabVIEW to
open each instance of the VI in it's own data space, so it acts the
same as
In the Application Builder on the VI Settings tab, highlight your top
level VI and click the 'Edit Build Settings' button. The last selection
in this dialog will let you force the front panel to full screen when
it's opened.
You can also set this property in the VI Properties. In VI Properties,
I'm guessing you forgot what password you set when you turned it on.
There is no way to just turn the password protection off without knowing
the password to first unlock it. If you could do that, it would defeat
the purpose of protecting it in the first place.
The VI password protection seems to
If you're OK with the copying and pasting, you could continue getting
the data into LabVIEW that way, and after converting the data into an
array, you can write it to a table through the 'Value' property of a
property node. This takes a 2D array of strings.
If you want to get away from the
Good thinking.
After a bit of experimenting, my best guess would be bits 4 and 5 of
the number indicate a version change and recomile, and I think bit 4
is the one for a version change.
Maybe somebody at NI could verify/correct this, or at least point to
some documentation on the mod bitset
DISTek Integration is currently seeking a Test Engineer. The Test
Engineer is responsible for the design, development, deployment and
support of test systems for electronic products. Position includes
high-level functions such as test planning, detailed design and
development of test software. The
Hello list, excuse the slight intrusion, but I thought somebody might be
interested in this.
Our Test Systems and Software group is taking resumes for a Test
Engineer with LabVIEW experience.
For a full job description and to submit your resume,
http://ww2.distek.com/MenuItems/Employment/TEL.asp
If you use the Save with Options and remove the diagrams, make sure
and do it to a BCOPY/B of your VIs as there is no way to get the
diagrams back. They are actually deleted from the VI, not just hidden.
Always keep a complete copy of your source code in a different
location so you can always get
I think the best way to do this would be to save the VI you want to
open multiple time as a VI template (.vit).
Then when you open a reference to the template and open the front
panel, the template gets renamed with a sequencial number, and it
changes to a .vi, just as if you had opened the
Sure, just zip up all the VIs and templates and attach it to a message
here. That way, more than just me can look at it.
If you had LabVIEW open when you did the installation of the
Application builder, it would not show up in the Tools menu until you
restarted LabVIEW. It only populates the menus at startup.
Ed
Sounds like you don't actually have a DAQ card installed in your PC.
The DAQ assistant can't list any channels if there are none available.
Unfortunatly, the exercises were written assuming you have a DAQ card.
Ed
Thanks Ryan,
Somehow, my search through the exchange did not turn up any topics
covering XP Tablet, or maybe I was just blind that day.
Anyway, that's kind of what I figured, and hoped. I should have one my
hands soon and will give it a try.
Ed
I have a customer looking at the new Tablet PCs and they would like to
use them for running some LabVIEW applications. In the end, these
would be built executables, but it would be nice to install LabVIEW
for debugging purposes.
I'd apppreciate any comments on both the run-time and development
There is not a sample test, but you can download a pdf of the Tasks
and Objectives that might covered on the test a
href=http://volt.ni.com/niwc/common.jsp?page=custed_cecp;here/a.
Look for the Certified LabVIEW Developer heading, then click the
Tasks and Objectives link. There is also other
The problem with the Make Current Values Default is that it cannot
be used on a VI or Global that is currently running or in use. Using
that method requires a re-compile, and that cannot be done while the
VI is running.
Reading and writing from a file is going to be your best option. Take
a look
You can use an Invoke node with the 'Abort VI' method and get a
reference to your subVI and kill it that way, but it's not good
practice to use Abort to stop a VI, it's really a developmet/debugging
tool. Another problem is the Sequence structure, they cannot be broken
out of before it's done
When I've seen this happen, it usually turns out to be a timing issue.
With Hilight Execution turned on, the program executes much slower
than it does when running normally.
Try putting some time delay between your steps, or Read/Write
functions one at a time to see if that fixes your problem.
I=92ve had this happen two times.
Once turned out to be an intermittent Ctrl key. The other time I was
using a Keyboard, Video Mouse switchbox to run two PC=92s with one
keyboard, mouse and display. To switch between the two PCs, you could
hit the Ctrl key three times quickly. Somehow that
You can use the 'Make Current Values Default' invoke node, but as the
name implies (note =93Values=94), it will set the current values to
default for Ball/B controls on the front panel. There is no way to
use this on just a single control.
There are other problems when using this property. The VI
I ran across an odd behavior with the BBuild Text Express VI/B
that wasn't there in 7.0.
When configuring the VI, if you select either Number or Boolean in the
Variable Properties before typing anything the Text with Variables
box, the first character you type will switch the Variable Properties
Different version of LabVIEW can peacefully co-exist on a PC. The
different versions will get installed in their own directories under
the main National Instruments directory. You should also uninstall old
DAQ drivers and install the latest available for your newest version
of LabVIEW. That will
You cannot set a controls default value wihle the VI is running. Doing
this requires the VI to be recompiled, and that cannot be done while
the VI is running.
The easiest way to do what you want would be to read the controls
value as the VI shuts down and write it to a config file. Then when
the
Although LabVIEW seems to know what version it was previously in, (it
shows this information when you close a VI without saving and it
promts you to save, you can click 'Explain' and it says it was in a
previous version and what that version was) I don't think you can get
that version number
I've seen a few others asking about this same problem with LabVIEW 7
lately. As far as I've been able to figure, the VI has been corrupted.
It acts like it's searching for a sub-vi with the same name as the top
level VI, which you cannot do. The other posts I've read about this
have not found a
This could get confusing quick, but I think I understand how it all
works.
The reentrant property does not affect any callers or callees'. It
strictly on a VI by VI basis.
In your last example, there would be 4 values of 'V', since both C and
S are reentrant, 'M' would call two instances of 'C',
The thing you have remember is that even though there are only two
instances of =91S=92 in the code of =91C=92, there are two instances of =91=
C=92
(if set to reentrant) in the code for =91M=92. So each instance of =91C=92
will have its own data space within =91M=92, and as it loads its subVIs,
I=92ve been tasked to build some VIs to control a Mitsubishi PLC that
controls a Temp/Vibe chamber. The PLC series in question is on the OPC
server support list, so that=92s not an issue.
Since there are only a dozen items that I need to communicate with, I
though I=92d try using Datasockets. The
Not real sure what you are trying to ask here.
If you don't want to use the Unbundle functions, you can get to the
cluster element values using a property node, but the Unbundle
functions are far more efficient and using the property nodes would be
just as annoying if not more so.
I don't think
If you want the action to occur with either the button click or menu
selection, configure the event case to watch for both events by
selecting Edit Events handled by this case, then in the top portion
where you select the 'Event Specifiers', click the plus sign to add
another event for that case.
1. Jack Hamilton wrote up a presentation on how to run a LabVIEW .exe
without installing the runtime engine. This presentation works only on
Windows and does not include NI-DAQ. You can read his presentation a
href=http://forums.lavausergroup.org/index.php?showtopic=122;here/a.
The basics of it is
I'd turn this option off as the others pointed out. It is annoying.
You can also get the Tools palette by holding the 'Shift' key down
while right-clicking. This works on both front panel and block
diagram. This is nice to know if you use the auto tool as it's a quick
way to get to the tool
I think something strange is going on here. Placing the indicators in
the True case and not writing to them when you do not have a match
should leave the last value written displayed. I do this all the time
and have never had this problem.
I dropped a new meter and connected it to the same place
LabVIEW can communicate through the serial port using its VISA
interface. LabVIEW comes with several example serial communication
programs that should help you get started. Look in the Help menu and
click Find Examples After the dialog opens and gets populated,
double click Hardware Input and
The path the custom menu is saved in the VI relative to itself. If you
move the VI, saving to an .llb or building an executable moves it
since the path changes, the VI can no longer find its menu.
You can dynamically build a path the menu by getting the current VI=92s
path and checking to see if
Express VI's were introduced in LabVIEW 7.0. So they cannot be
converted to 6.1 directly.
You MIGHT be able to do it if you first convert the Express node to a
subvi by right clicking and selecting Convert to SubVI, then try to
save that back to 6.1. Depending on what the node does, this may or
I've just run across a possible bug in the Build Text Express VI.
Drop the VI and at first configure an input to accept a numeric by
selecting Number under the Variables Properties section, and check the
=91Use Specified Precision=92 checkbox and set the precision to 4. Then
create a variable
Thanks Luca,
I searched for about an hour last night before posting trying to see
if this had already been reported, but couldn't find anything.
Is there a list of known bugs we can browse?
Ed
As you discovered, the Range and Coercion properties of controls do
not work when used in sub-vis.
Your best option is to go ahead and build your range checking into
your sub-vis. If it=92s something you will be doing a lot, just make
your range checking a sub-vi and drop it where needed. This
Just a guess here, but it could be that your code is taking more than
500ms to execute. The 'Wait' would then have no effect.
The 'Wait' functions start waiting as soon as they have thier value,
not after all the code in the loop has finished executing. So unless
there is data dependency between
OK, so which way is it. I've read various things over the past couple
hours and it seems nobody really knows or can agree what happens here.
The KB artical a
href=http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/12b2ea9ad5b265ad86256257004dd8e2?OpenDocument;here/a
seems to agree
Output values can be handled.
If you're building an array on the For loop, also grab the iteration
count into a shift register when you stop the loop, then you'll know
where in the array it stopped.
Otherwise you fill an array with NAN, empty string or some other
known value so you can tell
Something in the file must have gotten corrupted. It's searching for a
sub vi named Test.vi, but since the top level is named Test.vi,
LabVIEW would not have allowed you have a sub vi with the same name as
the top level, even if they were in different folders and had
different functionallity.
Do
Right click on the Control and navigate to CreateProperty Node. Now
on the newly created node, right click on it where it says Visible and
navigate to PropertiesDescription. This will output a string of the
controls description. Now grow the node by right clicking and
selecting Add Element. On on
Sounds like your counter might be in a While Loop using an initialized
shift register, probably in a sub-vi. If you have a 0 connected to the
left side register outside the loop, everytime the loop runs, it will
reset the register to 0.
There are ways to initialize shift registers inside the loop
It is actually somewhat possible. But not recommended. If you need to
break out of a loop, use a While Loop.
If you're dead set on using a For loop, put a Case structure in the
For loop and put all your code in the False case and leave the True
case empty. Put a shift register on the For loop and
And just to answer your question, the Controls[] property generates
the references in the 'Z' order of the controls on the panel.
So if you really wanted to, you could use the Move to Front, Move
to Back feature and set the order the the references will be
generated. Though I'm sure you'll find
This is an old problem with no easy solution as of now. For a better
description of what is going on here, you can read a
href=http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101RPAGEID=137HOID=5065000500D3370100HTHREAD=79827UCATEGORY_0=_49_%24_6_UCATEGORY_S=0;this
discussion/a
Never mind, I just figured it out.
Ed
If you have not un-installed the newer version of NI-DAQ, you should
do that first, then try installing the 6.9.1 version.
If you continue to get errors, there's a utility available from NI
that will clean up all references anywhere to NI software so you can
do a clean install. During the
Two things that I can think may be causing it.
Old video drivers or something corrupted in LabVIEW.
Try updating your video card drivers first, if that doesn't help, you
might have to reinstall LabVIEW.
Ed
Grab the attached VI's from my answer on a
href=http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101RPAGEID=137HOID=506500050011450100HTHREAD=83217UCATEGORY_0=_49_%24_6_UCATEGORY_S=0;this/a
discussion. It does what you want, but only works on Windows.
Ed
You're correct that you can only have either Controls or Indicators in
a cluster.
You can operate on individual cluster elements regardless of which
type (control or indicator) they are initially.
Define your cluster with all the elements you need, pass this into
your sub-vi and use either the
When I've seen this happen, it usually turns out to be a timing issue.
With Hilight Execution turned on, the program executes much slower
than it does when running normally.
Try putting some delay between your steps, one at a time to see if
that fixes your problem.
Your ActiveX calls may be
Property Nodes really have nothing to do with Event Structures.
Property Nodes either Read from or Write to the various properties of
the linked control/indicator. Event Structures react to an action from
a control/indicator.
Drop an event structure and a single boolean button inside of it,
It depends on how you want your sub-vis to behave.
Any sub-vi will follow what is set in its execution properties. So if
it=92s set for reentrant operation, it will run that way. If it=92s not
set for reentrant operation, the same instance of the VI will be used
regardless of what is calling it.
One option would be to create a small VI that would create the
directories for you, build this into an executable and include it with
your distribution.
Then in the App builder dialog, on the Installer Settings tab, hit the
Advanced button, check the Run Executable after installation box and
I believe the Student Edition of 7 is fully functional. It adds a tag
in the lower left corner of the windows identifing it as the student
edition.
To be sure, you should call NI support and verify.
Ed
Two things you could try.
Drop a property node and set the VI Server Class to 'VI'. Then select
as the property either Front Panel WindowIs Frontmost and create a
false constant for the property or Front Panel WindowState and
create a constant and set it to Minimized.
Run this property node
There are no hidden VI's, but there may be some sub-vi's on your
laptop that are not on your desktop.
These could include any sub-vis you created on you laptop and any
extra LabVIEW toolkits or drivers (NI-DAQ) that you installed on the
laptop.
If it's toolkit or driver VIs that are missing,
Or, if you use the Queue functions a lot, just customize your palette
view to include the Queue menu on the top level of the palette.
At least you'll have less digging to do.
Ed
Edwin O. Dickens - Certified LabVIEW Developer
DISTek
These sub-vis are part of the NI-DAQ driver install. Either you have
not yet installed NI-DAQ or they have been deleted.
You can download the currnet NI-DAQ a
href=http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C128D?opendocumentnode=132060_US;here/a
for all OS's.
Ed
Hello all,
I was wondering if anybody has used a NI-CAN PCMCIA card in a PCMCIA to PCI adapter,
and what brands would you recommend.
Thanks
Ed
67 matches
Mail list logo
