gleichman

Maybe this changed for better SCC compatibility?

QUOTE (Xrockyman @ Jul 8 2008, 10:21 AM) You mean like this? Cascading Ring Control Many thanks to Jacemdom for his way cool code. :worship:

QUOTE (crelf @ Jun 5 2008, 05:49 AM) I don't think so. TestStand 4.0 was released in April 2007 and it was the first version of TestStand with undo. I actually implemented my undo command a months earlier. My newest feature is a syntax checker.

QUOTE (crelf @ Jun 4 2008, 03:37 PM) Yeah, there was nothing like an accidental control drag in a 20 deep case structure to make you want to hurt an NI engineer. I've recently implemented "undo" into the sequence editor of my test executive. After living without undo in LabVIEW for so many years, this should have been an obvious feature to add, but it was a user request, not my own idea. - Alan

QUOTE (prads @ May 28 2008, 07:55 PM) I have doubts about your question. You can't insert new data into the middle of an existing text file. If you want to use a text file template, you will have to read it, insert the new data (in memory) and then write it back to disk. You could use unusual characters to mark where text is to be inserted such as ASCII(255).

QUOTE (PaulG. @ Apr 25 2008, 03:08 PM) I have had this problem in 8.5 and 8.5.1. I'd like to see your example where this does not occure. For my project I ended up making two type defs, one for my GUI and one for SubVIs.

I ran your test and I saw similar results. When the wait time was set to 1 ms, the average wait time was close to 2 ms. BUT, "wait until next millisecond multiple" vi is not made for critical timing. At 1 ms it is probably running up against a wall of how fast it can go back and forth between the OS. The wait until vi is like a sleep command that allows the OS to perform other tasks. If you are looking for better timing use the timed loop. I replaced the while loop with a timed loop in your example and I observed a measured time of 1.025ms for a setting of 1.0ms. Download File:post-151-1207831749.vi

QUOTE(fuzzycontrolfreak @ Feb 25 2008, 08:35 AM) That depends. What data are you trying to extract from your signal?

QUOTE(tmunsell @ Feb 14 2008, 01:08 PM) You must learn the ways of data flow. A structure will begin execution when all inputs are available. The outputs of a structure will become available at the completion of all code within the structure. Hence your loops are tied together and will not operate in parallel. To seperate your loops you must remove the data flow dependencies between them. To share information between the loops you can use Queues (preferred), global variables, local variables, or uninitialized shift registers. Alan

Wouldn't it be easier to just go back to the old version stored in source code control server?

It sounds very similar to the "Security System" CLD example.

What were the mirrors for? Did someone back out of the garage too quickly?

You're VI worked for me (WinXP, LV8.2.1). What results were you expecting? QUOTE(pdc @ Dec 14 2007, 01:11 PM)

QUOTE(ajwhi3 @ Dec 11 2007, 05:22 PM) Noooooo! Don't use a property node for updating control data. Just wire your array to the graph and don't do it in a for loop unless you want it animated. If your graph is not showing the data correct (transposed?), look at the help for your control type on how the data should be formatted. -Alan

QUOTE(ajwhi3 @ Dec 10 2007, 06:37 PM) Are you trying to plot one array of values in two different colors where the color indicates the gradient? If so, make a two copies of your array and replace the indicies in the first one with negative gradients with NaNs and in the second array replace the positive gradients with NaNs. NaN = Not a Number which can be typed in directly in a numeric control or constant. - Alan

Making a LabVIEW program into an executable can save some memory. Diagrams and debugging are removed in executables making them slightly more efficient. To create an executable with LabVIEW, you need the application builder which is an add on for FDS and Base. It is included in PDS and the DevSuites. I would not expect significant performance increase with an executable. Why do you assume that your problem is memory? Have you run the LabVIEW memory profiler? What kind of architecture are you using? Are you touching your hardware in more than one place? Some of us EEs right higher level software.

LabVIEW 8.2.1 You can still right click and set the default value in 8.5.

QUOTE(jpdrolet @ Oct 19 2007, 07:13 AM) I do now. School bus yellow and the VI medallion that looked like the new 3D controls. Maybe someone could add the LabVIEW splash screens to the wiki (with Easter egg variations).

QUOTE(JDave @ Oct 18 2007, 03:24 PM) They resisted for version VI. Instead we got the 6.0i. (Would that be VIi?)

There was no bird on head accessory and there was no way to add grey hair. http://forums.lavag.org/index.php?act=attach&type=post&id=6499 My son thought it was cool. http://forums.lavag.org/index.php?act=attach&type=post&id=6500

QUOTE(crelf @ Apr 19 2007, 10:27 AM) It looks like the "generate" product code button disappeared in 8.0 with the new project interface.

QUOTE(Aristos Queue @ Apr 15 2007, 09:52 PM) If, in theory, an easter egg was on the splash screen, how would one best look for it?

I don't think what Chris is saying is true. My example calls a VI that is NOT in the exe. I have down converted it to 8.0. http://forums.lavag.org/index.php?act=attach&type=post&id=5482 QUOTE(ars_stowers @ Apr 12 2007, 01:34 PM)

I still don't understand the problem. You can dynamically call VIs outside of an executable. I've attached a simple example of this. The executable and the dynamic VI share a VI that is located in the exe. Example written in LV8.2.1. http://forums.lavag.org/index.php?act=attach&type=post&id=5481 QUOTE(ars_stowers @ Apr 12 2007, 08:27 AM)

Have you checked with your local sales rep? This is probably just a bug with update advisor. Download the new version and see if your serial number works with it. QUOTE(SciWare @ Apr 12 2007, 06:42 AM)