Date   

Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Steve N4IRS
 

Dexter,
If you are referring to the ambed from XLX, it will not work. AB does not support that server. If you are using DMR you can use the internal vocoder in AB or the md380-emu.

Steve N4IRS

On 6/24/2019 12:54 PM, Dexter Harroo wrote:
Hi Guys, having this issue when starting A_B,
Error DV3000 not found aborting
, we have AMBED server running and the devices plugged into the same box that is running AMBE server and the reflector, is there something in the settings that I'm missing?


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Dexter Harroo
 

Hi Guys, having this issue when starting A_B,
Error DV3000 not found aborting
, we have AMBED server running and the devices plugged into the same box that is running AMBE server and the reflector, is there something in the settings that I'm missing?


Re: MMDVM_Bridge

Heiko DL1BZ
 

As I know from our DMRplus-sysops in Germany, they say you need to set in the options-line all 2 TS, TG not used need to be setup by zero. You have 5 TGs for slot1 and 5 TGs for slot2 and the option to setup a startup-reflektor.
My option line (from dmrgateway):
Options="StartRef=4039;RelinkTime=15;TS1_1=0;TS1_2=0;TS1_3=0;TS1_4=0;TS1_5=0;TS2_1=0;TS2_2=0;TS2_3=0;TS2_4=0;TS2_5=0;"

And I know too - the DMRplus team is not agree to bridge other network systems to the IPSC2-network, they thinking other than BM about such things. I had a lot of discussion about. That's what I know - they gave me clear information about this.

73 Heiko, DL1BZ


Re: OhioLink YSF to DMR bridge update

Steve N4IRS
 

You will need to replace the Analog_Bridge executable with one from here. <https://github.com/DVSwitch/Analog_Bridge/tree/master/bin>

On 6/23/19 12:54 PM, Tom Corcoran wrote:
and to change TG's do I enter *3TG in DVSM or just the TG#?
--
Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Steve N4IRS
 

Just the TG number

On 6/23/19 12:54 PM, Tom Corcoran wrote:
and to change TG's do I enter *3TG in DVSM or just the TG#?
--
Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Tom Corcoran
 

and to change TG's do I enter *3TG in DVSM or just the TG#?
--
Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Steve N4IRS
 

Correct.

On 6/23/19 11:48 AM, Tom Corcoran wrote:
So, just build cloud instance as before : ASL <-> DMR but skip setting up ASL node. Correct?
--
Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Tom Corcoran
 

So, just build cloud instance as before : ASL <-> DMR but skip setting up ASL node. Correct?
--
Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Steve N4IRS
 

Tom,
The quote below is from my description of using DVM connected directly to Analog_Bridge using the USRP protocol. the flow diagram would look like this:
DVSwitch Mobile <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR

The ability to switch modes and talkgroups can be done within ASL also using scripting. I am working on a writeup for ASL.

Steve N4IRS

On 6/22/19 3:52 PM, Tom Corcoran wrote:
Hello Steve,
 
I have been using the package as described in your update and it works perfectly. I am running DVM on an Inrico TM-7. 

DVSwitch Mobile <-> ASL <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR
Because I entered a DMR TG in Analog_Bridge, I assumed it was hardwired until I changed it. In your update, you say ...
 
"You can access any TG available on the network like you do on your DMR radio. You can choose any TG in the list and move over to the TG with a simple button press. You can dial any arbitrary TG from the keypad. The Callsign and DMRID are changeable in DVM." 
 
Does this mean I can use analog radio keypad to change TG's? If so, is it done by entering *3newTG? You refer to "any TG in the list" ... which list? All I see is a list of ASL nodes
 
Tnx for all your efforts and great support to the community. 
--
Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Tom Corcoran
 

Hello Steve,

another question related to DVM ... I wasn't aware that I could connect directly DVM <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR. Presumably no need for an ASL node in my cloud instance but not clear on what stanza(s) I change to enable DVM <-> Analog_Bridge connect. Advice?

-
Tnx ... Tom VE3NY


Re: OhioLink YSF to DMR bridge update

Tom Corcoran
 

Hello Steve,
 
I have been using the package as described in your update and it works perfectly. I am running DVM on an Inrico TM-7. 

DVSwitch Mobile <-> ASL <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR
Because I entered a DMR TG in Analog_Bridge, I assumed it was hardwired until I changed it. In your update, you say ...
 
"You can access any TG available on the network like you do on your DMR radio. You can choose any TG in the list and move over to the TG with a simple button press. You can dial any arbitrary TG from the keypad. The Callsign and DMRID are changeable in DVM." 
 
Does this mean I can use analog radio keypad to change TG's? If so, is it done by entering *3newTG? You refer to "any TG in the list" ... which list? All I see is a list of ASL nodes
 
Tnx for all your efforts and great support to the community. 
--
Tom VE3NY


HBlink rules.py

Carlos Minguela
 

