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.
|
More weird testing
Just because,
We are ALPHA testing a software only P25 to analog bridge. For now it is connected to the North America MMDVM P25 reflector and outputting analog on AllStar node 2600 and Echolink N4IRS-L It is receive ONLY. There is still a lot of work to do. Steve N4IRS, Milke N4IRR -- "What is IMBE_Bridge?"
|
|
|
|
Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID
HB_Bridge does rewrite the repeater id. See dmr_utils/ambe_bridge.py lines 453-455
|
|
|
|
Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID
Matthew 2E0SIP
Hi Riku, As it happens I've been using HB_Bridge today. I've taken a look at the code, and HB_Bridge doesn't rewrite the RptrId, referred to as the radio_id in the code, but a 'master' will validate it on arrival to ensure its one of the connected clients. So the following is currently impossible-
|
|
|
|
Re: Analog Bridge and DStar
You may want to make sure ircDDBGateway is actually listening to the
network not on the localhost IP.
toggle quoted messageShow quoted text
On 11/19/2017 07:58 PM, Mike
Swiatkowski via Groups.Io wrote:
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
Steve, XRF and DCS don't seem to work on my end maybe due to a registration issue. I'm going to have to table this for a while... It's consuming way too much time (like 3 or 4 days now) and I have to spend time with family. Something is seriously flawed with that Dummy Repeater install and the ability for it to talk to the gateway on the same LAN. Thanks for your help. We'll chat again later. Mike, AA9VI
On Sunday, November 19, 2017, 9:49:20 AM CST, Steven Blackford <kb7sqi@...> wrote:
Hi Mike, Sorry for the delay in getting back to you. You need to do 2 things before compile DummyRepeater & install it. After you do your git pull, you need to make sure you copy the modified version of DummyRepeaterThread.cpp from the Analog_Bridge/DummyRepeater directory into the OpenDV/DummyRepeater/DummyRepeater/ Like so: kb7sqi@kb7sqi-odroid:~$ cd tmp/source/g4klx/OpenDV/DummyRepeater/ kb7sqi@kb7sqi-odroid:~/tmp/source/g4klx/OpenDV/DummyRepeater$ cp ~/tmp/source/n4irs/Analog_Bridge/DummyRepeater/DummyRepeaterThread.cpp DummyRepeater/DummyRepeaterThread.cpp You can make a backup of the original file first if you like. You have to have the modified version from Steve, N4IRS's git hub for this all to work. After you done that, then you need to configure DummyRepeater to include the ThumbDV/AmbeServer/Star*DV Support. Here's how you do that: ./configure --with-ambeserver --with-stardv This will include support for both the ThumbDV/DV3000 & the Star*DV Dongle. If you don't need the Star*DV Dongle, you can leave the --with-stardv off. If you want to use this on a PI, then you need to make sure you include ---with-gpio as well to support the PIDV Board. Once configure has ran, then go ahead & do your make, install it, etc. Make sure to read the Notes.txt file about this: The modified version of DummyRepeater will use the USRP channel driver from AllS tarLink (Just like Analog_Bridge) DummyRepeater will use the default UDP ports for TX and RX. It uses address 127. 0.0.1 as defined by the USRP channel driver. If you need to use other ports or addresses, you can define them in the enviorme nt before you start dummyrepeter. USRP_IP="127.0.0.1";export USRP_IP USRP_TXPORT=34001;export USRP_TXPORT USRP_RXPORT=32001;export USRP_RXPORT Now when you start DummyRepeater, do it with the --verbose option: $ dummyrepeater --verbose That will give you more info in your Dummy_Repeater Log that'll be in the user home directory from where you start DummyRepeater. When you start up DummyRepeater, it will complain if it can't connect to ircDDBGateway. Check your ircDDBGateway logs also. That should get you going in the right direction. If you have any further questions, let me know. Steve, K4SQI On Sun, Nov 19, 2017 at 12:54 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote: Maybe a better question would be what are the proper steps for compiling Dummy Repeater? I'm assuming ithey steps are at the bottom of this message that I copied and to launch with the command "dummyrepeater". Do I need to compile with the AMBE tag? Are there any special tricks with DummyRepeater and Jessie other than downloading the .deb and installing manually for
|
|
|
|
Re: Analog Bridge and DStar
Steven Blackford
Mike, You could also copy my file into place. Startup Dummy Repeater & edit the configuration to match your setup, change the call signs from K4SQI to yours, etc. Make sure the RPT 1 & RPT 2 settings are correct as well. You'll see mine is "K4SQI A" & "K4SQI G" Those are important to make sure you have the proper spacing etc. Make sure your ircDDBGateway config is also setup properly so it can communicate with Dummy Repeater. Let me know how it goes. If you need to, you can reach me on BM TG 31254. I always monitor that via D-Star/DMR/C4FM. Steve, K4SQI
On Sun, Nov 19, 2017 at 11:55 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote: I did what you said and here is the error log from Dummy Repeater. What does this mean? The 48000 rate seems odd. Why isn't it 460800? Still, the GUI is visually up but it really doesn't see any traffic or seem to do anything. --
|
|
|
|
Re: Analog Bridge and DStar
Steven Blackford
Mike, It don't look like you have your .Dummy Repeater config setup properly. Take a look @ the second one I sent you for my AllStar/EchoLink Node. Your's should look similar: kb7sqi@kb7sqi-x61:~$ tail -f DummyRepeater-2017-11-19.log I: 2017-11-19 17:52:08: AMBE Dongle type: 2, device: /dev/ttyUSB0, address: 192.168.0.248:2461 M: 2017-11-19 17:52:08: DV3000 chip identified as: AMBE3000R I: 2017-11-19 17:52:08: Soundcard set to hw:0,0 AD1984 Analog(HDA Intel):hw:0,0 AD1984 Analog(HDA Intel) M: 2017-11-19 17:52:09: Opened hw:0,0 hw:0,0 Rate 48000 I: 2017-11-19 17:52:09: Gateway set to 192.168.0.250:20010, local set to 192.168.0.238:20013 I: 2017-11-19 17:52:09: Controller set to , config: 1, PTT Inversion set to 0, Squelch Inversion set to 0 I: 2017-11-19 17:52:09: End bleep set to 0 M: 2017-11-19 17:52:09: Starting ALSA reader thread M: 2017-11-19 17:52:09: Starting ALSA writer thread M: 2017-11-19 17:52:09: Open network connection to USRP M: 2017-11-19 17:52:55: Header decoded - My: K4SQI /ID51 Your: CQCQCQ Rpt1: K4SQI G Rpt2: K4SQI A M: 2017-11-19 17:52:55: Begin exporting PCM M: 2017-11-19 17:52:55: End exporting PCM
On Sun, Nov 19, 2017 at 11:55 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote: I did what you said and here is the error log from Dummy Repeater. What does this mean? The 48000 rate seems odd. Why isn't it 460800? Still, the GUI is visually up but it really doesn't see any traffic or seem to do anything. --
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
I did what you said and here is the error log from Dummy Repeater. What does this mean? The 48000 rate seems odd. Why isn't it 460800? Still, the GUI is visually up but it really doesn't see any traffic or seem to do anything.
Mike : 2017-11-19 00:05:43: DV3000 chip identified as: AMBE3000R M: 2017-11-19 00:05:43: Opened hw:0,0 hw:0,0 Rate 48000 M: 2017-11-19 00:05:43: Starting ALSA reader thread M: 2017-11-19 00:05:43: Starting ALSA writer thread E: 2017-11-19 00:06:44: Error returned from sendto, err=22 E: 2017-11-19 00:07:44: Error returned from sendto, err=22 E: 2017-11-19 00:08:44: Error returned from sendto, err=22 M: 2017-11-19 00:09:23: DV3000 chip identified as: AMBE3000R M: 2017-11-19 00:09:23: Opened hw:0,0 hw:0,0 Rate 48000 M: 2017-11-19 00:09:23: Starting ALSA reader thread M: 2017-11-19 00:09:23: Starting ALSA writer thread M: 2017-11-19 00:10:19: DV3000 chip identified as: AMBE3000R M: 2017-11-19 00:10:19: Opened hw:0,0 hw:0,0 Rate 48000 M: 2017-11-19 00:10:19: Starting ALSA reader thread M: 2017-11-19 00:10:19: Starting ALSA writer thread M: 2017-11-19 00:10:24: Transmitting to - My: WX9NC /B Your: CQCQCQ Rpt1: WX9NC G Rpt2: WX$ E: 2017-11-19 00:10:24: Error returned from sendto, err=22 E: 2017-11-19 00:10:24: Error returned from sendto, err=22 E: 2017-11-19 00:10:24: Error returned from sendto, err=22
|
|
|
|
Re: Analog Bridge and DStar
Steven Blackford
Hi Mike, Sorry for the delay in getting back to you. You need to do 2 things before compile DummyRepeater & install it. After you do your git pull, you need to make sure you copy the modified version of DummyRepeaterThread.cpp from the Analog_Bridge/DummyRepeater directory into the OpenDV/DummyRepeater/DummyRepeater/ Like so: kb7sqi@kb7sqi-odroid:~$ cd tmp/source/g4klx/OpenDV/DummyRepeater/ kb7sqi@kb7sqi-odroid:~/tmp/source/g4klx/OpenDV/DummyRepeater$ cp ~/tmp/source/n4irs/Analog_Bridge/DummyRepeater/DummyRepeaterThread.cpp DummyRepeater/DummyRepeaterThread.cpp You can make a backup of the original file first if you like. You have to have the modified version from Steve, N4IRS's git hub for this all to work. After you done that, then you need to configure DummyRepeater to include the ThumbDV/AmbeServer/Star*DV Support. Here's how you do that: ./configure --with-ambeserver --with-stardv This will include support for both the ThumbDV/DV3000 & the Star*DV Dongle. If you don't need the Star*DV Dongle, you can leave the --with-stardv off. If you want to use this on a PI, then you need to make sure you include ---with-gpio as well to support the PIDV Board. Once configure has ran, then go ahead & do your make, install it, etc. Make sure to read the Notes.txt file about this: The modified version of DummyRepeater will use the USRP channel driver from AllS tarLink (Just like Analog_Bridge) DummyRepeater will use the default UDP ports for TX and RX. It uses address 127. 0.0.1 as defined by the USRP channel driver. If you need to use other ports or addresses, you can define them in the enviorme nt before you start dummyrepeter. USRP_IP="127.0.0.1";export USRP_IP USRP_TXPORT=34001;export USRP_TXPORT USRP_RXPORT=32001;export USRP_RXPORT Now when you start DummyRepeater, do it with the --verbose option: $ dummyrepeater --verbose That will give you more info in your Dummy_Repeater Log that'll be in the user home directory from where you start DummyRepeater. When you start up DummyRepeater, it will complain if it can't connect to ircDDBGateway. Check your ircDDBGateway logs also. That should get you going in the right direction. If you have any further questions, let me know. Steve, K4SQI
On Sun, Nov 19, 2017 at 12:54 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote: Maybe a better question would be what are the proper steps for compiling Dummy Repeater? I'm assuming ithey steps are at the bottom of this message that I copied and to launch with the command "dummyrepeater". Do I need to compile with the AMBE tag? Are there any special tricks with DummyRepeater and Jessie other than downloading the .deb and installing manually for --
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
it compiled fine sans the linwxbase and libgtk needing to be > 3.0 so I found the debian packages and installed them. Then the compiling and install went fine. But, the issue is that the dummy repeater does not work. I'm not sure why. Is the a problem with running dummyrepeater on one box and having ircddbgateway on another, even though the gateway is specified properly on the first box?
Mike
|
|
|
|
Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID
OH1E Riku
i have this exact same problem.
i try create a small dmr network, but sending frames to masters are filtered because the radio id. what lines did you exacly changed to it accept any id? you can recreate this problem very easly you need to hotspots. create a master and parrot. configure them working propelly. then connect with one more client who has different id than firstone, the parrot will filter them. this issue is on hblink aswell it will filter them if you sending trafic between masters..
|
|
|
|
Re: DVMega AMBE3000
Matthew 2E0SIP
Hi all, Just a heads up I've modified AMBESever to allow Analog_Bridge to work with the DVMEGA AMBE3000, by sending a PKT_RESETSOFTCFG rather than a PKT_RESET. This forces it into the packet mode that Analog_Bridge expects rather than codec mode. I'm currently testing and its working nicely, however G7RPG had issues - his AMBE board seems to be chucking out none AMBE frames and won't respond to the reset. The code is available here- https://github.com/marrold/AMBEServer I am not very experienced with C so any feedback - good or bad would be appreciated. The Makefile is a particular mystery to me, but seems to work. Cheers
|
|
|
|
Re: Analog Bridge and DStar
Ryan Collier
Mike, what errors are you getting when you compile?
On Nov 19, 2017 12:54 AM, "mjswiatk via Groups.Io" <mjswiatk=yahoo.com@groups.io> wrote: Maybe a better question would be what are the proper steps for compiling Dummy Repeater? I'm assuming ithey steps are at the bottom of this message that I copied and to launch with the command "dummyrepeater". Do I need to compile with the AMBE tag? Are there any special tricks with DummyRepeater and Jessie other than downloading the .deb and installing manually for
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
Maybe a better question would be what are the proper steps for compiling Dummy Repeater? I'm assuming ithey steps are at the bottom of this message that I copied and to launch with the command "dummyrepeater". Do I need to compile with the AMBE tag? Are there any special tricks with DummyRepeater and Jessie other than downloading the .deb and installing manually for
libwxbase2.8-0_2.8.12.1+dfsg2-dmo4_amd64.deb libwxgtk2.8-0_2.8.12.1+dfsg2-dmo4_amd64.deb My ircddbgateway is at 10.1.1.31 My Dummy is at 10.1.1.2 I set repeater 2 in gateway as Dummy and 10.1.1.2 I set Dummy gateway as 10.1.1.31... I'm missing something...
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
Steve, Thanks for the files. I think my Dummy repeater is not working at all. I am running Dummy on Jessie and the ircddbgateway on another wheezy box. It seems to be similar to what you have done but the dummy repeater isn't seeing the gateway. I configured the Dummy inside the gateway as both homebrew and dummy and I don't see it working in either way. How can I best test the dummy repeater to see if it is working correctly?
Mike
|
|
|
|
Re: Analog Bridge and DStar
Steven Blackford
Mike, Just to make sure you have everything I that I have setup. I've also attached my ircddbgateway & the Dummy Repeater config file I have setup on a seperate computer running an AllStar/Echolink node w/ out a radio attached. Again this is connected to D-Star on DCS054B using an x86 system & a ThumbDV. I'll fully admit that I'm an AllStar newb. I was looking for a way to add in EchoLink to our Link system so I could monitor things & listen while I was working in Datacenters @ night. I attemped to get have a working AllStar Node & have my DMR<->D-Star bridge working on the same computer, but I couldn't figure out how to get the audio to pass from both DMR/D-Star over to EchoLink & vice versa. I could only get one side working. If some one else has any ideas on that, I'd love to hear them! :-) Again feel free to ask questions. I'll do my best to help out. 73 de K4SQI This computer's IP is 192.168.0.238. Again, I have my ircDDBGateway configured on a PI3 @ 192.168.0.250. The "A" Module is setup for D-Star going to the AllStar/EchoLink Node. "B" Module is my 440 DVAP. Then my "D" module is used for the D-Star<->DMR Bridge on the ODroid @ 192.168.0.240. Here's my config files. The Dummy Repeater config files are placed in what ever User home directory you're starting the dummy repeater software. The file should be named ".Dummy Repeater" It's a hidden file. Steve
On Sat, Nov 18, 2017 at 2:05 PM, mjswiatk via Groups.Io <mjswiatk@...> wrote: How to I configure Analog Bridge to communicate with ircddbgateway? I am using a DV3000 usb dongle. --
|
|
|
|
Re: Analog Bridge and DStar
Steven Blackford
Mike, I've attached my copies of my working config files that I use to create a full time bridge between D-Star<->DMR on BM TG 31254 and DCS054B. This has been working solidly for over a month now. If you have any questions, feel free to ask. Steve, N4IRS helped me get this up & running when I first started looking at creating a new bridge. I can't thank him enough. LOL I use this setup on an ODroid C1 w/ a PIDV setup on /dev/ttyS2 which is the GPIO board and then I have one of the Original DV-Dongle's on /dev/ttyUSB. The ODroid's IP address is 192.168.0.240. Since I already have ircDDBGateway running on a different device controlling my 440 DVAP, I just added a second "repeater" in the ircDDBGateway Config. ircDDBGateway is running on a PI3 w/ the IP of 192.168.0.250 and is configured to automatically connect to DCS054B on start up & if it gets disconnected. Hopefully that explains everything w/ enough detail. Again, if you have any questions, feel free to ask. :-) 73 de K4SQI!
On Sat, Nov 18, 2017 at 4:14 PM, Steven Blackford <kb7sqi@...> wrote:
--
|
|
|
|
Re: Analog Bridge and DStar
Steven Blackford
Mike, I'm happy to give you some help. I have the exact setup running & it works great. I can email you my configs here shortly to help get you started. :-) Steve
On Sat, Nov 18, 2017 at 4:08 PM, Steve N4IRS <szingman@...> wrote:
--
|
|
|
|
Re: Analog Bridge and DStar
Mike,
toggle quoted messageShow quoted text
You do not need Analog bridge if you are trying to connect D-Star with AllStarLink. The modified version of DummyRepeater will talk directly to the USRP channel driver in ASL. Steve N4IRS
On 11/18/2017 02:05 PM, mjswiatk via
Groups.Io wrote:
How to I configure Analog Bridge to communicate with ircddbgateway? I am using a DV3000 usb dongle.
|
|
|
|
Analog Bridge and DStar
Mike, AA9VI
How to I configure Analog Bridge to communicate with ircddbgateway? I am using a DV3000 usb dongle.
I have a few questions. 1) How do I configure Analog_Bridge.ini to allow ircddbgateway and dummy repeater to speak to analog bridge? The file is fairly straight-forward for DMR, but I want to interface with DStar. Does anyone have a sample file? 2) I get the error "cannot open the sound card" when I load dummyrepater. What I am doing wrong? I followed these directions: https://github.com/N4IRS/Analog_Bridge/blob/master/DummyRepeater/Notes.txt But, this does not seem to be adequate in explaining what else I need to do. Under Dummy Repeater--> Edit--> Preferences--> sound card I chose input and output to be the Dummy PCM. Under Dongle I chose DV3000 serial., /dev/ttyUSB0, and speed 460800. What do I choose for controller? Why would I get this error? thanks much, Mike, AA9VI
|
|
|