Date   

Re: Setting up a YSFn <--> ASL bridge

Steve KC1AWV
 

You can ignore the Vagrant stuff if you're not using Vagrant. I use Vagrant to spin up test machines when dealing with other distributions that are not Debian.

On Mon, Jun 10, 2019 at 5:05 PM Brett.williams via Groups.Io <Brett.williams=sss.gov@groups.io> wrote:
Steve, base on the ASL to DMR script you sent me for the I'm stuck at the line " vagrant init "  also, running a x86 machine and the -MMDVM Bridge file say  AMD64, will that be an issue ? 

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// 

DVSwitch Centos Test (In Vagrant test box, on Arch Linux dev system)

 

 

 

Create Vagrant test box

 

 

 

$ mkdir dvswitch-centos-test

 

$ cd dvswitch-centos-test

 

$ vagrant init

 

$ pico Vagrantfile

 

 

 

Change line 15 to read

 

config.vm.box = "bento/centos-7.6"

 

 

 

Save and exit

 

 

 

$ vagrant up

 

 

 

Wait for box to boot

 

 

 

$ vagrant ssh

 

 

 

---- Inside Test Box ----

 

 

 

$ sudo su

 

# yum update

 

# yum install epel-release

 

# yum groupinstall "Development Tools"

 

# yum install jq perl-Digest-SHA glibc-static

 

# cd /opt

 

# git clone https://github.com/DVSwitch/Analog_Bridge.git

 

# git clone https://github.com/DVSwitch/MMDVM_Bridge.git

 

 

 

--Analog Bridge--

 

 

 

# cd Analog_Bridge

 

# cp bin/Analog_Bridge.amd64 Analog_Bridge

 

 

 

--MMDVM Bridge--

 

 

 

# cd MMDVM_Bridge

 

# cp bin/MMDVM_Bridge.amd64 MMDVM_Bridge

 

 

 

--md380-emu for x86_64--

 

 

 

# git clone https://github.com/kc1awv/md380tools.git

 

# cd md380tools/emulator

 

# make

 

# mkdir /opt/md380-emu

 

# cp md380-emu /opt/md380-emu

 

 

 

 

 

--Build G4KLX Programs--

 

 

 

-DMRGateway- (if needed)

 

 

 

# cd /usr/src

 

# git clone https://github.com/g4klx/DMRGateway.git

 

# cd DMRGateway

 

# make

 

# mkdir /opt/DMRGateway

 

# cp -R Audio /opt/DMRGateway

 

# cp DMRGateway.ini /opt/DMRGateway

 

# cp DMRGateway /opt/DMRGateway

 

 

 

--Get BOTH DMR ID Scripts--

 

 

 

-DMRIdUpdate.sh - for MMDVM-

 

# cd /usr/src

 

# wget https://raw.githubusercontent.com/DVSwitch/DVSwitch-System-Builder/master/Directories/usr/local/sbin/DMRIDUpdate.sh

 

# mv DMRIDUpdate.sh /usr/local/sbin

 

 

 

-DMRIDUpdateBM.sh - for Analog_Bridge-

 

# cd /usr/src

 

# wget https://raw.githubusercontent.com/DVSwitch/DVSwitch-System-Builder/master/Directories/usr/local/sbin/DMRIDUpdateBM.sh

 

# mv DMRIDUpdateBM.sh /usr/local/sbin

 

 

 

-Create directories for scripts to put data into-

 

# mkdir -p /var/lib/mmdvm

 

# mkdir -p /var/lib/dvswitch

 

 

 

-Create directories for programs to write logs to-

 

# mkdir -p /var/log/mmdvm

 

# mkdir -p /var/log/dvswitch

 

 

 

-cron the ID update scripts-

 

# ln -s /usr/local/sbin/DMRIDUpdate.sh /etc/cron.daily

 

# ln -s /usr/local/sbin/DMRIDUpdateBM.sh /etc/cron.daily

 

 

 

--Create systemd scripts--

 

Use your favorite editor, I use nano/pico.

 

 

 

# yum install nano

 

 

 

# nano /lib/systemd/system/analog_bridge.service

 

 

 

[Unit]

 

Description=Analog_Bridge Service

 

# Description=Place this file in /lib/systemd/system

 

# Description=N4IRS 04/20/2018

 

 

 

# The device name should point to the

 

# port the mmdvm is plugged into.

 

# For USB ports (Arduino Due)

 

# BindTo=dev-ttyACM0.device

 

#

 

# To make the network-online.target available

 

# systemctl enable systemd-networkd-wait-online.service

 

 

 

After=network-online.target syslog.target

 

Wants=network-online.target

 

 

 

[Service]

 

Type=simple

 

StandardOutput=null

 

WorkingDirectory=/opt/Analog_Bridge

 

Environment=AnalogBridgeLogDir=/var/log/dvswitch

 

# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib

 

Restart=always

 

RestartSec=3

 

ExecStart=/opt/Analog_Bridge/Analog_Bridge /opt/Analog_Bridge/Analog_Bridge.ini

 

ExecReload=/bin/kill -2 $MAINPID

 

KillMode=process

 

 

 

[Install]

 

WantedBy=multi-user.target

 

 

 

# nano /lib/systemd/system/mmdvm_bridge.service

 

 

 

[Unit]

 

Description=MMDVM_Bridge Service

 

# Description=Place this file in /lib/systemd/system

 

# Description=N4IRS 04/20/2018

 

 

 

# The device name should point to the

 

# port the mmdvm is plugged into.

 

# For USB ports (Arduino Due)

 

# BindTo=dev-ttyACM0.device

 

#

 

# To make the network-online.target available

 

# systemctl enable systemd-networkd-wait-online.service

 

 

 

After=network-online.target syslog.target

 

Wants=network-online.target

 

 

 

[Service]

 

StandardOutput=null

 

WorkingDirectory=/opt/MMDVM_Bridge

 

RestartSec=3

 

ExecStart=/opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

 

Restart=on-abort

 

 

 

[Install]

 

