Date   

Re: DMR to YSF Weird Issue

Jake Litwin
 

Ahh i see. Thanks for the guidance Steve. 

On Sat, Nov 9, 2019 at 6:07 AM Steve N4IRS <szingman@...> wrote:
Jake,
Yes, the bug you reported was fixed in a later version of MMDVM_Bridge. I push fixes and enhancements to github first. Once proven, I build the apt packages. I'm refreshing all of the apt packages and adding some. My plan going forward is to package updates into apt on or around the first of the month if there are changes.

73, Steve N4IRS

On 11/8/19 11:54 PM, Jake Litwin wrote:
Actually, I think I got it Steve. The logs are back to normal. Thanks so much for the guidance. So the executable that I was running, I take it that must have been an older one?

On Fri, Nov 8, 2019 at 10:40 PM Jake Litwin via Groups.Io <litwinjwi=gmail.com@groups.io> wrote:
Thanks Steve 

All seems to be working on the mobiles now but I'm seeing this output in the logs. Is this normal?

: 2019-11-09 04:39:31.410 YSF, received network data from N7VDR/JIMI to ALL        at N7VDR     

I: 2019-11-09 04:39:31.410 YSF, Lookup call N7VDR returned id 3108345 -> 3108345

M: 2019-11-09 04:39:31.415 DMR, TX state = ON

I: 2019-11-09 04:39:31.415 DMR, Begin TX: src=3108345 rpt=0 dst=420 slot=2 cc=0 metadata=N7VDR

D: 2019-11-09 04:39:32.041 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.041 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.134 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.134 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:32.833 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.833 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.941 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.941 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:33.639 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:33.639 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:33.736 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:33.736 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:34.437 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:34.437 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:34.534 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:34.534 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:35.263 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:35.263 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:35.340 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:35.340 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.032 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.032 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:36.136 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:36.136 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.839 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.839 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

M: 2019-11-09 04:39:36.932 YSF, received network end of transmission, 5.7 seconds, 0% packet loss, BER: 0.0%

M: 2019-11-09 04:39:36.937 DMR, TX state = OFF, DMR frame count was 93 frames

M: 2019-11-09 04:39:39.645 YSF, received network data from WD0HDR/DAV to ALL        at WD0HDR    

I: 2019-11-09 04:39:39.645 YSF, Lookup call WD0HDR returned id 3108613 -> 3108613

M: 2019-11-09 04:39:39.650 DMR, TX state = ON

I: 2019-11-09 04:39:39.651 DMR, Begin TX: src=3108613 rpt=0 dst=420 slot=2 cc=0 metadata=WD0HDR

D: 2019-11-09 04:39:40.343 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:40.344 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:40.462 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:40.462 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.158 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:41.158 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:41.246 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:41.246 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.943 V/D Mode 2 Data, DT1



On Fri, Nov 8, 2019 at 10:13 PM Steve N4IRS <szingman@...> wrote:
There is no TX offset on s bridge.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 11:09:34 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR to YSF Weird Issue
 

Try adjusting TX offset in modem section to suit all.

On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: DMR to YSF Weird Issue

Steve N4IRS
 

Jake,
Yes, the bug you reported was fixed in a later version of MMDVM_Bridge. I push fixes and enhancements to github first. Once proven, I build the apt packages. I'm refreshing all of the apt packages and adding some. My plan going forward is to package updates into apt on or around the first of the month if there are changes.

73, Steve N4IRS

On 11/8/19 11:54 PM, Jake Litwin wrote:
Actually, I think I got it Steve. The logs are back to normal. Thanks so much for the guidance. So the executable that I was running, I take it that must have been an older one?

On Fri, Nov 8, 2019 at 10:40 PM Jake Litwin via Groups.Io <litwinjwi=gmail.com@groups.io> wrote:
Thanks Steve 

All seems to be working on the mobiles now but I'm seeing this output in the logs. Is this normal?

: 2019-11-09 04:39:31.410 YSF, received network data from N7VDR/JIMI to ALL        at N7VDR     

