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: ASL to P25 bridge
#analog_bridge
I rebooted and tried it again and I now have linux-headers-4.19.66-v7 installed and reported with uname -r.
I'll keep you posted Tom
|
|
Re: ASL to P25 bridge
#analog_bridge
Steve,
I just started with a fresh Raspian image and performed all of the suggested steps: apt-get update apt-get upgrade apt-get install raspberrypi-kernel-headers -y Unfortunately, I'm still seeing the same results. Fortunately, I haven't yet installed any of the ASL or DVSwitch stuff. root@P25reflector:/usr/src # uname -r 4.14.98-v7+
root@P25reflector:/usr/src # ls linux-headers-4.19.66+ linux-headers-4.19.66-v7+
Tom
|
|
Re: ASL to P25 bridge
#analog_bridge
2 options I can see at this point.
toggle quoted messageShow quoted text
1: Start with a fresh Stretch apt-get update apt-get upgrade apt-get install raspberrypi-kernel-headers -y Verify you have headers matching the running kernel. If so, install ASL. 2: Start with ASL 1.01 Steve
On 8/9/20 9:59 PM, Tom wrote:
Iroot@P25reflector:~ # apt-get install raspberrypi-kernel-headers -y
|
|
Re: ASL to P25 bridge
#analog_bridge
I guess I could start over with a working ASL image of my own and do all the dvswitch install including P25reflector and analog-bridge. That's a lot of re-do.
Tom
|
|
Re: MMDVM_Bridge.ini
#mmdvm_bridge
Charles Wiant
You first need to change directory to opt/MMDVM_Bridge
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of john.sutton45 via groups.io
I have followed the instructions for DVSwitch on Pi 3b+ and when and when I get to nano MMDVM_Bridge.ini the file is empty, also there is no program-name file.
|
|
Re: DMRIds.dat not updating
dvswitch update
Sent via smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of n3mel.epa@... <n3mel.epa@...>
Sent: Sunday, August 9, 2020 1:30:27 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: [DVSwitch] DMRIds.dat not updating Where do you set the timing for updating the DMRIds.dat file in DVSwitch or what is the command line to execute it manually?
Thank you in advance..
|
|
DMRIds.dat not updating
Where do you set the timing for updating the DMRIds.dat file in DVSwitch or what is the command line to execute it manually?
Thank you in advance..
|
|
Re: MMDVM_Bridge.ini
#mmdvm_bridge
What instructions did you follow?
toggle quoted messageShow quoted text
On 8/9/20 10:09 AM, john.sutton45 via
groups.io wrote:
I have followed the instructions for DVSwitch on Pi 3b+ and when and when I get to nano MMDVM_Bridge.ini the file is empty, also there is no program-name file.
|
|
ASL to P25 bridge
#analog_bridge
I want to make a bridge between ASL and P25. I understand that I must use the USRP channel driver and ports 32001, 34001.
I believe the flow is ASL<->analog_bridge<->MMDVM<->P25gateway<->P25reflector. I have several questions: 1) Can I do this without a DV3000?
2) What ports are used between modules?
AMBE_audio to MMDVM 32010, 42020 ?
MMDVM to P25gateway 34103,34100 ?
3) The analog_bridge.ini files that I have seen on the web appear to have DMR stuff like ToDMR port, FromDRM port,slot , color. When I install analog bridge will I see that or P25 settings?
Thanks, Tom / K5TRA
|
|
Re: AllStar and DummyRepeater
On 7/8/20 7:42 pm, Steve N4IRS wrote:
Maybe I was not clear. The files are at Thanks again Steve, got it all working. Had to do a bit of trial and error, and Googling to get ircDDBGateway to play ball, but it's all running now. Any activity on the AllStar side results in DummyRepeater going into transmit. Waiting on my MMDVM board to access the system from the D-STAR side, and give my old IC-91AD a run. :) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Perry Buch
heh which is why I was going crazy, appreciate the help and the dev on this. Makes these digital modes work as they should
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
As you can see, a YSF to DMR bridge is the absolute simplest
possible bridge.
toggle quoted messageShow quoted text
Steve N4IRS
On 8/7/2020 3:48 PM, Perry Buch wrote:
Nope that was the problem. Audio both ways working as expected. Thanks!
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Happy to help.
toggle quoted messageShow quoted text
Steve N4IRS
On 8/7/2020 3:48 PM, Perry Buch wrote:
Nope that was the problem. Audio both ways working as expected. Thanks!
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Perry Buch
Nope that was the problem. Audio both ways working as expected. Thanks!
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
That is the complete MMDVM_Bridge file?
toggle quoted messageShow quoted text
Have you set a static TG in BM selfecare for DMR ID 3168316?
On 8/7/2020 3:40 PM, Perry Buch wrote:
DVSwitch.ini
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Perry Buch
DVSwitch.ini
; Configure the DMR Partner ; Audio format is AMBE 72 bit [DMR] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 35100 ; Port to send AMBE TLV frames to (export) RXPort = 35103 ; Port to listen on (import) Slot = 2 ; Export slot
; Configure the Yaesu Fusion Partner ; Audio format is AMBE 72 bit ; Audio format is IMBE 88 bit [YSF] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 35103 ; Port to send AMBE TLV frames to (export) RXPort = 35100 ; Port to listen on (import) FallbackID = 3168316 ; In case we can not find a valid DMR id in the database, export this one ExportTG = 3168316 ; Which TG to export Slot = 2 ; Export slot [General] Callsign=KC2QJA Id=3168316 Timeout=180 Duplex=0 [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [DMR Network] Enable=1 Address=3102.repeater.net Port=62031 Jitter=360 Local=62032 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= Slot1=0 Slot2=1 Debug=0
[System Fusion Network] Enable=1 LocalAddress=0 LocalPort=3200 GatewayAddress=repeaters.as.utexas.edu GatewayPort=42000 Debug=0
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Perry Buch
I see no traffic on the Bridge when I key up, I see it on BM dashboard tho and the Hotspot is connected on my Dashboard.
Here are the more complete logs 2020-08-07 19:32:16.887 DMR, Opening DMR Network I: 2020-08-07 19:32:16.887 System Fusion Network Parameters I: 2020-08-07 19:32:16.887 Local Address: 0 I: 2020-08-07 19:32:16.887 Local Port: 3200 I: 2020-08-07 19:32:16.887 Gateway Address: repeaters.as.utexas.edu I: 2020-08-07 19:32:16.887 Gateway Port: 42000 I: 2020-08-07 19:32:16.887 Mode Hang: 3s M: 2020-08-07 19:32:16.945 Opening YSF network connection I: 2020-08-07 19:32:16.945 RSSI I: 2020-08-07 19:32:16.945 Mapping File: RSSI.dat W: 2020-08-07 19:32:16.945 Cannot open the RSSI data file - RSSI.dat I: 2020-08-07 19:32:16.945 DMR Id Lookups I: 2020-08-07 19:32:16.945 File: /var/lib/mmdvm/DMRIds.dat I: 2020-08-07 19:32:16.945 Reload: 24 hours W: 2020-08-07 19:32:16.945 Cannot open the DMR Id lookup file - /var/lib/mmdvm/DMRIds.dat I: 2020-08-07 19:32:16.945 DMR RF Parameters I: 2020-08-07 19:32:16.945 Id: 3168316 I: 2020-08-07 19:32:16.945 Color Code: 1 I: 2020-08-07 19:32:16.945 Self Only: no I: 2020-08-07 19:32:16.945 Embedded LC Only: yes I: 2020-08-07 19:32:16.945 Dump Talker Alias Data: no I: 2020-08-07 19:32:16.945 Prefixes: 0 I: 2020-08-07 19:32:16.945 Call Hang: 3s I: 2020-08-07 19:32:16.945 TX Hang: 3s I: 2020-08-07 19:32:16.945 Mode Hang: 10s M: 2020-08-07 19:32:16.945 DMR, Opening INI file: DVSwitch.ini M: 2020-08-07 19:32:16.945 DMR, Setting [DMR] Address -> 127.0.0.1 M: 2020-08-07 19:32:16.945 DMR, Setting [DMR] TXPort -> 35100 M: 2020-08-07 19:32:16.945 DMR, Setting [DMR] RXPort -> 35103 M: 2020-08-07 19:32:16.945 DMR, Setting [DMR] Slot -> 2 M: 2020-08-07 19:32:16.945 DMR, Transmitting on 127.0.0.1:35100 and listening on port 35103. Result = 1 I: 2020-08-07 19:32:16.945 YSF RF Parameters I: 2020-08-07 19:32:16.945 Low Deviation: no I: 2020-08-07 19:32:16.945 Remote Gateway: no I: 2020-08-07 19:32:16.945 Self Only: no I: 2020-08-07 19:32:16.945 DSQ: no I: 2020-08-07 19:32:16.945 Mode Hang: 10s M: 2020-08-07 19:32:16.945 YSF, Opening INI file: DVSwitch.ini M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] Address -> 127.0.0.1 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] TXPort -> 35103 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] RXPort -> 35100 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] FallbackID -> 3168316 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] ExportTG -> 3168316 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] Slot -> 2 M: 2020-08-07 19:32:16.945 YSF, Transmitting on 127.0.0.1:35103 and listening on port 35100. Result = 1 M: 2020-08-07 19:32:16.945 MMDVM_Bridge-20191105_V1.4.1 is running I: 2020-08-07 19:32:16.945 Started the DMR Id lookup reload thread M: 2020-08-07 19:32:26.970 DMR, Logged into the master successfully
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Show me your complete MMDVM_Bridge.ini and your complete
DVSwitch.ini
toggle quoted messageShow quoted text
On 8/7/2020 3:34 PM, Perry Buch wrote:
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
Perry Buch
root@localhost:/var/log/mmdvm# tail -f MMDVM_Bridge-2020-08-07.log M: 2020-08-07 19:32:16.945 YSF, Opening INI file: DVSwitch.ini M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] Address -> 127.0.0.1 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] TXPort -> 35103 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] RXPort -> 35100 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] FallbackID -> 3168316 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] ExportTG -> 3168316 M: 2020-08-07 19:32:16.945 YSF, Setting [YSF] Slot -> 2 M: 2020-08-07 19:32:16.945 YSF, Transmitting on 127.0.0.1:35103 and listening on port 35100. Result = 1 M: 2020-08-07 19:32:16.945 MMDVM_Bridge-20191105_V1.4.1 is running I: 2020-08-07 19:32:16.945 Started the DMR Id lookup reload thread M: 2020-08-07 19:32:26.970 DMR, Logged into the master successfully
|
|
Re: DMR to YSFn Bridge
#mmdvm_bridge
What do the logs say?
toggle quoted messageShow quoted text
On 8/7/2020 3:24 PM, Perry Buch wrote:
No ASL involved in this bridge.
|
|