Topics

D-Star

K4VL
 

OK I finally got my DMR Bridge working (I think) Now I would like to set up another ASL node with a D-Star bridge. Is the a how-to document like the ASL to DMR Bridge?

Skyler Fennell
 

I have not been able to find a how-to and it took me a while to get it to work. You will need another component that is not currently installed: IRCDDBGATEWAY. Below is the setup overview:

XRF <-> ircDDBGateway <-> MMDVM_Bridge <-> Analog_Bridge <-> USRP target

This thread helped me debug some issues:

ircDDBGateway was the biggest pain in the neck to get working. I was using command line only, no GUI and ,there is no conf file to begin with. So you will need to get a copy of this conf file and edit for your needs:

You will need to grab ircDDBGateway from here:







On Thu, Feb 7, 2019 at 2:06 PM K4VL <73dek4vl@...> wrote:
OK I finally got my DMR Bridge working (I think) Now I would like to set up another ASL node with a D-Star bridge. Is the a how-to document like the ASL to DMR Bridge?

Santu OTTAVI (TK1BI)
 

Hi,

Le 08/02/2019 à 05:25, Skyler Fennell a écrit :
ircDDBGateway was the biggest pain in the neck to get working. I was using command line only, no GUI and ,there is no conf file to begin with. So you will need to get a copy of this conf file and edit for your needs:

Thank you for your message. Hope to hear it works. I tested with ircddbgateway a few weeks ago, but I didn't manage to get audio from Asterisk to XLX.

It seems XLX was not understanding/processing the DCS connect packet from ircddbgateway :

XLX log was showing something like that :
      Jan 16 20:48:52 xlx xlxd: DCS packet (100) from 10.44.0.3

while a successful DCS incoming connection would display something like that :
      Jan 16 20:40:20 xlx xlxd: Opening stream on module K for client TK1BI   B with sid 41964 
     
The problem of DMR-ID resolution was solved, and MMDVM_Bridge was sending things that seemed to be correct :
      D: 2019-01-16 19:48:52.651 0000:  44 53 52 50 20 9C 67 00 40 00 00 54 4B 35 4B 50    *DSRP .g.@..TK5KP*
      D: 2019-01-16 19:48:52.651 0010:  20 20 47 54 4B 35 4B 50 20 20 47 43 51 43 51 43    *  GTK5KP  GCQCQC*
      D: 2019-01-16 19:48:52.651 0020:  51 20 20 54 4B 35 4B 50 20 20 20 44 56 53 57 75    *Q  TK5KP   DVSWu*
      D: 2019-01-16 19:48:52.651 0030:  07    

About ircddbgateway, I didn't manage to get  any debug traces. So I never understood what was going wrong...

Please, could you post your Analog_bridge.ini, MMDVM_Bridge.ini, dvswitch.ini, ircddbgateway.ini ?

73 de TK1BI

Skyler Fennell
 

Yes, The DMR ID resolving is in Analog_bridge. You need to point to the dmr lookup file. 

“”
So,
We found the issue.  Here is the clue. This is MMDVM_Bridge trying to TX to a D-Star reflector:

I: 2018-12-28 04:56:12.435 D-Star, Begin TX: src=3108034 rpt=301815 dst=9 slot=2 cc=1 metadata=3108034

Notice the Metadata: metadata=3108034
That is the call sign received from Analog_Bridge. 
That is what is being passed to ircDDBGateway as a callsign. This is BAD.

The problem was that Analog_Bridge could not resolve the DMRID. In this case because the Analog_Bridge.ini was pointing to a invalid dmrid file.
Once that was fixed the TX line looks like this:
I: 2018-12-28 04:56:12.435 D-Star, Begin TX: src=3108034 rpt=301815 dst=9 slot=2 cc=1 metadata=K0JSC

Now we have audio.

Jeff, FYI
I copied the ID file from /var/lib/dvswitch to /opt/Analog_Bridge because it was quick. You should fix Analog_Bridge to point to the data file in /var/lib/dvswitch.

