Add multiple TermChar properties in property node

Hello all
I am communicating to a device via RS232 and most of the responses are terminated with a <CRLF>. but some of the commands are not terminated. Can i use multiple termination char properties in the property node ?
- James
Using LV 2012 on Windows 7 64 bit

Usually, I set the termination settings before reading each command. If
the command is terminated with <CRLF> then set the termchar to
<LF> before reading the reply. Make a Read VI that will set or
not the termchar according to a boolean input.
Message Edité par Jean-Pierre Drolet le 07-19-2005 08:44 PM
LabVIEW, C'est LabVIEW
Attachments:
termchar.gif ‏6 KB

Similar Messages

Add Intellisense support to the property node

I really hate having to dig through a long hierarchy of menus when I know what I want:
Visual Studio (and other MS and non-MS products) have a feature called Intellisense, which is meant to make this easier. Basically, as you type, it pops up a list of matching objects, based on context, so you can quickly select what you want:
It would be nice if LV had a similar feature - click on a property in the property node using the text tool (or Ctrl+click if using the auto-tool) and now you can type in the property name and you will get an Intellisense-like pop-up, which will have all the relevant properties.
Specific features it could have:
It should know all the relevant names - full names with the hierarchy (Boolean Text.Font.Color), long names (Mechanical Action) and short names (MechAction). This could probably be similar to how Quick Drop handles shortcuts or they could simply appear as separate items.
It should be context sensitive. If the class is Boolean, then there's no need to have Listbox properties in the list.
It should match all the properties which include the search string (so "in" on a boolean would match both "Indicator" and "Strings[]") and only them.
It should have the ability to use caps for acronyms (e.g. in the above screenshot you could use "BT" instead of "Boolean Text", similar to what appears in this video).
It could probably also work on the invoke node, although there it's less needed.
It could probably also be used to quickly select a class if you have a class specifier using the same basic mechanism.
This example (LV 2009) shows how useful this could be. You don't need anything installed. Just run the VI and start changing properties.
Caveats:
It will only work on the last property in the node.
It doesn't have the proper list of names and it doesn't implement all the features in the idea, as this is just a basic example.
Note - this is similar to this idea, but I think that it's much more usable. Also note that the second idea refers to a QDKS which ships with 2010, but that is far from perfect.

Here's a more detailed response.
Browser:
Click Ctrl+Shift+B.
Get a new window. Great. Just lost a little bit of focus on what I was doing.
Find the search button. Oh, there it is. It's that little button.
Oh, another window popped up. What did I want? ... ... ... Ah, yes. It was that property.
Search for it. OK, that was easy. Now Enter.
Oh, I'm back to the original browser window, but the property is highlighted.
OK, so now I can drag the property into the BD and get a new property node with that property, but that's not actually what I wanted. I wanted to set a property on an existing node.
So, to summarize: A key combo, some mouse activity, 3 window changes and we still didn't get what we want.
Compare that to:
Ctrl+Click on the property you want to replace.
Start typing.
The intellisense popup appears as part of the current window, already navigable with the up and down keys.
Press Enter.
And two additional points:
Imagine working in VS without intellisense. What if you had to use something similar to the browser (or the menu hierarchy) every single time you wanted to get a property?
You encourage people to work with LV classes. Property nodes offer a productivity enhancement when working with classes and this offers another one, so you not only not be questioning it. You should be evangalizing it.
And for those who survived this far, a bonus. This example (LV 2009) shows how useful this could be. You don't need anything installed. Just run the VI and start changing properties.
Caveats:
It will only work on the last property in the node.
It doesn't have the proper list of names and it doesn't implement all the features in the idea, as this is just a basic example.

Symbole für..... - Modify the project properties using "Property Node"??

Hi,
I try to configure automatically the "Symbole für bedingte Deaktivierung" for a project.I have no idea how to translate it. I've attached a screenshot.
I used the reference for Application -> Project.ActiveProject -> .. I found the Name, Path, Description of the project, but I cannot find these 3 values (from the screenshot).
I got lost because most of the Properties are in English and my LabView is in German.
1. Can anyone translate (or make a screenshot) from a English Version - LabView for "Symbole" and "Symbole für bedingte Deaktivierung" window. I'm sure this is going to help me?
2. It would be even better if someone could tell me directly which property must be modified in order to modify the "Symbole".
Thanks,
Paul
Solved!
Go to Solution.
Attachments:
deutsch.JPG ‏54 KB

Although you already solved your problem, here the screenshot your requested.
Regards,
Manuel
Attachments:
Conditional Disable Symbols.png ‏50 KB

