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: DMRlink <-> HBlink communication
Bob kc2cwt
It was
On 07/12/2017 07:31 PM, Steve N4IRS
wrote:
run it in the foreground. -- Bob KC2CWT Carmel NewYork USA (914)497-5502
|
|
|
|
Re: DMRlink <-> HBlink communication
run it in the foreground.
toggle quoted messageShow quoted text
On 07/12/2017 07:30 PM, Bob kc2cwt
wrote:
|
|
|
|
Re: DMRlink <-> HBlink communication
Bob kc2cwt
Just checking as DMR-Link shout down to day and i see nothing in the logs . Did a restart and it working great On 07/12/2017 07:28 PM, Steve N4IRS
wrote:
You are already running the current hblink and dmrlink -- Bob KC2CWT Carmel NewYork USA (914)497-5502
|
|
|
|
Re: DMRlink <-> HBlink communication
You are already running the current hblink and dmrlink
toggle quoted messageShow quoted text
On 07/12/2017 07:17 PM, Bob kc2cwt
wrote:
|
|
|
|
Re: DMRlink <-> HBlink communication
Bob kc2cwt
What would be the best way to up date hb link and dmr link
On 07/12/2017 07:12 PM, Steve N4IRS
wrote:
Lets make sure you are running the current dmr_utils: -- Bob KC2CWT Carmel NewYork USA (914)497-5502
|
|
|
|
Re: DMRlink <-> HBlink communication
Lets make sure you are running the current dmr_utils:
toggle quoted messageShow quoted text
apt-get install python-dev -y apt-get install python-pip -y apt-get install python-twisted -y pip install bitstring pip install bitarray cd /opt git clone https://github.com/n0mjs710/dmr_utils.git cd dmr_utils/ pip install --upgrade . Notice the period at the end of the last line. I don't think this is it, but "it couldn't hurt." Steve
On 07/12/2017 06:58 PM, David Griffith
NZ6D wrote:
That did it. I am receiving the TG now. But whe I TX I get the following:
|
|
|
|
Re: DMRlink <-> HBlink communication
David Griffith NZ6D
That did it. I am receiving the TG now. But whe I TX I get the following:
Unhandled Error Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 73, in callWithContext return context.call({ILogContext: newCtx}, func, *args, **kw) File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext return func(*args,**kw) File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 614, in _doReadOrWrite why = selectable.doRead() --- <exception caught here> --- File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 246, in doRead self.protocol.datagramReceived(data, addr) File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 184, in datagramReceived self.func(_data, (_host, _port)) File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 261, in import_datagramReceived self.send_voice_header(_rx_slot) File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 526, in send_voice_header self.rewriteFrame(self._tempHead[i], _rx_slot.slot, _rx_slot.dst_id, _rx_slot.rf_src, _rx_slot.repeater_id) File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 562, in rewriteFrame _peerid = _frame[1:5] # int32 peer who is sending us a packet exceptions.TypeError: 'int' object has no attribute '__getitem__'
|
|
|
|
Re: DMRlink <-> HBlink communication
I really suggest you clone the 2 branch repositories and work from
there. Setup hblink.cfg and dmrlink.cfg as you did before. Leave
HB_Bridge.cfg and IPSC_Bridge.cfg just like they are. stop hblink
and dmrlink. start HB_Bridge.py and IPSC_Bridge.py both in the
foreground, so you can see what is happening.
toggle quoted messageShow quoted text
Steve
On 07/12/2017 05:11 PM, David Griffith
NZ6D wrote:
Thank you Steve (et all)
|
|
|
|
Re: DMRlink <-> HBlink communication
David Griffith NZ6D
Thank you Steve (et all)
I was a little confused. I did a new git clone and it looked like what I already had. But no HB_Bridge or IPSC_Bridge. So I grabbed each py and cfg off of each repository. I am running each and trying to figure out the cfg file ports section on each. Thanks.
|
|
|
|
DV3000 testing results
We have spent the last couple of weeks working with the DV3000u and below are our results.
This what we sent to NorthWest Digital ===================================================================================================
Two additional pieces of information. I moved the DV3000u to a D-Link powered hub. I ran AMBEtest4.py for 100,000 iterations. --- "What are HB_Bridge, IPSC_Bridge and Analog_Bridge?"
|
|
|
|
Re: DMRlink <-> HBlink communication
Rob,
toggle quoted messageShow quoted text
David is correct, For what you are trying to do, you need HB_Bridge and IPSC_Bridge. IPSC_Bridge is at <https://github.com/n0mjs710/DMRlink/tree/IPSC_Bridge> HB_Bridge is at <https://github.com/n0mjs710/HBlink/tree/HB_Bridge> If you are doing a git pull then you need to add the branch. git pull -b IPSC_Bridge https://github.com/n0mjs710/DMRlink.git git pull -b HB_Bridge https://github.com/n0mjs710/HBlink.git 73, Steve N4IRS
On 7/12/2017 3:03 PM, Rob WX1N wrote:
|
|
|
|
Re: DMRlink <-> HBlink communication
Rob WX1N
Hi David,
HBlink and DMRlink can’t talk to each other directly - you need to use HB_bridge and IPSC_bridge.
Rob, WX1N
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of David Griffith NZ6D
I am trying to get DMRlink peer to talk to hb_bridge_all. I have the peer set up and talking to the master in DMRlink with no issues. I have looked at the rules for both DMRlink and HBlink and hb_bridge_all. and have tried all kinds of different routing configurations. I can connect to my hblink master and see that I am transmitting but hblink will not forward to dmrlink and visa versa. I have tried hb_parrot and it works fine. Any help would be appreciated.
|
|
|
|
DMRlink <-> HBlink communication
David Griffith NZ6D
I am trying to get DMRlink peer to talk to hb_bridge_all. I have the peer set up and talking to the master in DMRlink with no issues. I have looked at the rules for both DMRlink and HBlink and hb_bridge_all. and have tried all kinds of different routing configurations. I can connect to my hblink master and see that I am transmitting but hblink will not forward to dmrlink and visa versa. I have tried hb_parrot and it works fine. Any help would be appreciated.
|
|
|
|
Re: Administrative request
We are now up to 80 members here. I have to say, I'm a little surprised. I REALLY, REALLY, REALLY would like to ask everyone to include their call sign in their display name in their profile.
73, Steve N4IRS
|
|
|
|
Re: Beta testing of DummyRepeater for ASL
This is interesting. What was the error?
toggle quoted messageShow quoted text
Thanks, Steve
On 07/09/2017 10:07 PM, Richard
(Joseph) VE2DJE wrote:
|
|
|
|
Re: Beta testing of DummyRepeater for ASL
Just finished my testing with the Powered USB HUB.
Here is my setup ALL Software running on a single Rpi3… . MMDVM | AST - Analog_Bridge – HB_Bridge – hb_confbridge – hbparrot | | ThumbDV BMServer 3021.
Confbridge has 3 rules TG9TS2 to AST TG9991TS2 to Parrot TG3027TS1 to BM .
ONLY ThumbDV plugged in powered hub . MMDVM Arduino Due plugged directly on RPi3 USB port Errors in ThumbDV test ( AMBEtest4.py) if mmdvm is plugged in powered USB Hub …
All functionnal . Max CPU use I have seen is 25 %
Richard VE2DJE
Provenance : Courrier pour Windows 10
|
|
|
|
Re: Beta testing of DummyRepeater for ASL
You should be able to listen to TG 3112122 on hoseline.
toggle quoted messageShow quoted text
On 07/09/2017 04:28 PM, David KE6UPI
wrote:
|
|
|
|
Re: Beta testing of DummyRepeater for ASL
David KE6UPI
Is there a way to listen to D-Star online like BrandMeister's Hoseline? David -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Sun, Jul 9, 2017 at 9:55 AM, Steve N4IRS <szingman@...> wrote: From the just for the heck of it department. To test the Raspberry with 2 Vocoders, I am running the following.
|
|
|
|
Re: Beta testing of DummyRepeater for ASL
From the just for the heck of it department. To test the Raspberry with 2 Vocoders, I am running the following.
BM (TG 3112122) <--> HB_Bridge <--> Analog_Bridge <--> DummyRepeater <---> DCS006T Both Analog_Bridge (AB) and DummyRepeater (DR) have Vocoders. AB is using the PiDV and DR is using the ThumbDV plugged into the powered hub. This is NOT the way to do this long term. This is just a test. I expect I'll put one side or the other to move a lot of traffic between the 2 networks. 73, Steve N4IRS
|
|
|
|
Re: Beta testing of DummyRepeater for ASL
Here is what I have on the hub I'm using. I do not think it is
anything special.
toggle quoted messageShow quoted text
lsusb: Bus 001 Device 012: ID 2001:f103 D-Link Corp. DUB-H7 7-port USB 2.0 hub Label reads: P/N: BDUBH7....A2 (Yes, the periods are in the Part Number) H/W Ver. : A2 Power Supply is 5V 3A
On 07/09/2017 12:05 AM, Richard
(Joseph) VE2DJE wrote:
|
|
|