Front Panel Wiring

Have installed Gigabyte GA-G41 M/board. I need a wiring diagram or info on which front panel color wires apply to each connection. Colors are White, Black, Blue, Green, Yellow, & Brown. The connections are On/Off switch, Status LED, & HDD LED. Which color wires apply to which? By trial and error I have determined the On/Off wires (Green & Blue). Any help appreciated.

take some pics of the cables i have the mobo picture you should have the speaker connected aswell 4 pin goes top right http://uk.gigabyte.com/fileupload/product/2/3743/3862_big.jpg
reset switch plug one in turn it on and press the reset switch see if your pc reboots
Thx dave
yoga 2, lenovo b540
3 custom gaming pc systems

Similar Messages

Plug markings on front panel wiring

mother board: msi 845e max
case: msi
os: xp sp3
cpu: p4
hdd: Samsung 40 GB
memory: Hynix 512 mb DDR
I want to confirm that unless the plugs from the front panel are marked + or - , it dosen't matter which you plug them into. The mother board manual does indicate + and -. I am rebuilding this computer adding upgraded parts from a HP with a fried power supply. Unfortunately I first thought to use the HP motherboard and thus removed the msi board from the case. I don't have the manual for the case. I know where all the plugs go but not if their orientation matters. Thanks

For reset and power switches, orientation doesn't matter, as the switch simply shorts the pins when pressed.
Its only the LEDs that must be connected the right way round. And generally as Wonkanoby said, the white lead is (-) and the coloured lead is (+). If the LED is connected the wrong way round it simply won't work, just try it if you're not sure, it won't cause any damage.

Reading main VI front panel in SubVI

Hi,
I'm trying to create a subVI that writes a header text file containing info on essential parameters in my measurements. My mainVI front panel has a few dozen controls, some of them contained in a handful of clusters.
What I'd want is just to be able to access and read the values at the subVI to construct the string I want to write to the file.
I wouldn't like to proceed the dumb way, i.e., building an array of clusters or individual controls or references to them and passing that to my subVI (and, obviously not passing each individual control/cluster as a subVI input).
I figured I'd like to have some kind of refnum of the mainVI frontpanel passed to my subVI and dig use a big pile of property nodes to dig out the info that i need, inside the SubVI. Is this a feasible solution and if so, what's the way to conduct it? If not, what would be a better way?
As before, I'm using LV7 so in case you answer with block diagram examples, I'd appreciate screenshots of them.
Thanks,
Lauri

Vostokki wrote:
I'm trying to create a subVI that writes a header text file containing info on essential parameters in my measurements. My mainVI front panel has a few dozen controls, some of them contained in a handful of clusters.
What I'd want is just to be able to access and read the values at the subVI to construct the string I want to write to the file.
I wouldn't like to proceed the dumb way, i.e., building an array of clusters or individual controls or references to them and passing that to my subVI (and, obviously not passing each individual control/cluster as a subVI input).
Lauri
Actually that is the preferred way to do. Why you may ask? It is because you decouple the functionality (creating your log file header) from your specific user interface. By doing so you can reuse this VI in other places or applications. By using the references directly this ties the subVI to the calling VI. Unless the subVI is specifically doing something to the UI itself a subVI should avoid accessing data it needs via direct references. It should require the data to be wired in with the appropriate clusters, arrays or whatever your data needs are.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Exporting front panel of subVI to calling VI

Is there a way to "export" the front panel of a subVI so that it becomes part of the (or a pane of) the calling VI? If so, what is it called? I don't know the right language to search for examples of this concept.
My problem is as follows:--
I built a nice, classy interface to a test program that allows the user a great deal of flexibility in controlling the parameters of the device under test and in seeing the impact of those parameters on other parameters. This has about 8-12 control objects, some of which are also wired to act as indicators so that changing one can display on another and vice versa. This interface and its supporting program is big enough that it belongs in its own subVI rather than in the main program. In addition, I built another interface that charts signals from the device under test; this is also big enough that it belongs in its own subVI.
I would like to have the front panels of both of these VIs be part of the front panel of the main program. That is, the front panel of the main program should "inherit" the front panel of each subVI wholesale. If I need to tweak the interface of one of the subVIs -- for example, to add, delete, or replace controls, indicators, displays, charts, etc. -- I would like to be able to do this without having to wrestle with the main VI and the connector pane between it and the subVI.
It seems that LabView should be capable of this, but I cannot find any help, guidance, pointers, etc., in the documentation, textbooks, or examples.
Could someone give me a clue?
Thanks,
Hugh Lauer