How to set property nodes for each of the multiple y-axes?

In Labview 6i, I have set up multiple y-axes on an xy graph. I want to change certain properties of each of the 2 y-axes independently. I believe I can do this using "property node".
However, after I have created a property node for the xy graph, I realised that there is only 1 y-axis selectable from the list of properties. How can I set the property of the other y-axis then?
Thanks for the help!

I believe there is a property called "active graph"... this allows you to
select the active graph to apply the property changes to...
Later...
meng118230 wrote in message
news:[email protected]..
> In Labview 6i, I have set up multiple y-axes on an xy graph. I want to
> change certain properties of each of the 2 y-axes independently. I
> believe I can do this using "property node".
>
> However, after I have created a property node for the xy graph, I
> realised that there is only 1 y-axis selectable from the list of
> properties. How can I set the property of the other y-axis then?
>
> Thanks for the help!

How to add context help text to a property node of an XControl?

Hi
anyone knows how to add description for a property node of an XControl which should appear in the context help window of LV?
In case of a method, the description of the method VI appears on the context help. But not for property node
Solved!
Go to Solution.

Hi Vsh,
You can set the property context help by right-clicking the xcontrol in your Project Explorer, selecting Properties, selecting the "Item Settings" category and clicking on the Property that you wish to write context help for. You will see a box titled "Description" on the right; this is where the context help is defined.
Let me know if you have trouble finding this.
Eric V
National Instruments
Applications Engineer
Certified LabVIEW Associate Developer
"I'm a Ramblin' Wreck from Georgia Tech and a helluva (NI Applications) Engineer!"

Using One Property Node For Multiple Controls/Indicators

Question for all you LabVIEW gurus. Is there a way to create 1 property node that is used for multiple indicators? For example, if I wanted to display the same value on 10 different indicators using the property node - value function do I need to create 10 separate property node-value instances for each indicator? Or is there a way to tie all of those indicators to only one property node?
Thanks!
Solved!
Go to Solution.

Hi hobby1
You could create a cluster, and inside in it put all the indicators, see the image attached
Attachments:
capture1.JPG ‏14 KB

Multiple property nodes

Hi,
I have about 10 or so numeric indicators that I modify their properties so I can change the background colors etc. The problem is, these indicators are not bundled or anything, so I bascally have 10 different property nodes that I have to wire and it looks bad in the block diagram. I was wondering if there is a way to bundle only the property nodes in the block diagram and apply the changes directly to the bundle so my code would be cleaner. Hope my question is clear enough. BTW, the changes made to every indicator property nodes are the same.
Thanks
Yohan

Attached is a vi and an image of the block diagram.
Edit: The VI will not run as is, you need to wire something to the property node in order for it to run.
Message Edited by Novatron on 06-23-2006 09:21 AM
Message Edited by Novatron on 06-23-2006 09:22 AM
Attachments:
Properties.vi ‏11 KB
Properties.jpg ‏55 KB

Property node for a chart with multiple axes

I have created a chart with two y axes, one for each of two data sets
that I am plotting. From the front panel, I can view the properties of
the chart and adjust the scales of the two axes separately under the
Scales tab. I need to, though, adjust the maximum and minimum of these
axes programmatically. How can I create a property node that refers to
one of the two y axes, and how can I specify which axis the node is
referring to? If create a generic YScale:Minimum property node, I get
an error.
Thanks for the help,
TJR

"...YScale:Minimum property node, I get an error."
That is curious.
You can specify the active scale for which the property will be applied.
The attached demo (in LV 7.1) illustrates how to do this by fist setting the index of the active scale and then updating its property (property nodes execute from top to bottom).
What error do you get?
Ben
Message Edited by Ben on 11-30-2005 08:07 PM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Attachments:
Set Active Scale.vi ‏27 KB
Set Active Scale.JPG ‏18 KB

Use of multiple property nodes for GUI manipulation

I have a LabVIEW 6.0.2 application where I'm using 14 different property nodes in the main loop. All of these have to do with GUI - hiding buttons when "X" isn't pressed, disabling and greying out controls if <0, popping one button on top of another depending on the mode of operation, etc, etc. While this works fine, the program is getting slow. I've noticed that using the old 2-D buttons works faster - things update faster and redraw quicker. However, more to the point, I once read that if you have to use a lot of Property Nodes like this, that you should bundle them into a sub-vi, thus replacing what would be Property Nodes with references. How does that make it faster?
Richard

