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: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.
Hello EA5GVK Joaquin,
can you explain what I am looking at on the desktop?? -- Tom VE3NY
|
|
|
|
test
Pierre Martel
Just making a test
|
|
|
|
Re: USRP connection on the Windows IAXRPT client?
There will be a Windows (Python3) USRP client.
Sent by smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve KC1AWV <smiller@...>
Sent: Monday, October 7, 2019 11:54:50 AM To: main@dvswitch.groups.io <main@dvswitch.groups.io> Subject: Re: [DVSwitch] USRP connection on the Windows IAXRPT client? If you're talking the Xelatec (xipar) IAXRPT dispatch console, I don't think so. It's closed source as well, so a separate Windows client would be needed to build in the USRP functions I believe.
On Mon, Oct 7, 2019 at 11:38 AM Russell, KV4S <russelljthomas@...> wrote:
-- Steve Miller
KC1AWV
|
|
|
|
Re: USRP connection on the Windows IAXRPT client?
If you're talking the Xelatec (xipar) IAXRPT dispatch console, I don't think so. It's closed source as well, so a separate Windows client would be needed to build in the USRP functions I believe.
On Mon, Oct 7, 2019 at 11:38 AM Russell, KV4S <russelljthomas@...> wrote:
-- Steve Miller KC1AWV
|
|
|
|
USRP connection on the Windows IAXRPT client?
This may not be available but does anyone know if you can configure the Windows client to talk to USRP?
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
OK, on github is version from M: 2019-10-07 06:55:32.816 Built 10:28:48 Jul 1 2019 (GitID #43be6b4)
You have update 2 July and this version has working XLX but is not avilabel as binary on GitHub 73 Waldek
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Please read the thread below.
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
SP2ONG Waldek
Hi Mike,
toggle quoted messageShow quoted text
I have try used "options=XLX:4004" but is not working me with XLX reflectror, I have used I: 2019-10-07 06:55:32.815 MMDVM_Bridge: I: 2019-10-07 06:55:32.816 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2019-10-07 06:55:32.816 Hacks by Mike N4IRR and Steve N4IRS I: 2019-10-07 06:55:32.816 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I: 2019-10-07 06:55:32.816 This software is for use on amateur radio networks only, I: 2019-10-07 06:55:32.816 it is to be used for educational purposes only. Its use on I: 2019-10-07 06:55:32.816 commercial networks is strictly prohibited. I: 2019-10-07 06:55:32.816 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2019-10-07 06:55:32.816 MMDVM_Bridge-20180423 is starting M: 2019-10-07 06:55:32.816 Built 10:28:48 Jul 1 2019 (GitID #43be6b4) ........ I: 2019-10-07 06:51:39.717 DMR Network Parameters I: 2019-10-07 06:51:39.717 Address: 172.16.1.10 I: 2019-10-07 06:51:39.717 Port: 62030 I: 2019-10-07 06:51:39.717 Local: 52033 I: 2019-10-07 06:51:39.717 Jitter: 360ms I: 2019-10-07 06:51:39.717 Slot 1: disabled I: 2019-10-07 06:51:39.717 Slot 2: enabled I: 2019-10-07 06:51:39.717 Mode Hang: 3s I: 2019-10-07 06:51:39.717 Options: XLX:4004 ..... M: 2019-10-07 06:55:33.010 MMDVM_Bridge-20180423 is running D: 2019-10-07 06:55:43.053 DMR, Sending authorisation D: 2019-10-07 06:55:43.089 DMR, Sending configuration D: 2019-10-07 06:55:43.129 DMR, Sending options M: 2019-10-07 06:55:43.165 DMR, Logged into the master successfully
On Thu, Oct 3, 2019 at 09:11 AM, Mike Zingman - N4IRR wrote:
Correct syntax for MB is
|
|
|
|
USPR and GPIO (4 wire analog interface) to P25
#mmdvm_bridge
#analog_bridge
Hi,
I was wondering if there is any progress in using analog audio with (PTT and COS via a Pi GPIO) _> USPR --- analog bridge -- P25 MMDVM Gateway. Any help would be greatly appreciated. Currently using a MMDVM hotspot - P25 radio to Analog 4 wire E+M circuit I'm sure this can be achieved with DVSwitch and P25 Gateway via USPR. Thanks Tim VK3TIM
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Yes, we are aware.
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Steve and Mike,
I suppose MMDVM_Bridge is based on MMDVMHost and looking at the sources in the version.h file https://github.com/g4klx/MMDVMHost/blob/master/Version.h#L22 there is information about the software version. Maybe it will be nice to put, for example, "20190701-MMDVM_Bridge" just like Andy does in MMDVMHost for Pi-Star: "20190923-Pi_Star" I suspect why I see "MMDVM_Unknow" in the "PACKAGE_ID" field of the Hombrew protocol from MMDVM_Bridge. Looking for MMDVMHost sources in DMRNetwork.cpp https://github.com/g4klx/MMDVMHost/blob/0b9c1b13629901803f8a3d63bec2695ad13c5269/DMRNetwork.cpp#L576 is placed in PACKAGE_ID information about the hardware/modem used. Because MMDVM_Bridge does not use a hardware modem, it is "MMDVM_Unknown" it looks OK, but it might be better to enter the "NONE" :-), but there is cosmetic information when we displayed information about connected systems / users, such as on maps or BM status, etc.: http://bm.ham-dmr.pl/status/list.htm 73 Waldek SP2ONG
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
SP2ONG Waldek
These values are shown in HBmonitor so it's probably worth to correspond to reality, i.e. version and type MMDVM (currently shows MMDVM_Unknow) but it is not urgent
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
I'll put it on the list.
toggle quoted messageShow quoted text
Are you actually testing for those values somewhere or is it cosmetic? Steve N4IRS
On 10/4/19 12:41 AM, Waldek SP2ONG wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
SP2ONG Waldek
Hi Steve and Mike When you compile the new version of MMDVM_Bridge, please update the information in the code with the version information from 20180423 to the current one and maybe MMDVM_Bridge will send PACKAGE_ID information in HBP, e.g. MMDVM_BRIDGE? Waldek
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
The build date is when I build it. The latest available version will
always be on the github site. I usually will update github when Mike
and I are doing a lot of bug fixes or enhancements. When Mike and I
feel it's ready, I will package it up into the apt repository.
toggle quoted messageShow quoted text
Steve
On 10/3/19 7:37 PM, Adrian Fewster
wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
I'm so glad.
toggle quoted messageShow quoted text
On 10/3/19 7:25 PM, Adrian Fewster
wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
You are talking about the published binary. Mike is talking about
the source.
toggle quoted messageShow quoted text
On 10/3/19 7:15 PM, Adrian Fewster
wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
Actually the latest commit date is beyond that. Several other issues/features were also addressed.
The XLX commit date is July 2
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
As I said, I will be doing a fresh build in the next day or so.
toggle quoted messageShow quoted text
On 10/3/19 6:38 PM, Adrian Fewster
wrote:
|
|
|
|
Re: MMDVM_BRIDGE and connect to XLX selected Module
#mmdvm_bridge
When you run MB the following will get logged and or output to the
screen:
toggle quoted messageShow quoted text
I: 2019-10-03 18:02:31.326 MMDVM_Bridge: I: 2019-10-03 18:02:31.326 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2019-10-03 18:02:31.326 Hacks by Mike N4IRR and Steve N4IRS I: 2019-10-03 18:02:31.326 = I: 2019-10-03 16:24:08.319 This software is for use on amateur radio networks only, I: 2019-10-03 16:24:08.319 it is to be used for educational purposes only. Its use on I: 2019-10-03 16:24:08.319 commercial networks is strictly prohibited. I: 2019-10-03 16:24:08.319 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2019-10-03 16:24:08.319 MMDVM_Bridge-20180423 is starting M: 2019-10-03 16:24:08.319 Built 10:47:32 Jun 24 2019 (GitID #30648ec) I have bolded the important information. The version "number: MMDVM_Bridge-20180423 is starting Will be updated the next major revision/release. Steve N4IRS
On 10/3/19 5:54 PM, Adrian Fewster
wrote:
|
|
|
