A quick how to on getting IPSC_Bridge , HB_Bridge and HBlink3 installed


area51now@...
 
Edited

In the beginning for me it was a major Hurdle just to get all the programs installed and with help of the experts on this forum and a lot of google searches I was able to make it all work.  Hopefully below info will be helpful for those just starting out with dmrlink, hblink & HBlink3 getting it all installed on Debian 10, once installed you can edit the config files to get it all running.

Debian 10  X64
 
# as root
apt-get update
apt-get upgrade -y
apt-get install git -y
apt-get install python-pip -y
apt-get install python3-pip -y
apt-get install python-twisted -y
apt-get install python3-twisted -y
pip install dmr-utils
pip3 install dmr-utils3

#as a regular user
git clone -b IPSC_Bridge https://github.com/HBLink-org/DMRlink.git
git clone -b HB_Bridge https://github.com/HBLink-org/HBLink.git
git clone https://github.com/HBLink-org/hblink3.git

# copying config files
cp DMRlink/dmrlink_SAMPLE.cfg DMRlink/dmrlink.cfg
cp HBLink/hblink-SAMPLE.cfg HBLink/hblink.cfg
cp hblink3/hblink-SAMPLE.cfg hblink3/hblink.cfg
cp hblink3/rules_SAMPLE.py hblink3/rules.py

# Starting the programs
DMRlink: python IPSC_Bridge.py
HBlink:  python HB_Bridge.py
HBlink3: python3 bridge.py

Enjoy

Bob

KB6LED
(Repository URL's updated 10/18/20)


ai6bx
 

This is a great process and order. I am curious what your dmrlink.cfg file looks like supporting several Moto DMR repeaters. I have it working with a single master instance and single peer instance however adding additional repeaters has caused none to work. I would assume I create a new peer instance for each repeater and have that instance point to my master instance. Am I wrong?


area51now@...
 

For each  moto trbo repeater on my server I added another instance of both  dmrlink and hblink,

Moto rpt 1 -<->-- IPSC_Bridge<->hblink
                                                              <->HBlink-3
Moto rpt 2- <->-- IPSC_Bridge<->hblink


Bob


ai6bx
 

Bob, I assume you added each instance in the dmrlink.cfg file correct? Did you add each Moto as a peer or master? I currently have the entries as peers.


area51now@...
 

What I meant was, I installed yet another instance of dmrlink and hblink I just made another directory for each to put them in and then configured each of those cfg. files. Since all my dmrlink and hblink instances reside in my opt directory  I just named each of the instances like dmrlink,dmrlink1, dmrlink2 etc hblink, hblink1,hblink2 etc it just made it easy for me to keep track of what was what. maybe someone can suggest more efficient method for adding additional instances .


Bob


Cort N0MJS <n0mjs@...>
 

There’s no need to make an entire 2nd copy to run multiple instances. You can specify a configuration files on the command line when you start the programs. When you do not, you’re just accepting the default. Here’s an example of multiple IPSC_Bridge.py and HB_Bridge.py instances running with only one copy:

python /home/cort/dmrlink/IPSC_Bridge.py -c /home/cort/dmrlink/k0pro.conf -b /home/cort/dmrlink/k0pro_bridge.conf
python /home/cort/hblink/HB_Bridge.py -c /home/cort/hblink/k0pro.conf -b /home/cort/hblink/k0pro_bridge.conf

python /home/cort/dmrlink/IPSC_Bridge.py -c /home/cort/dmrlink/ks-dmr_na-ww.conf -b /home/cort/dmrlink/ks-dmr_na-ww_bridge.conf
python /home/cort/hblink/HB_Bridge.py -c /home/cort/hblink/ks-dmr_na-ww.conf -b /home/cort/hblink/ks-dmr_na-ww_bridge.conf

python /home/cort/dmrlink/IPSC_Bridge.py -c /home/cort/dmrlink/ks-dmr_wwe-ks.conf -b /home/cort/dmrlink/ks-dmr_wwe-ks_bridge.conf
python /home/cort/hblink/HB_Bridge.py -c /home/cort/hblink/ks-dmr_wwe-ks.conf -b /home/cort/hblink/ks-dmr_wwe-ks_bridge.conf

This is UNIX guys, try invoking things with the -h flag. You can learn some valuable stuff:

cort@pollux:~/dmrlink$ python dmrlink.py -h
usage: dmrlink.py [-h] [-c CFG_FILE] [-ll LOG_LEVEL] [-lh LOG_HANDLERS]

optional arguments:
  -h, --help            show this help message and exit
  -c CFG_FILE, --config CFG_FILE
                        /full/path/to/config.file (usually dmrlink.cfg)
  -ll LOG_LEVEL, --log_level LOG_LEVEL
                        Override config file logging level.
  -lh LOG_HANDLERS, --log_handle LOG_HANDLERS
                        Override config file logging handler.
cort@pollux:~/dmrlink$ 



On Nov 26, 2019, at 8:10 PM, area51now via Groups.Io <area51now@...> wrote:

What I meant was, I installed yet another instance of dmrlink and hblink I just made another directory for each to put them in and then configured each of those cfg. files. Since all my dmrlink and hblink instances reside in my opt directory  I just named each of the instances like dmrlink,dmrlink1, dmrlink2 etc hblink, hblink1,hblink2 etc it just made it easy for me to keep track of what was what. maybe someone can suggest more efficient method for adding additional instances .


Bob

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






area51now@...
 

Thanks Cort, I guess I been doing the hard way ;)

