Date   

Where can I find protocol documentation?

George M0GXB
 

For starters, I would like to find a full, complete, and correct documentation for whatever the protocol is called (IPSC, HBLINK, ??) that things like MMDVM use to talk to the gateways.

I found an old (2015) document somewhere which is clearly an early alpha version and with errors too, but the actual data streams I am looking at are for something that has evolved a bit since then. So where is this specified?

And is that protocol used for any other links in the growing DV networks?

George M0GXB


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Yes i point each mbridge to her dmrid path. But i dont use analogue bridge her . Its only mbridge


Re: #mmdvm_bridge #mmdvm_bridge

k7wby@...
 

MMDMV_Briidge looks for DMRIds.dat and Analog_Bridge looks for subscriber_ids.csv. Since these are both static text files you need a copy for each instance in /var/lib. 
The initial install puts DMRIds.dat in /var/lib/mmdvm/ and susbscriber_ids.csv in var/lib/dvswitch/ You need a copy for each instance of MB and AB.
Something like /var/lib/dvswitch/ab1 and ab2 then /var/lib/mmdvm/mb1 & mb2. Move the .dat and .csv files into those directories for each instance and then change your AB and MB .ini files to point to the new locations. The update process uses the .ini files for the locations so the updates should still work according to plan.

I would chmod 0775 the new directories you created just to make sure they can be accessed. 


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

ok tonight i re update latest bin and now they work without crash but they have a issue with the id. look my mb1 and mb2 log with the id.my id is 3022260 but one of them missing the last digit, 3022260 -mb1 302226 so he w ont recognise the id as a callsign

mbridge 2
lM: 2020-11-03 03:58:11.006 YSF, Opening INI file: DVSwitch.ini
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] txPort -> 43500
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] rxPort -> 42500
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] txWidePort -> 43500
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] exportTG -> 1234
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] slot -> 2
M: 2020-11-03 03:58:11.006 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-11-03 03:58:11.006 YSF, Transmitting on 127.0.0.1:43500, and listening on port 42500.  Result = 1
M: 2020-11-03 03:58:11.006 MMDVM_Bridge-20201031_V1.6.0 is running
I: 2020-11-03 03:58:11.006 Started the DMR Id lookup reload thread
M: 2020-11-03 03:59:38.495 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 03:59:38.496 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 03:59:41.923 YSF, received network end of transmission, 3.5 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 03:59:51.552 YSF, received network data from VE2TBU     to *****H54DM at WIRESX    
I: 2020-11-03 03:59:51.552 YSF, Lookup call VE2TBU returned id 3022260 -> 3022260
M: 2020-11-03 03:59:55.856 YSF, received network end of transmission, 4.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 03:59:57.389 YSF, TX state = ON
I: 2020-11-03 03:59:57.389 YSF, Begin TX: src=3022260 rpt=0 dst=1234 slot=2 cc=0 metadata=VE2TBU
M: 2020-11-03 03:59:57.486 YSF, TX state = OFF
M: 2020-11-03 04:00:00.622 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 04:00:00.622 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 04:00:03.319 YSF, received network end of transmission, 2.8 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 04:01:36.737 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 04:01:36.737 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 04:01:40.462 YSF, received network end of transmission, 3.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 04:01:52.463 YSF, received network data from 3022260    to ALL        at VE2TBU    
I: 2020-11-03 04:01:52.463 YSF, Lookup call 302226 returned id 0 -> 1234567
M: 2020-11-03 04:01:54.085 YSF, received network end of transmission, 1.7 seconds, 0% packet loss, BER: 0.0%
og
now mbridge 1
M: 2020-11-03 03:58:08.975 YSF, Opening INI file: DVSwitch.ini
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] txPort -> 42500
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] rxPort -> 43500
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] txWidePort -> 42500
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] exportTG -> 1234
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] slot -> 2
M: 2020-11-03 03:58:08.975 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-11-03 03:58:08.975 YSF, Transmitting on 127.0.0.1:42500, and listening on port 43500.  Result = 1
M: 2020-11-03 03:58:08.975 MMDVM_Bridge-20201031_V1.6.0 is running
I: 2020-11-03 03:58:08.975 Started the DMR Id lookup reload thread
M: 2020-11-03 03:59:38.496 YSF, TX state = ON
I: 2020-11-03 03:59:38.496 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 03:59:38.496 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 03:59:38.856 YSF, Narrow transmit (72 bit)
M: 2020-11-03 03:59:41.928 YSF, TX state = OFF
M: 2020-11-03 03:59:51.552 YSF, TX state = ON
I: 2020-11-03 03:59:51.552 YSF, Begin TX: src=3022260 rpt=0 dst=1234 slot=2 cc=0 metadata=VE2TBU
I: 2020-11-03 03:59:51.752 YSF, Narrow transmit (72 bit)
M: 2020-11-03 03:59:55.856 YSF, TX state = OFF
M: 2020-11-03 03:59:57.384 YSF, received network data from VE2TBU     to ALL        at F1ZJC     
I: 2020-11-03 03:59:57.384 YSF, Lookup call VE2TBU returned id 3022260 -> 3022260
M: 2020-11-03 03:59:57.481 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-03 04:00:00.622 YSF, TX state = ON
I: 2020-11-03 04:00:00.622 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 04:00:00.622 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 04:00:00.927 YSF, Narrow transmit (72 bit)
M: 2020-11-03 04:00:03.324 YSF, TX state = OFF
M: 2020-11-03 04:01:36.744 YSF, TX state = ON
I: 2020-11-03 04:01:36.744 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 04:01:36.744 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 04:01:37.041 YSF, Narrow transmit (72 bit)
M: 2020-11-03 04:01:40.467 YSF, TX state = OFF
M: 2020-11-03 04:01:52.463 YSF, TX state = ON
I: 2020-11-03 04:01:52.463 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-11-03 04:01:52.463 YSF, No call or id found, using ini value: VA2TB     -l¬
I: 2020-11-03 04:01:52.823 YSF, Narrow transmit (72 bit)
M: 2020-11-03 04:01:54.090 YSF, TX state = OFF


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Ok tonight i re downlaod the binary . Change my mmdvmbridge binary for the latest download. Now they work both way without crash but mb1 show the right dmrid associated to the right callsign but mb2 alway  show the id but missing the last digit of the dmr id so  its somewhere in the mbridge software


