"find control" highlights the entire front panel

I have inherited a mid-size state-machine and am in the process of documenting it. If I double click a control on the FP, it takes me right to the item in the BD.
Conversely, If I double click (or right click --> find control) in the BD, it takes me to the FP and the entire thing is highlighted / found.
The entire FP is built on tabs.
Many of the controls / indicators are hidden via property nodes.
The code currently will not run due to a large number of DAQ devices not hooked up.
Thanks for any suggestions!!
Brian L
Solved!
Go to Solution.

Bingo.
As for the simulated DAQ's... Whenever I start the VI on my computer, the system is searching for all of the DAQmx vi's that have been placed. All the non-express vi's for the DAQ's are gray question blocks. After I have ignored 14 or so of these "find yourself" requests, an error box tells me that is is missing "daqmx.rc"
Also, Express VI's for the DAQ's will not let me see inside them
If this should be a new topic, I'll move it...
Brian

Similar Messages

How to make the LV front panel controls the current value through the program is set as the default value when the next time you open?

How to make the LV front panel controls the current value through the programis set as the default value when the next time you open?
1110340051

Try this: Re: How to make a VI remember the latest control value?
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice

How can i use the same front panel graph in more than one events in an event structure?

i want to display the signals from my sensorDAQ in a graph.but i have more than one event in the event structure to acquire the signal and display it in the graph.the first event is to acquire the threshold signals and its displayed in the graph as a feedback.after the first event is executed, i will call the second event,where the further signals are acuired and compared with the threshold signals from the event 1.my question is how can i use the same front panel control in more than two events in the event structure?please answer me i'm stuck.
Solved!
Go to Solution.

Hi,
I have attached here an example of doing the same using shift registers and local variables. Take a look. Shift register is always a better option than local variables.
Regards,
Nitzz
(Give kudos to good answers, Mark it as a solution if your problem is Solved)
Attachments:
Graph and shift registers.vi ‏12 KB
graph and local variables.vi ‏12 KB

How to show in the main front panel the progress of each sub Vi ?

my program has many sub VIs, i wish to show in the main front panel the progress of each sub Vi; what is the best way to do that?
atleast i need to show that each sub vi is completed, [can i add details on the main front panelsuch as: filename that is being read by a subVi, graphs plotted by a subVi, etc..]
can i display a graph from a subVi on the front panel of the main Vi?
what i hv done is attched as picture.
Solved!
Go to Solution.
Attachments:
Capture4.JPG ‏152 KB

as suggested...pass references and cntrl references
Spoiler (Highlight to read)
Attachments:
main ref cntrl.zip ‏27 KB

How to place event callback components and "main-VI" components in the same Front Panel?

What I'm trying to accomplish:
Place a .NET component, which generates events, and other standard LabVIEW components in the same Front Panel. The standard LabVIEW components should be updated when events are being generated in the .NET component.
How I tried to solve it:
Problem:
The event callback code must reside in a separate event callback VI. In order to "pass the event up" to the main VI I tried to use a global variable. The interrupt does occur:
but I was hoping that the string indicator would be updated when the event occurred, but it wasn't.
Questions:
What's the best way to solve what I try to accomplish? If I want to solve the problem on the picture above, how would I do it (it may not be the best solution, but I'm still curious what's wrong)? Please feel free to be over-explicit when replying as I am novice LabVIEW programmer. Thanks in advance for any help.

There are two bundle functions for creating clusters. The function simply called Bundle operates almost exactly like the Build Array function I showed. The type of the output cluster depends on whatever you wire in as inputs. You don't have to supply a specific type parameter.
The function called Bundle by Name takes in a specific type of cluster in the top input and allows you to fill in the values of that specific type of cluster. To create the specific type of cluster you want, you need to create a cluster of string references. Here's how to do that:
Go to the Front panel and drop down an empty cluster shell.
Go to the Refnum palette and drop down a Generic Control Refnum. Now here's a cool trick to turn that generic refnum into a string-specific refnum (a so-called strictly-typed refnum). Grab a string from the controls palette and drag it into the Generic Control Refnum. Once you drop it, you'll see the refnum change its icon to display a string picture.
Make copies of this string refnum (as many as you need) and add it to the cluster shell.
Now, if you're making specific types of clusters to work with, now is the absolute best time to learn about typedefs if you haven't already. It will save you hours and hours (if not days) of development time in the future. Trust me!
Jarrod S.
National Instruments

