[arm-allstar] Pulse-Back & Building a Repeater

Sat Jul 4 09:52:27 EST 2015

Thank you and Justin as well. And Justin, I wasn't complaining. Email couldn’t pick-up the quizzical look in my eye like, “OK. Which wire do I cut. The blue or the red?” LOL BOOM! I’m not new at repeaters but I don’t usually modify them either. That it is on the MRTI solves the problem. I guess only one wire then needs to be run unless this is it. But I definitely want the MSF to drop PL as soon as the it loses PL but leave the transmitter on. Most users don’t use decode but those that do will have a treat. I don’t have such luck searching Repeater Builder yet. If you know what you are looking for it is easy. Like not knowing how to spell a word and \Mom telling you to look it up in the dictionary.

Thank you both again.

From: Bob Brown - WØNQX 
Sent: Saturday, July 04, 2015 6:45 AM
To: ARM Allstar 
Subject: Re: [arm-allstar] Pulse-Back & Building a Repeater

you will find it here......

http://www.repeater-builder.com/motorola/msf/msf-interface-signals.html

" I don't have an MSF5000 in front of me so I can't tell you exactly what pins these signals are on, but you need to run a wire jumper from RDSTAT to TX PL STRIP inside the station controller and this will cause the 5000 to encode PL only when the receiver signal is valid.  (COR + valid PL).
It's a really easy modification on that station."

--
Thanks in Advance

   Bob, WØNQX

   Kansas City Metro Area

   http://drsm0ke.net

   http://byrg.net

   http://sm0kenet.net

Quis custodiet ipsos custodes?

--

On Sat, Jul 4, 2015 at 2:21 AM, R. Wayne <allstar at controlservers.net> wrote:

  I appreciate this info but I don’t have a full schematic or PIN OUT chart to refer to. Otherwise this would be excellent news.

  From: Justin Reed 
  Sent: Sunday, June 28, 2015 7:43 AM
  To: ARM Allstar 
  Subject: Re: [arm-allstar] Pulse-Back & Building a Repeater

  I don't have an MSF5000 in front of me so I can't tell you exactly what pins these signals are on, but you need to run a wire jumper from RDSTAT to TX PL STRIP inside the station controller and this will cause the 5000 to encode PL only when the receiver signal is valid.  (COR + valid PL).

  It's a really easy modification on that station.

  Justin

  On 6/28/2015 4:02 AM, R. Wayne wrote:

    I don’t know if I should be sending this here or to arm-app_rpt.

    Our repeater is temporarily using a remote base to talk up to our machine. We have Internet there but have not configured it yet. Our emote base is sending pulse-backs and I don’t know how to stop it. It is also sending our CWID from our MSF using its internal controller. I cannot turn it off without violating part 97. AFAIK the MSF doesn’t allow me to tell it to wait until the hang time drops to ID. I am using a RTCM on the remote base and I can turn off CWID on the repeater and let the RTCM send the CWID. But we’re back to pulse-backs. How do I deal with them?

    Next, we want to drop our MSF’s and build repeaters for our three sites using Motorola CDM 750’s and their 20KHz channel spacing is more favorable to us. The MSF’s are 30KHz channel spacing with a 2MHz wide front-end. I can use a RTCM as the controller on each repeater. Or I’d rather use our external link controllers. We have RF links that come in as well. I know that this is a lot to ask but what is the best way to do this? I am assuming that the repeater goes on port 1. The RTCM will go on port 2 or I can build a BBB and use a USB FOB. Port 3 would be for an external RF link that comes in. Our Allstar server is setup using .0320 and id bridged to another RoIP service. It also has Echolink but it is not active. Our link controller is fully addressable with a preamble that should allow me to avoid DTMF issues. I don’t know abut users in the repeater trying to control it or autopatch, which we have. Is this doable or have I misunderstood?

    I am grateful to this group for getting me this far. I look forward to get Allmon setup, announcements, etc., although our link controller has 250 DVR tracks.

    Thank you again in advance.

_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2 web page - http://hamvoip.org

------------------------------------------------------------------------------
  _______________________________________________

  arm-allstar mailing list
  arm-allstar at hamvoip.org
  http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

  Visit the BBB and RPi2 web page - http://hamvoip.org 

  _______________________________________________

  arm-allstar mailing list
  arm-allstar at hamvoip.org
  http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

  Visit the BBB and RPi2 web page - http://hamvoip.org

--------------------------------------------------------------------------------
_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150704/55688714/attachment.html>