Date   

Re: Allstar issue using DVSwitch

Steve N4IRS
 

Use *341522

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of John-EA5JAV <ambrosj@...>
Sent: Monday, January 17, 2022 2:27:19 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Allstar issue using DVSwitch
 
Hello, I have a problem with DVSwitch when using Allstar, everything is configured as am able to receive incoming transmissions when I connect to a node e.g. 41522 using command *241522 followed by SEND, but when I transmit nothing heard other end. My allstar node is bridged with Echolink Repeater and am able to Tx and Rx to myself when not connected to a node,  I can however Tx and Rx to a connected Allstar node via Echolink, why can't I Tx directly from Allstar? Any advice appreciated please. Thanks, John


Allstar issue using DVSwitch

John
 

Hello, I have a problem with DVSwitch when using Allstar, everything is configured as am able to receive incoming transmissions when I connect to a node e.g. 41522 using command *241522 followed by SEND, but when I transmit nothing heard other end. My allstar node is bridged with Echolink Repeater and am able to Tx and Rx to myself when not connected to a node,  I can however Tx and Rx to a connected Allstar node via Echolink, why can't I Tx directly from Allstar? Any advice appreciated please. Thanks, John


Screen Layout

Chris Viningre
 

How do I change the DVSwitch HTML Client screen layout? Menus are covering other menus and I would also like to add or change one of the buttons to TGIF. I would also like to change the profile photo.

image.png
--


Re: AMBE GPIO board for Pi B 3+ - Where to Buy One?

Rob KA2PBT
 

don't forget the ZUM AMBE board ... connects over ethernet or WIFI 


Re: AMBE GPIO board for Pi B 3+ - Where to Buy One?

Patrick Perdue
 

NWDigital used to make one, but they haven't for a while. If you only need one channel, get a ThumnDV or DVMega DVstick 30 USB dongle. There is also a three channel one, the DVstick 33.

On 1/15/2022 3:19 PM, Mike Jensen (ZL4IA) wrote:
Does anyone know where I can buy one of these AMBE GPIO boards for Pi B 3+.

I would like to build an advanced DVSwitch server.

Thanks
Mike
ZL4IA


Re: AMBE GPIO board for Pi B 3+ - Where to Buy One?

Mike KB8JNM
 

Could you point a link where you herd about such a device ?

On 1/15/2022 3:19 PM, Mike Jensen (ZL4IA) wrote:
Does anyone know where I can buy one of these AMBE GPIO boards for Pi B 3+.

I would like to build an advanced DVSwitch server.

Thanks
Mike
ZL4IA


AMBE GPIO board for Pi B 3+ - Where to Buy One?

Mike Jensen (ZL4IA)
 

Does anyone know where I can buy one of these AMBE GPIO boards for Pi B 3+.

I would like to build an advanced DVSwitch server.

Thanks
Mike
ZL4IA


Re: Fusion kills the MMDVM Bridge

Greg AD4GC
 

I made these changes (noted in bold) to the /opt/MMDVM_Bridge/DVSwitch.ini file and everything sprang to life. So far in testing it passes data and voice both directions and has stopped kicking out. 

; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or you can supply
;   an absolute path in the DVSWITCH environment variable, e.g:
;   DVSWITCH=/etc/MMDVM_Bridge/DVSwitch.ini
;   before executing MMDVM_Bridge
;
; Another method to set the enviorment variable is to use the systemd unit file
; by adding:
; Environment=DVSWITCH=/etc/MMDVM_Bridge/DVSwitch.ini
; to /lib/systemd/system/mmdvm_bridge.service
 
; Configure the DMR Partner
; Audio format is AMBE 72 bit
[DMR]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
txPort = 31100                  ; Port to send AMBE TLV frames to (export)
rxPort = 31103                  ; Port to listen on (import)
slot = 2                        ; Export slot
exportTG = 3158576              ; Which TG to export
hangTimerInFrames = 0           ; Use 50 for 3 seconds of hang time (3000 / 60)
talkerAlias = %callsign %location %description ; Get callsign location and description from MMDVM_Bridge.ini
 
; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
txPort = 31103                  ; Port to send AMBE TLV frames to (export)
rxPort = 31100                  ; Port to listen on (import)
txWidePort = 35105              ; Port to send IMBE TLV frames to for YSFw (export)
fallbackID = 3158576            ; In case we can not find a valid DMR id in the database, export this one
exportTG = 31219                ; Which TG to export
slot = 2                        ; Export slot
RemotePort = 6073               ; Port to send Gateway commands to
 
; Configure the BrandMeister connection
; Simple Terminal Feature Update
; Audio format is AMBE 72 bit
[STFU]                          ; Brandmeister Open DMR Terminal (ODMRT) Protocol
BMAddress = 3102.repeater.net   ; Brandmeister ODMRT server address
BMPort = 54006                  ; Brandmeister ODMRT port
BMPassword = Farming@19           ; Your Brandmeister password
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
txPort  = 36100                 ; Port to send AMBE TLV frames to (export)
rxPort  = 36103                 ; Port to listen on (import)
UserID  = 315857611             ; Your DMR ID + SSID
TalkerAlias = N0CALL Name City  ; Max 27 characters
StartTG = 31219                 ; Startup talk group
LogLevel = 3                    ; STFU log level (0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error)


Thank you guys for your help!
Best of 73
Greg AD4GC


Re: Fusion kills the MMDVM Bridge

Corey Dean N3FE
 

