Date   

Re: MB <> BM Works fine but EL not talking to it.

Mike KB8JNM
 

So Scott,
You are saying you can hear EL traffic on the connected ASL node ? But not through MMDVM>DMR

And you 'can' also hear ASL though MMDVM>DMR ?


Re: DVSwitch Dashboard

Tom Corcoran
 

Jason … tnx for the suggestion … refresh didn't work at this end. 
--
Tom VE3NY


MB <> BM Works fine but EL not talking to it.

scot forshaw
 

I have reach the stage that

EL/ASL node is working perfectly
MB< - > Brandmeister TG seems to be perfect (Tested with part from HS and remote HT connected to the BM TG and Parrot works as expected)

I cannot however for the life of me work out why Echolink is not pushing to the MB side of the system.

No audio is hitting EL or Allstar from the connected TG.

Could anyone point me to which config file is possibly affecting this?

I an trying to connect the Echolink node to MMDVM_Bridge to get that to take to BM. both parts working in isolation just not sending to each other.

Thank you in advance for any assistance
Scot
2E0WWV


Re: MMDVM Bridge logged in but not showing in Selfcare [solved]

scot forshaw
 

I would like to say this was solved early this morning by using BM HS Security settings pulled from Pi-Star. I was trying to connect to the wrong BM server. I now have HS Security back on and the MMDVM Bridge is communicating with BM perfectly.

I tested with Parrot etc and all seems well.

I have another problem regarding EL <> MB not talking but thats another question


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Eric-K6KWB
 

Its been a while when I made a bridge for FCS realizing I have no DMR connectivity and using two sets of MB looks like this:
YSF reflector<->MB-YSF<->MB_FCS<->YSF gateway and its working!
73, Eric


Re: DVSwitch Dashboard

Tom Corcoran
 

I will give the "refresh" approach a try. 

How about the idea idea of opening a terminal session that displays traffic - like pyUC or DVLink?
--
Tnx .. Tom VE3NY


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Eric-K6KWB
 

Yes Rudy my appologies, I realized you use to two instances of MB for DMRGateway. I'm glad you made it work and thanks Steve N4IRS.
best, 73 Eric


Re: old version of dvswitch

Steve N4IRS
 

Can it be done? I guess so. I don't know what hardware platform you are running on. I don't know how and when you installed the software. As I said, we are working towards a better method of updating.

On 5/17/20 6:57 PM, Kevin Halton wrote:

Steve,  could I just  paste the missing items into the proper directories or do I need to reinstall everything?

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, May 17, 2020 5:49 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] old version of dvswitch

 

Kevin,
I can't tell you there is a "easy way" today to upgrade. There are some changes coming to make upgrades smoother.

Steve

On 5/17/20 4:56 PM, Kevin Halton wrote:

I am running an ol version of Dvswitch, reading some of the latest posts and trying to follow along I realized I am missing YSFgateway, NXDNGateway,and DMRgateway. Is there an easy way to upgrade my current system to the latest without starting all over again?

 

Thanks in advance.

 

 

 



Re: old version of dvswitch

Kevin Halton
 

Steve,  could I just  paste the missing items into the proper directories or do I need to reinstall everything?

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, May 17, 2020 5:49 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] old version of dvswitch

 

Kevin,
I can't tell you there is a "easy way" today to upgrade. There are some changes coming to make upgrades smoother.

Steve

On 5/17/20 4:56 PM, Kevin Halton wrote:

I am running an ol version of Dvswitch, reading some of the latest posts and trying to follow along I realized I am missing YSFgateway, NXDNGateway,and DMRgateway. Is there an easy way to upgrade my current system to the latest without starting all over again?

 

Thanks in advance.

 

 

 


Re: old version of dvswitch

Steve N4IRS
 

Kevin,
I can't tell you there is a "easy way" today to upgrade. There are some changes coming to make upgrades smoother.

Steve

On 5/17/20 4:56 PM, Kevin Halton wrote:

I am running an ol version of Dvswitch, reading some of the latest posts and trying to follow along I realized I am missing YSFgateway, NXDNGateway,and DMRgateway. Is there an easy way to upgrade my current system to the latest without starting all over again?

 

Thanks in advance.

 

 



old version of dvswitch

Kevin Halton
 

