Ton Plomp

Hi!

I am beginner with LV. I want to know the difference between a "Value" Property Node of an indicator (integer, double or other) and a local variable pointing on this same indicator. Is there a difference in terms of performance??

Is there one solution to prefer??

Well cocowk,

very good question for a beginner. I'm not sure how much is the difference but if you dig into the NI Forums you will find major discussions on this issue.

For a quick start you could measure it yourself. Write 10000 times to a local and 10000 times to a property node and measure the time in between.

Ton

In several of my programs I use the name of a typedef as an identifier.

Since LV 7, there's an option (which is default ON):

"Disconnect type definitions and remove unused polmorphic VI instances"

When building an application (as small as possible), I only want to choose

for the removal of the unused polymorphic VI's

but I DON'T want to disconnect my typedefs.

So why is this one option in stead of two ...

I was last day with a NI tech-rep and he replied that this option is added for backwards compatibility. I think you'll have to replace the polymorphic VI's by the actual subVI's. One method i can think off is to make a source distribution where you have the option activated and then reconnect the typedef....

Which of the two is the best for you is up to you..

Ton

Sorry Id2x,

i've stumbled upon this earlier. You could select it with the FPGA-toolkit.

Ton

In fact , I don't know my problems is falling into which category. ^^"""

Well Carman what is the problem?

What are you trying to do?

That said:

You don't need the sequence structure, the data-flow will force the VI's to execute from left to right.

Secondly if you get unexpected results, connect the error out of the first VI (DIG-Line) to the seconed one (group config)

Also read the error status from the VI in the while loop, invert this and OR it with the switch and connect that to the loop condition (the green arrow).

Now the loop will end when the VI produces an error AND the switch is false (note that you've selected continue if true, this makes the loop run if the switch is true)

Stop if true is better IMHO. In that case you can OR the error state and the switch

Ton

hi , i

Well, they just stole NI's idea!

This is quite a year:

NI 30

LV 20

Apple 30:

Apple 30 Years

This one tricked me...

Ton

The grey colour also appears in Get Image.

Additioanally, setting the background colour of stacked charts isn't reliable. I can't make them all transparent, looks like a drawing problem. The part hidden by a pop-up window (tooolbox or so) while by transparent, but an update of the panel makes it grey again.

Ton

I'll hope to check this today with 8.0.1

Not fixed in 801

Hello All,

I'm trying to store some info in a control in a VI. But I don't want to risk the 'Reintialize values to default'. So i was digging the control methods to make the current value default. I can't find it, the only 'Make current values default' item is located in the VI-class were ALL controls are saved

So is this possible? and which class should I use.

Moreover, how te create a new control in LV8, in LV7 I used the get contorl [sIC] from type descriptor.. but this currently returns an array with the type descpriters in it...... :thumbdown:

Ton

Issue 1 solved: there is a PROPERTY Default Value....

Hi there,

while running a timed loop I would like to change its mode by wiring a mode enum control into the RHS data node of the Timed Loop. The Timed Loop does not seem to change its behaviour (let alone report the new mode) when I do this. Any ideas why?

thanks

Peter Badcock

Product Development

ResMed Ltd.

I've had no problem running you're example (8.0.1), the only thing you have to remind is that you can't initialize with 'no change' setting this kills you're loop BEFORE the first run. (error -820)

Ton

Well today I can add an attachements.... aaahhhh who needs proxies anyway??

Ton

Download File:post-2399-1142321884.vi

maybe the project duplicator tool helps ?

Post#2432

Tested it, (at work where i can't post) and forgot to take the VI home...

But the good news is, it works. You can create a new project:

Use the 'new' method of the application->project class

With the new reference you can do a lot of things. Only I haven't tested the creation of a build, I think this takes a LOT of settings...

Together with i2dx's tool it should be very interesting,

if I remember it tomorrow afternoon I wil post the code tomorrow

Ton

I don't see any way to do it from LabVIEW, although the project file is just an XML file (try opening one up in a text editor), so you could certainly dynamically create one using LabVIEW itself.

I THINK you can do it from LabVIEW, I can't check it at home, but I recall that the new VI-Server has references (with methods and properties) for Project Items. I was thinking about this since it would equalize the project settings between the different LV-programmers at our site.

You should be carefull with the XML files

The .lvlib files (Also coded in XML) have some binary info with them as my co-worker found out...

If I get it working (Scripting Projects) I will share (some of) my code!

Ton

FYI, confirmed by NI within the last week, and are unique to LV8:

1. Background color of VI's and Clusters do not show up in Print/Print preview. Everything comes out grey.

....

The grey colour also appears in Get Image.

Additioanally, setting the background colour of stacked charts isn't reliable. I can't make them all transparent, looks like a drawing problem. The part hidden by a pop-up window (tooolbox or so) while by transparent, but an update of the panel makes it grey again.

Ton

I'll hope to check this today with 8.0.1

Hello Daniel,

an abvious? one would be a template VI with the discription with the info you edited. This would implement that for each comment you need another subVI...

Another thing could be a discription added to some data, so that if you hover the corresponding wire the info pops up.

both solutions give the data in the instant help window.

Ton

Yeah I noticed them... unfortunately it means re-doing a lot of my code :headbang:

Has anyone found a workaround for trying to unflatten a null string into a cluster datatype so the cluster is empty? The unflatten function now yields error 42 (generic error), which I suppose can be ignored, but that may be a bit cumbersome.

What do you mean by a null-string? A zero length string?

And what type of cluster do you have. Does it include a string (where length information is stored with the data)

Success Ton