Please stop using 31219 as well and use your dmrid as a talkgroup.

Corey n3fe


On Jan 11, 2022, at 2:38 AM, Ernie Gm7kbk <erniepratt@...> wrote:


In Dvswitch.ini exportTG=9 under Dmr section  should be 31219.
No need for ysfgateway.
Run MMDVM_Bridge in a window. Look in ini file and you will see various debug=0 change to debug=1 to see live info.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Greg AD4GC via groups.io <ad4gc@...>
Sent: Tuesday, January 11, 2022 5:07:38 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Fusion kills the MMDVM Bridge
 
I finally found the script for a live log.....
This is two key-ups from YSF, it did not recognize the DMR right after the YSF key up, I had to wait until it "reset" to capture it.

pi@raspberrypi:~ $ tail -f /var/log/mmdvm/MMDVM_Bridge-2022-01-11.log
I: 2022-01-11 04:54:49.664 YSF, Narrow transmit (72 bit)
M: 2022-01-11 04:54:50.113 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 04:54:50.612 DMR Slot 2, received network end of voice transmission, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 04:54:50.612 YSF, TX state = OFF
M: 2022-01-11 04:55:03.806 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:55:03.806 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:55:03.813 DMR, TX state = ON
I: 2022-01-11 04:55:03.813 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:55:08.312 YSF, received network end of transmission, 4.6 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:55:08.312 DMR, TX state = OFF, DMR frame count was 75 frames
 
 
M: 2022-01-11 04:58:27.893 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:58:27.894 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:58:27.900 DMR, TX state = ON
I: 2022-01-11 04:58:27.900 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:58:31.994 YSF, received network end of transmission, 4.2 seconds, 0% packet loss, BER: 0.4%
M: 2022-01-11 04:58:32.000 DMR, TX state = OFF, DMR frame count was 68 frames
 
 
M: 2022-01-11 04:59:18.097 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:59:18.097 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:59:18.103 DMR, TX state = ON
I: 2022-01-11 04:59:18.103 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:59:23.183 YSF, received network end of transmission, 5.2 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:59:23.189 DMR, TX state = OFF, DMR frame count was 85 frames


And this is the live log with two DMR key-ups, when the bridge hears the DMR it passes audio through to YSF but only until YSF is keyed and then have to wait for it to reset.

pi@raspberrypi:~ $ tail -f /var/log/mmdvm/MMDVM_Bridge-2022-01-11.log
M: 2022-01-11 04:58:27.900 DMR, TX state = ON
I: 2022-01-11 04:58:27.900 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:58:31.994 YSF, received network end of transmission, 4.2 seconds, 0% packet loss, BER: 0.4%
M: 2022-01-11 04:58:32.000 DMR, TX state = OFF, DMR frame count was 68 frames
M: 2022-01-11 04:59:18.097 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:59:18.097 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:59:18.103 DMR, TX state = ON
I: 2022-01-11 04:59:18.103 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:59:23.183 YSF, received network end of transmission, 5.2 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:59:23.189 DMR, TX state = OFF, DMR frame count was 85 frames
 
 
M: 2022-01-11 05:04:24.256 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 05:04:24.256 YSF, TX state = ON
I: 2022-01-11 05:04:24.257 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 05:04:24.268 YSF, Narrow transmit (72 bit)
M: 2022-01-11 05:04:24.737 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 05:04:25.457 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 05:04:26.177 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 05:04:32.055 DMR Slot 2, received network end of voice transmission, 8.0 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 05:04:32.056 YSF, TX state = OFF
 
M: 2022-01-11 05:04:42.344 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 05:04:42.345 YSF, TX state = ON
I: 2022-01-11 05:04:42.346 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 05:04:42.408 YSF, Narrow transmit (72 bit)
M: 2022-01-11 05:04:43.006 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 05:04:43.726 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 05:04:44.447 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 05:04:52.484 DMR Slot 2, received network end of voice transmission, 10.2 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 05:04:52.484 YSF, TX state = OFF
 
So what is it that I am missing?
Any help will be appreciated! 
Thanks, 
Greg AD4GC


DVSwitch YSF DGID

Bruno
 

Hi,
Is it possible with DVSwitch to use DGIDs on YSF because we find several systems that use this Group Mode feature on C4FM stations.
Can we do the same thing with DVSwitch Server and Mobile.
--
73's
F1PTL Bruno


Re: Fusion kills the MMDVM Bridge

 

In Dvswitch.ini exportTG=9 under Dmr section  should be 31219.
No need for ysfgateway.
Run MMDVM_Bridge in a window. Look in ini file and you will see various debug=0 change to debug=1 to see live info.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Greg AD4GC via groups.io <ad4gc@...>
Sent: Tuesday, January 11, 2022 5:07:38 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Fusion kills the MMDVM Bridge
 
I finally found the script for a live log.....
This is two key-ups from YSF, it did not recognize the DMR right after the YSF key up, I had to wait until it "reset" to capture it.