Not sure if bundling them into a sub-vi by itself would make it faster. The nodes in the sub-vi would still have to access the user interface thread, and that's where the slow down comes from.
When I use any property node, I put it in a case structure and only write to it when needed. You just need to be able to detect when the value being written is changed from last loop iteration. It's useless to constantly rewrite the same value (doesn't have to be the "value" property) to the node.
Bundle them into a sub-vi and put the change detector, case structure and nodes in the sub-vi, this should help speed things up a bit. Assuming of course that the nodes are the slowdown. It may also help clean up the diagram a bit.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Is it possible to add text when using flashing button property node?

I am trying to get a text button that displays TEST to show "running"
when it flashes. I am using a property node for flashing.
At present it cycles between TEST and default color which is set in
flashing clolor options.

hi there,
use the "Strings[4]" property of the button. right click on the property node and see online doc for more information about the meanings of the 4 elements of strings[4].
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Performance penalty with property nodes?

In a specific application I have a front panel with three combo boxes and another three string indicators. Based on the selections made in the combo boxes, various messages will have to be displayed in the string displays. This naturally calls for multiple instances in the same VI where the combo boxes will have to be read and string display updates.
One choice would have been local variables ( of combo boxes & string indicators ) for passing the values around. But since this is going to make several copies and hit performance, I decided to use property nodes. And it works fine.
The question is, whether excessive use of property nodes has any adverse effect on performance ?
Thanks
Raghunathan
Raghunathan
LV2012 to Automate Hydraulic Test rigs.

Thanks! I would suggest to just do the experiment.
The attached little demo (LabVIEW 7.1) does the same thing (increment a I32 variable in a loop) in three different ways:
-- shift register
-- local variable
-- value properties
On my slow laptop, 10000 iterations take the following total time in ms.
shift registers: 3ms
Local variables: 5ms
Value Properties: 1891ms (!!)
Notice that the shift register solution would be much faster (more than 10x (or 1000000 in 20ms)) if the indicator is placed outside the loop, the only thing slowing it down is the update of the indicator.
In conclusion value properties are much more expensive than local variables or shift registers. If you just write once e.g. at the beginning of the program, it does not really matter, but once you do things repetitively in a loop, the costs add up. I always prefer wires because they also make the diagram easy to follow. Local variables break the dataflow and can cause race conditions. They have their limited use, especially in user interface related code. They have no business in pure computations.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
timers.vi ‏47 KB

What is difference between local variable and property node ?

What is difference between local variable and property node ?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview

To make things clear, here are two small examples that show how nasty locals and value properties can be to the naive programmer.
- Open the diagram of the race condition.vi before running it and try to predict what will be the values of the two counters after the third run.
- Use the Compare Locals Properties and Wires.vi to find out how slow locals and value properties can be (times 1000+).
This being demonstrated, I must add that I use globals and value properties quite often, because they are often very convenient
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Race condition.vi ‏9 KB
Compare Locals Properties and Wires.vi ‏18 KB

How can I make a "property node" for a VI?

Hello!
If I add a boolean button on the FP then I am able to make a property node for that button in the Block Diagram. But how can I make a property node for a VI? I have several VI:s an that together is one program. What I need to do is to verify what kind of VI some of my VI:s is. I need to verify if it is .exe or .vi-file, and if it is .exe then I want to disable run, abort, run continuously bottons otherwise not. I have hard that this is possible to do programmaticaly but I can´t figure out how. I am aware that I could do that manually in the File->vi properties->customize->windows appearance but theese choises makes it last forever.
I want to be able to stop and run and everything if it is a .vi file, but if it is .exe-file then all those buttons should be disabled.
Anyone have an example on this?
In an other message at this Forum I read "You can use the `Front Panel Window. Allow Runtime PopUp`" property to disable run-time shortcuts menues programmaticaly, but still I dont know how to create this property node.
/Amir

You really shouldn't open a new thread. If you don't understand something, ask and we will explain it.
Like I said in the other thread, you can check if you are running in LV or an EXE by using the Application>>Kind property. To get it, place a property node (from the Application Control palette) on the diagram, click it and find the property.
To set the properties for the VI, place another property node, right click it and select Select Class>>VI Server>>VI. You should have the properties you want under Front Panel Window.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here and here are a couple you can start with. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf). I believe chapter 17 of the user manual explains about programmatic control of VIs.
Try to take over the world!

Property Node in VI throws Error 7 in LV 7.1 but runs OK in LV80 and LV86