I: 2019-11-09 04:39:31.410 YSF, Lookup call N7VDR returned id 3108345 -> 3108345

M: 2019-11-09 04:39:31.415 DMR, TX state = ON

I: 2019-11-09 04:39:31.415 DMR, Begin TX: src=3108345 rpt=0 dst=420 slot=2 cc=0 metadata=N7VDR

D: 2019-11-09 04:39:32.041 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.041 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.134 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.134 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:32.833 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.833 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.941 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.941 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:33.639 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:33.639 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:33.736 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:33.736 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:34.437 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:34.437 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:34.534 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:34.534 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:35.263 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:35.263 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:35.340 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:35.340 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.032 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.032 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:36.136 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:36.136 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.839 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.839 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

M: 2019-11-09 04:39:36.932 YSF, received network end of transmission, 5.7 seconds, 0% packet loss, BER: 0.0%

M: 2019-11-09 04:39:36.937 DMR, TX state = OFF, DMR frame count was 93 frames

M: 2019-11-09 04:39:39.645 YSF, received network data from WD0HDR/DAV to ALL        at WD0HDR    

I: 2019-11-09 04:39:39.645 YSF, Lookup call WD0HDR returned id 3108613 -> 3108613

M: 2019-11-09 04:39:39.650 DMR, TX state = ON

I: 2019-11-09 04:39:39.651 DMR, Begin TX: src=3108613 rpt=0 dst=420 slot=2 cc=0 metadata=WD0HDR

D: 2019-11-09 04:39:40.343 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:40.344 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:40.462 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:40.462 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.158 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:41.158 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:41.246 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:41.246 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.943 V/D Mode 2 Data, DT1



On Fri, Nov 8, 2019 at 10:13 PM Steve N4IRS <szingman@...> wrote:
There is no TX offset on s bridge.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 11:09:34 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR to YSF Weird Issue
 

Try adjusting TX offset in modem section to suit all.

On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

 

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?


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

David BV3UN
 

Hi Ernie 
Could you drawing the link topology? Is 

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


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

 

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?



Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

David BV3UN
 

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?



Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

 

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 


Re: DMR to YSF Weird Issue

Adrian Fewster <vk4tux@...>
 

It seems odd your HT's would work and not the mobiles in regard to bridging software.

i was of course referring to your mmdvm config regarding modem section , and not the bridge. i understand the bridge has no modem connected,

in the bridging software..I thought that would be obvious when talking about the modem.

I have seen similar things due to frequency and deviation variations in mmdvm configurations.

Is it a mmdvm repeater or hotspot that feeds the RF to your YSF hardware    ?



On 9/11/19 2:54 pm, Jake Litwin wrote:
Actually, I think I got it Steve. The logs are back to normal. Thanks so much for the guidance. So the executable that I was running, I take it that must have been an older one?

On Fri, Nov 8, 2019 at 10:40 PM Jake Litwin via Groups.Io <litwinjwi=gmail.com@groups.io> wrote:
Thanks Steve 

All seems to be working on the mobiles now but I'm seeing this output in the logs. Is this normal?

: 2019-11-09 04:39:31.410 YSF, received network data from N7VDR/JIMI to ALL        at N7VDR     

I: 2019-11-09 04:39:31.410 YSF, Lookup call N7VDR returned id 3108345 -> 3108345

M: 2019-11-09 04:39:31.415 DMR, TX state = ON

I: 2019-11-09 04:39:31.415 DMR, Begin TX: src=3108345 rpt=0 dst=420 slot=2 cc=0 metadata=N7VDR

D: 2019-11-09 04:39:32.041 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.041 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.134 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.134 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:32.833 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.833 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.941 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.941 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:33.639 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:33.639 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:33.736 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:33.736 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:34.437 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:34.437 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:34.534 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:34.534 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:35.263 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:35.263 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:35.340 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:35.340 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.032 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.032 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:36.136 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:36.136 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.839 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.839 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