I am running an ol version of Dvswitch, reading some of the latest posts and trying to follow along I realized I am missing YSFgateway, NXDNGateway,and DMRgateway. Is there an easy way to upgrade my current system to the latest without starting all over again?

 

Thanks in advance.

 

 

_._,_._,_


Re: MMDVM Bridge logged in but not showing in Selfcare

Steve N4IRS
 

Scot,
If I had to guess, and I do since you are not posting enough of your log to see the callsign and DMR ID used to login to BM. I would guess a typo in either one of the fields.

Steve N4IRS

On 5/17/20 2:57 PM, scot forshaw wrote:
Hi, 
I have setup ALS MB AB as per https://4x5mg.net/2018/07/16/allstar-to-dmr-bridge/ and tried to trouble shoot using several variations...

Everything looks to be working as MMDVM_Bridge reports it has logged in correctly etc etc 

M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully

Similarly AB output is exactly the same as the examples in https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit 

Allstar is linking, Echolink is linking, the EL and ALS nodes work and I can connect tot hem via EL and even repeaters etc etc ...

It just does not show up in BM selfceare no matter what I have tried. 

Opened all the PORTS, shutdown my Pi-Star not he same LAN.

I feel that everything is there, can anyone help me understand why it is not appearing in BM so I can assign the TG ?

Many thanks in advance

Scot 2E0WWV

















M: 2020-05-17 18:50:13.131 DMR, Opening DMR Network
I: 2020-05-17 18:50:13.131 RSSI
I: 2020-05-17 18:50:13.131     Mapping File: RSSI.dat
W: 2020-05-17 18:50:13.132 Cannot open the RSSI data file - RSSI.dat
I: 2020-05-17 18:50:13.132 DMR Id Lookups
I: 2020-05-17 18:50:13.132     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-05-17 18:50:13.132     Reload: 24 hours
I: 2020-05-17 18:50:14.032 Loaded 164586 Ids to the DMR callsign lookup table
I: 2020-05-17 18:50:14.032 Started the DMR Id lookup reload thread
I: 2020-05-17 18:50:14.032 DMR RF Parameters
I: 2020-05-17 18:50:14.032     Id: 234785705
I: 2020-05-17 18:50:14.032     Color Code: 1
I: 2020-05-17 18:50:14.032     Self Only: no
I: 2020-05-17 18:50:14.032     Embedded LC Only: yes
I: 2020-05-17 18:50:14.032     Dump Talker Alias Data: no
I: 2020-05-17 18:50:14.033     Prefixes: 0
I: 2020-05-17 18:50:14.033     Call Hang: 3s
I: 2020-05-17 18:50:14.033     TX Hang: 3s
I: 2020-05-17 18:50:14.033     Mode Hang: 10s
M: 2020-05-17 18:50:14.033 DMR, Opening INI file: DVSwitch.ini
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] TXPort -> 31100
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] RXPort -> 31103
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Slot -> 2
M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully


MMDVM Bridge logged in but not showing in Selfcare

scot forshaw
 

Hi, 
I have setup ALS MB AB as per https://4x5mg.net/2018/07/16/allstar-to-dmr-bridge/ and tried to trouble shoot using several variations...

Everything looks to be working as MMDVM_Bridge reports it has logged in correctly etc etc 

M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully

Similarly AB output is exactly the same as the examples in https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit 

Allstar is linking, Echolink is linking, the EL and ALS nodes work and I can connect tot hem via EL and even repeaters etc etc ...

It just does not show up in BM selfceare no matter what I have tried. 

Opened all the PORTS, shutdown my Pi-Star not he same LAN.

I feel that everything is there, can anyone help me understand why it is not appearing in BM so I can assign the TG ?

Many thanks in advance

Scot 2E0WWV

