Re: Pi digital interface for Analog Radio (client)

Steve N4IRS
 

Still have this little issue:
The MMDVM software can look like a DMR repeater transmitter to a subscriber radio. The MMDVM software can look like a simplex signal (DMO) to a subscriber radio. What the MMDVM software can not do, is look like a subscriber radio to a DMR repeater. The same is true for traffic from a DMR repeater to the radio. The MMDVM software can not receive the output of a DMR repeater.

On 11/2/20 6:13 PM, Skyler Fennell wrote:
You could certainly do it with either Fusion or P25 with the remote gateway function enabled. 

I want to try it at some point ...

Radio less ASL node —> analog_bridge —> mmdvm_host P25/YSF REMOTE GATEWAY =1 —> ft-7800 9600 baud data port. 

Might be kinda a clunky mobile requiring a pi and a sound card and an extra speaker and mic   . 

So anyone, if I DO have a radio capable of Key/Unkey rapidly that would support tier II is there any hardware out there relatively easy to use to make a DMR client radio? 



On Mon, Nov 2, 2020 at 4:03 PM Jim Kusznir <jim@...> wrote:
Ok, thank you guys!

I figured there was a reason I didn't see someone making (overpriced) boxes that plugged into the data port of an analog radio to enable DMR...Even at $150, it would be a savings over buying a whole new radio.

--Jim


Re: Pi digital interface for Analog Radio (client)

Skyler Fennell
 

You could certainly do it with either Fusion or P25 with the remote gateway function enabled. 

I want to try it at some point ...

Radio less ASL node —> analog_bridge —> mmdvm_host P25/YSF REMOTE GATEWAY =1 —> ft-7800 9600 baud data port. 

Might be kinda a clunky mobile requiring a pi and a sound card and an extra speaker and mic   . 

So anyone, if I DO have a radio capable of Key/Unkey rapidly that would support tier II is there any hardware out there relatively easy to use to make a DMR client radio? 



On Mon, Nov 2, 2020 at 4:03 PM Jim Kusznir <jim@...> wrote:
Ok, thank you guys!

I figured there was a reason I didn't see someone making (overpriced) boxes that plugged into the data port of an analog radio to enable DMR...Even at $150, it would be a savings over buying a whole new radio.

--Jim


Re: Pi digital interface for Analog Radio (client)

Jim Kusznir
 

Ok, thank you guys!

I figured there was a reason I didn't see someone making (overpriced) boxes that plugged into the data port of an analog radio to enable DMR...Even at $150, it would be a savings over buying a whole new radio.

--Jim


Re: Compiling error on ./DVSwitch-System-Builder.sh

 

Got the problem ,  dvswitch-dashboard or  dvswitch-server would not install  because of a newer version of  libssl blocking lighttpd.

Here is what i did to fix it .

 SCREEN CAPTURE BEGINS

 root@vps275731:/tmp#apt-get install aptitude

root@vps275731:/tmp# aptitude  install lighttpd
The following NEW packages will be installed:
  libfam0{a} lighttpd
The following packages are RECOMMENDED but will NOT be installed:
  spawn-fcgi
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 311 kB of archives. After unpacking 1,041 kB will be used.
The following packages have unmet dependencies:
 libssl1.1 : Breaks: lighttpd (< 1.4.49-2) but 1.4.45-1 is to be installed
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     lighttpd [Not Installed]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Downgrade the following packages:
1)     libssl1.1 [1.1.1g-1+0~20200421.17+debian9~1.gbpf6902f (<NULL>, now) -> 1.1.0l-1~deb9u1 (oldstable)]

