toggle quoted messageShow quoted text
In the hblink.cfg:
Configure REPEATER-1 to point to your DM Master
The fields pretty much mimic the settings used for a MMDVM.
Start hblink in the foreground with python hblink.py
You should see it connect to the master and login.
On 01/14/2018 03:29 PM, Ed W8VT wrote:
Well the only think that I know that
actually works is the AllStar portion.
I also did the preliminary tests and seem to communicate with
the DV Dongle.
As far as HBLink and bridge, I'm not even sure if I have it
installed correctly in the proper directories and the proper way
to start and stop it.
Just kind of lost at this point. Your help is greatly
On 01/14/2018 02:59 PM, Steve N4IRS wrote:
Build from the outsides in.
Get HB_Bridge connected to BM.
You should be able to connect to the BM server and after
configuring the TG on the selfcare page, you should see data
from the TG in the HB log.
Configure AllStarLink with the USRP channel driver on the
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your
While Analog_Bridge is running in the foreground, you should see
traffic from ASL to Analog_Bridge
When you have both sides working run everything on the
On 01/14/2018 02:41 PM, JJ Cummings
Have you gotten HBlink working independent of Analog_Bridge?
Sent from the iRoad
The goal is to have a bridge
from Allstar to Brandmeister TG 313938 (cluster of
repeaters in SE OH).
Private Allstar node 1952 that can be connected when
Currently have this on a Raspberry Pi 2 with USB AMBE
On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Why don't you start with what you are trying to
accomplish and we can go from there.
73, Steve N4IRS
On 01/14/2018 12:40 PM, Ed
point, think I'm lost, dazed and confused (more than
normal). Is there a guru out there that might log in
and see if I have this stuff installed properly and
help explain some of the configs?