diyAB Amp - The "Honey Badger"

Running out of ideas

Me too.

As you replaced both the input and the power devices by some others with basically different principles of operation, I'd say you have got quite another amp that, perhaps and at it's best, just might resemble the Honey Badger, but isn't it anymore. I'm sure, though surely being no guru in that, it may need another compensation strategy, if not a complete another schematics that fits to your devices better.

As this discussion here strongly tends to get somewhat confused, not to say shattered, I'd like to ask the moderators to move these off-topics to another thread, in favor of keep staying on topic. We've yet got too much threads in this board where the running discussions no more have anything to do with the thread topics, e.g. the thread on Apex' 100W Ultimate Fidelity Amplifier - and many more. Thank you.

Best regards!
 
Member
Joined 2006
Paid Member
Has anyone looked at alternate VAS topologies for the Badger?

I added a buffer between the VAS and EF2 OPS of a very badger-like amp. Douglas Self shows such a buffer as figure F in his diagram of possible VAS variants:
dpafig11.gif


This keeps the VAS transistor sinking a near-constant 3mA. From the VAS' point of view, the buffer makes the EF2 look a lot like an EF3, a much lighter load. Could we call this an EF2.5 output?

Before and after schematics are attached. Q14 and R11 are the additions. I also adjusted the CCS feeding the VAS from 4.5mA to 9mA. (The VAS with output buffer can sink more current, shouldn't we be able to source more too on the other side?) The new version simulates with a lower distortion floor, about 10db lower. It's not a bad return for adding two elements.

Note the SOA protection circuitry dumps current to the VAS transistor, not to the buffer.

It's playing now. Subjectively this mod seems to help the amp play into a 4 ohm load (Klipsch Fortes) that it was sounding dull with before.
 

Attachments

  • amp1.png
    amp1.png
    80.5 KB · Views: 739
  • amp2.png
    amp2.png
    78 KB · Views: 731

Hi Terry,
that is not the final V2.4 as doesnt have baker clamp diode.
I do not the background why lay file of badger is required here, but i have created a badger v2.4 clone layout, that matches the schema and OS's layout (more or less, silk font is vector graphics). can it help?

reg
Prasi..


i will read previous posts to understand...I apologize if i am walking forbidden territory...
 
Last edited:
Oops! The "EF2.5" OPS above oscillates, which can be fixed with emitter degeneration on the buffer. New schematic attached.

It was oscillating with no load, with amplitude ~100mV and at a few 10s of MHz. It wasn't enough to be destructive, but let's not gamble. The oscillation happens on the real amp, and you can see it in simulation by removing the load and putting 600nH of parasitic inductance in series with the Zobel network. The real amp has a nice long Zobel return wire back to the ground star, it must be 100s of nH at least.

What loop was oscillating? It's not the global NFB loop or TMC loop; if you break both of those with 1GH inductors, AC sim still shows peaking. My guess is that this is the well-known effect where an EF, or chain of EFs, can oscillate in the absence of enough load. Adding the EF2.5 buffer makes this amp more prone to it. You want EF3-like performance, the cost is EF3-like stability concerns.

Base stoppers at the drivers and outputs help some too. A base stopper at the predriver buffer makes stability worse in simulation, oddly.

The revised design is below. I also replaced the KSC1845s in the current mirror with transistors that are free of quasi-saturation behavior.

So there you have it, the EF2.5. It's near-EF3 performance, can be retrofitted onto an EF2 OPS by adding one Q and two R's. It's probably stable? Have fun :)
 

Attachments

  • ampy.png
    ampy.png
    90.3 KB · Views: 616
You're right. That puts a shelf back into the response roll-off at about 20MHz. Thanks. This design needs a clean RC zobel.
I think this confirms what I have been saying for a long time.
The inductance in the route from output devices through the output Zobel and back to the decoupling attached to the output devices needs to be kept low.
This means short leads, short traces, compact low loop area for the whole route from device and back to the device.
Remember the current MUST return to source. In this case for the output Zobel, the source of Zobel current is the output device.
 
Yes, and the Zobel network must not be connected after the output coil, across the speaker posts just for convenience, as it is to be seen sometimes.

Best regards!
This is the alternative Zobel arrangement proposed by Thiele.
Leach adopted it.
Cherry discusses it.

I don't know how much the extra inductance in the route will affect the Zobel performance.