WantedBy=multi-user.target

 

 

 

-Reload systemd-

 

# systemctl daemon-reload

 

# systemctl start analog_bridge

 

# systemctl start mmdvm_bridge

 



--
Steve Miller
KC1AWV


Re: Setting up a YSFn <--> ASL bridge

Brett KB5YZB
 

Steve, base on the ASL to DMR script you sent me for the I'm stuck at the line " vagrant init "  also, running a x86 machine and the -MMDVM Bridge file say  AMD64, will that be an issue ? 

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// 

DVSwitch Centos Test (In Vagrant test box, on Arch Linux dev system)

 

 

 

Create Vagrant test box

 

 

 

$ mkdir dvswitch-centos-test

 

$ cd dvswitch-centos-test

 

$ vagrant init

 

$ pico Vagrantfile

 

 

 

Change line 15 to read

 

config.vm.box = "bento/centos-7.6"

 

 

 

Save and exit

 

 

 

$ vagrant up

 

 

 

Wait for box to boot

 

 

 

$ vagrant ssh

 

 

 

---- Inside Test Box ----

 

 

 

$ sudo su

 

# yum update

 

# yum install epel-release

 

# yum groupinstall "Development Tools"

 

# yum install jq perl-Digest-SHA glibc-static

 

# cd /opt

 

# git clone https://github.com/DVSwitch/Analog_Bridge.git

 

# git clone https://github.com/DVSwitch/MMDVM_Bridge.git

 

 

 

--Analog Bridge--

 

 

 

# cd Analog_Bridge

 

# cp bin/Analog_Bridge.amd64 Analog_Bridge

 

 

 

--MMDVM Bridge--

 

 

 

# cd MMDVM_Bridge

 

# cp bin/MMDVM_Bridge.amd64 MMDVM_Bridge

 

 

 

--md380-emu for x86_64--

 

 

 

# git clone https://github.com/kc1awv/md380tools.git

 

# cd md380tools/emulator

 

# make

 

# mkdir /opt/md380-emu

 

# cp md380-emu /opt/md380-emu

 

 

 

 

 

--Build G4KLX Programs--

 

 

 

-DMRGateway- (if needed)

 

 

 

# cd /usr/src

 

# git clone https://github.com/g4klx/DMRGateway.git

 

# cd DMRGateway

 

# make

 

# mkdir /opt/DMRGateway

 

# cp -R Audio /opt/DMRGateway

 

# cp DMRGateway.ini /opt/DMRGateway

 

# cp DMRGateway /opt/DMRGateway

 

 

 

--Get BOTH DMR ID Scripts--

 

 

 

-DMRIdUpdate.sh - for MMDVM-

 

# cd /usr/src

 

# wget https://raw.githubusercontent.com/DVSwitch/DVSwitch-System-Builder/master/Directories/usr/local/sbin/DMRIDUpdate.sh

 

# mv DMRIDUpdate.sh /usr/local/sbin

 

 

 

-DMRIDUpdateBM.sh - for Analog_Bridge-

 

# cd /usr/src

 

# wget https://raw.githubusercontent.com/DVSwitch/DVSwitch-System-Builder/master/Directories/usr/local/sbin/DMRIDUpdateBM.sh

 

# mv DMRIDUpdateBM.sh /usr/local/sbin

 

 

 

-Create directories for scripts to put data into-

 

# mkdir -p /var/lib/mmdvm

 

# mkdir -p /var/lib/dvswitch

 

 

 

-Create directories for programs to write logs to-

 

# mkdir -p /var/log/mmdvm

 

# mkdir -p /var/log/dvswitch

 

 

 

-cron the ID update scripts-

 

# ln -s /usr/local/sbin/DMRIDUpdate.sh /etc/cron.daily

 

# ln -s /usr/local/sbin/DMRIDUpdateBM.sh /etc/cron.daily

 

 

 

--Create systemd scripts--

 

Use your favorite editor, I use nano/pico.

 

 

 

# yum install nano

 

 

 

# nano /lib/systemd/system/analog_bridge.service

 

 

 

[Unit]

 

Description=Analog_Bridge Service

 

# Description=Place this file in /lib/systemd/system

 

# Description=N4IRS 04/20/2018

 

 

 

# The device name should point to the

 

# port the mmdvm is plugged into.

 

# For USB ports (Arduino Due)

 

# BindTo=dev-ttyACM0.device

 

#

 

# To make the network-online.target available

 

# systemctl enable systemd-networkd-wait-online.service

 

 

 

After=network-online.target syslog.target

 

Wants=network-online.target

 

 

 

[Service]

 

Type=simple

 

StandardOutput=null

 

WorkingDirectory=/opt/Analog_Bridge

 

Environment=AnalogBridgeLogDir=/var/log/dvswitch

 

# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib

 

Restart=always

 

RestartSec=3

 

ExecStart=/opt/Analog_Bridge/Analog_Bridge /opt/Analog_Bridge/Analog_Bridge.ini

 

ExecReload=/bin/kill -2 $MAINPID

 

KillMode=process

 

 

 

[Install]

 

WantedBy=multi-user.target

 

 

 

# nano /lib/systemd/system/mmdvm_bridge.service

 

 

 

[Unit]

 

Description=MMDVM_Bridge Service

 

# Description=Place this file in /lib/systemd/system

 

# Description=N4IRS 04/20/2018

 

 

 

# The device name should point to the

 

# port the mmdvm is plugged into.

 

# For USB ports (Arduino Due)

 

# BindTo=dev-ttyACM0.device

 

#

 

# To make the network-online.target available

 

# systemctl enable systemd-networkd-wait-online.service

 

 

 

After=network-online.target syslog.target

 

Wants=network-online.target

 

 

 

[Service]

 

StandardOutput=null

 

WorkingDirectory=/opt/MMDVM_Bridge

 

RestartSec=3

 

ExecStart=/opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

 

Restart=on-abort

 

 

 

[Install]

 

WantedBy=multi-user.target

 

 

 

-Reload systemd-

 

# systemctl daemon-reload

 

