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: ARM IMAGE
XLX does not do analog. The reason those connections sound "perfect" is that they go from digital to digital.
When you go to analog - in particular Allstar - higher-frequency components of the DMR signal are just not encoded well at the 8k sampling rate and get distorted. I don't know why, but Fusion in particular has a lot of energy in the range of 3500 Hz and that is a no-no for Allstar. The AMBE modes use a vocoder - which can produce sound energy above what the Nyquist limit would dictate. I guess they feel that emphasizing this part of the audio spectrum enhances intelligibility. But it is annoying when you go to a scheme that is encoding the audio (rather than vocoding it). Ken KE2N
|
|
|
|
Re: Some questions about dvswitch.sh and Analog_Bridge
Tim Payne
Hi Steve,
I have tried running only the 2 instances of AB and it happens when I send the dvswitch tune command. The logs I included had no MB running at all. Other tests I performed were only running the AB_P25 and then the AB_DMR along with the rest of the system and then when I ran the dvswitch command or keyed up on the radio there was no spamming of info packets. Today I though I would leave it running for a while after issuing the dvswitch tune 9999 (disconnect) running for 3 hours at 100 CPU. Does AB pull any setting from the DVswitch.ini file in the MB directory? I'll pull the Configs for those when I get to the PC tomorrow. Thanks Tim vk3ftzd
|
|
|
|
Re: Some questions about dvswitch.sh and Analog_Bridge
Tim,
toggle quoted messageShow quoted text
You are correct, suppressing the log does no good. We need to know what is going on. Lets start with the DMR side of the bridge. Turn off AB_P25. I assume you are running one instance of MB. So in MB.ini disable P25 and P25 networking. Set the log level to 1 and capture the AB and MB logs. I would also like to see your MB.ini and dvswitch.ini. Steve N4IRS
On 6/4/2020 5:35 AM, Tim Payne wrote:
Ok thanks. I'll try it. I know that I tried setting to 4 - warning and I got the close to 100% CPU usage but of course the packets were suppressed.
|
|
|
|
Re: Some questions about dvswitch.sh and Analog_Bridge
Hello Tim
I never look at logs. Just look at the info on the screen. Can see whats going on in real time. Also see whats gone down then just restart the software. There is always info passing back and forth from Analog_Bridge. It will be the transcoding from dmr to p25 thats using the cpu not the info.
|
|
|
|
Re: Some questions about dvswitch.sh and Analog_Bridge
Tim Payne
Ok thanks. I'll try it. I know that I tried setting to 4 - warning and I got the close to 100% CPU usage but of course the packets were suppressed.
Hiding the alerts doesn't necessarily mean it fixes the problem. You say you use the logs yourself. Do you see this in your logs? Is it normal to have this happening?
|
|
|
|
Re: Some questions about dvswitch.sh and Analog_Bridge
In the Analog_Bridge.ini
loglevel = 2 you could change it to 0 I never change it as I use this info to see whats going on. As I run in terminal windows the info from the logs act like a dashboard for me. Tx begin, Tx end, callsigns etc.
|
|
|
|
Re: #analog_bridge
#analog_bridge
andrew delgado
i did stop the ambe server here is the logs. same error on port 31100 will close upon sending the marco ^DMR mode
I: 2020-06-04 03:23:37.362 Tune macro: *DMR will invoke "/opt/Analog_Bridge/dvswitch.sh mode DMR" I: 2020-06-04 03:23:37.548 rxport=: 30000 M: 2020-06-04 03:23:37.549 TLV rx socket reopened for 127.0.0.1:30000 I: 2020-06-04 03:23:38.862 MESSAGE packet sent to USRP client: Setting mode to DMR I: 2020-06-04 03:23:38.937 ambeMode = DMR, size = 72 M: 2020-06-04 03:23:38.937 Connecting to DV3000 hardware...... M: 2020-06-04 03:23:38.948 Begin DV3000 decode I: 2020-06-04 03:23:39.009 txport=: 31103 I: 2020-06-04 03:23:39.102 rxport=: 31100 E: 2020-06-04 03:23:39.103 Can not bind port 31100, error code = 98 (Address already in use) M: 2020-06-04 03:23:39.103 TLV rx socket reopened for 127.0.0.1:31100 I: 2020-06-04 03:23:40.345 Macro result was 0
|
|
|
|
Re: #analog_bridge
#analog_bridge
andrew delgado
Yes Mike, Im running the stick at the same host using pi3,
my problem is when i issue the DMR mode @ Dvswitch mobile client the error pertaining to port 31100 will close. and will not receive audio from mobile phone ,and tx from mobile phone is okay. I: 2020-06-04 03:14:03.590 ambeMode = DMR, size = 72 M: 2020-06-04 03:14:03.591 Connecting to DV3000 hardware...... E: 2020-06-04 03:14:03.591 Can not bind port 2460, error code = 98 (Address already in use) M: 2020-06-04 03:14:03.625 Begin DV3000 decode I: 2020-06-04 03:14:03.670 txport=: 31103 I: 2020-06-04 03:14:03.742 rxport=: 31100 E: 2020-06-04 03:14:03.743 Can not bind port 31100, error code = 98 (Address already in use) M: 2020-06-04 03:14:03.743 TLV rx socket reopened for 127.0.0.1:31100 I: 2020-06-04 03:14:04.911 Macro result was 0
|
|
|
|
Re: Some questions about dvswitch.sh and Analog_Bridge
Tim Payne
Hey guys,
Still plotting on with this spamming of "INFO packet sent to USRP client" in my logs. it seems to be related to the 2 instances of AB. My setup is HBlink Master2 ----> MB -----> AB_DMR -----> AB_P25 ------> MB -------> P25Gateway. I have killed every other process for my setup and only included the 2 for AB. I have checked ports are correct and nothing looping back into itself or into another part. I have even changed the ports away from the port mappings in the example in case something else was causing this. Still scratching my head. I have uploaded my configs and logs in case anyone has the time to look and give a second opinion. Thanks Cheers 73's Tim VK3FTZD
|
|
|
|
Re: #analog_bridge
#analog_bridge
Andrew,
By the error you are seeing I have to assume you are running AMBEServer on the same machine as Analog_Bridge is running on. If this is so, you can just run the DV3000 (or other stick) directly. If for some reason you need to run AMBEServer, you can ignore the message (it is fixed in a future release of AB) Mike N4IRR
|
|
|
|
Re: #analog_bridge
#analog_bridge
andrew delgado
HI Ernie,
I only have one instance for analog and mmdvm bridge this is right after install and configuration from the pdf documentation posted here. Regards, Andrew
|
|
|
|
Re: ARM IMAGE
Hamvoip is based on Arch not Debian! So you need to use the correct package manager. pacman -Sy package_name This will install packages in Arch, if you need further information about pacman (not the arcade game!) then type... man pacman This will print out the manual to screen so that you can read it. Apt is Debian's package management as yum is for redhat/fedora based systems. Cheers
|
|
|
|
Re: ARM IMAGE
Pete Fierro
How were you able to get DV Switch on hamvoip?
toggle quoted messageShow quoted text
I did "apt-get install dvswitch -y" at the shell& got this message
|
|
|
|
Re: ARM IMAGE
Yes, I currently have DVSwitch installed on a HAMVOIP image and that allows allstar to DMR. I am sure it will do more but I have not looked into anything else just yet. The issue is even with a DV3000 USB installed the DMR to FM is not as good as it should be. Not like some of these XLX installs that just sound perfect.
|
|
|
|
Re: ARM IMAGE
On second thought, Will you be connecting the AllStar node to a
analog radio?
toggle quoted messageShow quoted text
Steve N4IRS
On 6/3/2020 10:05 AM, W8DSB wrote:
Is there a ARM image available (PI 4) that has ASL, DVSWitch already installed? I have made a few now using HAMVOIP and DVSwitch but the ASL to DMR is only so so even with a DV3000 USB dongle. Hoping to find something that works better.
|
|
|
|
Re: ARM IMAGE
Not yet.....
toggle quoted messageShow quoted text
On 6/3/2020 10:05 AM, W8DSB wrote:
Is there a ARM image available (PI 4) that has ASL, DVSWitch already installed? I have made a few now using HAMVOIP and DVSwitch but the ASL to DMR is only so so even with a DV3000 USB dongle. Hoping to find something that works better.
|
|
|
|
ARM IMAGE
Is there a ARM image available (PI 4) that has ASL, DVSWitch already installed? I have made a few now using HAMVOIP and DVSwitch but the ASL to DMR is only so so even with a DV3000 USB dongle. Hoping to find something that works better.
|
|
|
|
Re: #analog_bridge
#analog_bridge
You may have another Analoge_Bridge running.
MMDVM_Bridge and Analoge_Bridge have usually been installed to start up when your device is restarted. I get caught out myself. I like running them in terminal windows. Find it easier to fault find. sudo systemctl stop analog_bridge sudo systemctl stop mmdvm_bridge
|
|
|
|
#analog_bridge
#analog_bridge
Hi All,
Can you help me with the error below? it seems that theres an error on port when clicking the marco<>Mode Select <> DMR on mobile phone port 31100 will close. I: 2020-06-03 04:51:38.416 MESSAGE packet sent to USRP client: Setting mode to DMR I: 2020-06-03 04:51:38.489 ambeMode = DMR, size = 72 M: 2020-06-03 04:51:38.489 Connecting to DV3000 hardware...... E: 2020-06-03 04:51:38.489 Can not bind port 2460, error code = 98 (Address already in use) M: 2020-06-03 04:51:38.533 Begin DV3000 decode I: 2020-06-03 04:51:38.568 txport=: 31103 I: 2020-06-03 04:51:38.669 rxport=: 31100 E: 2020-06-03 04:51:38.670 Can not bind port 31100, error code = 98 (Address already in use) M: 2020-06-03 04:51:38.670 TLV rx socket reopened for 127.0.0.1:31100 I: 2020-06-03 04:51:39.905 Macro result was 0 Thanks! Andrew 73!
|
|
|
|
Re: ASL_node_list.txt
Works great Mike. tnx a lot. will be a big benefit when mobiling. FWIW, to make testing and loading simpler, I created a much smaller node_list.txt file - only a dozen entries instead of the 15K standard.
-- Tom VE3NY
|
|
|