Aitor Solar

QUOTE(Felipelc @ Jan 15 2008, 07:12 PM)

It's posible to have two colors 'themes' (buttons, graphs, text) in one VI, and select one of them with a selector or by an event detector?

Yes, though is not immediate. When the user selects the new color set, you'll have to change the colors of all the affected elements through property nodes.

Saludos,

Aitor

QUOTE(guruthilak@yahoo.com @ Jan 8 2008, 05:16 AM)

Any other way of doing it other than importing from LV 7.X

As already said, here you'll find a couple of tools: http://forums.lavag.org/Scripting-Workbench-Beta-t9518.html

Saludos,

Aitor

QUOTE(Saverio @ Jan 4 2008, 05:23 PM)

Does changing it by means of a hex editor count? 'Cause that's how I did it.

Did you changed the code of a .vi file? And doesn't LabVIEW return something as "corrupt VI" or similar?

Saludos,

Aitor

QUOTE(tcplomp @ Dec 19 2007, 10:53 AM)

it is installed by the OpenG 'Additional Application Control' package.

Well, the "Open VI Object Reference" function is inside LabVIEW, though is not shown in the palette. That OpenG package "just" gives an easy way of placing it in the block diagram .

Saludos,

Aitor

Yes, it seems you have to access specifically through the container pane:

Maybe it's easier to access to it through the block diagram:

Both work.

Saludos,

Aitor

QUOTE(Gavin Burnell @ Dec 15 2007, 02:50 PM)

I couldn't work out how to probe the incoming vi reference to work out the pattern of the connector pane and the types of controls connected - I had thought that if I had a strict vi reference I could do this at scripting time, but no it doesn't seem possible

Of course it's possible, my XNode does it:

Download File:post-1450-1198053874.avi

But when you have a strict VI reference the VI is reserved, so you usually can't use the run method (more tricks needed to do it), and so the XNode usefulness is reduced, hence I didn't mention this possibility.

QUOTE(Gavin Burnell @ Dec 15 2007, 02:50 PM)

Not now, it has a lot of dependencies . But I can pass it to test, send me a message if you want.

Saludos,

Aitor

QUOTE(Gustavo Fernandes @ Dec 18 2007, 04:30 PM)

I have not enough knowledge to do that. I'll look around trying to find an example. I'll be happy if someone can point me a good example or tutorial. TiA.

Search for "COM Builder" in the MathWorks site, there are a lot of examples, and for modern versions look into the .NET Builder: http://www.mathworks.com/products/netbuilder/

Saludos,

Aitor

What Tomi said, maybe you're using a non-creatable object. You can also generate your own COM object from Matlab to encapsulate the methods you want to use from LabVIEW.

Saludos,

Aitor

QUOTE(phuzionz @ Dec 18 2007, 09:54 AM)

Is it possible to programmaticaly assign a name to a case structure.

For example: Ik want to add a case with the name of an input string value.

Do you mean this?

http://lavag.org/old_files/monthly_12_2007/post-1450-1197971757.jpg' target="_blank">

EDIT: Oh, programmatically. That would be scripting, try the "Add Frame" method and the "Frame Names" property for CaseStructure class.

Saludos,

Aitor

I also prefer the first method (call me traditional ). To avoid the necesity of writing down the controls' names (so error-prone), I have developed an XNode to manage the Set Value and Get Value methods automatically. Visually is similar to the Call-By-Reference function, and you can easily drag a VI or browse to the desired VI:

The XNode's generated code just gets and sets the connected values:

Next step is to automatically update the XNode pattern when the referenced VI changes, but Aristos warning about linker functions has frightened me .

Saludos,

Aitor

3D Picture Control just doesn't work in remote panels. The screen remains black and nothing is shown.

CAR 46F27J15

Saludos,

Aitor

QUOTE(Tomi Maila @ Dec 1 2007, 11:22 PM)

Hint: The solution can be found from the dark side.

I think you are triying to do this, don't you? This avoids the "VI is not in a state compatible with this operation" error.

http://lavag.org/old_files/monthly_12_2007/post-1450-1196669259.jpg' target="_blank">

Saludos,

Aitor

QUOTE(Tomi Maila @ Nov 30 2007, 03:25 PM)

What's wrong with this video?

Maybe you are using the Fake Execution State method?

Saludos,

Aitor

QUOTE(Phantom Lord @ Nov 20 2007, 01:35 PM)

But then comes the big problem: There will be a motion to the next point and a measurement starts again, thats because I can't step

out of the while loop.

Create a local and test it in every iteration. See the attached VI.

Saludos,

Aitor

I addition to what Ton said, in the code you're not breaking the inner while loops. I'm not sure what's your goal, so:

1) If you want to check from an inner loop if the stop button have been pressed, you can use a local.

2) If you want to check from a running subVI if the stop button have been pressed, you can use the reference, but is probably better to implement some kind of communication as queues.

