L
Admin
[Technical article / FAQ, rfforum Editorial Team]
An analog RFoF link whose RF gain or SFDR ripples on a seconds-to-minutes scale is often the Mach-Zehnder bias loop hunting, not fiber dispersion or connector dirt. If the ripple correlates with bias voltage or second-harmonic lock error, stop the fiber scrub first.
1. What the bias loop owns
- Quadrature lock via second-harmonic null (or dither) keeps SFDR; a loose loop walks the operating point and paints RF gain and even-order products as "fiber fade".
- Optical power and photocurrent change with the same walk. A gain ripple that tracks bias DAC / error signal is electronics until proven otherwise.
- Cold start vs soaked lock points differ. A link that "settles after lunch" is often bias thermal, not the spool in the rack.
2. Freeze list before you re-polish connectors
- Bias mode (open-loop set-and-forget vs closed second-harmonic / dither), error signal, and whether ripple frequency matches the loop
- Optical power / photocurrent logged on the same time axis as RF gain
- Freeze bias, open the loop briefly, or hold DAC: if ripple dies, the fiber was never the patient
- OMI / drive level: compression can amplify bias sensitivity
3. Habit
Never close an "RFoF intermittent fade" ticket without a bias-error vs RF-gain overlay. Archive lock mode, soak time, and photocurrent next to every SFDR claim. If holding bias kills the ripple, schedule fiber work later.
4. Practical gate
- Scope or log bias error vs RF detector for one ripple period
- Hold / freeze bias for two minutes; re-check gain
- Only then chase connectors, EDFA, or dispersion
Discussion: on your last RoF gain hunt, did the fix land in bias lock, drive/OMI, or a real optical path — and do you require a bias-hold A/B before opening a fiber ticket?
— rfforum 编辑部 / Editorial Team
An analog RFoF link whose RF gain or SFDR ripples on a seconds-to-minutes scale is often the Mach-Zehnder bias loop hunting, not fiber dispersion or connector dirt. If the ripple correlates with bias voltage or second-harmonic lock error, stop the fiber scrub first.
1. What the bias loop owns
- Quadrature lock via second-harmonic null (or dither) keeps SFDR; a loose loop walks the operating point and paints RF gain and even-order products as "fiber fade".
- Optical power and photocurrent change with the same walk. A gain ripple that tracks bias DAC / error signal is electronics until proven otherwise.
- Cold start vs soaked lock points differ. A link that "settles after lunch" is often bias thermal, not the spool in the rack.
2. Freeze list before you re-polish connectors
- Bias mode (open-loop set-and-forget vs closed second-harmonic / dither), error signal, and whether ripple frequency matches the loop
- Optical power / photocurrent logged on the same time axis as RF gain
- Freeze bias, open the loop briefly, or hold DAC: if ripple dies, the fiber was never the patient
- OMI / drive level: compression can amplify bias sensitivity
3. Habit
Never close an "RFoF intermittent fade" ticket without a bias-error vs RF-gain overlay. Archive lock mode, soak time, and photocurrent next to every SFDR claim. If holding bias kills the ripple, schedule fiber work later.
4. Practical gate
- Scope or log bias error vs RF detector for one ripple period
- Hold / freeze bias for two minutes; re-check gain
- Only then chase connectors, EDFA, or dispersion
Discussion: on your last RoF gain hunt, did the fix land in bias lock, drive/OMI, or a real optical path — and do you require a bias-hold A/B before opening a fiber ticket?
— rfforum 编辑部 / Editorial Team
