Albert Geven

this was version 7.1.1, we did not yet try 8.2

rightclick on the output of the loop and disable indexing is what you need. please try to read a book on LV. Jim Krings book covers all this.

Hi Jimi It is possible. We experimented on a WTS and it worked but only 2 people at the time wanted this and after a few weeks it was not used for over a year so we skipped it. Another reason is licensing but that could be overcome with a concurrent licensing scheme. So yes it is possible but you may need some help with the administration and of course no IOcards!

I have added a nice empty vi with an old hp scope icon. Download File:post-175-1167249814.vi

Hi Marcel You could use a virtual machine,to test this out. The normal VMware players connect also the usb ports of your local machine so by copying a player from the VMware website you can create a Virtual Machine inside your development machine for quick testing. have a "goed rutsch" into 2007

The reason possibly is that your session has been closed, or that you are running a subvi without filling in the visa resource name. It happens to me all the time. Also there is an option in LabVIEW to automatically close all open session. In LV8.2 this is in the options\environment tab. Switch it off.

Are you using an ethernet hub or a crosscable? otherwise your computer and spectrum analyzer are talking on the same wire and both listening on the other wires. and that means no communication

Rob Thanks for this history, I really like it. It also shows that users can influence NI, especially in the early days. Has someone a more recent implementation of these 7400 chips in LabVIEW I would like to show it to some teachers that did an awful implementation of a flipflop.

I have the strong feeling that 8.2 solves many of the 8.01 problems and adds some new ones. look in the 8.2 buglist I would not yet advise upgrading from 7.1.1 to 8.2 if you don't need the new stuff but I will advise to upgrade from 8.01 to 8.2 The only thing that gets hinders us is that we need an installation of the runtime environment before we can run any 8.2 program. So we keep our LabVIEW installer program written in LabVIEW in a lower version.

We benchmarked some simple to variant and from variant operations for float,bool,string and the improvement is about 50 times as fast (lv7.1.1 compared with lv8.2)

Hi a coworker just uploaded a rather different implementation of the sqlite wrapper to: http://community.ni.com/examples/sqlite-wrapper-for-labview/ suggestions?

Hi Michael As one of the beta testers I'm now free to talk about the next (since may 1) The NXT in fact it is more like labview embedded. This one really compiles to the ARM processor. I've seen nice things with blue tooth phones and next last weekend. The phone controls the programs in the nxt and the nxt orders the phone to take a picture ! I really like it, even want to built robots with it. ps. what age is your son, my youngest is 19 so I'm glad I could betattest.......

I tried to build a growing arrow with the picture controltoolkit and succeeded, but found an interesting blob at the end of a vertical line. simply draw a line with thicknes 5 and the end will have a blob in the positive x direction. not a big one but you can see it. I changed my arrow drawing algoritme to line thickness 1 and fill but could not resist to ask if this is my windows that generates the problem or a bug in the picture control toolkit Anyhow it is the same in lv8.01 attached is a simple vi to show the blob(I guess that the line is extended with one extra positive x pixel. Download File:post-175-1144938147.vi

when plotting data from a 10 second data fetch and plotting with loose fit enabled. I get an x-axis of 1 hour and 10 seconds. (local time Greenwich -1) If I change the timezone to Greenwich the loose fit works Ok This did work correctly in 7.1

Activation did not work, but the Netherlands support team send us a 90 day registration ID and that worked

Great powerpoint presentation Because I missed the show, I'm glad I did not have to wait for the NI-week CD for this. Yes this is exactly what I think developers need to fix up an already good product. I guess that cleaning up example code, writing real programming books on LabVIEW and keeping a keen eye on the failures can move LabVIEW ahead of other languages. keep on going Rob

Hi C++ is just another dialect of C sometimes worse to read but essentially the same. The only problem for LabVIEW is the name mangling used is C++++ function calls to make overloading of names by the programmer possible. Export your externally needed functions in c-style and you can call from LabVIEW. But.. in fact the advise from Michael (writing in LabVIEw) is an even better response.

just look at my post on the subpanel update bug, I forgot to post it http://forums.lavausergroup.org/index.php?showtopic=1634

When updating the subpanel you need to force an update otherwise the redraw is missed. I noticed this when loading front panels that were shifted a few mm and it looked ok but when you pressed a button, nothing happened. It appeared to be that the actual button was a few mm shifted from the drawing. by forcing a redraw (minimising and opening again, or by hiding the front panel with another window) the error became clear. In the subvi a redraw is forced by modifying the background color of the transparent background. You don't see it but it helps. Download File:post-175-1123144234.zip

In a relatively complex bundle by name with long names and hide full names activated we stumbled over the following bug. This one is reported to NI but not yet solved. Take a cluster with inside two or more clusters with the same name item. e.g. main cluster not named sub cluster a with element d sub cluster b with element d sub cluster c with element d build a vi with a while loop and a case structure inside use an unitialized shiftreg and in the false case feed the rightside shiftreg with a constant cluster. in the true case unbundle the shiftreg say element a bundle the output of this unbundle with the original shiftreg wire and select cluster b to be updated by a use the output of this bundle to bundle again but now select c.d to be updated with a constant. If you succeed in selecting c.d (and the editor does not change it back to a.c) you don't have a bug but I do. a simple workaround is no to select the element directly but to use an extra unbundle. our problem was not seeing what happened because of the hide full names selection ! NI has confirmed this a bug and will find a fix. Albert Download File:post-175-1098973277.vi