Accept this solution? [Y/n/q/?] Y
The following packages will be DOWNGRADED:
  libssl1.1

SCREEN CAPTURE CONTINUES AND ENDS WITH FINISHED INSTALLATION


After  that ,  dvswitch-server is installing perfectly ...

There might be a more elegant way to resolve that  but it worked .


THANKS AGAIN FOR  YOUR GREAT WORK ...

MUCH APPRECIATED


Richard VE2DJE




Le 2020-11-02 à 07:22, Steve N4IRS a écrit :

apt-get install dvswitch-dashboard

On 11/2/20 6:58 AM, Richard (Joseph) VE2DJE wrote:
Thanks. Dvswitch installed and services are all running ok.
Will work on Android / Pyuc to clear out my questions.
No luck on Dvswitch  Server
Will get back to you 
We already have apache2 running.
Where can I get Dvswitch Dashboard to try installing it on the VPS. ??

Richard

Le dim. 1 nov. 2020 6 h 17 p.m., Steve N4IRS <szingman@...> a écrit :
Richard,
I suggest you use DVSwitch Server

If you are starting from scratch:

as root:
wget http://dvswitch.org/buster
chmod +x buster
./buster

apt-get update
apt-get install dvswitch will install analog-bridge, md380-emu, mmdvm-bridge, nxdngateway, nxdnparrot, p25gateway, p25parrot, ysfgateway, ysfparrot, ircddbgateway, quantar-bridge 

apt-get install dvswitch-server will install all of the above plus the menu and the dashboard.

If you want to continue from where you are:
edit /etc/apt/sources.list.d/dvswitch.list
change stretch to buster.
apt-get update
install from above.



On 11/1/20 5:50 PM, Richard (Joseph) VE2DJE wrote:

Running  Debian Stretch on  OVH VPS .   Asterisk is loaded  but was  stopped during compiling  ...


Got this error during compiling of the latest version



c++ -g -O3 -Wall -std=c++0x -pthread -c -o UDPSocket.o UDPSocket.cpp
UDPSocket.cpp: In member function ‘int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&)’:
UDPSocket.cpp:294:50: error: ‘LogMessage’ was not declared in this scope
    LogMessage("Re-opening UDP port on %u", m_port);
                                                                                                ^
Makefile:15: recipe for target 'UDPSocket.o' failed
make: *** [UDPSocket.o] Error 1..

root@vps275731:/srv/DVSwitch-System-Builder#





 I am  out of clue  >>>


Richard VE2DJE




Virus-free. www.avg.com


Re: #mmdvm_bridge #mmdvm_bridge

k7wby@...
 

O.K. That explains the problem better but leaves me without an answer. I have some suspicions and I have a hot spot that I can play and packet analyzer software so if you don't get it resolved let me know and I'll dig in to it.

Steve/K7WBY 


Re: Compiling error on ./DVSwitch-System-Builder.sh

Steve N4IRS
 

apt-get install dvswitch-dashboard

On 11/2/20 6:58 AM, Richard (Joseph) VE2DJE wrote:
Thanks. Dvswitch installed and services are all running ok.
Will work on Android / Pyuc to clear out my questions.
No luck on Dvswitch  Server
Will get back to you 
We already have apache2 running.
Where can I get Dvswitch Dashboard to try installing it on the VPS. ??

Richard

Le dim. 1 nov. 2020 6 h 17 p.m., Steve N4IRS <szingman@...> a écrit :
Richard,
I suggest you use DVSwitch Server

If you are starting from scratch:

as root:
wget http://dvswitch.org/buster
chmod +x buster
./buster

apt-get update
apt-get install dvswitch will install analog-bridge, md380-emu, mmdvm-bridge, nxdngateway, nxdnparrot, p25gateway, p25parrot, ysfgateway, ysfparrot, ircddbgateway, quantar-bridge 

apt-get install dvswitch-server will install all of the above plus the menu and the dashboard.

If you want to continue from where you are:
edit /etc/apt/sources.list.d/dvswitch.list
change stretch to buster.
apt-get update
install from above.



On 11/1/20 5:50 PM, Richard (Joseph) VE2DJE wrote:

Running  Debian Stretch on  OVH VPS .   Asterisk is loaded  but was  stopped during compiling  ...


Got this error during compiling of the latest version



c++ -g -O3 -Wall -std=c++0x -pthread -c -o UDPSocket.o UDPSocket.cpp
UDPSocket.cpp: In member function ‘int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&)’:
UDPSocket.cpp:294:50: error: ‘LogMessage’ was not declared in this scope
    LogMessage("Re-opening UDP port on %u", m_port);
                                                                                                ^
Makefile:15: recipe for target 'UDPSocket.o' failed
make: *** [UDPSocket.o] Error 1..

root@vps275731:/srv/DVSwitch-System-Builder#





 I am  out of clue  >>>


Richard VE2DJE




Re: Compiling error on ./DVSwitch-System-Builder.sh

 

