Welcome to DVSwitch
Purpose
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
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: Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm
#brandmeister
Dave M0UPM
Corey, I have messaged him as much in a private mail. Dave M0UPM BM UK Admin
toggle quoted messageShow quoted text
On 26 Dec 2020, at 22:31, Corey Dean N3FE <n3fe@...> wrote:
|
|
|
|
Re: Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm
#brandmeister
Corey Dean N3FE
Brandmeister prefers you to directly work with the master and do a true xlx connection as it uses the xlx protocol directly.
toggle quoted messageShow quoted text
On Dec 26, 2020, at 2:06 PM, craig.jump via groups.io <craig.jump@...> wrote:
|
|
|
|
Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm
#brandmeister
craig.jump@...
These are my ini files for a Brandmeister TG to XLX bridge
BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode) Had one way audio for a while and was tearing my hair out.. (now have none left :-) ) These might save someone some time.. problem was the DVSwitch ini file where I had to define the TG.. otherwise one way audio.. Remember and setup a static TG on the BM self service page and set your password accordingly. Craig 2M0JUM
|
|
|
|
Re: DVSwitch running on 2nd Raspberry Pi
Frank. Anytime you try and execute a command from the current directory, you must proceed it with a ./ so you should enter ./pyUC.py Also, Python may not be in your path. Try python3 pyUC.py. Let us know what happens
|
|
|
|
Re: DVSM APP server pool
Ralf, DC9NYC
I am sorry - the IP address is: ...
87.191.190.207, Port 50111 87.191.190.207, Port 50112
87.191.190.207, Port 50113 Ralf, DC9NYC
|
|
|
|
Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue"
#hblink
fabiobassa
Sure Steve I will post there too and ty again for wonderfull work done on those digital systems 73 ' s
|
|
|
|
Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue"
#hblink
I suggest you post this information in the HBlink subgroup <https://dvswitch.groups.io/g/HBlink>
Where more HBlink users will see it.
toggle quoted messageShow quoted text
Steve N4IRS
On 12/26/20 6:45 AM, fabiobassa wrote:
|
|
|
|
Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue"
#hblink
fabiobassa
Hello Bob, thank you for kind replay. unfortunately Parrot documentation on hblink3 is fragmented , a piece here, a piece there so a bit unconfortable to follow the puzzle On my radio of course the parrot is a group call and I can engage the parrot, what is frustrating WAS the wrong audio coming back I found another polish man talking about parrot on hblink3 and he says that first is necessary start the parrot service itself , otherwise no parrot service on board
that is my relative path. Following the guidance to have a parrot.service , in facts, now the parrot is working succesfully Was just the lack of a service thanks again , 73's Marco IZ8XOH
|
|
|
|
Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue"
#hblink
Bob KK6RQ
Dunno if this applies, but on our HBLink server Parrot 9990 has to be a *group* call... (I'm not the person maintaining it so I can't expand on that; I just know that's how it is...) KK6RQ
On Sat, Dec 26, 2020, 4:01 AM fabiobassa <fabiobassa@...> wrote:
|
|
|
|
Re: DVSwitch running on 2nd Raspberry Pi
Frank,
toggle quoted messageShow quoted text
pyUC is a client program written in Python3. It requires a system with a graphic interface (Linux window manager, Microsoft Windows, Apple MAC. it is not intended to run on the server. That is not to say it CAN'T be run on the server. I just want you to understand the program. When you run a Linux program it either must be in you path or you must explicitly tell Linux the full path. Since pyUC is a python program run it with python3 pyUC.py. The md380-emulator is installed and set to start on boot by the image or install script. To connect your DVSwitch Server to your HAMVOIP node: Add a private node to HAMVOIP. Use this as a guide for the node stanza <https://github.com/DVSwitch/Analog_Bridge/blob/master/ASL/rpt.conf.txt> instead of setting the rxchannel to 127.0.0.1, set it to the address of your DVSwitch Server Once you have the private node setup and working on HAMVOIP change the [USRP] stanza in Analog_Bridge.ini: [USRP] address = 127.0.0.1 ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge) txPort = 32001 ; Transmit USRP frames on this port rxPort = 34001 ; Listen for USRP frames on this port usrpAudio = AUDIO_UNITY ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC) usrpGain = 1.10 ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY) usrpAGC = -20,10,100 ; Set the agc threshold (db), slope (db) and decay (ms) tlvAudio = AUDIO_UNITY ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF) tlvGain = 0.35 ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY) Set the address above to the IP address of your HAMVOIP node. Steve N4IRS
On 12/25/20 6:51 PM, Frank C. D'Amato
wrote:
I set up a Raspberry Pi last week with Hamvoip. The Allstar Node is up and running and RF is connected. It has a private node 1999 also.
|
|
|
|
Re: DVSwitch running on 2nd Raspberry Pi
larry_n7fm
Frank which directory are you issuing the pyUC.py command from? If the same directory as the one holding pyUC.py script try ./pyUC.py.
toggle quoted messageShow quoted text
Otherwise make sure the path is know. Larry - N7FM
On 12/25/20 3:51 PM, Frank C. D'Amato wrote:
When I try to execute pyUC.py (by typing pyUC.py) I get "a -bash: pyUC.py: command not found"
|
|
|
|
DVSwitch running on 2nd Raspberry Pi
I set up a Raspberry Pi last week with Hamvoip. The Allstar Node is up and running and RF is connected. It has a private node 1999 also.
I installed DVSwitch on the second Pi (No ALS) I followed the DVSwitch Installation and User Guide v1.61.pdf instructions but am stuck at the pyUC I unzipped the USRP Client and copied it to home/pyUC I ran the following command; sudo apt-get install python3-pyaudio
sudo apt-get install portaudio19-dev
sudo apt-get install python3-pil.imagetk
I edited the pyUC.ini file and did a sudo chmod 775 pyUC.py When I try to execute pyUC.py (by typing pyUC.py) I get "a -bash: pyUC.py: command not found" Why would I get this error? My MMDVM_Bridge shows my callsign when I key my radio to the designated TG My ANALOG_Bridge shows my callsign when I key my radio to the designated TG I don't see any instructions on setting up the MD-380 Emulator, or how to finally connect the DVSwitch to my Hamvoip Allstar Node located at 192.168.1.9 on my network Please help
|
|
|
|
DVSwitch running on 2nd Raspberry Pi
I set up a Raspberry Pi last week with Hamvoip. The Allstar Node is up and running and RF is connected. It has a private node 1999 also.
I installed DVSwitch on the second Pi (No ALS) I followed the DVSwitch Installation and User Guide v1.61.pdf instructions but am stuck at the pyUC I unzipped the USRP Client and copied it to home/pyUC I ran the following command; sudo apt-get install python3-pyaudio
sudo apt-get install portaudio19-dev
sudo apt-get install python3-pil.imagetk
I edited the pyUC.ini file and did a sudo chmod 775 pyUC.py When I try to execute pyUC.py (by typing pyUC.py) I get "a -bash: pyUC.py: command not found" Why would I get this error? My MMDVM_Bridge shows my callsign when I key my radio to the designated TG My ANALOG_Bridge shows my callsign when I key my radio to the designated TG I don't see any instructions on setting up the MD-380 Emulator, or how to finally connect the DVSwitch to my Hamvoip Allstar Node located at 192.168.1.9 on my network Please help
|
|
|
|
macros not saving after restart of app
Hey guys I wanted to add macros in the config section of dvswitch to shut down or restart my allstar node but when i close the app and restart the app
it resets the macros I entered I believe I have the full version. Thanks.
|
|
|
|
#hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue"
#hblink
Hello all, But now I have a problem I'm not able to debug properly. Let descrive my setup: Scenario GOOD : I register into brandmeister , call the parrot 9990 and hear the talkback:
Scenario BAD : I log into local hblink , call the parrot and a lot of error coming out
DMR Slot 2, overflow in the DMR slot RF queue ( many many of these)
By searching on Google this same error It landed me to MAYBE a problem with tcxo on my hotspot hat but here come questions: Why the same hardware is working on brendmeister network and not working on local hblink? If was a tcxo problem it shouldn't have worked on neither What can I use to debug the underlaying problem or, if we do a sort od meeting, could anyone check from outside with different hardware if all the stuff are correct? Of course will give a public ip and open port and setup a momentary password for tests.
Thank you in advance for replays, 73's Marco iz8xoh Is that the reason ?
|
|
|
|
Re: Dvswitch crashes with weak 4G signal.
On 26/12/20 1:37 am, Brad N8PC wrote:
sounds like the problem is your not getting enough 4g signal to yourAll well and good, and improving the 4G signal is a good idea where that's an option, but none of this addresses what looks like a serious issue that the OP reported - DVSwitch server generating an uncontrolled transmission when communication with its controlling client is interrupted. If the data link is lost, the system should fail in a way that (1) doesn't result in uncommanded transmissions to the network and (2) so that client-server communication can be reestablished when the network connection is restored. The transmission (and apparent lockup) sounds like a serious issue to me. I haven't encountered it, because my DVSwitch installations have client (AllStar) and server on the same host or in the same data centre. I do have a "long haul" USRP link, but that's between AllStar in Sydney and DummyRepeater running here, and although that has been subjected to numerous network outages, it has been stable in its behaviour, meeting the criteria above (no unexpected transmissions or lockups, and simply picks up where it left off when the network comes back). I haven't tried talking to DVSwitch server over an unstable network link. And there's a lot more testing needed. Does this occur only between DVSwitch Mobile and the server? Or are connections between AllStar and DVSwitch affected too? Can it be replicated if DVSwitch mobile is on wifi (and the wifi or fixed Internet drops out)? Does any changes on the server side have an effect (Pi vs PC/cloud server, home vs data centre)? Just wondering if I can help test this myself, to assist with bug hunting. I can certainly do dodgy wifi and it only takes a 10 minute drive to reach unreliable mobile coverage. :) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Dvswitch crashes with weak 4G signal.
sounds like the problem is your not getting enough 4g signal to your
site. if your using a cellphone for net connection you will have a
problem with reliable communication as cell towers get busy. if you
have someone close by with line of site I would suggest an outside
internet antenna at each site like https://www.ui.com/products/
toggle quoted messageShow quoted text
you have to realize cell communications are not always best for internet connections. I run DVSwitch here on a raspberry Pi 4 with 5G internet connection Wifi without any of the problems your having. the other this you might try is changing from a cell phone to an actual MiFi (mobile data hotspot) that works on cell signals so as not to get other interruptions from the cell phone.
On 12/25/2020 5:02 AM, Pd1loi wrote:
Hello gentlemen of DVswitch.
|
|
|
|
Re: DVSM APP server pool
Ralf, DC9NYC
Mike,
at the moment the test-pool has tree member under a fixed internet-IP to share DVSM as a small HAM mobile-DVSM-App Service with focus - more people to can test, try and use that excellent mobile App-solution for DV. Most will use the App only (or later the http-Client) and will not install, run, care or handle a DVSM-Switch-Server installation (or are not able to do that). The IPs/Ports of the test-pool are: 87.191.190.190.207, UDP-Port 50111 87.191.190.190.207, UDP-Port 50112 87.191.190.190.207, UDP-Port 50113 No, I will not write an proxy, - I´am a cisco network-guy, but I have testet with a Load-Balancer and a DVSM-Farm with a VIP-IP with method "distribution static-sticky" - and some others LBA-methods. The problem is, - the loadbalancer can not find out witch DVSM-member is used or have mapped Reflectors/TG- linked or bind - or ist is free.The network-LBA can only detect wenn ip/port is not reachable and take-out then the single member from the pool. An LBA needs a criteria or a helper-port or an agent to check service is used/busy/mapped/armed ortransmitting or have Load, - or must can communicate with the properitary HAM/USRP/DVSM-service. So I think it is a better way, - the APP handle (client side the given member), an decide with member is free. The APP can communicate with the DVSM-Service directly and understand the communication and DVSM-status more better a network-LBA. At the moment the user enter all destinations under accounts and set check-box manualy to connect one of the member as linke. So, this has compelled me to write the the question for a pool feature in the DVSM-APP it will be a good feature for the big HAM community. Or build a multi-user DVSM-Switch but ist ist more complex as a pool feature. ... Regards, Ralf, DC9NYC
|
|
|
|
Dvswitch crashes with weak 4G signal.
Hello gentlemen of DVswitch.
I have already experienced a few times that when I have too little 4G (Mobile data) signal, DV switch crashes. The PTT key turns red, and then transmits continuously. I have also had 2x that I walk in the countryside and then I suddenly get the message unregistered and then I can turn the dVswitch off and on again, but nothing changes. But what I then hear from other amateurs is that the Rasberry Pi will transmit and will not return to normal mode. I just have to turn off the power and restart. I am using a Rasberry 3b with 32gb sd card. and an Inrico T320 with Android 7.0, it also has a 32GB SD card. And everything is up to date. So much for my findings about DVswitch. 73 PD1LOI
|
|
|
|
Re: Where the heck is hUC?
On 23/12/20 11:18 am, Steve N4IRS wrote:
The existing clients are Android any Python. The python client prettyAnother thing to look forward to! I love DVSwitch Mobile on my Android, but sometimes I only have the iPhone with me. Sold me yet again! :D -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|