<div dir="ltr">Here's another link to some more info in an email thread. <br><a href="http://ohnosec.org/pipermail/app_rpt-users/2015-December/013155.html">http://ohnosec.org/pipermail/app_rpt-users/2015-December/013155.html</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 5, 2016 at 10:22 PM, Lee Woldanski <span dir="ltr"><<a href="mailto:ve7fet@tparc.org" target="_blank">ve7fet@tparc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Just throwing this out there... wouldn't it be possible (trivial?) to configure the PIC (firmware) for 10MHz external clock, and replace the 9.6MHz crystal with 10MHz in from a GPSDO?<div><br></div><div><br></div><div>Lee</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Sun, Jun 5, 2016 at 1:33 PM, Sam Skolfield <span dir="ltr"><<a href="mailto:kj6qfs@gmail.com" target="_blank">kj6qfs@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Jesse, <br><br></div>From my understanding as well as many others, simulcasting WON'T work properly in overlap areas unless you replace the RTCM's internal 9.6MHz crystal with a GPSDO 9.6MHz @3.3 volts p-p. If you expect a cheap 9.6MHz crystal to derive a 1PPS signal and stabilize it between clock pulses down to a level acceptable for accurate syncing of CTCSS generation, free of intrinsic jitter, you are "optimistic" to say the least. <br><br></div>Jim Dixon has articulated this before on the email list. Simulcasting with the RTCMS in overlap areas WON'T WORK PROPERLY without this trivial modification. Obviously this requires usage of IDENTICAL equipment at each site. Here is a pointer to an email of his. <br><br><i><a href="http://ohnosec.org/pipermail/app_rpt-users/2013-November/007704.html" target="_blank">http://ohnosec.org/pipermail/app_rpt-users/2013-November/007704.html</a><br><br></i></div><div>Jim described a possible future RTCM design with convenient provisions for plugging in external 9.6MHz, but this has not happened. <br><br>73<br></div><div><i><br></i></div><i><br></i></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 5, 2016 at 1:04 PM, Jesse Lloyd <span dir="ltr"><<a href="mailto:ve7lyd@gmail.com" target="_blank">ve7lyd@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>You need both 1 pps and Rx GPS data to the RTCM<br><br>Cheers,<div>Jesse</div></div><div><div><div><br>On Jun 4, 2016, at 6:03 PM, Joe Moskalski <<a href="mailto:kc2irv@gmail.com" target="_blank">kc2irv@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div>I will be setting up a 2 site UHF simulcast system in the coming months and so far I have only one question to ask. The RTCM manual is a little vague on the GPS part of the setup. Normally, with other types of radio simulcast products (which I am very familiar with several) all you need to properly time the audio is a 1 pps signal from the GPS reference. The RTCM manual makes mention of the NMEA/TSIP data being connected but does not explicitly say if that serial data is needed or if only the 1 pps is needed for simulcast operation. From the other simulcast products I have worked with, you set your bulk delay to a value larger then the delay required for the furthest site and the system will adjust. Does the RTCM version of simulcast work the same way? I just want to be sure because this will determine what type of GPS locked reference oscillator I choose for the project. <br><br></div>Regards,<br></div>KC2IRV<br></div>-Joe<br></div><div><br>
<table style="border-top:1px solid #d3d4de">
<tbody><tr>
<td style="width:55px;padding-top:13px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/2016/icons/icon-envelope-tick-round-orange_184x116-v1.png" height="29px"></a></td>
<td style="width:470px;padding-top:12px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" style="color:#4453ea" target="_blank">www.avast.com</a>
</td>
</tr>
</tbody></table><a href="#m_-2916098998062417082_m_-3888457977868170799_m_-8328703430711967483_DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>
</div></blockquote></div></div><blockquote type="cite"><div><span>_______________________________________________</span><span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a></span><br><span><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>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. </span></span></div></blockquote></div><br>_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_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. <br></blockquote></div><span><font color="#888888"><br><br clear="all"><br>-- <br><div data-smartmail="gmail_signature">KJ6QFS<br>Sam Skolfield</div>
</font></span></div>
<br>_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_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. <br></blockquote></div><br><br clear="all"><div><br></div>-- <br></div></div><div data-smartmail="gmail_signature">Lee Woldanski, AScT<br>VE7FET</div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">KJ6QFS<br>Sam Skolfield</div>
</div>