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.
Just to make sure, you *do* have template.bin in the dmrlink directory, right?
Can you look back at the start of your log for any error message like:
Can not open template.bin file
Mike
Just to make sure, you *do* have template.bin in the dmrlink directory, right?
Can you look back at the start of your log for any error message like:
Can not open template.bin file
Mike
Vance,
I am chasing it now. Just to be clear:
hb_routing_rules are not used by basic HB to IPSC. Just HB_Bridge and IPSC_Bridge
It looks like this:
MMDVM <---> HB_Bridge <--->
Vance,
I am chasing it now. Just to be clear:
hb_routing_rules are not used by basic HB to IPSC. Just HB_Bridge and IPSC_Bridge
It looks like this:
MMDVM <---> HB_Bridge <--->
I am running HB_Bridge and IPSC_Bridge and have upgraded the dmr_utils. I have one TG routed both ways in hb_routing_rules.py and hb_routing_rules.py. HB_Bridge.cfg the TG has been added.
I can
I am running HB_Bridge and IPSC_Bridge and have upgraded the dmr_utils. I have one TG routed both ways in hb_routing_rules.py and hb_routing_rules.py. HB_Bridge.cfg the TG has been added.
I can
screen is a program that you can run up front and then disconnect from it as needed and still keep the software running. It is the same way you can autostart mmdvm. This is totally different from
screen is a program that you can run up front and then disconnect from it as needed and still keep the software running. It is the same way you can autostart mmdvm. This is totally different from
There were multiple copies of hblink.py running. I ran both with no problem. You should look into the program called "screen" so you can run a program in the foreground and if the connection
There were multiple copies of hblink.py running. I ran both with no problem. You should look into the program called "screen" so you can run a program in the foreground and if the connection
All is up to date...No difference. it doesn't crash IPSC_Bridge just logs to console. I still cant TX from client to MASTER but can hear traffic on TG through the client (MMDVM). I will keep looking
All is up to date...No difference. it doesn't crash IPSC_Bridge just logs to console. I still cant TX from client to MASTER but can hear traffic on TG through the client (MMDVM). I will keep looking
One connection can drop and the other can stay open. IPSC_Bridge stopping would not close the session.
And, if you are going to run it in the foreground, just run python IPSC_Bridge.py
One connection can drop and the other can stay open. IPSC_Bridge stopping would not close the session.
And, if you are going to run it in the foreground, just run python IPSC_Bridge.py