Hope that helps.

Saludos,

Aitor

QUOTE(tcplomp @ Nov 20 2007, 11:19 AM)

Right click an instance -> Open Polymorphic VI

<ctrl-I> -> Documentation

All right, is a shortcut to File -> VI Properties. You know, I always use a right-click on the VI icon and then "VI properties" and that doesn't work with polymorphics.

Thanks, Ton. I fell stupid now

Saludos,

Aitor

The stop command should be detected even if there are subVIs (but the loop won't stop till the end of the iteration). Could you post the code, in a simplified form?

BTW, in LV85 you can stop a for-loop too.

Saludos,

Aitor

Adding a description to a polymorphic VI should be obvious but... well... I can't find it.

I've been doing it through the poly VI reference, but sure there is an easier way, isn't it?

Saludos,

Aitor

QUOTE(M.M.K @ Nov 18 2007, 10:47 AM)

The output dose not reaches the Max. value

Because i goes from 0 to N-1, so your last iteration output is MAX - INC. Add a +1 to the N or to the i. Keep also in mind that you are casting a double to an int when you set the N value; you have no guarantee the selected increment can reach the max value (for example, if MIN=0, MAX=1 and Increment=0.3, you won't reach 1 but 0.9 or 1.2, depending on the N value).

Saludos,

Aitor

QUOTE(Michael_Aivaliotis @ Nov 15 2007, 09:49 AM)

I guess that makes 2 in the special "required outputs" club.

But I'm afraid you are still alone in the "detachable node" club .

I was going to explain how I did it, but I don't want to take away your well-earned NIweek beers .

Saludos,

Aitor

QUOTE(martin@aerodynamics @ Nov 14 2007, 12:30 PM)

Error 1077 is usually associated to a wrong property name. Are you sure all the German names you put are correct?

QUOTE(Tomi Maila @ Nov 14 2007, 03:13 PM)

Yes, the search capability should be heavily improved. I like the approach of your tool, though I still like a global search function because sometimes you just don't know where to look.

I also left out the possibility of creating constants, something your tool has. It was for the sake of simplicity, since you can create a constant from any property ot method, but in fact the question is more complicated if we include strict constants. It happens some classes (like the Vision Image Display) are in fact a strict sub-type of another class, allowing properties and methods the original (un-strict) class doesn't have. But for now I don't see the point of digging that way.

QUOTE(Tomi Maila @ Nov 14 2007, 03:13 PM)

Umm, do you mean the tool should automatically find all the possible classes, properties and methods? I'm afraid that's not an easy task and is far beyond the scope of this simple tool. Generation of the classes tree can be automatic (and fast) through scripting, but usually crashes labview. Finding the correct properties and methods names is more difficult and I prefer not to elaborate on that. I don't know if you have find an immediate way for recovering all that info, I haven't .

QUOTE(Tomi Maila @ Nov 14 2007, 03:13 PM)

Well, the startup seems really fast for me but, I have understood correctly, with the approach you propose, for adding or changing a property would be necessary to open the VI, change the value and making it the default value. I thing the txt files are much more versatile and user-configurable.

Saludos,

Aitor

Well, well, well, it seems really easy when you know how

Saludos,

Aitor

QUOTE(martin@aerodynamics @ Nov 13 2007, 10:39 AM)

Saludo

The tool looks verry vell!

Unfortunately I can't create a single property, since I'm using LabVIEW German, and all the Properties have different names...

I tried to edit the txt file and entered the german names but i still get the error 1113...

Umm. Open "update property.vi" and "update method.vi" and change the "VI Server:" text in both, since probably is also different in German. Follow the image guideline:

http://lavag.org/old_files/monthly_11_2007/post-1450-1194956768.jpg' target="_blank">

Saludos,

Aitor

QUOTE(dannyt @ Nov 12 2007, 01:07 PM)

It is possible for you to post LabVIEW 8.2 or 8.2.1 version please

Sure, here it is, try it. Keep in mind that this just replaces the llb, you'll still need the directories provided with the first zip.

Saludos,

Aitor

As requested, here is this simple tool intended for providing an easy way of calling properties and methods. I thinks it's pretty intuitive and works as other similar applications. Select the LV version, the class and the desired properties or method. Press "copy" to have the function in the clipboard and paste it in a block diagram.

Known issues:

• The description box doesn't show anything, because I haven't found a way of programmatically retrieving it. Any idea will be welcome.
  
• Some properties can't be created this way. For example, try Generic -> Owner and you'll see the deprecated property is created instead.
  
• Maybe not all properties and methods are included and can be some repeated. You can play with the txt files to add and try ned props/meths.
  
• The search capability was added as an afterthought and I would prefer to have it better integrated. But still useful.
  

Please tell me any improvement or idea you get.

Saludos,

Aitor