Thanks. Dvswitch installed and services are all running ok.
Will work on Android / Pyuc to clear out my questions.
No luck on Dvswitch  Server
Will get back to you 
We already have apache2 running.
Where can I get Dvswitch Dashboard to try installing it on the VPS. ??

Richard

Le dim. 1 nov. 2020 6 h 17 p.m., Steve N4IRS <szingman@...> a écrit :
Richard,
I suggest you use DVSwitch Server

If you are starting from scratch:

as root:
wget http://dvswitch.org/buster
chmod +x buster
./buster

apt-get update
apt-get install dvswitch will install analog-bridge, md380-emu, mmdvm-bridge, nxdngateway, nxdnparrot, p25gateway, p25parrot, ysfgateway, ysfparrot, ircddbgateway, quantar-bridge 

apt-get install dvswitch-server will install all of the above plus the menu and the dashboard.

If you want to continue from where you are:
edit /etc/apt/sources.list.d/dvswitch.list
change stretch to buster.
apt-get update
install from above.



On 11/1/20 5:50 PM, Richard (Joseph) VE2DJE wrote:

Running  Debian Stretch on  OVH VPS .   Asterisk is loaded  but was  stopped during compiling  ...


Got this error during compiling of the latest version



c++ -g -O3 -Wall -std=c++0x -pthread -c -o UDPSocket.o UDPSocket.cpp
UDPSocket.cpp: In member function ‘int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&)’:
UDPSocket.cpp:294:50: error: ‘LogMessage’ was not declared in this scope
    LogMessage("Re-opening UDP port on %u", m_port);
                                                                                                ^
Makefile:15: recipe for target 'UDPSocket.o' failed
make: *** [UDPSocket.o] Error 1..

root@vps275731:/srv/DVSwitch-System-Builder#





 I am  out of clue  >>>


Richard VE2DJE



Re: Pi digital interface for Analog Radio (client)

 

Another issue is the FT-8900 doesn't have the T/R switching speed to enable it to be a fully Tier II compliant radio.  I agree with Steve, the best solution for this scenario is an analog repeater/gateway, with DVSwitch behind it for access to the digital networks.

On 2/11/20 7:25 am, Steve N4IRS wrote:
Jim,
Yes, you can mix and match components from a number of different project. The radio you describe would have to pick off the analog audio from the mic, send it through a vocoder and then send the datastream back to the transmitter and on to the DMR repeater. In the receive direction, the radio would have to pick off the the audio from the discriminator, send it to the vocoder. The analog audio would need to be injected back into the radio so the audio could be sent to the speaker. As of this is doable. There is one actual problem. The MMDVM software can look like a DMR repeater transmitter to a subscriber radio. The MMDVM software can look like a simplex signal (DMO) to a subscriber radio. What the MMDVM software can not do, is look like a subscriber radio to a DMR repeater. The same is true for traffic from a DMR repeater to the radio. The MMDVM software can not receive the output of a DMR repeater.

If I were trying to accomplish what you seem to want, I would put my money into the hill top repeater. I would build a high quality analog repeater. The would give you the best mobile coverage. Now couple that repeater with a Digital Voice bridge and you not only get DMR, you get all 5 digital modes plus analog repeater networking. This does assume the hill top repeater has internet access as would a DMR repeater.

Just my take. YMMV
73, Steve N4IRS    

On 11/1/20 3:01 PM, Jim Kusznir wrote:
Hi all:

So, as I reread this and talked to others, it sounded like my request may not have been all that clear, so here's another go, more from application than technical function:

I usually am mobile while on ham radio (VHF/UHF).  I just recently installed an FT-8900.  In my area, due to terrain, 6m is used (and is occasionally the only reliable way to get out).  Cell tower coverage is pretty spotty.

I'm looking to use an existing wide-area DMR repeater transmitting on actual ham bands at "repeater power" located on hilltops with wide range.  I'm looking to do this mobile, where an HT would NOT cut it.  I would rather not have two completely separate radios and antennas in my vehicle, and the only viable mobile I've even considered to this point is the Anytone 578.  Unfortunately, even if I did go the dual-radio route, the Anytone does not allow for separating the control head, and that is required in my vehicle.  So, that leaves me with no ability to use DMR when mobile, which is 90% of my ham radio activity.

What I wanted was a way to do DMR with my existing FT-8900, much like I can do 9600 baud packet with my FT-8900 by plugging in additional equipment to the jack on the back of the radio.  I was hoping to create a "DMR TNC" with its own little display, mic, and speaker, and have it connect to my FT-8900 and use it as a CLIENT on the DMR system, and NOT need any internet in my vehicle (or immediate vicinity).

So, to accomplish this, I see:
1) there ARE software packages that can work with a Pi to connect via IP to the DMR network and run as a client (with a mic/speaker), allowing all talk group access,etc., available on the IP connection you are using.  This is 1/2 of what I was looking for, but no IP connectivity to the DMR network...I want to use my radio.
2) there are solutions for using a Pi to connect to an analog radio and turn it into a hotspot/repeater and connect to the DMR system with IP.  However, I am not looking to be a "repeater" (server) but a user (client).

