<div dir="ltr">You are correct Joe. The RTCM is a contender though it wouldn't exist or would be useless without Jim's software. <div><br></div><div>As Robert mentioned, and his friend is right. I was warned by a local and very knowledgeable elmer also. Personally I'm simulcasting but fortunately there is a node smack dab in the middle that "most" users will switch to so they don't hear the issues in the overlap zones. </div><div><br></div><div>I haven't yet cracked the RTCM's open to modify them and I may not ever do it just cause i'm lazy. It depends on how picky your users are. That's sort of a loaded question though. When folks get used to allstar (especially if you're running a high quality codec) and they travel into one of these overlap zones they'll probably complain because they're used to so much more fidelity! </div><div><br></div><div>Does it work without jumping through all the hoops...? Yes, it's just way more ugly in the areas that have overlapping coverage. </div><div><br></div><div>blah blah...i'm delirious and I still have two more night shifts to go!</div><div><br></div><div>73 de K0JSC</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 6, 2016 at 10:59 AM, <span dir="ltr"><<a href="mailto:app_rpt-users-request@ohnosec.org" target="_blank">app_rpt-users-request@ohnosec.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send App_rpt-users mailing list submissions to<br>
<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<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>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:app_rpt-users-owner@ohnosec.org">app_rpt-users-owner@ohnosec.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of App_rpt-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: RTCM Simulcast question (Robert Newberry)<br>
2. Re: App_rpt-users Digest, Vol 88, Issue 16 (Joe Leikhim)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 6 Jun 2016 12:56:57 -0400<br>
From: Robert Newberry <<a href="mailto:N1XBM@amsat.org">N1XBM@amsat.org</a>><br>
To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
Subject: Re: [App_rpt-users] RTCM Simulcast question<br>
Message-ID:<br>
<<a href="mailto:CAM09xEagKzHhFhw94cqe7oDKWkhr51fdTKt0CuQB2DMz7OH4Gg@mail.gmail.com">CAM09xEagKzHhFhw94cqe7oDKWkhr51fdTKt0CuQB2DMz7OH4Gg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Please don't flame me.<br>
<br>
I have a friend who used to work in the paging industry. When I talked to<br>
him about simulcast he was telling me about the paging industry the pains<br>
they went thru. He was saying that they used all of the same transmitters<br>
made around the same time. A signal can go from point A to B in transmitter<br>
a different lengths of time.<br>
<br>
He basically told me the same thing, that go do it and enjoy. He just<br>
warned me about PL sync and all of the details to getting it right. He just<br>
said at the end of the day that he was confident I could get it to work,<br>
but probably will not be satisfied with the results.<br>
<br>
N1XBM<br>
Apparare Scientor<br>
Paratus Communicare<br>
Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657<br>
<a href="http://www.radioguysrepeaternetwork.com" rel="noreferrer" target="_blank">www.radioguysrepeaternetwork.com</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/87496c0d/attachment-0001.html" rel="noreferrer" target="_blank">http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/87496c0d/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 6 Jun 2016 12:59:27 -0400<br>
From: Joe Leikhim <<a href="mailto:rhyolite@leikhim.com">rhyolite@leikhim.com</a>><br>
To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
Subject: Re: [App_rpt-users] App_rpt-users Digest, Vol 88, Issue 16<br>
Message-ID: <<a href="mailto:afeb133c-87cc-0c50-9e8d-5ee854a7fc24@leikhim.com">afeb133c-87cc-0c50-9e8d-5ee854a7fc24@leikhim.com</a>><br>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"<br>
<br>
There was mention on this board that drift of the 9.6 MHz clock causes<br>
the CTCSS phase to shift. If this is the case, you will have audible<br>
noise and possibly receiver CTCSS drop outs in overlap areas. You will<br>
have distortion of audio frequencies as well.<br>
<br>
Whatever solution to the 9.6 MHz clock must be phase coherent between<br>
RTCM nodes .<br>
<br>
I have no experience with RTCM, but am quite familiar with commercial<br>
simulcast in the LMR world. I am lurking here because I see the RTCM as<br>
a very affordable contender to the commercial products that exist today.<br>
<br>
Joe K4SAT<br>
<br>
<br>
On 6/6/2016 12:23 PM, Jeff Carrier wrote:<br>
> The RTCM and simulcast DOES work. As mentioned before, you have to be<br>
> using a transmitter that can accept a 10 mHz (or whatever) reference<br>
> signal. You also need 1 PPS for your receivers and transmitter. You<br>
> also need to sync the RTCM to your GPSDO (which I have not done). If<br>
> you have not done all this you WILL hear some "funk" in the overlap<br>
> areas.<br>
><br>
> That "funk" can go from usable to un-usable depending on how strong<br>
> the transmitters are in the overlap region.<br>
><br>
> Pardon the "non-technical" terms. It does work but the law of physics<br>
> do apply here.<br>
><br>
> de K0JSC<br>
><br>
> On Mon, Jun 6, 2016 at 9:54 AM, <<a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>
> <mailto:<a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a>>> wrote:<br>
><br>
> Send App_rpt-users mailing list submissions to<br>
> <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<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>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>
> <mailto:<a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a>><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:app_rpt-users-owner@ohnosec.org">app_rpt-users-owner@ohnosec.org</a><br>
> <mailto:<a href="mailto:app_rpt-users-owner@ohnosec.org">app_rpt-users-owner@ohnosec.org</a>><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of App_rpt-users digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: audio for direct VCO FM (Joe Leikhim) (Steve Wright)<br>
> 2. Re: RTCM Simulcast question (Steve Wright)<br>
> 3. Re: audio for direct VCO FM: Si5351B (David McGough)<br>
> 4. Re: RTCM Simulcast question (Joe Moskalski)<br>
> 5. Re: RTCM Simulcast question (David McGough)<br>
> 6. Re: RTCM Simulcast question (Joe Moskalski)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Mon, 6 Jun 2016 19:40:50 +1200<br>
> From: Steve Wright <<a href="mailto:info@meshnetworks.co.nz">info@meshnetworks.co.nz</a><br>
> <mailto:<a href="mailto:info@meshnetworks.co.nz">info@meshnetworks.co.nz</a>>><br>
> To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
> Subject: Re: [App_rpt-users] audio for direct VCO FM (Joe Leikhim)<br>
> Message-ID: <<a href="mailto:57552902.9070008@meshnetworks.co.nz">57552902.9070008@meshnetworks.co.nz</a><br>
> <mailto:<a href="mailto:57552902.9070008@meshnetworks.co.nz">57552902.9070008@meshnetworks.co.nz</a>>><br>
> Content-Type: text/plain; charset=windows-1252; format=flowed<br>
><br>
> On 04/06/16 04:00, Joe Leikhim <<a href="mailto:rhyolite@leikhim.com">rhyolite@leikhim.com</a><br>
> <mailto:<a href="mailto:rhyolite@leikhim.com">rhyolite@leikhim.com</a>>> wrote:<br>
> > Assuming the VCO is part of a PLL, the PLL will tend to<br>
> "correct" the<br>
> > modulation, [....]<br>
><br>
> Was planning to use the Si5351B - has VCO input.<br>
><br>
> S<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Mon, 6 Jun 2016 20:22:36 +1200<br>
> From: Steve Wright <<a href="mailto:info@meshnetworks.co.nz">info@meshnetworks.co.nz</a><br>
> <mailto:<a href="mailto:info@meshnetworks.co.nz">info@meshnetworks.co.nz</a>>><br>
> To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
> Subject: Re: [App_rpt-users] RTCM Simulcast question<br>
> Message-ID: <<a href="mailto:575532CC.2020304@meshnetworks.co.nz">575532CC.2020304@meshnetworks.co.nz</a><br>
> <mailto:<a href="mailto:575532CC.2020304@meshnetworks.co.nz">575532CC.2020304@meshnetworks.co.nz</a>>><br>
> Content-Type: text/plain; charset=windows-1252; format=flowed<br>
><br>
> On Sat, Jun 4, 2016 at 6:03 PM, Joe Moskalski <<a href="mailto:kc2irv@gmail.com">kc2irv@gmail.com</a><br>
> <mailto:<a href="mailto:kc2irv@gmail.com">kc2irv@gmail.com</a>>> wrote:<br>
><br>
> > I will be setting up a 2 site UHF simulcast system in the coming<br>
> months<br>
><br>
> Huh? I was told (on this list) that simulcast TX "doesn't work".<br>
><br>
><br>
><br>
> S<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Mon, 6 Jun 2016 10:46:38 -0400 (EDT)<br>
> From: David McGough <<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a> <mailto:<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a>>><br>
> To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
> Subject: Re: [App_rpt-users] audio for direct VCO FM: Si5351B<br>
> Message-ID:<br>
><br>
> <<a href="mailto:Pine.LNX.4.44.1606060946450.4196-100000@goliath.inttek.net">Pine.LNX.4.44.1606060946450.4196-100000@goliath.inttek.net</a><br>
> <mailto:<a href="mailto:Pine.LNX.4.44.1606060946450.4196-100000@goliath.inttek.net">Pine.LNX.4.44.1606060946450.4196-100000@goliath.inttek.net</a>>><br>
> Content-Type: TEXT/PLAIN; charset=US-ASCII<br>
><br>
><br>
> Hi Steve,<br>
><br>
> We're getting way off topic for the mailing list, but, I thought<br>
> I'd post<br>
> this reply here if there are any other interested hams out there,<br>
> perhaps<br>
> who are also experimenting in this area.<br>
><br>
> I haven't played with the Si5351B version of this interesting<br>
> chip, yet. I<br>
> wonder whether the voltage control input of this chip would be<br>
> suitable<br>
> for AF FM modulation? Assuming that you could modulate the VCXO at<br>
> audio<br>
> frequencies (the datasheet isn't completely clear to me about<br>
> that), an<br>
> immediate issue would be that everytime you change the fractional-N<br>
> division ratio, you'll change the modulation index. This will have<br>
> to be<br>
> compensated for, one way or another.<br>
><br>
> I've been playing with several boards with Si5351 chips. They're<br>
> pretty<br>
> neat. They're also pretty noisy! ...With both spurious and phase<br>
> noise.<br>
> The phase noise can be improved somewhat with a better external<br>
> crystal<br>
> oscillator, the spurs seem more challenging. Using the on-board<br>
> VCXO with<br>
> the 5351B, you can't use a high quality external oscillator, so phase<br>
> noise and overall frequency stability could be an issue, too.<br>
><br>
> Anyhow, for my applications, I'm following the Si5351 with a secondary<br>
> clean-up VCO/PLL, which was already in the radios. I just needed a<br>
> frequency-agile reference oscillator, so to speak. I think the<br>
> Si5351 will<br>
> work well for this, based on my preliminary tests! (I'd certainly<br>
> like to<br>
> hear the experiences from anyone who has already been down this road!)<br>
><br>
> I guess you're not finding any local sources of surplus radios?<br>
> Do you<br>
> have any 6m power amps available?<br>
><br>
><br>
> 73, David KB4FXC<br>
><br>
><br>
><br>
> On Mon, 6 Jun 2016, Steve Wright wrote:<br>
><br>
> > On 04/06/16 04:00, Joe Leikhim <<a href="mailto:rhyolite@leikhim.com">rhyolite@leikhim.com</a><br>
> <mailto:<a href="mailto:rhyolite@leikhim.com">rhyolite@leikhim.com</a>>> wrote:<br>
> > > Assuming the VCO is part of a PLL, the PLL will tend to<br>
> "correct" the<br>
> > > modulation, [....]<br>
> ><br>
> > Was planning to use the Si5351B - has VCO input.<br>
> ><br>
> > S<br>
> ><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 4<br>
> Date: Mon, 6 Jun 2016 11:03:11 -0400<br>
> From: Joe Moskalski <<a href="mailto:kc2irv@gmail.com">kc2irv@gmail.com</a> <mailto:<a href="mailto:kc2irv@gmail.com">kc2irv@gmail.com</a>>><br>
> To: <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>><br>
> Subject: Re: [App_rpt-users] RTCM Simulcast question<br>
> Message-ID:<br>
><br>
> <CAES28qxB06niu+nL4Y5QfUvgZFf-y8s=<a href="mailto:uZdH2afzxKnwr0HV%2Bw@mail.gmail.com">uZdH2afzxKnwr0HV+w@mail.gmail.com</a><br>
> <mailto:<a href="mailto:uZdH2afzxKnwr0HV%252Bw@mail.gmail.com">uZdH2afzxKnwr0HV%2Bw@mail.gmail.com</a>>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> > It seems clear that in order for simulcast to work properly with<br>
> the RTCM<br>
> > I will need to clock the CPU to the GPSDO. Is there a device<br>
> available to<br>
> > give you the 9.6 mhz reference from the 10 mhz out from the<br>
> GPSDO or does<br>
> > anyone have a schematic available so that I can build them myself?<br>
> ><br>
> ><br>
> <<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon</a>><br>
> Virus-free.<br>
> <a href="http://www.avast.com" rel="noreferrer" target="_blank">www.avast.com</a> <<a href="http://www.avast.com" rel="noreferrer" target="_blank">http://www.avast.com</a>><br>
> <<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link</a>><br>
> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/a36d4626/attachment-0001.html" rel="noreferrer" target="_blank">http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/a36d4626/attachment-0001.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 5<br>
> Date: Mon, 6 Jun 2016 11:36:01 -0400 (EDT)<br>
> From: David McGough <<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a> <mailto:<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a>>><br>
> To: <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>><br>
> Subject: Re: [App_rpt-users] RTCM Simulcast question<br>
> Message-ID:<br>
><br>
> <<a href="mailto:Pine.LNX.4.44.1606061122550.4196-100000@goliath.inttek.net">Pine.LNX.4.44.1606061122550.4196-100000@goliath.inttek.net</a><br>
> <mailto:<a href="mailto:Pine.LNX.4.44.1606061122550.4196-100000@goliath.inttek.net">Pine.LNX.4.44.1606061122550.4196-100000@goliath.inttek.net</a>>><br>
> Content-Type: TEXT/PLAIN; charset=US-ASCII<br>
><br>
><br>
> Hi Joe,<br>
><br>
> While on the subject of the Si5351 chips, the application of<br>
> converting<br>
> one reference clock to a secondary frequency is what they were<br>
> designed<br>
> for. So, since you've already got a GPS reference, this -might- be an<br>
> inexpensive starting point...For this application, you obviously won't<br>
> need all the bells and whistles presented in this article! See:<br>
><br>
> <a href="http://www.knology.net/~gmarcus/Si5351/Si5351_VFO_QEX.pdf" rel="noreferrer" target="_blank">http://www.knology.net/~gmarcus/Si5351/Si5351_VFO_QEX.pdf</a><br>
> <<a href="http://www.knology.net/%7Egmarcus/Si5351/Si5351_VFO_QEX.pdf" rel="noreferrer" target="_blank">http://www.knology.net/%7Egmarcus/Si5351/Si5351_VFO_QEX.pdf</a>><br>
> <a href="http://www.knology.net/~gmarcus" rel="noreferrer" target="_blank">http://www.knology.net/~gmarcus</a> <<a href="http://www.knology.net/%7Egmarcus" rel="noreferrer" target="_blank">http://www.knology.net/%7Egmarcus</a>><br>
><br>
> Note that I would replace the Si5351 25MHz reference with a decent<br>
> TCXO<br>
> (available on ebay, etc.)....Note that I haven't used the Si5351<br>
> with an<br>
> RTCM, there may be simpler/better ways???<br>
><br>
><br>
> 73, David KB4FXC<br>
><br>
><br>
><br>
><br>
> On Mon, 6 Jun 2016, Joe Moskalski wrote:<br>
><br>
> > > It seems clear that in order for simulcast to work properly<br>
> with the RTCM<br>
> > > I will need to clock the CPU to the GPSDO. Is there a device<br>
> available to<br>
> > > give you the 9.6 mhz reference from the 10 mhz out from the<br>
> GPSDO or does<br>
> > > anyone have a schematic available so that I can build them myself?<br>
> > ><br>
> > ><br>
> ><br>
> <<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon</a>><br>
> > Virus-free.<br>
> > <a href="http://www.avast.com" rel="noreferrer" target="_blank">www.avast.com</a> <<a href="http://www.avast.com" rel="noreferrer" target="_blank">http://www.avast.com</a>><br>
> ><br>
> <<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link</a>><br>
> > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2><br>
> ><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 6<br>
> Date: Mon, 6 Jun 2016 11:54:11 -0400<br>
> From: Joe Moskalski <<a href="mailto:kc2irv@gmail.com">kc2irv@gmail.com</a> <mailto:<a href="mailto:kc2irv@gmail.com">kc2irv@gmail.com</a>>><br>
> To: David McGough <<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a> <mailto:<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a>>><br>
> Cc: <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>><br>
> Subject: Re: [App_rpt-users] RTCM Simulcast question<br>
> Message-ID:<br>
><br>
> <<a href="mailto:CAES28qx-G3wytTXKMRVvzMNm%2B498_c-aeNB6JrTWmZOR7A7ZcA@mail.gmail.com">CAES28qx-G3wytTXKMRVvzMNm+498_c-aeNB6JrTWmZOR7A7ZcA@mail.gmail.com</a><br>
> <mailto:<a href="mailto:CAES28qx-G3wytTXKMRVvzMNm%252B498_c-aeNB6JrTWmZOR7A7ZcA@mail.gmail.com">CAES28qx-G3wytTXKMRVvzMNm%2B498_c-aeNB6JrTWmZOR7A7ZcA@mail.gmail.com</a>>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> I mentioned this to someone else, QRP Labs has a kit that creates<br>
> a OCXO<br>
> around the Si5351 chip. here is the link:<br>
><br>
> <a href="http://www.qrp-labs.com/ocxokit.html" rel="noreferrer" target="_blank">http://www.qrp-labs.com/ocxokit.html</a><br>
><br>
> If you couple this with another kit of theirs you can program it<br>
> it any<br>
> frequency you want. My only thought is would it be accurate/stable<br>
> enough.<br>
><br>
> <a href="http://www.qrp-labs.com/progrock.html" rel="noreferrer" target="_blank">http://www.qrp-labs.com/progrock.html</a><br>
><br>
><br>
><br>
> <<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon</a>><br>
> Virus-free.<br>
> <a href="http://www.avast.com" rel="noreferrer" target="_blank">www.avast.com</a> <<a href="http://www.avast.com" rel="noreferrer" target="_blank">http://www.avast.com</a>><br>
> <<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link</a>><br>
> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2><br>
><br>
> On Mon, Jun 6, 2016 at 11:36 AM, David McGough <<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a><br>
> <mailto:<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a>>> wrote:<br>
><br>
> ><br>
> > Hi Joe,<br>
> ><br>
> > While on the subject of the Si5351 chips, the application of<br>
> converting<br>
> > one reference clock to a secondary frequency is what they were<br>
> designed<br>
> > for. So, since you've already got a GPS reference, this -might-<br>
> be an<br>
> > inexpensive starting point...For this application, you obviously<br>
> won't<br>
> > need all the bells and whistles presented in this article! See:<br>
> ><br>
> > <a href="http://www.knology.net/~gmarcus/Si5351/Si5351_VFO_QEX.pdf" rel="noreferrer" target="_blank">http://www.knology.net/~gmarcus/Si5351/Si5351_VFO_QEX.pdf</a><br>
> <<a href="http://www.knology.net/%7Egmarcus/Si5351/Si5351_VFO_QEX.pdf" rel="noreferrer" target="_blank">http://www.knology.net/%7Egmarcus/Si5351/Si5351_VFO_QEX.pdf</a>><br>
> > <a href="http://www.knology.net/~gmarcus" rel="noreferrer" target="_blank">http://www.knology.net/~gmarcus</a> <<a href="http://www.knology.net/%7Egmarcus" rel="noreferrer" target="_blank">http://www.knology.net/%7Egmarcus</a>><br>
> ><br>
> > Note that I would replace the Si5351 25MHz reference with a<br>
> decent TCXO<br>
> > (available on ebay, etc.)....Note that I haven't used the Si5351<br>
> with an<br>
> > RTCM, there may be simpler/better ways???<br>
> ><br>
> ><br>
> > 73, David KB4FXC<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Mon, 6 Jun 2016, Joe Moskalski wrote:<br>
> ><br>
> > > > It seems clear that in order for simulcast to work properly<br>
> with the<br>
> > RTCM<br>
> > > > I will need to clock the CPU to the GPSDO. Is there a device<br>
> available<br>
> > to<br>
> > > > give you the 9.6 mhz reference from the 10 mhz out from the<br>
> GPSDO or<br>
> > does<br>
> > > > anyone have a schematic available so that I can build them<br>
> myself?<br>
> > > ><br>
> > > ><br>
> > > <<br>
> ><br>
> <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon</a><br>
> > ><br>
> > > Virus-free.<br>
> > > <a href="http://www.avast.com" rel="noreferrer" target="_blank">www.avast.com</a> <<a href="http://www.avast.com" rel="noreferrer" target="_blank">http://www.avast.com</a>><br>
> > > <<br>
> ><br>
> <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" rel="noreferrer" target="_blank">https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link</a><br>
> > ><br>
> > > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2><br>
> > ><br>
> ><br>
> > _______________________________________________<br>
> > App_rpt-users mailing list<br>
> > <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:App_rpt-users@ohnosec.org">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<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> and<br>
> scroll down<br>
> > to the bottom of the page. Enter your email address and press the<br>
> > "Unsubscribe or edit options button"<br>
> > You do not need a password to unsubscribe, you can do it via email<br>
> > confirmation. If you have trouble unsubscribing, please send a<br>
> message to<br>
> > the list detailing the problem.<br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/a06570ac/attachment.html" rel="noreferrer" target="_blank">http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/a06570ac/attachment.html</a>><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> App_rpt-users mailing list<br>
> <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:App_rpt-users@ohnosec.org">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>
><br>
> End of App_rpt-users Digest, Vol 88, Issue 16<br>
> *********************************************<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> App_rpt-users mailing list<br>
> <a href="mailto:App_rpt-users@ohnosec.org">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>
<br>
--<br>
Joe Leikhim<br>
<br>
<br>
Leikhim and Associates<br>
<br>
Communications Consultants<br>
<br>
Oviedo, Florida<br>
<br>
JLeikhim@Leikhim.com<br>
<br>
<a href="tel:407-982-0446" value="+14079820446">407-982-0446</a><br>
<br>
<a href="http://WWW.LEIKHIM.COM" rel="noreferrer" target="_blank">WWW.LEIKHIM.COM</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/00c882a2/attachment.html" rel="noreferrer" target="_blank">http://ohnosec.org/pipermail/app_rpt-users/attachments/20160606/00c882a2/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">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>
<br>
End of App_rpt-users Digest, Vol 88, Issue 19<br>
*********************************************<br>
</blockquote></div><br></div>