# systemctl start analog_bridge

 

# systemctl start mmdvm_bridge

 


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

OK,

Let's start over. Show me the complete:

Analog_Bridge.ini

MMDVM_Bridge.ini

DVSwitch.ini

Stop MMDVM_Bridge

Delete the MMDVM_Bridge log

Start MMDVM_Bridge

Show the complete MMDVM_Bridge log.

Steve

On 6/10/19 2:56 PM, Tom Corcoran wrote:
Tnx for specific guidance Steve …. however, still no connections ..

Log now reads:

System Fusion Network Parameters
I: 2019-06-10 18:42:35.212     Local Address: 0
I: 2019-06-10 18:42:35.212     Local Port: 3200
I: 2019-06-10 18:42:35.212     Gateway Address: 144.217.241.23
I: 2019-06-10 18:42:35.212     Gateway Port: 42100
I: 2019-06-10 18:42:35.212     Mode Hang: 3s
M: 2019-06-10 18:42:35.212 Opening YSF network connection
I: 2019-06-10 18:42:35.212 RSSI
I: 2019-06-10 18:42:35.212     Mapping File: RSSI.dat
W: 2019-06-10 18:42:35.212 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-10 18:42:35.212 DMR Id Lookups
I: 2019-06-10 18:42:35.212     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-10 18:42:35.212     Reload: 24 hours
I: 2019-06-10 18:42:35.475 Loaded 135612 Ids to the DMR callsign lookup table
I: 2019-06-10 18:42:35.475 YSF RF Parameters
I: 2019-06-10 18:42:35.475     Low Deviation: no
I: 2019-06-10 18:42:35.475     Remote Gateway: no
I: 2019-06-10 18:42:35.475     Self Only: no
I: 2019-06-10 18:42:35.475     DSQ: no
I: 2019-06-10 18:42:35.475     Mode Hang: 10s
M: 2019-06-10 18:42:35.475 YSF, Opening INI file: DVSwitch.ini
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] TXPort -> 31103
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] RXPort -> 31100
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 18:42:35.479 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2019-06-10 18:42:35.479 MMDVM_Bridge-20180423 is running
I: 2019-06-10 18:42:35.479 Started the DMR Id lookup reload thread


DVSwitch.ini
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; 35100  Port to send AMBE TLV frames to (export)
RXPort = 31100                  ; 35103  Port to listen on (import)
FallbackID = 3112488            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 77353                ; Canada Which TG to export
Slot = 2                        ; Export slot

Analog_Bridge.ini

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103   ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31100   ;  AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3023284                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 302328401                  ; ID of source repeater
txTg = 77353                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames



--
Tom VE3NY


Re: Setting up a YSFn <--> ASL bridge

Steve KC1AWV
 
Edited

***EDIT - I got your ports mixed up.***

In Analog_Bridge.ini try changing
 
fromDMRPort = 31103
toDMRPort = 31100
 
to
 
txPort = 31100
rxPort = 31103
 
Steve KC1AWV

On Mon, Jun 10, 2019 at 2:56 PM Tom Corcoran <tcorcoran@...> wrote:
Tnx for specific guidance Steve …. however, still no connections ..

Log now reads:

System Fusion Network Parameters
I: 2019-06-10 18:42:35.212     Local Address: 0
I: 2019-06-10 18:42:35.212     Local Port: 3200
I: 2019-06-10 18:42:35.212     Gateway Address: 144.217.241.23
I: 2019-06-10 18:42:35.212     Gateway Port: 42100
I: 2019-06-10 18:42:35.212     Mode Hang: 3s
M: 2019-06-10 18:42:35.212 Opening YSF network connection
I: 2019-06-10 18:42:35.212 RSSI
I: 2019-06-10 18:42:35.212     Mapping File: RSSI.dat
W: 2019-06-10 18:42:35.212 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-10 18:42:35.212 DMR Id Lookups
I: 2019-06-10 18:42:35.212     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-10 18:42:35.212     Reload: 24 hours
I: 2019-06-10 18:42:35.475 Loaded 135612 Ids to the DMR callsign lookup table
I: 2019-06-10 18:42:35.475 YSF RF Parameters
I: 2019-06-10 18:42:35.475     Low Deviation: no
I: 2019-06-10 18:42:35.475     Remote Gateway: no
I: 2019-06-10 18:42:35.475     Self Only: no
I: 2019-06-10 18:42:35.475     DSQ: no
I: 2019-06-10 18:42:35.475     Mode Hang: 10s
M: 2019-06-10 18:42:35.475 YSF, Opening INI file: DVSwitch.ini
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] TXPort -> 31103
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] RXPort -> 31100
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 18:42:35.479 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2019-06-10 18:42:35.479 MMDVM_Bridge-20180423 is running
I: 2019-06-10 18:42:35.479 Started the DMR Id lookup reload thread


DVSwitch.ini
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; 35100  Port to send AMBE TLV frames to (export)
RXPort = 31100                  ; 35103  Port to listen on (import)
FallbackID = 3112488            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 77353                ; Canada Which TG to export
Slot = 2                        ; Export slot

Analog_Bridge.ini

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103   ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31100   ;  AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3023284                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 302328401                  ; ID of source repeater
txTg = 77353                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames



--
Tom VE3NY

 

 



--
Steve Miller
KC1AWV


Re: Setting up a YSFn <--> ASL bridge

Tom Corcoran
 

Tnx for specific guidance Steve …. however, still no connections ..

Log now reads:

