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: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.
Jay
Thank you. And thanks for all the work on the image. I have been been trying do accomplish some of what you have for a year. -- jb N4NQY
|
|
Re: Output callsigns to variable or CSV file
From what program are you trying to get data from?
toggle quoted messageShow quoted text
On 2/2/2020 12:24 PM,
Jaenulton@... wrote:
I am working on a script that will log a timestamps and callsign to a text file. I can't figure out how to get the callsign of the station that is broadcasting. Setting it as a variable for use in bash would be really cool, but at this point I would even be happy with a one liner writing it to a TMP .txt file.
|
|
Output callsigns to variable or CSV file
Jaenulton@...
I am working on a script that will log a timestamps and callsign to a text file. I can't figure out how to get the callsign of the station that is broadcasting. Setting it as a variable for use in bash would be really cool, but at this point I would even be happy with a one liner writing it to a TMP .txt file.
Could anyone suggest how to get the callsign from the command line when the RX begins?
|
|
Re: EA5GVK with Zumspot AMBE Server...
ve6gcd@...
In addition, additional network changes might be required depending on where you will use DVSwitch mobile.
If the Ambe Server is installed in the house, and you want to use DVSwitch mobile from outside, then you probably need to set up port forwarding in your router for the unit.
|
|
Re: EA5GVK with Zumspot AMBE Server...
ve6gcd@...
I also tried MD380emu before but I prefer the Zum Ambe Server as the audio conversion to DMR is like night and day between the two.
However, when I used it for YSF I noticed some popping sound in between transmissions. This does not happen when on DMR mode. I do not believe that this is hardware related. Please note that the Zum Ambe Board was only introduced recently, so probably the Analog_Bridge software needs to be modified for YSF to work well on the new hardware. Thus, in the meantime I use Zum Ambe Server for DMR. And for YSF, I configured Analog_Bridge to use ThumbDV on serial mode.
|
|
Re: EA5GVK with Zumspot AMBE Server...
Adam Liette
Ok. I didn't know about that part of analog_bridge.ini. What I'm aiming for is to use the AMBE board rather than md380emu and be able to use the DV-Switch mobile app. It was my understanding that using an AMBE device would allow it to work better on D-Star,
etc.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of ve6gcd@... <ve6gcd@...>
Sent: Saturday, February 1, 2020 10:27:54 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] EA5GVK with Zumspot AMBE Server... Can you tell me what do you want to do with it on the Pi?
I used the Zum Ambeboard as vocoder hardware for Analog_Bridge. So upon inserting the configured SD card (Ambe Server mode with IP address 192.168.1.230 and port 2460) to the Zum Ambeboard, I plugged the Ethernet data cable to the unit then powered it on. Afterwards, I configured the Analog_Bridge.ini with the following lines: [DV3000]
address = 192.168.1.230 ; IP address of AMBEServer
rxPort = 2460 ; Port of AMBEServer
; address = /dev/ttyUSB0 ; Device of DV3000U on this machine
; baud = 460800 ; Baud rate of the dongle (230400 or 460800)
serial = false ; Use serial=true for direct connect or serial=false for AMBEServer
|
|
Re: EA5GVK with Zumspot AMBE Server...
ve6gcd@...
Can you tell me what do you want to do with it on the Pi?
I used the Zum Ambeboard as vocoder hardware for Analog_Bridge. So upon inserting the configured SD card (Ambe Server mode with IP address 192.168.1.230 and port 2460) to the Zum Ambeboard, I plugged the Ethernet data cable to the unit then powered it on. Afterwards, I configured the Analog_Bridge.ini with the following lines: [DV3000]
address = 192.168.1.230 ; IP address of AMBEServer
rxPort = 2460 ; Port of AMBEServer
; address = /dev/ttyUSB0 ; Device of DV3000U on this machine
; baud = 460800 ; Baud rate of the dongle (230400 or 460800)
serial = false ; Use serial=true for direct connect or serial=false for AMBEServer
|
|
Re: EA5GVK with Zumspot AMBE Server...
Adam Liette
I had that part done, but I wasn't sure if there was anything special to do on the Pi. I selected the AMBE device, etc, but wasn't getting anywhere on DMR or other modes.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of ve6gcd@... <ve6gcd@...>
Sent: Saturday, February 1, 2020 5:26:03 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] EA5GVK with Zumspot AMBE Server... I setup one before, you just need to set it up using the configurator in the Zum website. Afterwards you just copy the created file to the included SD card, insert it to the ambeboard and you should be good to go
|
|
Re: EA5GVK with Zumspot AMBE Server...
ve6gcd@...
I setup one before, you just need to set it up using the configurator in the Zum website. Afterwards you just copy the created file to the included SD card, insert it to the ambeboard and you should be good to go
|
|
EA5GVK with Zumspot AMBE Server...
Adam Liette
Hello all. I’ve seen references to using the various AMBE thumb sticks, but has anyone used the Zumspot AMBE server with their installation of EA5GVK’s image? I have the Zumspot device that works either via the network or USB, but didn’t have any luck when I tried it.
Thanks, Adam, W8FLH
|
|
Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.
EA5GVK Joaquin
dvlink dvlink
El jue., 30 ene. 2020 23:38, Jay <jay.n4nqy@...> escribió: What is the login and password for V8 Virtual machine?
|
|
Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.
Jay
What is the login and password for V8 Virtual machine?
-- jb N4NQY
|
|
Re: MMDVM_Bridge not sending to NXDNGateway
Bill N2WNS
AND.... That was easy. working like a champ.
|
|
Re: MMDMV_Bridge password
I would login to selfcare and set the password. I believe BM wants people to move away from passw0rd so you may want to choose a unique password.
toggle quoted messageShow quoted text
Steve N4IRS
On 1/29/2020 3:31 AM, Phil VK3VB wrote:
Greetings.
|
|
MMDMV_Bridge password
Phil VK3VB
Greetings.
I have had a DMR-P25 DVSWITCH running succesfully for a few months. About a week ago the brandmeister connection dropped off and I am seeing M: 2020-01-29 06:31:49.848 DMR, Closing DMR Network M: 2020-01-29 06:31:49.850 DMR, Opening DMR Network E: 2020-01-29 06:31:59.909 DMR, Login to the master has failed, retrying network  ... M: 2020-01-29 06:31:59.911 DMR, Closing DMR Network M: 2020-01-29 06:31:59.912 DMR, Opening DMR Network E: 2020-01-29 06:32:09.968 DMR, Login to the master has failed, retrying network I am told the password is incorrect, but nothing has changed and it is set to "passw0rd" in the MMDVM_Bridge.ini, which is correct for the master. Any way to capture the connection request string that is being sent so I can see if something weird is going on? thanks Phil VK3VB
|
|
Re: MMDVM_Bridge not sending to NXDNGateway
Correct
Sent by smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Bill N2WNS <n2wns.radio@...>
Sent: Wednesday, January 29, 2020 7:27:47 AM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] MMDVM_Bridge not sending to NXDNGateway AH... So no analog bridge for this since no transcoding?
|
|
Re: MMDVM_Bridge not sending to NXDNGateway
Bill N2WNS
AH... So no analog bridge for this since no transcoding?
|
|
Re: MMDVM_Bridge not sending to NXDNGateway
As I said,
toggle quoted messageShow quoted text
Cross connect TX to RX and RX to TX [DMR] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 31015 ; Port to send AMBE TLV frames to (export) RXPort = 31014 ; Port to listen on (import) [NXDN] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 31014 ; Port to send AMBE TLV frames to (export) RXPort = 31015 ; Port to listen on (import)
On 1/28/20 9:11 PM, Bill N2WNS wrote:
This is a DMR<->NXDN. I wasn't sure if the MD380 server was needed, so I put it in there anyway. I read it wasn't needed for DMR/NXDN/YSF but I intend on added P25 to the Mix at some point and believed it would be needed then. I mapped out all my ports on paper before putting this in place.
|
|
Re: MMDVM_Bridge not sending to NXDNGateway
Bill N2WNS
This is a DMR<->NXDN. I wasn't sure if the MD380 server was needed, so I put it in there anyway. I read it wasn't needed for DMR/NXDN/YSF but I intend on added P25 to the Mix at some point and believed it would be needed then. I mapped out all my ports on paper before putting this in place.
Here is my DVSwtich config : [DMR] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 31015 ; Port to send AMBE TLV frames to (export) RXPort = 31014 ; Port to listen on (import) Slot = 2 ; Export slot [NXDN] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 31017 ; Port to send AMBE TLV frames to (export) RXPort = 31016 ; Port to listen on (import) FallbackID = 34000 ; In case we can not find a valid DMR id in the da tabase, export this one NXDNFallbackID = 34000 ; Use this ID when the input DMR ID is not found in the database Translate = 31360=31360 ; Translate NXDN TG < -- > DMR TG (bidirection al) Slot = 2 ; Export slot
|
|
Re: MMDVM_Bridge not sending to NXDNGateway
Bill,
toggle quoted messageShow quoted text
I'm a little confused. This is a DMR to NXDN bridge? I believe it is based on your first message. You don't need a transcoder to bridge DMR <-> NXDN Here is the flow diagram. DMR Network <-> MMDVM_Bridge <-> NXDNGateway <-> NXDN Network. That's it. One copy of MMDVM_Bridge with NXDN and DMR enabled in MMDVM_Bridge.ini What you want to do is "cross connect" DMR to NXDN in DVSwitch.ini By cross connect, I mean TX Port to RX Port and RX Port to TX Port. Steve N4IRS
On 1/28/20 8:37 PM, Bill N2WNS wrote:
So in troubleshooting, I came in from the NXDN side and and was able to hit MMDVM_Bridge:
|
|