M: 2019-11-09 04:39:36.932 YSF, received network end of transmission, 5.7 seconds, 0% packet loss, BER: 0.0%

M: 2019-11-09 04:39:36.937 DMR, TX state = OFF, DMR frame count was 93 frames

M: 2019-11-09 04:39:39.645 YSF, received network data from WD0HDR/DAV to ALL        at WD0HDR    

I: 2019-11-09 04:39:39.645 YSF, Lookup call WD0HDR returned id 3108613 -> 3108613

M: 2019-11-09 04:39:39.650 DMR, TX state = ON

I: 2019-11-09 04:39:39.651 DMR, Begin TX: src=3108613 rpt=0 dst=420 slot=2 cc=0 metadata=WD0HDR

D: 2019-11-09 04:39:40.343 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:40.344 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:40.462 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:40.462 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.158 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:41.158 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:41.246 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:41.246 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.943 V/D Mode 2 Data, DT1



On Fri, Nov 8, 2019 at 10:13 PM Steve N4IRS <szingman@...> wrote:
There is no TX offset on s bridge.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 11:09:34 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR to YSF Weird Issue
 

Try adjusting TX offset in modem section to suit all.

On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: DMR to YSF Weird Issue

Jake Litwin
 

Actually, I think I got it Steve. The logs are back to normal. Thanks so much for the guidance. So the executable that I was running, I take it that must have been an older one?


On Fri, Nov 8, 2019 at 10:40 PM Jake Litwin via Groups.Io <litwinjwi=gmail.com@groups.io> wrote:
Thanks Steve 

All seems to be working on the mobiles now but I'm seeing this output in the logs. Is this normal?

: 2019-11-09 04:39:31.410 YSF, received network data from N7VDR/JIMI to ALL        at N7VDR     

I: 2019-11-09 04:39:31.410 YSF, Lookup call N7VDR returned id 3108345 -> 3108345

M: 2019-11-09 04:39:31.415 DMR, TX state = ON

I: 2019-11-09 04:39:31.415 DMR, Begin TX: src=3108345 rpt=0 dst=420 slot=2 cc=0 metadata=N7VDR

D: 2019-11-09 04:39:32.041 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.041 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.134 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.134 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:32.833 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.833 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.941 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.941 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:33.639 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:33.639 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:33.736 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:33.736 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:34.437 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:34.437 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:34.534 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:34.534 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:35.263 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:35.263 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:35.340 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:35.340 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.032 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.032 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:36.136 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:36.136 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.839 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.839 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

M: 2019-11-09 04:39:36.932 YSF, received network end of transmission, 5.7 seconds, 0% packet loss, BER: 0.0%

M: 2019-11-09 04:39:36.937 DMR, TX state = OFF, DMR frame count was 93 frames

M: 2019-11-09 04:39:39.645 YSF, received network data from WD0HDR/DAV to ALL        at WD0HDR    

I: 2019-11-09 04:39:39.645 YSF, Lookup call WD0HDR returned id 3108613 -> 3108613

M: 2019-11-09 04:39:39.650 DMR, TX state = ON

I: 2019-11-09 04:39:39.651 DMR, Begin TX: src=3108613 rpt=0 dst=420 slot=2 cc=0 metadata=WD0HDR

D: 2019-11-09 04:39:40.343 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:40.344 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:40.462 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:40.462 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.158 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:41.158 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:41.246 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:41.246 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.943 V/D Mode 2 Data, DT1



On Fri, Nov 8, 2019 at 10:13 PM Steve N4IRS <szingman@...> wrote:
There is no TX offset on s bridge.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 11:09:34 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR to YSF Weird Issue
 

Try adjusting TX offset in modem section to suit all.

On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

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 


Re: DMR to YSF Weird Issue

Jake Litwin
 

Thanks Steve 

All seems to be working on the mobiles now but I'm seeing this output in the logs. Is this normal?

: 2019-11-09 04:39:31.410 YSF, received network data from N7VDR/JIMI to ALL        at N7VDR     

