Removing front panel board of a PowerMac G5

hi,
i need to attach a relais to the power button of a PowerMac G5 (the recent ones with dual core) so that it can be switched on remotely. i've done this before on a G3 which was quite easy.
the G5 however seems to be a beast. the board enclosure seems to be glued(?) to the front of the G5, at least there are no visible screws or latches. i found this article:
http://manuals.info.apple.com/en/PMG5FrtPanelCableDIY.pdf
but it says nothing about removing or opening the panel itself. i'm rather bad with soldering and i've never done SMD soldering, otherwise i'd just go directly to the front panel connector on the main board.
there must be some easy way to remove the panel, no?
thanks for help! best, -sciss-

hallo,
the energy saver option does not work. if the computer is shutdown normally, taking away the power and re-applying power will NOT power up the computer. this option unfortunately seems only to work when the computer is hard-shutdown (just taking away the power and not shutting the system down) ... since i need to do clean up and also because there will certainly be problems one day, hard power off is not an option for us.
-sciss-
Mac OS X (10.4.7)

Similar Messages

Can't remove Front Panels in Application Builder

I have had a few issues using Application Builder (v7.1) in regards to it removing or not removing front panels for my subvi's when I was trying to compile. Here are the conclusions I came to if anyone else runs into the problems I had.
Problem 1) Some of the front panels were being removed for dynamically loaded VI's, which were not set as dynamic VI's in the Application Builder, but which were static-linked VI's in the program (so they were loaded in memory as linked subvi's but called dynamically). When the Application Builder decided to remove the front panel for those VI's, there was an error when loading them dynamically.
Problem 2) Some of the front panels were NOT being removed for subvi's that I didn't want to have their front panel built into the compiled program. Loading front panels that are not needed uses extra memory, but there was no way to change the option to not load the front panel for certain particular subvi's in Application Builder--the option was grayed out.
For problem 1, I decided not to worry about linking the files dynamically in the Application Builder, but to just make sure the Application Builder would include their front panels. For problem 2, I had to figure out what was making Application Builder force the front panels to be included when I deemed it unnecessary, so that I could fix them not to be included. Basically then, going through my VI's that were forcibly included, I came up with a list of stuff I began checking for each time I would run into one where I didn't want to include the front panel. I have attached my list to this post.
My solution for problem 1 was then to use a customized appearance for my static-linked / dynamically loaded VI's, and disable the menu bar (forces the front panel to be included by Application Builder without changing appearance, since I never actually see the FP). My solution for problem 2 was often to remove property nodes referencing text on the front panel controls. Sometimes I was able to perform a numeric->text or enum->text conversion instead of referencing the text of the control itself, and sometimes I realized I didn't want anything to change and that it was ok to include the front panel so I could (for example) get a list of strings for my enum control.
I have attached the reference list I came up with of things to check for to make sure your VI properties are set correctly if you are trying to get Application Builder NOT to include the front panel of your subvi. The list might not be complete, but it's helped me to narrow down things very quickly and find the problems I was having.
Attachments:
ThingsToCheck.doc ‏61 KB

m3nth wrote:
Problem 1) Some of the front panels were being removed for dynamically loaded VI's, which were not set as dynamic VI's in the Application Builder, but which were static-linked VI's in the program (so they were loaded in memory as linked subvi's but called dynamically). When the Application Builder decided to remove the front panel for those VI's, there was an error when loading them dynamically.
This is expected behaviour. The application has no way of knowing that these VIs will at some time be called dynamically. That would require analysing and understanding the entire program and in cases where you calculate the dynamic VI to be called at runtime it still wouldn't be feasable to do so.
m3nth wrote:
Problem 2) Some of the front panels were NOT being removed for subvi's that I didn't want to have their front panel built into the compiled program. Loading front panels that are not needed uses extra memory, but there was no way to change the option to not load the front panel for certain particular subvi's in Application Builder--the option was grayed out.
There are several reasons why a front panel is needed. One of them is when the VI is called dynamically, even if the FP is never displayed and AppBuilder will account for that for VIs which have been added as dynamic VI to the project.
The other is when a VI uses some Property Nodes or Attribute Nodes as they are called now.
So to solve your problem 1) you could also just drop some property node in the diagram of such VIs and be done with it.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Pin assignment (front panel to mainboard connection)

Hi, does anyone know the correct pin assignment of the front panel? Got a g5 in pieces and I want to reassemble it. I know there is a cable for replacement but I don't wanna buy it - using spare parts instead.
Help much appreciated