So I tried to configure a subpanel, and found it very confusing. It seems that when you put a subpanel control on the front panel, you have to then set up a way to invoke the subVI. Since my subVI has some inputs and outputs on its connector pane, I created a VI reference for it and wired that to the type specifier node of the Open VI Reference node. I then inserted a Call VI by Reference node, so that I could wire up the inputs and outputs of my subVI. Finally, I wired this to the subpanel Invoke Method (Insert VI).
This is different from the examples I found. In those cases, the subVIs had no inputs or outputs on their connector panes, but rather took all of their information from their front panels.
I got different behavior on different attempts to run it. The most common (and most recent) behavior is that the subVI front panel opens up a few seconds after the main VI starts, but it is not quite "in" the subpanel. Instead, it is offset about an inch from both the top and left, as if it were a floating window that I cannot move. Also, it has annoying scroll bars on the bottom and right, which I don't want.
Incidentally, I have two of these subVIs, and I have not yet tried to put the second one into a subpanel.
What I would really like to do is
have both subVIs populate their respective subpanels as soon as the main VI starts, but before any work gets done.
after both subpanels are loaded, run the two subVIs in parallel, one to control the device under test and the other to capture its signals.
have no scrollbars in the subpanel windows.
In fact, what would be the best from a GUI point of view is for the two subpanels to be permanently part of the front panel of the main VI.
Any guidance or insight would be most helpful.
REgards,
Hugh

Close top vi front panel while sub vi front panel run

Hello,
I'm writing wiring a program and have several (several several several .. ) VI which launches Sub-VI with their front panel.
During there Sub VI, the Front Panel of the Top-VI get bored behind...
Is it possible to Hide this Front Panel while the sub-VI is running.
Thanks
Solved!
Go to Solution.

Sorry for this post, i didn't read every replies of the folowing topic :
http://forums.ni.com/t5/LabVIEW/closing-front-panel/m-p/300115
The VI of falkpl :HideFPvi.vi 24 KB is a very good method for my VI.
Sorry again, hope this'll help someone

Can I Bind a Front Panel LED to a specific element in an array of booleans?

In LabVIEW 2010 I have a string of LEDs. I have and array of boolean values that contain the values that the LEDs should indicate.
What is the best way to connect the LEDs to elements in the array of booleans?
Can I Bind a Front Panel LED to a specific element in an array of booleans?
How is this done?
Can anyone show sample code?
Solved!
Go to Solution.

Imagine that you have an I/O card that provides 128, 256 or 1024 digital inputs and the requirement is to have an LED on the front panel to represent the state of each digital input. This frequently occurs.
Wiring that many digital inputs individually is a royal pain and then some !
It would make sense to have one shared variable as an array of Booleans that represents the status of all inputs and then use data binding instead of wiring each individually. The individually wiring would violate all recommendations on diagram size and fan out.
Frequently scanned For loops to update all of the LEDS would take alot of CPU time.
Wouldn't it be MUCH better if PSP could be used to update the LEDs whenever the data changed (as it is supposed to do) ?
In my case I have a LabVIEW Yaskawa servo driver that provides me information about 16 servo drives that may be connected. I have LEDs on the front panel to represent some of that status for each individual drive. But Yaskawa provides the information on the drives as an array of clusters of information for each drive, which I perform some business logic on and turn into shared array of Booleans to feed the LEDs (and some banks of switches as well).
Unfortunately LabVIEW does not seem to have any way to bind the LEDs (and Switches) to individual elements in the shared array of Booleans. It is just not that smart. Even with only several banks of 16 LEDs and Switches, wiring them individually using Decimate Array of Index Array functions is a royal pain and makes the block diagrams very large. It would be much worse and almost unreasonable to do if the size of the information was much larger.