Red box Highlighting the entire work area of the Block diagram

I have a thin red box highlighting the entire work are of the block diagram...I've checked for breakpoints but dont see any. I run the code and after completion the entire work area turns black for a couple seconds and then the red box flashes and the continue button on the tool bar is hightlighted. Any assistance would be great
tks

This is indeed a breakpoint.
You should be able to clear it by selecting your breakpoint tool from the tools palette and clicking outside of your main code area.
When your breakpoint tool is going to set a breakpoint, the tool is filled in with black. When is is going to clear a breakpoint, it is not filled.
You can also search for breakpoints from the Edit menu Find function. Click the Select Object icon goto Others and select Breakpoint. This will find all your breakpoints. Sometimes they get set by mistake and you don't know it.
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.

Viewing the logged front panel data

I’m writing into the datalog file, I can see that the data is recording every one second, but when I retrieve the data i.e. viewing the logged front panel there is only one data since the range is from 0 to 0 ([0..0]). Does anyone know why? And how can I fix the problem?

You should Never rely on the abort button on the tool bar to stop a VI in a loop writing to a file. The abort stops everything immediately and you don't properly close the file. Instead of using a boolean contant in your loop to get you an endless loop, add a Stop button (a boolean switch) to your front panel. Wire that through an inverter to the Continue terminal of the loop, or (if you're using LabView 6.x) right-click on the Continue terminal and change to Stop if True, then wire the Stop button directly to the terminal. Then pass the file RefNum out of the loop to the Close File function.
For debugging purposes, I do use the Abort toolbar button, but I never create a VI with the Abort as the only means of stopping a VI. Anytime you want to st
op a VI in a loop, you may want to have some control over how it stops. There may be files to close, instruments to shut down, results to process, etc. Even if the VI is very basic or even temporary, just get in the habit of using a Stop button on your front panel rather than a boolean constant to get an endless loop. It's really not that much more work and it gives you control over your VI.

Udio to my clip. When I bring it over it highlights the entire clip as opposed to adding it above or below. Then I can't edit the audio clip. HELP!!

Trying to add audio to my clip. When I bring it over it highlights the entire clip as opposed to adding it above or below. Then I can't edit the audio clip. HELP!!

Just discovered this nifty little bug myself today. Boy, Leopard is really bug city, I'm definitely regretting the upgrade. I was glad to find the 'show in mailbox' trick, although then once I went to re-send the message, it duplicated it for some reason and sent it twice, so now my business contact thinks I'm a moron because I sent him this super large attachment TWICE thanks to moronic Mail.app.
Another interesting thing though, is that after finding the email via 'show in mailbox' and opening it, it actually displayed the MP3 attachment as the old Tiger quicktime player (w/progress bar) as opposed to when I first composed the message and it would only display it as an icon. I thought they had just removed that feature for some reason, but nope! Another bug!

Using the soft front panel to take a differential measurement.

I have a PXI- 5152 digitizer and need to use the soft front panel to take a differential measurement. I found how to do this by programmatically, but cannot figure out how to do this on the soft front panel. Can anyone help?

Hi Towleb1,
From you second sentence in your question I assume you already found this resource, but just in case I wanted to provide you with a white paper called Differential Measurements Using High-Speed Digitizers. This is a fantastic resource that includes flowcharts and instructions for hardware self-calibration, probe compensation, gain and offset calibration, and actually taking the differential measurement itself.
As far as taking a differential measurement with the NI SCOPE Soft Front Panel, are you talking about taking a single differential measurement or are you talking about taking a differential measurement between two channels on the PXI-5152?
You mentioned that you found how to do this programmatically, but is there a reason you specifically want to use the NI SCOPE Soft Front Panel instead of LabVIEW?
Sam B.
Applications Engineer
National Instruments

