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).
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) WHEREAS47 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.
Not sure but maybe this msg should say "net queue" ? Have not yet studied this code enough...https://github.com/g4klx/MMDVMHost/blob/master/P25Control.cpp#L766
Also.... this number may grow too
Not sure but maybe this msg should say "net queue" ? Have not yet studied this code enough...https://github.com/g4klx/MMDVMHost/blob/master/P25Control.cpp#L766
Also.... this number may grow too
I have not yet forked and patched Jonathan's code. Here is the change to P25Network.cpp Let me know results.
void CP25Network::clock(unsigned int ms)
{
unsigned char
I have not yet forked and patched Jonathan's code. Here is the change to P25Network.cpp Let me know results.
void CP25Network::clock(unsigned int ms)
{
unsigned char
So,
I have had NO response from anyone who can test a change to MMDVMHost. I'll make it a little easier. I will provide a ARM or x86 binary. I can't provide a binary for anyone running Pi-Star at this
So,
I have had NO response from anyone who can test a change to MMDVMHost. I'll make it a little easier. I will provide a ARM or x86 binary. I can't provide a binary for anyone running Pi-Star at this
Steve,
Don't quite understand what you mean. Not from a Linux background and my knowledge is very limited. Sorry for that.
I tried to add one more TG in the macro D script, and it failed to
Steve,
Don't quite understand what you mean. Not from a Linux background and my knowledge is very limited. Sorry for that.
I tried to add one more TG in the macro D script, and it failed to
Steve,
To answer your question, the latest version of MMDVM_Bridge (V1.6.8) installed to /opt/MMDVM_Bridge.
dvswitch.sh is in /opt/Analog_Bridge not in /opt/MMDVM_Bridge so it is in one location
Steve,
To answer your question, the latest version of MMDVM_Bridge (V1.6.8) installed to /opt/MMDVM_Bridge.
dvswitch.sh is in /opt/Analog_Bridge not in /opt/MMDVM_Bridge so it is in one location
One suggestion, DVSwitch.ini should need little to no modification. You will be editing the AB ini files so, make your changes there and leave DVswitch.ini stock.
Steve
One suggestion, DVSwitch.ini should need little to no modification. You will be editing the AB ini files so, make your changes there and leave DVswitch.ini stock.
Steve
Great diagram! Think I saw that at one point early on and forgot about it. I think I'm armed with the tools I need to figure this out. Still learning and even though this is challenging
Great diagram! Think I saw that at one point early on and forgot about it. I think I'm armed with the tools I need to figure this out. Still learning and even though this is challenging
Thanks Steve (again!) Starting to make a little more sense now. Was following some loose instructions that didn't mention two instances of MMDVM_Bridge being needed. And I also don't remember
Thanks Steve (again!) Starting to make a little more sense now. Was following some loose instructions that didn't mention two instances of MMDVM_Bridge being needed. And I also don't remember
OK,
So we know the macro is firing the script. Macros A B and C run
The MMDVM_Bridge install moved dvswitch.sh from /opt/Analog_Bridge to /opt/MMDVM_Bridge Do you have it in both
OK,
So we know the macro is firing the script. Macros A B and C run
The MMDVM_Bridge install moved dvswitch.sh from /opt/Analog_Bridge to /opt/MMDVM_Bridge Do you have it in both