Hi lebom, and a Warm Welcome to Apple Discussions and the Power Mac G5 Forum!
This may help...
Front Panel Board Connector
Pin# Signal Type
1 25V
2 V-GND
3 FW TPA Twisted Pair Shield 110 Ohm
4 FW TPA + Twisted Pair Shield 110 Ohm
5 CHASSIS GND FW
6 CHASSIS GND USB
7 FW TPB Twisted Pair Shield 100 Ohm
8 FW TPB+ Twisted Pair Shield 100 Ohm
9 USB PWR
10 USB GND
11 USB Twisted Pair Shield 60 Ohm
12 USB+ Twisted Pair Shield 60 Ohm
13 LED
14 PWR BTN
15 AUDIO SENSE
16 AUDIO COM Twisted TRI
17 AUDIO RIGHT Twisted TRI
18 AUDIO LEFT Twisted TRI

Z87-G43 Board Front panel USB Problem

I have installed the board and windows 7 64bit
Updated the Bios and checked everything I could. I do NOT get the connect tones from anything I connect to the front panel USB ports. I have used 2 (KNOWN GOOD, works on other machines) connector sets with 2 ports each, and ALL of the ports have the same symptoms. All of the usb devices have the connect tones when inserted to any of the rear ports. I have not tried the USB3 port for the front because I do not have the wiring and related header connector. My phone, (Samsung GS4) when connected to the rear ports always opens an explorer window showing the Ext SDCard and the Internal memory. when I connect to any of the front panel ports, no sound, no pop-up of explorer, but I do see the device when I manually open explorer and can open the connection manually.
I am at a loss as to what is not right and how I can make it work correctly. If anyone can give me any information to correct this, I'd be very grateful. (Tech Support was no help)
Thank you, and Aloha From Hawaii!

