Why was the continuous-time VCO block discontinued in the Communications Toolbox, and what is the recommended way to model it for PLL/RF synthesizer design?
Show older comments
I am designing a PLL/frequency synthesizer for an RF transceiver, and for this application I require a continuous-time VCO to generate clean I/Q signals at the desired frequency through the PLL.
Previously, the Communications Toolbox included a continuous-time VCO block, but in recent releases it only provides square-wave VCOs. The Mixed-Signal Blockset has similar square-wave oscillators, which are not ideal for my RF modeling needs.
My questions are:
- What is the recommended approach to realistically model a continuous-time VCO in Simulink for PLL and synthesizer applications?
- If I use an analog filter after the square-wave VCO to approximate a sinusoid, will this introduce additional noise or artifacts?
- If I design my own continuous-time VCO using a MATLAB Function block, is there a straightforward way to add phase noise (similar to the existing VCO block functionality), or do I need to manually implement mean/variance-based noise processes each time?
Any guidance, examples, or suggestions on how to best model a clean continuous-time VCO with realistic phase noise in current MATLAB/Simulink would be greatly appreciated.
Answers (2)
I "know nuthink!" about the field, but the release notes for R2024a contain the following
VCO and PLL blocks have been removed
These VCO and PLL blocks have been removed:
- Phase-Locked Loop (R2024a)
- Baseband PLL (R2024a)
- Charge Pump PLL (R2024a)
- Linearized Baseband PLL (R2024a)
- Continuous-Time VCO (R2024a)
To design voltage-controlled oscillators (VCOs) and phase-locked loops (PLLs), use the Phase-Locked Loops (R2024a) (Mixed-Signal Blockset) blocks.
3 Comments
Humayun
on 25 Sep 2025
dpb
on 25 Sep 2025
Sorry can't be of more help but I know nothing in the area to be able to infer how to use the replacement blocksets; looking at the documentation wasn't of help to me in seeing how to use the new toolset.
Do you have a model using the previous components? If so, my recommendation is to submit a support request to official Mathworks support requesting guidance in moving that model to the new toolbox.
Submit to Mathworks at <Product Support Page>
Amit Kansal
on 18 May 2026
Are you able to use the MIxed-Signal Blockset's Phase-Locked Loop blocks?
- Recommended approach to realistically model a continuous‑time VCO in Simulink for PLL / synthesizer applications
A practical and recommended approach in Simulink is to start with the Ring Oscillator VCO in Mixed‑Signal Blockset (which naturally outputs a pulse train), and then convert that pulse-train timing information into a sinusoid by reconstructing phase and generating sin(phase) (and cos(phase) for I/Q).
MathWorks provides an example that demonstrates exactly this workflow : Generate Sinusoidal Output from VCO
For I/Q generation: once you have the reconstructed phase
, you generate:

This is consistent with how the example reconstructs phase and then generates a sinusoid from it.
2. If I use an analog filter after a square‑wave VCO to approximate a sinusoid, will this introduce additional noise or artifacts?
Using a filter after a square wave can create a sinusoid-like fundamental, but it’s typically not the cleanest or most realistic approach for PLL/synth modeling because:
- A square wave contains strong harmonics; an analog filter suppresses harmonics but also adds group delay / phase shift and may introduce amplitude droop depending on filter design and operating conditions. (Those are “artifacts” in the sense that they are not intrinsic to the VCO itself, but to the post-processing.)
- If you include noise/phase-noise at the square-wave source, the filter will shape that noise in a way that may not match how phase noise manifests on a true sinusoidal oscillator output.
The example (Generate Sinusoidal Output from VCO) is generally a better approach because it does not rely on harmonic filtering; instead it reconstructs the oscillator phase from timing and directly produces a sine wave from phase.
That said, it’s important to note the example’s stated scope: it focuses on ideal behavior and explicitly does not model impairments like jitter or phase noise.
So the guidance is:
- If you just need a quick sinusoid-like waveform and don’t care about spectral purity or phase-noise realism in the waveform, filtering can be a quick approximation.
- If you want a cleaner, PLL/synth-relevant sinusoid generation method (especially for I/Q paths), the phase-reconstruction method shown in the example is the better foundation
3. If I design my own continuous‑time VCO using a MATLAB Function block, can I add phase noise “like the existing VCO block,” or must I implement noise processes each time?
You do not need to reinvent phase-noise modeling from scratch each time — Mixed‑Signal Blockset already provides a phase-noise workflow you can reuse.
There are two practical paths:
Option A (recommended): Use the Ring Oscillator VCO phase-noise capability + sinusoid reconstruction :
- The Ring Oscillator VCO block models frequency control and also supports period jitter and flicker-noise based phase-noise modeling, using a mathematical description intended to be computationally efficient.
- It also allows you to control/fit the phase-noise profile via parameters (Gaussian noise level, corner frequency, flicker exponent, etc.).
- Then you apply the same sine-output reconstruction approach as in “Generate Sinusoidal Output from VCO” to produce a sinusoid (and I/Q), but now your phase trajectory is driven by the VCO’s timing/phase behavior.
This gives you a path to a “continuous-time sinusoidal VCO output” while still leveraging the built-in VCO/phase-noise modeling machinery.
Option B: Build your own MATLAB Function VCO and inject phase noise yourself
If you fully custom-build the oscillator in a MATLAB Function block (e.g., compute (
output (
), then yes — you typically need to implement a noise process (e.g., integrate a frequency-noise process or add a phase-noise process) yourself.
However, Mixed‑Signal Blockset provides a reference workflow for specifying and validating phase noise against datasheet points using the Ring Oscillator VCO + VCO Testbench (Phase Noise Analysis in VCO). That example shows how to input a phase-noise profile (offsets + dBc/Hz levels), estimate parameters, and validate the resulting spectrum in simulation.
So even if you choose a custom implementation, the Mixed‑Signal Blockset phase-noise example provides a template for how to parameterize and validate phase-noise behavior rather than relying on ad-hoc mean/variance tuning.
Categories
Find more on Mixed-Signal Blockset in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!