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 to XLX
Patrick Perdue
Oh yes, I forgot to mention that the MMDVM_Bridge is in its own directory with different rx and tx ports in DVSwitch.ini to avoid conflict with the existing bridge.
toggle quoted messageShow quoted text
On Nov 30, 2019, at 16:49, Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: Brandmeister to XLX
Patrick Perdue
That was actually the first configuration I tried. Same result either with the Interface IP address, or local loopback. I’ll mess with it some more later. The MMDVM_Bridge part looks easy enough once I can get it talking to XLXD.
toggle quoted messageShow quoted text
On Nov 30, 2019, at 16:39, Ernie Gm7kbk <erniepratt@...> wrote:
|
|
|
|
Re: Brandmeister to XLX
See Ernie's reply AND since you are running 2 copies of MB, change the local post on one of them
Sent by smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 4:37:24 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] Brandmeister to XLX I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago. The relevant part of MMDVM_Bridge.ini looks like this:
[DMR Network]
Small part of the MMDVM_Bridge log: E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port. On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge
|
|
|
|
Re: Brandmeister to XLX
Use the ip address of the machine not 127.0.0.1
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 9:37:24 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] Brandmeister to XLX I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago. The relevant part of MMDVM_Bridge.ini looks like this:
[DMR Network]
Small part of the MMDVM_Bridge log: E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port. On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge
|
|
|
|
Re: Brandmeister to XLX
Patrick Perdue
I downloaded the latest MMDVM_Bridge earlier today. My current
issue is getting MMDVM-Bridge connected to XLXD on the same
machine. I'm sure I've directly connected a hotspot to the
reflector before, but that was a while ago. The relevant part of MMDVM_Bridge.ini looks like this:
[DMR Network]
Small part of the MMDVM_Bridge log: E: 2019-11-30 21:34:28.884 DMR, Connection to the master has
timed out, retrying connection tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.
On 11/30/2019 4:20 PM, Ernie Gm7kbk
wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge
|
|
|
|
Re: Brandmeister to XLX
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge
|
|
|
|
Re: Brandmeister to XLX
Patrick Perdue
OK. I just tried setting up an instance of MMDVM_Bridge to point to 127.0.0.1 on port 62030 (MMDVM) using the DMRNetwork. I thought XLXD responded to that, but apparently it doesn't, as the connection timed out.
On 11/30/2019 2:57 PM, Steve KC1AWV
wrote:
|
|
|
|
Cort N0MJS <n0mjs@...>
PLEASE TAKE NOTICE:
We have asked this many time. If you intend to ask for help, the following are absolutely mandatory. The people who write the software will not supply help if you do not: * Include the explicit names of the programs you’re running and how they’re connected. This isn’t “HBlink3” it’s probably bridge.py, probably not DMRlink, but IPSC_Bridge.py * Include copied of configuration files, rule files, etc. The files, or the text NO SCREENSHOTS * Include any pertinent, tracebacks (errors) and/or log files * NO SCREENSHOTS From this moment on, I will not offer or even respond to requests for help if these things are not included. Period.
-- Cort Buffington H: +1-785-813-1501 M: +1-785-865-7206
|
|
|
|
ai6bx
I have DMRlink configured and running with a bridge to a Motorola master as well as two peer moto DMR machines linked to a master instance I have built within DMRlink. I also have HBlink3 installed with a master for my hotspot. This seems to be running as well with no errors. As I have no interest at this point in linking to Brandmeister, I have not built an OpenBridge or built out the Repeater-1 profile so both are set to false. I can see my hotspot keying and can also see activity in the logfiles for DMRlink. What I am not seeing is traffic passing between the two. It feels like I am missing a stanza in the .cfg files or a bridge activating somewhere.
Any pointers would be appreciated.
|
|
|
|
Re: mmdvmb.service in amd64?
Dropped full path and now all is working as intended. Cloud instance of DVS supporting YSF, P25 and DMR (BM, TGIF and QRM).
tnx for help .-- Tom VE3NY
|
|
|
|
Re: Brandmeister to XLX
DMRGateway is not required. I have made a note in my old doc that reflects this. I will be creating a new doc that should be available after the holidays. Steve KC1AWV
On Sat, Nov 30, 2019, 2:55 PM Patrick Perdue <patrick@...> wrote: Hello:
|
|
|
|
Brandmeister to XLX
Patrick Perdue
Hello:
I found an old docc referring to using two instances of MMDVM_Bridge and DMRGateway to bridge DMR to XLX. Is this necessary anymore, or can we now just use two instances of MMDVM_Bridge, since it seems you can now specifically address XLX modules? I want to use XLX and ambed for transcoding DMR to D-STAR (DCS via XLXD) since this is already in place, and bridge between that and Brandmeister.
|
|
|
|
Re: mmdvmb.service in amd64?
You don't need the full path
toggle quoted messageShow quoted text
systemctl status mmdvm_bridge systemctl start mmdvm_bridge ststemctl stop mmdvm_bridge systemctl enable mmdvm_bridge What is the result of systemctl status mmdvm_bridge? what is the result (not just it did not work) of systemctl start mmdvm_bridge? what is the result of ls /lib/systemd/system/mmdvm_bridge.service?
On 11/30/19 7:28 AM, Tom Corcoran
wrote:
|
|
|
|
Re: mmdvmb.service in amd64?
I have tried systemctl restart /lib/systemd/system/mmdvm_bridge.service as well as /lib/systemd/system/mmdvm_bridge.service restart and system doesn't restart to reset the MMDVM_Bridge.ini file. Macro makes the change but does not restart. Am I missing something? tnx ... Tom VE3NY
|
|
|
|
Re: Dvswitch software not running on Odroid N2
Ernie,
toggle quoted messageShow quoted text
Thanks for trying them out. Steve
On 11/30/19 5:08 AM, Ernie Gm7kbk
wrote:
Hello Steve
|
|
|
|
Re: Dvswitch software not running on Odroid N2
Hello Steve
Working fine on Odroid N2 running Ubuntu. Thanks
|
|
|
|
Re: mmdvmb.service in amd64?
I'm going to guess you want mmdvm_bridge.service it is in
/lib/systemd/system
toggle quoted messageShow quoted text
That being said, you should not need to touch the service file. Just rename MMDVM_Bridge.amd64 to MMDVM_Bridge Steve N4IRS
On 11/29/19 7:14 PM, Tom Corcoran
wrote:
I can graze on winscp, but please ... where is file?
|
|
|
|
Re: mmdvmb.service in amd64?
I can graze on winscp, but please ... where is file?
-- Tom VE3NY
|
|
|
|
Re: Dvswitch software not running on Odroid N2
I now have a board that will do aarch64 (arm64) I bought a RPi4 and I'm running Ubuntu 19.10 on it.
I have pushed MMDVM_Bridge.arm64 and Analog_Bridge.arm64 to GitHub. I will build the other support programs over the next few days. The ONLY testing I did was to make sure the executables ran. I will be doing full testing as I build the support programs. 73, Steve N4IRS
|
|
|
|
Re: mmdvmb.service in amd64?
jim.lathan@...
Try the command in terminal, if it returns without go for it
On Fri, Nov 29, 2019 at 5:17 PM Tom Corcoran <tcorcoran@...> wrote: tnx for speedy response .
|
|
|