Note, All of the above does point out that Mike and I need to look at the logic of resolving and passing Metadata. One more thing for the list.

73, Steve N4IRS
“””


On Fri, Feb 8, 2019 at 3:27 AM Santu OTTAVI (TK1BI) <t.ottavi@...> wrote:
Hi,

Le 08/02/2019 à 05:25, Skyler Fennell a écrit :
ircDDBGateway was the biggest pain in the neck to get working. I was using command line only, no GUI and ,there is no conf file to begin with. So you will need to get a copy of this conf file and edit for your needs:

Thank you for your message. Hope to hear it works. I tested with ircddbgateway a few weeks ago, but I didn't manage to get audio from Asterisk to XLX.

It seems XLX was not understanding/processing the DCS connect packet from ircddbgateway :

XLX log was showing something like that :
      Jan 16 20:48:52 xlx xlxd: DCS packet (100) from 10.44.0.3

while a successful DCS incoming connection would display something like that :
      Jan 16 20:40:20 xlx xlxd: Opening stream on module K for client TK1BI   B with sid 41964 
     
The problem of DMR-ID resolution was solved, and MMDVM_Bridge was sending things that seemed to be correct :
      D: 2019-01-16 19:48:52.651 0000:  44 53 52 50 20 9C 67 00 40 00 00 54 4B 35 4B 50    *DSRP .g.@..TK5KP*
      D: 2019-01-16 19:48:52.651 0010:  20 20 47 54 4B 35 4B 50 20 20 47 43 51 43 51 43    *  GTK5KP  GCQCQC*
      D: 2019-01-16 19:48:52.651 0020:  51 20 20 54 4B 35 4B 50 20 20 20 44 56 53 57 75    *Q  TK5KP   DVSWu*
      D: 2019-01-16 19:48:52.651 0030:  07    

About ircddbgateway, I didn't manage to get  any debug traces. So I never understood what was going wrong...

Please, could you post your Analog_bridge.ini, MMDVM_Bridge.ini, dvswitch.ini, ircddbgateway.ini ?

73 de TK1BI

Skyler Fennell
 

Sorry I didnt read your whole email and my reply may have been poinless. I’ll give you all my conf files when I’m @ computer

On Fri, Feb 8, 2019 at 6:04 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Yes, The DMR ID resolving is in Analog_bridge. You need to point to the dmr lookup file. 

“”
So,
We found the issue.  Here is the clue. This is MMDVM_Bridge trying to TX to a D-Star reflector:

I: 2018-12-28 04:56:12.435 D-Star, Begin TX: src=3108034 rpt=301815 dst=9 slot=2 cc=1 metadata=3108034

Notice the Metadata: metadata=3108034
That is the call sign received from Analog_Bridge. 
That is what is being passed to ircDDBGateway as a callsign. This is BAD.

The problem was that Analog_Bridge could not resolve the DMRID. In this case because the Analog_Bridge.ini was pointing to a invalid dmrid file.
Once that was fixed the TX line looks like this:
I: 2018-12-28 04:56:12.435 D-Star, Begin TX: src=3108034 rpt=301815 dst=9 slot=2 cc=1 metadata=K0JSC

Now we have audio.

Jeff, FYI
I copied the ID file from /var/lib/dvswitch to /opt/Analog_Bridge because it was quick. You should fix Analog_Bridge to point to the data file in /var/lib/dvswitch.

Note, All of the above does point out that Mike and I need to look at the logic of resolving and passing Metadata. One more thing for the list.

73, Steve N4IRS
“””


On Fri, Feb 8, 2019 at 3:27 AM Santu OTTAVI (TK1BI) <t.ottavi@...> wrote:
Hi,

Le 08/02/2019 à 05:25, Skyler Fennell a écrit :
ircDDBGateway was the biggest pain in the neck to get working. I was using command line only, no GUI and ,there is no conf file to begin with. So you will need to get a copy of this conf file and edit for your needs:

