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: Coming to a browser near you
jacomms
😊
Justin Albury J Albury Communications 0417246791 VK2JUZ ----------------------------------------------------------------- This email, and any attachments are for the use of the intended recipient(s) and may contain confidential/privileged information. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not copy, disclose or distribute its contents to any other person. We do not accept any liability in connection with transmitting, unauthorised access to, or viruses in this email and its attachments. This notice should not be removed. ----------------------------------------------------------------------------------
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
On Behalf Of Steve N4IRS
Sent: Thursday, 19 November 2020 3:33 AM To: main@DVSwitch.groups.io Subject: [DVSwitch] Coming to a browser near you
In the discussion of a issue with radioid.net missing some entries this weekend I posted a screenshot of a work in progress. So, since the cat is out of the bag...
|
|
|
|
Re: os for Raspberry Pi
Thanks
I hope to setup on a pi also. Wht are the best directions -- 73s, Warmest wishes to you and blessings to your family.
Andre
Toronto, CANADA
website VE3SP.com
VE3SP.com
|
|
|
|
Re: os for Raspberry Pi
toggle quoted messageShow quoted text
I am ready to try my luck and build a DMR to YSF server. I plan on using a Raspberry Pi 3 B+. What Operating System should I use and where should I download it? --
Doug Gooden troytrojan@...
|
|
|
|
os for Raspberry Pi
thlongan@...
I am ready to try my luck and build a DMR to YSF server. I plan on using a Raspberry Pi 3 B+. What Operating System should I use and where should I download it?
|
|
|
|
Re: ASL to DMR - not receiving inbound traffic
Gerry Filby
Thanks for the response Brad !
I tried that and it stopped working altogether. I looked in /opt/MMDV_Bridge/DVSwitch.ini and TX/RX are defined: [DMR] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 31100 ; Port to send AMBE TLV frames to (export) RXPort = 31103 ; Port to listen on (import) Slot = 2 ; Export slot ExportTG = 0 ; Which TG to export TalkerAlias = Roger Nowhere Il. DVSWITCH So I'm assuming that needs to be reversed in Analog_Bridge.ini ? - Tx goes to Rx and visa versa: [AMBE_AUDIO] address = 127.0.0.1 ; IP address of xx_Bridge txPort = 31103 ; Transmit TLV frames to partner on this port rxPort = 31100 ; Listen for TLV frames from partner on this port ambeMode = DMR ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format) minTxTimeMS = 2500 ; Minimum time in MS for hang delay (0-10000) I'm getting traffic from the TG 91, but only if I momentarily click my PTT on the analog side whilst a 3rd party is speaking in the TG. If the 3rd party in the TG stops an restarts their over, I don't resume receiving their traffic from the TG. g
|
|
|
|
Coming to a browser near you
In the discussion of a issue with radioid.net missing some entries this weekend I posted a screenshot of a work in progress. So, since the cat is out of the bag...
This is a work in progress of the new web (HTML) client. We have no release date and the program has not even gone into beta test yet. I'll post update info here when available.
|
|
|
|
Re: Dashboard for multiple instances in DVSwitch
Problem solved. I followed this great article : https://n2rac.com/dmr-digital-amateur-radio-setup-several-instances-dvswitch-server-3694caaf6bf1 # cp /opt/Web_Proxy/ /opt/Web_Proxy2/ -r
# cp /lib/systemd/system/webproxy.s
And edit recursively all "version 2" .php files (starting from index2.php) to point at second instance's locations and also all .php files references to "version 2" .php
|
|
|
|
Re: ASL to DMR - not receiving inbound traffic
Gerry in your Analog_bridge.ini under Ambe_Audio set your ports to
tx=31100 Rx=31103 then it will work
toggle quoted messageShow quoted text
On 11/17/2020 7:13 PM, Gerry Filby
wrote:
Hi Folks,
|
|
|
|
DVSwitch running on RPI 3 A+
Working fine, just had to try!
Rich
|
|
|
|
User guide page 3
Great guide! Suggest a bit of clarity on wireless setup would be useful. Two separate sections on page 3 would help and methods 2and3 don’t seem to apply anymore.
rich
|
|
|
|
ASL to DMR - not receiving inbound traffic
Gerry Filby
Hi Folks,
I've worked through the "ASL to DMR Bridge How To" pdf and I think I have things more or less set up - I get the expected CLI output when running MMDVM_Bridge and Analog_Bridge in the foreground per the doc. I'm connecting to TG 91 (Worlwide) in Analog_bridge.ini thusly: [AMBE_AUDIO] address = 127.0.0.1 ; IP address of xx_Bridge txPort = 31103 ; Transmit TLV frames to partner on this port rxPort = 31100 ; Listen for TLV frames from partner on this port ambeMode = DMR ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this f$ minTxTimeMS = 2500 ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes gatewayDmrId = 310307899 ; ID to use when transmitting from Analog_Bridge repeaterID = 310307801 ; ID of source repeater txTg = 91 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge txTs = 2 ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge colorCode = 1
|
|
|
|
Re: Will DVSwitch support my Raspberry Pi 3B+ 3.5" 320x480 TFT Touch Screen
Depends on what you want to do. Tell us more.
toggle quoted messageShow quoted text
Steve N4IRS
On 11/17/2020 3:48 PM,
KM4GCY@... wrote:
I build my Raspberry Pi 3 with a 3.5" 320x480 TFT Touch Screen in hopes to find an image that would support it, is DWSwitch a good solution?
|
|
|
|
Will DVSwitch support my Raspberry Pi 3B+ 3.5" 320x480 TFT Touch Screen
I build my Raspberry Pi 3 with a 3.5" 320x480 TFT Touch Screen in hopes to find an image that would support it, is DWSwitch a good solution?
|
|
|
|
Dashboard for multiple instances in DVSwitch
kpappa@...
I have installed two functional instances on my Raspberry PI, but so far I managed to have Dashboard only for the first instance. Any idea or anyone have implemented such a similar task ?
|
|
|
|
Re: M17 to ASL
Skyler Fennell
Sorry Steve (kc1awv) for bad mouthing the mode, sometimes I forget the filter, and think its a really cool project and am willing to help where I can to improve on it. I’m guilty of it too but a lot of us take all this free open source software for granted. Skyler
On Mon, Nov 16, 2020 at 7:09 AM Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: M17 to ASL
Skyler Fennell
Thank you Steve, I really appreciate your work!
On Mon, Nov 16, 2020 at 6:31 AM Steve KC1AWV <smiller+groups@...> wrote: Skyler,
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Because it's all digital. No need for a Analog component.
toggle quoted messageShow quoted text
On 11/16/2020 8:43 AM, Aaron Groover
wrote:
This is where i get stuck. How does it communicate without Analog_Bridge.ini?
|
|
|
|
low audio from dmr to echolink
Jose Manuel Martinez Barbera
![]()
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Aaron Groover
This is where i get stuck. How does it communicate without Analog_Bridge.ini?
|
|
|
|
Re: M17 to ASL
Skyler,
I'm sorry that your experience with M17 hasn't been as stellar as some may expect. Please, understand that the protocol is still very much in its infancy, and there are many people working on the protocol to improve it. As of now, there are no plans by the M17 Working Group on implementing any sort of cross-mode / cross-protocol capability, as the protocol is still not finished. There are several projects working on doing so, but again these are all very much in an 'alpha' stage. If you would like to participate or know more about the progress, you may visit the website or join us on our chat channels to further the discussion there. Thanks! Steve KC1AWV
|
|
|