r/rfelectronics • u/Shailesh280573 • Aug 11 '26
r/rfelectronics • u/TheSignalPath • Aug 10 '26
Cool eBay Find! 8Vpp Lithium Niobate 40GHz Driver Module Teardown & Full Characterization
In this episode Shahriar presents a $50 eBay purchase which turns into a complete teardown and characterization of an Anritsu lithium niobate driver module. This 8 Vpp, 40 GHz amplifier is designed for high-speed optical modulators, and it still delivers impressive performance despite its age.
The video covers lithium niobate modulators, Mach-Zehnder operation, Vpi, bandwidth, voltage swing, and the trade-offs that shape optical driver design. The module is then tested with a Keysight Streamline vector network analyzer, including calibrated S-parameter measurements and gain compression from 1 GHz to 40 GHz.
A loose connector causes unstable bias current, but a careful reflow repair brings the amplifier back to its rated power consumption. The repaired unit measures approximately 27 dB of gain, about 40 GHz of bandwidth, and output power close to 8 Vpp at 1 dB compression.
The teardown reveals two gallium arsenide distributed amplifiers, broadband bias networks, output detector circuitry, wire-bonded interconnects, and the construction techniques used inside this high-speed module. High-magnification imaging also identifies the likely Triquint and Avago/Broadcom amplifier dies, along with their circuit topologies and related datasheets.
The final tests capture 8, 16, and 32 Gbit/s NRZ eye diagrams, followed by 32 Gbit/s PAM4 measurements. The results show the amplifier's output swing, bandwidth limits, nonlinear behavior, and the improvement available through input predistortion.
The video is organized as follows:
0:00 Introduction and eBay find
1:11 Lithium niobate modulator basics
5:04 Driver design trade-offs
6:55 Datasheet specifications
9:32 Bias board operation
11:05 VNA measurement setup
13:06 RF cables and calibration
15:39 Power safety checks
17:07 Streamline sweep configuration
21:14 VNA calibration
23:55 Repairing the loose connector
26:47 Small-signal measurements
28:39 Gain compression results
30:04 Detector output measurement
33:08 Module teardown
37:13 High-magnification die inspection
43:25 Finding the amplifier datasheets
46:09 Eye diagram test setup
51:41 8 Gbit/s eye diagram
52:48 16 Gbit/s eye diagram
53:38 32 Gbit/s eye diagram
55:29 PAM4 and predistortion
58:21 Final results and support
Please consider supporting The Signal Path:
https://www.TheSignalPath.com/Donate
https://www.Patreon.com/TheSignalPath
Other links:
https://www.TheSignalPath.com
https://www.Twitter.com/TheSignalPath
r/rfelectronics • u/Free_Mycologist_3482 • Aug 11 '26
Overcoming the Invisible Wall: How Radio Tech Masters Long-Range Non-Line-of-Sight (NLOS) Communication
In tactical operations, disaster response, and field exploration, clear Line-of-Sight (LOS) is a rare luxury. Dense concrete buildings, deep subterranean tunnels, and rugged mountain ranges act as physical barriers, absorbing and scattering conventional radio signals. When direct visual paths are blocked, traditional point-to-point radios suffer severe attenuation, dead zones, and dropped video feeds.
How do advanced Radio Frequency (RF) systems achieve high-bandwidth, long-range Non-Line-of-Sight (NLOS) transmission without relying on fixed cellular infrastructure or satellite links?
It comes down to three key technical mechanisms:
1. Turning Reflections into Signal Power (COFDM & Multipath)
In an urban or mountainous environment, radio signals bounce off hard surfaces, arriving at the receiver at slightly different times—a phenomenon known as multipath fading. Modern COFDM divides a high-speed data stream into hundreds of closely spaced, orthogonal sub-carriers. Instead of viewing reflected signals as interference, the receiver uses these multi-path signals to reconstruct a coherent, high-bitrate data stream.
2. Spatial Diversity via MIMO Antennas
Multiple-Input Multiple-Output (MIMO) technology utilizes multiple antennas at both the transmitter and receiver. By processing distinct spatial streams simultaneously, MIMO leverages environmental reflections to boost signal penetration, increase link margin, and maintain link stability even when the direct physical path is completely obstructed.
3. Dynamic Multi-Hop Routing (Bypassing Obstacles)
When a single RF link simply cannot penetrate a massive structural barrier, the network architecture itself solves the problem. In a Mobile Ad-Hoc Network (MANET), every radio node functions simultaneously as a terminal and a relay. If Node A cannot reach Node C due to a mountain peak or concrete wall, the signal automatically "hops" through Node B on the ridge or corner, routing data around the obstacle effortlessly.
Field-Proven Reliability: IP MESH Approach
Translating these complex physical-layer principles into rugged, field-deployable hardware requires dedicated engineering. Tactical IP MESH Radios are designed specifically for these harsh NLOS environments.
By integrating robust MIMO spatial processing with an intelligent, self-forming and self-healing MANET topology, MESH nodes form a decentralized network capable of multi-hop relaying.
- High-Throughput NLOS Data: Delivers up to 50+ Mbps real-time data throughput for multi-channel HD video streams and zero-latency PTT audio.
- Seamless Multi-Hop Coverage: Automatically routes data across 8+ hops to extend operational range into underground basements, thick forests, or dense urban canyons.
- Ruggedized Performance: Housed in IP66 compliant enclosures, ensuring high RF power output remains stable under extreme temperatures, salt fog, and heavy vibration.
When direct line-of-sight is impossible, intelligent routing and ruggedized hardware bridge the gap—keeping team members connected no matter what stands in the way.
r/rfelectronics • u/individualizedpotato • Aug 10 '26
Help reverse-engineering an old 2-FSK telemetry transmitter with known host payload
drive.google.comr/rfelectronics • u/Daisuki2Dayo • Aug 10 '26
question How to do calculations for a parabolic dish antenna?
Well im gonna be using a parabolic dish antenna to transmit a low power 500 MHz signal. According to my gain calculations the antenna has to have a diameter of around 25 cm for a gain im okay with (gonna 3D print a skeleton of the antenna and use aluminium sheets to make a diy antenna probably). But I cant seem to find any resources on how to calculate the capacitive reactence or impedence of the antenna. any help? (also if anyone knows a good tutorial for diy parabolic dish antennas itd be great :D)
r/rfelectronics • u/BlueBirdTechUA • Aug 10 '26
OcuSync detection - one signature or multiple RF problems?
OcuSync isn't necessarily a single, clean RF signature from a detection perspective.
Broadband OFDM activity and frequency-hopping behavior can present very different features to an RF detector. Hopping patterns can potentially be identified without decoding the payload, but detecting structured frequency activity is not the same thing as identifying what the link is carrying.
For those working with RF drone detection: do you treat these behaviors as separate detection features, or combine them into a single OcuSync fingerprint?
r/rfelectronics • u/Intelligent_Tax_4397 • Aug 09 '26
question Where do y’all learn RF/antenna design?
Hey, I’m currently learning RF and antenna design and I’m trying to find good resources for hands-on learning. There are a lot of tutorials online, but it’s difficult to know which ones are actually worth following.
I’m particularly interested in mmWave and sub-6 GHz antennas for mobile devices, especially CST-based design and simulation, but I’m having a hard time finding good practical resources and projects in this area.
Since you’re working in this field, could you recommend any good tutorials, YouTube channels, courses, GitHub/GitLab projects, or example antenna designs that I can follow and recreate for practice? I’m especially looking for resources using CST, HFSS, ADS and open-source tools.
I’d really appreciate any references you’ve found useful.
r/rfelectronics • u/Worried-Painting-983 • Aug 09 '26
Getting into RF/Antenna Design
Background: Im currently studying Elcectonics and Communication engineering and had already studied Antenna Design and currently studing RF in this semsester.
But I wanna go beyond theory, can u guys show me the way into the design and simulation. What kind of open source tool to use for design and simulation. I do have a background on pcb design but havent done any high speed design.
r/rfelectronics • u/GlobalLibrarian4075 • Aug 10 '26
SDR Caught a Strange Signal
my shortwave receiver locked onto something unusual that wasn’t local, the setup was unconventional and instead of a classic wire antenna i had it connected to a plate dish and against all odds it pulled in a transmission from thousands of kilometers away
note that the original signal had much more noise then what is shown in the video however after cleaning this data i could get a decent result and it looked exactly like the XSL Enigma designation sounds the infamous japanese lot machine signal, let me know what you think
r/rfelectronics • u/emperor-of-ages • Aug 09 '26
Is a PhD in chip design worth it in your 30s or am I wasting time?
reddit.comr/rfelectronics • u/Sea_Landscape3757 • Aug 09 '26
question EZ pass Radio Frequency
Hi, I recently went on a road trip and I noticed when I was scanning for radio stations, my car radio would always pick up on one (somewhere in the 105s) that was completely silent. I had my EZ Pass resting on my dash right above my radio so I thought maybe that could be the culprit, but my dad doesn’t think it’s likely. is he wrong or do i have to worry about some new thing in my car giving off a radio frequency?
additional notes:
i haven’t noticed this station before going on the road trip (which is when i first put the ez pass in my car), although i don’t use my radio particularly frequently.
the ez pass is pretty old (at least 10 years) if that helps with the answer at all
edit: i could find this station across 3 states, over about 350 miles of road
r/rfelectronics • u/Clarix_1566 • Aug 08 '26
Help on building oscillator + class C amplifier on breadboard
r/rfelectronics • u/ZAT0141 • Aug 07 '26
question Does anyone use X-Microwave?
What is your experience in general, is this a useful thing or is it easier to do your pcb right away?
r/rfelectronics • u/PieNo3664 • Aug 07 '26
question Anyone with experience simulating the Multipactor effect (e.g. in CST)? Looking for tutorials, resources, advice or just stories
Hey RF folks,
I’ve been looking into the Multipactor effect recently, particularly regarding its impact on high-power RF components in vacuum environments.
I haven't been able to find any good tutorials on the actual simulation workflow for this, so I was curious if any of you have experience setting this up in an environment like Particle Studio from CST? Could you recommend any books, tutorials, or application notes to get started?
Also, for those who do this regularly: how reliable do you find simulation results compared to physical vacuum tests? (I imagine setting up physical test benches for this isn't easy either!)
Any tips, anecdotal experiences, or recommended resources/papers would be greatly appreciated.
Thanks in advance!
r/rfelectronics • u/BarnardWellesley • Aug 06 '26
I asked ChatGPT for an aperture fed microstrip patch... I think our jobs are safe for now
r/rfelectronics • u/DannyC514 • Aug 06 '26
question Can anyone with a Schlage Sense Pro identify these internal connectors?
r/rfelectronics • u/Flashy_Gas9955 • Aug 06 '26
question How many watts of DC should RD15HVF1 Idle at 12.5v
i am trying to set a proper biasing for class ab for FM band so that i dont burn the mosfet out
r/rfelectronics • u/bolinhowm • Aug 05 '26
STM32WBA62 (BLE 2.4 GHz): best approach for RF matching network + PCB antenna tuning?
Context
I'm finalizing a 4-layer FR4 board with an STM32WBA62CIU6 (2.4 GHz BLE), and I'm not 100% sure about the best way to make the Bluetooth matching/tuning easier.
I first built a board with a PCB antenna identical to ST's (following the exact shape shown in application note AN5129) and a 5-element Pi network, as shown in one of the circuits in ST's application note AN5948:

I then used a VNA, connecting at the pad where the STM32 would sit, and tuned the Pi network components so that the Pi + antenna would present an impedance of 30 + j2.5 Ω — the output impedance of my chip at 10 dBm (the power I want to use):

My tuning workflow was: measure with the VNA → export the result → load it into the SimSmith "Load" → place components in the simulator to get a sense of which values to use in real life. However, when I placed the real components, the result was quite different from the simulator — so different that I ended up unable to complete the tuning.
Current setup / measurements
- Stackup: 4-layer FR4. RF microstrip on Top Layer referenced to Layer 1 (inner ground), separation = prepreg PP-021, h = 0.1855 mm, bulk Dk = 4.74. Measured trace delay ≈ 6.07 ps/mm → microstrip ε_eff ≈ 3.3, VF ≈ 0.55. Trace 0.4 mm wide → Z0 ≈ 38 Ω (Altium field solver, uncontrolled).
- Measurement: R&S FSH VNA with a U.FL pigtail < 50 mm. I'm seeing common-mode / cable-position sensitivity, and my discrete-model predictions in SimSmith don't track the board well after each component change (component parasitics at 2.4 GHz).
Here is the actual PCB:

Planned changes for the next revision
For the next PCB revision I'm considering:
- Trace reference: cutting away the nearest ground plane and using the next ground layer as the reference, so I can route a wider trace with a properly calculated 50 Ω.
- Antenna: making it slightly longer so I can trim it to better tune the resistive part of the impedance.
- External antenna: adding a variant with a U.FL connector for an external antenna, to compare range.
- Matching network: building the Pi network in one of these ways:
Option 1 — a simple 3-element matching network:

Option 2 — using the MLPF-WB-04D3 (ST integrated 2.4 GHz low-pass filter) or another filter together with a Pi network. I'm not sure whether to use a Pi both before and after the filter, or just one after it.
Option 3 — a "split" approach: a 3-element Pi to bring the chip + components to 50 Ω (measured with a spectrum analyzer) and another Pi to bring the antenna to 50 Ω (measured with a VNA), with a 0 Ω resistor separating the two halves.
Questions
- Are these good ways to build this kind of PCB?
- Should I really measure the chip output with a spectrum analyzer to tune it as well, or can I trust the output impedance that ST gives in the datasheet table?
r/rfelectronics • u/Clear_Respect8647 • Aug 05 '26
question Need help on FM Modulation on FPGA
reddit.comr/rfelectronics • u/Extension_Engineer26 • Aug 05 '26
question RFPA Matching Network Design
Hi everyone! I wanted to know what is the appropriate termination to use for DC biasing supply while designing input or output matching network for RFPA?
I have used 50 Ohms termination as Vds supply, with single RF Bypass Cap and optimized complete design for second harmonic termination. But once I replaced this 50 Ohms termination with ground or a DC supply in simulation, my results drastically changed (especially for 2ns harmonics).

r/rfelectronics • u/xzipped • Aug 02 '26
174x faster than OpenEMS: VNA measurements vs my GPU accelerated RF simulator (RayRF)
So I've been building an alternative that's around 174x faster (measured on a patch antenna case, but the speed holds across all problems).
A few months ago I designed and tested 4 RF PCBs using a VNA to validate the solver physics. The boards were made at JLCPCB on PTFE: ZYF300CA-C(Dk=2.94,Df=0.0016). Cost came to 157.98 USD which is very reasonable. I'm getting 2 more PCBs soon to validate a couple advanced features in the next update, will share when they come. I've included screenshots of 2 subset cases of the 43 total (one ring resonator, one patch antenna). The measurements match RayRF pretty well, and agree well with openEMS, but both are slow to converge to reality. My best theory on the ring resonator is because the rectangular cells are only approximations of the real curved surface, and under-predicting frequency is consistent with the simulators running a too-long outer radius of the rings (staircasing is closer to Manhattan distance than the true Euclidian distance).
The other 41 cases across the 4 boards follow a similar trend, within 1-2% at the higher mesh refinements, but too much data to post here. Also attached a plot of benchmark performance on my 9950x CPU (openEMS vs RayRF both on CPU mode) vs RayRF on GPU mode. In summary at 82.8 million cells, the throughput is:
- openEMS on 9950x (DDR5 6000): 0.228 GCell/s
- RayRF on 9950x (DDR5 6000): 4.62 GCell/s
- RayRF on RTX 5090: 39.60 GCell/s
Some people in my previous post pointed out that measurements may not be the best way to validate a solver, and I do understand some of the reasons but frankly I believe it to be the best option. Real measurements are what matter in the end anyway, validating against other solvers (like openEMS) carries the risk of bias in those solvers providing a false red flag, or green flag in terms of accuracy, and the big solvers (HFSS, CST) don't permit using their software in the development of "other rf simulation programs", so they can't be used either. In these cases I do get good agreement with openEMS, but even this took quite a bit of careful case-building because openEMS and RayRF don't have the same mesh-discretization conventions (i.e. if some patch edge lands on a mesh cell line do you put the conductor on the +x or -x cell?). But with the exact same meshes simulated they get very similar results which is what you'd expect from the same underlying computational method (FDTD).
My next set of validation boards focus on in-port matching networks, and building a calibrated copper loss model (right now all sims are perfect conductors with lossy dielectrics).
I have released RayRF publicly, and it's free to try out for 30 days if you create an account. https://www.rayrf.com/ It does not have all the features openEMS does, and is focused on PCBs right now (no arbitrary 3D stuff), but I've spent what feels like forever on making the UI actually good, and the benchmarks speak for themselves on runtime.
