Front Panel USB3 solution for 990FXA-GD65?

I just got a 990FXA-GD65 and a case with front panel USB3. I assumed (incorrectly) that there would be a USB3 header on the MB. Is there any way to hook up the front panel USB3 male plug (20-pin I believe) to one of the back panel USB ports with some kind of adapter?
Thanks.

Yes they make those adapters and they make adapters for plugging those ports into the USB header on the motherboard. Then you can always put an add on card for USB3 connection.

Similar Messages

Front Panel LEDs problems for Mega 180

Hi, it's rigth one year I got a Mega 180, and I've not ended yet to tune and optimize it
I admit it's like a hobby now
I immediately ask you for my LEDs problems.
I have read many topics and maybe other people have the same my problem, also if I'm not sure if they treat about the Front Panel LEDs when they speak about the "LCD Display".
I have some switched off LEDs in my front panel, in the "time" displayng and in the volume bar: I have to substituite them? Someone have done it before? It's possible to remove the front panel or I have to disasseble all the pc
Or it's a firmware problem?
I also thank all people that cured the section of optical devices compatibility: last week I bought a new Pioneer 111D, because my LG GSA-4167B was not suitable in the PC mode, for DVD playback.
In fact I had many problems for the DVD fluently playback: I have spent 4 months trying new video codecs and also substituting the video card, then I finally have understood that was an optical device problem.
The Pioneer 111D was perfect in the PC mode, but then I had problems for HI-FI playing mode
Then I finally used my old Pioneer 108, that I had in the old desktop, and all work (I pray) fine both in HI-FI and PC mode.
I'll be very happy also to describe to whom that will ask me, my experience with the Mega 180 "assembling", during the last year, hoping it could be useful for other people.
Thanx

> Hi, I'm new to LabVIEW! Ok, what I'm trying to do is create a front
> panel with 9 LEDs. Then I have a Menu Ring, with three different
> options. These options determine the order in which the LEDs are lit.
> So what I was planning on doing was creating three subVIs, one for
> each of the options...but how can I do that when I only have one
> boolean for each LED? So basically how can I relate the LEDs on the
> front panel into the subVIs? I tried using globals - but it seemed
> like that just passed on the state of the boolean instead of allowing
> me to actually change the boolean in the subVI. I hope this makes
> sense...I'm really confused! Thanks for any help!
Initially, you might just hook your ring to a case structure to
determine which frame exe
cutes. You can put the terminals for the
Booleans in the different diagrams and about the only other thing to
keep in mind is that you probably want a delay in the loop.
Greg McKaskle

890fxa-gd70 front panel sound

hi, i want to ask if 890fxa-gd70 supports ac97 front panel audio?..
i know the board has hdaudio but my case only has ac97 connection..
i want to know if i can safely plug my ac97 front panel audio to the board..
if not supported how can i use my ac97 front panel audio to my 890fxa-gd70..
will i need to buy a new hdaudio wire or can i just rearrange the pins in my ac97 to make it work..
thanks..

hmm.. does that mean it is safe to plug my ac97 front panel to my mobo?..
btw i saw this on the net:
AC'97 front panel audio does not work with onboard HD Audio
The onboard front panel audio connector provides microphone in and line out signals for the front panel. Many chassis manufacturers offer chassis with front panel audio ports and cabling. Those front panel solutions may support either AC’97 audio or High Definition (HD) audio.
The onboard audio headers on Intel Desktop Boards with the Intel® 945 chipset and later support HD audio.
Compatibility:
HD front panel audio solutions should be plugged into HD onboard headers.
AC’97 front panel audio solutions should be plugged into AC’97 onboard headers.
Some AC’97 front panel audio solutions (but not all) may work with HD onboard headers.
If you want connect an AC’97 front panel audio system to HD onboard headers, try these steps:
Connect Mic_IN (MIC) to MIC2_L.
Connect Audio_R (RIN) to OUT2_R
Connect Audio_L (LIN) to OUT2_L.
MIC_RET and OUT_RET are for HD audio only; you don't need to connect them for AC'97 audio.
Intel does not validate AC’97 front panel audio solutions with boards using HD audio. If the steps above do not work, you will need to use an HD front panel audio solution for full compatibility with Intel Desktop Boards using Intel 945 chipsets and later.
but i dont know what pin# are:
Mic_IN (MIC) : MIC2_L.
Audio_R (RIN) : OUT2_R
Audio_L (LIN) : OUT2_L.
MIC_RET and OUT_RET
i looked at the link you gave me but i cant see any of the listed names there..