System Fusion Network Parameters
I: 2019-06-10 18:42:35.212     Local Address: 0
I: 2019-06-10 18:42:35.212     Local Port: 3200
I: 2019-06-10 18:42:35.212     Gateway Address: 144.217.241.23
I: 2019-06-10 18:42:35.212     Gateway Port: 42100
I: 2019-06-10 18:42:35.212     Mode Hang: 3s
M: 2019-06-10 18:42:35.212 Opening YSF network connection
I: 2019-06-10 18:42:35.212 RSSI
I: 2019-06-10 18:42:35.212     Mapping File: RSSI.dat
W: 2019-06-10 18:42:35.212 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-10 18:42:35.212 DMR Id Lookups
I: 2019-06-10 18:42:35.212     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-10 18:42:35.212     Reload: 24 hours
I: 2019-06-10 18:42:35.475 Loaded 135612 Ids to the DMR callsign lookup table
I: 2019-06-10 18:42:35.475 YSF RF Parameters
I: 2019-06-10 18:42:35.475     Low Deviation: no
I: 2019-06-10 18:42:35.475     Remote Gateway: no
I: 2019-06-10 18:42:35.475     Self Only: no
I: 2019-06-10 18:42:35.475     DSQ: no
I: 2019-06-10 18:42:35.475     Mode Hang: 10s
M: 2019-06-10 18:42:35.475 YSF, Opening INI file: DVSwitch.ini
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] TXPort -> 31103
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] RXPort -> 31100
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 18:42:35.479 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 18:42:35.479 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2019-06-10 18:42:35.479 MMDVM_Bridge-20180423 is running
I: 2019-06-10 18:42:35.479 Started the DMR Id lookup reload thread


DVSwitch.ini
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; 35100  Port to send AMBE TLV frames to (export)
RXPort = 31100                  ; 35103  Port to listen on (import)
FallbackID = 3112488            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 77353                ; Canada Which TG to export
Slot = 2                        ; Export slot

Analog_Bridge.ini

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103   ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31100   ;  AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3023284                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 302328401                  ; ID of source repeater
txTg = 77353                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames



--
Tom VE3NY


Re: Installing DVSwitch programs apt-get install vs github

Frank Decuire
 

Steve 

Thanks for the quick response,


Frank
K6fed 


On Jun 10, 2019, at 10:40 AM, Steve N4IRS <szingman@...> wrote:

It is the first topic in the message section: <https://dvswitch.groups.io/g/main/topic/updated_dvswitch_repository/18971786?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,18971786>

On 6/10/2019 1:38 PM, Don WB5EKU wrote:
I would like that info also. 
Thanks
Don
WB5EKU

On Mon, Jun 10, 2019, 10:32 AM Frank Decuire via Groups.Io <k6fed=yahoo.com@groups.io> wrote:
Steve,
Where can if find the location for the DVSwitch app repository? I’m still new to the DVSwitch program would like to make sure the apps l install are coming from the right resources.


Thanks

Frank K6FED 


Sent from Yahoo Mail for iPad

On Monday, June 10, 2019, 7:56 AM, Steve N4IRS <szingman@...> wrote:

I have been told there is some confusion about where to install some of the DVSwitch programs from. Since there are the apt packages and github, which to choose?
Always install from the apt repository. The apt repository not only installs the program, it installs and required OS programs. It creates the directory structure of logging and data. It sets up systemd so the program starts at boot.

Github is used to provide a place for us to upload a new version of the executable BEFORE I make a new package. If there is a bug fix we are testing, it will go on github first. If you want to try the new executable, backup your existing executable and replace it from github. If it does not work, restore the old executable. Not really rocket science.

Steve N4IRS


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

On 6/10/2019 2:13 PM, Tom Corcoran wrote:
Hello Steve,

I did send both mmdvm and analog bridge ini files earlier in this thread. Actually, only sent the parts i thought were relevant. send entire file?
--
Tom VE3NY


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

Sorry,
I should have looked. Here is what I see:

Analog_Bridge.ini
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103                ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31100                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW

*** DVSwitch.ini

[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)

I have only posted the relevant entries. In short:
Analog_Bridge is listening on Port 31103 for traffic but MMDVM_Bridge is sending on port 35100
MMDVM_Bridge is listening on Port 35103 for traffic but Analog_Bridge is sending on port 31100

73, Steve N4IRS


On 6/10/2019 2:13 PM, Tom Corcoran wrote:
Hello Steve,

I did send both mmdvm and analog bridge ini files earlier in this thread. Actually, only sent the parts i thought were relevant. send entire file?
--
Tom VE3NY


Re: Setting up a YSFn <--> ASL bridge

Tom Corcoran
 

Hello Steve,

I did send both mmdvm and analog bridge ini files earlier in this thread. Actually, only sent the parts i thought were relevant. send entire file?
--
Tom VE3NY


Re: Installing DVSwitch programs apt-get install vs github

 

Thanks
73
WB5EKU

On Mon, Jun 10, 2019, 10:40 AM Steve N4IRS <szingman@...> wrote:
It is the first topic in the message section: <https://dvswitch.groups.io/g/main/topic/updated_dvswitch_repository/18971786?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,18971786>

On 6/10/2019 1:38 PM, Don WB5EKU wrote:
I would like that info also. 
Thanks
Don
WB5EKU

On Mon, Jun 10, 2019, 10:32 AM Frank Decuire via Groups.Io <k6fed=yahoo.com@groups.io> wrote:
Steve,
Where can if find the location for the DVSwitch app repository? I’m still new to the DVSwitch program would like to make sure the apps l install are coming from the right resources.


Thanks

Frank K6FED 


Sent from Yahoo Mail for iPad

On Monday, June 10, 2019, 7:56 AM, Steve N4IRS <szingman@...> wrote:

I have been told there is some confusion about where to install some of the DVSwitch programs from. Since there are the apt packages and github, which to choose?
Always install from the apt repository. The apt repository not only installs the program, it installs and required OS programs. It creates the directory structure of logging and data. It sets up systemd so the program starts at boot.

Github is used to provide a place for us to upload a new version of the executable BEFORE I make a new package. If there is a bug fix we are testing, it will go on github first. If you want to try the new executable, backup your existing executable and replace it from github. If it does not work, restore the old executable. Not really rocket science.

Steve N4IRS


How does MMDVM bridge fit into a DV bridge?

Steve N4IRS
 

MMDVM_Bridge (MB) does most of the heavy lifting required to build a bridge. In fact it IS the bridge. The job of MB is to connect to a foreign network and produce a data stream that can be sent to another program like Analog_Bridge or even back to MB for transmission to another foreign network. Let's consider a simple YSF to DMR bridge.

