Wolfram

I can't confirm. I do get a valid refnum out. I tested this on LV 8.0.1 & 8.2. Maybe it is an issue on LV 8.0. Wolfram

Hi all, does anybody know something about the internal error: #### #Date: Tue, Aug 15, 2006 10:09:46 PM #OSName: Windows NT #OSVers: 5.1 #AppName: LabVIEW #Version: 8.2 #AppKind: FDS #AppModDate: 07/27/2006 11:08 GMT .\manager\ThEvent.cpp(152) : DAbort: $Id: //labview/branches/Europa/dev/source/manager/ThEvent.cpp#4 $ 0x00C8A502 - LabVIEW <unknown> + 0 0x00C8A6B6 - LabVIEW <unknown> + 0 0x00C8A801 - LabVIEW <unknown> + 0 0x00C8AD3F - LabVIEW <unknown> + 0 0x00C8ACCB - LabVIEW <unknown> + 0 0x00C87075 - LabVIEW <unknown> + 0 0x0060508A - LabVIEW <unknown> + 0 0x00616690 - LabVIEW <unknown> + 0 0x004CCB39 - LabVIEW <unknown> + 0 0x0051FE26 - LabVIEW <unknown> + 0 0x0051FD54 - LabVIEW <unknown> + 0 0x0051FD6F - LabVIEW <unknown> + 0 0x0122CA73 - LabVIEW <unknown> + 0 0x7C816FD7 - kernel32 <unknown> + 0 0x00000000 - LabVIEW <unknown> + 0 Wolfram

Here is the direct link: ftp://ftp.ni.com/evaluation/labview/pc/labview_82.exe

Now, the directory is gone. It was just deleted by NI.

If anybody is interested. Here is the download link for "LabVIEW 8.20 anniversary edition": ftp://ftp.ni.com/outgoing/20060704_0205 Readme: ftp://ftp.ni.com/outgoing/20060704_0205/readme.html Have fun Wolfram

http://forums.lavag.org/index.php?showtopi...amp;#entry14161

Try the short cut "Ctrl+M"

I heard about a new LabVIEW Version 8.20 (20 years of existing LabVIEW). Probably coming out at this year's NI Week.

Another small solution. Have fun Wolfram Download File:post-1013-1144705333.vi

There is a way to change the tab captions. See enclosed example. Wolfram Download File:post-1013-1140005841.vi

"invalid Lock State" representing value 0 is just a wildcard with no meaning.

It's better to deinstall LV 8, then install LV 7, subsequently reinstall LV8. In the past, I had no problems with more LV-Versions on 1 System (I have 5 versions in parallel on my system), when the installations were made by the oldest versions first. Wolfram

I suppose there is some private primitive called "New Application Reference" same like the existing "New VI" primitive.

It seems, that only the private special stuff key works. So, up to now, we can use LV 7.1 to progam scripting tools and use LV 8.0 to run them. This could be interesting, especially for those methods and properties that have produced an error message "not yet implemented" when running them with LV7.1.

Hello Michael, the old ini keys seem to work, but not in full. I have written a formula parser in LV7.1 by using the formula node's functionality (see attachment). In LV8, running the formula VI does work, but editing of properties/methods is not possible, since there are no properties and methods availaible to select. There must be some new keys. The known keys will only show some hidden stuff. Other stuff like the scripting features are still not available. Regards Wolfram Download File:post-1013-1130071417.llb

Jonas, there is a start trigger but no stop trigger available. I've attached an example created with DAQmx assistant. The example uses a rising start trigger at PFI0 for starting the data acquisition. Regards Wolfram Download File:post-1013-1129501956.vi

Great debugging challenge...

Use this and have fun. Wolfram Download File:post-1013-1125771079.vi

In case structures, you usually have to enter all included values, if the case structure handles integers. For me, this would be a strange feature, if strings are handled differently. So I think this is a bug.

This is the new G-tunnel programming technique.

Another nice case bug. Download File:post-1013-1124973923.vi

The one case bug with only "False". Download File:post-1013-1124823090.vi

Why don't you upgrade to a newer LabVIEW version?

I suppose in autumn.