Welcome to DVSwitch
DVSwitch is a set of tools and programs related to provisioning and operating Amateur Radio digital voice networks.
Purpose
The purpose of DVSwitch is as follows:
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
Mission Statement/Position
Our stated position is:
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Rudy,
toggle quoted messageShow quoted text
You should have 2 different MB log files. One for MB_BM and one for MB_XLX See the [Log] stanza in each MB.ini Look at the FileRoot value for each MB. Steve
On 5/15/2020 9:10 AM, Rudy N6DOZ wrote:
Steve, here's the logs for both MBs.
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Rudy,
Double check your MB_BM DVSwitch.ini set to slot 1, should be slot 2. M: 2020-05-15 07:06:48.384 DMR, Opening INI file: DVSwitch.ini M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] TXPort -> 32100
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] RXPort -> 32103
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] Slot -> 1 73, Eric
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Ernie,
So do you have it setup as the more previous way (Steve Millar's doc https://docs.google.com/document/d/1n17cx_9elLJoMmcQWM0_XOm2dicKdIC6ar_0S16904A/edit) with two DMRGateways? Would you mind sharing your .ini snips?
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Steve, here's the logs for both MBs.
MB_BM I: 2020-05-15 07:06:42.831 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGINT
I: 2020-05-15 07:06:45.626 MMDVM_Bridge:
I: 2020-05-15 07:06:45.626 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2020-05-15 07:06:45.626 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-05-15 07:06:45.626 =
I: 2020-05-15 07:06:48.213 This software is for use on amateur radio networks only,
I: 2020-05-15 07:06:48.213 it is to be used for educational purposes only. Its use on
I: 2020-05-15 07:06:48.213 commercial networks is strictly prohibited.
I: 2020-05-15 07:06:48.213 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-05-15 07:06:48.213 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2020-05-15 07:06:48.213 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac)
I: 2020-05-15 07:06:48.213 General Parameters
I: 2020-05-15 07:06:48.213 Callsign: N6DOZ
I: 2020-05-15 07:06:48.213 Id: 3150692
I: 2020-05-15 07:06:48.213 Duplex: no
I: 2020-05-15 07:06:48.213 Timeout: 180s
I: 2020-05-15 07:06:48.213 D-Star: disabled
I: 2020-05-15 07:06:48.213 DMR: enabled
I: 2020-05-15 07:06:48.213 YSF: disabled
I: 2020-05-15 07:06:48.213 P25: disabled
I: 2020-05-15 07:06:48.213 NXDN: disabled
I: 2020-05-15 07:06:48.213 Modem Parameters
I: 2020-05-15 07:06:48.214 Port: /dev/null
I: 2020-05-15 07:06:48.214 RX Invert: no
I: 2020-05-15 07:06:48.214 TX Invert: no
I: 2020-05-15 07:06:48.214 PTT Invert: no
I: 2020-05-15 07:06:48.214 TX Delay: 100ms
I: 2020-05-15 07:06:48.214 RX Offset: 0Hz
I: 2020-05-15 07:06:48.214 TX Offset: 0Hz
I: 2020-05-15 07:06:48.214 RX DC Offset: 0
I: 2020-05-15 07:06:48.214 TX DC Offset: 0
I: 2020-05-15 07:06:48.214 RF Level: 100.0%
I: 2020-05-15 07:06:48.214 DMR Delay: 0 (0.0ms)
I: 2020-05-15 07:06:48.214 RX Level: 50.0%
I: 2020-05-15 07:06:48.214 CW Id TX Level: 50.0%
I: 2020-05-15 07:06:48.214 D-Star TX Level: 50.0%
I: 2020-05-15 07:06:48.214 DMR TX Level: 50.0%
I: 2020-05-15 07:06:48.214 YSF TX Level: 50.0%
I: 2020-05-15 07:06:48.214 P25 TX Level: 50.0%
I: 2020-05-15 07:06:48.215 NXDN TX Level: 50.0%
I: 2020-05-15 07:06:48.215 RX Frequency: 432100000Hz (432100000Hz)
I: 2020-05-15 07:06:48.215 TX Frequency: 432100100Hz (432100100Hz)
M: 2020-05-15 07:06:48.215 Opening the MMDVM
I: 2020-05-15 07:06:48.215 Display Parameters
I: 2020-05-15 07:06:48.215 Type:
I: 2020-05-15 07:06:48.215 DMR Network Parameters
I: 2020-05-15 07:06:48.215 Address: 45.77.186.5
I: 2020-05-15 07:06:48.215 Port: 62030
I: 2020-05-15 07:06:48.215 Local: 62033
I: 2020-05-15 07:06:48.215 Jitter: 360ms
I: 2020-05-15 07:06:48.215 Slot 1: disabled
I: 2020-05-15 07:06:48.215 Slot 2: enabled
I: 2020-05-15 07:06:48.215 Mode Hang: 3s
I: 2020-05-15 07:06:48.215 Options: XLX:4001
I: 2020-05-15 07:06:48.215 Info Parameters
I: 2020-05-15 07:06:48.215 Callsign: N6DOZ
I: 2020-05-15 07:06:48.216 RX Frequency: 432100000Hz
I: 2020-05-15 07:06:48.216 TX Frequency: 432100100Hz
I: 2020-05-15 07:06:48.216 Power: 1W
I: 2020-05-15 07:06:48.216 Latitude: 37.654202deg N
I: 2020-05-15 07:06:48.216 Longitude: -122.429802deg E
I: 2020-05-15 07:06:48.216 Height: 16m
I: 2020-05-15 07:06:48.216 Location: "South San Francisco, CA USA"
I: 2020-05-15 07:06:48.216 Description: "M2X_MMDVM_BRIDGE"
I: 2020-05-15 07:06:48.216 URL: "https://www.qrz.com/db/N6DOZ"
M: 2020-05-15 07:06:48.216 DMR, Opening DMR Network
I: 2020-05-15 07:06:48.216 RSSI
I: 2020-05-15 07:06:48.216 Mapping File: RSSI.dat
W: 2020-05-15 07:06:48.216 Cannot open the RSSI data file - RSSI.dat
I: 2020-05-15 07:06:48.216 DMR Id Lookups
I: 2020-05-15 07:06:48.216 File: /var/lib/mmdvm/DMRIds.dat
I: 2020-05-15 07:06:48.216 Reload: 24 hours
I: 2020-05-15 07:06:48.383 Loaded 164301 Ids to the DMR callsign lookup table
I: 2020-05-15 07:06:48.384 DMR RF Parameters
I: 2020-05-15 07:06:48.384 Id: 3150692
I: 2020-05-15 07:06:48.384 Color Code: 1
I: 2020-05-15 07:06:48.384 Self Only: no
I: 2020-05-15 07:06:48.384 Embedded LC Only: yes
I: 2020-05-15 07:06:48.384 Dump Talker Alias Data: no
I: 2020-05-15 07:06:48.384 Prefixes: 0
I: 2020-05-15 07:06:48.384 Call Hang: 3s
I: 2020-05-15 07:06:48.384 TX Hang: 3s
I: 2020-05-15 07:06:48.384 Mode Hang: 10s
M: 2020-05-15 07:06:48.384 DMR, Opening INI file: DVSwitch.ini
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] TXPort -> 32100
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] RXPort -> 32103
M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] Slot -> 1
M: 2020-05-15 07:06:48.385 DMR, Transmitting on 127.0.0.1:32100 and listening on port 32103. Result = 1
M: 2020-05-15 07:06:48.385 MMDVM_Bridge-20191105_V1.4.1 is running
I: 2020-05-15 07:06:48.385 Started the DMR Id lookup reload thread
M: 2020-05-15 07:07:08.405 DMR, Logged into the master successfully
M: 2020-05-15 07:07:08.405 DMR, Remote CMD: txTg=4000
M: 2020-05-15 07:07:08.405 DMR, Tune: id=3150692, tg=4000, mode=Group
M: 2020-05-15 07:07:08.405 DMR, Remote CMD: txTg=4001
M: 2020-05-15 07:07:08.405 DMR, Tune: id=3150692, tg=4001, mode=Group
M: 2020-05-15 07:07:08.456 DMR Slot 2, received network voice header from N6DOZ to TG 9
M: 2020-05-15 07:07:08.461 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2020-05-15 07:12:26.479 DMR, TX state = ON
I: 2020-05-15 07:12:26.479 DMR, Begin TX: src=3135404 rpt=0 dst=311620 slot=1 cc=0 metadata=N6DOZ
M: 2020-05-15 07:12:30.077 DMR, TX state = OFF, DMR frame count was 62 frames
M: 2020-05-15 07:12:33.743 DMR Slot 2, received network voice header from N6DOZ to TG 9
M: 2020-05-15 07:12:37.402 DMR Slot 2, received network end of voice transmission, 3.9 seconds, 1% packet loss, BER: 0.0%
M: 2020-05-15 07:12:46.739 DMR Slot 2, received network voice header from N6DOZ to TG 9
M: 2020-05-15 07:12:49.226 DMR Slot 2, received network end of voice transmission, 3.1 seconds, 11% packet loss, BER: 0.0%
M: 2020-05-15 07:13:15.060 Closing the MMDVM
I: 2020-05-15 07:13:15.417 Stopped the DMR Id lookup reload thread
M: 2020-05-15 07:13:15.418 DMR, Closing DMR Network
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
XLX Will be passing its traffic via Tg9.
What I do is MB to MB to Dmrgateway.
In the settings of the Dmrgateway rewrite tg9 to tg on Brandmeister.
This works well on Dmr+ and Brandmeister.
You can also rewrite from slot2 to slot1.
This setup will run all day every day without needing a restart.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, May 15, 2020 10:40:58 AM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge #mmdvm_bridge logs snips? ini snips?
On 5/15/20 3:29 AM, Rudy N6DOZ wrote:
After putting a static TG through BM selfcare, I was able to hear audio coming from someone on the BM TG side.
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
logs snips? ini snips?
toggle quoted messageShow quoted text
On 5/15/20 3:29 AM, Rudy N6DOZ wrote:
After putting a static TG through BM selfcare, I was able to hear audio coming from someone on the BM TG side.
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
After putting a static TG through BM selfcare, I was able to hear audio coming from someone on the BM TG side.
However, when I transmit from the XLX side, no audio is heard on the BM TG side. I'm trying to look for errors in the logs, but nothing is showing up for me. Thanks again. 7-3 N6DOZ
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Ok :) Easy enough. Thank you!
I'll set everything up tonight and post my results. Thanks a ton! 7-3 N6DOZ
|
|
|
|
Setting up YSF
Pete Fierro <overthetop52@...>
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Easiest way is to setup a static TG in BM selfcare.
toggle quoted messageShow quoted text
On 5/14/20 9:31 PM, Rudy wrote:
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Thanks Steve! [General]
Callsign=N6DOZ
Id=315069220 <-- with two digit ssid
Timeout=180
Duplex=0
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62042
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
MB_BM DVSwitch.ini [DMR]
Address = 127.0.0.1
TXPort = 32100 <-- cross connected
RXPort = 32103 <-- cross connected
Slot = 2
-- MB_XLX MMDVM_Bridge.ini [General]
Callsign=N6DOZ
Id=3150692
Timeout=180
Duplex=0
[DMR Network]
Enable=1
Address=45.77.186.5
Port=62030
Jitter=360
Local=62052
Password=passw0rd
Options=XLX:4001
Slot1=1
Slot2=1
Debug=1
MB_XLX DVSwitch.ini [DMR]
Address=127.0.0.1
TXPort = 33103 <-- cross connected
RXPort = 33100 <-- cross connected
Slot = 2
|
|
|
|
Re: Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
The cross connect is done in DVSwitch.ini
toggle quoted messageShow quoted text
MB_BM DVSwitch.ini [DMR]
Address = 127.0.0.1
TXPort = 32100
RXPort = 32103
Slot = 2
MB_XLX DVSwitch.ini [DMR]
Address=127.0.0.1
TXPort = 32103
RXPort = 32100
Slot = 2 TX to RX RX to TX Steve N4IRS
On 5/14/20 9:19 PM, Rudy wrote:
Now based on everything I read so far doing a search on bridging XLX to BM DMR via MMDVM_Bridge (no longer needing DMRGateway), the structure is as follow:
|
|
|
|
Bridging XLX to BM DMR (New Way 2020)
#mmdvm_bridge
Now based on everything I read so far doing a search on bridging XLX to BM DMR via MMDVM_Bridge (no longer needing DMRGateway), the structure is as follow:
BM TG <-> MB_BM <-> MB_XLX <-> XLX Reflector Now, I have created to instances of MMDVM_Bridges with utilizing unique ports to each other. I am able to connect the respective instances to DMR and the XLX reflector but for the life of me, I can not figure out how the two MMDVM_Bridges are to be connected. BM TG <-> MB_BM < ??? > MB_XLX <-> XLX Reflector MB_BM MMDVM_Bridge.ini [General]
Callsign=N6DOZ
Id=315069220 <-- with two digit ssid
Timeout=180
Duplex=0
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62042
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
MB_BM DVSwitch.ini [DMR]
Address = 127.0.0.1
TXPort = 32100
RXPort = 32103
Slot = 2
Q. What protocol am I to use to connect this MB_BM to the other instance? MB_XLX MMDVM_Bridge.ini [General]
Callsign=N6DOZ
Id=3150692
Timeout=180
Duplex=0
[System Fusion]
Enable=1
[DMR Network]
Enable=1
Address=45.77.186.5
Port=62031
Jitter=360
Local=62052
Password=passw0rd
Options=XLX:4001
Slot1=1
Slot2=1
Debug=1
MB_XLX DVSwitch.ini [DMR]
Address=127.0.0.1
TXPort = 33100
RXPort = 33103
Slot = 2
Q. Same question here, what protocol am I to use to connect this MB_XLX to the other instance? Thanks in advance! 7-3 N6DOZ. TL;DR
I ended up doing what Ernie Gm7kbk suggested, which is basically running the MB_BM through DMRGateway to change TG9 to my target TG. Works great!
BM <-> DMRGateway <-> MB_BM <-> MB_XLX <-> XLX
|
|
|
|
Re: Is there a simple way for Bridging a Brandmeister TG to an XLX Reflector (new 2020 Version)
Patrick,
Did you ever get this configuration working? If so, would you mind sharing your configurations MMDVM_Bridge.ini and DVSwitch.ini for both instances? 7-3, Rudy
|
|
|
|
Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.
EA5GVK Joaquin
On Thu, May 14, 2020 at 12:18 PM, Jeff Lehman, N8ACL wrote:
OK. Good Luck. I can’t help more than that. I was just curious.Thank you, Jeff. Take it easy. We have Steve who is helping us a lot, so the Dvswitch application is phenomenal. Greetings.
|
|
|
|
Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.
Jeff Lehman, N8ACL
OK. Good Luck. I can’t help more than that. I was just curious.
toggle quoted messageShow quoted text
|
|
|
|
Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.
EA5GVK Joaquin
Hi, Jeff. Not just a single dvswitch user. One Analog_Bridge , MMDVM_Bridge, md380-emu, on a raspberry pi with debian 10 buster.
El jue., 14 may. 2020 a las 20:42, Jeff Lehman, N8ACL via groups.io (<n8acl=icloud.com@groups.io>) escribió:
|
|
|
|
Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.
Jeff Lehman, N8ACL
Joaquin,
toggle quoted messageShow quoted text
Just out of curiosity, does EA5GVK possibly hav a couple of hotspots on the same frequency that have that Talkgroup set on them? There has been some problems with people having multiple hotspots and they tend to loop back on themselves on a talk group. So I was just curious. :) Jeff
|
|
|
|
Re: Possible Loop in QSO DMR and MMDVM_Bridge or Analog_Bridge malfunction.
EA5GVK Joaquin
Good afternoon, Steve.
I report again the same problem of LOOP of my friend EA1HWR, I have attached the logs of the new Analog_Bridge and MMDVM_Bridge, armhf, as well as the log provided by BM Spain. For you to see also the server the problem that generates the loop. Steve can be seen at 19:23 in the BM log which coincides with 17:23 utc in the analog_bridge and MMDVM_Bridge log. Any more information will be reported to you.
|
|
|
|
DvSwitch MObile
honda5603@...
Does anyone know if a bluetooth PTT and speaker will work with DVSwitch Mobile?
https://www.amazon.com/Bluetooth-Microphone-Button-speaker-Android/dp/B01NBB7DU0?pf_rd_r=1J5WDE24V1891MDMKHV2&pf_rd_p=4ef03d4f-fc52-4cba-b905-5ea280a737fe&pd_rd_r=2035ea1c-9f3b-4a7b-bc8b-b817267b7f0a&pd_rd_w=zTkw6&pd_rd_wg=9lxrZ&ref_=pd_gw_ci_mcx_mr_hp_d
|
|
|