Ideally, I would like to take parts from both of the above and "mash them together" so that my software frontend will interface with a board (perhaps like the STMDVM, perhaps just an ADC like NWDR's DRAWs hat) which will connect with the analog radio.  Yea, I will likely need something like the ThumbDV or some other AMBE vocoder chip connected via USB....OK.  The missing piece seems to be some sort of software bits to act as an RF client.  I'm also wondering if this hasn't already been done because the analog radio cannot switch its transmitter on/off fast enough to do TDM as a client....If it actually isn't possible for this (or other technical reasons), please let me know!

One more thing: I am NOT limiting options to "ready built systems".  I am a tinkerer, and I am good with linux.  I'm sure I could get a DMR-AllStarLink system going or other such stuff.  I'm not an outright coder, so modding the source code of the client to implement what I'm looking for is beyond me, but I don't require something as neatly packaged as PiStar (but would gladly accept it if it were there!).

Thanks again all!
--Jim, K7LL


-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Hi Steve. All set this way. Different path for .ini and log. The system work well its not a issue to start and run mb1 and mb2. I runnning it in ysf without any issue and no crash in mb1 or2 if i only use fusion ysf . This issue appear when a user use hotspot with dmr2ysf . A the moment they it the ptt in dmr2ysf now  see the mb crash but for other use its ok like nxdn2ysf working good ysf2ysf reflector working good . Its only with dmr2ysf users . I double check my dvs and mb and all seem ok . Only in the dvs log  i see for the log the path is for the quantar but i dont no if i only use ysf part if he needed  to have the log path. I will try later in case of .... thank s again


Re: Compiling error on ./DVSwitch-System-Builder.sh

Steve N4IRS
 

Richard,
I suggest you use DVSwitch Server

If you are starting from scratch:

as root:
wget http://dvswitch.org/buster
chmod +x buster
./buster

apt-get update
apt-get install dvswitch will install analog-bridge, md380-emu, mmdvm-bridge, nxdngateway, nxdnparrot, p25gateway, p25parrot, ysfgateway, ysfparrot, ircddbgateway, quantar-bridge 

apt-get install dvswitch-server will install all of the above plus the menu and the dashboard.

If you want to continue from where you are:
edit /etc/apt/sources.list.d/dvswitch.list
change stretch to buster.
apt-get update
install from above.



On 11/1/20 5:50 PM, Richard (Joseph) VE2DJE wrote:

Running  Debian Stretch on  OVH VPS .   Asterisk is loaded  but was  stopped during compiling  ...


Got this error during compiling of the latest version



c++ -g -O3 -Wall -std=c++0x -pthread -c -o UDPSocket.o UDPSocket.cpp
UDPSocket.cpp: In member function ‘int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&)’:
UDPSocket.cpp:294:50: error: ‘LogMessage’ was not declared in this scope
    LogMessage("Re-opening UDP port on %u", m_port);
                                                                                                ^
Makefile:15: recipe for target 'UDPSocket.o' failed
make: *** [UDPSocket.o] Error 1..

root@vps275731:/srv/DVSwitch-System-Builder#





 I am  out of clue  >>>


Richard VE2DJE



Compiling error on ./DVSwitch-System-Builder.sh

 

Running  Debian Stretch on  OVH VPS .   Asterisk is loaded  but was  stopped during compiling  ...


Got this error during compiling of the latest version



c++ -g -O3 -Wall -std=c++0x -pthread -c -o UDPSocket.o UDPSocket.cpp
UDPSocket.cpp: In member function ‘int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&)’:
UDPSocket.cpp:294:50: error: ‘LogMessage’ was not declared in this scope
    LogMessage("Re-opening UDP port on %u", m_port);
                                                                                                ^
Makefile:15: recipe for target 'UDPSocket.o' failed
make: *** [UDPSocket.o] Error 1..

root@vps275731:/srv/DVSwitch-System-Builder#





 I am  out of clue  >>>


Richard VE2DJE


Re: #mmdvm_bridge #mmdvm_bridge

k7wby@...
 
Edited

Didn't see this error before sorry, I really need to be more attentive:

Segmentation fault (core dumped)

Caused by trying to write to the same log file from two different instances of mmdvm_bridge.

Fix: 
mkdir /var/lib/mmdvm/mb1
mkdir /var/lib/mmdvm/mb2
mkdir /var/lib/dvswitch/dvs1
mkdir /var/lib/dvswitch/dvs2

Change the log file locations in both of your new MMDVM_Bridge.ini and DVSwitch.ini files to point to the new locations
Also make sure that your new DMRIds.dat file locations are correct in your MMDVM_Bridge.ini files or you they won't get updated.


DVSwitch Server official release at 12:00 UTC October 31, 2020

Steve N4IRS
 