YSF Reflector <-> MMDVM_Bridge <-> BrandMeister (BM)

It does not get any simpler then that. MB connects to both the YSF Reflector and BM. No gateways needed, very simple. This is a singe instance of MB. What do I mean by single instance? One copy of MB is running.
MB uses 2 configuration files. One file configures MB for connecting to the foreign network(s) The second file configures MB to send the data to another program or back to MB itself. Let's start with configuring MB to connect to the foreign networks. The file is MMDVM_Bridge.ini I will only show the [stanzas] that really matter and only the fields.

MMDVM_Bridge.ini

[DMR]
Enable=1

[System Fusion]
Enable=1

The above 2 stanzas simply enable the DMR and YSF modes in MB

[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Password=passw0rd

[System Fusion Network]
Enable=1
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166

The above 2 stanzas enable and configure the foreign network connections required for the bridge.
Now let's look at DVSwitch.ini

[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)

[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)

In the DMR stanza above, traffic coming from the DMR network, in this case, BM is processed by MB and sent out UDP port 31100 to IP address 127.0.0.1 (local host or the machine running MB) Traffic received on UDP port 31103 is processed and sent out to the DMR network. In the YSF stanza above, traffic coming from the YSF reflector is processed by MB and sent out UDP port 35100 to IP address 127.0.0.1 Traffic received on UDP port 35103 is processed and sent out to the YSF Reflector.

OK, so how do we bridge DMR to YSF? Do we need another program? Are we finished? No to all. What we want is when traffic is received from BM it is sent to YSF and vice versa. What we need to do, is send the traffic right back into MB.

DVSwitch.ini
[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)

[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)

Again,
Traffic coming in from BM is received by MB processed and sent out UDP port 31100 to IP address 127.0.0.1 (local host or the machine running MB) If you look at the TXPort for DMR it matches the RXPort for YSF. The TXPort for YSF matches the RXPort for DMR.
Let me present it a different way:

[DMR]                     YSF
Address = 127.0.0.1 <---> Address = 127.0.0.1
TXPort = 31100 <--------> RXPort = 31100
RXPort = 31103 <--------> TXPort = 31103

That is all there is to it. If there is any magic, it's in what happens to the data received from the foreign network. MB takes apart the data and "normalizes" it so that another DVSwitch program can use it. That DVSwitch program can be Analog_Bridge or even MB itself. MB can process 5 foreign networks at the same time. What MB can NOT do is to process 2 of the same foreign networks at the same time. For that, you need a second instance of MB.

Hope this helps.

73, Steve N4IRS


Re: Installing DVSwitch programs apt-get install vs github

Steve N4IRS
 

On 6/10/2019 1:38 PM, Don WB5EKU wrote:
I would like that info also. 
Thanks
Don
WB5EKU

On Mon, Jun 10, 2019, 10:32 AM Frank Decuire via Groups.Io <k6fed=yahoo.com@groups.io> wrote:
Steve,
Where can if find the location for the DVSwitch app repository? I’m still new to the DVSwitch program would like to make sure the apps l install are coming from the right resources.


Thanks

Frank K6FED 


Sent from Yahoo Mail for iPad

On Monday, June 10, 2019, 7:56 AM, Steve N4IRS <szingman@...> wrote:

I have been told there is some confusion about where to install some of the DVSwitch programs from. Since there are the apt packages and github, which to choose?
Always install from the apt repository. The apt repository not only installs the program, it installs and required OS programs. It creates the directory structure of logging and data. It sets up systemd so the program starts at boot.

Github is used to provide a place for us to upload a new version of the executable BEFORE I make a new package. If there is a bug fix we are testing, it will go on github first. If you want to try the new executable, backup your existing executable and replace it from github. If it does not work, restore the old executable. Not really rocket science.

Steve N4IRS


Re: Installing DVSwitch programs apt-get install vs github

Steve N4IRS
 

Frank,
This will install the repo to your Debian based system:

To install the repository:
As root
cd /tmp

wget http://dvswitch.org/install-dvswitch-repo
chmod +x install-dvswitch-repo
./install-dvswitch-repo
 apt-get update

The repository is visible at <http://dvswitch.org/ASL_Repository/>

Since I still host the ASL repo the directory structure is shared.

73, Steve N4IRS


On 6/10/2019 1:32 PM, Frank Decuire via Groups.Io wrote:
Steve,
Where can if find the location for the DVSwitch app repository? I’m still new to the DVSwitch program would like to make sure the apps l install are coming from the right resources.


Thanks

Frank K6FED 


Sent from Yahoo Mail for iPad

On Monday, June 10, 2019, 7:56 AM, Steve N4IRS <szingman@...> wrote:

I have been told there is some confusion about where to install some of the DVSwitch programs from. Since there are the apt packages and github, which to choose?
Always install from the apt repository. The apt repository not only installs the program, it installs and required OS programs. It creates the directory structure of logging and data. It sets up systemd so the program starts at boot.

Github is used to provide a place for us to upload a new version of the executable BEFORE I make a new package. If there is a bug fix we are testing, it will go on github first. If you want to try the new executable, backup your existing executable and replace it from github. If it does not work, restore the old executable. Not really rocket science.

Steve N4IRS


Re: Installing DVSwitch programs apt-get install vs github

 

I would like that info also. 
Thanks
Don
WB5EKU

On Mon, Jun 10, 2019, 10:32 AM Frank Decuire via Groups.Io <k6fed=yahoo.com@groups.io> wrote:
Steve,
Where can if find the location for the DVSwitch app repository? I’m still new to the DVSwitch program would like to make sure the apps l install are coming from the right resources.


Thanks

Frank K6FED 


Sent from Yahoo Mail for iPad

On Monday, June 10, 2019, 7:56 AM, Steve N4IRS <szingman@...> wrote:

I have been told there is some confusion about where to install some of the DVSwitch programs from. Since there are the apt packages and github, which to choose?
Always install from the apt repository. The apt repository not only installs the program, it installs and required OS programs. It creates the directory structure of logging and data. It sets up systemd so the program starts at boot.

Github is used to provide a place for us to upload a new version of the executable BEFORE I make a new package. If there is a bug fix we are testing, it will go on github first. If you want to try the new executable, backup your existing executable and replace it from github. If it does not work, restore the old executable. Not really rocket science.

Steve N4IRS


Re: Installing DVSwitch programs apt-get install vs github

Frank Decuire
 

Steve,
Where can if find the location for the DVSwitch app repository? I’m still new to the DVSwitch program would like to make sure the apps l install are coming from the right resources.


Thanks

Frank K6FED 

On Monday, June 10, 2019, 7:56 AM, Steve N4IRS <szingman@...> wrote:

I have been told there is some confusion about where to install some of the DVSwitch programs from. Since there are the apt packages and github, which to choose?
Always install from the apt repository. The apt repository not only installs the program, it installs and required OS programs. It creates the directory structure of logging and data. It sets up systemd so the program starts at boot.

Github is used to provide a place for us to upload a new version of the executable BEFORE I make a new package. If there is a bug fix we are testing, it will go on github first. If you want to try the new executable, backup your existing executable and replace it from github. If it does not work, restore the old executable. Not really rocket science.

Steve N4IRS


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

Since you are troubleshooting ASL <-> YSF please include your Analog_Bridge.ini

Steve

On 6/10/2019 12:34 PM, Tom Corcoran wrote:
I did notice this from earlier today
--
Tom VE3NY

(Partial MMDVM log dump)

I: 2019-06-10 12:02:36.438 YSF RF Parameters
I: 2019-06-10 12:02:36.438     Low Deviation: no
I: 2019-06-10 12:02:36.438     Remote Gateway: no
I: 2019-06-10 12:02:36.438     Self Only: no
I: 2019-06-10 12:02:36.438     DSQ: no
I: 2019-06-10 12:02:36.438     Mode Hang: 10s
M: 2019-06-10 12:02:36.438 YSF, Opening INI file: DVSwitch.ini
I: 2019-06-10 12:02:36.438 Started the DMR Id lookup reload thread
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] TXPort -> 35100
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] RXPort -> 35103
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 12:02:36.438 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
M: 2019-06-10 12:02:36.438 MMDVM_Bridge-20180423 is running
M: 2019-06-10 12:05:18.182 YSF, received network data from VE6LK      to ALL        at VE2DMR   
I: 2019-06-10 12:05:18.182 YSF, Lookup call VE6LK returned id 3026207 -> 3026207
M: 2019-06-10 12:05:18.912 YSF, received network end of transmission, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-10 12:05:28.135 YSF, received network data from VE3ERQ     to ALL        at VE2DMR   
I: 2019-06-10 12:05:28.135 YSF, Lookup call VE3ERQ returned id 3023150 -> 3023150
M: 2019-06-10 12:05:28.900 YSF, received network end of transmission, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-10 12:10:39.513 Closing the MMDVM
I: 2019-06-10 12:10:40.485 Stopped the DMR Id lookup reload thread
M: 2019-06-10 12:10:40.485 Closing YSF network connection
I: 2019-06-10 12:10:40.485 MMDVM_Bridge-20180423 exited on receipt of SIGTERM


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

