Michael Aivaliotis

Thanks, i will try it like this (in the moment it won't hide...)

1371[/snapback]

An easier way is to just right-click on the boolean and create a property node just for the boolean.

BTW, is it possible with a "dialog ring", too?

1371[/snapback]

You can use the Strings array property to specify the number of items.

I like to add 3, 4 or five options more to my radio button but I can't find something in the right click menu. Isn't this possible?

:question:

1355[/snapback]

Yes, this is possible. No right-click required. Just go to your Dialog pallete and select an additional radio button. Drag it over to your radio button area and drop it in. You can drop in as many radio booleans as you require.

I would suggest you perform a search in the forums before posting. This will help you resolve issues faster.

In regards to your question about launching a VI, I suggest you read this post:

How to open a VI within a VI

Ok. No worries, Iv since found an example on 7.1 which shows me exactly how to do it all. Cheers anyway.

Topper99

1354[/snapback]

Which example is that? Could you let us know so others can benefit?

Also, is there a reason why you are using the xy plot with picture control? It's more efficient and easier to use the standard XY graph indicator on the graph pallette.

Do you now an example because after a right click on the node i can't find visible in the properties. :headbang:

1352[/snapback]

Sorry, my English is poor. I try to explain my condition again. There is a example. In my user interface, in special reason I want to put the Numeric 13 under the Numeric 12 on the listbox 2 and use scroll.  The listbox  can accept strings and it can use scroll. Is there have any methods can put the Numeric 13 under the Numeric 12 on the listbox 2 and use scroll?

1335[/snapback]

Ok, I think I got it now. One question, do you absolutely require editing of the numerics? If not, then you can just convert the numbers to strings and feed them into the listbox. If you require editing then a better approach would be to use an array of numerics than a listbox. If you want to have a scrollbar then you can use the technique described here:

Replacing the Array index with a slider.

it should be saved with t_listbox___tab_control_panel.vi in this same directory.

best regards

Mikrobi

1351[/snapback]

Just a suggestion for future posts (for all members). If your code requires related multiple VI's, please include them all inside an *.llb file or a *.zip file. This will help others launch and run your example quicker. :thumbup:

I have to compare two strings. This are only text strings.

1341[/snapback]

 

If you go to the comparison palette, you will see the Equal? function. Pretty self explanatory. If they are the same then boolean is true. Does exact match only.

Well wouldn't you know it. Leave it up to sneaky users like myself to try something like this.

Plop down a Timed Loop. Double-click on the loop to bring up the Loop Configuration Dialog. Click on one of the front panel objects such as "Use Terminal". Now Press ctrl+period on your keyboard (shortcut for abort VI). Voila, the dialog hangs and you cannot get out of it or labview unless you abort the task from windows.

No why would I press ctrl+period? Hmm...

I want add a scale dynamic which means I want add a scale when the program is running, not in edit mode. so do you have a better idea?

1326[/snapback]

It's not possible (yet) to create or remove a scale at

run time. Scales can only be created by right clicking on them and

selecting "duplicate scale". Scales can only be deleted by right clicking on them and

selecting "delete scale". Scales can only be moved to the other side of the plot

window, at edit-time, by right clicking on them and selecting "swap sides"

Scales that exist (have been created at edit time) can be made

visible or hidden at run-time. Once a Scale is made "active" the "YScale.Visible" attribute

is used to show or hide the scale. During run-time, plots can be scaled-to/associated-with scales

that have been created at edit time. Once a Plot is made "active", it can be associated with a

scale using the "Plot.Y Scale Index" attribute.

You must create the scale first at edit time and then use properties to hide it.

how to get the plot area's position property of a wavegraph in labview 7.1, I can only find the size property.

1296[/snapback]

You can't get the plot area position from a property. You can get the entire graph control position but not the plot area. One thing you can do as a work around is to use some simple math to calculate the plot area position if you know the control position. This assumes that the size of the plot area doesn't change relative to the entire control.

Maybe legend->Position->All Elements is what you want?!

1327[/snapback]

No, this only gives you the position of the legend. The plot area is the black box element that shows the graph.

Hmm,

In application builder, have you included a toplevel VI in your Source Files tab?

I think you should be ok with changing the update rate and amplitude on one channel. I haven't done this but a quick search throughout the DAQmx examples in my LV70 shows a method for doing this. The problem may arise when you need to adjust this across multiple channels. I think the NI boards use a common clock source for AO generation and as such will limit you to adjusting the update rate on all channels at once.

Here is an old NI example for sinewave output.

Generating a Continuous Analog Output Waveform

I think you can find a similar one for DAQmx. If you need to change the actual output waveform then you can take a look at the function generator example in your LV. This will allow you to output different waveforms based on a selector. The trick here is that if you have update rate limitations then you can "fool" the AO by changing the actual output data and keep the rate the same.

Well, there are many ways of doing this. It depends on the level of control you require. At the most simplest form is a method called Remote Panels. See a link here with more info:

LabVIEW Remote Panels Tutorial

If this is not sufficient then I can discuss some other methods.

James, your interpretation is as good as mine. I'll give it a shot.

ancle,

You have a small screen resolution and your VI block diagram has limited space? You want to have a scroll mechanism to place multiple VI's in a small diagram area? You can use a sequence structure!

Unless I got it wrong.

There are many ways to do that... one is to play with the button property node ("value")... Download File:post-575-1091712910.vi

1305[/snapback]

If you change the mechanical action as James mentioned, it will be a cleaner solution. It doesn't sound like you need adjustable delay.

I had a lapse of reason -- the VI that I wrote doesn't coerce variants, it strips typedefs.

1287[/snapback]

Ah, that explains the blank stare on my face ... I was thinking "man Jim's really lost me here"... I thought it was just too many beers I had... :beer:

I have a question.  Well, I currently have a cluster containing 9 clusters with 3 of the same elements within each cluster.  My question is without using loops, or extracting each cluster element individually.  Is it possible to grab the first two elements of each cluster.  I was trying to use some array manipulations but it did not work as planned.    Any ideas out there? Thanks in advance..

Vince

1273[/snapback]

Well, as you are discovering, manipulating your data is a real pain in the ######. Correct? That's good. It's good because this is a sure sign that you have chosen the wrong data structure to store your data. Instead of trying to jump through hoops to fit the data mold, why not change the data structure to the easiest form for you to handle... an array! This is why it is a good thing to sit down and think through the data structures you will be using to pass data around your application. if I were you, I would scrap the clusters and go for an array...

I was thinking of testing that VI, but I figured that it would work.  I didn't realize that the coercion only occurs when the output is strictly typed... too bad.  Yes, this would be a non-trivial problem to solve in G.  For now, we'll leave that one for the wishlist, I guess.

1150[/snapback]

Non-trivial but possible. Besides, it's done already in the variant config data tools... not?

Do you mean show what the indicators are displaying?

You can do that by having the front panel of the sub-vi open while running the caller... no?

Well, it's a feedthrough....

The SCC-FT01 is a feedthrough module that connects directly to the analog input (AI) and analog output (AO) channels of a data acquisition (DAQ) device. You can use the breadboard area of the SCC-FT01 to develop custom signal-conditioning circuitry that can connect to and condition any of the analog, digital (P0.), and general-purpose counter/timer (CTR) channels of E Series DAQ devices.

What more can I say?

Yes, go to the Dialog Controls Pallette. That's it.

Also, the Graph you saw is not built into LabVIEW. This is a trick. Someone has taken the traditional box in the graph and replaced it with a box stolen from a button in the Dialog Pallette.

Would saving without the block diagram prevent the user from accidently/intentionally rearanging the front panel icons, or is there a seperate lock command for those?

1255[/snapback]

Actualy, password locking would prevent ANY editing including front panel changes.

If you go to the very last button to the right on the tool bar, (the one that contains "move forward" "group" "ungroup" etc.) There's a selection called "Lock".

Just select all controls that you want to lock in place and go up and select "Lock" and there ya go.

1258[/snapback]

Yes, this is a good option as well. It sounds like you are running LV code on a test system and your operators are aborting the VI or something. When you build your VI, you should design it so it automatically runs on startup and has all the menus and toolbars disabled. If you have to click the RUN button to execute your application then something is wrong.

Yes, this is not obvious at first. Not very intuitive. You have to feed in 2D arrays for both X and Y inputs. You have to define all your data. LabVIEW does not automatically apply the 1D data set to all plots. In your specific case you have to add a build array function on the X data (if it is identical).

What do you want to do with the detected pulse? Are you trying to measure the time between pulses, counting the pulses or just triggering something?

If measurement and counting is the key here then the focus of your attention should be using the counters and the examples in LV surrounding them. Counters are excellent for that.

As far as the DAQ occurences, I see no reason why they shouldn't work actually. However this seems like an backward way of doing it since it fires an occurrence when certain amount of data is acquired not when the pulse arrives. If you look at the help for the DAQ Occurrence Config.vi, you will see an option called: set the occurrence every time the output of the counter specified in the channel string control changes state such that an interrupt is generated. This might work!