I: 2019-11-09 04:39:31.410 YSF, Lookup call N7VDR returned id 3108345 -> 3108345

M: 2019-11-09 04:39:31.415 DMR, TX state = ON

I: 2019-11-09 04:39:31.415 DMR, Begin TX: src=3108345 rpt=0 dst=420 slot=2 cc=0 metadata=N7VDR

D: 2019-11-09 04:39:32.041 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.041 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.134 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.134 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:32.833 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:32.833 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:32.941 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:32.941 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:33.639 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:33.639 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:33.736 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:33.736 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:34.437 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:34.437 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:34.534 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:34.534 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:35.263 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:35.263 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:35.340 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:35.340 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.032 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.032 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

D: 2019-11-09 04:39:36.136 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:36.136 0000:  55 71 5F 2F 6C 21 52 20 03 FA                      *Uq_/l!R ..*

D: 2019-11-09 04:39:36.839 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:36.839 0000:  1D 22 62 5F 29 54 30 53 52 52                      *."b_)T0SRR*

M: 2019-11-09 04:39:36.932 YSF, received network end of transmission, 5.7 seconds, 0% packet loss, BER: 0.0%

M: 2019-11-09 04:39:36.937 DMR, TX state = OFF, DMR frame count was 93 frames

M: 2019-11-09 04:39:39.645 YSF, received network data from WD0HDR/DAV to ALL        at WD0HDR    

I: 2019-11-09 04:39:39.645 YSF, Lookup call WD0HDR returned id 3108613 -> 3108613

M: 2019-11-09 04:39:39.650 DMR, TX state = ON

I: 2019-11-09 04:39:39.651 DMR, Begin TX: src=3108613 rpt=0 dst=420 slot=2 cc=0 metadata=WD0HDR

D: 2019-11-09 04:39:40.343 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:40.344 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:40.462 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:40.462 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.158 V/D Mode 2 Data, DT1

D: 2019-11-09 04:39:41.158 0000:  2F 22 62 5F 25 54 30 52 52 59                      */"b_%T0RRY*

D: 2019-11-09 04:39:41.246 V/D Mode 2 Data, DT2

D: 2019-11-09 04:39:41.246 0000:  59 70 46 5D 6C 20 50 20 03 23                      *YpF]l P .#*

D: 2019-11-09 04:39:41.943 V/D Mode 2 Data, DT1



On Fri, Nov 8, 2019 at 10:13 PM Steve N4IRS <szingman@...> wrote:
There is no TX offset on s bridge.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 11:09:34 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR to YSF Weird Issue
 

Try adjusting TX offset in modem section to suit all.

On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: DMR to YSF Weird Issue

Steve N4IRS
 

There is no TX offset on s bridge.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Friday, November 8, 2019 11:09:34 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR to YSF Weird Issue
 

Try adjusting TX offset in modem section to suit all.

On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: DMR to YSF Weird Issue

Steve N4IRS
 

Jake,
Replace your MMDVM_Bridge executable with one from here <https://github.com/DVSwitch/MMDVM_Bridge/tree/master/bin> Choose the proper file for your hardware.
You can download the file with wget https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.xxxx

If you don't know which file to choose tell us your hardware.

73, Steve N4IRS

On 11/8/19 10:53 PM, Jake Litwin wrote:
Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


DMR to YSF Weird Issue

Jake Litwin
 

Just curious to see if anyone has experienced this.. I have YSF bridged to DMR with MMDVM with the instructions provided here on the DVSwitch group. Everything seems to be fine except when mobile YSF radios receive a transmission from the DMR side, there's only about a second or two of audio and then nothing. The blue light on the YSF mobile blinks. YSF handhelds like the FT-3's, FT-2's, receive DMR just fine without any issues. Not sure why my setup would be affecting the mobile YSF radios only and not the YSF handhelds.


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

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 


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

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 


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

David BV3UN
 

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 


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

 

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 



Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

 

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


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

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

4761 - 4780 of 9925