Hi, a group of friends are unifying platforms which we have. So far we have managed to unify some of the platforms but others have not. With success we have managed to see that all HBlink accepts them as peers. But when mixing them some only receive audio but do not transmit. Attached I send you how we have configured the rules in case you can identify the possible error in them:

 
BRIDGES = {
    'BRIDGES': [
            {'SYSTEM': 'MASTER',     'TS': 2, 'TGID': 4004,    'ACTIVE': True, 'TIMEOUT': 10, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'XLX215-D',    'TS': 2, 'TGID': 4004,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],     'OFF': [],         'RESET': []},
            {'SYSTEM': 'XLX215-D',    'TS': 2, 'TGID': 9,       'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],     'OFF': [],         'RESET': []},
            {'SYSTEM': 'MASTER',    'TS': 2, 'TGID': 33015, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [], 'OFF': [], 'RESET': []},            
            {'SYSTEM': 'TG33015',    'TS': 2, 'TGID': 33015, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [], 'OFF': [], 'RESET': []},       
            {'SYSTEM': 'MASTER',     'TS': 2, 'TGID': 7225,    'ACTIVE': True, 'TIMEOUT': 10, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'ARG-TGIF',    'TS': 2, 'TGID': 7225,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],     'OFF': [],         'RESET': []},
            {'SYSTEM': 'TG7225',    'TS': 2, 'TGID': 7225,    'ACTIVE': True, 'TIMEOUT': 2,  'TO_TYPE': 'NONE', 'ON': [],     'OFF': [],         'RESET': []},           
        ]
}

These connections are fixed and we only want to use HBlink as a bridge of all the platforms. There are no connections to it from users since we only want to unify.  Thanks in advance for any help you can give us. 73 de KP4CA.


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Steve N4IRS
 

Yes

On 6/21/2019 3:20 PM, Dexter Harroo wrote:
DSTAR<------> <---ircDDBGateway---> <---MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR

So this is the correct illustration


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Steve N4IRS
 

Supported? Well not really, it's from someone else. I have not built a install package for it. It can be built from source or I think someone has packages available.

On 6/21/2019 3:15 PM, Dexter Harroo wrote:
ok Thanks Steve. I guess ircDDBGateway isn't supported on here?


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Dexter Harroo
 

DSTAR<------> <---ircDDBGateway---> <---MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR

So this is the correct illustration


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Dexter Harroo
 

ok Thanks Steve. I guess ircDDBGateway isn't supported on here?


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Steve KC1AWV
 

Depends on how you're starting the service. If you're using the systemd scripts, this is how I would do it:

Make a copy of the existing AB systemd script, make it identifiable as a different script

cd /lib/systemd/system
cp analog_bridge.service analog_bridge-dstar.service

Then, edit the copy with your editor of choice

pico analog_bridge-dstar.service

And edit the ExecStart line to load up the configuration for the instance you want. I'll assume you're doing the dstar config

ExecStart=/opt/Analog_Bridge/Analog_Bridge /opt/Analog_Bridge/Analog_Bridge_DStar.ini

Save and exit the editor. Then update the systemd files

systemctl daemon-reload

Then star the new service

systemctl start analog_bridge-dstar.service

You can do the same for the DMR instance as well, just change the names and files where needed.

Steve KC1AWV


On Fri, Jun 21, 2019 at 2:59 PM Dexter Harroo <dex.9y4c@...> wrote:

[Edited Message Follows]

Hi guys:
Its me again, This time i am assisting a friend of mines in setting up DStar to DMR link i did some reading and want to make sure i understand the instructions and doing it correctly.
this is what i have so far.
DSTAR<------>MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR

Analog_Bridge_Dstar.ini
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 32103                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 32100                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DSTAR                        ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3740029                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 3740029                    ; ID of source repeater
txTg = 1972                                ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 1                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

DvSwitch.ini Dstar Stanza

