Front panel issues

Hi All,
I had a question about the front panel connectors. I have a Lian-Li PC60 series case. On the JFP1 slot I have the reset and power switch configured correctly in that they both work.
However the HHD and Power LED aren't working. The HDD LED glows a constant red (the hard drive is functioning normally) and the Power LED isn't working at all.
My case doesn't have the two pin HDD and Power LED connectors that connect to JFP1, only one 3 pin Power LED connector that connects under the 4 pin speaker connector in JFP2. I figured I might have reversed the correct side and connected positive to ground, but after changing that, it doesn't work either way.
Both LED's functioned with my old IC-7G board.
Any ideas?
Other than that the PC appears to be working fine.

They seem a little high i'm no expert on your CPU or its temp, other than knowing the max is about 70C. Check temp in bios its usually more accurate.
Check any literature that came with CPU or try
AMD Athlon™ 64 Processor Power and Thermal Data Sheet
Mine 3200 (754) shows 38C - 53C Idle/Load
It's certainly not dangerous or something to be overly concerned about, just something you might want to investigate at your liesure.

Similar Messages

Audigy 2 ZS Platinum - Front panel issues

Hello there,
I originally had the Creative Audigy 2 ZS Platinum and all was fine. It all worked and the world was happy. I then (won't go into details) managed to damage the card and whilst I still got sound, the front panel and the joystick port would not work. As it was only the card that was broken, I purchased a new Audigy 2 ZS card assuming I would be able to just stick the front panel connector back on and all would be hunky-dory.
As you probably guessed, I am here, so all is not well. Whilst the game port now works, the front panel still does not respond to anything and I am at a loss. Is there some kind of jumper I need to switch or something? What have I done wrong.
All input is more that welcome, thanks...

i am having front panel issues. i think the damage to the card is a potential problem, but i don't think it's the cause for the panel not working. i think something is just seriously wrong with creative hardware. i really don't think pre-sales testing was performed extensi'vely enough. i have had more problems with my audigy 2 platinum in the 2.5 yrs i've had it than a new born baby. to make a long story short, i did a complete upgrade of my system, the only thing i kept was my case and audigy 2 and front dri've bay. i did nothing different than i had before, re-installed windows and everything. everything EXCEPT the front dri've bay works. i do get the red light from the optical out though, so there is power. i don't know what's wrong with this thing. all i can say is: creative you need to get your s**t together, you have as many issues with your sound blaster cards as microsoft has with windows. tech support: you need to do something for once and answer posts that people ask. i posted my question about this problem 7 months ago when it happened, guess how many repsonses i have. ZERO, NONE, NADA, NOT ONE RESPONSE. i don't blame forum users, not everyone knows, i blame tech support b/c you don't respond. i have no clue why, but do something, please.

7,1 was a dream: Media shortcuts/front panel issues

Hey
I have a Dell Inspiron 6400. On the front it have this Media Shortcuts / Frontpanel
In iTunes 7.1 they did work. Like, I could minimize iTunes, use other programs and still I could change songs and stuff. But after all the updates on iTunes, this ability is gone. It's only with Windows Media Player it'll work.
Anyone have an idea about how I can fix this?
(or that Apple could fix this and keep it in their iTunes in the future)
Message was edited by: VonWeibye

Could you clarify a bit on how the PXI-6528 was acting while you were seeing these problems? Does this card have values display on the Remote Front Panel, and if so were they still updating properly? I believe you were saying that, but I wanted to be sure because that makes a big difference.
If everything became static, including the DIO card, at the same time, then I'd say see if your browser updated, or something in your network settings was changed without you noticing. Perhaps an update ran and reset some of your firewall settings, or an Internet Explorer update changed something that required a reboot.
If just the outputs of chassis 2 were the problem, and the DIO card values on your remote front panel still worked well, then it is most likely a problem with your MXI-4 cards or your fiber optic cable that cause the change in behavior.
Miles G.
National Instruments
Applications Engineer

RT Remote Front Panel issues.

I'll start with my setup:
2 PXI-1042 chassis connected via fiber-optic using NI PXI-8336 (MXI-4) cards.
Chassis 1: PXI-8108 embedded controller running LabVIEW Real-time OS (2010), PXI-6528 DIO, PXI-8336 MXI-4.
Chassis 2: MXI-4 in slot 1, 4 PXI-8334 DMM, PXI-6528 DIO, PXI-6281 M-series DAQ.
The real-time executable monitors analog and digital inputs and DMM measurements, displays the values using numeric and boolean indicators, generates alarms and allows users to acknowledge alarms via a Remote Front Panel. The code has a custom error handler that traps errors and stores them in a global array. This allows the code to display them on a console and allows the user to acknowledge and clear errors, and scroll through multiple error messages. We used property nodes sparingly.
The system is monitored by two laptops with the correct run-time engine installed (both laptops have the LabVIEW development suite). Under normal conditions, one laptop keeps control of the Remote Front Panel at all times.
The problem:
The system was running flawlessly for 3 months of continuous use. Then, for no apparent reason, the indicators that display measurements from "Chassis 2" (specifically the DAQ) stopped updating.
If the user refreshed the browser, the Remote Front Panel client would reconnect to the RT Web Server and get updated values, but they were always static. Essentially, refreshing the browser took a "snapshot" of the data, but the indicators did not update continuously as before. At the same time, DIO inputs to "Chassis 1" responded appropriately to changes in state.
Refreshing the browser on one laptop would update the values for that laptop only, and the other laptop could be refreshed independently and have different values displayed, but both laptop's indicators were static. During this time, the DMM measured inputs were not changing and the "Chassis 2" DIO inputs did not change state (i.e., we could not perturb the inputs), so we could not determine if those indications were affected.
Also, the error console did not respond to user input until the browser was refreshed and the client reconnected to the target.
We know the RT application is running on the target because there is code that monitors the status of the loops by changing state every loop iteration and displays the status to the user.
Our short-term solution was to reboot the RT controller by powering down both chassis, starting "Chassis 2", then starting "Chassis 1". It's been running for a few days now without incident.
Since the data displayed after refresh was accurate based on comparison to gages in the system, we do not suspect a measurement problem.
Possible culprits:
1. The RT Web Server has malfunctioned in some way (memory problems, synchronization, etc.)
2. The MXI-4 link.
3. Cosmic rays? Sunspots? Nearby radar stations? Neighboring HAM radio operators (with massive amplifiers)?
If anyone has any ideas, they are welcome. We are concerned that this will be an ongoing problem, if only every few months or so.

Could you clarify a bit on how the PXI-6528 was acting while you were seeing these problems? Does this card have values display on the Remote Front Panel, and if so were they still updating properly? I believe you were saying that, but I wanted to be sure because that makes a big difference.
If everything became static, including the DIO card, at the same time, then I'd say see if your browser updated, or something in your network settings was changed without you noticing. Perhaps an update ran and reset some of your firewall settings, or an Internet Explorer update changed something that required a reboot.
If just the outputs of chassis 2 were the problem, and the DIO card values on your remote front panel still worked well, then it is most likely a problem with your MXI-4 cards or your fiber optic cable that cause the change in behavior.
Miles G.
National Instruments
Applications Engineer

Front panel USB connection to MB 990fxagd80v2

Hi Gents, new member here with some issues on me last build. I assemble my families computers , about one every 5 years. Other than that I am not hot in computers. So when I get into a build I have some homework and studying to do, and some glitches. At this moment my newest machine is up and running Win 7 with a few loss ends. My case is an USB 2.0 era with 2 ports in the front bottom behind a little door. Each USB cable has 3 wires ending in a flat 3 pin female plug. The motherboard has 2 USB male ports, 9 pins each, one coded blue the other red each one has an alignment notch. This MB came with a sack of M-connectors to be an easy transition between the front panel plugs and the Motherboard, so, 2 of the M-connectors are red and blue, and have alignment lugs that appear to be made for the USB ports on the MB. The problem is they do not fit. While I am gentle and careful I don't believe they fit. I have other front panel issues I'll save for another time. My Gazelle case seems to use different nomenclature than the motherboard. But the USBs are the issue now, anyone have some light on this subject? I would also like to convert one of the front USBs to 3.0.

"Each USB cable has 3 wires ending in a flat 3 pin female plug."
That can't be right as USB are 4 wire, red, white, green, black. Connectors are 5 or 10 pin plugs with no connection on the 5th pin not used on both types & 9 being the key on the 10 pin plug.
"I'm not sure is I have a variation from the standard MB or what..."
Any connectors, MB headers are standard throughout the industry therefore they will be the same from all manufacturers.
"or is the connection does not use m-connectors"
You should not need m-connector for USB anyway. m-connector was introduced mainly for front panel connections that had individual wires for each LED, switches and such. The set in the pic I show is from old P35 MB.
Can you post a photo(s) of the case connectors you have?
See here how to add photo's: https://forum-en.msi.com/index.php?topic=90789.0
Personally I use Photobucket to host my pics.
M-connectors for USB should be clearly marked as such if the MB even came with any for USB. Over the years they have eliminated some and I think the ones for USB were eliminated.
USB plug:

Front Panel Mass Binding Project Variables Issue

Hello -
When attempting to bind controls to shared variables through the front panel mass binding option, there is an issue where you can not seem to bind a "project item" to the control. The method of binding I am using is to export a text list of control names, urls, mode, and function to a text editor utilizing the front panel binding mass configuration options. The text editor shows, in the fourth column, a "0" for no function, a "1" for network item, and a "2" for project item. when attempting to import the list back into the front panel binding mass configuration, all "2" indications become "1", as all items are treated as network. Thus one can not effectively bind to a project shared variable item.
The binding works fine manually by means of utilizing the properties selection of the control, but it is difficult to do this for 821 controls, as in my application.
My application is based on a OPC served group of 821 variables which are linked to controls and indicators through the shared variable representation for each item created in the multiple variable editor.
Does anyone have a work around for this issue, as it is a showstopper right now, ie, you can not effectively bind a large quantity of controls or indicators to project located shared variables as required.
The rationale behind utilizing project located variables instead of network located variables is to reduce the amount of calls to the OPC server which was causnig a large latency in the refresh of the 821 items. With the items defined as shared variables within the project, a single call is issued, which has tremendously sped up the refresh cycle for the list of variables.
Thank you in advance for your insight in this matter,
John DeCroos

Hello Brian A.,
In response to you comment --
"in 2006, and John did not follow up with any more information for Efosa"
-- a great deal of information was provided to NI (Efosa and many, many others, up to the product manager for the DCS module). I have never heard back on a fix for this bug for the identified version of LabVIEW. The reply by Efosa here was well after we had shipped our product -- (please see date + Efosa's apology) -- we had found our own solution as is identified in the original post.
My solution was, as is also indicated in my original post, to manually bind each variable. This was unbelievably time consuming, but was all I had.
The version of software I am now working on uses far less variables, manually bound to avoid the multiple binding issue we had in the past.
I have checked the mass binding function in LV 8.5.1, it works fine now. I guess it would have been nice to have had a reply that the bug had been resolved ---- would have helped me out a bit.
Thank you,
John DeCroos

Mobile VI Front Panel Display issue

I am not sure whether I should report this as a big of Mobile Module, so post it here and see if anybody else encounters the same issue.
When create a mobile VI, if you put a TCP Connection control and String array on the front panel the same time, it won't run. It compiles and deploys all fine, but when you try to run it, it doesn't. And if you put it as a subVI, it will stuck when it is called.
Guess I am lucky. Just so happened that I needed to put both controls on the front panel and ran it as a subVI. Every time this subVI was called, the whole program stopped. It is a simple subVI call, but maybe it is so simple that it becomes so hard to debug. I started to check if the memory was full, then subVI property, and then put all kinds of breakpoints to debug. Finally, just when I ran out of debugging ideas, I was looking at all the controls on the front panel. Is it possible that one of those controls has some sort of conflicts with others, or the mobile module simply cannot load the type of control(s). So, I took one out at a time.
It took me a whole morning, but that's how I found this bug. I hope after I post it here, it can save your time to debug this type of bugs.
Attachments:
TCP Control.vi ‏10 KB

Hi, Paul,
This could be another bug of Mobile Module if you can repeat what I did.
Here is the issue. When I transfer time stamp from PC (time stamp flattened to string) to the palm (then unflattened back to time stamp), the time stamp on the palm is always plus one hour. Don't know if this is a bug or a programming error?
Thanks.

Fatal1ty Champion Front Panel I/O Issue

'Fatalty Champion Front Panel I/O Issue I just purchased a Creative PCI Express Sound Blaster X-Fi Titanium Fatalty Champion Series Sound Card. I have installed the card and front panel into my system with the latest drivers.
I am unable to get the front panel to work (the soundcard works fine). It has no lights, volume does not work and the mode selection does not work, in fact the only thing that works are my headphones. When I plug in my headphones my speakers mute and I get sound in my headphones. I have disconnected all connections and reconnected them ensure they are fully seated. I have reseated my card as well.
System Specs
EVGA X58
2G of 600 RAM
2 Vertex20 SSD?s in RAID0
DVD Player
GTX295 and a GTX8800
Dual Mon
Win7 x64 Ultimate
My system is extremely stable with no issues other than the new Sound Card. Here is the driver I used, Creative Sound Blaster X-Fi Titanium Driver 2.7.0007. I have also tried the Product Identification Module Update.
Any suggestions?

Thanks for the answer so fast.
I use win xp 32 bit,is there any solution for win xp
Product indentification module update
File Name : PID_W7PCAPP_US_2__0.exe
Requirements:
[color="#ff0000"]Microsoft Windows 7 64-bit, Windows 7 32-bit <
Sound Blaster X-Fi and X-Fi Titanium series of audio devices listed above<
Review and found this also
XFTI_PCDRVBETA_US_2_7_0008.exe
Fixes:
Resolves issue of Sound Blaster X-Fi I/O Dri'veBay not workingin Windows XP. <
But I have the same problem.
If you me that fix to you with that patch, I'll have to install win 7.
Regards

Dr. Damien's Development - The Xylophone Project X - Font Issues and Front Panel Layout

The Show Raw Data button was made active in this installment. Doing this in a robust fashion was more involved than one might think, due to font and platform issues (remember I want to port this to a Windows Mobile device eventually). The following changes were made.
The A frequency indicator was made active. This was an oversight from the last update.
A front panel object, XylophoneFP.lvclass, was created to hold the front panel references and methods.
The front panel object was used to implement the Show Raw Data button.
The front panel object was used to compensate for font issues.
When testing this application on Windows Vista, I noticed that the font differences between Vista and XP were annoying enough that I wanted to fix them. This will also lay the groundwork for any layout issues when porting to Windows Mobile. Usually, I create a cluster containing all my front panel references, but this time I put them into an object. Besides the usual object boilerplate, there are two methods, one to rearrange the front panel and one to show/hide the data graphs.
Once the controls and indicators are properly arranged, showing and hiding the data graphs is simple. VI server methods are used to find the edges of the outer controls, some whitespace is added, then the front panel size is reset. Arranging the controls in the first place is much more complex. Dialog controls are used, and these controls change size based on the default font size. Font sizes can change due to user preference or when using the application in a different operating system than it was developed in. Button sizes can also change due to localization.
This problem is difficult to solve cleanly, and the VI which does this, XylFP.lvlib:XylophoneFP.lvclass:ArrangeControls.vi, shows the problem. It relies on the actual sizes of the controls/indicators to rearrange the front panel in a hopefully pleasing fashion. Even though this is a relatively simple UI, the VI is fairly complex. It uses VI server calls to determine the current sizes of controls and then rearrange them. If you choose to do something similar, consider the following hints:
The Bounds property of all controls is not writable. To change the size of controls, you need to find the property or properties which change the size. There may be more than one (which is why Bounds is not writable). For example, to change the size of a boolean, use the Button Size property.
In many cases, the property you use to change the size of the control will not be the same value as the Bounds property. Using the boolean again, the Bounds of a 3D LED include the 3D effect around the LED, but the Button Size only includes the LED itself. Comparing the Bounds property to the result of a query to the property you will be setting will give you the necessary offset to convert between the two.
Make sure you label your wires if you attempt to do things like this. Long wires are very common in this type of programming. It is difficult enough to keep track of things without the added aggravation of having the trace wires back to their source to identify them.
A few judiciously placed type converters can eliminate many type conversion dots. This is not usually a real problem in this context, but you should get into the habit of efficient programming.
I will be hiking through the mountains of New Mexico with the Boy Scouts for the next couple of weeks, so do not be dismayed if I do not reply to comments very quickly. However, comments and suggestions are still welcome and encouraged. I will reply when I return.
Previous Installments
Data Acquisition Concept
GUI Concepts
Specifications
Core Architecture
Data Acquisition and Note Analysis
Sound Acquisition Revisited
Sound Analysis
Configuration Dialog
Calibration Dialog
Message Edited by DFGray on 06-05-2009 03:09 PM
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
XylophoneX.zip ‏1259 KB

DFGray wrote:
I put the event structure in the command loop so that events are processed synchronously. In the past, I have run into a variety of race condition/synchronization issues when separating the event and command loops and prefer to keep them together to make the program structure simpler.
It is simpler but you give up any multi CPU performance. That LV is inherently parallel is one (the only) real advantage over a text based development system. I can write good structured text that is almost as visually easy to parse as LV. With modern syntax coloring engines, the difference in icons vs. structured text is not that great.
But the challenge I give the traditional text coders is to keep track of many mulitple threads. This is why dataflow is a powerful concept. Yes it does lead to asynchronous execution but if you impose synchronicity on your code you are working against LV. I get most first time programs where everything is in a sequence structure. "Just to be safe".
Of course this is much better but my first design goal is that any application should take advantage of a much hardware as possible, degrade gracefully on slower hardware and play nice with other running applications. This simpler structure severely handicaps that first goal.
In this case it is simple enough to "get away" with it since as you point out that there should not be anything that takes significant CPU time. But that may not be true on the PDA?
If you are going to run it on the PDA will we be discussing techniques to seamlessly use both NIDAQmx Base and NIDAQmx in the same system? That is a real challenge. I look forward to more of this!
Cheers!

X-Fi issue - front panel headphone j

Just replaced my aging Audigy OEM with an X-Fi Platinum yesterday. Sound quality is great and the system is stable, but I'm having a slight issue with the headphone jack on the front panel. When I plug in headphones, the system properly reconfigures the speaker setup for headphones and mutes the speakers. However, after 2 seconds, sounds start playing softly from the right front and subwoofer channels in addition to the headphones.
Any idea how I can fix the problem? All my connections seem fine and I'm using the latest official X-Fi drivers (not the Beta)

bump

Front Panel Audio Issues on both Z97 and X99

Hello,
I am an owner of a Z97 PC Mate and a X99s SLI Plus Mobo.
On both of these mobos, with the latest realtek drivers I cannot get front panel audio working.
I have also tried the MSI drivers for each mobo from the product pages.
I have "Disable front panel jack detection" enabled on both. If I disable this, it shows the jacks not being utilized.
The realtek hd manager shows that both the front panel headphone and mic jack are being utiliized, even with nothing is plugged in and if I have the front panel header disconnected from the mobo. On each model I made sure that HD Audio is enabled in the UEFI.
I feel that since I am having the issue on two seperate products that there is a similar issue between each that I cannot figure out. I do not have this issue on my ASUS Z77 Sabertooth.

Quote from: Nichrome on 02-May-15, 15:28:51
Hi
What is the case are you using?
Also are you sure you plug the front audio properly? Or if there are no bent/missing pins? I am on my 3rd MSI board (I switch a lot :D ) but all worked fine with my case.
Try using audio while either board is running on non conductive surface (e.g. wooden table or motherboard box). Might be something shortening the board.
I've tried both boards in all 3 cases I own.
NZXT Switch 810
Raidmax POS (Honestly don't know the name of it, but it has HD Audio connector)
Phanteks Enthoo Luxe

MSI GF615M-P33:Front Panel Jack headphone issues.

When plugged in front panel can't hear people talking in videos(no matter what software I use) nor mp3 files but I can hear music alright.
At the rear sound panel it works well.
I got the newest Realtek HD Audio Manager driver....

Found out that front panel jack place is a little bit up........If I put it in totally it sounds quietly.
I have to find a good "location" in female jack to have good volune....

Qosmio F50-108 - Front operation panel issue

Hello, I have qosmio F50-108 and the front panel does not work me, I think I uninstal a program. Please link to the driver. thanks akem
sorry for my bad english

Hi Akem
Sorry but I dont understand what you are meaning exactly by front panel?
Do you mean the Toshiba Control buttons like (play, pause stop, etc)
If you are meaning these buttons and if you have removed an drivers which controls these buttons then a solution should be easy.
First of al you should try to set the OS back to the early time point before you have removed this driver. For this you have to use the system restore utility.
Secondly if the procedure described above will not work, try to reinstall the VAP (Value Added Package).

Front Steel Panel Issue

Hey, i have a strange problem with E6 Front Silver Panel... whenever i change the memory card the panel near the memory card slot bends a little and now its finally totally bent. Nokia guys changed the phone once but are not ready to accept the fact again.. any ideas ?

Hi Akem
Sorry but I dont understand what you are meaning exactly by front panel?
Do you mean the Toshiba Control buttons like (play, pause stop, etc)
If you are meaning these buttons and if you have removed an drivers which controls these buttons then a solution should be easy.
First of al you should try to set the OS back to the early time point before you have removed this driver. For this you have to use the system restore utility.
Secondly if the procedure described above will not work, try to reinstall the VAP (Value Added Package).

Open front panel of sub vi when called - how?

Hello,
I have a VI with several sub VIs.
I want some of the sub VI front panels to be opened, if they are not yet opened and if they are called but I want them to stay in the background.
There are two SubVI Node setups: "Open Front Panel when loaded" and "show front panel when called"
Both are not what I want. If I select "show front panel when called", then the front panels are opened but flickering because they are called often and alternately.
Greetings Johannes
Using LabVIEW 7.1 and 2009 recently
Solved!
Go to Solution.

johanneshoer wrote:
No, no issue with my code :-)
Yeah, we've heard that one before...
@smercurio_fc: With your example I can see if a subVI is opened or not, but how can I open the subVI during run time if it is not opened
Just call the method with it set to "write" (right-click and select "Change to Write"). I don't recall if LV 7.0 has a Front Panelpen method. Check the LabVIEW manual.

Front panel issues

Similar Messages

Maybe you are looking for