Ancient_Hacker said:
Wear safety glasses.
But seriously, how about some diodes to clip the gate excursions? I
know, Spice says the voltages will track perfectly. IMHO asking for
2% tracking shows an awful lot of faith in the matching of dynamic
transconductances.
No need at all for transconductance matching. This is just a string of
cascoded cascodes.
Win,
I first thought that there could be some pb with mosfets' capacitance
mismatch, but there isn't: you start with high voltage, equally distributed
between all the MOSFETs (due to the 10M) which is then reduced by the
capacitive string, whatever the capacitance mismatch. Thus the voltage can
never exceed the peek voltage you choose and this relieve you from adding...
additional Fets.
It'd had been more painful had you wanted a positive ramp... (looking at the
datahseet)
Hmm, maybe even not since they are nicely avalanche rated. And their low Qgd
will help too.
So, resetting the output voltage will probably require no extra care.
My guess is that with such a low Qgd (6.5nC is 20V on 330p) that you can
probably lower the 330p, to maybe 100p, and reduce the capacitive string
"parasitic" current.
As for the ID falling at the end of pulse, it can only come from a
gate-source current but I think it's unlikely on a real fet: at 150V VDS
you're still well in the gate plateau and thus it can't be a CGS current.
Did you check your model on this point?
It's not clear to me where the ID prop delays and VGS prop delay/spike comes
from (not much time available) but I guess the Coss(s?) have something to do
there.
When I saw your first post about this "self dividing cascode" I thought yes,
that's the ticket. I still think it is. And pretty elegant too.
I started to build a spice sim, but the editor crashed before I had a chance
to save. Can you send me your file (I too run intusoft). That'll save some
of the time I'm short of ATM.