Tom,
The top of the log file reports the settings as seen by MMDVM_Bridge it helps to show it.
To save a back and forth, also post your MMDVM_Bridge.ini

Steve N4IRS

On 6/10/2019 12:34 PM, Tom Corcoran wrote:
I did notice this from earlier today
--
Tom VE3NY

(Partial MMDVM log dump)

I: 2019-06-10 12:02:36.438 YSF RF Parameters
I: 2019-06-10 12:02:36.438     Low Deviation: no
I: 2019-06-10 12:02:36.438     Remote Gateway: no
I: 2019-06-10 12:02:36.438     Self Only: no
I: 2019-06-10 12:02:36.438     DSQ: no
I: 2019-06-10 12:02:36.438     Mode Hang: 10s
M: 2019-06-10 12:02:36.438 YSF, Opening INI file: DVSwitch.ini
I: 2019-06-10 12:02:36.438 Started the DMR Id lookup reload thread
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] TXPort -> 35100
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] RXPort -> 35103
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 12:02:36.438 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
M: 2019-06-10 12:02:36.438 MMDVM_Bridge-20180423 is running
M: 2019-06-10 12:05:18.182 YSF, received network data from VE6LK      to ALL        at VE2DMR   
I: 2019-06-10 12:05:18.182 YSF, Lookup call VE6LK returned id 3026207 -> 3026207
M: 2019-06-10 12:05:18.912 YSF, received network end of transmission, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-10 12:05:28.135 YSF, received network data from VE3ERQ     to ALL        at VE2DMR   
I: 2019-06-10 12:05:28.135 YSF, Lookup call VE3ERQ returned id 3023150 -> 3023150
M: 2019-06-10 12:05:28.900 YSF, received network end of transmission, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-10 12:10:39.513 Closing the MMDVM
I: 2019-06-10 12:10:40.485 Stopped the DMR Id lookup reload thread
M: 2019-06-10 12:10:40.485 Closing YSF network connection
I: 2019-06-10 12:10:40.485 MMDVM_Bridge-20180423 exited on receipt of SIGTERM


Re: Setting up a YSFn <--> ASL bridge

Tom Corcoran
 

I did notice this from earlier today
--
Tom VE3NY

(Partial MMDVM log dump)

