Monday, December 12, 2016

Repairing an Ampeg PF-500 part 2

I was able to install the IRS20957 IC and the amplifier did in fact come back to life! Unfortunately, after some length of time playing at high volumes, it cuts out - first intermittently with some static, then with a loud snap. A brief cool-down brings it back again, though. I wonder if it's not some of the other power supply-related components that are failing intermittently. I would need to run it hard for a while, then leave it on after cut out for a bit to see if it cools down and starts working again. If that's the case, my guess would be the power supply's MOSFETs might have suffered over-current, or I guess it could be that I did a bad job joining the 4227s to their heat sink. At this point, I have everything I need (including know-how) to quickly get into the output section and can do the supply section pretty quickly, too, so I'm not exactly lost in the woods.

I still have that replacement main PCB on order, too...

Updates coming as they are available! I'm working on a Champ 5F1 clone in the mean time.

Sunday, December 4, 2016

Repairing an Ampeg PF-500

I recently got the urge to buy a backup or easy travel bass amplifier so I didn't have to lug around my whole rack kit if I wanted to jam loud. I found a broken Ampeg Portaflex PF-500 on eBay and figured I could probably fix it, or at the very least, get hold of the replacement parts from an Ampeg service center. The following is the adventure:

The amp arrived with one of the two IRFB4227 power transistor cut out of the board and the holes for it desoldered. I ordered a few of that replacement as well as some of the main switch-mode power supply transistors and the main bridge rectifier, just in case. Some folks on forums like talkbass have suggested that the IRFB4127 could be used in place of the 4227, as it has higher RMS and peak current specs, but the turn-off delay is longer by quite a bit. Either way, the replacement transistors arrived and I set about replacing the known-bad one and figured I'd go ahead and desolder the other one while I was in there.

This is not a good picture of the power MOSFETs on the far left side of the chassis. They're a bit of a pain to get to in situ, so the easiest way to deal with it turns out to be trying to loosen the hold-down bracket and removing the heat sink. That may require removing the big heat-shrinked capacitor right in front of the middle screw; the amp came for me without the middle screw in place, so I don't know how the PO or his service tech dealt with that problem, as it also didn't look as though the cap had ever been desoldered. Maybe needle-nose pliers? An about 5mm deep 90-degree PH1 bit? I don't know.

Here's a shot of the switch-mode MOSFETs. The bridge rectifier is behind that. These are hard to get to for unscrewing, but a 10mm right-angle driver should be fine. These are actually working well in my board; the power amp disaster did not affect the power supply's outputs.

Worth noting - my transistor tester reported that the still-installed output MOSFET was still good! I'm not sure how that happened, but I saved the part just in case.

After installing the new parts, the amp powered on and passed its self-test. No sound output, though. Next step came testing to make sure the power supply was actually working. I got a case of the apprentice shakes and blew out both replacement output MOSFETs and let the smoke out of one of the diodes nearby.

That little dude right there is what died. Nobody around here has SMD parts like that in stock, so another order to Mouser. ER1D diodes are reasonably close to 1N4004s, so I bodged one in to continue testing while the correct part is on its way. I also swapped back in the one known-good 4227 and the one remaining new 4227, and got back out of fault land into an amp that just doesn't work right. At this point, I plugged headphones in and was surprised to hear my bass coming through them! So now at least I knew that the input board was not totally dead, the power supply was good, and both of my output MOSFETs were good.

Next came testing the output board. The red wires are the outputs from the power section, and the blue wires are the returns to ground. A simple check with a multimeter made plenty of beeps across, and hooking up a signal generator and oscilloscope revealed a good clear signal transmission. Okay, so now we know the input board is good and the output board (at least as far as the power amp was concerned) is good.

Next comes trying to trace the signal through the head. I did NOT feel like trying to tear out the input board, so I started at the beginning of the main board.