M: 2020-05-17 18:50:13.131 DMR, Opening DMR Network
I: 2020-05-17 18:50:13.131 RSSI
I: 2020-05-17 18:50:13.131     Mapping File: RSSI.dat
W: 2020-05-17 18:50:13.132 Cannot open the RSSI data file - RSSI.dat
I: 2020-05-17 18:50:13.132 DMR Id Lookups
I: 2020-05-17 18:50:13.132     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-05-17 18:50:13.132     Reload: 24 hours
I: 2020-05-17 18:50:14.032 Loaded 164586 Ids to the DMR callsign lookup table
I: 2020-05-17 18:50:14.032 Started the DMR Id lookup reload thread
I: 2020-05-17 18:50:14.032 DMR RF Parameters
I: 2020-05-17 18:50:14.032     Id: 234785705
I: 2020-05-17 18:50:14.032     Color Code: 1
I: 2020-05-17 18:50:14.032     Self Only: no
I: 2020-05-17 18:50:14.032     Embedded LC Only: yes
I: 2020-05-17 18:50:14.032     Dump Talker Alias Data: no
I: 2020-05-17 18:50:14.033     Prefixes: 0
I: 2020-05-17 18:50:14.033     Call Hang: 3s
I: 2020-05-17 18:50:14.033     TX Hang: 3s
I: 2020-05-17 18:50:14.033     Mode Hang: 10s
M: 2020-05-17 18:50:14.033 DMR, Opening INI file: DVSwitch.ini
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] TXPort -> 31100
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] RXPort -> 31103
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Slot -> 2
M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Rudy N6DOZ
 
Edited

Kevin,

The ports would have to cross, yes. Here's that segment in my working DVSwitch.ini

DVSwitch.ini
 
[DMR]
Address = 127.0.0.1             
TXPort = 34100                  
RXPort = 34103                  
Slot = 2                      
                   
 
[YSF]
Address = 127.0.0.1             
;Address = 45.77.186.5          
TXPort = 34103                  
RXPort = 34100                  
FallbackID = 3135404            
ExportTG = 311620               
Slot = 2                       


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Kevin Halton
 

Jumping in here, I want to make certain I understand. In dvswitch.ini  dmr is 31100 TX and 31103 RX and YSF is 35100 TX and 35103 RX. So I would change ysf RX to 31100 and ysf TX to 31103 ? Make any TG / Reflector changes and restart?

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, May 17, 2020 11:41 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

 

Correct. Cross connect YSF to DMR in DVSwitch.ini TX to RX RX to TX

On 5/17/20 11:39 AM, Rudy N6DOZ wrote:

I'll reconstruct the chain as such.

BM <-> MB <-> YSFGateway <-> FCS Reflector

 

 


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Rudy N6DOZ
 
Edited

 
 
 
Steve, thanks a ton :) Got it working!
 
BM <-> MB <-> YSFGateway <-> FCS Reflector
 
Here's are ini snips so folks can refer to it (with just the important parts).
 
 
MMDVM_Bridge.ini
 
[General]
Callsign=N6DOZ
Id=315069220
Timeout=180
Duplex=0
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge-DMX
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=1
 
[DMR Network] ; to DMR
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Password=passw0rd
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=62045
GatewayAddress=127.0.0.1
GatewayPort=62046
Debug=0
 
 
 
DVSwitch.ini
 
[DMR]
Address = 127.0.0.1             
TXPort = 34100                  
RXPort = 34103                  
Slot = 2                      
                  
 
[YSF]
Address = 127.0.0.1              
TXPort = 34103                  
RXPort = 34100                  
FallbackID = 3135404            
ExportTG = 311620               
Slot = 2                        
 
 
YSFGateway.ini
 
[General]
Callsign=N6DOZ
#Suffix=RPT
# Suffix=ND
Id=3150692
RptAddress=127.0.0.1
RptPort=62045
LocalAddress=127.0.0.1
LocalPort=62046
Daemon=0
 
[Network]
Startup=FCS00457
InactivityTimeout=10
Revert=1
Debug=0
 
[FCS Network]
Enable=1
Rooms=/var/lib/mmdvm/FCSRooms.txt
Port=42002     

# Port=42002 - Make sure this doesn't run into a YSFReflector or XLXReflector running on the same machine
 


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Steve N4IRS
 

Correct. Cross connect YSF to DMR in DVSwitch.ini TX to RX RX to TX

On 5/17/20 11:39 AM, Rudy N6DOZ wrote:

I'll reconstruct the chain as such.

BM <-> MB <-> YSFGateway <-> FCS Reflector

 


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Rudy N6DOZ
 

I'll reconstruct the chain as such.

BM <-> MB <-> YSFGateway <-> FCS Reflector

 


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Steve N4IRS
 

[General]
Callsign=N0CALL
Id=1234567
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
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=C

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=1

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=hblink.dvswitch.org
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# 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=127.0.0.1
GatewayPort=4200
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


Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge

Steve N4IRS
 

