Date   

Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Steve N4IRS
 

Easiest way is to setup a static TG in BM selfcare.

On 5/14/20 9:31 PM, Rudy wrote:

Thanks Steve!

Wow! Here I thought I needed another protocol to run to get these two instances of MMDVM_Bridge to talk to one another.


Q.
Next question would be, where do I put the information on what TG to direct the data to?



MB_BM MMDVM_Bridge.ini (REVISED)

[General]
Callsign=N6DOZ
Id=315069220 <-- with two digit ssid
Timeout=180
Duplex=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62042
Password=passw0rd
Slot1=1
Slot2=1
Debug=0


MB_BM DVSwitch.ini
[DMR]
Address = 127.0.0.1             
TXPort = 32100    <-- cross connected             
RXPort = 32103    <-- cross connected              
Slot = 2                      
 

--


MB_XLX MMDVM_Bridge.ini
 
[General]
Callsign=N6DOZ
Id=3150692
Timeout=180
Duplex=0

[System Fusion]
Enable=1
 
[DMR Network]
Enable=1
Address=45.77.186.5
Port=62031
Jitter=360
Local=62052
Password=passw0rd
Options=XLX:4001
Slot1=1
Slot2=1
Debug=1

MB_XLX DVSwitch.ini

[DMR]
Address=127.0.0.1  
TXPort = 33103    <-- cross connected                   
RXPort = 33101    <-- cross connected                  
Slot = 2                       


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Rudy N6DOZ
 
Edited

Thanks Steve!

Wow! Here I thought I needed another protocol to run to get these two instances of MMDVM_Bridge to talk to one another.


Q.
Next question would be, where do I put the information on what TG to direct the data to?



MB_BM MMDVM_Bridge.ini (REVISED)

[General]
Callsign=N6DOZ
Id=315069220 <-- with two digit ssid
Timeout=180
Duplex=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62042
Password=passw0rd
Slot1=1
Slot2=1
Debug=0


MB_BM DVSwitch.ini
[DMR]
Address = 127.0.0.1             
TXPort = 32100    <-- cross connected             
RXPort = 32103    <-- cross connected              
Slot = 2                      
 

--


MB_XLX MMDVM_Bridge.ini
 
[General]
Callsign=N6DOZ
Id=3150692
Timeout=180
Duplex=0
 
[DMR Network]
Enable=1
Address=45.77.186.5
Port=62030
Jitter=360
Local=62052
Password=passw0rd
Options=XLX:4001
Slot1=1
Slot2=1
Debug=1

MB_XLX DVSwitch.ini

[DMR]
Address=127.0.0.1  
TXPort = 33103    <-- cross connected                   
RXPort = 33100    <-- cross connected                  
Slot = 2                       


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Steve N4IRS
 

The cross connect is done in DVSwitch.ini

MB_BM DVSwitch.ini
[DMR]
Address = 127.0.0.1             
TXPort = 32100                 
RXPort = 32103                
Slot = 2                     

MB_XLX DVSwitch.ini

[DMR]
Address=127.0.0.1  
TXPort = 32103                 
RXPort = 32100                
Slot = 2                      

TX to RX
RX to TX

Steve N4IRS

On 5/14/20 9:19 PM, Rudy wrote:
Now based on everything I read so far doing a search on bridging XLX to BM DMR via MMDVM_Bridge (no longer needing DMRGateway), the structure is as follow:

BM TG <-> MB_BM <-> MB_XLX <-> XLX Reflector

Now, I have created to instances of MMDVM_Bridges with utilizing unique ports to each other. I am able to connect the respective instances to DMR and the XLX reflector but for the life of me, I can not figure out how the two MMDVM_Bridges are to be connected.

BM TG <-> MB_BM < ??? > MB_XLX <-> XLX Reflector

MB_BM MMDVM_Bridge.ini
[General]
Callsign=N6DOZ
Id=315069220 <-- with two digit ssid
Timeout=180
Duplex=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62042
Password=passw0rd
Slot1=1
Slot2=1
Debug=0


MB_BM DVSwitch.ini
[DMR]
Address = 127.0.0.1             
TXPort = 32100                 
RXPort = 32103                
Slot = 2                      
 

Q. What protocol am I to use to connect this MB_BM to the other instance?


MB_XLX MMDVM_Bridge.ini
 
[General]
Callsign=N6DOZ
Id=3150692
Timeout=180
Duplex=0

