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

Sat Dec 24 07:28:24 UTC 2011

Jim, 

WOW, that was a quick feature update and new firmware addition. Man you work fast. 

Thanks for this great functional feature to the RTCM. An early Christmas gift! <GRIN>

73

Marshall - ke6pcv

  _____  

From: Jim Duuuude [mailto:telesistant at hotmail.com] 
Sent: Friday, December 23, 2011 8:34 PM
To: Marshall Oldham; conny at tangandjonsson.com
Cc: app_rpt mailing list
Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable

I've been really busy (and productive) today.

The new version (0.60) of the RTCM/Voter board firmware now supports the following:

Notification via CW of host connection failure (with the option of repeating it 
periodically if still failed, along with option of repeating it after receiver un-key).

Notification via CW of host connection restoral after failure. 

"Offline" repeat mode, where it becomes a "dumb" repeater if host connection is lost.
Includes settable hang time. The "Notification via CW of host connection failure" feature
also can serve as a CW identifier in this mode (and was designed to do so).

The CW speed, CW strings (content of messages), and some other stuff is user-settable
from a menu.

Speaking of menus, the "big humongous" main menu is now split in to 3 nice, smaller ones.
The 2 sub-menus are IP (networking) parameters, and "Offline Mode" parameters.

The only thing it does *NOT* do is generate CTCSS tone when transmitting. I doubt it ever
will, since we are pretty much out of code space in the processor. This would require the
use of floating point trig functions to calculate generation constants (or from a table), neither
of which we have room for.

The 0.60 version will be available on SVN at 2115 PST tonight.

JIM WB6NIL

  _____  

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

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
To: app_rpt-users at ohnosec.org
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 [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
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 

Regards,
Mark Guibord
Micro-Node International

_______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
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/9f618f95/attachment.html>