[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32103                  ; Port to send AMBE TLV frames to (export)
RXPort = 32100                  ; Port to listen on (import)
FallbackID = 3740029            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1972                 ; Which TG to export
Slot = 2                                ; Export slot

Analog_Bridge_DMR.ini
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31101                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; ID of source repeater
txTg = 1972                             ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           

DvSwitch.INI DMR Stanza
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31101                  ; Port to listen on (import)
Slot = 2                        ; Export slot


Can someone take a look and let me know if I'm on the right track or If I am Missing anything?
Question How do i go about running the 2 Instances of Analog_Bridge?



--
Steve Miller
KC1AWV


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Steve N4IRS
 

Looks about right. Don't forget you need ircDDBGateway between MB and D-Star reflector.

On 6/21/2019 2:57 PM, Dexter Harroo wrote:
Hi guys:
Its me again, This time i am assisting a friend of mines in setting up DStar to DMR link i did some reading and want to make sure i understand the instructions and doing it correctly.
this is what i have so far.
DSTAR<------>MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR

Analog_Bridge_Dstar.ini
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 32103                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 32100                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DSTAR                        ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3740029                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 3740029                    ; ID of source repeater
txTg = 1972                                ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 1                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

DvSwitch.ini Dstar Stanza

[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32103                  ; Port to send AMBE TLV frames to (export)
RXPort = 32100                  ; Port to listen on (import)
FallbackID = 3740029            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1972                 ; Which TG to export
Slot = 2                                ; Export slot

Analog_Bridge_DMR.ini
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31101                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; ID of source repeater
txTg = 1972                             ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           

DvSwitch.INI DMR Stanza
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31101                  ; Port to listen on (import)
Slot = 2                        ; Export slot


Can someone take a look and let me know if I'm on the right track or If I am Missing anything?


setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

Dexter Harroo
 
Edited

Hi guys:
Its me again, This time i am assisting a friend of mines in setting up DStar to DMR link i did some reading and want to make sure i understand the instructions and doing it correctly.
this is what i have so far.
DSTAR<------>MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR

Analog_Bridge_Dstar.ini
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 32103                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 32100                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DSTAR                        ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3740029                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 3740029                    ; ID of source repeater
txTg = 1972                                ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 1                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

DvSwitch.ini Dstar Stanza

[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32103                  ; Port to send AMBE TLV frames to (export)
RXPort = 32100                  ; Port to listen on (import)
FallbackID = 3740029            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1972                 ; Which TG to export
Slot = 2                                ; Export slot

Analog_Bridge_DMR.ini
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31101                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; ID of source repeater
txTg = 1972                             ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           

DvSwitch.INI DMR Stanza
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31101                  ; Port to listen on (import)
Slot = 2                        ; Export slot


Can someone take a look and let me know if I'm on the right track or If I am Missing anything?
Question How do i go about running the 2 Instances of Analog_Bridge?


Re: OhioLink YSF to DMR bridge update

Steve N4IRS
 

Gary,
Thanks for the update. Working with the Ohio Link team was a pleasure. The back and forth helped us learn a few things and find a bug or two. I expect the changes will be incorporated in future versions. Please keep us informed about the blocking message.

Your comment about bringing up a AllStarLink (ASL) node to experiment with DVSwitch Mobile (DVM) brings up a point I would like to address. DVM can be used in two ways. One, as a client for ASL using the native ASL protocol, IAX. In this configuration ASL can be simply that, an analog node capable of connection to other analog nodes. The flow diagram would look like this:
DVM <-> ASL <-> ASL Network.

With this configuration from DVM you can connect your ASL node to any other ASL (or EchoLink) nodes. Very clean and simple. ASL will support multiple logins from DVM so users can easily share the node. If you want to ALSO be able to connect to one or more of the digital voice networks, you can add that to ASL. Your flow diagram will look like this:
DVM <-> ASL <-> Analog_Bridge <-> MMDVM_Bridge <-> digital voice network

You now have access to both the analog and digital voice networks. You can also have multiple logins and share access. This configuration can (with some expansion) can give users access to analog and digital at the same time. For example, one (or more) user on analog and one user on digital. ASL provides quite a lot of functionality if you want. Please note, the one thing you do not have in this configuration is MetaData. DVM will not show you who is talking and all DVM users will share one DMR ID.

DVM does not REQUIRE you to build a ASL node for access. DVM also supports a direct connection to Analog_Bridge (AB) In this configuration a single user can directly access all of the supported digital modes. Your flow diagram will look like this:
DVM <-> Analog_Bridge <-> MMDVM_Bridge <-> digital voice network.

We refer to this as "hot spot in the cloud" Though the hotspot does not really be in the cloud, it can be running on a RPi in your shack. DVM becomes the user interface for AB. In this configuration DVM will display MetaData from the DV network and when you transmit from DVM, your DMR ID and callsign will be correct. In subsequent messages and in the wiki I will cover this configuration in more detail.

Last but not least, I love the "the Swiss army knife of digital radio" Mike and I have been running the DVSwitch programs on the RPi (and other types) Some for testing and some for day to day use. A while ago we started referring to these Pis as Swiss army knives" since they had all the software we needed in one place to build whatever we needed. 

73, Steve N4IRS
      

On 6/20/2019 8:39 PM, Gary - KE8O wrote:
Just wanted to give you an update on Ohio Link. Prior to Dayton the DVSwitch team setup a demo bridge as our previous YSF to DMR solution was having some issues.  I've been running our own DVSwitch instance now locally for a week now bridging our YSF to DMR. I started out only bridging when I was around to monitor and started bridging 24/7 since last Sunday. We only had one occurrence of the BM blocked user message in that time and that was on the first day when I was running the old MB binary with the VW issue causing one way audio with WiresX.  After installing the updated binary from github its been flawless. I know that binary had nothing in to fix the minimum TX duration so whatever was causing the original issue with the BM block message is still lurking. I've now moved on to setting up an Allstar server and node to experiment with DVMobile. My server and node number are now registered so its time to install and configure the software. I'm giving a presentation in the middle of July to our local club on digital radio. I'm hoping to be able to pass around an Inrico T320 as one of the digital radio demos.
 
Thank you guys for such a great product. It's the Swiss army knife of digital radio!

73,
...Gary, KE8O

5301 - 5320 of 9518