I: 2019-06-10 12:02:36.438 YSF RF Parameters
I: 2019-06-10 12:02:36.438     Low Deviation: no
I: 2019-06-10 12:02:36.438     Remote Gateway: no
I: 2019-06-10 12:02:36.438     Self Only: no
I: 2019-06-10 12:02:36.438     DSQ: no
I: 2019-06-10 12:02:36.438     Mode Hang: 10s
M: 2019-06-10 12:02:36.438 YSF, Opening INI file: DVSwitch.ini
I: 2019-06-10 12:02:36.438 Started the DMR Id lookup reload thread
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] TXPort -> 35100
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] RXPort -> 35103
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 12:02:36.438 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 12:02:36.438 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
M: 2019-06-10 12:02:36.438 MMDVM_Bridge-20180423 is running
M: 2019-06-10 12:05:18.182 YSF, received network data from VE6LK      to ALL        at VE2DMR   
I: 2019-06-10 12:05:18.182 YSF, Lookup call VE6LK returned id 3026207 -> 3026207
M: 2019-06-10 12:05:18.912 YSF, received network end of transmission, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-10 12:05:28.135 YSF, received network data from VE3ERQ     to ALL        at VE2DMR   
I: 2019-06-10 12:05:28.135 YSF, Lookup call VE3ERQ returned id 3023150 -> 3023150
M: 2019-06-10 12:05:28.900 YSF, received network end of transmission, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-10 12:10:39.513 Closing the MMDVM
I: 2019-06-10 12:10:40.485 Stopped the DMR Id lookup reload thread
M: 2019-06-10 12:10:40.485 Closing YSF network connection
I: 2019-06-10 12:10:40.485 MMDVM_Bridge-20180423 exited on receipt of SIGTERM


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

Tom,
For me, I like a small clean log when I troubleshoot. In the case of MMDVM_Bridge, I stop the bridge. I delete the log file. I run one test and then I stop MMDVM_Bridge. You should have a pretty clean log to troubleshoot from.
I notice this in your log:
I: 2019-06-10 16:17:30.977     Gateway Address: 144.217.241.23    ; 96.47.95.121 ysfreflector.dvswitch.org

I don't THINK MMDVM_Bridge likes "; " as a comment. I would put anything you want to save for later on a new line by it self proceded by a pound "#"
It may be nothing, but it removes all doubt.

Steve N4IRS

On 6/10/2019 12:23 PM, Tom Corcoran wrote:
Steve/Steve,

If there is another way to share log files here, tell me. The AB log is humungus so didn't post it (yet).
--
Tom VE3NY

I: 2019-06-10 16:17:30.975 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-06-10 16:17:30.975 This software is for use on amateur radio networks only,
I: 2019-06-10 16:17:30.975 it is to be used for educational purposes only. Its use on
I: 2019-06-10 16:17:30.975 commercial networks is strictly prohibited.
I: 2019-06-10 16:17:30.975 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-06-10 16:17:30.975 MMDVM_Bridge-20180423 is starting
M: 2019-06-10 16:17:30.975 Built 13:54:43 May 30 2018 (GitID #9cdea41)
I: 2019-06-10 16:17:30.975 General Parameters
I: 2019-06-10 16:17:30.975     Callsign: VE3NY
I: 2019-06-10 16:17:30.975     Id: 3023284
I: 2019-06-10 16:17:30.975     Duplex: no
I: 2019-06-10 16:17:30.975     Timeout: 180s
I: 2019-06-10 16:17:30.975     D-Star: disabled
I: 2019-06-10 16:17:30.975     DMR: disabled
I: 2019-06-10 16:17:30.975     YSF: enabled
I: 2019-06-10 16:17:30.975     P25: disabled
I: 2019-06-10 16:17:30.975     NXDN: disabled
I: 2019-06-10 16:17:30.975 Modem Parameters
I: 2019-06-10 16:17:30.975     Port: /dev/null
I: 2019-06-10 16:17:30.975     RX Invert: no
I: 2019-06-10 16:17:30.975     TX Invert: no
I: 2019-06-10 16:17:30.975     PTT Invert: no
I: 2019-06-10 16:17:30.975     TX Delay: 100ms
I: 2019-06-10 16:17:30.975     RX Offset: 0Hz
I: 2019-06-10 16:17:30.975     TX Offset: 0Hz
I: 2019-06-10 16:17:30.975     RX DC Offset: 0
I: 2019-06-10 16:17:30.975     TX DC Offset: 0
I: 2019-06-10 16:17:30.975     RF Level: 100.0%
I: 2019-06-10 16:17:30.975     DMR Delay: 0 (0.0ms)
I: 2019-06-10 16:17:30.975     RX Level: 50.0%
I: 2019-06-10 16:17:30.975     CW Id TX Level: 50.0%
I: 2019-06-10 16:17:30.975     D-Star TX Level: 50.0%
I: 2019-06-10 16:17:30.975     DMR TX Level: 50.0%
I: 2019-06-10 16:17:30.975     YSF TX Level: 50.0%
I: 2019-06-10 16:17:30.975     P25 TX Level: 50.0%
I: 2019-06-10 16:17:30.975     NXDN TX Level: 50.0%
I: 2019-06-10 16:17:30.975     RX Frequency: 434000000Hz (434000000Hz)
I: 2019-06-10 16:17:30.975     TX Frequency: 434000000Hz (434000000Hz)
M: 2019-06-10 16:17:30.977 Opening the MMDVM
I: 2019-06-10 16:17:30.977 Display Parameters
I: 2019-06-10 16:17:30.977     Type:
I: 2019-06-10 16:17:30.977 System Fusion Network Parameters
I: 2019-06-10 16:17:30.977     Local Address: 0
I: 2019-06-10 16:17:30.977     Local Port: 3200
I: 2019-06-10 16:17:30.977     Gateway Address: 144.217.241.23    ; 96.47.95.121 ysfreflector.dvswitch.org
I: 2019-06-10 16:17:30.977     Gateway Port: 42100
I: 2019-06-10 16:17:30.977     Mode Hang: 3s
M: 2019-06-10 16:17:30.977 Opening YSF network connection
I: 2019-06-10 16:17:30.977 RSSI
I: 2019-06-10 16:17:30.977     Mapping File: RSSI.dat
W: 2019-06-10 16:17:30.977 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-10 16:17:30.977 DMR Id Lookups
I: 2019-06-10 16:17:30.977     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-10 16:17:30.977     Reload: 24 hours
I: 2019-06-10 16:17:31.200 Loaded 135612 Ids to the DMR callsign lookup table
I: 2019-06-10 16:17:31.200 YSF RF Parameters
I: 2019-06-10 16:17:31.200     Low Deviation: no
I: 2019-06-10 16:17:31.200     Remote Gateway: no
I: 2019-06-10 16:17:31.200     Self Only: no
I: 2019-06-10 16:17:31.200     DSQ: no
I: 2019-06-10 16:17:31.200     Mode Hang: 10s
M: 2019-06-10 16:17:31.200 YSF, Opening INI file: DVSwitch.ini
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] TXPort -> 35100
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] RXPort -> 35103
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 16:17:31.202 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
M: 2019-06-10 16:17:31.202 MMDVM_Bridge-20180423 is running
I: 2019-06-10 16:17:31.205 Started the DMR Id lookup reload thread