Into the input on a hacked-together speaker cable test rig was a 2kHz 0.2V sine wave. Whatever happens to that in the input board, it comes out on pin 7 of that connector. On goes the oscilloscope and hey! 2kHz on pin 7. Great, so the problem is now isolated specifically to the audio section of the main board. I turned off the amplifier and checked continuity from the big resistor next to the big toroidal inductor (L7, obscured under hot snot) near the output jumper (visible in both of the previous pictures on the bottom edges of each). I had continuity from there to the output jacks, so at least I knew that the traces were intact. Next came oscilloscoping at each marked test point on the main board schematic.
Input of C33: couldn't find it.
Pin 7 of U18: success! 2kHz right there.
Pin 1 of U18: 2kHz once again.
Output of L7: a small DC voltage offfset. No sine wave.

Okay great, that's a big swath of components that could have failed, but at least the two dual op-amps were good. In reviewing the schematic for potential test points, I noticed that there is only one more place that the signal actually passes through on its way to the output MOSFETs, and that's an IRS20957 audio IC.

I can't tell for sure that the IC under that "heat sink" is U1, but it looks to have the right number of pins to be the part.

That's where this repair job is right at the moment. I suspect that people who have PF-500 heads that have sound that "cuts out" but no fault light to go along with it are probably dealing with this IRS20957 IC failing intermittently. What's interesting about this amplifier's self testing is that it isn't failing on whatever is broken in that chip, at least not consistently. About half the time I had my bodged test lead connected to either the main instrument input, the preamp output, or the power amp input, the amp would fail to start. I never had any problems with it starting without the test plug inserted, and the preamp board was clearly okay with the 0.2V input amplitude, as it passed it undistorted to both the main board pin 7 input and the tuner out jack on the output board. Is it possible it was faulting because of additional load on the IRS20957? Who knows. I do know that that heat sink is hilarious. I also know that, at least according to the product example picture at Full Compass, the revision J board (mine is a revision C) doesn't even have a heat sink on U1.

I ordered a replacement IRS20957 and a few more IRFB4227s just in case I pooch up this board again in testing. The solder pads for the outputs are getting very tired, and the last time I tried to do a SMD (installing a pair of THS3092 opamp ICs into an MHS-5200A signal generator in place of the AD812s that came in it), I managed to destroy three of the sixteen traces on the board and had to do some very careful scrape-and-bodge work on the board; thus, I don't have a whole lot of faith in getting to where I can call this rev C board a finished, working, and perhaps most importantly, reliable project. Fortunately, that Full Compass link up there exists, so I have a (hopefully rev J) replacement main board on order to put in once I've finished screwing up the one currently installed.
I think this'll be a nice amplifier once it's done. It has a speakon output which should prevent future short-circuit damage while plugging or unplugging the speakers, and the rest of the device is in really good shape. I plan on giving it a good workout and comparison to my SVT-3PRO once the servicing mission is complete. In the meantime, I wait patiently for some delivery person to bring me a box of lil' black boxes...

Saturday, June 6, 2015

Not photos - problems with Windows Backup

On Friday, my Windows 8.1 PC began giving me errors about "bad image" for a file called wtsapi32.dll. So began my adventure down "oh where are my backup folders?" and "I hope this lasts long enough to get my user directory copied over." It did, and a windows refresh largely fixed my problems, much to the chagrin of the router, which needed to serve my steam library, creative cloud applications, and various other archives and executable installers.

That didn't quite fix my problems - my main drive kept reporting errors through the Windows action center, so I set about trying to fix that. That's when I noticed BIOS taking forever to finish POST. I cleared to defaults with no benefit, then had the bright idea to flash back to an older version. At some point, though, Asus made it so that the flash utility won't go backward. I had to then dig up instructions for USB BIOS flashback, which included "make sure the CPU and memory are unseated."

Yeah okay.

PROTIP #1 - Asus USB BIOS flashback does *not* require a bare motherboard for my specific combination of Z97-PRO/4790K/2x4GB Crucial Ballistix Sport/2x8GB Crucial Ballistix sport. I would imagine this is true for other Z97 and X99 boards (the X99 instructions don't mention removing components, while the Z97 instructions did).