Running log on front panel

I am thinking about creating a running log on the front panel of my VI. It is bascially a string indicator. Each time I write to it in my VI, the indicator will keep what is on there, and write on the next line. To do this, I am thinking about using a shift register to preserve what is in the indicator and continue to append to it.
Is that the best approach?
Yik
Kudos and Accepted as Solution are welcome!
Solved!
Go to Solution.

Ray.R wrote:
... since we are sharing ideas ...
I had implemented something similar to what SMercurio described, except that I used an ActionEngine. This allowed me to keep a log from any of the sub-vi's simply by "dropping in" the ActionEngine. It had additional features to enable / disable logging, select a file/folder, etc. Worked great.
Well, the core of it is an Action Engine. I just use wrapper VIs to perform certain functions. For example, there's a "Memory Log - Add Entry" VI that gets used by subVIs. That's just so I don't have to keep wiring the enum constant to specify what action to take. Gets tiresome after a while.

LV 8.0.1 'NOT RESPONDING' and/or 'split' and unusable front panel while scrolling

Hello,
Is anyone aware of any display or front-panel glitches and bugs with LV 8.0.1? I have been using LV for years, but I have never seen the front panel tear itself (literally) in sections while I use the standard scoll bars at the edges of teh screen, then become completely unusable and go into [NOT RESPONDING] mode (???). In other words, my front panel displays have always moved as one continuous piece when scrolling. During these recent episodes, I would use the scroll bars and parts of my front panel displays would not move while the other section(s) tore away and scrolled as I commanded. When this happens, my entire PC would slow down, the CPU usage would rise and a approach 100%, and the VI was unusable. I have been writing a particular VI for several months, starting in LV 6.1, then LV 8.0 PRO-DEV, and recently upgraded to the LV 8.0.1 'maintenance' release. The problem that I describe here began to occur within two weeks of the maintenance upgrade. The problem seemed to be propagating to my back-up version after I opened each VI in unsuccessful attempts to find a VI that did not appear corrupted. It seemed as if any VI that I opened was going to be plagued by the bug that I described above and I thought that I was going to lose months of expensive work and my job!!!!. In a last ditch effort ( and a stroke of pure genius) I started saving some of these coorupt version as 'PREVIOUS' in LV7.1 format. This seems to have turned the situation around, for now, and saved my VIs from becoming corrupted and completely unusable.
Please let me know if anyone else has seen this. Also, please let me know how to avoid this, in the future. Does this indicate corruption of my LV 8.0.1 PRO-DEV environment or the VI files (or both)? Does NI have tools to correct these corruptions?
Thank you.

Thank you. I can only point to the following events/ techniques that were somewhat different from my previous experiences/ techniques:
1) Performed 'SAVE AS... ' new file name to these files over several months and several times a day using similar filenames with only one number character different between them
2) Logging long data files to the root C: drive and closing in on less < 5GB HDD remaining (could this be overwriting soem temp files that LV uses to manag graphics???)
3) After saving to LV 7.1 and re-opening with LV 8.0, I get a message that is new to me that explained something about wiring a Boolean constant to a case structure and how LV 7.1 or previous used this to keep a sub-vi in memory (???). Unfortunately for me, I did not capture the exact syntax of this message and I do not wish to intentionally repeat this graphical feature.
4) I copied a small block of code that contained a 'cloned' sub-vi from one block diagram to the a similar VI that , shortly afterward, exhibited the front-panle 'tearing' feature. This is something that I usually do not do, and, again, is one of the only new actions from anything that I have done in LV for the past several years.
5) After the message described in (3), above, the rescued LV 7.1 version had moved a handful of the most recently added indicators to a very remote location, about 30 seconds of edge-scrolling time, to the left of my front panel graphics. I perfromed a 'drag' operation by selecting these and bumping them to the right edge of the screen for about 30 seconds to get them back to the vicinity of my front-panel graphics. I have never experienced a VI that shifted inidcators so far off the edge of the screen.
These are the only ' unique' events that I can recall before the 'tear; effect.
Thank you.