1: What is segfaulting?
2: show me the ini file NOT the log
3: DMR to YSF should look like this (only one instance of MB is needed)

BM <-> MB <-> YSFGateway <-> FCS Reflector

On 5/17/20 11:09 AM, Rudy N6DOZ wrote:

Setup is BM-TG <->MB_BM<->MB_YSF<->YSF Gateway<->FCS00457

 

 

MB_YSF:


I: 2020-05-17 15:06:03.798 General Parameters

I: 2020-05-17 15:06:03.798     Callsign: N6DOZ

I: 2020-05-17 15:06:03.798     Id: 3150692

I: 2020-05-17 15:06:03.798     Duplex: no

I: 2020-05-17 15:06:03.798     Timeout: 180s

I: 2020-05-17 15:06:03.798     DMR: enabled

I: 2020-05-17 15:06:03.798     YSF: disabled

I: 2020-05-17 15:06:03.798 Modem Parameters

I: 2020-05-17 15:06:03.798     Port: /dev/null

I: 2020-05-17 15:06:03.798     RX Invert: no

I: 2020-05-17 15:06:03.798     TX Invert: no

I: 2020-05-17 15:06:03.798     PTT Invert: no

I: 2020-05-17 15:06:03.798     TX Delay: 100ms

I: 2020-05-17 15:06:03.798     RX Offset: 0Hz

I: 2020-05-17 15:06:03.798     TX Offset: 0Hz

I: 2020-05-17 15:06:03.798     RX DC Offset: 0

I: 2020-05-17 15:06:03.798     TX DC Offset: 0

I: 2020-05-17 15:06:03.798     RF Level: 100.0%

I: 2020-05-17 15:06:03.798     DMR Delay: 0 (0.0ms)

I: 2020-05-17 15:06:03.798     RX Level: 50.0%

I: 2020-05-17 15:06:03.798     CW Id TX Level: 50.0%

I: 2020-05-17 15:06:03.798     D-Star TX Level: 50.0%

I: 2020-05-17 15:06:03.798     DMR TX Level: 50.0%

I: 2020-05-17 15:06:03.798     YSF TX Level: 50.0%

I: 2020-05-17 15:06:03.798     P25 TX Level: 50.0%

I: 2020-05-17 15:06:03.798     NXDN TX Level: 50.0%

I: 2020-05-17 15:06:03.798     RX Frequency: 432100000Hz (432100000Hz)

I: 2020-05-17 15:06:03.798     TX Frequency: 432100100Hz (432100100Hz)

M: 2020-05-17 15:06:03.798 Opening the MMDVM

I: 2020-05-17 15:06:03.798 Display Parameters

I: 2020-05-17 15:06:03.798     Type: 

I: 2020-05-17 15:06:03.798 RSSI

I: 2020-05-17 15:06:03.798     Mapping File: RSSI.dat

W: 2020-05-17 15:06:03.798 Cannot open the RSSI data file - RSSI.dat

I: 2020-05-17 15:06:03.798 DMR Id Lookups

I: 2020-05-17 15:06:03.798     File: /var/lib/mmdvm/DMRIds.dat

I: 2020-05-17 15:06:03.798     Reload: 24 hours

I: 2020-05-17 15:06:03.961 Loaded 162402 Ids to the DMR callsign lookup table

I: 2020-05-17 15:06:03.961 DMR RF Parameters

I: 2020-05-17 15:06:03.961     Id: 3150692

I: 2020-05-17 15:06:03.961     Color Code: 1

I: 2020-05-17 15:06:03.961     Self Only: no

I: 2020-05-17 15:06:03.961     Embedded LC Only: yes

I: 2020-05-17 15:06:03.961     Dump Talker Alias Data: no

I: 2020-05-17 15:06:03.961     Prefixes: 0

I: 2020-05-17 15:06:03.961     Call Hang: 4s

I: 2020-05-17 15:06:03.961     TX Hang: 4s

I: 2020-05-17 15:06:03.961     Mode Hang: 10s

M: 2020-05-17 15:06:03.961 DMR, Opening INI file: DVSwitch.ini

M: 2020-05-17 15:06:03.962 DMR, Setting [DMR] Address -> 127.0.0.1

M: 2020-05-17 15:06:03.962 DMR, Setting [DMR] TXPort -> 34103

