Putting several transmitters on one frequency on purpose means managing interference instead of avoiding it. This post touches on the theory behind simulcast, and how coverage and timing are tuned in a real system.<\/p>\n\n\n\n
Simulcast is controlled interference<\/h3>\n\n\n\n
Every mobile radio already deals with interference from its own signal. At a single site, the signal reaches the radio by a direct path and also by reflections off buildings and terrain. The reflected copies arrive a little later and at a different strength. This is ordinary multipath<\/strong>, and receivers handle it every day.<\/p>\n\n\n\n
Simulcast adds more of the same. A second site on the same frequency is, from the radio’s point of view, one more source of “reflections”: its direct path and its own reflections all land on top of the first site’s. This is co-channel multipath interference<\/strong>. The job of simulcast design is to keep that interference under control, so that where two sites overlap the radio still recovers clean audio or data.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
What the receiver does with it<\/h3>\n\n\n\n
A receiver amplifies what arrives at its antenna, mixes it down to an intermediate frequency, and demodulates it. When two or more signals are on, or very nearly on, the same frequency, they go through the mixer together and come out combined. Distortion is added along the way. What the radio finally produces depends on how its demodulator handles that combined signal. Everything else in simulcast design exists to make sure that combination still demodulates cleanly.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
Carrier frequency and phase<\/h3>\n\n\n\n
A mixer produces the sum and the difference of the signals fed into it. Put two transmitters at 147.000000 MHz and 147.000001 MHz, only 1 Hz apart, and the receiver sees a 1 Hz difference product. That is heard as a rolling fade, sometimes called “mobile flutter”.<\/p>\n\n\n\n
Being frequency<\/em>-locked is not the same as being phase<\/em>-locked. To a receiver, a small change in phase looks just like a change in frequency, so a slow phase drift between sites also shows up as a rolling fade, and there is little that can be done about it at the receiver. <\/p>\n\n\n\n
Hear this your self<\/h3>\n\n\n\n
You can reproduce the effect on a bench with two audio signal generators. Set one to 440 Hz and the other to 441 Hz at the same level, and mix them into a single speaker. The combined tone swells and fades once per second, because the two waves drift in and out of step, adding together and then cancelling. The beat rate is simply the difference between the two frequencies. Two carriers at 147.000000 and 147.000001 MHz beat at the same 1 Hz as the two tones.
This analogy has a limit. In the radio the beat happens to the RF carrier, before the audio is recovered. An FM receiver ignores changes in signal level, so the listener doesn’t hear a smooth swell. They hear the audio flutter and break into noise each time the two carriers cancel. Try turning one generator down: the fade becomes shallower. That is the capture effect at work, as described below. When one signal is much stronger than the other, the weaker one can barely pull it down.<\/p>\n\n\n\n
Note: the demo needs both tones summed into one speaker or one channel, not one tone in each ear.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
Audio timing: the 30-degree rule<\/h3>\n\n\n\n
The decoded audio from each transmitter has to reach the radio within 30 degrees<\/strong> of phase of each other. Turning that into a time depends on the audio frequency. Using 1,000 Hz as the reference:<\/p>\n\n\n\n
\n
360\u00b0 \u00f7 30\u00b0 = 12, so the budget is one twelfth of a cycle.<\/li>\n\n\n\n
A 1,000 Hz tone has a 1 ms period.<\/li>\n\n\n\n
1 ms \u00f7 12 \u2248 83 \u00b5s<\/strong>.<\/li>\n<\/ul>\n\n\n\n
The higher the audio frequency, the tighter the budget. <\/p>\n\n\n\n
The same effect applies to data. For digital modulations, the limit is expressed as delay spread<\/strong>, and refers to the bit-error-rate versus delay-spread curves in TIA TSB-88. These show the error rate climbing as the delay spread between sites increases, with some modulations tolerating much more spread than others.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
Capture effect and overlap<\/h3>\n\n\n\n
An FM detector will capture<\/strong> the stronger of two signals when their levels are different enough. It locks onto the stronger one and largely ignores the weaker. The narrower the deviation, the less capture effect there is.<\/p>\n\n\n\n
This defines where timing matters. An overlap area<\/strong> is a place where no single transmitter is strong enough to capture the receiver. Only there does the delay between sites need to be managed. The thing that matters is the delay difference inside the overlap areas, not<\/em> the distance between the transmitters.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
The speed of radio adds up<\/h3>\n\n\n\n
Radio travels at about 5.4 \u00b5s per mile<\/strong>. That sounds quick, but the miles add up: 10 miles is 54 \u00b5s and 20 miles is 108 \u00b5s. Compare that with the 83 \u00b5s budget at 1 kHz. A path-length difference of 20 miles is already too much if the receiver is in an overlap area.<\/p>\n\n\n\n
What matters is the difference in arrival time at the radio, not the distance to either site. <\/figcaption><\/figure>\n\n\n\n
Example<\/th>
Path lengths<\/th>
Arrival difference<\/th>
Result<\/th><\/tr><\/thead>
Two sites, mobile close to one<\/td>
20 mi \/ 2 mi<\/td>
97.2 \u00b5s<\/td>
OK only if the near site captures the receiver<\/td><\/tr>
A radio might be in overlap with all three. Avoid this by controlling coverage.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
The three-site case is closer to the real world. A pair of nearby sites can be well matched while a distant site’s signal arrives far too late. The is answer is to control where each site’s coverage goes, so a radio isn’t left in overlap with a far-off site.<\/p>\n\n\n\n
Flutter in the overlap zone<\/h3>\n\n\n\n
SVRG’s analysis.<\/strong> This section works out the effect out from basic two-signal FM theory, and the second figure comes from a simple computer simulation, not a field recording.<\/p>\n\n\n
<\/p>\n
<\/p>\n
Drive through an overlap area where both sites are strong and the audio can take on a rapid, rhythmic flutter<\/strong>: a fast chop or warble, not hiss. It speeds up as you speed up and goes away when you stop. With our two test sites setup you can clearly hear this effect driving north, toward one site and straight away from another site to the south, along the hwy 101 corridor in Morgan Hill.<\/p>\n
<\/p>\n
<\/p>\n
This is the “mobile flutter” from the carrier section, but here the motion makes it, not the transmitters. Even with both carriers locked to exactly the same frequency, a moving radio hears each one shifted slightly by the Doppler effect<\/strong>. Driving toward Site N, its signal arrives a little high, by the car’s speed divided by the wavelength. Driving away from Site S, its signal arrives low by the same amount. At 30 mph on 147 MHz each shift is 6.6 Hz, so the receiver sees two carriers 13.2 Hz apart. That is no different from two transmitters 13 Hz off frequency: the combined signal fades in and out 13 times a second.<\/p>\n
<\/p>\n
<\/p>\n
\nDriving toward one site and away from the other. Each site’s signal is Doppler-shifted the opposite way, and the two add and cancel in a pattern that stands still on the road. The level curve is computed for two signals 1 dB apart.<\/figcaption>\n<\/figure>\n
<\/p>\n
<\/p>\n
There is a second way to see the same thing. Where two signals cross, they add in some places and cancel in others, and that pattern stands still on the ground. When the two signals come from opposite directions, the cancellations (nulls) are half a wavelength apart: 1.02 m at 147 MHz, 0.34 m at 445 MHz. The car simply drives through them. At 30 mph, 13.4 m\/s \u00f7 1.02 m gives the same 13 nulls a second.<\/p>\n
The table is the fastest case, with one site straight ahead and the other straight behind. If the sites are not on opposite sides of you, the nulls are farther apart and the flutter is slower. Drive across the line between two sites instead of along it, and both signals arrive from the side: neither is Doppler-shifted much, and the flutter should all but stop. The same standing pattern is why a handheld user in an overlap can sometimes clear up the audio by moving a foot or two.<\/p>\n
<\/p>\n
<\/p>\n
Why it is a flutter, not hiss.<\/strong> An FM receiver’s limiter strips off changes in amplitude, so the dips themselves aren’t heard as long as the signal at the bottom of each dip stays well above the noise. With both sites strong, it does. Two signals 1 dB apart dip about 19 dB, and two signals 0.3 dB apart about 29 dB; a strong signal 20 or 30 dB down is still a usable signal. What the limiter can’t remove is the phase<\/em> of the combined signal, which swings quickly each time the two carriers pass through opposition, and that swing is what reaches the audio. When the two signals also fade on their own and trade places as the stronger one, the combined phase can slip a full turn, which is heard as a sharper pop.<\/p>\n
<\/p>\n
<\/p>\n
Audio timing decides how bad it sounds.<\/strong> If both sites’ audio arrives at exactly the same moment, both carriers carry identical modulation and the phase swing at each dip is brief and small. In the simulation below, with the levels 1 dB apart, the receiver’s tone comes through clean, dips and all. If the two sites’ audio arrives a time \u03c4 apart, the modulation itself rocks the carriers’ relative phase back and forth, by about 360\u00b0 \u00d7 peak deviation \u00d7 \u03c4. At 2.5 kHz deviation and 80 \u00b5s, the narrowband delay limit in the design criteria above, that is \u00b172\u00b0. Whenever the slow 13 Hz rotation brings the two carriers within 72\u00b0 of opposition, the audio pushes them through cancellation again and again, and the waveform is torn up. That covers 144\u00b0 of every 360\u00b0, about 40% of each flutter cycle. The simulation agrees: measured in 1 ms slices, 43% of the audio falls below 20 dB SINAD, in a burst around every dip.<\/p>\n
<\/p>\n
<\/p>\n
\nA quarter of a second of the drive in the figure above, simulated. The only difference between the two audio traces is the timing of the two sites’ audio. Shading marks where the 72\u00b0 swing reaches cancellation. Model: same carrier frequency at both sites, no noise, no independent fading, ideal FM detector. SVRG simulation, not a field recording.<\/figcaption>\n<\/figure>\n
<\/p>\n
<\/p>\n
So the motion sets the rhythm, and the alignment sets the damage. A difference in deviation between the sites rocks the phase the same way, most at low audio frequencies: a 10% mismatch on a 300 Hz tone at full deviation is about \u00b148\u00b0. The case simulated here is the worst corner of an overlap area, with the delay right at the design limit and the two signals within about a dB. It shows why delay and deviation are worth matching as closely as the equipment allows, and why it pays to know where the overlap areas fall.<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
Design it on the computer first<\/h3>\n
<\/p>\n
<\/p>\n
A coverage-prediction program for simulcast has to calculate time-delay interference<\/strong> as well as signal level. Design criteria:<\/p>\n
With those two numbers, a prediction can mark each place as either captured<\/em> by one site (more than 15 dB stronger than the others, so delay doesn’t matter) or in overlap<\/em> (where the arrival-time difference has to be within the delay limit). Because narrower deviation gives less capture, deviation is one of the inputs that moves the overlap areas.<\/p>\n
<\/p>\n
<\/p>\n
Antenna downtilt: a trade-off<\/h3>\n
<\/p>\n
<\/p>\n
Tilting a site’s antenna down clearly raises signal levels close to the site. It reduces the areas of overlap interference, but at a cost. High sites lose some of their wide-area coverage, so talk-out is reduced in some places. Simulcast from high sites is often difficult, and much of the reason for choosing a high site goes away once its coverage has to be pulled in.<\/p>\n
<\/p>\n
<\/p>\n
You can’t tune a simulcast system by driving around<\/strong>. You need to model it in software. <\/strong><\/p>\n
<\/p>\n
<\/p>\n
Software modeling: delay spread<\/h3>\n
<\/p>\n
<\/p>\n
Salinas Valley Repeater Group uses its own in house modeling software to calculate and map the delay spread for our simulcast system. A delay spread map lets us visualize the differential delay or ‘delay spread’ within the designed coverage area of our system.<\/p>\n
<\/p>\n
<\/p>\n<\/figure>\n
<\/p>\n
<\/p>\n
The map pictured shows an area in Santa Cruz County that will be out of our phase budget so the resulting signal in this area will have distortion artifacts.<\/p>\n
<\/p>\n
<\/p>\n
\n
<\/p>\n
reference sources<\/h3>\n
<\/p>\n
<\/p>\n
\n
\n
\n
Joe Blaschka Jr., PE, ADCOMM Engineering Company, “Simulcast \u2013 Theory or why we do the things we do,”<\/em> Simulcast Forum XX, Las Vegas, 2016.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
<\/p>\n
<\/p>\n
\n
\n
\n
Joe Blaschka Jr., PE, ADCOMM Engineering Company, “Simulcast \u2013 Propagation and Tuning,”<\/em> Simulcast Forum XXII, Orlando, 2018.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
![\"\"](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/simulcast_fig1_multipath-1024x476.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/simulcast_fig2_receiver-1024x216.png\")
<\/figure>\n\n\n\n![\"1Hz](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/simulcast_fig5_rf_vs_audio-1024x1010.png\")
<\/figure>\n\n\n\n![\"Fig](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/simulcast_fig6_30deg-1024x778.png\")
<\/figure>\n\n\n\n![\"Overlap](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/simulcast_fig7_capture-1024x1005.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/simulcast_fig3_overlap-1024x381.png\")
![\"Left:](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/10\/simulcast_fig8_doppler.png\")
\n![\"Simulated](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/10\/simulcast_fig9_flutter.png\")
\n![\"Out](\"https:\/\/w6dxw.com\/wp-content\/uploads\/2026\/09\/delayspread-1024x870.png\")
<\/figure>\n