DMRlink, HBlink AllStarLink etc.
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/> 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?"
Great work Steve and Mike, I'll be looking to get hblink and Analog_bridge up and running. I'll try my best to get it working without asking too many questions. 73 Peter On 23/05/2017 17:01, Steve Zingman 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/> 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)
Le 23/05/2017 à 18:01, Steve Zingman a écrit :
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/> 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)
Hi, Thank you for the great job. We did not deploy DMR here yet. We're still playing around with D-Star and Asterisk. As far as there's no open-source solution to connect D-Star and Asterisk, I planned to write a gateway, which would connect to an XLX reflector. But my free time is very limited for now. Seeing your post, and even if I don't know anything about HBR and IPSC networks :-), it comes obvious to me that instead of writing a monolithic D-Star to Asterisk gateway, a better idea would be to write a D-Star to "DV-Switch" gateway. Please, could you tell more about the "DV_Switch" block on your diagrams ? What kind of software is it ? Is there a dedicated API ? Do you think writing a "DStar_Bridge" would be feasible ? As far as Python is my favourite programming language, I could have a look at Cort's code, and maybe I could use it as a template for making a D-Star bridge ? I'm looking forward to seeing all the code :-) 73 de TK1BI
Hi, Yes, The plan is to write a D-Star_bridge. The D-Star_bridge would work just like the other Partners. It would communicate with D-Star via ircDDBgateway and communicate with a partner. For what you want to do, it would work something like this: ircDDBGateway <---> D-Star_bridge <---> Analog_bridge <---> AllStar. At this time DVSwitch is in the planning stages. The detail are yet to be worked out. 73, Steve N4IRS On 5/24/2017 5:16 AM, Toussaint OTTAVI wrote:
Le 23/05/2017 à 18:01, Steve Zingman a écrit :
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/> 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)
Hi,
Thank you for the great job.
We did not deploy DMR here yet. We're still playing around with D-Star and Asterisk. As far as there's no open-source solution to connect D-Star and Asterisk, I planned to write a gateway, which would connect to an XLX reflector. But my free time is very limited for now.
Seeing your post, and even if I don't know anything about HBR and IPSC networks :-), it comes obvious to me that instead of writing a monolithic D-Star to Asterisk gateway, a better idea would be to write a D-Star to "DV-Switch" gateway.
Please, could you tell more about the "DV_Switch" block on your diagrams ? What kind of software is it ? Is there a dedicated API ? Do you think writing a "DStar_Bridge" would be feasible ? As far as Python is my favourite programming language, I could have a look at Cort's code, and maybe I could use it as a template for making a D-Star bridge ?
I'm looking forward to seeing all the code :-)
73 de TK1BI
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Le 24/05/2017 à 14:20, Steve Zingman a écrit :
Yes, The plan is to write a D-Star_bridge. The D-Star_bridge would work just like the other Partners. It would communicate with D-Star via ircDDBgateway and communicate with a partner. For what you want to do, it would work something like this: ircDDBGateway <---> D-Star_bridge <---> Analog_bridge <---> AllStar. At this time DVSwitch is in the planning stages. The detail are yet to be worked out.
Thank you. I'll wait for the details and source to be published. I have no skills (and no fun) in C programming, but I think it's doable in Python, and I'll be happy to contribute. Moreover, in order to avoid duplicate work by different people, did you have a look at XLX reflector ? It's intented to be a multiprotocol reflector, originally for D-Star, but DMR is being implemented, and Fusion may follow. On a block diagram, it may occupy the same place as your DVSwitch : a central dispatcher for various digital flows from different protocols. In my premiminary design, I thought about doing that : Asterisk [chan_USRP] <--> [USRP_Client] My Gateway [DExtra client] <--> [DExtra protocol driver] XLX reflector Then, I just need to code an USRP client, a D-Extra client, an AMBE client, and route flows between them. But I didn't try anything yet (too busy for the next few weeks...)
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@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/> 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@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
These guys seem to be of the opinion that sleep is overrated. And yes, I know exactly what you mean about barely keeping my head above water. *grin* Matthew N8OHU On May 26, 2017 4:25:28 PM EDT, Michael Hebert <mhebert1975@gmail.com> 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@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/> 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@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
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@msgstor.com <mailto:szingman@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@lists.keekles.org <mailto:Allstar-Digital@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@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Thank you! On Fri, May 26, 2017 at 4:15 PM, Steve Zingman <szingman@msgstor.com> wrote:
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@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/> 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@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
participants (5)
-
Matthew Pitts -
Michael Hebert -
Peter -
Steve Zingman -
Toussaint OTTAVI