pi@raspberrypi:~ $ tail -f /var/log/mmdvm/MMDVM_Bridge-2022-01-11.log
I: 2022-01-11 04:54:49.664 YSF, Narrow transmit (72 bit)
M: 2022-01-11 04:54:50.113 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 04:54:50.612 DMR Slot 2, received network end of voice transmission, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 04:54:50.612 YSF, TX state = OFF
M: 2022-01-11 04:55:03.806 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:55:03.806 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:55:03.813 DMR, TX state = ON
I: 2022-01-11 04:55:03.813 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:55:08.312 YSF, received network end of transmission, 4.6 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:55:08.312 DMR, TX state = OFF, DMR frame count was 75 frames
 
 
M: 2022-01-11 04:58:27.893 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:58:27.894 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:58:27.900 DMR, TX state = ON
I: 2022-01-11 04:58:27.900 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:58:31.994 YSF, received network end of transmission, 4.2 seconds, 0% packet loss, BER: 0.4%
M: 2022-01-11 04:58:32.000 DMR, TX state = OFF, DMR frame count was 68 frames
 
 
M: 2022-01-11 04:59:18.097 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:59:18.097 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:59:18.103 DMR, TX state = ON
I: 2022-01-11 04:59:18.103 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:59:23.183 YSF, received network end of transmission, 5.2 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:59:23.189 DMR, TX state = OFF, DMR frame count was 85 frames


And this is the live log with two DMR key-ups, when the bridge hears the DMR it passes audio through to YSF but only until YSF is keyed and then have to wait for it to reset.

pi@raspberrypi:~ $ tail -f /var/log/mmdvm/MMDVM_Bridge-2022-01-11.log
M: 2022-01-11 04:58:27.900 DMR, TX state = ON
I: 2022-01-11 04:58:27.900 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:58:31.994 YSF, received network end of transmission, 4.2 seconds, 0% packet loss, BER: 0.4%
M: 2022-01-11 04:58:32.000 DMR, TX state = OFF, DMR frame count was 68 frames
M: 2022-01-11 04:59:18.097 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:59:18.097 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:59:18.103 DMR, TX state = ON
I: 2022-01-11 04:59:18.103 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:59:23.183 YSF, received network end of transmission, 5.2 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:59:23.189 DMR, TX state = OFF, DMR frame count was 85 frames
 
 
M: 2022-01-11 05:04:24.256 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 05:04:24.256 YSF, TX state = ON
I: 2022-01-11 05:04:24.257 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 05:04:24.268 YSF, Narrow transmit (72 bit)
M: 2022-01-11 05:04:24.737 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 05:04:25.457 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 05:04:26.177 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 05:04:32.055 DMR Slot 2, received network end of voice transmission, 8.0 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 05:04:32.056 YSF, TX state = OFF
 
M: 2022-01-11 05:04:42.344 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 05:04:42.345 YSF, TX state = ON
I: 2022-01-11 05:04:42.346 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 05:04:42.408 YSF, Narrow transmit (72 bit)
M: 2022-01-11 05:04:43.006 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 05:04:43.726 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 05:04:44.447 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 05:04:52.484 DMR Slot 2, received network end of voice transmission, 10.2 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 05:04:52.484 YSF, TX state = OFF
 
So what is it that I am missing?
Any help will be appreciated! 
Thanks, 
Greg AD4GC


Re: Fusion kills the MMDVM Bridge

Greg AD4GC
 

I finally found the script for a live log.....
This is two key-ups from YSF, it did not recognize the DMR right after the YSF key up, I had to wait until it "reset" to capture it.

pi@raspberrypi:~ $ tail -f /var/log/mmdvm/MMDVM_Bridge-2022-01-11.log
I: 2022-01-11 04:54:49.664 YSF, Narrow transmit (72 bit)
M: 2022-01-11 04:54:50.113 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 04:54:50.612 DMR Slot 2, received network end of voice transmission, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 04:54:50.612 YSF, TX state = OFF
M: 2022-01-11 04:55:03.806 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:55:03.806 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:55:03.813 DMR, TX state = ON
I: 2022-01-11 04:55:03.813 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:55:08.312 YSF, received network end of transmission, 4.6 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:55:08.312 DMR, TX state = OFF, DMR frame count was 75 frames
 
 
M: 2022-01-11 04:58:27.893 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:58:27.894 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:58:27.900 DMR, TX state = ON
I: 2022-01-11 04:58:27.900 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:58:31.994 YSF, received network end of transmission, 4.2 seconds, 0% packet loss, BER: 0.4%
M: 2022-01-11 04:58:32.000 DMR, TX state = OFF, DMR frame count was 68 frames
 
 
M: 2022-01-11 04:59:18.097 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:59:18.097 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:59:18.103 DMR, TX state = ON
I: 2022-01-11 04:59:18.103 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:59:23.183 YSF, received network end of transmission, 5.2 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:59:23.189 DMR, TX state = OFF, DMR frame count was 85 frames


And this is the live log with two DMR key-ups, when the bridge hears the DMR it passes audio through to YSF but only until YSF is keyed and then have to wait for it to reset.

pi@raspberrypi:~ $ tail -f /var/log/mmdvm/MMDVM_Bridge-2022-01-11.log
M: 2022-01-11 04:58:27.900 DMR, TX state = ON
I: 2022-01-11 04:58:27.900 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:58:31.994 YSF, received network end of transmission, 4.2 seconds, 0% packet loss, BER: 0.4%
M: 2022-01-11 04:58:32.000 DMR, TX state = OFF, DMR frame count was 68 frames
M: 2022-01-11 04:59:18.097 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:59:18.097 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:59:18.103 DMR, TX state = ON
I: 2022-01-11 04:59:18.103 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:59:23.183 YSF, received network end of transmission, 5.2 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:59:23.189 DMR, TX state = OFF, DMR frame count was 85 frames
 
 
M: 2022-01-11 05:04:24.256 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 05:04:24.256 YSF, TX state = ON
I: 2022-01-11 05:04:24.257 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 05:04:24.268 YSF, Narrow transmit (72 bit)
M: 2022-01-11 05:04:24.737 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 05:04:25.457 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 05:04:26.177 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 05:04:32.055 DMR Slot 2, received network end of voice transmission, 8.0 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 05:04:32.056 YSF, TX state = OFF
 
