<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>That explains it very well. But the MSF isn’t the problem yet, I don’
think. Isn’t it the remote base? Once we connect the RTCM to the MSF and it
controls the MSF and does the CWIDs won’t this issue disappear?</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=kd8usf@yahoo.com
href="mailto:kd8usf@yahoo.com">KD8USF</A> </DIV>
<DIV><B>Sent:</B> Wednesday, June 10, 2015 8:00 PM</DIV>
<DIV><B>To:</B> <A title=app_rpt-users@ohnosec.org
href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</A> </DIV>
<DIV><B>Subject:</B> Re: [App_rpt-users] Setting Up a Remote Base
w/RTCM</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV
style="FONT-SIZE: 16px; FONT-FAMILY: helveticaneue-light, helvetica neue light, helvetica neue, helvetica, arial, lucida grande, sans-serif; COLOR: #000; BACKGROUND-COLOR: #fff">
<DIV id=yui_3_16_0_1_1433571713052_282683><SPAN
id=yui_3_16_0_1_1433571713052_282742>The reason why you are seeing the pulse go
over the link is because when the link radio unkeys it hears the repeater tail
and therefore keys up the link again. I also run an MSF5000, it does the CWID
with no PL which keeps the ID off the link unless someone kerchunks the repeater
while it's ID'ing. One way to stop the pulsing would be to set no tail on the
repeater, but if you're like me I have at least a 2 sec tail because I don't
want the repeater going up and down all the time like a simplex radio, and with
no tail you would not hear the repeater come back to you when you keyed it
up.</SPAN></DIV>
<DIV id=yui_3_16_0_1_1433571713052_282877><SPAN
id=yui_3_16_0_1_1433571713052_282742>Andrew.</SPAN></DIV>
<DIV id=yui_3_16_0_1_1433571713052_282741> </DIV>
<DIV id=yui_3_16_0_1_1433571713052_282613 class=signature> </DIV>
<DIV> </DIV>
<DIV id=yui_3_16_0_1_1433571713052_282694
style="FONT-SIZE: 16px; FONT-FAMILY: helveticaneue-light, helvetica neue light, helvetica neue, helvetica, arial, lucida grande, sans-serif">
<DIV id=yui_3_16_0_1_1433571713052_282693
style="FONT-SIZE: 16px; FONT-FAMILY: helveticaneue, helvetica neue, helvetica, arial, lucida grande, sans-serif">
<DIV id=yui_3_16_0_1_1433571713052_282692 dir=ltr>
<HR SIZE=1>
<FONT id=yui_3_16_0_1_1433571713052_282691 size=2 face=Arial><B><SPAN
style="FONT-WEIGHT: bold">From:</SPAN></B> R. Wayne
<allstar@controlservers.net><BR><B><SPAN
style="FONT-WEIGHT: bold">To:</SPAN></B> app_rpt-users@ohnosec.org <BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, June 10, 2015 1:36
PM<BR><B id=yui_3_16_0_1_1433571713052_282690><SPAN
id=yui_3_16_0_1_1433571713052_282689
style="FONT-WEIGHT: bold">Subject:</SPAN></B> [App_rpt-users] Setting Up a
Remote Base w/RTCM<BR></FONT></DIV>
<DIV id=yui_3_16_0_1_1433571713052_282699 class=y_msg_container>
<DIV> </DIV>
<DIV id=yiv1169983959>
<DIV id=yui_3_16_0_1_1433571713052_282698 dir=ltr>
<DIV id=yui_3_16_0_1_1433571713052_282697 dir=ltr>
<DIV id=yui_3_16_0_1_1433571713052_282696
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV id=yui_3_16_0_1_1433571713052_282695>Our remote base isn’t cutting it. It
is half-duplex using a Vertex VX-4200. We are told that the audio has no bottom,
it is sending CWID that it hears from the repeater (I knew why) and is sending
pulses. I didn’t set the hardware or software up, so as I ask please know that I
am at the top of a mountain and the remote base at the bottom where we have
internet. Here’s what we are dealing with. Our intent is to attach the RTCM at
the repeater site once we have internet up there. Until then...</DIV>
<DIV id=yui_3_16_0_1_1433571713052_282700> </DIV>
<DIV id=yui_3_16_0_1_1433571713052_282701>The DB-15 on the back of the Vertex
VX-4200 is *almost* capable of being used as a repeater controller output.</DIV>
<DIV> </DIV>
<DIV id=yui_3_16_0_1_1433571713052_282702>Pin 1 = TX Audio</DIV>
<DIV id=yui_3_16_0_1_1433571713052_282703>Pin 2 = RX Audio</DIV>
<DIV>Pin 6 = External PTT</DIV>
<DIV>Pin 9 = COR (see notes)</DIV>
<DIV>Pin 15 = GRND</DIV>
<DIV> </DIV>
<DIV>COR is achieved by creating voltage divider using other pins. Only then
will one get COR but not COS. PL will only make it to the speaker on the front
panel and rear jack. PL IS NOT on pin 2. Pin 2 is squelched but when it receives
the repeater’s built-in controller (a Motorola MSF-5000). Every time our CWID
goes off our remote base sends it to everyone.</DIV>
<DIV> </DIV>
<DIV>Here are the problems. First, we’re told that we are committing link abuse
by “jumping” or key clicking every time someone else transmits on a node our
node replies. I don’t know what I am talking bout at this point. <IMG
class="yiv1169983959wlEmoticon yiv1169983959wlEmoticon-smile"
style="BORDER-TOP-STYLE: none; BORDER-BOTTOM-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none"
alt=Smile data-id="a18676e7-831c-3606-381d-971c8ad6125e">:-)</DIV>
<DIV> </DIV>
<DIV>Next I am told that our audio has no bottom end. No bass. The pin that
we’re able to pull from is the only source that we’re aware of and is the pin
used by Vertex to send audio to their VRS (mobile repeater).</DIV>
<DIV> </DIV>
<DIV><A href="http://www.shercoares.org/doc_files/manuals/vx4200_sm.pdf"
rel=nofollow
target=_blank>http://www.shercoares.org/doc_files/manuals/vx4200_sm.pdf</A></DIV>
<DIV> </DIV>
<DIV>I’ve been told to turn PL off and let the repeater pass through the tone.
But please remember that pin 2 has no PL on it. Only the front panel speaker and
rear speaker jack audio are muted by PL.</DIV>
<DIV> </DIV>
<DIV>The easiest solution may be a GM300 but I cannot get the darn software on
our old 386 laptop. The floppy decided to only read those created by itself.
We’re puckered up on this one.</DIV>
<DIV> </DIV>
<DIV>Suggestions are
appeciated.</DIV></DIV></DIV></DIV></DIV><BR>_______________________________________________<BR>App_rpt-users
mailing list<BR><A href="mailto:App_rpt-users@ohnosec.org"
ymailto="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"
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"
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></DIV></DIV></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>App_rpt-users mailing
list<BR>App_rpt-users@ohnosec.org<BR>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<BR><BR>To
unsubscribe from this list please visit
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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></DIV></BODY></HTML>