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: more: not connecting to BM any more
OK - so I probably made a typo in the frequency. Complicated by the unwanted ini changes from the update.
If I understand then, DVSwitch looks like a simplex hot spot from the BM side. So you have to tell BM you are a simplex node, even if you are a repeater (at least until some fix is implemented). Can you clarify if the ID in the [General] stanza should be CCS7 or the 9-digit CCS7+2 or does it matter? The DVSwitch dashboard shows both numbers. 7-digits for GW ID and 9-digits for RPT ID. (That is coming from AB I guess). Am I to understand that MMDVM_Bridge, in addition to its protocol translation function, is also a DMR gateway? (or perhaps DMR does not need a gateway)? Thanks Ken PS I fixed the DSTAR error message by killing ircgatewayd and setting DSTAR enable=0 in MMDVM I suspect the error was due to a conflict with the actual DSTAR repeater that I run at the same public IP.
|
|
|
|
hytera USB packet structure
Kev
Hello everybody,
I've spent the last couple of months reading through the etsi documents trying to figure out the packet structure of the 'forward to pc' option on a hytera radio. Having done some detective work and comparing packets I can decode radio ID, LLID, and extract SMS data by bit bashing. I would prefer to actually understand the whole packet structure so I can decode it properly rather than blindly extracting the useful data. The packet does at first appear to be a standard etsi packet, containing all the blocks. The issue I'm having is the documents and all open source software I can find deal with the air side blocks, not a network packet. Take for example the first 8 bits in the packet : "00001001", which could be any of the following : 1) 1001 = Idle Data 2) Privacy Flag=0, Reserved Flag=0 and FLCO=001001 making up the first line in a Full LC header. 3) 001001=8 bit ISO/IEC 8859-7 4) 1001 = SAP 9 = Short Data Services over PDP Without figuring out some basics, like blocktype I can't work out which interleaving to use (bptc, hamming etc) Then there is the LLID. All ETSI documents say it should be 24bits+24bits, but I see the CAI in each address making it 28 or 32 bits for each. I've attached a text file with some example recieved data split into colums to make comparision easier for myself. Im not asking for a full packet decode (although I wouldn't say no!), just a push in the right direction on how to figure out the packet type (It must be the first thing transmitted right?) I realise this isn't a DVSwitch question, but I cant think of a more knowledgeable group of people on the DMR protocol. If you think there would be a better place to ask this, please let me know! Thank you for taking the time to read this, I really hope you can help. Regards Kev
|
|
|
|
Re: Registration of Dv Switch
OK,
toggle quoted messageShow quoted text
Thank you.
On 3/15/2021 10:33 AM, g6luu alan
wrote:
Using DvSwitch.img on my own Rpi2 , on own Network
|
|
|
|
Re: Registration of Dv Switch
g6luu alan
Using DvSwitch.img on my own Rpi2 , on own Network
|
|
|
|
Re: Registration of Dv Switch
Are you using your own server or someone else?
toggle quoted messageShow quoted text
On 3/15/2021 10:02 AM, g6luu alan
wrote:
DVSwitch Server (USRP)
|
|
|
|
Re: Registration of Dv Switch
DVSwitch Server (USRP)
Been 'resetting' and working now, not sure what 'changed' but all good now Got a lot of RX Data coming down from , i guess, the Network ? Fantastic Network ! Like it a lot . 73 alan
|
|
|
|
Re: Emulator timed out on encode!
G4WXN@...
I have decided I am flogging a dead horse here, so have decided to start again, and use the Rpi image 2020-10-31-DVSwitch-Server-lite.img
I am assuming that is the most up to date version? -- Derek G4WXN
|
|
|
|
P25 to DMR bridge using DVSwitch Server
David Young
Trying to understand how to use the new DVSwitch-Server to bridge from P25 to DMR. Using the old DVSwitch bridging, two instances of Analog_Bridge were required, which I assume is still necessary but DVSwitch-Server seems to only auto-start one instance of Analog_Bridge. The second I have been starting manually. I think I am missing something here. How do I setup DVSwitch-Server to auto start two instances of Analog_Bridge? I have been using the primary Analog_Bridge with it's .ini file (Analog_Bridge.ini) setup for the P25 side and then I add another instance of Analog_Bridge in the same default folder named Analog_Bridge_DMR with it's associated .ini file (Analog_Bridge_DMR.ini). The DMR side Analog_Bridge I have been manually starting which is where I think I am missing the correct procedure. Doing the P25 to DMR bridge this way works, but I do run into problems usually after it runs for some time (sometimes afew hours and some times a day or so), then either it stops running or the audio gets distorted with very long latency. When I look at the server stats I see a very large amount of disk IO operations and the CPU usage goes upward over 50% which seems excessive as I am only running two bridges on the server, P25 and NXDN, both to DMR. I also noted that the Analog_Bridge_DMR.log generating messages which say MMDVM success constantly which is causing the log file to grow quite large. I have changed the logging from the default of 2 (message) to 0 (None) which stops these messages. The primary Analog_Bridge.log file does not do this.
I am sure I must not be following the correct setup to bridge P25 to DMR with DVSwitch-Server, help? -- Dave WB6DTB
|
|
|
|
Re: Connection Issue to BM
Fixed. I must have misunderstood about the DUPLEX=1.
toggle quoted messageShow quoted text
Thanks! 73 Scott, N4UPC
On 3/14/2021 6:50 PM, Steve N4IRS
wrote:
Set Duplex = 0
|
|
|
|
Re: Connection Issue to BM
Set Duplex = 0
toggle quoted messageShow quoted text
On 3/14/21 7:41 PM, N4UPC - Scott via
groups.io wrote:
|
|
|
|
Re: Connection Issue to BM
--- [General] Callsign=N4UPC #Id=316235620 Id=3162356 Timeout=180 Duplex=1 [Info] RXFrequency=222340000 TXFrequency=222340000 Power=1 Latitude=41.7333 Longitude=-50.3999 Height=0 Location=USA Description=Bridge URL=https://www.dodropin.net [Log] # Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal DisplayLevel=1 FileLevel=2 FilePath=/var/log/mmdvm FileRoot=MMDVM_Bridge [DMR Id Lookup] File=/var/lib/mmdvm/DMRIds.dat Time=24 [NXDN Id Lookup] File=/var/lib/mmdvm/NXDN.csv Time=24 [Modem] Port=/dev/null RSSIMappingFile=/dev/null Trace=0 Debug=0 [D-Star] Enable=1 Module=B [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [System Fusion] Enable=0 [P25] Enable=0 NAC=293 [NXDN] Enable=0 RAN=1 Id= [D-Star Network] Enable=0 GatewayAddress=127.0.0.1 GatewayPort=20010 LocalPort=20011 Debug=0 [DMR Network] Enable=1 Address=3102.repeater.net Port=62031 Jitter=360 Local=62032 Password=xxxxxxx # for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md # for XLX the syntax is: Options=XLX:4009 # Options= Slot1=0 Slot2=1 Debug=0 [System Fusion Network] Enable=0 LocalAddress=0 LocalPort=3200 GatewayAddress=127.0.0.1 GatewayPort=4200 Debug=0 [P25 Network] Enable=0 GatewayAddress=127.0.0.1 GatewayPort=42020 LocalPort=32010 Debug=0 [NXDN Network] Enable=0 #LocalAddress=127.0.0.1 Debug=0 LocalPort=14021 GatewayAddress=127.0.0.1 GatewayPort=14020 --- 73 Scott, N4UPC
On 3/14/2021 6:37 PM, Steve N4IRS
wrote:
Show MMDVM_Bridge.ini
|
|
|
|
Re: Connection Issue to BM
Show MMDVM_Bridge.ini
toggle quoted messageShow quoted text
On 3/14/21 7:36 PM, N4UPC - Scott via
groups.io wrote:
|
|
|
|
Re: Connection Issue to BM
Also RX/TX freq is the same. 73, Scott N4UPC
On Sun, Mar 14, 2021 at 18:33, N4UPC - Scott via groups.io <n4upc@...> wrote:
All,
|
|
|
|
Re: Connection Issue to BM
toggle quoted messageShow quoted text
On 3/14/21 7:33 PM, N4UPC - Scott via
groups.io wrote:
All,
|
|
|
|
Connection Issue to BM
All,
My DVSwitch system as suddenly stopped connecting to BM. I've made the changes to the MMDVM_Bridge file as previously noted: [General] Callsign=N4UPC #Id=316235620 Id=3162356 Timeout=180 Duplex=1 Still no joy. All I get in the MMDVM_Bridge.log is: E: 2021-03-14 23:31:05.954 DMR, Master is closing down M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network E: 2021-03-14 23:31:16.167 DMR, Master is closing down M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network E: 2021-03-14 23:31:26.373 DMR, Master is closing down M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network I also did an upgrade and rebooted the system afterward. Stumped! --
73 Scott, N4UPC
|
|
|
|
Re: Registration of Dv Switch
What are you connecting to? AllStar (IAX) or DVSwitch Server (USRP)
toggle quoted messageShow quoted text
Steve N4IRS
On 3/14/21 6:01 PM, g6luu alan wrote:
|
|
|
|
Registration of Dv Switch
g6luu alan
Hi de G6LUU Have installed Dv Switch on a second android device Which is a T320 nd I have a problem. It says on Status 'Not registered' . I cannot work out away round this problem , Tried the "Register button with no success Any help would be appreciated Regards alan G6LUU
|
|
|
|
Re: M17 to ASL
Ok, so the only issue I see at this point is with Analog_Bridge. It's not aware of M17 as a digital mode and does not know how to send frames to M17Gateway.
I suppose we'll have to wait until Analog_Bridge supports M17. Steve KC1AWV
|
|
|
|
Re: Emulator timed out on encode!
G4WXN@...
Terrible audio apparently, so I think a reinstall.
-- Derek G4WXN
|
|
|
|
Re: Emulator timed out on encode!
G4WXN@...
I've figured it out, I had to add the repository manually.
I think I may have an old version or install, I used the brute force install, it's probably nearly a year old. Anyway it's working, not sure if it's worth a complete setup from scratch, as I have a lot of work with scripts and macros invested. -- Derek G4WXN
|
|
|