M
Mikko Kiviranta
Guest
Dear Colleaques,
Checking the manufacturer-specified S-parameters of the
Infineon BFP640 transistor I noticed that the values at the
low-frequency end look funny. For instance, at 100MHz
(Vce=2.0 Ic=2.5mA) S22 = 0.9995<-3.0 which would translate
into 18ohms with 0.8pF in series, or alternatively 200kohm
with 0.8pF in parallel. This does not sound like a collector
of a decent BJT at all!
What am I seeing? Could it be the dc-blocking capacitor
of the network analyzer used by Infineon? At 500MHz
(Vce=2.0V, Ic=2.5mA) S22 = 0.9699<-14.4, or 48ohms with
0.8pF in series, which would support the dc-block
hypothesis.
But then again, for (Vce=3.0, Ic=20mA) Infineon gives
S22 = 0.9892<-7.5 at 100MHz, or 63ohms + 2.1pF,
and at 500 MHz S22 = 0.7818<-32, or 68ohms + 2.1pF.
Changing the DUT bias point would change the size of
the NWA dc-block? Not very assuring. Besides, publishing
S-parameters which would not reflect the properties of the
DUT but would rather be dominated by the setup parasitics
does not sound what a professional company like Infineon
would do.
Taking randomly another device, the Infineon BFP620F,
I notice similar behavior. For Vce=2.0V, Ic=2.5mA
S22 = 0.9978<-3.2 at 100MHz and S22 = 0.9599<-15.9
at 500MHz. Again S-parameters I would not expect.
Take another manufacturer: Philips BFG425W is specified
(Vce=3.0V Ic=20mA) with S22 = 0.935<-8.3 at 100MHz, i.e
260ohms+2.8pF or , and S22 = 0.720<-32.8 at 500MHz,
or 78ohms + 2.5pF. Again a stange series capacitance,
or
Phase accuracy of the network analyzer would make
the readings at extreme S-parameter magnitudes unreliable,
of course, but the question is why a BJT would show such
extreme parameters at all. A nicely-behaving example
is the Agilent MGA-82563 with S22 = 0.16<-99 spec (or
50ohm in parallel with 10pF) at 100MHz. Agreed, it
is not a bare BJT, but I wouldn't expect it to differ
that radically.
So, what's going on here? Do manufacturers knowingly
publish data dominated by the dc-blocking cap? I can't
imagine this being any sort of resonance of the package
parasitics, either, as 100MHz should be effectively dc
for these devices. I guess I'm missing something very
simple and obvious here...
Regards,
Mikko
Checking the manufacturer-specified S-parameters of the
Infineon BFP640 transistor I noticed that the values at the
low-frequency end look funny. For instance, at 100MHz
(Vce=2.0 Ic=2.5mA) S22 = 0.9995<-3.0 which would translate
into 18ohms with 0.8pF in series, or alternatively 200kohm
with 0.8pF in parallel. This does not sound like a collector
of a decent BJT at all!
What am I seeing? Could it be the dc-blocking capacitor
of the network analyzer used by Infineon? At 500MHz
(Vce=2.0V, Ic=2.5mA) S22 = 0.9699<-14.4, or 48ohms with
0.8pF in series, which would support the dc-block
hypothesis.
But then again, for (Vce=3.0, Ic=20mA) Infineon gives
S22 = 0.9892<-7.5 at 100MHz, or 63ohms + 2.1pF,
and at 500 MHz S22 = 0.7818<-32, or 68ohms + 2.1pF.
Changing the DUT bias point would change the size of
the NWA dc-block? Not very assuring. Besides, publishing
S-parameters which would not reflect the properties of the
DUT but would rather be dominated by the setup parasitics
does not sound what a professional company like Infineon
would do.
Taking randomly another device, the Infineon BFP620F,
I notice similar behavior. For Vce=2.0V, Ic=2.5mA
S22 = 0.9978<-3.2 at 100MHz and S22 = 0.9599<-15.9
at 500MHz. Again S-parameters I would not expect.
Take another manufacturer: Philips BFG425W is specified
(Vce=3.0V Ic=20mA) with S22 = 0.935<-8.3 at 100MHz, i.e
260ohms+2.8pF or , and S22 = 0.720<-32.8 at 500MHz,
or 78ohms + 2.5pF. Again a stange series capacitance,
or
Phase accuracy of the network analyzer would make
the readings at extreme S-parameter magnitudes unreliable,
of course, but the question is why a BJT would show such
extreme parameters at all. A nicely-behaving example
is the Agilent MGA-82563 with S22 = 0.16<-99 spec (or
50ohm in parallel with 10pF) at 100MHz. Agreed, it
is not a bare BJT, but I wouldn't expect it to differ
that radically.
So, what's going on here? Do manufacturers knowingly
publish data dominated by the dc-blocking cap? I can't
imagine this being any sort of resonance of the package
parasitics, either, as 100MHz should be effectively dc
for these devices. I guess I'm missing something very
simple and obvious here...
Regards,
Mikko