Bob


Alex IK7SEC
 

Hi Cort,  

just to clarify, multiple instances are required only if every ipsc repeaters have different TG routings, for example because they have different own tg, or they are always required ?

 


area51now@...
 

Alex I believe your going to have to add another instance for each repeater.

Bob


Cort N0MJS <n0mjs@...>
 

Multiple repeaters in the same IPSC system are fine. The underlying dmrlink.py that lives beneath IPSC_Bridge.py will process all traffic as an IPSC peer regardless. When I say peer, I mean it in the true sense, not the role a device plays in IPSC Link Establishment.

On Nov 29, 2019, at 3:36 PM, Alex IK7SEC <ik7sec@...> wrote:

Hi Cort,  

just to clarify, multiple instances are required only if every ipsc repeaters have different TG routings, for example because they have different own tg, or they are always required ?

 

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






N3MEL <n3mel.epa@...>
 

It appears that the Github URL https://github.com/n0mjs710/HBlink.git to the install files for HBlink are no longer available?   


Michael Karp
 

It would appear as such... :\


area51now@...
 

Also no go here, maybe the repository is being worked on.

Bob


Corey Dean N3FE
 

I am sure there are other forks of the software out there.  You are correct, it is no longer available.  Please remember this whole thing started with Cort writing it for the K0USY group. With all the request from users, in my personal opinion, it was pulling him away from his main goal of development for the K0USY system.  The repo was used as his storage location and it was opened up for others to use.  This became a problem because users would say it didn't work and he was in the middle of working on it.  Cort did make a post about this many times in the past.

With all the other forks out there maybe it is time for other people/groups to pick this project up and start working on it.

Corey  N3FE

 


On 2020-10-14 17:36, area51now via groups.io wrote:

Also no go here, maybe the repository is being worked on.

Bob


Michael Karp
 

Unfortunate that a group of a few people pulled him away so much that it had to come down. I’m not a developer by any means, but would be happy to contribute any way I can. 

I guess my only question would be if the existing repo in use by my system would have to worry about anything in the future that would make the existing repo stop working as is... spent quite some time bringing it up for a local cluster on the east coast and am very thankful for the work put in... but also need to plan ahead to make sure that it will function properly for the forseable future, assuming we don’t expose the system to the internet. 

:)

On Thu, Oct 15, 2020 at 8:09 AM Corey Dean N3FE <n3fe@...> wrote:

I am sure there are other forks of the software out there.  You are correct, it is no longer available.  Please remember this whole thing started with Cort writing it for the K0USY group. With all the request from users, in my personal opinion, it was pulling him away from his main goal of development for the K0USY system.  The repo was used as his storage location and it was opened up for others to use.  This became a problem because users would say it didn't work and he was in the middle of working on it.  Cort did make a post about this many times in the past.

With all the other forks out there maybe it is time for other people/groups to pick this project up and start working on it.

Corey  N3FE

 


On 2020-10-14 17:36, area51now via groups.io wrote:

Also no go here, maybe the repository is being worked on.

Bob


Corey Dean N3FE
 

I would like to clarify something.  That email I sent was not Cort’s words.  That was just my thoughts or opinion was all and nothing more.

Corey


On Oct 15, 2020, at 8:26 AM, Michael Karp <kn4kcw@...> wrote:


Unfortunate that a group of a few people pulled him away so much that it had to come down. I’m not a developer by any means, but would be happy to contribute any way I can. 

I guess my only question would be if the existing repo in use by my system would have to worry about anything in the future that would make the existing repo stop working as is... spent quite some time bringing it up for a local cluster on the east coast and am very thankful for the work put in... but also need to plan ahead to make sure that it will function properly for the forseable future, assuming we don’t expose the system to the internet. 

:)

On Thu, Oct 15, 2020 at 8:09 AM Corey Dean N3FE <n3fe@...> wrote:

I am sure there are other forks of the software out there.  You are correct, it is no longer available.  Please remember this whole thing started with Cort writing it for the K0USY group. With all the request from users, in my personal opinion, it was pulling him away from his main goal of development for the K0USY system.  The repo was used as his storage location and it was opened up for others to use.  This became a problem because users would say it didn't work and he was in the middle of working on it.  Cort did make a post about this many times in the past.

With all the other forks out there maybe it is time for other people/groups to pick this project up and start working on it.

Corey  N3FE

 


On 2020-10-14 17:36, area51now via groups.io wrote:

Also no go here, maybe the repository is being worked on.

Bob


Corey Dean N3FE
 

I would like to clarify something.  That email I sent was not Cort’s words.  That was just my thoughts or opinion was all and nothing more.

Corey


On Oct 15, 2020, at 8:08 AM, Corey Dean <n3fe@...> wrote:



I am sure there are other forks of the software out there.  You are correct, it is no longer available.  Please remember this whole thing started with Cort writing it for the K0USY group. With all the request from users, in my personal opinion, it was pulling him away from his main goal of development for the K0USY system.  The repo was used as his storage location and it was opened up for others to use.  This became a problem because users would say it didn't work and he was in the middle of working on it.  Cort did make a post about this many times in the past.

With all the other forks out there maybe it is time for other people/groups to pick this project up and start working on it.

Corey  N3FE

 


On 2020-10-14 17:36, area51now via groups.io wrote:

Also no go here, maybe the repository is being worked on.

Bob