So now with the 1304 BIOS reflashed, CMOS cleared, and things reconfigured, the computer stopped complaining. On to the backup problems.

When trying to use the system image backup option in Windows 8.1 pro, I would get started down the path and get an error about either the drive being unavailable or inaccessible. Neither of those things were true; I was able to copy hundreds of gigabytes over eSATA, Firewire 800, and USB2.0. After a lot of searching on errors 0x807800C5, 0x80780081, and 0x8078004F, I found a post at (click here if you want it) that went through some stuff, then someone mentioned EFI system partitions and Mac OS. 


Infosphere, my external backup drive, had been used previously on Mac OS X as a time machine drive. I don't know if that specifically causes the problems, but I do know Windows tends not to like drives with 200MB EFI partitions very much, as I had a bunch of flash drives that I had to gparted back to life after I jumped ship last summer. I didn't think there was any problem with the external HDD, though, as it had functioned just fine and I even remember it having worked as a system image backup destination before. That may have been something changed in an update at some point, but I think what is more likely is that I don't have Paragon HFS+ drivers installed right now. Regardless, I was able to use diskpart to nuke the existing NTFS and EFI system partitions and create a new single partition setup that immediately accepted a system image backup.

         CLEAR TIME 16:50

PROTIP #2 - always nuke your drives fully when changing platforms. I was up until 3am last night working on this and I'm fleshing out this post at 1am, having finished up downstairs about an hour ago. gparted, diskpart, doesn't matter - get rid of that stupid EFI partition on any disk upon which it has inserted itself.

PROTIP #3 - I have no factual evidence to base this one on, but all of my trouble started when I used Windows Movie Maker to produce video game footage. Learn premiere pro instead if you have CC.

Thursday, September 18, 2014

New Camera time

Pentax K-01. I have a backup body... it has better high ISO performance than my primary camera. Oops. Also it's fun to use!

The rest:

Sunday, September 7, 2014

Today's hike

Beautiful weather and decent light!

Great Salt Lake

Taken May 31, 2007. My Dad and I have made it a point to go to the various parks around the Great Salt Lake when I'm out visiting. In 2007, we went to Antelope Island, which more or less tops off the Oquirrh mountain range on the west side of the Salt Lake valley. The park itself is home to a fairly diverse mammal population, as well as some fascinating rock features thanks to the shoreline erosion from the old Lake Bonneville. Seen here, Dad's looking out at something out over or on the other side of the lake (I don't remember), though the picture makes it look like he's observing the rock with binoculars.

Note the horrible air quality - I brought down the blue luminance some to make it look more natural; without it, the picture looks like this. It only gets worse over time, as the state doesn't seem to care much about preserving the area for everyone.

Friday, September 5, 2014

return to "form"

I have a fantastic idea for "why do I have blog?" - it goes like this.

Each time I open Lightroom, I'm forcing myself to develop, proof, and upload a photo. I've been just tweeting them, but I think from now on, I'm going to post it here instead and write a little bit about it. Maybe give some context, some insight into the development process, or maybe just recount the day of the shoot.

To go back a couple days:

These doves were my friends in the spring of 2006. I had taken over classroom support management responsibilities and, with them, a desk and window in an office. I brought in a bird feeder, but it quickly became apparent that all I was getting were garbage birds. I tried filling it with black oil sunflower seeds instead, but nothing interesting was coming to eat. Then I forgot about it for a week or two and opened the window to see these two greeting me. They had started to eat the seeds that fell out of the feeder. I took it down and poured out its contents; for the next month or so, I had them as regular visitors. As long as I kept the window cracked about this far, they'd even let me watch them eat.

Photo was shot with a Pentax MX and I'm guessing the M50/1.7. I'd also guess Agfa color film, but I'd have to go find the negative to be sure - this is an old old old old old scan.