I have been asked to post this in other subgroups for the benefit of those not subscribed to the server subgroup <https://dvswitch.groups.io/g/Server>

We are pleased to introduce DVSwitch Server. DVSwitch Server provides the DVSwitch components, Analog_Bridge, MMDVM_Bridge and Quantar_Bridge. Included with DVSwitch Server are the necessary support programs for connecting to the Digital voice networks. Those programs are ircDDBGateway, NXDNGateway, P25Gateway and YSFGateway. For testing we have included NXDNParrot, P25Parrot and YSFParrot. Various other support programs are included as are scripting to make things all work together. When you install DVSwitch Server either from the apt repository or the Raspberry Pi image, all of the programs are installed and most are pre-configured ready for use.

DVSwitch has it's early roots in the AllStar analog network. AllStar provided a easy to use method of interconnecting analog voice repeater. We felt it made sense to add the ability to connect that analog repeater to the amateur digital voice networks for DMR, NXDN, P25 and YSF. DVSwitch was born and we continue to support AllStar today. The same components, Analog_Bridge and MMDVM_Bridge could also be used to build bridges between different digital voice networks. Some digital voice network bridges are very easy like NXDN to YSF. Others, like P25 to DMR can be more complex. At the end of the day it's all about how you configure the components.

One of the things we saw a need for is the ability to access both the analog network of AllStar and the digital voice networks. Enter DVSwitch Mobile and pyUC. DVSwitch Mobile is a Android based client capable of accessing analog and digital networks. pyUC provides the ability to connect to digital voice networks for desktop computer running Windows, Linux and macOS (can't just call it OSX anymore) If you can run Python on your desktop, you can run pyUC. DVSwitch Mobile and pyUC are the most configurable digital voice clients available today. I think I can say honestly, no other client provided the wealth of macro functionality coupled with user definable menus. These 2 features alone alloy you to "build it your way" I'll venture to say someone will do something we have not even thought of, and we wrote it!

For any of this to work, you need a server. That server can be as simple as a Raspberry Pi, or a 32/64 bit Intel or a cloud based system. DVSwitch Server runs on hardware using CPUs from ARM, Intel (and compatible) If you can run a Debian based Linux distribution (32 or 64 bit) you can probably run DVSwitch Server. For other Linux distributions such as Arch, Centos, etc, you will have to "roll your own" All of the binaries are on the DVSwitch GitHub repository. We have added some programs to DVSwitch Server to either make it easier to configure, or to display and control the server remotely. For configuration, we have include a menu system. The menu will guide you through entering the information needed to get the server up and running. If you don't want to use the menu or you use the menu to do the base configuration and then customize for your application that's fine. You are not locked into the menu.  We have included a web base dashboard to DVSwitch Server to let you see what is going on. One feature of the dashboard is the ability to listen to the received audio on a web browser. Last but not least is the ability to see the running services, view their resource utilization and if need be, restart services. This feature if deployed directly exposed to the Internet could cause problems, We have limited it's access to what are usually referred to as private IP address. (more later) 

DVSwitch Server includes a text based menu system to help you get up and running quickly. The menu is written by HL5KY. The menu will walk you through initial configuration of the server and help you install and maintain macros for use by DVSwitch Mobile. The menu has been translated into French, German, Greek, Japanese,  Korean, Polish and Spanish. It should take you no more then 10 minutes to configure the server from the menu. Included with the menu is a program to make a backup image of your SD card for the image. In the future you will also be able to backup just the configuration for transport to a new system. 

DVSwitch Server includes a dashboard you can use to view the system status. The dashboard is based on the Pi-Star dashboard and has been modified for DVSwitch by SP2ONG. The dashboard is display only, you can not change any settings from the dashboard. It is safe to expose the dashboard on a public IP address. We have added the ability to listen to the audio that would be sent to the client. In other words, if you have selected DMR on TG91 from DVSM or pyUC, that same audio is available to a web browser. If you don't want the feature available, you can disable it.

DVSwitch Server includes a System Monitor dashboard based on the program Monit. Monit is configured to monitor all of the DVSwitch Programs used in the server and will also allow you to stop / start / restart a service from a web browser. You can also reboot the server if you need to. Due to the nature of the abilities of System Monitor, Access is limited to private non-routable addresses.

We have built extensive scripting to support DVSwitch Server. I won't list all of the different scripts, but some of them take care of updating the host and user file daily so that you are always up to date when accessing a remote reflector or looking at the display on DVSwitch Mobile to see who is transmitting with name and callsign. Scripting is used to change digital modes and talkgroups / reflectors. All of this is available for you to use and add to. The heart of the scripting is a master script called, wait for it, dvswitch.sh. This script makes controlling all of the DVSwitch components and support programs easy and more importantly, to build your own scripts. Is there something we have not though of? You can script it yourself. You can call that script from DVSwitch Mobile with a macro or you can call that script from AllStar. How about connecting to your favorite talkgroup on Tuesday night from 8:00 to 10 PM? You can do that. I'm sure there are things people will want to do that we have not thought of. dvswitch.sh will handle the "heavy lifting" for you.  

The DVSwitch Server image is of course password protected. There is one user login defined on the image. That user is dvswitch. The image is distributed with a default password of "dvswitch" You will be FORCED to change that password on your first login. This is to protect you. You never want to expose a machine to the Internet with a known default password.  The root user is disabled from logging in. There is no back door. We can not remotely access your server. We have provided a method of resetting the password if you forget it. For this to work, you must have physical access to the Raspberry Pi. Power off the server and remove the SD card. Each Raspbian SD card  has a partition that can accessed from Windows, macOS or Linux. Insert the card into your desktop computer (or use a USB card reader) On the accessible partition (boot) place a file named "passwd_reset" This file should contains a single line of "login:password" where login is dvswitch and the password is your NEW password. for example, dvswitch:secret will reset the password for the user dvswitch to "secret" Reinsert the SD card back into the Raspberry Pi and power up. When the system is fully booted, the password has been reset. if you look at the boot partition, you will see a file named "passwd_reset_COMPLETE" if you still can not login, power down the Raspberry Pi and check the SD card. If something went wrong with the password reset, you will see a file on the boot partition named "passwd_reset_FAIL" If this is the case, you will have to use your backup SD card. (You did backup didn't you?)

Are there bugs? No, everything is perfect! Of course there will be bugs found. There will be enhancements added. Since all of the DVSwitch and support programs are built with apt, if a bug is found or a enhancement is added, all you have to do is apt-get update followed by apt-get upgrade. This will replace or upgrade the programs.  This is the method all Debian based systems handle bug fixes and enhancements. This works the same no matter if you are using the image or you installed DVSwitch from apt-get install. We have included scripting to help diagnose problems. One of the biggest issues is collecting the data we need to help you. Scripting is included to collect basic system information. This is a work in progress and will be enhanced over time.

We have included documentation to help you get up and running quickly. Some of you may remember the first DVSwitch Mobile documentation written by W8RIK. Joe expanded that documentation, and with the help of K2KXK, we have a more extensive document. I have to hand it to these guys, they were trying to write documentation while we were changing to program. Not a easy task!

We have in the works a set of tutorial videos by W0RMT to help people see and understand the system. We have the first two introductory videos are available at <https://youtu.be/ykW8oF1AGUc> and <https://youtu.be/5tx4yULb3r8> with more to come.  

Is that all there is? No, "Software means never having to say you are done" (with apologies to Erich Segal) We have more ideas to add features. We have some ideas to make DVSwitch easier to use in your application.  Without the help of HL5KY, W8RIK, SP2ONG , K2KXK, W0RMT and the beta test team, we would not be here today.

All of this is great, but WHERE DO I GET IT? (Really, you made me read that whole thing just to get here?) There are links on <https://dvswitch.groups.io/g/Server> and <http://dvswitch.org/DVSwitch-Server-RPi.zip> to the most current image and documentation in a zip file. We have also provided a link to the directory that contains those files in case all you need is one file out of the zip <http://dvswitch.org/files/DVSwitch_Images/Raspberry_Pi/Buster/>


Re: Pi digital interface for Analog Radio (client)

Steve N4IRS
 

Jim,
Yes, you can mix and match components from a number of different project. The radio you describe would have to pick off the analog audio from the mic, send it through a vocoder and then send the datastream back to the transmitter and on to the DMR repeater. In the receive direction, the radio would have to pick off the the audio from the discriminator, send it to the vocoder. The analog audio would need to be injected back into the radio so the audio could be sent to the speaker. As of this is doable. There is one actual problem. The MMDVM software can look like a DMR repeater transmitter to a subscriber radio. The MMDVM software can look like a simplex signal (DMO) to a subscriber radio. What the MMDVM software can not do, is look like a subscriber radio to a DMR repeater. The same is true for traffic from a DMR repeater to the radio. The MMDVM software can not receive the output of a DMR repeater.

If I were trying to accomplish what you seem to want, I would put my money into the hill top repeater. I would build a high quality analog repeater. The would give you the best mobile coverage. Now couple that repeater with a Digital Voice bridge and you not only get DMR, you get all 5 digital modes plus analog repeater networking. This does assume the hill top repeater has internet access as would a DMR repeater.

Just my take. YMMV
73, Steve N4IRS    

On 11/1/20 3:01 PM, Jim Kusznir wrote:
Hi all:

So, as I reread this and talked to others, it sounded like my request may not have been all that clear, so here's another go, more from application than technical function:

I usually am mobile while on ham radio (VHF/UHF).  I just recently installed an FT-8900.  In my area, due to terrain, 6m is used (and is occasionally the only reliable way to get out).  Cell tower coverage is pretty spotty.

I'm looking to use an existing wide-area DMR repeater transmitting on actual ham bands at "repeater power" located on hilltops with wide range.  I'm looking to do this mobile, where an HT would NOT cut it.  I would rather not have two completely separate radios and antennas in my vehicle, and the only viable mobile I've even considered to this point is the Anytone 578.  Unfortunately, even if I did go the dual-radio route, the Anytone does not allow for separating the control head, and that is required in my vehicle.  So, that leaves me with no ability to use DMR when mobile, which is 90% of my ham radio activity.

What I wanted was a way to do DMR with my existing FT-8900, much like I can do 9600 baud packet with my FT-8900 by plugging in additional equipment to the jack on the back of the radio.  I was hoping to create a "DMR TNC" with its own little display, mic, and speaker, and have it connect to my FT-8900 and use it as a CLIENT on the DMR system, and NOT need any internet in my vehicle (or immediate vicinity).

So, to accomplish this, I see:
1) there ARE software packages that can work with a Pi to connect via IP to the DMR network and run as a client (with a mic/speaker), allowing all talk group access,etc., available on the IP connection you are using.  This is 1/2 of what I was looking for, but no IP connectivity to the DMR network...I want to use my radio.
2) there are solutions for using a Pi to connect to an analog radio and turn it into a hotspot/repeater and connect to the DMR system with IP.  However, I am not looking to be a "repeater" (server) but a user (client).

