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: Analog_Bridge and tune.sh script
#analog_bridge
SP2ONG Waldek
I have use part of your script tune.sh where is:
_sock.sendto(cmd, ('127.0.0.1', 31100))
|
|
Re: Analog_Bridge and tune.sh script
#analog_bridge
Are you sending the tune command to AB or MB?
toggle quoted messageShow quoted text
On 7/10/2019 10:44 AM, Waldek SP2ONG
wrote:
This happens when the mmdv_bridge restart is done and then this script will be used
|
|
Re: Analog_Bridge and tune.sh script
#analog_bridge
I don't restart MB. I keep all modes enabled and restart AB with the
proper mode enabled.
toggle quoted messageShow quoted text
On 7/10/2019 10:44 AM, Waldek SP2ONG
wrote:
This happens when the mmdv_bridge restart is done and then this script will be used
|
|
Re: Analog_Bridge and tune.sh script
#analog_bridge
I'll have to test this.
toggle quoted messageShow quoted text
On 7/10/2019 10:44 AM, Waldek SP2ONG
wrote:
This happens when the mmdv_bridge restart is done and then this script will be used
|
|
Re: Analog_Bridge and tune.sh script
#analog_bridge
SP2ONG Waldek
This happens when the mmdv_bridge restart is done and then this script will be used
|
|
Re: Analog_Bridge and tune.sh script
#analog_bridge
I have not seen this happen.
toggle quoted messageShow quoted text
On 7/10/2019 3:30 AM, Waldek SP2ONG
wrote:
Hi Steve
|
|
Analog_Bridge and tune.sh script
#analog_bridge
SP2ONG Waldek
Hi Steve
I use the attached tuns.sh script to switch groups in Ananlog_Bridge. This script is a part of your tune.sh script. Sometimes it happens that after using this script, the repeaterID gatewayDmrId is reset to 0 As a result, when it is transmits by AB on the new talk group, the DMRID for source and transmiter is 0 I do not know if you also had such situations? 73 Waldek
|
|
Re: DMRlink to Motorola Mastger
#dmrlink
Please review this article in the wiki for DMRLink to Brandmeister. Steve KC1AWV
On Tue, Jul 9, 2019 at 6:01 PM KK4zmg <kk4zmg@...> wrote: Ok i have got it talking to my Motorola master. -- Steve Miller KC1AWV
|
|
Re: DMRlink to Motorola Mastger
#dmrlink
KK4zmg
Ok i have got it talking to my Motorola master.
Now im trying to get Dmrlink to connect with brandmiester. This is what I have for configuration. [bm]
ENABLED: True
RADIO_ID: 311078
IP:
PORT: 5000
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 64.94.238.196
MASTER_PORT: 55001
GROUP_HANGTIME: 5 That repeater number is setup in brandmiester as a repeater and linked to my dash board. Any help would be great. Thanks kk4zmg Richard
|
|
Re: Trying to set up Parrot
Thank you for sharing Jesse!
On Mon, Jul 8, 2019 at 4:51 AM Jesse Neu via Groups.Io <parkrangersteve=yahoo.com@groups.io> wrote: There is very little in the way of documentation on setting up parrot and it took me two weeks to figure out you have to run separate config files. I finally got it working on my master server and I thought I would share a short how to on getting it up and running.
|
|
Re: Trying to set up Parrot
Jesse Neu
There is very little in the way of documentation on setting up parrot and it took me two weeks to figure out you have to run separate config files. I finally got it working on my master server and I thought I would share a short how to on getting it up and running.
Enjoy Parrot Example Parrot or Echo Test functions as a separate Master server. To set up Parrot on the same server as your current master you will need to either copy the HBlink directory to run a second instance or point hb_parrot.py to a secondary configuration file. Configuring hblink.cfg In your Configuration file called by hb_parrot.py you will need the following master configured [Parrot-1] #Can be anything you want, Naming in this file isn't important MODE: MASTER ENABLED: True REPEAT: True MAX_PEERS: 10 EXPORT_AMBE: False IP: PORT: 54000 #Remember this port number, you'll need it later PASSPHRASE: s3cr37w0rd #You'll need this too GROUP_HANGTIME: 5 USE_ACL: True REG_ACL: DENY:1 SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL In your primary configuration called by hb_confbridge.py you will need to have the following PEER configured [Parrot-1] #Can be anything you want, You'll need this later MODE: PEER ENABLED: True LOOSE: False EXPORT_AMBE: False IP: PORT: 54001 MASTER_IP: 127.0.0.1 #loopback is fine if you are running both master and parrot on the same server MASTER_PORT: 54000 #Same port as before PASSPHRASE: s3cr37w0rd #Must match password for our Parrot-1 Master above CALLSIGN: W1ABC #Your callsign RADIO_ID: 312000 #Your RadioID RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 1 LATITUDE: 38.0000 LONGITUDE: -095.0000 HEIGHT: 75 LOCATION: Anywhere, USA DESCRIPTION: This is a cool repeater URL: www.w1abc.org SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 OPTIONS: USE_ACL: True SUB_ACL: DENY:1 TGID_TS1_ACL: PERMIT:ALL TGID_TS2_ACL: PERMIT:ALL Now we need to conference them together. For simplicity I will only include the relevant block. Make sure the 'SYSTEM' matches both Master and Peer exactly, put them both in the same time slot and talk group. 'ECHOTEST': [ {'SYSTEM': 'MASTER-1', 'TS': 1, 'TGID': 9998, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [3,], 'OFF': [8,10], 'RESET': []}, {'SYSTEM': 'PARROT-1', 'TS': 1, 'TGID': 9998, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [3,], 'OFF': [8,10], 'RESET': []}, ], Start hb_confbridge.py and parrot.py with their respective config files and everything should work!
|
|
Analog_Bridge and local voice services
#analog_bridge
SP2ONG Waldek
Steve,
I really like the potential of Ananlog_bridge. I would like to launch an information service locale using the restored information in wav files. On the ananlog we can use DTMF to start playing different information. In the case of DMR, only on the basis of the target ID number, we can run, for example, a macro. Would it be possible for Steve to get Ananlog_Bridge if he receives data from the DMR network eg in the field dst = for example it will be 940 (dst = 940) then AB will execute the macro defined as 940? Suppose that TG900 is for voice services Makro 910 (current weather report): # change to TG900 tune 900 # playing the wav file 900.wav via a script 940.py Makro 920 (local newsletter): tune 900 941.py e.t.c Would this require changes in Ananlog_Bridge but a separate version? What do you think about such an idea?
|
|
Re: Analog_Bridge and Received USRP packet of wrong size
It looks like the last frame of the file is "short" not 320 bytes.
toggle quoted messageShow quoted text
On 7/7/19 12:11 PM, Waldek SP2ONG
wrote:
Ok when I have comment outt 57 - 60 now
|
|
Re: Analog_Bridge and Received USRP packet of wrong size
SP2ONG Waldek
Ok when I have comment outt 57 - 60 now
M: 2019-07-07 16:06:42.939 PTT on W: 2019-07-07 16:07:36.781 Received USRP packet of wrong size D: 2019-07-07 16:07:36.802 cpu_time_used = 53863, minTxTime = 2000, pttTime = 3442474491, end = 3442528354 M: 2019-07-07 16:07:36.802 PTT off (keyed for 53863 ms) no warning before "PTT on" message but still after PTT on
|
|
Re: Analog_Bridge and Received USRP packet of wrong size
In lines 57 through 60 it looks like you are trying to assert a PTT.
It is not needed, the sending of audio with the PTT flag on will
assert PTT. Try commenting out 57 through 60.
toggle quoted messageShow quoted text
On 7/7/19 8:20 AM, Waldek SP2ONG wrote:
Hi Steve,
|
|
Analog_Bridge and Received USRP packet of wrong size
SP2ONG Waldek
Hi Steve,
We use MB / AB with an attached script to play information emcom every hour, if the file info.wav exists in the directory. Generally everything works, but in the Analog_Bridge log I saw the information "Received USRP packet of wrong size". I would like to know the reason for this message and eliminate this problem. I: 2019-07-07 08:14:31.913 Starting USRP --> Analog_Bridge (encoder) -> TLV thread W: 2019-07-07 08:15:00.949 Received USRP packet of wrong size M: 2019-07-07 08:15:00.949 PTT on W: 2019-07-07 08:15:41.680 Received USRP packet of wrong size D: 2019-07-07 08:15:41.708 cpu_time_used = 40759, minTxTime = 2000, pttTime = 1562487300949, end = 1562487341708 M: 2019-07-07 08:15:41.708 PTT off (keyed for 40759 ms) 73 Waldek
|
|
Re: MMDVM_Bridge and HBLink3 missing CALL END
david bencini ik5xmk
Hi Steve and all,
for completeness of information ( MMDVM_Bridge/DOC/DMRplus_startup_options.md ), the line Options= in DMR+ for startup also accepts the configuration for SLOT 2 in this way: Options=StartRef=4013;RelinkTime=15;UserLink=1;TS1_1=262;TS1_2=1;TS1_3=20;TS1_4=110;TS1_5=270;TS2_1=2241;TS2_2=22251;TS2_3=;TS2_4=;TS2_5=; Thank you all for your wonderful work. 73, David IK5XMK (sysop of IT-MLINK DMRPlus Network)
|
|
Re: HBlink3 DMR server to Motorola repeater
toggle quoted messageShow quoted text
On 7/3/19 9:29 PM, area51now via
Groups.Io wrote:
Thank you for the quick reply what would be the appropriate group to talk about this, DVswitch openbridge? just looking for a little direction on getting this running.
|
|
Re: HBlink3 DMR server to Motorola repeater
area51now@...
Thank you for the quick reply what would be the appropriate group to talk about this, DVswitch openbridge? just looking for a little direction on getting this running.
Thank you Bob KB6LED
|
|
Re: HBlink3 DMR server to Motorola repeater
You should ask your question in the HBlink subgroup. That being
said, you will need HB_Bridge and IPSC_Bridge from here. <https://github.com/n0mjs710/HBlink/tree/HB_Bridge>
and here <https://github.com/n0mjs710/DMRlink/tree/IPSC_Bridge>
Your flow diagram will look like this:
toggle quoted messageShow quoted text
SLR5700 <-> IPSC_Bridge <-> HB_Bridge <-> HBlink3 73, Steve N4IRS
On 7/3/19 9:02 PM, area51now via
Groups.Io wrote:
HI all I am not sure I am in the right spot to ask but ill try. I have successfully have the HBlink3 for DMR up and running and I can access via my MMVM hotspot to Branmister and TGIF I would like to
|
|