Welcome to DVSwitch
Purpose
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
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: DVSwitch Server Dying once a day
Jay,
toggle quoted messageShow quoted text
We are looking at a possible cause / solution. Steve
On 2/25/2020 12:01 PM, Jay wrote:
Maybe someone has a solution. I have Raspberry Pi 3 with DVSwitch built from the most current instructions. It works great but sometime overnight, every night, the device becomes unreachable. By that I mean I VNC into it and it will not conned until it is rebooted. Its like it went to sleep and doesn't want to wake up.
|
|
Re: First release of USRP Client (pyUC)
Geoff,
toggle quoted messageShow quoted text
You can leave the default server alone, it will not be used when connecting to ASL. Set aslMode=1 Setup you ASL node using the USRP channel driver. Set the ports to the same value rxchannel = USRP/127.0.0.1:12345:12345 Please be aware that you can not control the node (*70 etc) from pyUC. All you can do is transmit and receive. Steve N4IRS
On 2/25/2020 1:58 PM,
ve6gcd@... wrote:
Hi Steve,
|
|
Re: First release of USRP Client (pyUC)
ve6gcd@...
Hi Steve,
Can you tell me how to set this up for ASL USRP node? The downloaded pyUC.ini file has defaultServer=DMR. aslMode=0 For AllStarLink Do I need to set defaultServer to blank, while aslMode=1? 73, Geoffrey VE6GCD
|
|
DVSwitch Server Dying once a day
Jay
Maybe someone has a solution. I have Raspberry Pi 3 with DVSwitch built from the most current instructions. It works great but sometime overnight, every night, the device becomes unreachable. By that I mean I VNC into it and it will not conned until it is rebooted. Its like it went to sleep and doesn't want to wake up.
Has anyone else experienced this. The OS is fully up to date. All IP addresses are static. No other software has been installed. I just enabled VNC and started using it. I do not believe it is DVSwitch software that is the cause but I have a bunch of Pi3 devices running without this occurring on them. Any suggestions or hints would be helpful. -- jb N4NQY
|
|
YSF to DMR setup with hang time
#mmdvm_bridge
ve6gcd@...
Hi,
I would like to setup MMDVM_Bridge where FCS room can comminicate with a Brandmeister Talkgroup. Due to the loop ban processing in BM, I would like to set it up such that DMR will have minimum of 2 seconds RX for every transmission coming from the FCS room. Can you guys tell me how the MMDVM_Bridge should be configured? Please advise. Thanks. 73, Geoffrey VE6GCD
|
|
Re: setting up MMDVM_Bridge and Analog_Bridge
#analog_bridge
#mmdvm_bridge
What error do you get?
toggle quoted messageShow quoted text
On 2/21/20 12:29 PM, yo2lqa@...
wrote:
Hi Steve.I use linux deploy apk on my android phone and i run debian in chroot.I have installed dvswitch...analog_bridge-md380-emu-mmdvm_bridge and connect to ipsc2 romania(DMR+).I have one problem,my md380-emu don't start as service in chroot.How can i solve this?
|
|
Re: alll star help
Brad NK8J <bradnk8j@...>
do you have your port forwarding open for echolink set in your
router? EchoLink requires that your router or
firewall allow inbound and outbound UDP to ports 5198 and 5199,
and outbound TCP to port 5200
toggle quoted messageShow quoted text
On 2/18/2020 12:06 AM, clayton wrote:
hi i new to this i just put this on my pi i can get ecolink to long in but can not conet to it and all so i see dmr working but all star will not work this is the file a flower
|
|
Re: setting up MMDVM_Bridge and Analog_Bridge
#analog_bridge
#mmdvm_bridge
yo2lqa@...
Hi Steve.I use linux deploy apk on my android phone and i run debian in chroot.I have installed dvswitch...analog_bridge-md380-emu-mmdvm_bridge and connect to ipsc2 romania(DMR+).I have one problem,my md380-emu don't start as service in chroot.How can i solve this?
73' YO2LQA
|
|
small pop at start of transmissions from DMR from Analog_Bridge
Patrick Perdue
Hi:
One of the things I've noticed for the few months I've used DVSwitch with a ThumbDV is that there is always a small pop at the start of transmissions from DMR to Analog_Bridge, and thus to ASL. I was just wondering if there is a way to delay the start of received audio by a few MS to avoid that somewhere in the chain, or if that would even make a difference. I don't recall this using the md380-emu, but it's been a long time since I've used it, so I could be wrong about that. Thanks and 73 de KE4DYI
|
|
alll star help
clayton
hi i new to this i just put this on my pi i can get ecolink to long in but can not conet to it and all so i see dmr working but all star will not work this is the file a flower
https://4x5mg.net/2018/07/16/allstar-to-dmr-bridge/ ps can any have a look at i have ssh working if some has some spar time to look at it thank you vk7zcr vk7zcr@... 0466588193
|
|
Re: Time Slot separate networks?
Another way to do it is at the repeater level if you have the ability to use DMRGateway (i.e. on Pi-Star). I am doing this on my repeater and doing some TGRewrite rules to direct talkgroups to one network or another. That way if you had multiple repeaters, and one person wanted to key up a talkgroup, it wouldn't tie up the whole network of repeaters with that one talkgroup; it would be on one specific repeater. If you are using a non-Pi-Star repeater (Moto, Hytera, etc) then the rules.py solution that has been mentioned would be the best route. -Andy, KDØIOE
On Wed, Feb 19, 2020 at 3:02 PM Kevin Halton <Khalton@...> wrote:
--
|
|
Re: Time Slot separate networks?
Kevin Halton
Put all of bm talkgroups on One slot and the repeater network on the other time slot in rules.py
toggle quoted messageShow quoted text
On Feb 19, 2020, at 3:54 PM, Skyler Fennell <electricity440@...> wrote:
|
|
Re: Time Slot separate networks?
JJ Cummings
That’s all trivially done in your rules file, that is what defines what TG gots to what TS and to / from what system.
toggle quoted messageShow quoted text
Sent from the iRoad
On Feb 19, 2020, at 13:54, Skyler Fennell <electricity440@...> wrote:
|
|
Time Slot separate networks?
Skyler Fennell
Home brew DMR repeater. Is it possible to change the network based on time slot? For example, I would like TS1 to be connected to my HBLINK server to host all of the local DMR repeaters, and TS2 to be connected to the brandmeister network for people to play with.
|
|
Re: Problems with MMDVM_Bridge timing out
Here is my working samples, hope its help. Do you have any log to start with?
You should have a latest version of MB to connect to XLX: https://github.com/DVSwitch/MMDVM_Bridge/tree/master/bin log version sample: M: 2020-01-25 02:13:55.953 MMDVM_Bridge-20191105_V1.4.1 is starting [DMR Network] Enable=1
Address="XLX dns name" or IP
Port=62030
Jitter=360
Local=62033
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=XLX:4001
Slot1=0
Slot2=1
Debug=0
73, Eric
|
|
Re: all star
do you have a allstar node #?
toggle quoted messageShow quoted text
On 2/18/2020 3:30 AM, clayton wrote:
|
|
Re: Problems with MMDVM_Bridge timing out
Local ports should be different.
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Bryan Jackson <beej-uk@...>
Date: 19/02/2020 09:45 (GMT+00:00)
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Problems with MMDVM_Bridge timing out
So I have installed two instances of MMDVM_Bridge to acheive and XLX to DMR Bridge but I am having stability problems. Here is is the layout.
XLXd ->MMDVM_Bridge-XLX->MMDVM_Bridge-BM->Brandmeister. Both instances keep timing out the connection and reconnecting to the masters every few minutes . I have used YSF2DMR to connect to both XLXd and Brandmeister and the connection is stable MMDVM_Bridge version is 1.4-20200110-8. Any Ideas where to start looking ?
|
|
Problems with MMDVM_Bridge timing out
Bryan Jackson
So I have installed two instances of MMDVM_Bridge to acheive and XLX to DMR Bridge but I am having stability problems. Here is is the layout.
XLXd ->MMDVM_Bridge-XLX->MMDVM_Bridge-BM->Brandmeister. Both instances keep timing out the connection and reconnecting to the masters every few minutes . I have used YSF2DMR to connect to both XLXd and Brandmeister and the connection is stable MMDVM_Bridge version is 1.4-20200110-8. Any Ideas where to start looking ?
|
|
all star
clayton
Hi I just install this on a raspberry pi https://4x5mg.net/2018/07/16/allstar-to-dmr-bridge/ I can get ecolink to comet and and dmr but not all star and all so the bight from one to the over Can any sper some to to long and have a look at what done woring
Sent from Mail for Windows 10
|
|
Re: Dvswitch app.. can not connect?
Charles,
toggle quoted messageShow quoted text
If I understand the question you want to connect to 2 different nodes. I assume from the no computer comment, you do not have a node of your own. If I have this correct, you would need the node owners to grant you access to their nodes from DVSwitch Mobile. So in short rather then connecting to your node and then to their node, you would connect directly to their node. 73, Steve N4IRS
On 2/17/20 10:28 PM, Charles Fraga
wrote:
Is it possible to set up the dvswitch app on an android to link to a specific node (45685, 45882) without having a computer. I am a truck driver and only have a phone and a tablet. Can someone explain what should be in each line for the account on the app.
|
|