M: 2020-05-17 15:06:03.962 DMR, Setting [DMR] RXPort -> 34100

M: 2020-05-17 15:06:03.962 DMR, Setting [DMR] Slot -> 2

M: 2020-05-17 15:06:03.962 DMR, Transmitting on 127.0.0.1:34103, and listening on port 34100.  Result = 1

M: 2020-05-17 15:06:03.962 MMDVM_Bridge-20200309_V1.5.1 is running

I: 2020-05-17 15:06:03.962 Started the DMR Id lookup reload thread

M: 2020-05-17 15:07:38.478 DMR, TX state = ON

I: 2020-05-17 15:07:38.478 DMR, Begin TX: src=3135404 rpt=0 dst=311620 slot=1 cc=0 metadata=N6DOZ

Segmentation fault (core dumped)

 

 

MB_BM

I: 2020-05-17 14:58:01.577 General Parameters

I: 2020-05-17 14:58:01.577     Callsign: N6DOZ

I: 2020-05-17 14:58:01.577     Id: 315069220

I: 2020-05-17 14:58:01.578     Duplex: no

I: 2020-05-17 14:58:01.578     Timeout: 180s

I: 2020-05-17 14:58:01.578     D-Star: disabled

I: 2020-05-17 14:58:01.578     DMR: enabled

I: 2020-05-17 14:58:01.578     YSF: disabled

I: 2020-05-17 14:58:01.578     P25: disabled

I: 2020-05-17 14:58:01.578     NXDN: disabled

I: 2020-05-17 14:58:01.578 Modem Parameters

I: 2020-05-17 14:58:01.578     Port: /dev/null

I: 2020-05-17 14:58:01.578     RX Invert: no

I: 2020-05-17 14:58:01.578     TX Invert: no

I: 2020-05-17 14:58:01.578     PTT Invert: no

I: 2020-05-17 14:58:01.578     TX Delay: 100ms

I: 2020-05-17 14:58:01.578     RX Offset: 0Hz

I: 2020-05-17 14:58:01.578     TX Offset: 0Hz

I: 2020-05-17 14:58:01.578     RX DC Offset: 0

I: 2020-05-17 14:58:01.578     TX DC Offset: 0

I: 2020-05-17 14:58:01.578     RF Level: 100.0%

I: 2020-05-17 14:58:01.578     DMR Delay: 0 (0.0ms)

I: 2020-05-17 14:58:01.579     RX Level: 50.0%

I: 2020-05-17 14:58:01.579     CW Id TX Level: 50.0%

I: 2020-05-17 14:58:01.579     D-Star TX Level: 50.0%

I: 2020-05-17 14:58:01.579     DMR TX Level: 50.0%

I: 2020-05-17 14:58:01.579     YSF TX Level: 50.0%

I: 2020-05-17 14:58:01.579     P25 TX Level: 50.0%

I: 2020-05-17 14:58:01.579     NXDN TX Level: 50.0%

I: 2020-05-17 14:58:01.579     RX Frequency: 432100000Hz (432100000Hz)

I: 2020-05-17 14:58:01.579     TX Frequency: 432100100Hz (432100100Hz)

M: 2020-05-17 14:58:01.580 Opening the MMDVM

I: 2020-05-17 14:58:01.580 Display Parameters

I: 2020-05-17 14:58:01.580     Type: 

I: 2020-05-17 14:58:01.580 DMR Network Parameters

I: 2020-05-17 14:58:01.580     Address: 3102.repeater.net

I: 2020-05-17 14:58:01.580     Port: 62031

I: 2020-05-17 14:58:01.580     Local: random

I: 2020-05-17 14:58:01.580     Jitter: 750ms

I: 2020-05-17 14:58:01.580     Slot 1: disabled

I: 2020-05-17 14:58:01.581     Slot 2: enabled

I: 2020-05-17 14:58:01.581     Mode Hang: 3s

I: 2020-05-17 14:58:01.582 Info Parameters

I: 2020-05-17 14:58:01.582     Callsign: N6DOZ

I: 2020-05-17 14:58:01.582     RX Frequency: 432100000Hz

I: 2020-05-17 14:58:01.582     TX Frequency: 432100100Hz

I: 2020-05-17 14:58:01.582     Power: 1W

I: 2020-05-17 14:58:01.583     Latitude: 37.654202deg N