Can I have an array of controls without having them in the array front panel holder?

I would like to link a number of boolean control buttons in an array without grouping them on the front panel the way it does when you make an array and then put in a boolean control.
Here's the background:
I have 8 linear motors controlled by CANbus, and so each button type (Move, Stop, Home, etc) is duplicated 8 fold. I have an event structure that is currently triggered with a separate case for EVERY button with only a very small difference in the code inside each case. Ideally I could have the buttons in arrays and then check the new array value against the old value on a value change event. The alternative for me is to have each case handle the 8 buttons (with a Mouse Down? filter event) and then use the Boolean.Text value from the CtlRef and search an array of all Boolean.Text Values for the 8 buttons to see which name matches and process accordingly. I have something like 200 buttons, so making the arrays of Boolean.Text values from the reference nodes is WAY too time consuming as I have to go through like 5 levels of right click menus. Any suggestions?

Mark,
You might consider using clusters on the front panel. Create a type def'd cluster that has all the boolean controls for 1 channel. You can drop 8 of these on the front panel and the event structure can detect a change in a cluster. Easy to convert cluster to array behind the scenes. Remember that order of cluster determines index of value in array.
Message Edited by Wayne.C on 04-09-2010 05:19 PM

Saving the Control Values on a Front Panel

I am creating a VI in which I have approximately 10 front panel controls that can be changed by a user. Instead of entering the same values over an over again, I would like to provide the user the option to save a set of control values that can then be loaded the next time around via a drop-down box. Before I began I just wanted to see if anyone had done anything similar. I was stumped as to how to approach it. Any suggestions?
Matt

Matt,
You can also use a datalog file. LabVIEW can write and read clusters to a file, and as long as the cluster don't change you should be fine.
Basically your code would grab the value of each control, bundle it into a cluster and save that cluster to a file. For reading, you read your cluster from the file and get each individual value to drop it in the right control.
I'm sure there are some shipping examples on this too.
I hope this helps.
Regards,
Juan Carlos
N.I.

How to highlight the entire folder with the tag color, as before?

