Date   

Re: DVSwitch Dashboard

Jason - WY7JT
 

It does have a bug I've been meaning to investigate. But a work around is to refresh it when someone is transmitting and it will populate the rest of the dashboard. At least that works consistently here. 

Jason - WY7JT



On Sun, May 17, 2020 at 4:41 AM Steve N4IRS <szingman@...> wrote:
The dashboard is on my ever expanding todo list.

Steve

On 5/16/20 10:27 PM, Tom Corcoran wrote:

have anyone installed a dashboard with dvswitch? I have tried to get the mmdvmhost-dashboard to work without success. It shows current transmission but no LH list. I would be quite happy with a display like the pyUC client has. Or, simple terminal session that displays connected traffic (like the DVLink app). Any thoughts?

 
--
Tom VE3NY


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

Rudy N6DOZ
 

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

 


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

Steve N4IRS
 
Edited

Are you telling me MMDVM_Bridge is segfaulting? if so, please post COMPLETE MMDVM_Bridge.ini
When does it segfault? At startup or when passing traffic?


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Rudy N6DOZ
 

Eric, I have started a new thread for the FCS to DMR link here.


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

Rudy N6DOZ
 

MMDVM_Bridge 1.4.1.

Updated to MMDVM_Bridge 1.5.1 and got the same result.

uname -a

 

Linux vultr.guest 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/debian_version

buster/sid


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

Steve N4IRS
 

What program is core dumping?

On 5/17/20 10:53 AM, Rudy N6DOZ wrote:

Thanks Steve.

I've been playing with the setup Eric K6KWB suggested and I get a "Segmentation fault (core dumped)" error.

Stand by for snips...



Re: Problem of TalkerAlias in DVSwitch.in

Steve N4IRS
 

Hi,
We tested this by looking at the MMDVMHost log of the receiving station. We did not see a change in the DMR ID. Do you see the change in the DMR ID on a receiving radio or a dashboard? I will be testing with a MD380 later today.

73, Steve N4IRS

On 5/17/20 8:47 AM, 정성환 wrote:

Hi All,


DVSwitch.in which is undated recently was added new "TalkerAlias" line in [DMR] and "Message" line [STAR] section each.

The function of the Message in [DSTAR] has no problem because the DSTAR do not use the DMR ID I think.

But the "TalkerAlias in [DMR] has some problems that the DMR id number of transmitting station is changed to another different one in several seconds. So the National DMR id also is changed to another different nation DMR. But the information having the TalkerAlias is correct. 


How can I overcome this problem?


de DS5HVM form KOREA






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

Rudy N6DOZ
 

Thanks Steve.

I've been playing with the setup Eric K6KWB suggested and I get a "Segmentation fault (core dumped)" error.

Stand by for snips...


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Steve N4IRS
 

Eric,
Happy to help by adding the steering. That is the value of this forum. Mike and I read the comment and problems. We try to address those type of "pain points" as we see them.
That is the value of this tight feedback loop.

73, Steve N4IRS

On 5/16/20 5:53 PM, Eric-K6KWB wrote:
Yes you need two MB one connect to BM and one for YSF Gateway. Almost similar to the first one you create use YSF Gateway and select FCS.
BM-TG??<->MB_BM<->MB_YSF<->YSF Gateway<->FCS003

Did you download from DVSwitch System Builder a complete package:
https://github.com/DVSwitch/DVSwitch-System-Builder

Looks like Steve have developed a new update to steer TGs in MB, will see how does it work, thank you Steve for this update. :)
73, Eric


noise on DVSWITCH

Paul on6dp
 

HI,
I have a HBLINK and DVSWitch on the same VPS.
There are about 40 users oin the DVSWitch (not on same time hi)
Few users, has a bif noise when they try to receive anything. Others don't have that problem.
Anybody can help me to resolve that problem?
Anybody has already had that problem ?

Regards
73 Paul, ON6DP


Re: Problem of TalkerAlias in DVSwitch.in

Steve N4IRS
 

Hi,
Short term answer, comment out TalkerAlias in DVSwitch.sh while we investigate the problem.
; TalkerAlias = Roger Nowhere Il. DVSWITCH


 

