Topics

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.

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.

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.

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.

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.

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.

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.

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.

Walter Holmes K5WH
 

Steve,

 Was this a pretty recent change?  As I just installed the bridge about 2 or 3 weeks ago.

Many thanks,
Walter/K5WH

Dexter Harroo
 

What did you do to resolve the issue? I seem to be having the same problem


On Sat, Nov 9, 2019, 12:55 AM Jake Litwin <litwinjwi@...> 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.

Steve N4IRS
 

On 11/11/19 5:28 PM, Dexter Harroo wrote:
What did you do to resolve the issue? I seem to be having the same problem

On Sat, Nov 9, 2019, 12:55 AM Jake Litwin <litwinjwi@...> 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.

Carlos Minguela <minguela@...>
 

Thanks Steve.  I had the same problem and this fix solve it.  

73
Carlos
KP4CA

Walter Holmes K5WH
 

Steve,

 I tried replacing the file, but I was not able to get the service to start afterwards.
Here is what my system is.   4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64
So I used the MMDVM_Bridge.amd64 and removed the .amd64 of course, reset the machine, but the service did not deem to start properly.  I had to replace the original file for that to come back up properly.
 Any idea where I should look further into this?
many thanks, Walter/K5WH

Steve N4IRS
 

Put MMDVM_Bridge.amd64 in /opt/MMDVM_Bridge (do not rename file)
As root:
systemctl stop mmdvm_bridge
./MMDVM_Bridge.amd64 MMDVM_Bridge.ini

Does the program run?
 

On 11/12/2019 9:54 AM, Walter Holmes K5WH wrote:
Steve,

 I tried replacing the file, but I was not able to get the service to start afterwards.
Here is what my system is.   4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64
So I used the MMDVM_Bridge.amd64 and removed the .amd64 of course, reset the machine, but the service did not deem to start properly.  I had to replace the original file for that to come back up properly.
 Any idea where I should look further into this?
many thanks, Walter/K5WH

Walter Holmes K5WH
 

hmm, even as root, I get a permission denied message when trying to run that.

Steve N4IRS
 

hmmm,
Try this, I don't think it will work but

chmod +x MMDVM_Bridge.amd64

try again

I'm checking here too

On 11/12/2019 10:51 AM, Walter Holmes K5WH wrote:
hmm, even as root, I get a permission denied message when trying to run that.

Steve N4IRS
 

Walter,
I updated MMMDVM_Bridge.amd64 yesterday. Please get a fresh copy from github.

Steve

On 11/12/2019 10:51 AM, Walter Holmes K5WH wrote:
hmm, even as root, I get a permission denied message when trying to run that.

Walter Holmes K5WH
 

yes, that works now Steve..

many thanks,

Walter Holmes K5WH
 

Steve,

 

To have this run as a service now, should I rename the MMMDVM_Bridge.amd64 file as MMMDVM_Bridge, so I can restart the mmdvm_bridge service?

 

Or is there an easier way to have the ./MMDVM_Bridge.amd64 MMDVM_Bridge.ini launch at startup automatically?

 

Or possibly the apt-get update and apt-get upgrade if the package is updated there already?

 

Thanks,

Walter/K5WH

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Tuesday, November 12, 2019 10:02 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to YSF Weird Issue

 

Walter,
I updated MMMDVM_Bridge.amd64 yesterday. Please get a fresh copy from github.

Steve

On 11/12/2019 10:51 AM, Walter Holmes K5WH wrote:

hmm, even as root, I get a permission denied message when trying to run that.

 

Steve N4IRS
 

Walter,
The reason the  file has a extension is so that people can determine which file they need for their architecture. You can rename the file so that it matches your service.
I put the most current version on github so people can try the new program to fix bugs or add features before I publish the file in the APT repository.

Once a month, I will update the APT repository, if the most current program is over 2 weeks old (and no bugs reported)

73, Steve N4IRS

On 11/14/19 6:39 PM, Walter Holmes K5WH wrote:

Steve,

 

To have this run as a service now, should I rename the MMMDVM_Bridge.amd64 file as MMMDVM_Bridge, so I can restart the mmdvm_bridge service?

 

Or is there an easier way to have the ./MMDVM_Bridge.amd64 MMDVM_Bridge.ini launch at startup automatically?

 

Or possibly the apt-get update and apt-get upgrade if the package is updated there already?

 

Thanks,

Walter/K5WH

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Tuesday, November 12, 2019 10:02 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to YSF Weird Issue

 

Walter,
I updated MMMDVM_Bridge.amd64 yesterday. Please get a fresh copy from github.

Steve

On 11/12/2019 10:51 AM, Walter Holmes K5WH wrote:

hmm, even as root, I get a permission denied message when trying to run that.