M: 2022-01-11 05:04:42.344 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 05:04:42.345 YSF, TX state = ON
I: 2022-01-11 05:04:42.346 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 05:04:42.408 YSF, Narrow transmit (72 bit)
M: 2022-01-11 05:04:43.006 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 05:04:43.726 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 05:04:44.447 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 05:04:52.484 DMR Slot 2, received network end of voice transmission, 10.2 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 05:04:52.484 YSF, TX state = OFF
 
So what is it that I am missing?
Any help will be appreciated! 
Thanks, 
Greg AD4GC


Re: Fusion kills the MMDVM Bridge

Greg AD4GC
 

YSFGateway-2022-01-11.log

M: 2022-01-11 03:40:30.892 Opening YSF network connection
I: 2022-01-11 03:40:30.892 Opening UDP port on 4200
M: 2022-01-11 03:40:30.892 Opening YSF network connection
I: 2022-01-11 03:40:30.892 Opening UDP port on 42000
M: 2022-01-11 03:40:30.892 Resolving FCS999 address
M: 2022-01-11 03:40:30.952 Opening FCS network connection
I: 2022-01-11 03:40:30.952 Opening UDP port on 42001
I: 2022-01-11 03:40:30.952 The ID of this repeater is 00000
I: 2022-01-11 03:40:30.960 Loaded 2500 FCS room descriptions
I: 2022-01-11 03:40:30.981 Loaded 1243 YSF reflectors
I: 2022-01-11 03:40:30.981 Loaded YSF parrot
I: 2022-01-11 03:40:31.174 Opening UDP port on 6073
M: 2022-01-11 03:40:31.175 No connection startup
M: 2022-01-11 03:40:31.175 Starting YSFGateway-20200908
M: 2022-01-11 03:40:39.085 Link successful to MMDVM
M: 2022-01-11 03:45:57.194 Opening YSF network connection
I: 2022-01-11 03:45:57.212 Opening UDP port on 4200
M: 2022-01-11 03:45:57.212 Opening YSF network connection
I: 2022-01-11 03:45:57.212 Opening UDP port on 42000
M: 2022-01-11 03:45:57.213 Resolving FCS999 address
M: 2022-01-11 03:45:57.273 Opening FCS network connection
I: 2022-01-11 03:45:57.273 Opening UDP port on 42001
I: 2022-01-11 03:45:57.273 The ID of this repeater is 00000
I: 2022-01-11 03:45:57.309 Loaded 2500 FCS room descriptions
I: 2022-01-11 03:45:57.357 Loaded 1243 YSF reflectors
I: 2022-01-11 03:45:57.358 Loaded YSF parrot
I: 2022-01-11 03:45:57.609 Opening UDP port on 6073
M: 2022-01-11 03:45:57.609 No connection startup
M: 2022-01-11 03:45:57.609 Starting YSFGateway-20200908
M: 2022-01-11 03:46:05.591 Link successful to MMDVM
M: 2022-01-11 03:53:29.632 Opening YSF network connection
I: 2022-01-11 03:53:29.657 Opening UDP port on 4200
M: 2022-01-11 03:53:29.657 Opening YSF network connection
I: 2022-01-11 03:53:29.657 Opening UDP port on 42000
M: 2022-01-11 03:53:29.657 Resolving FCS999 address
M: 2022-01-11 03:53:29.673 Opening FCS network connection
I: 2022-01-11 03:53:29.673 Opening UDP port on 42001
I: 2022-01-11 03:53:29.673 The ID of this repeater is 00000
I: 2022-01-11 03:53:29.713 Loaded 2500 FCS room descriptions
I: 2022-01-11 03:53:29.769 Loaded 1243 YSF reflectors
I: 2022-01-11 03:53:29.770 Loaded YSF parrot
I: 2022-01-11 03:53:30.082 Opening UDP port on 6073
M: 2022-01-11 03:53:30.083 No connection startup
M: 2022-01-11 03:53:30.083 Starting YSFGateway-20200908
 


Re: Fusion kills the MMDVM Bridge

Greg AD4GC
 

MMDVM_Bridge-2022-01-11.log

