You need to set two properties to activate the correct cell and then
you can read it's string property.
The positioning properties are the ActiveItemTag and
ActiveColNum properties. With them you select the tree item by it's
tag and the active column. The string can then be read from the Cell
I'm going to start playing with Labview 7 in Linux.
The app I have in mind needs serial I/O and database access, and presently
uses the database toolkit in Windows. Serial seems no problem in Linux but I
assume ODBC may be. The only option I can find from a brief Google is to use
some VIs for
When you build a shared library with LV 7.0, the .h file is
automatcally generated and included in the distribution cab file.
How to replace this .h file with my own .h file?
You wrote, I find it hard to believe that so many instrument did not
really meet the spec
I think you ascribe too much computing intelligence to these
instruments. Many of these devices run a simple homemade operating
system, or better, a commercial single-threaded embedded operating
system.
The strict answer to Why? is because we only implemented the special
initialization code for the Initialize function. autoConnectToFirst
is optional in VPP 3.2, and we chose not to implement it as a special
case.
You'll just need to fix the Call Library Node in your VI wrapper to
use the proper
See my comments in your other posting of the same question, a
href=http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101RPAGEID=135HOID=5065000800A2D4USEARCHCONTEXT_CATEGORY_0=_49_%24_6_USEARCHCONTEXT_CATEGORY_S=0UCATEGORY_0=_49_%24_6_UCATEGORY_S=0;here/a.
Brian
LabVIEW can do VISA and NI-488.2 directly; you don't need C++ or VB.
First of all, you should see if there are instrument drivers available
for your instruments. There are thousands of free drivers available
on http://ni.com/idnet/. Search there first, because if you can find
a driver for any
David,
Create a VI which loads all VIs in that library then ''Save with Options''
selecting the option ''To new location(s) - prompt for each''. You are
then able to save one VI at a time with new names. The resulting .llb will
contain the renamed VIs only.
Hope this helps and happy wireworks
We often have a similar scenario when installing PC based DAQ (including PXI
with Windows) at clients' sites. Usually, the client contact asks us not to
mention certain terms in any of our documentation (eg: PC, Operating System,
PCI Card, etc), and instead call the PC a Data Acquisition
Greg,
Thanks a mill, worked a treat! Also, after unlocking the controls I
could delete them and save the VI without LabVIEW crashing! *Happy
Customer Smile*
OK Brian,
Thanks.
I found one driver only ( for my TEKTRONIX DSA602 ).
No drivers found for my HP 3336B , HP 8922M , HP 8525A , HP 8568B and
others.
In LabView 7 I now see the Instrument I/O Assistant.
I clicked it and it prompts me Please find the VI named I-O
Assistant Block vi .
I
Just like Html pages, if you submit page new page will come. Like that
if i want to do in labview once i submit first vi and if i want to
open new VI by closing first VI ? How I can do? can any one help
thanks
Thanks,
That is exactly what I needed
A code snippet showing the problem has been posted to the Lava User
Group:
http://forums.lavausergroup.org/index.php?showforum=45
Regards
Henrik Molsen
microLEX Systems
Dr. Neergaards Vej 5C
DK-2970 Hoersholm
Denmark
Tel: +45-45 76 21 00
Fax: +45-45 76 22 00
Email: [EMAIL PROTECTED]
WEB:
David,
Just open all your VI's of this LLB which use the VI you want to rename.
Then open VI (you want to rename) and save it using save as... menu item.
Make sure that in the file dialog box the checkbox save a copy without
updating caller (or similar, I have a german OS and have to translate
15 matches
Mail list logo