Has anyone found deliveries of R&S test gear has become awfully long, like it’s normally 14 weeks or so, and one day before it should arrive, stretched out another 8 weeks? This is not a small power supply, but VSG’s, a VNA, MXO4 scope etc. I know they have Dram in them, but seriously….

Hii All, Is anyone here working or have worked on Polar modulated Power Amplifiers? I would like to get some guidance for my masters thesis. Thank you

Hello!

I am currently working on a project where we use 250 watt RF input power.
I'm looking to design a PCB-based Marchand balun, the design uses coupled transmission lines on two dielectric layers with a common ground plane.
Would this be possible without burning the PCB, what should i look for when simulating (for the 250Watt part)?
I am using Rogers4350B and frequency are 1.4-1.7GHz

BR Me

Follow-up to my previous post on updates to the Tiny RF Simulator Project.

Since then there have been 27 releases, v0.20.1 through v0.28.2. Full notes are in the CHANGELOG and on the releases page.

Receiver and analyzer

• Receiver Requirements panel: set a frequency band, an acceptable gain range, and a maximum noise figure. Each sweep gets pass, fail, or incomplete per metric and overall. Limits save with the project.
• Output-power and two-tone IIP3 requirements, with configurable tone spacing and input-level sweeps.
• Network Analyzer and receiver requirements now measure paths through a 1:2 switch feeding parallel branches that rejoin at a 2:1 switch. Combiner paths still report no data.
• The PFB inspector reports integrated channel noise and effective noise bandwidth. Its hover SNR uses channel noise, not the analyzer's RBW.
• Spectrum analyzer RBW and VBW now go from 1 kHz to 100 MHz. Network Analyzer gain and noise-figure plots autoscale.

New parts and instruments

• SPDT RF switches, 1:2 and 2:1, with insertion loss and isolation settings. The unselected path leaks in at the isolation floor.
• Power Meter: total power in dBm from any signal-node output, whether tone-only, noise-only, or combined.
• PFB filter calculator: synthesizes a Kaiser prototype, reports achieved metrics against the rejection target, and applies the design to a PFB channelizer.
• Hovering a node shows the strongest-tone SNR at its first output.

Test flows

• A GUI-free test-flow runner. A JSON file sweeps component parameters and records measurements, and results export as JSON.
• The Test Flow panel (View > Test Flow) runs those files against the live circuit.
• The panel can now write flows: pick a component and parameter, add conditions and measurements, save, and reload.
• Results report the value a component actually applied after normalization. A requested ADC decimation of 3, for example, reports 2.

Agent interface (MCP)

• An MCP client such as Claude Code can read and edit the circuit in an open simulator window. Enable Agent Server under View > Agent. The rf-sim-mcp bridge ships in the release archives.
• Agents can read the circuit, run port measurements, network-analyzer sweeps, receiver measurements, and test flows. Each call can apply up to 64 edits with checkpoints. Reverting a checkpoint needs confirmation.
• Agents cannot open, save, or name files (yet)

Editing and projects

• Swap a placed library part in place. The new part keeps the old part's id, position, links, and probes. A swap is refused, with the reason shown, if the new part lacks a port that is wired, probed, or used by an instrument.
• The editor rejects a second link into a single-source input and any link that would create a cycle.
• Out-of-range values stay as loaded and are flagged in amber. Previously the limit replaced them on the next edit.
• The header shows the project's Git commit and counts of staged, unstaged, untracked, and conflicted files.
• Hover tooltips list the interaction hints: Ctrl+click probes, Shift+click removes a probe, right-click opens the menu.
• User manual, part 1 of 3 (install and a guided tutorial), is in the repo under manual/pages/.

Fixes that change results

• Ideal-mode amplifier H2/H3 distortion was inflated by 2G/3G dB because gain was applied as a power ratio. It now matches the S-parameter branch.
• Ideal low-pass, high-pass, band-pass, and band-stop filters compare each bin's magnitude, so complex-baseband (ADC) spectra filter symmetrically. A negative-frequency blocker is now rejected by a low-pass filter.
• Equalizers and mixers handle negative (complex-baseband) frequencies correctly.
• Combiner added noise is clamped at zero. A negative term had been reported as InvalidNoise.
• Projects saved before the sparam_filepath rename now load their S-parameter files instead of falling back to the manual model.

Behavior changes

• Project-local extensions need one Trust click before they run. A project extension that reuses a built-in or global ID is reported as Shadowed and does not run.
• Ideal filter library definitions must set their cutoffs. Low-pass and high-pass need fc_low_Hz. Band-pass and band-stop need fc_low_Hz and fc_high_Hz. Definitions without them are refused instead of using the 100 and 200 MHz defaults.

What should the next update(s) cover?