<div dir="ltr"><div>Jeff is correct for pointing out the need for coverage modeling. This saves a great deal of time, effort and guess work. Terrain makes a huge difference when it comes to where you have overlap and also where you have overlap and lack capture of any one transmitter site. One thing many people get wrong with simulcast is that more power can be detrimental to achieving your goal. Modeling the coverage from each site and choosing the particular antenna and pattern for where you want to cover in respect to the other transmitters is key. In my humble opinion and it has worked for me, my main goal when creating a simulcast system is not how to get the audio sounding good in overlap but how to reduce the overlap areas with no capture to a minimum. This has to do mainly with the terrain causing issues where you audio is not arriving to the field unit(s) with the calculated delay due to anomalies in the terrain. <br></div>You also need to pay attention to particular antenna characteristics such as gain, electrical down tilt, mechanical down tilt and so on. I have found normally the site within a simulcast system that has the greatest coverage is often the site with one of the lowest ERP's. Once the RF coverage side of the house is right, the rest is adjustable. This is coming from a commercial simulcast standpoint.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 14, 2017 at 12:34 AM, Jeff DePolo <span dir="ltr"><<a href="mailto:jd0@broadsci.com" target="_blank">jd0@broadsci.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> First: They both need to launch the audio waveform at exactly<br>
> the same time T=0 in same phase. This also means that there<br>
> may need to be bulk delay to ensure that the most distant<br>
> (with respect to the IP back haul network) transmitter site,<br>
> receives the entire data payload before it is transmitted. I<br>
> am just learning about the RTCM so I believe that bulk delay<br>
> is inherent to the process.<br>
><br>
><br>
> Assuming both sites are exactly synced T=0, then where the<br>
> wave fronts meet midway will be in exactly sync even though<br>
> 35.1us (6.5 miles x 5.4 us = 35.1 us) has passed due to<br>
> propagation delay.<br>
<br>
</span>That's not correct (the part about "the wave fronts"). Simulcast audio/PL<br>
launch delay only guarantees AF synchronicity to the extent<br>
practical/possible (e.g. within a few microseconds of each other), but<br>
certainly not at the same RF phase. A microsecond at 150 MHz is 150 cycles.<br>
<span class=""><br>
> The wave fronts will also form a pair of theoretical opposing<br>
> hyperbolic curves that meet at the center of the two sites<br>
> like this: x1 )( x2 with the x representing each site.<br>
<br>
</span>Again, you can't look at it in the RF domain; AF sync is what you're working<br>
hard to achieve; you'll never get it at RF.<br>
<br>
Also keep in mind that sync at the midpoint isn't necessarily the goal. In<br>
a perfect world with no terrain, identical antenna patterns, identical ERP,<br>
etc. it might be, but not in the real world. You need to do coverage models<br>
for each of the sites (using actual ERP's and antenna patterns), see where<br>
the most-problematic areas are (i.e. the areas where capture effect isn't<br>
going to hide potential sins), and make decisions as to where to optimize<br>
and where to tolerate degradation, and then set delays accordingly.<br>
<span class=""><br>
> 1) Don't worry about frequency offset until you are sure the<br>
> timing and other parameters are correct.<br>
<br>
</span>Agree. Until the delays are correct (and again, that doesn't necessarily<br>
mean equal at the midpoint), there's no sense in adding another variable to<br>
the equation. Offsetting carrier frequency only helps mitigate cancellation<br>
nulls, it does nothing to mitigate delay errors.<br>
<br>
--- Jeff WN3A<br>
<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/<wbr>antivirus</a><br>
<div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.<wbr>allstarlink.org</a><br>
<a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://lists.allstarlink.org/<wbr>cgi-bin/mailman/listinfo/app_<wbr>rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://lists.allstarlink.org/<wbr>cgi-bin/mailman/listinfo/app_<wbr>rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. </div></div></blockquote></div><br></div>