[System Fusion]
Enable=1
 
[DMR Network]
Enable=1
Address=45.77.186.5
Port=62031
Jitter=360
Local=62052
Password=passw0rd
Options=XLX:4001
Slot1=1
Slot2=1
Debug=1

MB_XLX DVSwitch.ini

[DMR]
Address=127.0.0.1  
TXPort = 33100                  
RXPort = 33103                 
Slot = 2                       


Q. Same question here, what protocol am I to use to connect this MB_XLX to the other instance?



Thanks in advance! 7-3 N6DOZ.


Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Rudy N6DOZ
 
Edited

Now based on everything I read so far doing a search on bridging XLX to BM DMR via MMDVM_Bridge (no longer needing DMRGateway), the structure is as follow:

BM TG <-> MB_BM <-> MB_XLX <-> XLX Reflector

Now, I have created to instances of MMDVM_Bridges with utilizing unique ports to each other. I am able to connect the respective instances to DMR and the XLX reflector but for the life of me, I can not figure out how the two MMDVM_Bridges are to be connected.

BM TG <-> MB_BM < ??? > MB_XLX <-> XLX Reflector

MB_BM MMDVM_Bridge.ini
[General]
Callsign=N6DOZ
Id=315069220 <-- with two digit ssid
Timeout=180
Duplex=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62042
Password=passw0rd
Slot1=1
Slot2=1
Debug=0


MB_BM DVSwitch.ini
[DMR]
Address = 127.0.0.1             
TXPort = 32100                 
RXPort = 32103                
Slot = 2                      
 

Q. What protocol am I to use to connect this MB_BM to the other instance?


MB_XLX MMDVM_Bridge.ini
 
[General]
Callsign=N6DOZ
Id=3150692
Timeout=180
Duplex=0

[System Fusion]
Enable=1
 
[DMR Network]
Enable=1
Address=45.77.186.5
Port=62031
Jitter=360
Local=62052
Password=passw0rd
Options=XLX:4001
Slot1=1
Slot2=1
Debug=1

MB_XLX DVSwitch.ini

[DMR]
Address=127.0.0.1  
TXPort = 33100                  
RXPort = 33103                 
Slot = 2                       


Q. Same question here, what protocol am I to use to connect this MB_XLX to the other instance?



Thanks in advance! 7-3 N6DOZ.
 
TL;DR
I ended up doing what Ernie Gm7kbk suggested, which is basically running the MB_BM through DMRGateway to change TG9 to my target TG. Works great!
 
BM <-> DMRGateway <-> MB_BM <-> MB_XLX <-> XLX
 


Re: Is there a simple way for Bridging a Brandmeister TG to an XLX Reflector (new 2020 Version)

Rudy N6DOZ
 

Patrick,

Did you ever get this configuration working? If so, would you mind sharing your configurations MMDVM_Bridge.ini and DVSwitch.ini for both instances?

7-3, Rudy


Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.

EA5GVK Joaquin
 

On Thu, May 14, 2020 at 12:18 PM, Jeff Lehman, N8ACL wrote:
OK. Good Luck. I can’t help more than that. I was just curious.
Thank you, Jeff. Take it easy.
We have Steve who is helping us a lot, so the Dvswitch application is phenomenal.
Greetings.


Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.

Jeff Lehman, N8ACL
 

OK. Good Luck. I can’t help more than that. I was just curious.

Jeff Lehman, N8ACL
E-mail: N8ACL@...
Hamshack Hotline: 4218
Website: https://n8acl.ddns.net



On May 14, 2020, at 2:45 PM, EA5GVK Joaquin <ea5gvk@...> wrote:

Hi, Jeff. Not just a single dvswitch user. One Analog_Bridge , MMDVM_Bridge, md380-emu, on a raspberry pi with debian 10 buster.

El jue., 14 may. 2020 a las 20:42, Jeff Lehman, N8ACL via groups.io (<n8acl=icloud.com@groups.io>) escribió:
Joaquin,
Just out of curiosity, does EA5GVK possibly hav a couple of hotspots on the same frequency that have that Talkgroup set on them? There has been some problems with people having multiple hotspots and they tend to loop back on themselves on a talk group. So I was just curious. :)

Jeff

Jeff Lehman, N8ACL
E-mail: N8ACL@...
Hamshack Hotline: 4218
Website: https://n8acl.ddns.net