Re: Setting up a YSFn <--> ASL bridge

Tom Corcoran
 

Steve/Steve,

If there is another way to share log files here, tell me. The AB log is humungus so didn't post it (yet).
--
Tom VE3NY

I: 2019-06-10 16:17:30.975 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-06-10 16:17:30.975 This software is for use on amateur radio networks only,
I: 2019-06-10 16:17:30.975 it is to be used for educational purposes only. Its use on
I: 2019-06-10 16:17:30.975 commercial networks is strictly prohibited.
I: 2019-06-10 16:17:30.975 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-06-10 16:17:30.975 MMDVM_Bridge-20180423 is starting
M: 2019-06-10 16:17:30.975 Built 13:54:43 May 30 2018 (GitID #9cdea41)
I: 2019-06-10 16:17:30.975 General Parameters
I: 2019-06-10 16:17:30.975     Callsign: VE3NY
I: 2019-06-10 16:17:30.975     Id: 3023284
I: 2019-06-10 16:17:30.975     Duplex: no
I: 2019-06-10 16:17:30.975     Timeout: 180s
I: 2019-06-10 16:17:30.975     D-Star: disabled
I: 2019-06-10 16:17:30.975     DMR: disabled
I: 2019-06-10 16:17:30.975     YSF: enabled
I: 2019-06-10 16:17:30.975     P25: disabled
I: 2019-06-10 16:17:30.975     NXDN: disabled
I: 2019-06-10 16:17:30.975 Modem Parameters
I: 2019-06-10 16:17:30.975     Port: /dev/null
I: 2019-06-10 16:17:30.975     RX Invert: no
I: 2019-06-10 16:17:30.975     TX Invert: no
I: 2019-06-10 16:17:30.975     PTT Invert: no
I: 2019-06-10 16:17:30.975     TX Delay: 100ms
I: 2019-06-10 16:17:30.975     RX Offset: 0Hz
I: 2019-06-10 16:17:30.975     TX Offset: 0Hz
I: 2019-06-10 16:17:30.975     RX DC Offset: 0
I: 2019-06-10 16:17:30.975     TX DC Offset: 0
I: 2019-06-10 16:17:30.975     RF Level: 100.0%
I: 2019-06-10 16:17:30.975     DMR Delay: 0 (0.0ms)
I: 2019-06-10 16:17:30.975     RX Level: 50.0%
I: 2019-06-10 16:17:30.975     CW Id TX Level: 50.0%
I: 2019-06-10 16:17:30.975     D-Star TX Level: 50.0%
I: 2019-06-10 16:17:30.975     DMR TX Level: 50.0%
I: 2019-06-10 16:17:30.975     YSF TX Level: 50.0%
I: 2019-06-10 16:17:30.975     P25 TX Level: 50.0%
I: 2019-06-10 16:17:30.975     NXDN TX Level: 50.0%
I: 2019-06-10 16:17:30.975     RX Frequency: 434000000Hz (434000000Hz)
I: 2019-06-10 16:17:30.975     TX Frequency: 434000000Hz (434000000Hz)
M: 2019-06-10 16:17:30.977 Opening the MMDVM
I: 2019-06-10 16:17:30.977 Display Parameters
I: 2019-06-10 16:17:30.977     Type:
I: 2019-06-10 16:17:30.977 System Fusion Network Parameters
I: 2019-06-10 16:17:30.977     Local Address: 0
I: 2019-06-10 16:17:30.977     Local Port: 3200
I: 2019-06-10 16:17:30.977     Gateway Address: 144.217.241.23    ; 96.47.95.121 ysfreflector.dvswitch.org
I: 2019-06-10 16:17:30.977     Gateway Port: 42100
I: 2019-06-10 16:17:30.977     Mode Hang: 3s
M: 2019-06-10 16:17:30.977 Opening YSF network connection
I: 2019-06-10 16:17:30.977 RSSI
I: 2019-06-10 16:17:30.977     Mapping File: RSSI.dat
W: 2019-06-10 16:17:30.977 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-10 16:17:30.977 DMR Id Lookups
I: 2019-06-10 16:17:30.977     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-10 16:17:30.977     Reload: 24 hours
I: 2019-06-10 16:17:31.200 Loaded 135612 Ids to the DMR callsign lookup table
I: 2019-06-10 16:17:31.200 YSF RF Parameters
I: 2019-06-10 16:17:31.200     Low Deviation: no
I: 2019-06-10 16:17:31.200     Remote Gateway: no
I: 2019-06-10 16:17:31.200     Self Only: no
I: 2019-06-10 16:17:31.200     DSQ: no
I: 2019-06-10 16:17:31.200     Mode Hang: 10s
M: 2019-06-10 16:17:31.200 YSF, Opening INI file: DVSwitch.ini
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] TXPort -> 35100
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] RXPort -> 35103
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] ExportTG -> 77353
M: 2019-06-10 16:17:31.202 YSF, Setting [YSF] Slot -> 2
M: 2019-06-10 16:17:31.202 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
M: 2019-06-10 16:17:31.202 MMDVM_Bridge-20180423 is running
I: 2019-06-10 16:17:31.205 Started the DMR Id lookup reload thread

5041 - 5060 of 9081