On 5/17/20 8:47 AM, 정성환 wrote:

Hi All,


DVSwitch.in which is undated recently was added new "TalkerAlias" line in [DMR] and "Message" line [STAR] section each.

The function of the Message in [DSTAR] has no problem because the DSTAR do not use the DMR ID I think.

But the "TalkerAlias in [DMR] has some problems that the DMR id number of transmitting station is changed to another different one in several seconds. So the National DMR id also is changed to another different nation DMR. But the information having the TalkerAlias is correct. 


How can I overcome this problem?


de DS5HVM form KOREA






Problem of TalkerAlias in DVSwitch.in

정성환
 

Hi All,


DVSwitch.in which is undated recently was added new "TalkerAlias" line in [DMR] and "Message" line [STAR] section each.

The function of the Message in [DSTAR] has no problem because the DSTAR do not use the DMR ID I think.

But the "TalkerAlias in [DMR] has some problems that the DMR id number of transmitting station is changed to another different one in several seconds. So the National DMR id also is changed to another different nation DMR. But the information having the TalkerAlias is correct. 


How can I overcome this problem?


de DS5HVM form KOREA





Re: DVSwitch Dashboard

Steve N4IRS
 

The dashboard is on my ever expanding todo list.

Steve

On 5/16/20 10:27 PM, Tom Corcoran wrote:

have anyone installed a dashboard with dvswitch? I have tried to get the mmdvmhost-dashboard to work without success. It shows current transmission but no LH list. I would be quite happy with a display like the pyUC client has. Or, simple terminal session that displays connected traffic (like the DVLink app). Any thoughts?

 
--
Tom VE3NY


DVSwitch Dashboard

Tom Corcoran
 
Edited

has anyone installed a dashboard with dvswitch? I have tried to get the mmdvmhost-dashboard to work without success. It shows current transmission but no LH list. I would be quite happy with a display like the pyUC client has. Or, simple terminal session that displays connected traffic (like the DVLink app). Any thoughts?

 
--
Tom VE3NY


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Rudy N6DOZ
 

Eric,

Thanks, I greatly appreciate the working sample and the URL for the system builder—that's awesome!

Need to make a few more instances of MB :P and put YSFGateway.

7-3 Rudy


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Rudy N6DOZ
 

Steve,

Great! Eagerly awaiting the full release! 

Thanks for your hard work. 7-3


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Eric-K6KWB
 
Edited

Rudy,

Here is a working sample YSGateway
[General]
Callsign= K6KWB
#Suffix=
# Suffix=ND
Id=your id
RptAddress=127.0.0.1
RptPort=62045   >>>port of your choice should cross MB_YSF
LocalAddress=127.0.0.1
LocalPort=62046
Daemon=0
 
[Info]
RXFrequency=437000000
TXFrequency=437000000
Power=1
Latitude=34.0686
Longitude=-117.9390
Height=0
Location=Los Angeles, CA
Description=DVSwitch
URL=https://your url
 
[Network]
Startup=FCS003   >>>>>your FCS number here
# Startup=Alabama Link 
InactivityTimeout=0
Revert=0
Debug=0
 
[YSF Network]
Enable=0
Port=0
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
 


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Steve N4IRS
 

Testing on Pi full release later.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Rudy N6DOZ <n6doz@...>
Sent: Saturday, May 16, 2020 6:08:16 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge #mmdvm_bridge
 

That's awesome Steve! How about for those folks who aren't on a Rasberry Pi? :P My services are on the cloud running Ubuntu 18.04.4 LTS.

If the updates apply, which one do I grab from Github?

Thanks for all the hard work Steve!


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Steve N4IRS
 

Should not have to. Will also allow you not to need DMRGateway for XLX

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Eric-K6KWB <kf6itc@...>
Sent: Saturday, May 16, 2020 6:04:55 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge #mmdvm_bridge
 
Steve N4IRS,
That latest update on MB means we dont need to set up static TG on self care? set TG on DVSwitch.ini is enough?
Appreciated.
best and 73, Eric


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge

Rudy N6DOZ
 

Eric, cool. I'll check it out!

3501 - 3520 of 9882