Thank you for your message. Hope to hear it works. I tested with ircddbgateway a few weeks ago, but I didn't manage to get audio from Asterisk to XLX.

It seems XLX was not understanding/processing the DCS connect packet from ircddbgateway :

XLX log was showing something like that :
      Jan 16 20:48:52 xlx xlxd: DCS packet (100) from 10.44.0.3

while a successful DCS incoming connection would display something like that :
      Jan 16 20:40:20 xlx xlxd: Opening stream on module K for client TK1BI   B with sid 41964 
     
The problem of DMR-ID resolution was solved, and MMDVM_Bridge was sending things that seemed to be correct :
      D: 2019-01-16 19:48:52.651 0000:  44 53 52 50 20 9C 67 00 40 00 00 54 4B 35 4B 50    *DSRP .g.@..TK5KP*
      D: 2019-01-16 19:48:52.651 0010:  20 20 47 54 4B 35 4B 50 20 20 47 43 51 43 51 43    *  GTK5KP  GCQCQC*
      D: 2019-01-16 19:48:52.651 0020:  51 20 20 54 4B 35 4B 50 20 20 20 44 56 53 57 75    *Q  TK5KP   DVSWu*
      D: 2019-01-16 19:48:52.651 0030:  07    

About ircddbgateway, I didn't manage to get  any debug traces. So I never understood what was going wrong...

Please, could you post your Analog_bridge.ini, MMDVM_Bridge.ini, dvswitch.ini, ircddbgateway.ini ?

73 de TK1BI

Charles Wiant
 

Hello I am in the same boat got bridge running with dmr no problem looking for documentation for setting up DSTAR. Thank You Charles any help would be appreciated .

Steve N4IRS
 

D-Star is not that different from DMR in setup. Change from DMR to D-Star in AB.ini and point at the D-Star ports in DV.ini. Add ircddbgateway. Enable D-Star in MB.ini Stir and let simmer for 30 minutes.

I am working on a complete set of sample files for use with DVSwitch Mobile that may help.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Charles Wiant via Groups.Io <kd8itc@...>
Sent: Friday, February 8, 2019 9:58:31 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] D-Star
 

Hello I am in the same boat got bridge running with dmr no problem looking for documentation for setting up DSTAR. Thank You Charles any help would be appreciated .

K4VL
 

Thanks enjoy the ham fest 


On Sat, Feb 9, 2019, 6:14 AM Steve N4IRS <szingman@... wrote:
D-Star is not that different from DMR in setup. Change from DMR to D-Star in AB.ini and point at the D-Star ports in DV.ini. Add ircddbgateway. Enable D-Star in MB.ini Stir and let simmer for 30 minutes.

I am working on a complete set of sample files for use with DVSwitch Mobile that may help.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Charles Wiant via Groups.Io <kd8itc=aol.com@groups.io>
Sent: Friday, February 8, 2019 9:58:31 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] D-Star
 

Hello I am in the same boat got bridge running with dmr no problem looking for documentation for setting up DSTAR. Thank You Charles any help would be appreciated .

Santu OTTAVI (TK1BI)
 

Le 09/02/2019 à 13:14, Steve N4IRS a écrit :
D-Star is not that different from DMR in setup.
Yes, but as far as there are several software involved, there are a lot of tiny things that can make things going wrong :-)

When I tested with ircddbgateway, XLX did not process the DCS connection request packet ! Investigating is still on the todo list :-)

Steve N4IRS
 

No matter what you bridge there are several pieces of software involved. The methodology is still the same.

On 2/11/19 5:22 AM, Santu OTTAVI (TK1BI) wrote:

Le 09/02/2019 à 13:14, Steve N4IRS a écrit :
D-Star is not that different from DMR in setup.
Yes, but as far as there are several software involved, there are a lot of tiny things that can make things going wrong :-)

When I tested with ircddbgateway, XLX did not process the DCS connection request packet ! Investigating is still on the todo list :-)