Topics

MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge


David
 





Hi Adrian

thanks for you infomation ,yes i use XLX with transcoding (one AMBE 3003 with ambed)
my goal is cross link XLX DMR <-> BM TG as my understand the lnk should

XLX(Dstar)<->transcode<->XLX(DMR)<->MMDVM_Bridge_XLX<->MMDVM_Bridge_BM<->BM TG(static TG gruop)

my problem both MMDBM_bridge can see frame from XLX or BM but only one way audio BM -> XLX (unstable still some audo drop

XLX -> BM is audio is not work .but can see the frame on both MB log (see below)

XLX side :

M: 2019-11-10 02:43:22.258 DMR Slot 2, received network voice header from BV3UN to TG 9
M: 2019-11-10 02:43:22.263 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-11-10 02:43:35.926 DMR Slot 2, received network voice header from BV3UN to TG 9
M: 2019-11-10 02:43:38.450 DMR Slot 2, received network end of voice transmission, 2.9 seconds, 12% packet loss, BER: 0.0%
M: 2019-11-10 02:43:41.062 DMR Slot 2, received network voice header from BV3UN to TG 9
M: 2019-11-10 02:43:45.311 DMR Slot 2, received network end of voice transmission, 4.4 seconds, 1% packet loss, BER: 0.0%
M: 2019-11-10 02:52:22.389 DMR, TX state = ON
I: 2019-11-10 02:52:22.389 DMR, Begin TX: src=4601096 rpt=0 dst=91 slot=2 cc=0 metadata=4601096
M: 2019-11-10 02:52:23.850 DMR, TX state = OFF, DMR frame count was 26 frames
M: 2019-11-10 02:52:29.990 DMR, TX state = ON
I: 2019-11-10 02:52:29.990 DMR, Begin TX: src=2345451 rpt=0 dst=91 slot=2 cc=0 metadata=M0ZEL
M: 2019-11-10 02:52:31.366 DMR, TX state = OFF, DMR frame count was 26 frames

BM side

M: 2019-11-10 02:43:22.262 DMR, TX state = ON
I: 2019-11-10 02:43:22.262 DMR, Begin TX: src=4660018 rpt=0 dst=9 slot=2 cc=0 metadata=BV3UN
M: 2019-11-10 02:43:22.268 DMR, TX state = OFF, DMR frame count was 2 frames
M: 2019-11-10 02:43:35.931 DMR, TX state = ON
I: 2019-11-10 02:43:35.931 DMR, Begin TX: src=4660018 rpt=0 dst=9 slot=2 cc=0 metadata=BV3UN
M: 2019-11-10 02:43:38.456 DMR, TX state = OFF, DMR frame count was 43 frames
M: 2019-11-10 02:43:41.064 DMR, TX state = ON
I: 2019-11-10 02:43:41.064 DMR, Begin TX: src=4660018 rpt=0 dst=9 slot=2 cc=0 metadata=BV3UN
M: 2019-11-10 02:43:45.311 DMR, TX state = OFF, DMR frame count was 72 frames

it seems TX site sill in BG TG 9 group not my wanted (46600)
在 2019年11月10日 星期日 上午8:49:24 [GMT+8], Adrian<vk4tux@...> 寫道:


ircddbgateway 2015 will work with XLX reflectors with no issue, if the
entry is in either DCS | DPLUS or DExtra host files, and very easily
manually added.


You can use ;




for reference or use,

which are correct propriety system [USTRUST] source with XLX supplement
for vacant number slots.

These are easy to manually edit for the XLX system you wish to add,
using DCS | REF| XRF prefix instead of XLX.

For latest ircddbgateway using XLX link feature, the link protocol is DCS.

However the system uses the XLX DMR database list to use a pure currect
list

of XLX reflectors and this is the main reason for it's addition to XLX,
I requested and worked with Geoff on this last year.


Config ;

xlxEnabled=1

which should already be in place.


If you are connecting to a XLX with transcoding, it is better to connect
with DMR direct now from MMDVM_Bridge,

rather than connecting via D-Star.

vk4tux



David
 

Hi Ernie

Thank a lot ,I will create new topic for ask 


 

Hi David
Were starting to get off topic.
Hblink3 has XLX connection built in. Set master-1 to any tg you want. Set up XLX-1 to the server you want to connect to.
In the rules.py change Client-1 to XLX-1. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of davidchien0327 via Groups.Io <davidchien0327@...>
Sent: Saturday, November 9, 2019 6:12:59 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
Hi Ernie 
Could you drawing the link topology? Is 

XLX DMR <->MB 1<-> HBlink 1<->to someone reflector?


David
 

Hi Ernie 
Could you drawing the link topology? Is 

XLX DMR <->MB 1<-> HBlink 1<->to someone reflector?


 

Hi David
That should work fine. I'm using hblink3 to do most of of my connections. Will find this  new update to MB very handy.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of davidchien0327 via Groups.Io <davidchien0327@...>
Sent: Saturday, November 9, 2019 5:32:08 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
Mine is change to 62042(+10) and works ,(no time out anymore) because I found had one MB connect BM TG 4601 and bridge to P25
 
Now I try to my XLX DMR module D to BM TG 46620 

Is link as below is right ?
XLX DMR <->MB 1<->MB 2<-> BM TG 

Ernie may I know yours is work normal?



David
 

Mine is change to 62042(+10) and works ,(no time out anymore) because I found had one MB connect BM TG 4601 and bridge to P25
 
Now I try to my XLX DMR module D to BM TG 46620 

Is link as below is right ?
XLX DMR <->MB 1<->MB 2<-> BM TG 

Ernie may I know yours is work normal?



 

Been rock solid since  I changed to Local=62035.
Thanks for all the help.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Saturday, November 9, 2019 4:51:37 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 

I said the define (i.e : define = stating a specified port number) is disabled, not the return port, I understand it is random return, that is very obvious.

On 9/11/19 11:13 am, Steve N4IRS wrote:
It is not disabled, it is random.

root@dvsm-server:/opt/MMDVM_Bridge# netstat -unap
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           13375/MMDVM_Bridge 
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           498/md380-emu      
udp        0      0 0.0.0.0:68              0.0.0.0:*                           487/dhcpcd         
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           13375/MMDVM_Bridge <------------ Defined in MB.ini
udp        0      0 0.0.0.0:34984           0.0.0.0:*                           336/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           336/avahi-daemon: r



root@dvsm-server:/opt/MMDVM_Bridge# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           13401/MMDVM_Bridge 
udp        0      0 0.0.0.0:2460            0.0.0.0:*                           13412/Analog_Bridge
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           498/md380-emu      
udp        0      0 0.0.0.0:34880           0.0.0.0:*                           13401/MMDVM_Bridge  <------------- Commented out
udp        0      0 0.0.0.0:68              0.0.0.0:*                           487/dhcpcd         
udp        0      0 0.0.0.0:34984           0.0.0.0:*                           336/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           336/avahi-daemon: r


On 11/8/19 8:03 PM, Adrian Fewster wrote:

[DMR Network]
Enable=1
Address=xlxdmr.duckdns.org
Port=62030
Jitter=300
#Local=62032
Password=passw0rd
Options=XLX:4017
Slot1=0
Slot2=1
Debug=0


Is what is used successfully here, Local define is disabled with #.



On 9/11/19 10:29 am, davidchien0327 via Groups.Io wrote:
Hi Ernie

You are fix time out problem right ? You mean you change dmr local port form default 62032 to another ? for example 62066 on mmdvm-bridge.ini ?

Thanks 


Adrian Fewster <vk4tux@...>
 

I said the define (i.e : define = stating a specified port number) is disabled, not the return port, I understand it is random return, that is very obvious.

On 9/11/19 11:13 am, Steve N4IRS wrote:
It is not disabled, it is random.

root@dvsm-server:/opt/MMDVM_Bridge# netstat -unap
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           13375/MMDVM_Bridge 
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           498/md380-emu      
udp        0      0 0.0.0.0:68              0.0.0.0:*                           487/dhcpcd         
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           13375/MMDVM_Bridge <------------ Defined in MB.ini
udp        0      0 0.0.0.0:34984           0.0.0.0:*                           336/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           336/avahi-daemon: r



root@dvsm-server:/opt/MMDVM_Bridge# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           13401/MMDVM_Bridge 
udp        0      0 0.0.0.0:2460            0.0.0.0:*                           13412/Analog_Bridge
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           498/md380-emu      
udp        0      0 0.0.0.0:34880           0.0.0.0:*                           13401/MMDVM_Bridge  <------------- Commented out
udp        0      0 0.0.0.0:68              0.0.0.0:*                           487/dhcpcd         
udp        0      0 0.0.0.0:34984           0.0.0.0:*                           336/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           336/avahi-daemon: r


On 11/8/19 8:03 PM, Adrian Fewster wrote:

[DMR Network]
Enable=1
Address=xlxdmr.duckdns.org
Port=62030
Jitter=300
#Local=62032
Password=passw0rd
Options=XLX:4017
Slot1=0
Slot2=1
Debug=0


Is what is used successfully here, Local define is disabled with #.



On 9/11/19 10:29 am, davidchien0327 via Groups.Io wrote:
Hi Ernie

You are fix time out problem right ? You mean you change dmr local port form default 62032 to another ? for example 62066 on mmdvm-bridge.ini ?

Thanks 


Steve N4IRS
 

It is not disabled, it is random.

root@dvsm-server:/opt/MMDVM_Bridge# netstat -unap
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           13375/MMDVM_Bridge 
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           498/md380-emu      
udp        0      0 0.0.0.0:68              0.0.0.0:*                           487/dhcpcd         
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           13375/MMDVM_Bridge <------------ Defined in MB.ini
udp        0      0 0.0.0.0:34984           0.0.0.0:*                           336/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           336/avahi-daemon: r



root@dvsm-server:/opt/MMDVM_Bridge# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           13401/MMDVM_Bridge 
udp        0      0 0.0.0.0:2460            0.0.0.0:*                           13412/Analog_Bridge
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           498/md380-emu      
udp        0      0 0.0.0.0:34880           0.0.0.0:*                           13401/MMDVM_Bridge  <------------- Commented out
udp        0      0 0.0.0.0:68              0.0.0.0:*                           487/dhcpcd         
udp        0      0 0.0.0.0:34984           0.0.0.0:*                           336/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           336/avahi-daemon: r


On 11/8/19 8:03 PM, Adrian Fewster wrote:

[DMR Network]
Enable=1
Address=xlxdmr.duckdns.org
Port=62030
Jitter=300
#Local=62032
Password=passw0rd
Options=XLX:4017
Slot1=0
Slot2=1
Debug=0


Is what is used successfully here, Local define is disabled with #.



On 9/11/19 10:29 am, davidchien0327 via Groups.Io wrote:
Hi Ernie

You are fix time out problem right ? You mean you change dmr local port form default 62032 to another ? for example 62066 on mmdvm-bridge.ini ?

Thanks 


Adrian Fewster <vk4tux@...>
 

[DMR Network]
Enable=1
Address=xlxdmr.duckdns.org
Port=62030
Jitter=300
#Local=62032
Password=passw0rd
Options=XLX:4017
Slot1=0
Slot2=1
Debug=0


Is what is used successfully here, Local define is disabled with #.



On 9/11/19 10:29 am, davidchien0327 via Groups.Io wrote:
Hi Ernie

You are fix time out problem right ? You mean you change dmr local port form default 62032 to another ? for example 62066 on mmdvm-bridge.ini ?

Thanks 


David
 

Hi Ernie

You are fix time out problem right ? You mean you change dmr local port form default 62032 to another ? for example 62066 on mmdvm-bridge.ini ?

Thanks 


 

Adrian
Got on to your XLX. I have fixed the problem. Had to change the dmr local port. Had another HB running on the Ubuntu machine.
The Debian 9 pc only had one MB running  it connected fine without any changes.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 9:59:18 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 

Ernest, can you try your bridge with XLX389 ?


xlxdmr.duckdns.org



On 9/11/19 7:26 am, Adrian Fewster via Groups.Io wrote:

I put back to xlx389 and no issue ;

I: 2019-11-08 21:23:50.043 Starting M: 2019-11-08 21:24:08.883 DMR, Logged into the master successfully
M: 2019-11-08 21:24:08.883 DMR, Remote CMD: txTg=4000
M: 2019-11-08 21:24:08.883 DMR, Tune: id=5054444, tg=4000, mode=Group
M: 2019-11-08 21:24:08.884 DMR, Remote CMD: txTg=4017
M: 2019-11-08 21:24:08.884 DMR, Tune: id=5054444, tg=4017, mode=Group
M: 2019-11-08 21:24:08.916 DMR Slot 2, received network voice header from 5054444 to TG 9
M: 2019-11-08 21:24:08.921 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%



On 9/11/19 5:02 am, Ernie Gm7kbk wrote:
You can test my XLX

IP 81.150.10.62
Port 62030
XLX:4005


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, November 8, 2019 4:43:42 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
Should not need DMRGateway What is your option and what server and port?

On 11/8/2019 11:22 AM, davidchien0327 via Groups.Io wrote:
Thanks KB3FS and Steve ,I had update to last MB version and can connect my XLX DMR with selected module with Options ,and seems can pass traffic from BM TG to my xlx module D 

But I got same result as Ernie
MB connects and will pass traffic. Then drops  with connection  to the master has timed out. Then reconnects. On both MMDVM-xlx and mmdvm-bm ,network link as below

XLX DMR <-> MB-xlx<->MB-bm<->BM TG 46620

Is the link correct? Or I need to add DMRgateway to each side ?
Thanks
De BV3UN 



 

I will try it on another machine.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, November 8, 2019 8:42:45 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
I disconnected about 20:16. Never lost connection to the XLX server.

On 11/8/2019 3:28 PM, Ernie Gm7kbk wrote:
19-11-08 20:19:18.696 DMR Slot 2, lost audio for 407ms filling in
D: 2019-11-08 20:19:19.104 DMR Slot 2, lost audio for 408ms filling in
D: 2019-11-08 20:19:19.511 DMR Slot 2, lost audio for 407ms filling in
M: 2019-11-08 20:19:19.791 DMR Slot 2, network watchdog has expired, 52.1 seconds, 2% packet loss, BER: 0.0%
E: 2019-11-08 20:20:17.736 DMR, Connection to the master has timed out, retrying connection
M: 2019-11-08 20:20:17.736 DMR, Closing DMR Network
M: 2019-11-08 20:20:17.736 DMR, Opening DMR Network
D: 2019-11-08 20:20:27.779 DMR, Sending authorisation
D: 2019-11-08 20:20:27.815 DMR, Sending configuration
This is what it is doing at the moment every 52 seconds


Steve N4IRS
 

I disconnected about 20:16. Never lost connection to the XLX server.

On 11/8/2019 3:28 PM, Ernie Gm7kbk wrote:
19-11-08 20:19:18.696 DMR Slot 2, lost audio for 407ms filling in
D: 2019-11-08 20:19:19.104 DMR Slot 2, lost audio for 408ms filling in
D: 2019-11-08 20:19:19.511 DMR Slot 2, lost audio for 407ms filling in
M: 2019-11-08 20:19:19.791 DMR Slot 2, network watchdog has expired, 52.1 seconds, 2% packet loss, BER: 0.0%
E: 2019-11-08 20:20:17.736 DMR, Connection to the master has timed out, retrying connection
M: 2019-11-08 20:20:17.736 DMR, Closing DMR Network
M: 2019-11-08 20:20:17.736 DMR, Opening DMR Network
D: 2019-11-08 20:20:27.779 DMR, Sending authorisation
D: 2019-11-08 20:20:27.815 DMR, Sending configuration
This is what it is doing at the moment every 52 seconds


 

19-11-08 20:19:18.696 DMR Slot 2, lost audio for 407ms filling in
D: 2019-11-08 20:19:19.104 DMR Slot 2, lost audio for 408ms filling in
D: 2019-11-08 20:19:19.511 DMR Slot 2, lost audio for 407ms filling in
M: 2019-11-08 20:19:19.791 DMR Slot 2, network watchdog has expired, 52.1 seconds, 2% packet loss, BER: 0.0%
E: 2019-11-08 20:20:17.736 DMR, Connection to the master has timed out, retrying connection
M: 2019-11-08 20:20:17.736 DMR, Closing DMR Network
M: 2019-11-08 20:20:17.736 DMR, Opening DMR Network
D: 2019-11-08 20:20:27.779 DMR, Sending authorisation
D: 2019-11-08 20:20:27.815 DMR, Sending configuration
This is what it is doing at the moment every 52 seconds


Steve N4IRS
 

M: 2019-11-08 14:23:14.874 MMDVM_Bridge-20191105_V1.4.0 is running
D: 2019-11-08 14:23:25.000 DMR, Sending authorisation
D: 2019-11-08 14:23:25.112 DMR, Sending configuration
M: 2019-11-08 14:23:35.333 DMR, Logged into the master successfully
D: 2019-11-08 14:23:35.333 DMR, Sending XLX options
M: 2019-11-08 14:23:35.333 DMR, Remote CMD: txTg=4000
M: 2019-11-08 14:23:35.333 DMR, Tune: id=3112138, tg=4000, mode=Group
M: 2019-11-08 14:23:35.333 DMR, Remote CMD: txTg=4005
M: 2019-11-08 14:23:35.333 DMR, Tune: id=3112138, tg=4005, mode=Group
M: 2019-11-08 14:23:35.461 DMR Slot 2, received network voice header from N4IRS to TG 9
M: 2019-11-08 14:23:35.467 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-11-08 14:23:38.840 DMR Slot 2, received network voice header from 2E0MHG to TG 9
M: 2019-11-08 14:23:39.805 DMR Slot 2, received network end of voice transmission, 1.0 seconds, 0% packet loss, BER: 0.0%
M: 2019-11-08 14:25:43.917 P25, received network transmission from KE0ABR to TG 10200
M: 2019-11-08 14:25:44.249 P25, network end of transmission, 0.7 seconds, 0% packet loss
M: 2019-11-08 14:26:16.250 P25, Remote CMD: rxport=30000
M: 2019-11-08 14:26:17.335 P25, Remote CMD: message=Setting mode to DMR
M: 2019-11-08 14:26:17.355 P25, Remote CMD: ambeMode=DMR
M: 2019-11-08 14:26:17.381 P25, Remote CMD: txport=31103
M: 2019-11-08 14:26:17.401 DMR, Remote CMD: rxport=31100
M: 2019-11-08 14:26:18.442 DMR, Remote CMD: info
M: 2019-11-08 14:26:20.936 DMR Slot 2, received network voice header from 2W0HFU to TG 9
M: 2019-11-08 14:26:25.503 DMR Slot 2, received network end of voice transmission, 4.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-11-08 14:28:40.586 P25, received network transmission from KE0ABR to TG 10200
M: 2019-11-08 14:28:41.308 P25, network end of transmission, 1.1 seconds, 0% packet loss

Has not dropped yet. (system time is wrong on test machine)

On 11/8/2019 2:02 PM, Ernie Gm7kbk wrote:
You can test my XLX

IP 81.150.10.62
Port 62030
XLX:4005


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, November 8, 2019 4:43:42 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
Should not need DMRGateway What is your option and what server and port?

On 11/8/2019 11:22 AM, davidchien0327 via Groups.Io wrote:
Thanks KB3FS and Steve ,I had update to last MB version and can connect my XLX DMR with selected module with Options ,and seems can pass traffic from BM TG to my xlx module D 

But I got same result as Ernie
MB connects and will pass traffic. Then drops  with connection  to the master has timed out. Then reconnects. On both MMDVM-xlx and mmdvm-bm ,network link as below

XLX DMR <-> MB-xlx<->MB-bm<->BM TG 46620

Is the link correct? Or I need to add DMRgateway to each side ?
Thanks
De BV3UN 




 

You can test my XLX

IP 81.150.10.62
Port 62030
XLX:4005


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, November 8, 2019 4:43:42 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
Should not need DMRGateway What is your option and what server and port?

On 11/8/2019 11:22 AM, davidchien0327 via Groups.Io wrote:
Thanks KB3FS and Steve ,I had update to last MB version and can connect my XLX DMR with selected module with Options ,and seems can pass traffic from BM TG to my xlx module D 

But I got same result as Ernie
MB connects and will pass traffic. Then drops  with connection  to the master has timed out. Then reconnects. On both MMDVM-xlx and mmdvm-bm ,network link as below

XLX DMR <-> MB-xlx<->MB-bm<->BM TG 46620

Is the link correct? Or I need to add DMRgateway to each side ?
Thanks
De BV3UN 



Steve N4IRS
 

Should not need DMRGateway What is your option and what server and port?

On 11/8/2019 11:22 AM, davidchien0327 via Groups.Io wrote:
Thanks KB3FS and Steve ,I had update to last MB version and can connect my XLX DMR with selected module with Options ,and seems can pass traffic from BM TG to my xlx module D 

But I got same result as Ernie
MB connects and will pass traffic. Then drops  with connection  to the master has timed out. Then reconnects. On both MMDVM-xlx and mmdvm-bm ,network link as below

XLX DMR <-> MB-xlx<->MB-bm<->BM TG 46620

Is the link correct? Or I need to add DMRgateway to each side ?
Thanks
De BV3UN 



David
 

Thanks KB3FS and Steve ,I had update to last MB version and can connect my XLX DMR with selected module with Options ,and seems can pass traffic from BM TG to my xlx module D 

But I got same result as Ernie
MB connects and will pass traffic. Then drops  with connection  to the master has timed out. Then reconnects. On both MMDVM-xlx and mmdvm-bm ,network link as below

XLX DMR <-> MB-xlx<->MB-bm<->BM TG 46620

Is the link correct? Or I need to add DMRgateway to each side ?
Thanks
De BV3UN 


Steve N4IRS
 

Yep,
That's what I get for copy and pasting at 05:44 AM local.

On 11/8/2019 9:49 AM, David Aitcheson KB3EFS wrote:
Uh OH me thinks needed more coffee...

All that is correct save for the typo in the "mv" line...  See below:

On 11/8/19 5:44 AM, Steve N4IRS wrote:
as root:
systemctl stop mmdvm_bridge
cd /tmp
wget https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.armhf

mv /opt/MMDVM_Bridge/MMDVM_Bridge mv /opt/MMDVM_Bridge/MMDVM_Bridge.old
SHOULD BE:
mv  /opt/MMDVM_Bridge/MMDVM_Bridge  /opt/MMDVM_Bridge/MMDVM_Bridge.old
Eliminate the second "mv" and all works fine.

cp /tmp/MMDVM_Bridge.armhf /opt/MMDVM_Bridge/MMDVM_Bridge
systemctl start mmdvm_bridge


Thus the corrected commands in order are:

as root:
systemctl stop mmdvm_bridge
cd /tmp
wget https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.armhf
mv /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.old
cp /tmp/MMDVM_Bridge.armhf /opt/MMDVM_Bridge/MMDVM_Bridge
systemctl start mmdvm_bridge

73
Dave
KB3EFS