On May 14, 2020, at 2:37 PM, EA5GVK Joaquin <ea5gvk@...> wrote:

Good afternoon, Steve.
I report again the same problem of LOOP of my friend EA1HWR, I have attached the logs of the new Analog_Bridge and MMDVM_Bridge, armhf, as well as the log provided by BM Spain. For you to see also the server the problem that generates the loop. 
Steve can be seen at 19:23 in the BM log which coincides with 17:23 utc in the analog_bridge and MMDVM_Bridge log.
Any more information will be reported to you. <Analog_Bridge.log><Log BM EA1HWR LOOP.txt><MMDVM_Bridge-10-2020-05-14.log>





Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.

EA5GVK Joaquin
 

Hi, Jeff. Not just a single dvswitch user. One Analog_Bridge , MMDVM_Bridge, md380-emu, on a raspberry pi with debian 10 buster.


El jue., 14 may. 2020 a las 20:42, Jeff Lehman, N8ACL via groups.io (<n8acl=icloud.com@groups.io>) escribió:
Joaquin,
Just out of curiosity, does EA5GVK possibly hav a couple of hotspots on the same frequency that have that Talkgroup set on them? There has been some problems with people having multiple hotspots and they tend to loop back on themselves on a talk group. So I was just curious. :)

Jeff

Jeff Lehman, N8ACL
E-mail: N8ACL@...
Hamshack Hotline: 4218
Website: https://n8acl.ddns.net



On May 14, 2020, at 2:37 PM, EA5GVK Joaquin <ea5gvk@...> wrote:

Good afternoon, Steve.
I report again the same problem of LOOP of my friend EA1HWR, I have attached the logs of the new Analog_Bridge and MMDVM_Bridge, armhf, as well as the log provided by BM Spain. For you to see also the server the problem that generates the loop.
Steve can be seen at 19:23 in the BM log which coincides with 17:23 utc in the analog_bridge and MMDVM_Bridge log.
Any more information will be reported to you. <Analog_Bridge.log><Log BM EA1HWR LOOP.txt><MMDVM_Bridge-10-2020-05-14.log>


Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.

Jeff Lehman, N8ACL
 

Joaquin,
Just out of curiosity, does EA5GVK possibly hav a couple of hotspots on the same frequency that have that Talkgroup set on them? There has been some problems with people having multiple hotspots and they tend to loop back on themselves on a talk group. So I was just curious. :)

Jeff

Jeff Lehman, N8ACL
E-mail: N8ACL@...
Hamshack Hotline: 4218
Website: https://n8acl.ddns.net



On May 14, 2020, at 2:37 PM, EA5GVK Joaquin <ea5gvk@...> wrote:

Good afternoon, Steve.
I report again the same problem of LOOP of my friend EA1HWR, I have attached the logs of the new Analog_Bridge and MMDVM_Bridge, armhf, as well as the log provided by BM Spain. For you to see also the server the problem that generates the loop.
Steve can be seen at 19:23 in the BM log which coincides with 17:23 utc in the analog_bridge and MMDVM_Bridge log.
Any more information will be reported to you. <Analog_Bridge.log><Log BM EA1HWR LOOP.txt><MMDVM_Bridge-10-2020-05-14.log>


Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.

EA5GVK Joaquin
 

Good afternoon, Steve.
I report again the same problem of LOOP of my friend EA1HWR, I have attached the logs of the new Analog_Bridge and MMDVM_Bridge, armhf, as well as the log provided by BM Spain. For you to see also the server the problem that generates the loop.
Steve can be seen at 19:23 in the BM log which coincides with 17:23 utc in the analog_bridge and MMDVM_Bridge log.
Any more information will be reported to you.


DvSwitch MObile

honda5603@...
 

Does anyone know if a bluetooth PTT and speaker will work with DVSwitch Mobile?

https://www.amazon.com/Bluetooth-Microphone-Button-speaker-Android/dp/B01NBB7DU0?pf_rd_r=1J5WDE24V1891MDMKHV2&pf_rd_p=4ef03d4f-fc52-4cba-b905-5ea280a737fe&pd_rd_r=2035ea1c-9f3b-4a7b-bc8b-b817267b7f0a&pd_rd_w=zTkw6&pd_rd_wg=9lxrZ&ref_=pd_gw_ci_mcx_mr_hp_d


New to the group

lelahrobinson76@...
 

Hey everyone, new to the group. 
Very excited for this group's content.
Any tips or advice as a new member of the group?


