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: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
That's fine with me, I will start over.
Where, in the install steps that you list, should the dependencies and dmr_utils be installed?
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Cort N0MJS <n0mjs@...>
It’s all python. Outside of shell scripts, the variation of Linux won’t matter. I wrote it all on MacOS and run it in production on Debian, raspbian and Ubuntu.
toggle quoted messageShow quoted text
Nothing should be limiting in any way on any Unix-like os.
On Jan 2, 2019, at 2:53 PM, Steve N4IRS <szingman@...> wrote:
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
I can't tell you what OS flavor to use. I just don't trust your
python environment. All I can tell you is I run Mint on my desktop
and pure Debian on my servers. YMMV
toggle quoted messageShow quoted text
On 1/2/2019 3:49 PM, Jason Johnston
wrote:
This is a fresh start from the software itself, but not the OS. Is that what you are referring to?
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
Here is the result of that command, running with SUDO
jape@josephus:/opt/dmrlink/HBlink$ sudo pip show dme_utils
The directory '/home/jape/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Steve, in your reply #2727, there is nothing about installing dmr_utils or dependencies. If I am going to start over with a new OS, where do these steps fall in the process?
|
|
Re: P25<-->DMR issue "Still"
Ian Tulley
Thanks Steve, will give that a try soon.
toggle quoted messageShow quoted text
------------------ Regards Ian (VK2HK)
|
|
Re: P25<-->DMR issue "Still"
Set the USRP audio settings in BOTH ini files to:
toggle quoted messageShow quoted text
aslAudio = AUDIO_USE_GAIN agcGain = 1.0 dmrAudio = AUDIO_USE_GAIN dmrGain = 1.0 From there you can go up to 1.5,2,etc or down .9,.8,etc.
On 1/2/2019 3:46 PM, Ian Tulley wrote:
Hi Steve, if I do systemctl status md380-emu it shows it as running, if I TX from the P25 radio, I get very broken audio out of the DMR, if I TX from the DMR Radio I just get very harsh hash from the P25 Radio, that was with the USRP Audio settings as per default. I am assuming I will need to adjust those on both of the Analog_Bridge ini files ??
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
This is a fresh start from the software itself, but not the OS. Is that what you are referring to?
I am running this on Ubuntu 16.04 LTS. Is there any reason this wouldn't work? In reading online forums, facebook groups, etc - and talking with several people who are using their own DMRlink/HBlink server, I get mixed opinions about whether Ubuntu will work or not. It is a Debian based OS, but different enough that some say it won't work, even though it works on Raspian, which is much more watered-down than what I am running. If I am going to start fresh all over again, what OS do you recommend I start with? It can be anything, I don't care, I just want to know what works best.
|
|
Re: P25<-->DMR issue "Still"
Ian Tulley
Hi Steve, if I do systemctl status md380-emu it shows it as running, if I TX from the P25 radio, I get very broken audio out of the DMR, if I TX from the DMR Radio I just get very harsh hash from the P25 Radio, that was with the USRP Audio settings as per default. I am assuming I will need to adjust those on both of the Analog_Bridge ini files ??
toggle quoted messageShow quoted text
I have not done any as yet this morning, but will be looking at it hopefully in the next hour. ------------------ Regards Ian (VK2HK)
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
OK,
toggle quoted messageShow quoted text
I'm confused here is my result root@orangepipc:~# pip show dmr_utils Name: dmr-utils Version: 0.1.19 Summary: ETSI DMR (Digital Mobile Radio) Tier II Utilities Home-page: https://github.com/n0mjs710/dmr_utils Author: Cortney T. Buffington, N0MJS Author-email: n0mjs@... License: GPLv3 Location: /usr/local/lib/python2.7/dist-packages Requires: bitstring, bitarray I'm out of answers. Best I can tell you at this point is to start fresh. At least that is what I would do. Steve
On 1/2/2019 3:41 PM, Jason Johnston
wrote:
My MMDVM hotspot is connecting to my server via the HBlink.cfg file. I show it is connected now. I am running both the hotspot and the HBlink server here on my home network, so I just have it connecting to an internal IP, but it seems to be working.
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
My MMDVM hotspot is connecting to my server via the HBlink.cfg file. I show it is connected now. I am running both the hotspot and the HBlink server here on my home network, so I just have it connecting to an internal IP, but it seems to be working.
Here is the cmd you asked for: jape@josephus:/opt/dmrlink/HBlink$ pip show dmr_utils
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
What is the result of:
toggle quoted messageShow quoted text
pip show dmr_utils
On 1/2/2019 3:23 PM, Jason Johnston
wrote:
OK got that done, trying to run the dmrlink.py in the foreground, getting this message below - it doesn't appear to be connecting to the cbridge yet. I haven't tried the hblink connection yet.
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
OK got that done, trying to run the dmrlink.py in the foreground, getting this message below - it doesn't appear to be connecting to the cbridge yet. I haven't tried the hblink connection yet.
toggle quoted messageShow quoted text
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
That is the foreground.
toggle quoted messageShow quoted text
On 1/2/2019 2:54 PM, Jason Johnston
wrote:
how do I run it in the foreground to watch it?
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
how do I run it in the foreground to watch it?
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
python name_of_program.py
toggle quoted messageShow quoted text
On 1/2/2019 2:42 PM, Jason Johnston
wrote:
I've already done all of that, about a year ago upon initial setup, but it seems some things have changed since then. I will remove all of my current installs and start from scratch.
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
I've already done all of that, about a year ago upon initial setup, but it seems some things have changed since then. I will remove all of my current installs and start from scratch.
A couple of questions, though: How do you start *.py files and how do I run it in the foreground to watch it?
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
If you are trying to connect a HB based system (MMDVM) to your
c-Bridge
toggle quoted messageShow quoted text
You will need the 2 branches: https://github.com/n0mjs710/DMRlink/tree/IPSC_Bridge https://github.com/n0mjs710/HBlink/tree/HB_Bridge You can put all the files in the same directory. Build from the outside in. That way you can see the traffic flow as you add a program. Configure dmrlink.cfg to login to your c-Bridge as a peer Configure hblink as a server for your repeater run dmrlink and verify it is logging into the c-Bridge run hblink and verify your MMDVM repeater is logging in. These are just for TESTING your configs. Configure HB_Bridge.cfg and IPSC_Bridge.cfg to talk to each other. (cross UDP ports) Start IPSC_Bridge.py You should see it login to your c-Bridge Start HB_Bridge.py You should see your MMDVM Repeater login to it. If you have the HB_Bridge.cfg and IPSC_Bridge.cfg correct, you should see traffic flow. While building, run everything in the foreground so that you can watch the logs in real time. Make sure you see the traffic before moving on. Steve N4IRS
On 1/2/2019 2:22 PM, Jason Johnston
wrote:
I was able to get it downgraded and I ran the pip install dmr_utils cmd again, and it seems to work - although it says I have everything that I need
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
I was able to get it downgraded and I ran the pip install dmr_utils cmd again, and it seems to work - although it says I have everything that I need
I DID do the upgrade manually, since the OS prompted me to do that, so having a line in your instructions, saying to avoid this, would be helpful. Now that I have that done, what would be the next step to get it to actually connect to the cbridge? This Ubuntu box is a test box, we can do anything we want to do, and aren't going to lose anything. Fire away.
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Cort N0MJS <n0mjs@...>
I STRONGLY recommend that if you need to update outside of what your distribution package maintainer uses that you use a python virtualenv (virtual environment). And this stuff is getting way outside of what I’m comfortable providing support on really quickly.
Cort Buffington 785-865-7206
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Cort know much more about python then I do but I did find this:
toggle quoted messageShow quoted text
<https://stackoverflow.com/questions/49836676/error-after-upgrading-pip-cannot-import-name-main> See number 402 and also <https://github.com/pypa/pip/issues/5221>
On 1/2/2019 2:05 PM, Jason Johnston
wrote:
Here is a cat cmd from the file referenced in the error"
|
|