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: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
MB connects and will pass traffic. Then drops with connection to the master has timed out. Then reconnects.
From: Adrian <vk4tux@...>
Sent: Thursday, November 7, 2019 4:24:26 PM To: Ernest Pratt <erniepratt@...>; main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge Ok, on that, it appears to connect in two stages running a disconnect , then target ; I: 2019-11-07 16:21:07.842 Starting M: 2019-11-07 16:21:26.821 DMR, Logged into the master successfully M: 2019-11-07 16:21:26.821 DMR, Remote CMD: txTg=4000 M: 2019-11-07 16:21:26.821 DMR, Tune: id=5054444, tg=4000, mode=Group M: 2019-11-07 16:21:26.822 DMR, Remote CMD: txTg=4017
On 8/11/19 1:37 am, Ernest Pratt wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Adrian Fewster <vk4tux@...>
Ok, on that, it appears to connect in two stages running a disconnect , then target ; I: 2019-11-07 16:21:07.842 Starting M: 2019-11-07 16:21:26.821 DMR, Logged into the master successfully M: 2019-11-07 16:21:26.821 DMR, Remote CMD: txTg=4000 M: 2019-11-07 16:21:26.821 DMR, Tune: id=5054444, tg=4000, mode=Group M: 2019-11-07 16:21:26.822 DMR, Remote CMD: txTg=4017
On 8/11/19 1:37 am, Ernest Pratt wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Thanks Adrian.Will update to night.
From: Adrian <vk4tux@...>
Sent: Thursday, November 7, 2019 3:27:43 PM To: Ernest Pratt <erniepratt@...>; main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge Confirming V1.4 does work direct with XLX here. No DMRGateway needed. On 8/11/19 1:21 am, Ernie Gm7kbk wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Adrian Fewster <vk4tux@...>
Confirming V1.4 does work direct with XLX here. No DMRGateway
needed.
On 8/11/19 1:21 am, Ernie Gm7kbk wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
At work at moment, will download in one hour and test.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, November 7, 2019 3:05:10 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge Are you running the latest MMDVM_Bridge from github? I posted the latest 2 days ago.
On 11/7/2019 10:03 AM, Ernie Gm7kbk wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Are you running the latest MMDVM_Bridge from github? I posted the
latest 2 days ago.
toggle quoted messageShow quoted text
On 11/7/2019 10:03 AM, Ernie Gm7kbk
wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
I tried the other day to connect directly to my xlx server, and could not. Connected via hblink3 instead. Mb says it connected but xlx does not see the connection.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, November 7, 2019 2:39:56 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge David,
Yes the latest MMDVM_Bridge in github has all the current fixes. Please let me know your results. Steve N4IRS On 11/7/2019 9:35 AM, davidchien0327 via Groups.Io wrote:
Hi Steve and Mike
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
David,
toggle quoted messageShow quoted text
Yes the latest MMDVM_Bridge in github has all the current fixes. Please let me know your results. Steve N4IRS
On 11/7/2019 9:35 AM, davidchien0327
via Groups.Io wrote:
Hi Steve and Mike
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
David BV3UN
Hi Steve and Mike
my i know the latest vesion of MMDVM Bridge had fix the problem that can not connect select XLX DMR module ? i am wait for it to bridge BM DMR to XLX DMR module thanks
|
|
|
|
Re: BrandMeister to XLX
David BV3UN
Hi N0KEG
may i know any update .i just see all of posts of this topic and the doc write by Steve KC1AWV but still confused . if i just whant to bradge DMR TG to XLX dmr module .as i understood as below item 1 right ? 1.BM<->DMRGateway_BM<->MMDVM_Bridge_BM<->MMDVM_Bridge_XLX<->DMRGateway_XLX<->XLXD or item 2 ? 2.BM<->DMRGateway_BM<->MMDVM_Bridge_BM<->MMDVM_Bridge_XLX<->XLXD and 3 i need to follow doc to do rewite TG ?? thanks
|
|
|
|
IPSC-bridge Dmrlink and HBlink3: help for how to
#dmrlink
#best_practices
#hblink
Alex IK7SEC
Hi all,
i'd like to connect our Hblink3 to some Motorola repeaters.
Here i'd like to share what I think to have understooded to check if is it right and\or what I should do to get my goal.
I think this post could be usefull to make and edit a Wiki about it.
I apologize for the large number of questions in one post.
So, these are my notes (please correct and review it):
System should be configured in this way:
Prerequisites/ Starting points: Hblink3 fully working (with dmr_utils3 installed too)
Moto Rpt <---> dmrlink <--> IPSC_link <--> Hblink3<--> Rest of Wolrld
ip ip
port port
password password
1) #download packets
git clone -b HB_Bridge https://github.com/n0mjs710/HBlink.git (it will make a dir /hblnk)
git clone -b IPSC_Bridge https://github.com/n0mjs710/DMRlink.git
2) installing dmrlnk\Ipsc_bridge ./mk-dmrlink After that is it necessary or usefull merge dmr_link directory with dmr:link3 ???
installing Hb_bridge... How? Is it self executing without any kind of installation? Or is it simply necessary merge Hblink3 with this hblink?
3) Configure dmrlink: which are main config files? IPSC_bridge.cfg? dmrlink.cfg?
Configure HB_bridge: which are main config files (can we use only hblink3 configs?)
4) Executing dmrlink alone for testing: $ sudo python3 dmrlink.py ????? IPSC_bridge.py ??? Both of these? None of these?
Stop dmrlink
Executing Hb_bridge alone for testing: $ sudo python3 .....bridge.py ???? (which is executable file from HB_Bridge)
Thank you in advance for yours tips and tricks.
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
SP2ONG Waldek
Steve and Mike
I checked the latest version of MMDVM_Bridge v1.4 and replaced the YSF <-> XLX connection with the YSF2DMR for the versions with MMDVM_Bridge to connect the YSF Reflector with the XLX reflector on the selected module and it looks like it works.
|
|
|
|
Re: Linking DMR to Echolink
Tito Lopez - YN1OB
I recently setup an ASL node in the cloud with the procedures from that link. It works fine if you take the time to tune it up. Lots of fun linking up those 3 systems. 73's
On Wed, Nov 6, 2019, 8:54 PM Patrick Perdue <patrick@...> wrote:
|
|
|
|
Re: Linking DMR to Echolink
Patrick Perdue
You can setup EchoLink in ASL, then use the USRP driver as described to bridge using ASL, Analog_Bridge and MMDVM_Bridge. My advice, don't. EchoLink over DMR and vice versa sounds horrible, especially with the MD380-emu vocoder. It's not much better with a hardware dongle. The GSM codec of EchoLink, plus the levels all over the place make it a pretty substandard experience, both on analog and digitally, but especially digital. I have recently had to ban nodes from my bridge who connected EchoLink, because it was generating bad noises on digital modes, and didn't sound much better on analog. When the object is to communicate, and that isn't possible due to layers of artifacts due to clipping and transcoding *before* going to DMR, etc. But, if you really want to do this, see this post for setting up a bridge between DMR and ASL. https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg and this for configuring EchoLink on ASL: https://wiki.allstarlink.org/wiki/Echolink_Channel_Driver You'll need an EchoLink -l node number before configuring anything.
On 11/6/2019 10:52 PM, Dexter Harroo wrote:
Hi Guys,
|
|
|
|
Linking DMR to Echolink
Hi Guys,
Don't know if this has been asked before. is there any software in the group that i can use to link lets say DMR to Echolink? if there is i am willing to give it a go.
|
|
|
|
Re: Analog_Bridge remote control (TLV) commands exposed.
Just once
toggle quoted messageShow quoted text
On 11/6/2019 4:16 PM, K4VL wrote:
|
|
|
|
Re: Analog_Bridge remote control (TLV) commands exposed.
K4VL
Thank you Will I need to do this every time I update or just once?
On Wed, Nov 6, 2019 at 3:14 PM Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: Analog_Bridge remote control (TLV) commands exposed.
This is from the readme included with the image zip file:
toggle quoted messageShow quoted text
There may have been updates to the operating system and AllStarLink since this image was built. Run the following commands after the first time you boot. sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel sudo apt-get update sudo apt-get upgrade -y sudo reboot <http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme>
On 11/6/2019 4:12 PM, K4VL wrote:
|
|
|
|
Re: Analog_Bridge remote control (TLV) commands exposed.
K4VL
Raspberry Pi 3
On Wed, Nov 6, 2019 at 2:39 PM Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: Analog_Bridge remote control (TLV) commands exposed.
What hardware platform?
toggle quoted messageShow quoted text
apt-get update/upgrade are not going to install anything below. Everything is on github for now.
On 11/6/2019 3:23 PM, K4VL wrote:
|
|
|