[App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable

Thu Dec 22 22:35:37 UTC 2011

I agree!  
I was going to ask exactly the same question.  Maybe this
loss-of-connectivity-failover function could be enhanced to include a
simple timed morse ID and dedicated repeater tail tone so you
know immediately that something is wrong.
Michael.VK5ZEA

----- Original Message -----
From: "Marshall Oldham" 
To:"Jim Duuuude" , 
Cc:"app_rpt mailing list" 
Sent:Thu, 22 Dec 2011 13:42:57 -0800
Subject:Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is
nowavailable

This would be a good function or to add in the future firmware!     

-------------------------
  FROM: Jim Duuuude [mailto:telesistant at hotmail.com] 
SENT: Thursday, December 22, 2011 12:51 PM
TO: conny at tangandjonsson.com
CC: Marshall Oldham; app_rpt mailing list
SUBJECT: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)
is nowavailable

   Not at the moment as the firmware currently stands. However, that's
not a bad idea.
It could simply act as a totally "dumb" controller and just repeat the
input back to
the output.

JIM

-------------------------
 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)
is nowavailable
From: conny at tangandjonsson.com
Date: Thu, 22 Dec 2011 13:46:17 -0700
CC: ke6pcv at cal-net.org; app_rpt-users at ohnosec.org
To: telesistant at hotmail.com

If you use RTCM as "generic" radio interface on the hill and a linux
box at a remote location connected over an IP connection and you loose
the connection can the RTCM failover to be a minimal repeater
controller on the hill? 
 73 de N5HC /Conny  
 On Dec 21, 2011, at 12:52 PM, Jim Duuuude wrote: 
  Yeah, that's the general idea. The location of the Linux server
running app_rpt/Asterisk can be
more or less anywhere within Internet connectivity of all of the
receiver and/or transmitter sites.
Of course, "Internet" can mean either some sort of public Internet
connection, or a privately-provided
Internet connection (low-cost microwave link(s), etc).

The only limitation is that an RTCM/Voter module *must* be located on
the same LAN as the Linux
server, to at least provide a GPS-based timing reference. A system
could be set up with a server
located in some sort of datacenter "on the ground", and all the radios
could have an RTCM "on the
hill" with them, and as long as there is Internet connectivity of some
sort between each of them
and the server, the system will work nicely. That is providing that
there is an RTCM located at
the server location also (whether or not that particular RTCM has
radio hardware connected to it
or not).

One minimal Linux server can easily support 1 or 2 dozen RTCM's (on 1
or 2 allstar nodes),
and a larger server could easily support MANY dozens of them on dozens
of allstar nodes.
Of course, you REALLY dont want to put too many of them on a single
server, being a potential
single point of failure. For pretty much any practical purpose, the
reasonable limitation is
the point of failure/redundancy issue, not technical limitations.

I'm not sure if you were clear on this, so I thought I would mention
that the RTCM is not just
usable as a GPS-timing-based Multi-Receiver Voting system and/or a
Simulcast Transmitter system.
It can also be used as a "generic" radio interface for a conventional
(non-GPS-based) either simplex
or full duplex (repeater) radio. The advantage of doing this would be
to not have the Linux
host "on the hill" with the radio (as mentioned above). In addition,
the RTCM allows for 
portable/mobile operation with a mobile/portable Internet connection
in both the GPS-based
and non-GPS-based environments. 

JIM WB6NIL

-------------------------
 From: ke6pcv at cal-net.org [1]
To: app_rpt-users at ohnosec.org [2]
Date: Wed, 21 Dec 2011 10:54:18 -0800
Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)
is nowavailable

I have been looking at the Allstar RTCM (Radio Thin Client
Module) and it really looks like a GREAT product and addition to the
already cool Allstar hardware.     Among all the other cool features
of the RTCM (Radio Thin Client Module) like Transmitter Simulcasting
and Receiver Voting, if I understand the documentation  correctly
you can use this very small Radio Thin Client Module at a remote
radio site to set up an Allstar repeater node if the site has
internet connection without a COMPUTER at the site?    Then you can
point the node on the hilltop back to a server on the ground somewhere
that is easy to get too?     How many total sites can
you use Radio Thin Client Modules on and point back to a single
server on the ground?      If this is the case, All I can say is
WOW, how cool!    73    Marshall          

-------------------------
FROM: app_rpt-users-bounces at ohnosec.org
[3] [mailto:app_rpt-users-bounces at ohnosec.org] ON BEHALF OF Mark
Guibord
SENT: Sunday, December 18, 2011 11:03 AM
TO: app_rpt-users at ohnosec.org [4]
SUBJECT: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is
nowavailable

	Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based
Voting Multi-Receiver and Simulcast Transmit System is now available
for purchase.  

	For more information visit http://micro-node.com/thin-m1.html [5]  

	Regards, 

	Mark Guibord 

	Micro-Node International 

_______________________________________________ App_rpt-users mailing
list App_rpt-users at ohnosec.org
[6] http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users [7] 
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org [8]
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users [9]

Links:
------
[1] mailto:ke6pcv at cal-net.org
[2] mailto:app_rpt-users at ohnosec.org
[3] mailto:app_rpt-users-bounces at ohnosec.org
[4] mailto:app_rpt-users at ohnosec.org
[5] http://micro-node.com/thin-m1.html
[6] mailto:App_rpt-users at ohnosec.org
[7] http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
[8] mailto:App_rpt-users at ohnosec.org
[9] http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20111223/c4cc4cf2/attachment.html>