Hi everybody
I build a custom IVI instrument driver and using the LV tool <Generate VI Interface from Instrumnet CVI Driver> I was able to get a LV wrapper for each driver method. From LV86 I saved first in LV80 and from LV80 I saved as LV71. I have all these LV versions on installed on my PC.
I have no trouble in using these LV wrappers in any of these LV versions as they work OK.
Now my IVI driver has also Properties that the Import Driver Tool does not convert as a wrapper and for that reason I had to create a Property Node Warpper myself and saved in the same LLB under LV/instr.lib folder.
Once I have all these method wrappers and the property node wrappers I made a small VI
1. Initialize IVI With Options on a TCPIP instrument
2. Set-Get an IVI Timeout property
3 Close IVI driver on TCPIP instrument.
Good part is that in LV 86 and in LV 80 the VI is running fine when I use these LV version wrappers from their coresponding instr.lib folder.
As soon as I am going to use the LV 71 wrappers in LV 71 I could create the same small VI to Set/Get Timeout and the VI look OK nothing is broken but when I run it the Initialization is OK but as soon as is reaching the Timeout Set Property Node gets out an Error Code 7.
To run this VI the user need to install the jdCMR IVI driver then add the LV71 jdCMR wrappers inside LV71/instr.lib and then he may build any VI using these LV warppers.
The only problem is that the Property Node get out an Error Code 7 and the same error code get out from Property Node if I am picking the Property Node from VISA Advanced Pallette, connect this node to jdCMR driver, set Timeout property inside the node and after connecting the input and output references plus the input and output error to Initialize and Close LV wrappers I still get this error at running time.
The same LV 71 VI if I open in LV80 or in LV 86 runs without any problem?
Does anybody knows why LV 71 is not working the same way as LV80 and LV86 with respect to Property Node?
Btw When I save my VI from LV 80 to LV 71 I get this warning...
IVI Error Message Builder.vi
    Cannot save VI from VI.LIB to previous version.
Merge Errors.vi
    Cannot save VI from VI.LIB to previous version.
Thanks
Sorin

Hi
For further testing of the IVI driver Property Node bug with LabVIEW 7.1 IVI drivers I download and installed two different IVI drivers from two very known instrument companies, Rodhe-Schwarz and Agilent Technologies.
I have to mention that both these companies releasead their IVI NI LabVIEW 7.1 drivers under NI Instrument Driver Network and ready to be installed and used by any customer of these two instruments.
The bug is present only in LabVIEW 7.1 version as if I take the same VI that breaks in LabVIEW 7.1 I could run it without any problem in LabVIEW 8.0 or LabVIEW 8.6 versions.
Anybody could test this bug for these two NI released IVI drivers in simulation in LabVIEW 7.1 by following these links below.
Agilent ag81150ni IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=55798957B1A633BDE0440003BA7CCD...
   Rodhe Schwarz rsngpt IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E91D6659CE034080020E748...
After installation complete close LabVIEW 7.1 if was open, then restart LabVIEW 7.1 and now you may see under the LabVIEW Instrument Driver Palette two new IVI drivers ready to be used as LabVIEW 7.1 wrappers.
Open a new blank VI and from Instrument Driver Palette use two well known Vis that are Initialize With Options.vi and Close.vi add them on your blank VI block diagram and connect thm together. Accept all default parameters except Simulate that must be Simulate=1.
Both Vis run OK in simulation mode without errors. Now pick a Property Node from VISA Advanced Panel and squeeze this between the Initialize With Options VI and Close VI and make the instrument reference in-out and error in-out connections.
Now run these two simple Vis in simulation
I run Rodhe Schwarz IVI driver and Property Node passes OK until the end
I run Agilent IVI driver but Property Node is getting out Error Code 7 that is the same as my own driver error.
Both these IVI drivers are under NI Instrument Driver Networks and have been built and integrated as native NI IVI instrument drivers.
Question is why they behave so different with respect to Property Node from the VISA Advanced Panel?
I attached the screen shots as PNG files that show clearly the difference of VISA Property Node behaviour when used under the same circumstances.
Thanks  Sorin
Attachments:
ScreenTestShots.zip ‏152 KB

Xy Graph property node:apply to all plots

I have an xy graph with multiple plots and am using property nodes to give each plot a different color. My problem is that i would like to set the "point style" for every plot to be the same, in other words: create a default point style that differs from the XY graph default.
Cheers
CLA, CLED, CTD,CPI, LabVIEW Champion
Platinum Alliance Partner
Senior Engineer
Using LV 2013, 2012
Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.

You can do this statically on the "Plots" tab of the graph properties dialog box. You can also get a property node to alter this dynamically by right-clicking on the graph and selecting Create >> Property Node >> Plot >> Point Style.
Brian R.
District Sales Manager
Washington DC
National Instruments

Add multiple TermChar properties in property node

Similar Messages

Maybe you are looking for