I've always highlighted important folders with colors, so that they stand out among others in a list for quicker access. Now in Mavericks list view, there is only a small color dot to the right of the folder's name (sometimes very far from the folder's name if the column is large). As a result, it is much harder to pick important folders. Is there any way to apply the tag color to the whole folder, as it used to be in all previous systems? Or at the very least, to move the dot to the left of the folder name within lists, as in Icon view? I really hope Apple did not remove this feature simply for the sake of design. Thanks.

mistersquid, S. G. is actually referring to the new Tags feature in Mavericks. This replaces entirely the Labels feature in previous versions of the OS, as far as I can tell.
Labels would let you apply a color highlight to a folder. It would appear as a color behind the entire row.
With Mavericks, however, Labels are gone and are replaced with Tags, which just puts a small colored dot off to the right of the folder name (and it's always like this, not just when you click on the folder), and some of these aren't distinct enough from one another (i.e. purple and gray look almost identical if you're scrolling through a series of "gray" folders pretty quickly—you may miss that one purple dot). Also, like S. G. mentioned, these can be pretty far off in your periphery if you've got long folder names, so this just adds another level of "hard-to-see-ness" (it's a technical term ).
I'm a graphic designer and I have been using Labels to colorize my job folders according to their current status. For example:
No label = job is open/in progress.
The next color schemes were more of a "stop light" effect, going from red to green:
Red = job is approved. Prep final files and send to printer/client.
Yellow = job is done. Prepare job ticket/calculate time for billing.
Green = job is done and job ticket is ready to go (hence the green color) to my co-worker for billing/invoicing.
Gray = job is finished/billed/closed (i.e., I've "grayed it out").
Purple = job transferred to another co-worker (i.e., I got too busy and they're working on it now). This one is a rarer color, and with Tags it's a bit difficult to discern one or two purple (more like a light lavender) dots in a sea of gray ones.
I agree with S. G. and would love to see a stronger means of identifying the status of a project at a glance reappear—perhaps as a selectable alternative to Tags in the Finder preferences (because I can definitely see how the two means of colorizing a folder could compete with one another), like a checkbox to the effect of "Use Labels instead of Tags," similar to the "Open folders in tabs instead of new windows" option.
Feedback submitted. Thanks, yodathejedi, for the link.
Message was edited by: Xiebinrui -- oops, duplicated word. Fixed!

"Shared Variable Control" combo box on Front Panel is empty after Build

Hello;
I have a project using shared variables and the DSC module. I am working on building a .exe application now that the project seems to run well.
I have several places on the front panel where I have shared variable controls. These combo boxes allow the user to click the drop down button and browse the list of shared variables in the project, as well as "browse". When I run the VI from the project, the combo boxes fully populate with all of the deployed tags in the project (I have only one .lvlib in the project).
When I build the project and run the executable, the only item in the combo box list is the "browse..." selection. I can click on that and browse to my variables, but it is much more time consuming to do so than to simply select the desired variable from the drop down list.
So, how can I populate the list of shared variables from a particular library ino the Shared Variable Control combo box in a project build?
A couple of things I have done to try to esolve th problem are ensure that the "Enable Enhanced DSC Run-Time Support" box is checked in the advanced tab of the build window, added the appropriate .lvlib file to the "Dynamic VI's and SUpport Files" window under the "Source Files" tab of the build window, and properly deployed the tag library programmatically in the project.
Thanks,
Michael Hampson
Michael Hampson
President
XL Automation, Inc.

Hi Michael,
What you see in the development environment is to make it easier for developers, and as far as I know, there's no way to automatically populate the shared variable control during run time in an executable. The reason being that the shared variable control would have no way to know which process it should be using to get the variables from. The attached vi demostrate how you can acquire the list of shared variables in a process. You can also set the default values of the shared variable control by right clicking it on the front pannel, go to Data Operations->Make Current Value Default. I can do some more research on this, but I'm about 95% sure that there's no way to convert the array of shared variables to populate the shared variable control, as the shared variable control is a special type of xControl.
Yi Y.
Applications Engineer
http://www.ni.com/support
Message Edited by Yi Y on 07-02-2007 01:27 AM
Attachments:
SharedVariableList.vi ‏15 KB

How to create control dynamically while front panel fly using Xcontrol or anyothere options but without scripting tools

Hello friends
I have one doubt How to create control dynamically while front panel fly using Xcontrol or anyothere options but without scripting tools.I need to create the controls while vi is running.For example I need to create one Boolean while VI was Fly and i need one Examples it is easy to understand.
Jayavel

You must be using a different dictionary than the rest of us.
You can't dynamically create controls while a VI is running. (If I'm mistaken, then I'm sure someone else can jump in and say how it can be done.)
Do you have a finite number of controls you could possibly need? What you can do is create enough controls of the type you need ahead of time. At the beginning of your program, you hide all of those controls. As you need to create a control, you make it visible using property nodes. There are numerous properties you can set at run time suce as ranges, colors, captions, ... Of course you can't wire these controls to any other bits of code ahead of time since at that time, you haven't defined what you want each one to actually control. But if you use an event structure to detect when the values of the controls have changed, you can then programmatically pass the data off to other parts of your code using queues. The architecture can get complicate quite fast, so you may want to look through Ben's Action Engine Nugget and other related threads for how to create mechanisms for using these controls. Perhaps storing queue reference numbers or assign user events to each one.

How to move NI hypertrend control around on Labview front panel

Hi everyone,
Please I would like to know if the NI hypertrend control from the DSC pallette can be draged across the front panel and how to do it.
Once I put this control on the front panel, it just stays where I put it and would not allow me to move it around.
I will appreciate any suggestion on this.
Thanks.
Solved!
Go to Solution.

Left click above left of it> hold and drag a box around it. This selects it and you can drag it.This works for me.
Using LabVIEW 2010SP1 and TestStand 4.5

"find control" highlights the entire front panel

Similar Messages

Maybe you are looking for