I: 2022-01-11 03:53:29.458 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2022-01-11 03:53:29.458 This software is for use on amateur radio networks only,
I: 2022-01-11 03:53:29.458 it is to be used for educational purposes only. Its use on
I: 2022-01-11 03:53:29.458 commercial networks is strictly prohibited.
I: 2022-01-11 03:53:29.458 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2022-01-11 03:53:29.458 MMDVM_Bridge-20210520_V1.6.8 is starting
M: 2022-01-11 03:53:29.458 Built 07:13:59 May 28 2021 (GitID #3cfcf23)
I: 2022-01-11 03:53:29.458 General Parameters
I: 2022-01-11 03:53:29.458     Callsign: AD4GC
I: 2022-01-11 03:53:29.458     Id: 315857611
I: 2022-01-11 03:53:29.458     Duplex: no
I: 2022-01-11 03:53:29.458     Timeout: 180s
I: 2022-01-11 03:53:29.459     D-Star: disabled
I: 2022-01-11 03:53:29.459     DMR: enabled
I: 2022-01-11 03:53:29.459     YSF: enabled
I: 2022-01-11 03:53:29.459     P25: disabled
I: 2022-01-11 03:53:29.459     NXDN: disabled
I: 2022-01-11 03:53:29.459 Modem Parameters
I: 2022-01-11 03:53:29.459     Port: /dev/null
I: 2022-01-11 03:53:29.459     RX Invert: no
I: 2022-01-11 03:53:29.459     TX Invert: no
I: 2022-01-11 03:53:29.459     PTT Invert: no
I: 2022-01-11 03:53:29.459     TX Delay: 100ms
I: 2022-01-11 03:53:29.459     RX Offset: 0Hz
I: 2022-01-11 03:53:29.459     TX Offset: 0Hz
I: 2022-01-11 03:53:29.459     RX DC Offset: 0
I: 2022-01-11 03:53:29.459     TX DC Offset: 0
I: 2022-01-11 03:53:29.459     RF Level: 100.0%
I: 2022-01-11 03:53:29.459     DMR Delay: 0 (0.0ms)
I: 2022-01-11 03:53:29.459     RX Level: 50.0%
I: 2022-01-11 03:53:29.460     CW Id TX Level: 50.0%
I: 2022-01-11 03:53:29.460     D-Star TX Level: 50.0%
I: 2022-01-11 03:53:29.460     DMR TX Level: 50.0%
I: 2022-01-11 03:53:29.460     YSF TX Level: 50.0%
I: 2022-01-11 03:53:29.460     P25 TX Level: 50.0%
I: 2022-01-11 03:53:29.460     NXDN TX Level: 50.0%
I: 2022-01-11 03:53:29.460     RX Frequency: 440850000Hz (440850000Hz)
I: 2022-01-11 03:53:29.460     TX Frequency: 440850000Hz (440850000Hz)
M: 2022-01-11 03:53:29.460 Opening the MMDVM
I: 2022-01-11 03:53:29.460 Display Parameters
I: 2022-01-11 03:53:29.460     Type:
I: 2022-01-11 03:53:29.460 DMR Network Parameters
I: 2022-01-11 03:53:29.460     Address: 3102.master.brandmeister.network
I: 2022-01-11 03:53:29.461     Port: 62031
I: 2022-01-11 03:53:29.461     Local: 62032
I: 2022-01-11 03:53:29.461     Jitter: 360ms
I: 2022-01-11 03:53:29.461     Slot 1: disabled
I: 2022-01-11 03:53:29.461     Slot 2: enabled
I: 2022-01-11 03:53:29.461     Mode Hang: 3s
I: 2022-01-11 03:53:29.490 Info Parameters
I: 2022-01-11 03:53:29.490     Callsign: AD4GC
I: 2022-01-11 03:53:29.490     RX Frequency: 440850000Hz
I: 2022-01-11 03:53:29.490     TX Frequency: 440850000Hz
I: 2022-01-11 03:53:29.490     Power: 0W
I: 2022-01-11 03:53:29.490     Latitude: 37.328266deg N
I: 2022-01-11 03:53:29.490     Longitude: -84.523560deg E
I: 2022-01-11 03:53:29.490     Height: 0m
I: 2022-01-11 03:53:29.490     Location: "Bee Lick, KY EM77rh"
I: 2022-01-11 03:53:29.490     Description: "MMDVM_Bridge"
I: 2022-01-11 03:53:29.490     URL: "https://groups.io/g/DVSwitch"
M: 2022-01-11 03:53:29.491 DMR, Opening DMR Network
I: 2022-01-11 03:53:29.491 System Fusion Network Parameters
I: 2022-01-11 03:53:29.491     Local Address: 0
I: 2022-01-11 03:53:29.491     Local Port: 3200
I: 2022-01-11 03:53:29.491     Gateway Address: 192.168.254.2
I: 2022-01-11 03:53:29.491     Gateway Port: 42020
I: 2022-01-11 03:53:29.491     Mode Hang: 3s
M: 2022-01-11 03:53:29.491 Opening YSF network connection
I: 2022-01-11 03:53:29.491 RSSI
I: 2022-01-11 03:53:29.491     Mapping File: /dev/null
I: 2022-01-11 03:53:29.491 Loaded 0 RSSI data mapping points from /dev/null
I: 2022-01-11 03:53:29.491 DMR Id Lookups
I: 2022-01-11 03:53:29.491     File: /var/lib/mmdvm/DMRIds.dat
I: 2022-01-11 03:53:29.491     Reload: 24 hours
I: 2022-01-11 03:53:33.087 Loaded 209729 Ids to the DMR callsign lookup table
I: 2022-01-11 03:53:33.088 DMR RF Parameters
I: 2022-01-11 03:53:33.088 Started the DMR Id lookup reload thread
I: 2022-01-11 03:53:33.088     Id: 315857611
I: 2022-01-11 03:53:33.091     Color Code: 1
I: 2022-01-11 03:53:33.091     Self Only: no
I: 2022-01-11 03:53:33.091     Embedded LC Only: yes
I: 2022-01-11 03:53:33.091     Dump Talker Alias Data: no
I: 2022-01-11 03:53:33.091     Prefixes: 0
I: 2022-01-11 03:53:33.091     Call Hang: 3s
I: 2022-01-11 03:53:33.091     TX Hang: 3s
I: 2022-01-11 03:53:33.091     Mode Hang: 10s
M: 2022-01-11 03:53:33.091 DMR, Opening INI file: DVSwitch.ini
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] address -> 127.0.0.1
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] txPort -> 31100
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] rxPort -> 31103
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] slot -> 2
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] exportTG -> 0
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] hangTimerInFrames -> 0
M: 2022-01-11 03:53:33.093 DMR, Setting [DMR] talkerAlias -> %callsign %location %description
M: 2022-01-11 03:53:33.094 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
I: 2022-01-11 03:53:33.094 YSF RF Parameters
I: 2022-01-11 03:53:33.094     Low Deviation: no
I: 2022-01-11 03:53:33.094     Remote Gateway: no
I: 2022-01-11 03:53:33.094     Self Only: no
I: 2022-01-11 03:53:33.094     DSQ: no
I: 2022-01-11 03:53:33.094     Mode Hang: 10s
M: 2022-01-11 03:53:33.094 YSF, Opening INI file: DVSwitch.ini
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] address -> 127.0.0.1
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] txPort -> 31103
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] rxPort -> 31100
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] txWidePort -> 35105
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] fallbackID -> 3158576
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] exportTG -> 9
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] slot -> 2
M: 2022-01-11 03:53:33.095 YSF, Setting [YSF] RemotePort -> 6073
M: 2022-01-11 03:53:33.096 YSF, Transmitting on 127.0.0.1:31103, and listening on port 31100.  Result = 1
M: 2022-01-11 03:53:33.096 MMDVM_Bridge-20210520_V1.6.8 is running
M: 2022-01-11 03:53:43.236 DMR, Logged into the master successfully: 3102.master.brandmeister.network:62031
M: 2022-01-11 03:53:51.436 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 03:53:51.436 YSF, TX state = ON
I: 2022-01-11 03:53:51.436 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 03:53:51.447 YSF, Narrow transmit (72 bit)
M: 2022-01-11 03:53:51.953 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 03:53:52.611 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 03:53:53.337 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 03:53:54.891 DMR Slot 2, received network end of voice transmission, 3.7 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 03:53:54.891 YSF, TX state = OFF
M: 2022-01-11 03:53:59.513 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 03:53:59.513 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 03:53:59.519 DMR, TX state = ON
I: 2022-01-11 03:53:59.519 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 03:54:04.711 YSF, received network end of transmission, 5.3 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 03:54:04.716 DMR, TX state = OFF, DMR frame count was 87 frames
M: 2022-01-11 04:02:11.368 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 04:02:11.368 YSF, TX state = ON
I: 2022-01-11 04:02:11.368 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 04:02:11.379 YSF, Narrow transmit (72 bit)
M: 2022-01-11 04:02:11.840 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 04:02:12.562 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 04:02:13.281 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 04:02:13.769 DMR Slot 2, received network end of voice transmission, 2.6 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 04:02:13.770 YSF, TX state = OFF
M: 2022-01-11 04:02:23.343 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 04:02:23.343 YSF, TX state = ON
I: 2022-01-11 04:02:23.343 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 04:02:23.463 YSF, Narrow transmit (72 bit)
M: 2022-01-11 04:02:24.001 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 04:02:24.720 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 04:02:25.425 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 04:02:28.066 DMR Slot 2, received network end of voice transmission, 4.8 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 04:02:28.066 YSF, TX state = OFF
M: 2022-01-11 04:02:33.844 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:02:33.845 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:02:33.850 DMR, TX state = ON
I: 2022-01-11 04:02:33.850 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:02:41.451 YSF, received network end of transmission, 7.7 seconds, 0% packet loss, BER: 0.2%
M: 2022-01-11 04:02:41.456 DMR, TX state = OFF, DMR frame count was 127 frames
M: 2022-01-11 04:26:34.682 DMR Slot 2, received network voice header from AD4GC to TG 31219
M: 2022-01-11 04:26:34.682 YSF, TX state = ON
I: 2022-01-11 04:26:34.682 YSF, Begin TX: src=3158576 rpt=0 dst=31219 slot=2 cc=0 metadata=AD4GC
I: 2022-01-11 04:26:34.693 YSF, Narrow transmit (72 bit)
M: 2022-01-11 04:26:35.163 DMR Talker Alias (Data Format 3, Received 3/10 char): 'AD4'
M: 2022-01-11 04:26:35.881 DMR Talker Alias (Data Format 3, Received 6/10 char): 'AD4GC '
M: 2022-01-11 04:26:36.631 DMR Talker Alias (Data Format 3, Received 10/10 char): 'AD4GC Greg'
M: 2022-01-11 04:26:38.503 DMR Slot 2, received network end of voice transmission, 4.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-01-11 04:26:38.503 YSF, TX state = OFF
M: 2022-01-11 04:26:47.538 YSF, received network data from AD4GC      to ALL        at AD4GC
I: 2022-01-11 04:26:47.538 YSF, Lookup call AD4GC returned id 3158577 -> 3158577
M: 2022-01-11 04:26:47.544 DMR, TX state = ON
I: 2022-01-11 04:26:47.544 DMR, Begin TX: src=3158577 rpt=0 dst=9 slot=2 cc=0 metadata=AD4GC
M: 2022-01-11 04:26:52.839 YSF, received network end of transmission, 5.4 seconds, 0% packet loss, BER: 0.3%
M: 2022-01-11 04:26:52.845 DMR, TX state = OFF, DMR frame count was 88 frames
 


