[Allstar Digital] DMRlink, HBlink AllStarLink etc.

Steve Zingman szingman at msgstor.com
Fri May 26 17:15:41 EDT 2017 

Michael,
Our DMRGateway program was a analog to DMRlink bridge. It's been out for 
a while and we were getting problems reported that were hard to pin 
down. When Mike looked deeper he figured out where major issue was. That 
started us down the road of being able to support HBlink. HBlink had 
major advantages when connecting to a BM network. No BM admin 
intervention required. It turned out that the method of connecting to 
DMRGateway could be simplified and leveraged to connect IPSC to HB. 
After much back and forth we settled on the "partner" concept. Partners 
talk to each other. Now what do we call them? IPSC_bridge? OK. 
HB_bridge? OK. What do we do with DMRGateway. it was odd man out. I did 
not want to rename it. We had a years worth of exposure with that name. 
But it had to be consistent. So... Analog_bridge. Some of this 
discussion was done at Dayton. We decided to demo at Dayton and use the 
new names. No sooner do we get back and Jonathan announces DMRGateway. 
The name fits perfectly with the other gateways he built for the other 
modes. Sometimes timing works.

What is this thing sleep you speak of? And where can I download it?

73, Steve N4IRS

On 05/26/2017 04:25 PM, Michael Hebert wrote:
> Steve,
>
> When do you guys sleep! I am trying to hold on to your coat tales and 
> can barely keep my head above the water. LOL. I want to better 
> understand the Analog_bridge and DMRgateway. So, it seems you 
> relabeled your DMRGateway release to Analog_bridge and Jonathan 
> released a version called DMRGateway. It looks like his allows for the 
> connection of up to three different DMR networks to one MMDVM system.
>
> Thanks again to all of you that contribute!! This is really and 
> exciting time in Ham Radio
>
> Michael KD5DFB
>
> On Tue, May 23, 2017 at 11:01 AM, Steve Zingman <szingman at msgstor.com 
> <mailto:szingman at msgstor.com>> wrote:
>
>      I should have done this the first day of Hamvention 2017, but
>     busy does not describe the last couple of weeks. Mike N4IRR and I
>     have been working on updating and expanding the bridging ability
>     of ASL, DMRlink and HBlink.
>     The new applications are referred to as Partners. Partners by
>     themselves don't do much. When 2 or more partners communicate, the
>     partnership forms a bridge between different systems.
>
>      DMRlink is the Open Source IPSC Master / Peer "stack" written in
>     python by Cort Buffington, N0MJS. Applications are built on top of
>     this stack. An example application built on top of the stack is
>     the parrot. DMRlink provides the communications to and from IPSC.
>     This can be a Motorola repeater or a Network device like c-Bridge
>     or BrandMeister. We have added to the available applications,
>     IPSC_bridge. This partner application communicates with DMRlink
>     and provides a bridge to other systems.
>
>      HBlink is the Open Source HB Master / Peer "stack" written in
>     python by Cort Buffington, N0MJS. Applications are built on top of
>     this stack. An example application built on top of the stack is
>     the parrot. HBlink provides the communications to and from HB
>     Repeater Protocol. This can be a MMDVM repeater, DVMega HotSpot,
>     OpenSpot or a Network device like DMR+ or BrandMeister. We have
>     added to the available applications, HB_bridge. This partner
>     application communicates with HBlink and provides a bridge to
>     other systems.
>
>      The third partner is not quite new. New capabilities have been
>     added and old capabilities enhanced. That partner is called
>     Analog_bridge.  It was formerly called DMRGateway. Analog_bridge
>     accepts a stream of analog audio, uses a Vocoder from NW Digital
>     to convert to AMBE and communicates it to a partner. That analog
>     audio can come from ASL or a application running on a desktop
>     computer. A deficiency in the method of signaling PTT assert /
>     de-assert has been fixed. The name Analog_bridge better describes
>     it's function. Some of you may have noticed Jonathan G4KLX just
>     announced his gateway DMRGateway. Thank goodness there will not be
>     any confusion in the names.
>
>      Any Partner can communicate with any other Partner to form a
>     bridge. Consider you want to bridge ASL to IPSC. (What ambe_audio
>     and DMRGateway used to do) ASL <---> Analog_bridge <--->
>     IPSC_bridge <---> IPSC Network. This works quite well with a
>     simple Motorola Master / Peer configuration or a c-Bridge. With
>     BrandMeister, there are limitations imposed. You need a BM
>     administrator to configure the BM side of the connection. Any
>     changes to TS or TG has to be coordinated with BM. Now consider
>     another way to accomplish the same ASL to BM connection. ASL <--->
>     Analog_bridge <---> HB_bridge <---> HBR Network.  The HB_bridge
>     connection is treated the same way a MMDVM is treated by BM. You
>     as the sysop define what TS/TG is used. You can build it your way.
>
>      I have spoken with Cort, The methods used to allow Partners to
>     communicate will be expanded to include communications with other
>     protocols and services. Cort is busy working on support for remote
>     logging and display. Please be aware, this software is BETA. It's
>     early in the cycle. There will be bugs and features need to be
>     added. HBlink, DMRlink and other yet to be announced programs and
>     tools. (D-Star_bridge?) Please understand we can not support every
>     possible protocol, there are only so many hours in the day and
>     some protocols would have to be reverse engineered. Oh, and some
>     of even have lives. These are tools that allow you to enhance the
>     systems you operate. They are NOT networks. Build it your way.
>     After all, this is HAM radio.
>
>      Analog_bridge, HB_bridge and IPSC_bridge will be posted to the
>     repositories in a couple of days. I have uploaded some simple
>     block diagrams to <http://dvswitch.org/files/DVSwitch/
>     <http://dvswitch.org/files/DVSwitch/>> I know some of this
>     information is outside of the ASL Digital area. We will form a new
>     more general list to discuss digital bridging in general. (YAML,
>     Yet another mail list)
>
>     -- 
>     "What are HB_bridge, IPSC_bridge and Analog_bridge?"
>
>     _______________________________________________
>     Allstar-Digital mailing list
>     Allstar-Digital at lists.keekles.org
>     <mailto:Allstar-Digital at lists.keekles.org>
>     http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>     <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
>
>
>
>
> _______________________________________________
> Allstar-Digital mailing list
> Allstar-Digital at lists.keekles.org
> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/allstar-digital/attachments/20170526/8a9936bc/attachment.html>

More information about the Allstar-Digital mailing list