Ideally, I would like to take parts from both of the above and "mash them together" so that my software frontend will interface with a board (perhaps like the STMDVM, perhaps just an ADC like NWDR's DRAWs hat) which will connect with the analog radio.  Yea, I will likely need something like the ThumbDV or some other AMBE vocoder chip connected via USB....OK.  The missing piece seems to be some sort of software bits to act as an RF client.  I'm also wondering if this hasn't already been done because the analog radio cannot switch its transmitter on/off fast enough to do TDM as a client....If it actually isn't possible for this (or other technical reasons), please let me know!

One more thing: I am NOT limiting options to "ready built systems".  I am a tinkerer, and I am good with linux.  I'm sure I could get a DMR-AllStarLink system going or other such stuff.  I'm not an outright coder, so modding the source code of the client to implement what I'm looking for is beyond me, but I don't require something as neatly packaged as PiStar (but would gladly accept it if it were there!).

Thanks again all!
--Jim, K7LL


Re: Pi digital interface for Analog Radio (client)

Jim Kusznir
 

Hi all:

So, as I reread this and talked to others, it sounded like my request may not have been all that clear, so here's another go, more from application than technical function:

I usually am mobile while on ham radio (VHF/UHF).  I just recently installed an FT-8900.  In my area, due to terrain, 6m is used (and is occasionally the only reliable way to get out).  Cell tower coverage is pretty spotty.

I'm looking to use an existing wide-area DMR repeater transmitting on actual ham bands at "repeater power" located on hilltops with wide range.  I'm looking to do this mobile, where an HT would NOT cut it.  I would rather not have two completely separate radios and antennas in my vehicle, and the only viable mobile I've even considered to this point is the Anytone 578.  Unfortunately, even if I did go the dual-radio route, the Anytone does not allow for separating the control head, and that is required in my vehicle.  So, that leaves me with no ability to use DMR when mobile, which is 90% of my ham radio activity.

What I wanted was a way to do DMR with my existing FT-8900, much like I can do 9600 baud packet with my FT-8900 by plugging in additional equipment to the jack on the back of the radio.  I was hoping to create a "DMR TNC" with its own little display, mic, and speaker, and have it connect to my FT-8900 and use it as a CLIENT on the DMR system, and NOT need any internet in my vehicle (or immediate vicinity).

So, to accomplish this, I see:
1) there ARE software packages that can work with a Pi to connect via IP to the DMR network and run as a client (with a mic/speaker), allowing all talk group access,etc., available on the IP connection you are using.  This is 1/2 of what I was looking for, but no IP connectivity to the DMR network...I want to use my radio.
2) there are solutions for using a Pi to connect to an analog radio and turn it into a hotspot/repeater and connect to the DMR system with IP.  However, I am not looking to be a "repeater" (server) but a user (client).

Ideally, I would like to take parts from both of the above and "mash them together" so that my software frontend will interface with a board (perhaps like the STMDVM, perhaps just an ADC like NWDR's DRAWs hat) which will connect with the analog radio.  Yea, I will likely need something like the ThumbDV or some other AMBE vocoder chip connected via USB....OK.  The missing piece seems to be some sort of software bits to act as an RF client.  I'm also wondering if this hasn't already been done because the analog radio cannot switch its transmitter on/off fast enough to do TDM as a client....If it actually isn't possible for this (or other technical reasons), please let me know!

One more thing: I am NOT limiting options to "ready built systems".  I am a tinkerer, and I am good with linux.  I'm sure I could get a DMR-AllStarLink system going or other such stuff.  I'm not an outright coder, so modding the source code of the client to implement what I'm looking for is beyond me, but I don't require something as neatly packaged as PiStar (but would gladly accept it if it were there!).

Thanks again all!
--Jim, K7LL

2421 - 2440 of 9775