Allstar RTCM (Radio Thin Client Module) is now available
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
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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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
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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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 GuibordMicro-Node International _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
At 06:52 AM 12/22/2011, 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).
Hmm, a very tempting piece of hardware! :) 73 de VK3JED / VK3IRL http://vkradio.com
I agree Tony... I have one application that is crying out for this box RIGHT NOW. Michael. VK5ZEA On 22/12/2011 06:45, Tony Langdon, VK3JED wrote:
At 06:52 AM 12/22/2011, 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).
Hmm, a very tempting piece of hardware! :)
73 de VK3JED / VK3IRL http://vkradio.com
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
At 07:26 AM 12/22/2011, Michael Carey wrote:
I agree Tony... I have one application that is crying out for this box RIGHT NOW.
I can also see a lot of potential for "out of the box" solutions using this box. It's quite inexpensive for what it does. 73 de VK3JED / VK3IRL http://vkradio.com
Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv _____ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Yeah you got it. Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works. JIM WB6NIL From: ke6pcv@cal-net.org To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Date: Wed, 21 Dec 2011 12:23:28 -0800 Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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 GuibordMicro-Node International _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
An interesting side note form yesterday's install: While no port forwarding is necessary at the receiver sites, it is necessary at the master site. You must port forward port 667 UDP to the asterisk/app_rpt/voter. Unfortunately our IT guys were not around to set up the port forwarding for us. So we decided to use another port that was still forwarded but no longer used. Thanks to Jim having the foresight to allow any port to be used!!! It may be of some interest to note that the port we used was one of the IRLP ports. :-) -- Tim :wq On Dec 21, 2011, at 12:52 PM, Jim Duuuude wrote:
Yeah you got it.
Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works.
JIM WB6NIL
From: ke6pcv@cal-net.org To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Date: Wed, 21 Dec 2011 12:23:28 -0800
Jim,
Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house?
If I understand this correctly this would mean that:
1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software.
If so, this seems like a pretty cool little piece of hardware!
Marshall - ke6pcv
From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable
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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Jim, All I can say is WOW! I love the fact that you don't need a "COMPUTER" at the remote site and you don't need to deal with the "PORT FORWARDING" issue or network provisioning as well. It sure seems like you guys have made a simple, easy to use product that is really a good bargain. When you start adding up the cost of hardware to build an Allstar node the "Old Fashion Way" <GRIN> with a computer and Sound FOB, the RTCM sure seems to be a pretty good deal. And it is very small and does not take up any space in the equipment rack at a repeater site. Marshall _____ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 12:52 PM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Yeah you got it. Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works. JIM WB6NIL _____ From: ke6pcv@cal-net.org To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Date: Wed, 21 Dec 2011 12:23:28 -0800 Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv _____ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Now THIS is what I wanted to hear. So I guess as long as I can ping the AllStar server, then it will work. We have a large wireless LAN network but each geographical section is on its own ip range. I have 10 repeater sites I want to link up. Looks like my D-Star project must be put on hold for awhile. Anyone want to buy 4x URIx's? Shaun zr5s Ps! "Low Power Input voltage (7-24Vdc approximately 80ma) " You must be pulling my co-ax, or is this really true? On 21/12/11 22:52, Jim Duuuude wrote:
Yeah you got it.
Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works.
JIM WB6NIL
------------------------------------------------------------------------ From: ke6pcv@cal-net.org To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Date: Wed, 21 Dec 2011 12:23:28 -0800
Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv
------------------------------------------------------------------------ *From:* Jim Duuuude [mailto:telesistant@hotmail.com] *Sent:* Wednesday, December 21, 2011 11:52 AM *To:* Marshall Oldham; app_rpt mailing list *Subject:* RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable
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@cal-net.org To: app_rpt-users@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, ifI 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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] *On Behalf Of *Mark Guibord *Sent:* Sunday, December 18, 2011 11:03 AM *To:* app_rpt-users@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 visithttp://micro-node.com/thin-m1.html
Regards,
Mark Guibord
Micro-Node International
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
No virus found in this message. Checked by AVG - www.avg.com <http://www.avg.com> Version: 2012.0.1890 / Virus Database: 2109/4694 - Release Date: 12/21/11
yep, if you get pingage you get connectage. JIM Date: Thu, 22 Dec 2011 04:09:56 +0200 From: shaun@pmbnet.co.za To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Now THIS is what I wanted to hear. So I guess as long as I can ping the AllStar server, then it will work. We have a large wireless LAN network but each geographical section is on its own ip range. I have 10 repeater sites I want to link up. Looks like my D-Star project must be put on hold for awhile. Anyone want to buy 4x URIx's? Shaun zr5s Ps! "Low Power Input voltage (7-24Vdc approximately 80ma) " You must be pulling my co-ax, or is this really true? On 21/12/11 22:52, Jim Duuuude wrote: Yeah you got it. Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works. JIM WB6NIL From: ke6pcv@cal-net.org To: telesistant@hotmail.com; app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Date: Wed, 21 Dec 2011 12:23:28 -0800 Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2109/4694 - Release Date: 12/21/11
What is the maximum latency that can be tolerated? I just returned from a road trip during which I streamed my mobile scanner monitoring railroad communications (yes, some people actually listen to that stuff). I kept a ping process running on my little netbook computer running the streaming application to see when my phone fell out of range. I noted typical ping times in the several hundred millisecond range on AT&T's mobile data network, which might be of interest to those intending to run mobile nodes like this. Keep in mind that ping is the red-headed step-child of protocols and its payload can be dropped at will by routers in favor of more important payloads, so real traffic can still squeeze its way through when your ping packets get dropped on the floor. Bote W4NUD From: Jim Duuuude Sent: Wednesday, 21 December, 2011 23:10 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable yep, if you get pingage you get connectage. JIM _____ Date: Thu, 22 Dec 2011 04:09:56 +0200 From: shaun@pmbnet.co.za Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Now THIS is what I wanted to hear. So I guess as long as I can ping the AllStar server, then it will work. We have a large wireless LAN network but each geographical section is on its own ip range. I have 10 repeater sites I want to link up. Looks like my D-Star project must be put on hold for awhile. Anyone want to buy 4x URIx's? Shaun zr5s On 21/12/11 22:52, Jim Duuuude wrote: Yeah you got it. Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works. JIM WB6NIL
It will definitely handle 500ms without any problems (I think the actual limit is around 700ms or so). That is limited by the amount of RAM buffer available in the RTCM/Voter module. The "host" side, of course, could probably buffer hours if you put enough RAM in it :-). In addition, it supports use of an ADPCM codec (which uses 1/2 the bandwidth of the normal one) and has a 40ms packet rate, rather then the usual 20ms rate both of which are well-suited for a marginal "mobile" connection environment. JIM WB6NIL From: bote_radio@botecomm.com To: app_rpt-users@ohnosec.org Date: Thu, 22 Dec 2011 06:44:45 -0500 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable What is the maximum latency that can be tolerated? I just returned from a road trip during which I streamed my mobile scanner monitoring railroad communications (yes, some people actually listen to that stuff). I kept a ping process running on my little netbook computer running the streaming application to see when my phone fell out of range. I noted typical ping times in the several hundred millisecond range on AT&T's mobile data network, which might be of interest to those intending to run mobile nodes like this. Keep in mind that ping is the red-headed step-child of protocols and its payload can be dropped at will by routers in favor of more important payloads, so real traffic can still squeeze its way through when your ping packets get dropped on the floor. BoteW4NUD From: Jim Duuuude Sent: Wednesday, 21 December, 2011 23:10 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable yep, if you get pingage you get connectage. JIMDate: Thu, 22 Dec 2011 04:09:56 +0200 From: shaun@pmbnet.co.za Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Now THIS is what I wanted to hear. So I guess as long as I can ping the AllStar server, then it will work. We have a large wireless LAN network but each geographical section is on its own ip range. I have 10 repeater sites I want to link up. Looks like my D-Star project must be put on hold for awhile. Anyone want to buy 4x URIx's? Shaun zr5s On 21/12/11 22:52, Jim Duuuude wrote: Yeah you got it. Another thing I probably should have mentioned is that the RTCM/Voter module uses an Internet protocol that is specifically designed to work on ANY Internet connection from which "generic web surfing" is possible (behind any number of NAT routers/firewalls, etc and where LAN address is provided via DHCP). No "port forwarding" or "network provisioning" nightmares are necessary. You can just plug it in and it works. JIM WB6NIL _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Hi Marshall et al, Yesterday Jim helped us get the voter stuff installed on our two meter Micor repeaters here in the SoCal area. It's working awesome! You cannot tell when the voter switches sites... the audio transfers without any sort of click or telltale indication of any kind. There is a cool command in app_rpt that shows you how the voter is performing in real time. The command is "voter display your_node_no" and it looks like this: It shows you on a scale of 0 to 255 the amount of quieting. It looks much like the RX level set thingy in app_rpt. The currently selected receiver will have an asterisk before it's name. The scale slides up and down and the asterisk jumps back and forth as the voter operates. It's really interesting and fun to watch it as people are using the system. We are also simulcasting. The city hall transmitter's coverage (of the basement) does not overlap Santiago so we didn't need TX freq stabilization. If and when we do need to expand the city hall coverage we have Trimble Thunderbolt GPS' installed and ready stabilize a couple of Quantars (wish, wish) or Jim's soon-to-be-released frequency divider goodie. I've attached a simple block diagram of the system. -- Tim :wq On Dec 21, 2011, at 12:23 PM, Marshall Oldham wrote:
Jim,
Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house?
If I understand this correctly this would mean that:
1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software.
If so, this seems like a pretty cool little piece of hardware!
Marshall - ke6pcv
From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable
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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Tim, Thanks for the display and the block diagram. I can't wait to play with some of this new hardware when I get time. This is all very cool stuff! :) I am really excited about the possibilities and flexibility of this new hardware and technology! 73 Marshall - ke6pcv _____ From: Tim Sawyer [mailto:tim.sawyer@me.com] Sent: Wednesday, December 21, 2011 1:36 PM To: Marshall Oldham; app_rpt mailing list Cc: Jim Duuuude Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable Hi Marshall et al, Yesterday Jim helped us get the voter stuff installed on our two meter Micor repeaters here in the SoCal area. It's working awesome! You cannot tell when the voter switches sites... the audio transfers without any sort of click or telltale indication of any kind. There is a cool command in app_rpt that shows you how the voter is performing in real time. The command is "voter display your_node_no" and it looks like this:
Hi Marshal, We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is "perma-link" nodes. The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS's 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical. The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater's output. Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don't have much simulcast data, the overlap area is quite small. The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it's dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems. Over all very cool stuff... Pete WI6H... From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv ________________________________ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Before I break open my kid's piggy-bank for a couple of "ALLSTAR RTCM (RADIO THIN CLIENT MODULE)'s " http://micro-node.com/thin-m1.html I need an important question answered. .............please? If both rptr's are in the same coverage area, and transmit at the same time on the same freq, BUT perfectly in sync using the GPS sync option...................... will the end user (client/club member) hear a perfect signal? (even if he/she where in range of both transmitters?) One would think you would hear a heterodyne of some sort with both signals reaching and mixing into the users transceiver. We all know that if 2 hams try use their local repeater at the same time (doubling) then the end result is Yucky, unless the one users tx signal is much stronger than the other user. Is this RTCM system so accurate, that the user hears a perfectly synced and clear signal? Shaun zr5s
Yes. That's how simulcast systems work. When you base your syncronization on a GPSDO (GPS Disciplined Oscillator) such as the Trimble Thunderbolt (which has accuracy typically of 10-20 parts per TRILLION, which means that if you were transmitting at 1GHz, you would be no more then 0.010 to 0.020 Hz off) *and* the audio is in sync with that timing source *and* the deviation is set consistently accurately between all transmitters, then, yes, its quite possible. Obviously, you need to use transmitters appropriately suited for this type of application, which either by initial design or by modification, allow injection of an external (to the transmitter) reference frequency. Some transmitters are designed with this in mind. Others can be trivially modified to allow this. For example, the Trimble Thunderbolt has its precise frequency output at 10 MHz. Some transmitters will operate directly from the frequency reference. Others need some other frequency. If this is the case, a clock generator (locked to the Thunderbolt's 10 Mhz output) that produces the appropriate frequency is needed. Some radio manufacturers, such as the one that Pete Elke (WI6H) was referring to make devices specifically suited for this purpose (he was using the clock generator within a high stability oscillator unit from an old Motorola paging transmitter). Another option would be to use the PCGM (Programmable Clock Generator Module) that Mark at Micro-Node (K7IZA) is coming out with soon. It takes the 10 MHz input from the Trimble Thunderbolt, and generates pretty much whatever reference frequency you "tell it to" (from 6-200 MHz), and also, acts as a power supply for the Trimble Thunderbolt. The reason I keep making specific reference to the Trimble Thunderbolt is because they are readily available on the surplus market (rather inexpensively), and are EXTEREMELY well-suited for this application (probably the best selection given all of the parameters involved here). JIM WB6NIL
Date: Thu, 22 Dec 2011 12:41:11 +0200 From: shaun@pmbnet.co.za To: app_rpt-users@ohnosec.org; zs5bg@harc.org.za; zs5z@harc.org.za Subject: [App_rpt-users] RADIO THIN CLIENT MODULE and "Simulcast Transmit System"
Before I break open my kid's piggy-bank for a couple of "ALLSTAR RTCM (RADIO THIN CLIENT MODULE)'s " http://micro-node.com/thin-m1.html I need an important question answered. .............please?
If both rptr's are in the same coverage area, and transmit at the same time on the same freq, BUT perfectly in sync using the GPS sync option...................... will the end user (client/club member) hear a perfect signal? (even if he/she where in range of both transmitters?) One would think you would hear a heterodyne of some sort with both signals reaching and mixing into the users transceiver.
We all know that if 2 hams try use their local repeater at the same time (doubling) then the end result is Yucky, unless the one users tx signal is much stronger than the other user.
Is this RTCM system so accurate, that the user hears a perfectly synced and clear signal?
Shaun zr5s
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Hi Shaun, At the moment we are limited to transmitters that use 14.4Mhz as their oscillator base (MCX. Syntors, MSF500s, MaxTrax) since the Motorola UHSO only creates that frequency from the 10mhz Trimble GPS. If we select a different transmitter model (that is not 14.4 based) a clock generator like Mark's Programmable Clock Generator Module will be needed. We were lucky in that I had a bunch of UHSO units for a 900Mhz project that we could borrow for the thin client 440 project. Pete/WI6H From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim Duuuude Sent: Thursday, December 22, 2011 4:25 AM To: shaun@pmbnet.co.za; app_rpt mailing list; zs5bg@harc.org.za; zs5z@harc.org.za Subject: Re: [App_rpt-users] RADIO THIN CLIENT MODULE and "Simulcast Transmit System" Yes. That's how simulcast systems work. When you base your syncronization on a GPSDO (GPS Disciplined Oscillator) such as the Trimble Thunderbolt (which has accuracy typically of 10-20 parts per TRILLION, which means that if you were transmitting at 1GHz, you would be no more then 0.010 to 0.020 Hz off) *and* the audio is in sync with that timing source *and* the deviation is set consistently accurately between all transmitters, then, yes, its quite possible. Obviously, you need to use transmitters appropriately suited for this type of application, which either by initial design or by modification, allow injection of an external (to the transmitter) reference frequency. Some transmitters are designed with this in mind. Others can be trivially modified to allow this. For example, the Trimble Thunderbolt has its precise frequency output at 10 MHz. Some transmitters will operate directly from the frequency reference. Others need some other frequency. If this is the case, a clock generator (locked to the Thunderbolt's 10 Mhz output) that produces the appropriate frequency is needed. Some radio manufacturers, such as the one that Pete Elke (WI6H) was referring to make devices specifically suited for this purpose (he was using the clock generator within a high stability oscillator unit from an old Motorola paging transmitter). Another option would be to use the PCGM (Programmable Clock Generator Module) that Mark at Micro-Node (K7IZA) is coming out with soon. It takes the 10 MHz input from the Trimble Thunderbolt, and generates pretty much whatever reference frequency you "tell it to" (from 6-200 MHz), and also, acts as a power supply for the Trimble Thunderbolt. The reason I keep making specific reference to the Trimble Thunderbolt is because they are readily available on the surplus market (rather inexpensively), and are EXTEREMELY well-suited for this application (probably the best selection given all of the parameters involved here). JIM WB6NIL
Date: Thu, 22 Dec 2011 12:41:11 +0200 From: shaun@pmbnet.co.za To: app_rpt-users@ohnosec.org; zs5bg@harc.org.za; zs5z@harc.org.za Subject: [App_rpt-users] RADIO THIN CLIENT MODULE and "Simulcast Transmit System"
Before I break open my kid's piggy-bank for a couple of "ALLSTAR RTCM (RADIO THIN CLIENT MODULE)'s " http://micro-node.com/thin-m1.html I need an important question answered. .............please?
If both rptr's are in the same coverage area, and transmit at the same
time on the same freq, BUT perfectly in sync using the GPS sync option...................... will the end user (client/club member) hear a perfect signal? (even if he/she where in range of both transmitters?) One would think you would hear a heterodyne of some sort with both signals reaching and mixing into the users transceiver.
We all know that if 2 hams try use their local repeater at the same time (doubling) then the end result is Yucky, unless the one users tx signal is much stronger than the other user.
Is this RTCM system so accurate, that the user hears a perfectly synced and clear signal?
Shaun zr5s
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Some observations: You beat us to the punch, but that's OK. We would call this a gateway, which is what most in the industry call it and should give you greater traction on the commercial market. I would also substitute "tcp/ip" for "internet" as a broader term that doesn't scare people who see the Internet as a den of iniquity rife with malware and trouble. This device is still a computer, albeit a simplified one. Note that it has a reset button on it, just like the gateway that one of my clients produces. Every once in a great while I need to hit that button, FYI. It could be caused by a power glitch or excessive RF impinging on the box, but overall they can be quite reliable, just not a panacea. I have heard from commercial radio shop guys involved with setting up simulcast 2-way LMR systems remark that simulcast systems were never intended to have large interference (overlap) zones. They initially were seen as ways to connect regions separated by geographical boundaries, such as mountains. Then the salesmen just HAD to sell them to customers on flat land, which is when the fun began in the days before we mere peons could access accurate gps signals. Presumably gps synchronization solves most of the problems, but with analog radio systems running 5KC deviation on UHF it actually worked a little better to have the transmitter frequencies dithered a few Hertz either way. Don't ask me why, but that's what the boys at the PEPCo radio shop found out. Maybe there are better, newer findings these days. Overall, I'm not a fan of simulcast transmitters, particularly in amateur radio service where (I hope!) the users are technically savvy enough to know when to switch to another repeater to extend coverage. If you can make it work, then great! Bote W4NUD From: Peter Elke Sent: Thursday, 22 December, 2011 04:10 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Hi Marshal, We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is “perma-link” nodes. The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS’s 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical. The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater’s output. Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don’t have much simulcast data, the overlap area is quite small. The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it’s dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems. Over all very cool stuff… Pete WI6H… From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv _____ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
How do you control launch delay for your simulcast transmitters? 73 Jim W7RY From: Peter Elke Sent: Thursday, December 22, 2011 1:10 AM To: app_rpt mailing list Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)isnowavailable Hi Marshal, We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is "perma-link" nodes. The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS's 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical. The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater's output. Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don't have much simulcast data, the overlap area is quite small. The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it's dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems. Over all very cool stuff. Pete WI6H. From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv ------------------------------------------------------------------------------ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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 GuibordMicro-Node International _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -------------------------------------------------------------------------------- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2109/4695 - Release Date: 12/21/11
Despite the fact that in my personal experience I have never been involved in a case where it was necessary to have "launch delay", there certainly a number of people that have done these things for years that are of the opinion that it sure is necessary in certain cases. Currently as the device currently stands, it does not inherently support this feature. It was intended that in cases where this was necessary, it could be accomplished externally to the RTCM. Some transmitters (such as the Motorola Quantar, which we have used somewhat extensively so far and had WONDERFUL results) have that feature built in to them, since use as a simulcast transmitter was designed into them from the beginning. In situations where this is not the case, an external variable delay device can be utilized to accomplish this feature. If experience over time shows us that there are a significant number of users that require (as opposed to just wanting, for no good reason) this feature, I have no problem designing that feature into a new version of the RTCM/Voter board. It would, however increase the cost and complexity of the device. At this time, it is not included in the current version of the device. JIM WB6NIL From: w7ry@centurytel.net To: pete.elke@esquared.com; app_rpt-users@ohnosec.org Date: Thu, 22 Dec 2011 08:00:59 -0800 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)isnowavailable How do you control launch delay for your simulcast transmitters? 73 Jim W7RY From: Peter Elke Sent: Thursday, December 22, 2011 1:10 AM To: app_rpt mailing list Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)isnowavailable Hi Marshal, We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is “perma-link” nodes. The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS’s 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical. The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater’s output. Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don’t have much simulcast data, the overlap area is quite small. The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it’s dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems. Over all very cool stuff… Pete WI6H… From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable 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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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 GuibordMicro-Node International _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2109/4695 - Release Date: 12/21/11 _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
What is launch delay and it's purpose? -- Tim :wq On Dec 22, 2011, at 8:00 AM, Jim W7RY wrote:
How do you control launch delay for your simulcast transmitters?
73 Jim W7RY
From: Peter Elke Sent: Thursday, December 22, 2011 1:10 AM To: app_rpt mailing list Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)isnowavailable
Hi Marshal,
We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is “perma-link” nodes.
The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS’s 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical.
The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater’s output.
Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don’t have much simulcast data, the overlap area is quite small.
The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it’s dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems.
Over all very cool stuff…
Pete WI6H…
From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable
Jim,
Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventional full duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features? As long as I have some sort of internet connection at the remote sites back to my house?
If I understand this correctly this would mean that:
1) No cost of computer at the radio site. 2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it. 3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software.
If so, this seems like a pretty cool little piece of hardware!
Marshall - ke6pcv
From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable
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@cal-net.org To: app_rpt-users@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2109/4695 - Release Date: 12/21/11
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
The general concept is that since radio waves travel at the speed of light, if transmitters in a simulcast system are sufficiently far apart, there are "zones" in which the signals get sufficiently out of phase with each other, based upon distance from the transmitters. "Launch Delay" is a feature, that allows a fixed delay to put put the in the modulation audio (in the microsecond (and fractions thereof) range) in an attempt to "compensate" for such areas (attempt to make the signals "meet" in the proper areas). In practice, sometimes its rather straightforward, and sometimes, its just kinda of a "black magic" to get this anywhere near right or reasonable. Sometimes, using this ends up making things even worse then not having it at all (being that sometimes, when you "fix" one area, you "break" others). Clearly every case is unique. JIM WB6NIL From: tim.sawyer@me.com Date: Thu, 22 Dec 2011 09:13:49 -0800 To: w7ry@centurytel.net CC: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)isnowavailable What is launch delay and it's purpose? -- Tim :wq On Dec 22, 2011, at 8:00 AM, Jim W7RY wrote:How do you control launch delay for your simulcast transmitters? 73Jim W7RY From: Peter ElkeSent: Thursday, December 22, 2011 1:10 AMTo: app_rpt mailing listSubject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module)isnowavailable Hi Marshal, We have been running two separate test projects with the module over the last few weeks. So far they seem very functional and cut down on node management if your goal is “perma-link” nodes. The first project is to take separate sites and merge them into one frequency (and one big node). At this point we have two of the eight cut over and we have worked out the basic mechanics. We use Micor receivers and MSX100 transmitters (that may change). The transmitters are frequency locked using MSF5000 UHSO units with the reference source being a GPS’s 10Mhz output. The UHSO creates 14.4Mhz that is fed into the MCX units. In our testing it became very clear that all of the radios need to be identical. The voting is very cool, you can watch as is switches between the receive sites (very quickly, multiple times in a 1 second period) and the toggling goes unnoticed on the repeater’s output. Our next phase is to create larger overlapping coverage area to see how it sounds mixed by adding a third site in the middle of the current two. At this point we don’t have much simulcast data, the overlap area is quite small. The other project is an upgrade to my portable Beagleboard node that I use traveling. The old version was an Astro portable driven by a LOX board. The Beagle had a USB WiFi to a Verizon hot spot box. The upgrade swaps out the beagle for a RTCM and makes the connection from the road automatic. To create the internet for the module the old USB wifi was switched out for a Ubiquiti PicoStation set up as a bridge. When there is cell coverage it works and when there is no cell coverage it’s dead, simple, easy, no-dialing. The first road test was today, all went well other than some LTE Verizon problems. Over all very cool stuff… Pete WI6H… From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Marshall Oldham Sent: Wednesday, December 21, 2011 12:23 PM To: 'Jim Duuuude'; 'app_rpt mailing list' Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) isnowavailable Jim, Okay so one server running Allstar node software at a central location (like my house) can support a dozen RTCM's being used as "Generic" conventionalfull duplex (repeaters) radio interfaces on far away hilltops even if I do not want to use the RTCM GPS-Timing Multi receiver voting or Simulcast Transmitter features?As long as I have some sort of internet connection at the remote sites back to my house? If I understand this correctly this would mean that: 1) No cost of computer at the radio site.2) No worry about the node computer locking up at the remote radio site and having to reboot or reset it.3) No cost other than the RTCM (Radio Thin Client Module) to setup an Allstar node at the remote radio site. (no computer, no URI, no Sound FOB) 4) If I use the RTCM (Radio Thin Client Module) I have the ability to setup a normal Allstar node at the present time and then later if I want to I can upgrade the hilltop for GPS-Timing Multi receiver voting and Simulcast Transmitter by simply adding a GPS receiver at the site and reconfiguring the software. If so, this seems like a pretty cool little piece of hardware! Marshall - ke6pcv From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Wednesday, December 21, 2011 11:52 AM To: Marshall Oldham; app_rpt mailing list Subject: RE: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailableYeah, 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@cal-net.org To: app_rpt-users@ohnosec.org Date: Wed, 21 Dec 2011 10:54:18 -0800 Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailableI 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 documentationcorrectly 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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Mark Guibord Sent: Sunday, December 18, 2011 11:03 AM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailableAllstar 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 GuibordMicro-Node International _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users___________________... App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2109/4695 - Release Date: 12/21/11_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (10)
-
Bote Man -
Jim Duuuude -
Jim W7RY -
Mark Guibord -
Marshall Oldham -
Michael Carey -
Peter Elke -
Shaun Rudling -
Tim Sawyer -
Tony Langdon, VK3JED