Trouble getting a subvi to update a graph in real-time on the front panel

Hi All,
First post here, so play nice =). I am trying to update a graph on the front panel from within one of my subvis, however it does not update it in real-time. It will only show the completed graph after the subvi finishes running. I have tried to use references/property nodes and I have also tried using my chart as a global variable, but neither of those methods have worked (I am probably doing it wrong). Can anyone provide a detailed walk-through of how to do this using either one of those methods? Or perhaps even a different method?

ModusPwnens wrote:
This is how you do it, right?:
Try this for a quick demo of the reference method:
Create a VI as shown in the image.
Select only the while loop and do "edit...create subVI" (as shown). (you will get a subVI that contains the needed connectors and is alread wired to the reference)
Run the main VI, and the chart will update every 200ms.
Note that this is only a draft and many things are missing. (For example, the subVI cannot be stopped at the moment. Also, you want a graph, and not a chart.)
LabVIEW Champion . Do more with less code and in less time .
Attachments:
updateViaSub.PNG ‏32 KB

Switching between two tables in the front panels

Hi
I am working on an application,which has two "Tables"
in the front panel. Both the tables do get updated
simultaneously from the same test,
Table-A displays
A short summary report while the test is beign executed, and result.
Table-B displays
A detailed report of the test and its condition and parameter
along with results.
My front end is a simple display table, along with couple of
Button controls,like "START","ABORT","DeTAIL DISPLAY" and "QUIT"
ofcourse.
All these buttons are used in Event driven case structures except
"DeTAIL DISPLAY"
as the execution beigns, on the press of start button,
there are number of tests in which i have to pass, parameters to
DLL and get back the result parameters.
The end customer requires to switch the display between the TABLE-A & TABLE-B during execution.
so i have a, seperate while loop,where in a case structure is wired to "DeTAIL DISPLAY"
button, and if true, visible is set to true to TABLE-B, and false to TABLE-A,
and vis-versa. as per the logic this while loop should take care of switching between the
tables.
The other while loop Takes care of the entire test.
My problem is that, while i execute the switching of tables are not fast.
it waits till the tests are over,and event case structure is in idle state, and then switches to the other table.
Also some times i am unable to click on button"DeTAIL DISPLAY", as the event control
case structure, is not responding till end of the execution.
How to over come this problem
rags

Hi,
Have you tried using notifiers in master slave architecture?
check this out
Attachments:
Notifier.vi ‏45 KB

Printer error on 8500 A910 front panel flashing lights.

I'm getting a printer error on an AIO 8599 A910, with all the lights on the front panel flashing. I restart, as prompted, but 2-3 minutes later, it has the same error message. I just (within the last week) did the firmware update. Any help would be appreciated. Otherwise, I'm dumping this thing.

All:
I'm on my second 8500. It was failing, too, and for the same reason. I switched over to a USB connection, and the problem ended. I also tried it again, but with hard wired ethernet vice wireless. Again, no problem. There seems to be a problem with the wireless circuitry used in the 8500, as well a a few of the Photsmart series printers as well.
I could not believe that it was this simple. I called HP, and pointed out what I'd found. The young lady who answered the call was very nice, asked lots of questions, checked with her folks there, and then cam back and said that if you go into the Network tab of them embedded web server of the printer, then go to network protocols, the select IPv4 ONLY, the problem will stop. I've not tried it yet, but I will. Perhaps some of you all who are having this problem can give it a shot and come back to the forum to let us know.
HP does have, I'm told, a firmware fix for this due, but....
Later,
JDM

How to find VI's connected terminals when controls are hidden on the front panel?

When working with a sub-VI which has terminals connected to hidden controls is there a straight-forward way to find the terminals on the block diagram?
I click on the terminal and an outline appears on the front panel but when I try to click on that outline I can not unhide the control.
The only way I have discovered to find the terminal of the connected control is just check each terminal on the block diagram which looks like it might be connected.
I'm using LV7.1 but also use 8.5.
Thanks,
Davey