Thank you for your reply.
I have an older Antec Case and I have tried a brand new front panel connector I got from Frys and it acts the same Way. the only difference is that the connector is a one piece assembly that connects directly to the mobo header pins. the one in the case has individual pin connectors. both systems end up with the same scenario. When I plug in a thumb drive, there is no connect or disconnect sound and I still can manually open explorer and access the thumb drive or my phone but nothing pops up to signify any port access.BTW, I am a systems engineer and have spent the last 13 years building machines for a transportation company (bus) My previous board in the same case used the front panel connection and it worked just fine, but since the board died and was only supportive of XP I decided to upgrade to Win 7 64bit and have 16gb ram. All the rear connectors work just fine, but I need all of them so have to use the front panel connection for phone, and thumb drive access. I suspect the mobo has a design problem. The tech support person had no suggestion to correct this problem too! :<(

I have a powermac dual g5 2.0 that wont start up.When I plug it in I get the click from the power supply. When I hit the start button, the white led on the front panel lights up and stays lit. No whir sound from the hard drive or the fan. No lights on the

I have a powermac dual g5 2.0 that wont start up.When I plug it in I get the click from the power supply. When I hit the start button, the white led on the front panel lights up and stays lit. No whir sound from the hard drive or the fan. No lights on the motherboard

The click usually indicates a big problem, but...
How to reset the SMU/PMU on a Power Mac G5 (Late 2004) or Power Mac G5 (Late 2005) ...
http://support.apple.com/kb/HT1436
Earlier G3, G4, G5 models...
http://support.apple.com/kb/HT1939
Might be time to replace the PRAM Battery, 4 years is close to their lifespan, far less if ever without AC power, & can cause strange startup problems...
See which one your G5 has...
http://eshop.macsales.com/item/Newer%20Technology/CR2032/
http://eshop.macsales.com/item/Newer%20Technology/BAA36VPRAM/

Help with front panel audio on K9N board.

Okay, I admit I'm a bit of a moron with front panel audio but I just can't figure out how to configure this board with my case. Here are the pins:
Case:
Mic In
Mic Bias
SpeakOut L
Return L
SpeakOut R
Return R
Ground
Motherboard:
PIN    SIGNAL      DESCRIPTION
1    PORT 1L      Analog Port 1 -Left channel
2    GND      Ground
3    PORT 1R      Analog Port 1 -Right channel
4    PRESENCE#     Active low signal -signals BIOS that a High Definition Audio dongle is connected to the analog header. PRESENCE# = 0 when a High Definition Audio dongle is connected.
5    PORT 2R      Analog Port 2 -Right channel
6    SENSE1_RETIRN     Jack detection return from frontpanel JACK1
7    SENSE_SEND     Jack detectionsenselinefrom the High Definition Audio CODEC jack detection resistor network
8    KEY      ConnectorKey
9    PORT 2L      Analog Port 2 -Left channel
10    SENSE2_RETIRN     Jack detection return from frontpanel JACK2
I haven't been able to make any sense of the two, so if anyone here can help, I would appreciate it very much.

Quote from: crazy on 09-June-06, 15:51:46
You may tell us more information about your mainboard, please give us the detailed name of your mainboard. :D Then there will be more users could give some suggestions.
Sorry, there aren't that many K9N boards out there, but mine is the K9N Platinum MS7250 Version 1.0. It's the AM2 non-SLI nVidia nForce 570 Chipset model.
Thanks for any help.

"The VI's front panel may have been removed."

I was running my program in the development environment and had a sudden exit from labview (w/o a microsoft crash dialog).
So I start labview, file recovery comes up so I recover all and then save all (don't remember if it involved the file in question).
Now a subVI is throwing this error every time I try to open it:
Everything seems to be working and no broken run arrows, etc., but I can't get it open and I need to. Anyone know how to recover from this?
-B
bah! I meant to post this in LabVIEW. Can someone move it?
Message Edited by blawson on 10-22-2009 01:00 PM
-Barrett
CLD

Cross-posting a similar problem: Unable to display the Front Panel of a VI
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

LEDs on front panel

Employed my Vista Pavilion for several years without incident until last night when I noticed the top "on/off" button which usually glows a light blue was unlit.   I originally assumed a power glitch, so I just restarted the machine to note the following:
    Fans come on and the power supply seems OK, but the system did not boot.   The screen was just black with no characters or image/background. In fact, the screen's power saving mode soon engaged indicating the video card was not sending a signal. Never get to the BIOS screens.
     Now here is what I think may be significant: the green LED and blue LED in the front console were on continuously.
Sometimes, hardware manufacturers provide diagnostic information by way of the lights (e.g., washing machines).   In other words, turning on LEDs can provide state information. Is this true with HP hardware?
Some more clues which tell you what is not the problem. I happened to have a new power supply handy, so I traded it out with the same results.   In normal operation, the green LED indicates disk activity, so I just removed the disk entirely to see if the green light would go out.   Nope, still on steady.   The blue LED typically implies the WiFi operation but I rather doubt at this pre-boot state the WiFi would be working.
I traced the power button line (two grey wires) to a half-sized board in the rear. No breaks in the wire or bad connections.
Any ideas?

HP Pavilion Elite m9357c Desktop PC
Motherboard Specification, MCP61PM-HM (Nettle3)
http://h20564.www2.hp.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-c01357175
Don't understand this reference to a half-height board.
The Front Panel Header (9-pin, 2x5) on the motherboard is where those front panel LEDs and buttons are terminated.
EXAMINE Pictorial in the Internet link to motherboard (above).
HOWEVER, some HP Desktop models have a front LED to show the user of LAN or Wi-Fi connections.
That wire would connect to the network card or motherboard via a different connector.
Some Media PCs of this era (2008) had Infared connections (option) for remote control of TV tuner option card.
LEDs do not last forever (have a long, but finite life) and can fail due to DC over-voltage or surge conditions (environmental, component failure).
In addition, this Desktop PC is now 7 years old .... a long-life for any desktop.
IF the motherboard has failed (component failure, such as capacitors), then replacement may be best advice.

Save and recall front panel configuration on FPGA

First of all, I am a first time user of Labview. The application is with an FPGA on a NI-9146 board.
My question is, I would like to save the front panel settings when I exit the application, then recall them the next time the application is started.
Seems to be a few ways to do this but are not supported with the FPGA module.
The application is fairly straight forward timing and the Windows host PC will provide a GUI to the operator.
Solved!
Go to Solution.

Someone may correct me if I'm wrong, but this task is more tedious then it needs to be.
The normal way of doing this on the FPGA is to plop down a FPGA read function for every control on the FPGA front panel, then write them to a file. Probably using an OpenG function, but really something like the binary write would work if you don't expect to add/remove items. Then when the application starts you need to reverse the process ploping down a FPGA write function for every control.
Now there is a slighly easier way that in theory works in a limited use case. The FPGA VI when running is just like a normal VI and you can get a reference to it. Here you could run the OpenG Write Panel to INI, and Read Panel from INI. These are two canned functions that save tons of time. Now the reason this might not work for most FPGA developers is because in the end, the goal is to not see the FPGA VI and instead only run the bit file and call into the FPGA using the hooks NI provides. It sounds like you are going to have the VI shown anyway so this method may actually work for you.
It does kinda suck and I think it would be nice if NI had a way to read and write all FPGA front panel controls at once for things like this.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

NI DC Power Soft Front Panel Error - 200247

Hello All,
I am having trouble opening the ni DC power soft front panel. The error message I repeatedly am seeing is below:
When I try to run the vi mentioned in the error above, the same error occurs:
How can I go about getting my soft front panel to work? I have been using the DC power API to execute tests over the past week using the example VI's, but am at a point where the soft front panel would be very helpful to my workflow.
I am using the following:
NI PXIe-4139 SMU
NI PXIe-1082 Chassis
NI PXIe-8360 Controller
Windows 7 64bit
Labview 14
MAX 14.5.0f0
DC Power 14.2
I have tried running the soft front panel using clean installs of DC Power 14.1 and 14.2 and see the same error message. I have uninstalled the other modular instrument driver packages on my computer, NI-Fgen and NI-Scope, reinstalled DC Power, and still I see the error message. It could be that I am not uninstalling these software packages 100% correctly (I use the windows add/remove to NI Remove software dialog process....)
I appreciate any help getting this DC Power soft front panel working.
Thank You,
Andrew Goett

Hi Andrew,
Can you possibly give me a MAX technical report for your system? The instructions can be found here. Use Method 1.
Also, can you check which version of niModInst.dll you have on your system? This file can be found here: <Program Files>\IVI Foundation\IVI\Bin\niModInst.dll
Right-click on the file, select Properties, and then click on the Details tab. The information I need is the "Project version" field. See the image below:
In addition to the MAX report, could you send me a ZIP file of the contents of this folder: <Program Files>\National Instruments\Shared\niModInst
I've attached a simple program (NI-ModInst Code.vi) to test if NI-ModInst is failing across the board or if it only is failing to identify NI-DCPower devices. Open the program, select a driver that you have installed on your system, and run the program. The code should tell you the number of devices you have in the system that are associated with that driver, as well as list out the model numbers for those devices. This list will include simulated devices. Test the code with various drivers in your system to see if you get the same error.
Let me know how this works out.

MSI 180 front panel not working in both modes

hi,
I bought a msi mega 180 with AMD cpu, works quite nice for a barebone
Now the problem is the front panel doesn't work anymore. It worked before, but now it doesn't work anymore. I think nothing is changed.
I thougt the panel was broken, so I replaced it by a new version at an officiele msi distributor in NL, I placed the new panel. But nothing happened on that panel, on pc and hifi mode.
So I think the barebone is broken, anyone can tell what to try before I can conclude the barebone (motherboard) is broken?
btw, it's connected by 2 connectors, 1 looks like an audo connector the other one looks like a normal connector to me.

Hi,
I don’t think the front panel or the main board is broken I think its something else we haven’t figured out and MSI not willing to help us... I have Mega 865 and I have been having the same problem for almost 3 weeks now... sometimes it works and sometimes it doesn’t in both modes everything else will work normal except LCM.
Once it works will work perfectly until I unplug the power from the computer then LCM display will not start.
The problem begins when a hardware is installed the first time to get the problem I had just installed a pinnacle TV tuner when I took it off it came back the second time i installed a DVD rom but when I took it out still didn’t work I removed almost everything checked all cables and changed memory couldn’t get it work then I decided to put back everything TV card, DVD-rom, same memory back and still didn’t. Since it had happened before i was not convinced that it was broken then the second day I put the computer on and it worked on its own.. Now it works when ever it feels for it and take the day whenever.
Let me know if you find anything helpful.

While loop with stop button within event structure locks up front panel.

I am not sure if this is a bug with my program or a bug within LabVIEW. If you believe that this is a bug with my program then I will post my program to be looked at.
The problem I am having is there is a while loop within an event structure that fires when a particular value changes. Once the "Activate" button is pressed the while loop within the event structure starts going with a polling frequency of 1hz (1000ms wired to the "wait till next ms multiple" vi). There is a "Deactivate" button that is wired to the stop control of the while loop and an outter while loop that resets the event structure so that the activate button is being listened to again.
Once inside the while loop, however, none of the button are responsive within the front panel. The VI continues to run, and only 60% of my CPU is being consumed, but none of the button or scroll bars work. The only way for me to terminate the program is with the "Abort" button next to the "Run" button. If I remove the event structure so that the while loop in question runs as soon as the program starts, the front panel remains responsive. I've inserted probes within the while loop and verified that it is not running prior to the "Activate" button being asserted, and it is running after the assertion of the "Activate" button with the expected polling frequency set by the "wait till next ms multiple" vi.
Can anyone help? Do I need to post my code?
-Nic

It is typically not a good idea to stall an event structure by placing loops inside event cases. What good is an event structure if it is not free to repond to events?
Have a look at some alternative solutions, such as in the following link:
http://forums.ni.com/ni/board/message?board.id=170&message.id=224817#M224817
LabVIEW Champion . Do more with less code and in less time .

Noise when using Front-Panel headphone j

This message is for those who may experience noise in headphones plugged into a case's front jack. These noises would likely be heard if one uses a quality phone set with good isolation. (not noise cancelling type) and during quiet times, such as when no music or other audio source is being played, or perhaps when listening to programming with very high dynamic range and the frequent, very low loudness passages of music, etc.. There is no problem with the card. (I'm using an Xtreme Gamer card) The problem will be with the header panel on the case itself. You need to isolate the case ground from the other grounds coming in from the various board headers, such as USB, the sound card, etc. I accomplished this by scraping away the foil from around the stud landings on the panel module board. Of course you need to exercise care when performing such a modification but you will be rewarded with absolute, golden silence, when that's what you should be getting. Again, there is NO problem with the card.

If it is possible to remove the circuit board assembly for the front panel jacks from the case, you can see how the circuit foil "traces" on the board are connected. In my situation, and probably yours, you may find that the mounting screws that hold the circuit board to the computer case will also have the foil traces under them and that those traces will be a common ground to the rest of the circuits on the board. The problem arises because the computer case ground is at a somewhat different "signal" level than the grounds coming into the circuit board from the various "header" connectors, that is, the connectors you mate with the corresponding pins on your sound card, as well as the USB pins, if you choose to hook them up too. There is a great deal of strange noises that can be present in a given motherboard's circuits and associated grounds. All the ground connections from the headers coming into the board should only go to the individual connectors on the front panel. I cut away the foil paths where the grounds were all run together on the circuit board, thus isolating them from one another, as well as cut away the foil under the mounting screws. You may even have to cut foil from both sides of the board, depending on your model. You need to take care not to open up a circuit when making those cuts. A good, sharp Xacto knife or utility knife should work fine.
I found it strange that the designers of the board didn't consider the problem of "ground loops", which is what the problem is defined as. Ground loops, as you can see now, can happen when when a circuit or even separate components altogether, such as a computer, TV and HIFI system are all connected together. In the?HIFI setup case, hum results because the point of incoming cable ground for your TV and/or Internet are at a different 60 Hz voltage from the ground in your home's wiring,?to which your computer is connected for power. This causes a current to flow through the audio cable shields that is large enough to induce a voltage into the audio equipment. I've even heard of ground loops so bad that people have seen sparks when trying to hook up the audio cables between the pieces of equipment. Almost anyone who has a system hookup such as I described has run into that problem of hum when using their computer's audio into their HIFI setup. The only relief is to get some type of ground "isolator" that connects between the incoming cable and your TV and/or Internet cable modem. A quick and dirty solution is to use a grounding adapter in the AC connection for your computer and other equipment that uses a grounding plug. This, of course, is not recommended, but will kill the hum for now. I thought I would throw in the HIFI setup hum problem since, as I said, many people are suffering from that problem.
Even if the header grounds were all shorted together, the problem would be no where near as bad as having the case ground shorted to the header grounds, which was the way mine was made.
I know this is a looooonnnnnng winded post but trying to explain something like this in writing is not easy. Hopefully you will now have a better understanding of what I meant the first time, even though it was by no means a short post either.

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.

Closing references to front panel objects

Short version of my question: are programmatically generated references to front panel objects (controls, etc.) automatically disposed of when the VI exits?
More details: I'm recursively retrieving references to all the controls on the front panel. (I say recursively because I'm also getting the individual controls from clusters, subclusters, and so on.) I then return an array of control references, which does not include the references to clusters--only standalone controls or the actual controls themselves contained in clusters.
Do I need to explicitly close the references to clusters that this VI generates, or is it unnecessary since the VI will run briefly, return an array, and then exit?
Or another scenario: in a subVI I open a reference to the parent VI. Do I need to close that reference at the end of the subVI, or is it pointless because the reference will be disposed of when the subVI exits anyway?
(I did find this article, which I think addresses my question, but I'm not sure.)
Thanks,
peppergrower

http://forums.ni.com/ni/board/message?board.id=170&thread.id=159571&view=by_date_ascending&page=1
Jean-Marc
Jean-Marc
LV2009 and LV2013
Free PDF Report with iTextSharp

Removing front panel board of a PowerMac G5

Similar Messages

Maybe you are looking for