I: 2020-05-17 14:58:01.583     Longitude: -122.429802deg E

I: 2020-05-17 14:58:01.583     Height: 16m

I: 2020-05-17 14:58:01.583     Location: "South San Francisco, CA USA"

I: 2020-05-17 14:58:01.583     Description: "FCS_MMDVM_BRIDGE"

I: 2020-05-17 14:58:01.583     URL: "http://www.kapihan.net"

M: 2020-05-17 14:58:01.583 DMR, Opening DMR Network

I: 2020-05-17 14:58:01.583 RSSI

I: 2020-05-17 14:58:01.583     Mapping File: RSSI.dat

W: 2020-05-17 14:58:01.583 Cannot open the RSSI data file - RSSI.dat

I: 2020-05-17 14:58:01.583 DMR Id Lookups

I: 2020-05-17 14:58:01.583     File: /var/lib/mmdvm/DMRIds.dat

I: 2020-05-17 14:58:01.583     Reload: 24 hours

I: 2020-05-17 14:58:01.754 Loaded 162402 Ids to the DMR callsign lookup table

I: 2020-05-17 14:58:01.755 DMR RF Parameters

I: 2020-05-17 14:58:01.755     Id: 315069220

I: 2020-05-17 14:58:01.755     Color Code: 1

I: 2020-05-17 14:58:01.755     Self Only: no

I: 2020-05-17 14:58:01.755     Embedded LC Only: yes

I: 2020-05-17 14:58:01.755     Dump Talker Alias Data: no

I: 2020-05-17 14:58:01.755     Prefixes: 0

I: 2020-05-17 14:58:01.755     Call Hang: 3s

I: 2020-05-17 14:58:01.755     TX Hang: 3s

I: 2020-05-17 14:58:01.755     Mode Hang: 10s

M: 2020-05-17 14:58:01.755 DMR, Opening INI file: DVSwitch.ini

I: 2020-05-17 14:58:01.756 Started the DMR Id lookup reload thread

M: 2020-05-17 14:58:01.756 DMR, Setting [DMR] Address -> 127.0.0.1

M: 2020-05-17 14:58:01.756 DMR, Setting [DMR] TXPort -> 34100

M: 2020-05-17 14:58:01.756 DMR, Setting [DMR] RXPort -> 34103

M: 2020-05-17 14:58:01.756 DMR, Setting [DMR] Slot -> 1

M: 2020-05-17 14:58:01.756 DMR, Transmitting on 127.0.0.1:34100, and listening on port 34103.  Result = 1

M: 2020-05-17 14:58:01.756 MMDVM_Bridge-20200309_V1.5.1 is running

D: 2020-05-17 14:58:11.801 DMR, Sending authorisation

D: 2020-05-17 14:58:11.847 DMR, Sending configuration

M: 2020-05-17 14:58:11.898 DMR, Logged into the master successfully

M: 2020-05-17 15:07:38.473 DMR Slot 2, received network late entry from N6DOZ to TG 311620

M: 2020-05-17 15:07:39.069 DMR Talker Alias (Data Format 1, Received 6/10 char): 'N6DOZ '

M: 2020-05-17 15:07:39.791 DMR Talker Alias (Data Format 1, Received 10/10 char): 'N6DOZ Rudy'

M: 2020-05-17 15:07:39.911 DMR Slot 2, received network end of voice transmission, 1.6 seconds, 0% packet loss, BER: 0.0%


YSFGateway

M: 2020-05-17 15:04:46.058 Opening YSF network connection

I: 2020-05-17 15:04:46.058 Opening UDP port on 62046

M: 2020-05-17 15:04:46.058 Resolving FCS00x addresses

M: 2020-05-17 15:04:46.060 Opening FCS network connection

I: 2020-05-17 15:04:46.060 Opening UDP port on 42002

I: 2020-05-17 15:04:46.060 The ID of this repeater is 00000

I: 2020-05-17 15:04:46.061 Loaded 800 FCS room descriptions

I: 2020-05-17 15:04:46.061 Loaded 825 YSF reflectors

I: 2020-05-17 15:04:46.061 Loaded YSF parrot

M: 2020-05-17 15:04:46.064 Automatic (re-)connection to FCS00457

M: 2020-05-17 15:04:46.065 Starting YSFGateway-20200405

 

M: 2020-05-17 15:04:46.223 Linked to FCS004-57