How can I display a changing variable in a subvi on the front panel of the main vi as the subvi is excuting

In the document attached the vi on the right is sub to the vi on the left. On the subvi on the right the variable "Field Reading" is continuously updated on the front panel of the subvi as the "for" loop is executed, but only the last value of the variable is updated on the main vi front panel which is what is expected. My question is how can I display the changing value of "Field Reading" on the main vi front panel as the "for" loop in the subvi is running?
Thank you.
Solved!
Go to Solution.
Attachments:
Doc2.docx ‏554 KB

Hopefully I can explain it well enough. It really is simple.
1) Create an empty global variable and call it something like User Interface References.vi
2) For each and every control and indicator on your front panel, right-click and select Create/Reference
3) Place these references wherever you like (I use a series of Event cases to perform my initialisation and these all live in one of these event cases). They can be placed anywhere in the main vi.
4) For each of the references, right-click and select Create/Indicator
5) Moving to the front panel, Cut all the indicators and Paste them in the global variable (eg. User Interface References.vi)
6) Moving back to the block diagram, wire the global variable to each of the references and select the same named global variable.
All the hard work is now done (until you add another user interface terminal). You should now have something that look as shown below, [except the reference labels would be to the left (not sure why the snippet put them above)]. In my latest program I have 82 references!
Done. You can now access all your front panel controls and indicators anywhere in your program as shown below.
You can just select Value in most cases, but in this particular case I wanted to fire off an Event to do some things (log the alarm) as well as just update the value. So, this is another bonus with the method.
Hopefully this all makes sense. If not, let me know.

How to create two front panels

Hi in my application i am using two Monitors ..
so i like to use one monitor for Vision display and control operation (Front panel )
And another For Motion Control Front panel .. is it possible to do this ..
(In this case How to split my Front panel of my Vi ..)