Ben wrote:
smercurio_fc wrote:
If I understood the premise of the question it sounds like you have controls/indicators wired to the VI connector pane, but for some reason these controls/indicators are hidden. If this is a VI you wrote slap yourself. If this is a VI someone else wrote, go slap them.
One way that you can find the terminals on the block diagram by performing a search by text. The context help will show you the names of the controls/indicators. The only problem with this approach is that if the control/indicator has the caption visible rather than the label, then the context help will show the caption, not the label.
Another method is to use scripting. Not sure if it's worth the effort for just one VI, though.
Before we get all slap-happy I have to ask...
If I have a sub-VI which is set for Print on completion and the controls in/out for the icon connector are NOT supposed to show up on the final report, isn't setting those objects as hidden a viable option?
Ben
Well, of course, Ben. My comment was not meant to be taken seriously... hence the smiley happy icon. To respond to your question in a more serious matter, though, there's always exceptions to rules. That's why they're rules - they're meant to be broken. Otherwise they wouldn't be rules. It's a strange state of the universe, isn't it? Although, one could probably just place the control behind another object. That sort of hides it, doesn't it?

Front panel audio jack is not working on K9N Neo V2

My front panel audio jack is not working on K9N Neo V2. I check the JAUD1 cable and it appears to be connected to the front panel audio jack. My soundcard driver cannot detect any gadgets when I plug it in the front panel. My audio drivers and BIOS are up to date. Is there any known solution to this? My computer is only a few months old and I have not tried the front audio jack until recently. I'm on Vista home premium btw.
Also, I've got another problem, my processor is AMD 64x2 4400+ overclocked to 2.63Ghz. I've been using that clock value ever since I built this computer and stress tested the processor and found that it would not cause any problems like hanging or overheating. However, I recently decided the need for AMD's Cool & Quiet technology and enabled it. It caused BSODs every few days or per week that didn't happen before. I tried it with the default clock value and it still causes BSODs. Can someone help me?

Quote
Thanks. Its ironic that disabling it actually enables it.
It has to day with the front panel audio wiring of your case. How many wires are there that can be connected to the board's pin header?
Quote
Sound quality isn't very good
Can you be more descriptive? Is the quality better if you plug the headphone into one of the jack at the back panel? (Also, make sure you tell the Realtek HD Audio Manager, that a headphone is connected (and not regular speakers).

Using config files to setup front panel objects and DAQ info.

I am trying to write a program that condenses 5 versions into one. I need to be able to load a configuration file based on the users choice of which machine they are using and use that information for my dropdown boxes and for what was constants in a case structure based on a choice from the droplist.
For example, if a certain part was selected, it had 5 limits listed as constant that the data aquired was compared to. The limits were inside a case structure wired to the droplist.

"I have a case structure that is connected to a digital line. The program receives a value from the machine's PLC and it picks the appropriate case. Inside this case, there are constants for tolerances for the measurement that was selected. Each case has the same number of constants to control the tolerances for 5 different characteristics of the measurement. There are 32 cases each with different values. The problem is, I have 5 different versions of the program with up to 32 cases in each structure, (over 150 different sets of tolerances). I do not have them all in one program as the same case number is used somewhere else and may have different values. The display information on screen is also different from one machine to the other, and I want to
be able to hide or show certain front panel objects. I would like to set up an .ini file of some sort that stores all my case selections and load them in blocks, on one machine i load these 32, on a different machine, load the other, etc. Also be able to load the preferences for what is visible and what is not on the front panel."

Saving Image of front panel in an application

See attached image.
Using my source code, I can save the image of the front panel with no problem. However, when i build an application and run this, the image of the front panel does not save. Can anyone help?
Attachments:
Save Image of Front Panel.JPG ‏19 KB

This piece of code does the trick, don't mind the wiring.
André
Message Edited by andre.buurman@carya on 09-17-2007 05:39 PM
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)
Attachments:
Top level dir.PNG ‏10 KB

Front Panel Wiring

Similar Messages

Maybe you are looking for