Fusion kills the MMDVM Bridge

Greg AD4GC
 

I am trying to build a simple DMR<-->YSF bridge. Both the bridge and reflector are on my network and as far as I know all the required ports have been forwarded and opened. I have followed the wiki to the letter, and shazzam it works! Well at least from DMR --> YSF, as soon as the YSF reflector is keyed the bridge stops working for an unknown amount of time, but after several minutes I can check by keying the DMR and it will pass to YSF again. It doesn't matter how many times or how long DMR is used, as soon as YSF is used it stops for a peiod of time.

If someone would be kind enough to tell me how (what I need to type) to access the live logs to see what is happening, I will be glad to put them in a reply. But here is my MMDVM_Bridge.ini, DVSwitch.ini, and YSFGateway.ini files.

Thanks in advance,
Greg AD4GC

The MMDVM_Bridge.ini:
[General]
Callsign=AD4GC
Id=315857611
Timeout=180
Duplex=0
 
[Info]
RXFrequency=440850000
TXFrequency=440850000
Power=0
Latitude=37.328268
Longitude=-084.52356
Height=0
Location=Bee Lick, KY EM77rh
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=E>
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port=/dev/null
RSSIMappingFile=/dev/null
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=B
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=1
 
[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0
 
[DMR Network]
Enable=1
Address=3102.master.brandmeister.network
Port=62031
Jitter=360
Local=62032
Password=Farming@19
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DM>
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=192.168.254.2
GatewayPort=42020
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


The DVSwitch.ini:
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or you can supply
;   an absolute path in the DVSWITCH environment variable, e.g:
;   DVSWITCH=/etc/MMDVM_Bridge/DVSwitch.ini
;   before executing MMDVM_Bridge
;
; Another method to set the enviorment variable is to use the systemd unit>
; by adding:
; Environment=DVSWITCH=/etc/MMDVM_Bridge/DVSwitch.ini
; to /lib/systemd/system/mmdvm_bridge.service
 
; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <-->>
[QUANTAR]
address = 0.0.0.0               ; Address to send IMBE TLV frames to (expo>
txPort = 34103                  ; Port to send IMBE TLV frames to (export)
rxPort = 34100                  ; Port to listen for IMBE TLV frames on (i>
quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
debug = 0                       ; Debug 0 = off, 1 = on (adds lots of addi>
logLevel = 2                    ; Logging levels, 0=No logging, 1=Debug, 2>
logFilePath = /var/log/dvswitch/Quantar_Bridge.log
 
; Configure the DMR Partner
; Audio format is AMBE 72 bit
[DMR]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (expo>
txPort = 31100                  ; Port to send AMBE TLV frames to (export)
rxPort = 31103                  ; Port to listen on (import)
slot = 2                        ; Export slot
exportTG = 9                    ; Which TG to export
hangTimerInFrames = 0           ; Use 50 for 3 seconds of hang time (3000 >
talkerAlias = %callsign %location %description ; Get callsign location and>
 
; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
[DSTAR]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (expo>
txPort = 32100                  ; Port to send AMBE TLV frames to (export)
rxPort = 32103                  ; Port to listen on (import)
fallbackID = 1234567            ; In case we can not find a valid DMR id i>
exportTG = 9                    ; Which TG to export
slot = 2                        ; Export slot
RemotePort = 54321              ; Port to send Gateway commands to
message = %location %description ; Get location and description from MMDVM>
 
; Configure the NXDN Partner
; Audio format is AMBE 72 bit
[NXDN]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (expo>
txPort = 33100                  ; Port to send AMBE TLV frames to (export)
rxPort = 33103                  ; Port to listen on (import)
fallbackID = 1234567            ; In case we can not find a valid DMR id i>
nxdnFallbackID  = 12345         ; Use this ID when the input DMR ID is not>
translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirec>
slot = 2                        ; Export slot
RemotePort = 6075               ; Port to send Gateway commands to
 
; Configure the P25 Partner
; Audio format is IMBE 88 bit
[P25]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (expo>
txPort = 34100                  ; Port to send AMBE TLV frames to (export)
rxPort = 34103                  ; Port to listen on (import)
slot = 2                        ; Export slot
RemotePort = 6074               ; Port to send Gateway commands to
 
; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
address = 127.0.0.1             ; Address to send AMBE TLV frames to (expo>
txPort = 31103                  ; Port to send AMBE TLV frames to (export)
rxPort = 31100                  ; Port to listen on (import)
txWidePort = 35105              ; Port to send IMBE TLV frames to for YSFw>
fallbackID = 3158576            ; In case we can not find a valid DMR id i>
exportTG = 31219                ; Which TG to export
slot = 2                        ; Export slot
RemotePort = 6073               ; Port to send Gateway commands to
 
; Configure the BrandMeister connection
; Simple Terminal Feature Update
; Audio format is AMBE 72 bit
[STFU]                          ; Brandmeister Open DMR Terminal (ODMRT) P>
BMAddress = 3102.repeater.net   ; Brandmeister ODMRT server address
BMPort = 54006                  ; Brandmeister ODMRT port
BMPassword = passw0rd           ; Your Brandmeister password
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (expo>
txPort  = 36100                 ; Port to send AMBE TLV frames to (export)
rxPort  = 36103                 ; Port to listen on (import)
UserID  = 123456789             ; Your DMR ID + SSID
TalkerAlias = N0CALL Name City  ; Max 27 characters
StartTG = 31219                 ; Startup talk group
LogLevel = 3                    ; STFU log level (0=No logging, 1=Debug, 2>
 
[ASL]
address = 127.0.0.1
txPort = 30100
rxPort = 30103
 
The YSFGateway.ini
[General]
Callsign=AD4GC
Suffix=RPT
# Suffix=ND
Id=315857611
RptAddress=127.0.0.1
RptPort=3200
LocalAddress=127.0.0.1
LocalPort=4200
WiresXMakeUpper=1
WiresXCommandPassthrough=0
Daemon=0
 
[Info]
RXFrequency=223500000
TXFrequency=223500000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg
Description=DVSwitch
URL=https://groups.io/g/DVSwitch
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=E>
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=YSFGateway
 
[aprs.fi]
Enable=0
# Server=noam.aprs2.net
Server=euro.aprs2.net
Port=14580
Password=9999
Description=APRS Description
Suffix=Y
 
[Network]
# Startup=Alabama-Link
InactivityTimeout=0
Revert=0
Debug=0
 
[YSF Network]
Enable=1
Port=42000
Hosts=/var/lib/mmdvm/YSFHosts.txt
ReloadTime=60
ParrotAddress=127.0.0.1
ParrotPort=42012
# YSF2DMRAddress=127.0.0.1
# YSF2DMRPort=42013
# YSF2NXDNAddress=127.0.0.1
# YSF2NXDNPort=42014
# YSF2P25Address=127.0.0.1
# YSF2P25Port=42015
 
[FCS Network]
Enable=1
Rooms=/var/lib/mmdvm/FCSRooms.txt
Port=42001
 
[Mobile GPS]
Enable=0
Address=127.0.0.1
Port=7834
 
[Remote Commands]
Enable=1
Port=6073
 
 
 


moderated Re: DV switch lost status

Steve N4IRS
 

OK,
So, until that feature is implemented and documented, we will just answer, HamVoIP release V1.7.0-01 no longer works with the status tab in DVSwitch Mobile.

Steve N4IRS

On 1/10/22 8:20 AM, David McGough wrote:
Steve & Everyone,

The linkslists were turned off for "phonemode" devices way back in
the rev 456 beta release, which was over a year ago. I'm surprised no
beta testers noticed this issue, since this code was running on many hubs
around the world.

The reason I turned this off was because very long linkslists were
clobbering some phone devices, leaving them unstable! I'll add an option
to turn this back on for users who wish to enable the feature.


73, David KB4FXC


On Mon, 10 Jan 2022, Steve N4IRS wrote:

Does not work for me.

On 1/10/22 7:55 AM, Patrick Perdue wrote:
To fix this, add "telemenabled=255" to your node's stanza.


On 1/10/2022 7:37 AM, Steve N4IRS wrote:
Mike,
This is a HamVoip issue. Something changed on the last update. You
will have to ask on their list.

Steve N4IRS

On 1/10/22 7:21 AM, W3YXZ Mike via groups.io wrote:
When I start DV switch, mobile app and connect to a hub. There's a
list of connected nodes pop up on the screen. Also on the status tab
there should be a list of connected nodes. You can see my phone
connected on bubble chart.







Re: MMDVM Bridge and YSF Reflector don´t talk to each other

Greg AD4GC
 

Uli,

I have been searching how to combine a YSF Reflector and MMDVM Bridge on the same Raspberry Pi. In my ignorance of how most of this works, I attempted to install the MMDVM Bridge on the Pi that I have a working reflector on, only to lose the reflector. Would you be kind enough to tell me how to put both on a single Pi?

Thanks, 
Greg
AD4GC


moderated Re: DV switch lost status

David McGough
 

Steve & Everyone,

The linkslists were turned off for "phonemode" devices way back in
the rev 456 beta release, which was over a year ago. I'm surprised no
beta testers noticed this issue, since this code was running on many hubs
around the world.

The reason I turned this off was because very long linkslists were
clobbering some phone devices, leaving them unstable! I'll add an option
to turn this back on for users who wish to enable the feature.


73, David KB4FXC

On Mon, 10 Jan 2022, Steve N4IRS wrote:

Does not work for me.

On 1/10/22 7:55 AM, Patrick Perdue wrote:

To fix this, add "telemenabled=255" to your node's stanza.


On 1/10/2022 7:37 AM, Steve N4IRS wrote:
Mike,
This is a HamVoip issue. Something changed on the last update. You
will have to ask on their list.

Steve N4IRS

On 1/10/22 7:21 AM, W3YXZ Mike via groups.io wrote:
When I start DV switch, mobile app and connect to a hub. There's a
list of connected nodes pop up on the screen. Also on the status tab
there should be a list of connected nodes. You can see my phone
connected on bubble chart.






moderated Re: DV switch lost status

W3YXZ Mike
 

Thanks


moderated Re: DV switch lost status

Steve N4IRS
 

Does not work for me.

On 1/10/22 7:55 AM, Patrick Perdue wrote:

To fix this, add "telemenabled=255" to your node's stanza.


On 1/10/2022 7:37 AM, Steve N4IRS wrote:
Mike,
This is a HamVoip issue. Something changed on the last update. You will have to ask on their list.

Steve N4IRS

On 1/10/22 7:21 AM, W3YXZ Mike via groups.io wrote:
When I start DV switch, mobile app and connect to a hub. There's a list of connected nodes pop up on the screen. Also on the status tab there should be a list of connected nodes. You can see my phone connected on bubble chart. 


501 - 520 of 10557