Hi
If we use Border Layout, the Panels which are added to the main panel are not displaying properly.
Solution is to use BoxLayout with AXIS parameter. Statement looks like this:
mainPanel.setLayout(new BoxLayout(mainPanel, BoxLayout(PAGE_AXIS));
Thank You for giving Reply,

Determine Front Panel in memory

Hi!
Is there any way to determine, is the front panel loaded into memory, programitically?
Thanks!
+++ In God we believe, in Trance we Trust +++
[Hungary]
Solved!
Go to Solution.

Well, easy rule of thumb:
LV does not load the front panel into memory if not needed.
LV loads the front panel into memory if you display it.
LV loads the front panel into memory if using property nodes requiring the front panel. This info can be obtained from the detailed help of this property:
LV loads the front panel into memory for certain methods (also documented in detailed help of the method).
On a side note:
Please do not mix execution of code in the UI thread with loading the front panel. The UI thread is always running and does not determine wether (or not) front panels are loaded into memory!
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How do I programatically open a LabView Front panel?

I want to use a test stand variable (perhaps a sequence global) to control whether certain VIs open their front panels, and wait for subsequent operator interaction. Can I get there using the API and something like this: "Step_TSInfoProp.TSInfo_StepAdditions.LVStep_ModulePathProp" ?
I tried passing a boolean to the VI and then having it optionally open its own front panel using the VI Server, but I could not see it because it would always be behind the TestStand Window.

Sean, The reason for doing this is that the client wants a "debug level" control of some sort. If set below some value, the VIs just do their thing, take their measurements, report, or whatever and go on their way blindly as what we expect a good test sequence to do. However when this value is set above some level (the threshold may be different for various categories of tests) the VI becomes interactive. This would allow an operator to see a measured value, and possibly tinker with the instrument parameters or the UUT, before continuing on. This might be similar to a single step command, but not necessarily pausing at every step. Inside of the VI I can test the value of the variable (either passed in through the connector pane or via the sequence context) and thus decide whether to be interactive or silent. I can also use the VI server to open my front panel or not. But in doing so, even though I try to make the VI panel frontmost, it is hidden by Teststand. If the VI attribute is "dialog" then it does show up on top of everything else, but unfortunately does so even when I don't tell it to open at all.
PC

Storage VI blocking on front panel interaction

For some reason that I can't figure out, the "write data" storage vi (and perhaps others) will block during
front panel interactions. For instance clicking on a ring button will block until you select something.
The button doesn't have to be on the same VI either. Also editing a separate VI, when you right click
and start looking for the right function in block mode or widget (I forget the labview term) in the Front Panel,
will block the write.
The problem with this is that my main program is saving data from a ring buffer, so if someone takes
too long making a selection, I've lost data. I attached a VI that can demonstrate the bug
(at least on what I can try it on). I've gotten the attached VI to work with labview 8.0 and labview 8.0.1
Attachments:
Storage Vi Bug.vi ‏42 KB

Hello,
Thank you for posting this well written description and
great small example which reproduces the problem! This seems to be only occurring with the
write data like you mention. I’m not
exactly sure the cause, but I filed a bug-report on it (3ZNC2Q3A), so we can
investigate here. I’m betting it has
something to do with user interface interactions between the controls and the
write measurement file VI, as components from each could run in the UI thread
and block each other. Unfortunately, I
don’t see any immediate workaround without having to change a few things up
with your program structure. For example,
instead of a ring, you could just have one or two checkboxes for the options
and see which the user has pressed. Because
the write file VI is the only one that is blocked, you could conceivably separate
your data acquisition thread and your file IO thread (many times it’s a good
idea anyway). Using the Queue datatype,
you could add all the data to the queue in the non-writing loop, and write to
file in the separate file IO loop. If
the write to file blocks the data will continue to queue and no data will be
lost. This is known as a
producer/consumer VI design pattern.
Your consumer would be the file IO portion of your code. Check out the tutorial of this structure here.
Are these alternatives acceptable? Unfortunately, with the way the write VI
interacts with the user interface thread I don’t see any way to avoid this
problem. I apologize for any problems
that have occurred as a result of this behavior.
Travis M
LabVIEW R&D
National Instruments

What is the best way to zero a 'custom voltage with excitation' sensor from the front panel?

What is the best way to zero a 'custom voltage with excitation' sensor from the front panel?
Thanks for any help

Hi Donavan,
There are two options for zeroing with the NI-9237. You can perform offset nulling and shunt calibration with a strain task, or if you use custom excitation you can use software compensation.
See the Bridge Balancing, Offset Nulling section in the Load, Force, and Torque Measurements tutorial. Take a measurement before the strain is applied and subtract this from all subsequent measurements. See the above tutorial to consider the tradeoff in accuracy between these two options.
Hope this helps,
Jennifer O.
Applications Engineer
National Instruments

Analog output to the DAQ that changes when controls on the front panel change

I'm using the PCI-6024E, and trying to output an analog waveform that can change when one of the two controls on the front panel change. It outputs fine setting it to continuous output and using a simple while loop around the "Is Task Done" VI, but if I put the "Write" VI in the while loop, it doesn't output steadily. I then tried to use an event structure, so that I'd only have to write every time something on the front panel changes, but for some reason it was writing finite samples, even though I set the Timing VI to continuous. I looked around the NI site, and found an article about this with an example. I tried to change it around to use my waveform, but whenever I run it, I get a memory underflow error. Has anyone needed to do this before? Thanks in advance.
-- Josh Matloff

Hi Josh-
It looks like you forgot to post the code still, but I'll take a stab at the problem anyway. It sounds like you're looking for a way to update a continuous waveform at runtime.
You will need to stop the task in order to replace the write buffer information, but this will only be a small gap in operation. I have attached a modified LabVIEW shipping example that shows how to use value change events for any of the pertinent waveform parameters to either programmatically stop the task, replace the buffer, set timing and restart or to just pass the task information straight through. This will lead to continuous operation with no breaks at the output.
Please let us know if this clears up your questions.
Thanks-
Tom W
National Instruments
Attachments:
Cont Gen Voltage Wfm-Int Clk with Runtime Update.vi ‏134 KB

Front Panel Dilemma

I am using Run VI invoke node to run a VI that is reentrant and for passing a single paramter to the same I am using set control node. Now the calling VI will be an exe when packaged and needs to run as an NT service wherein I am not allowed to use any UIs. The set control would not work otherwise is what I presume -I mean without a front panel being loaded for the called VI. Please assist in finding a work around or correcting me if I am wrong in my assumption.

sumitrishi wrote:
> I have to set the auto dispose preoperty to 'true' and wait until done
> to 'false'. So if I dont have the application builder include the
> front panel ( which is what I want exactly) then would the reference
> be not closed by itself ?
You have to leave the panel in the application as otherwise you won't
even be able to open and run the VI.
> How can I prevent it from happening ? Do I have to do it
> programatically by making the VI hold a reference to itself till the
> time that running instance is required? I think I tried this but it
> does not work.
Yes leave the frontpanel in the build, open inside the VI as soon as
possible a VI refnum and you can even set Frontpanel.Open of that refnum
to False to make sure it is
really invisible. Keep the VI refnum open
inside a shift register until you are ready to shutdown, but don't close
the VI refnum until after you have properly disposed any other possible
resources. Once the internal VI refnum is gone while no front panel is
visible, (it must be present in the built nevertheless for VI server to
be able to start it up as independant task), your VI will abort
immediately even if the diagram still contains code to execute to close
files, VISA resources, etc.
> If you feel that it should have worked then I might try
> again. My program actually is a kind of server that spawns a new
> thread everytime a request comes from the client and this server needs
> to be running as a windows NT service . The hierarchy on the server
> side is that it runs a re-entrant VI (that has a control on the front
> panel that need to be set at the time of spawning).
One more reasone to NOT remove the front panel. If you remove the
frontpanel you can't use methods
such as Set Control Value to manipulate
the control value as it is really not present at all.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Audigy 2 and front panel au

Hi all,
I have a SoundBlaster Audigy 2 (SB0240) I plan to put in my new computer setup, which is going into an Antec P60 case. The new case has front panel audio connectors for both speakers and microphone. The connector is compatible with the Intel specs. Is there a way I can connect my Audigy 2 to this? My mainboard's SoundStorm 2 audio has this connector, but I am unsure if I can do this with an Audigy 2 card.Message Edited by dterborg on --2004 2:36 AM

Bump...can anyone help me here?

View front panel by going to a registered domain name

Hi all,
I have a registered domain name, say, www.frontpanel.com
By configuring a router, I can now view a running LabVIEW front panel within campus by going to 128.200.xxx.xxx/frontpanel.html, my questoin is, how can I view the frontpanel from outside of our campus. Say, I have a registered domain name as shown above.
The LabVIEW is version 2012, and the system is Windows 7.
Thanks for any help,
-Chen

This has nothing to do with LabVIEW but...
You need the network to be configured to allow external requests to the PC and to set up the domain name to point to the external IP address of the computer.
If it were a home network, you'd configure your router/modem to forward requests on the ports required (port forwarding port 80 for the frontpanel.html and any ports that Remote Front Panels needs) from the internet to the PC that is running the Remote Front Panel VI.
For the domain name to work, you need to configure it's DNS settings to point to the external IP address as above. If it's a static IP address then that's pretty easy to just put in the IP address but if it's dynamic then you need to use a dynamic DNS service (e.g. dyndns).
If you're on a Campus network, you'd have to go through / talk to their IT department and I'd be very surprised if they allowed that to happen.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Looking for a way to programmatically set the visible portion of the front panel when a subVI opens

I am looking for a way to programmatically set the visible portion of the front panel when a subVI opens. Haven't found any posts that relate, but I'm not sure how to ask the right question. To be clear, I want to write a helper VI to go through a list of subVIs to make sure the background images are all in the same place when their respective subVIs open. I hate manually playing with scroll bars before I save each of the VIs... I'm figuring I need to find the top/left location of the background image (know how to do this already) and then set a VI FP property to these values or some offset, but I can't find the relevant property. FP:run-timeposition:custom looked promissing, but only affects the location of the window, not the area of the front panel the window is displaying.
Solved!
Go to Solution.

Cool. Getting closer. The way I implemented your suggestion affects the subVI only if it is open. I can use this to do what I'm after, perhaps putting the code into each subVI. Maybe open all subs, run the helper, and save. Seems like I'm missing the elegant version...
My proof of concept code:

Is there anything like a front-panel OPEN or FP.STATE property for an RT (cRIO) VI?

I'm wondering if there is a way for an RT VI to detect when its front-panel is open, both when run interactively from within a project and also when accessed remotely as an embedded window within a browser?
Solved!
Go to Solution.

I know about the "Remote Panel:Connections to Clients" property and I'm already using that to tell whether a remote connection is active (as opposed to running the VI within the development environment). It cannot however tell if the front panel is open within the development environment.
As for the property-node returning an error, that does not appear to work here (perhaps I have selected the wrong property, I'm using the get-reference-to-front-panel property). I suspect that since the VI is setup to work with a remote front panel, the VI thinks that a front panel does exist even when a remote connection does not. I suspect this error check would work if the VI had not been setup for use with a remote connection because then the front panel would be stripped out as the VI was built or perhaps deployed to the RT system.

Front Panel USB3 solution for 990FXA-GD65?

Similar Messages

Maybe you are looking for