Re: YSFReflector to Allstarlink

honda5603@...
 

That got it!  Thanks Ernie and Steve for all your help!  I really do appreciate the fast turnarounds too.

73,

KC9HTA


Re: YSFReflector to Allstarlink

 

The Error
E: 2020-05-13 18:16:03.129 Error returned from sendto, err: 22

I: 2020-05-13 17:03:55.771 System Fusion Network Parameters
I: 2020-05-13 17:03:55.771     Local Address: 127.0.0.1  >>>>>>>> Change to Ip address of machine
I: 2020-05-13 17:03:55.771     Local Port: 3200
I: 2020-05-13 17:03:55.771     Gateway Address: 192.168.1.72 
I: 2020-05-13 17:03:55.771     Gateway Port: 42000
I: 2020-05-13 17:03:55.771     Mode Hang: 3s



Re: YSFReflector to Allstarlink

honda5603@...
 

Okay I'm running Debian 10 that might be an issue.  Had to install net tools to get netstat


Re: YSFReflector to Allstarlink

Steve N4IRS
 

If you can copy and paste the output of cat, you can copy and paste the output of the commands.

On 5/13/20 2:12 PM, honda5603@... wrote:
That's what I've been doing, copy and past the entire log after cat it


Re: YSFReflector to Allstarlink

honda5603@...
 

I did find an issue with ports: 

I don't think the YSF side of things is working properly:

E: 2020-05-13 18:16:02.945 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.006 Error returned from sendto, err: 22
I: 2020-05-13 18:16:03.006 YSF, Narrow transmit (72 bit)
E: 2020-05-13 18:16:03.129 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.185 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.303 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.425 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.486 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.609 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.727 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.783 Error returned from sendto, err: 22
E: 2020-05-13 18:16:03.905 Error returned from sendto, err: 22
E: 2020-05-13 18:16:04.023 Error returned from sendto, err: 22
E: 2020-05-13 18:16:04.085 Error returned from sendto, err: 22
E: 2020-05-13 18:16:04.207 Error returned from sendto, err: 22
M: 2020-05-13 18:16:04.223 YSF, TX state = OFF
E: 2020-05-13 18:16:04.223 Error returned from sendto, err: 22
E: 2020-05-13 18:16:06.483 Error returned from sendto, err: 22
E: 2020-05-13 18:16:11.486 Error returned from sendto, err: 22
E: 2020-05-13 18:16:16.492 Error returned from sendto, err: 22
E: 2020-05-13 18:16:21.497 Error returned from sendto, err: 22
E: 2020-05-13 18:16:26.500 Error returned from sendto, err: 22
E: 2020-05-13 18:16:31.504 Error returned from sendto, err: 22
E: 2020-05-13 18:16:36.509 Error returned from sendto, err: 22
E: 2020-05-13 18:16:41.513 Error returned from sendto, err: 22
E: 2020-05-13 18:16:46.515 Error returned from sendto, err: 22
M: 2020-05-13 18:16:50.605 YSF, TX state = ON
I: 2020-05-13 18:16:50.605 YSF, Begin TX: src=3118583 rpt=311858301 dst=37921 slot=2 cc=1 metadata=KC9HTA
E: 2020-05-13 18:16:50.646 Error returned from sendto, err: 22
E: 2020-05-13 18:16:50.703 Error returned from sendto, err: 22
I: 2020-05-13 18:16:50.703 YSF, Narrow transmit (72 bit)
E: 2020-05-13 18:16:50.825 Error returned from sendto, err: 22
E: 2020-05-13 18:16:50.887 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.009 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.127 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.183 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.305 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.423 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.490 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.515 Error returned from sendto, err: 22
E: 2020-05-13 18:16:51.607 Error returned from sendto, err: 22
M: 2020-05-13 18:16:51.709 YSF, TX state = OFF
E: 2020-05-13 18:16:51.709 Error returned from sendto, err: 22


Re: YSFReflector to Allstarlink

honda5603@...
 

That's what I've been doing, copy and past the entire log after cat it


Re: YSFReflector to Allstarlink

Steve N4IRS
 

Can you not copy and paste from TeraTerm? 

On 5/13/2020 2:09 PM, honda5603@... wrote:
Using TeraTerm from a PC.


Re: YSFReflector to Allstarlink

honda5603@...
 

Using TeraTerm from a PC.

3821 - 3840 of 10148