L
Admin
[Technical article / FAQ, rfforum Editorial Team]
A GaN PA datasheet that quotes a high Psat or efficiency often does it under pulsed conditions. Dropping that number into a CW link budget is how a thermal and efficiency miss gets blamed on "process variation." CW and pulsed are different products until the duty, pulse width, and case temperature are written next to the claim.
1. What the footnotes hide
- Pulsed Psat at 10% duty with a short pulse can be 1–3 dB above what the same die delivers in CW at the same case temperature, because the junction never reaches the CW thermal state.
- Efficiency and ACLR footnotes often assume a pulse train or a specific load; CW modulated drive at the same average power is a different thermal and trapping story.
- "Typical" vs "minimum" and the case-temperature reference (25 °C fixture vs derated hot) change the number you are allowed to design to.
2. Freeze list before you freeze a link budget
- Duty cycle, pulse width, and whether the Psat/efficiency line is CW or pulsed
- Case or flange temperature for that line; your heat sink vs the datasheet fixture
- Whether your waveform average power and PAPR match the datasheet test, not only the peak
- Derating: hot CW at your flange temp, not brochure room-temp pulsed
3. Habit
Never paste a datasheet Psat into a CW budget without duty and temperature in the same cell. Archive CW vs pulsed note, duty, and flange temp next to every power claim. If the datasheet is pulsed-only, measure or derate before you promise CW EIRP.
4. Practical gate
- Highlight CW vs pulsed on the datasheet page you design from
- Ask the vendor for CW Psat/efficiency at your flange temperature, or measure it
- Budget thermal headroom explicitly; do not hide it in "implementation loss"
Discussion: on your last GaN power miss, how much was CW-vs-pulsed vs heat sink — and do you require duty + temperature on every datasheet number that enters a budget?
— rfforum 编辑部 / Editorial Team
A GaN PA datasheet that quotes a high Psat or efficiency often does it under pulsed conditions. Dropping that number into a CW link budget is how a thermal and efficiency miss gets blamed on "process variation." CW and pulsed are different products until the duty, pulse width, and case temperature are written next to the claim.
1. What the footnotes hide
- Pulsed Psat at 10% duty with a short pulse can be 1–3 dB above what the same die delivers in CW at the same case temperature, because the junction never reaches the CW thermal state.
- Efficiency and ACLR footnotes often assume a pulse train or a specific load; CW modulated drive at the same average power is a different thermal and trapping story.
- "Typical" vs "minimum" and the case-temperature reference (25 °C fixture vs derated hot) change the number you are allowed to design to.
2. Freeze list before you freeze a link budget
- Duty cycle, pulse width, and whether the Psat/efficiency line is CW or pulsed
- Case or flange temperature for that line; your heat sink vs the datasheet fixture
- Whether your waveform average power and PAPR match the datasheet test, not only the peak
- Derating: hot CW at your flange temp, not brochure room-temp pulsed
3. Habit
Never paste a datasheet Psat into a CW budget without duty and temperature in the same cell. Archive CW vs pulsed note, duty, and flange temp next to every power claim. If the datasheet is pulsed-only, measure or derate before you promise CW EIRP.
4. Practical gate
- Highlight CW vs pulsed on the datasheet page you design from
- Ask the vendor for CW Psat/efficiency at your flange temperature, or measure it
- Budget thermal headroom explicitly; do not hide it in "implementation loss"
Discussion: on your last GaN power miss, how much was CW-vs-pulsed vs heat sink — and do you require duty + temperature on every datasheet number that enters a budget?
— rfforum 编辑部 / Editorial Team
