<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>Hi </span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Shaun,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>At the moment we are limited to transmitters that use 14.4Mhz as their oscillator base (MCX. Syntors, MSF500s, MaxTrax) since the Motorola UHSO only creates that frequency from the 10mhz Trimble GPS. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>If we select a different transmitter model (that is not 14.4 based) a clock generator like Mark’s </span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Programmable Clock Generator Module will be needed. We were lucky in that I had a bunch of UHSO units for a 900Mhz project that we could borrow for the thin client 440 project.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Pete/WI6H</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] <b>On Behalf Of </b>Jim Duuuude<br><b>Sent:</b> Thursday, December 22, 2011 4:25 AM<br><b>To:</b> shaun@pmbnet.co.za; app_rpt mailing list; zs5bg@harc.org.za; zs5z@harc.org.za<br><b>Subject:</b> Re: [App_rpt-users] RADIO THIN CLIENT MODULE and "Simulcast Transmit System"<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Yes. That's how simulcast systems work.<br><br>When you base your syncronization on a GPSDO (GPS Disciplined Oscillator)<br>such as the Trimble Thunderbolt (which has accuracy typically of 10-20 parts<br>per TRILLION, which means that if you were transmitting at 1GHz, you would<br>be no more then 0.010 to 0.020 Hz off) *and* the audio is in sync with that timing<br>source *and* the deviation is set consistently accurately between all transmitters,<br>then, yes, its quite possible.<br><br>Obviously, you need to use transmitters appropriately suited for this type of application,<br>which either by initial design or by modification, allow injection of an external (to the<br>transmitter) reference frequency. Some transmitters are designed with this in mind.<br>Others can be trivially modified to allow this.<br><br>For example, the Trimble Thunderbolt has its precise frequency output at 10 MHz.<br>Some transmitters will operate directly from the frequency reference. Others need<br>some other frequency. If this is the case, a clock generator (locked to the Thunderbolt's<br>10 Mhz output) that produces the appropriate frequency is needed.<br><br>Some radio manufacturers, such as the one that Pete Elke (WI6H) was referring to<br>make devices specifically suited for this purpose (he was using the clock generator<br>within a high stability oscillator unit from an old Motorola paging transmitter).<br><br>Another option would be to use the PCGM (Programmable Clock Generator Module) that<br>Mark at Micro-Node (K7IZA) is coming out with soon. It takes the 10 MHz input from the<br>Trimble Thunderbolt, and generates pretty much whatever reference frequency you<br>"tell it to" (from 6-200 MHz), and also, acts as a power supply for the Trimble Thunderbolt.<br><br>The reason I keep making specific reference to the Trimble Thunderbolt is because they are<br>readily available on the surplus market (rather inexpensively), and are EXTEREMELY well-suited<br>for this application (probably the best selection given all of the parameters involved here).<br><br>JIM WB6NIL<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>> Date: Thu, 22 Dec 2011 12:41:11 +0200<br>> From: shaun@pmbnet.co.za<br>> To: app_rpt-users@ohnosec.org; zs5bg@harc.org.za; zs5z@harc.org.za<br>> Subject: [App_rpt-users] RADIO THIN CLIENT MODULE and "Simulcast Transmit System"<br>> <br>> Before I break open my kid's piggy-bank for a couple of "ALLSTAR RTCM <br>> (RADIO THIN CLIENT MODULE)'s " http://micro-node.com/thin-m1.html<br>> I need an important question answered. .............please?<br>> <br>> If both rptr's are in the same coverage area, and transmit at the same <br>> time on the same freq, BUT perfectly in sync using the GPS sync <br>> option...................... will the end user (client/club member) hear <br>> a perfect signal? (even if he/she where in range of both transmitters?)<br>> One would think you would hear a heterodyne of some sort with both <br>> signals reaching and mixing into the users transceiver.<br>> <br>> We all know that if 2 hams try use their local repeater at the same time <br>> (doubling) then the end result is Yucky, unless the one users tx signal <br>> is much stronger than the other user.<br>> <br>> Is this RTCM system so accurate, that the user hears a perfectly synced <br>> and clear signal?<br>> <br>> Shaun<br>> zr5s<br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<o:p></o:p></span></p></div></div></div></body></html>