Date   

Re: AMBED

Steve N4IRS
 

Ken,
You are in uncharted waters. We have no experience with the 6 channel device. If AMBED emulates AMBEServer that might work. 

On 07/23/2018 09:52 PM, Ken KE2N via Groups.Io wrote:
can someone help  me with instructions to use the NW Digital 6-channel device with Analog Bridge?  I have AMBED on the same machine as my DVSwitch install and have used it with XLXD so I know that it works.  Will analog bridge talk to the 6-channel USB device directly, or do I run AMBED and set some port numbers accordingly?   If the 6 channel device is out of the question, I do have a pair of ThumbDV's that could be pressed into service.

Thanks
Ken


Re: DMR to DSTAR

Steve N4IRS
 

Those commands are not valid with Analog_Bridge.

On 07/23/2018 10:07 PM, Mike, AA9VI via Groups.Io wrote:
Steve,
Can you issue the following commands and post the output?
uhd_usrp_probe
uhd_find_devices
I am getting "No UHD Devices Found" and that may be the problem with all of this...

Here is my reference: https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio


Re: DMR to DSTAR

Mike, AA9VI
 

Steve,
Can you issue the following commands and post the output?
uhd_usrp_probe
uhd_find_devices
I am getting "No UHD Devices Found" and that may be the problem with all of this...

Here is my reference: https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio


AMBED

Ken KE2N
 

can someone help  me with instructions to use the NW Digital 6-channel device with Analog Bridge?  I have AMBED on the same machine as my DVSwitch install and have used it with XLXD so I know that it works.  Will analog bridge talk to the 6-channel USB device directly, or do I run AMBED and set some port numbers accordingly?   If the 6 channel device is out of the question, I do have a pair of ThumbDV's that could be pressed into service.

Thanks
Ken


Re: Allstarlink dvswitch raspberry pi 3 b+

Mike KB8JNM
 

The instructions are the same as a pc.

https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit


But if this was a fresh pi image, you need to do this first...

http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme

If you did not, you might want to start with a fresh image.

...mike/kb8jnm


On 07/22/2018 04:54 AM, m0tfg@... wrote:
Hi i get stuck because some of the commands are not working. maybe someone can help me to figure out how to make it work. i am trying to install asl dmr bridge on raspberry pi 3 B+
and i not that expert, im just trying to follow those step by step instructions. many thanks in advance... 73



Re: Allstarlink dvswitch raspberry pi 3 b+

Ken KE2N
 

looks like you are starting with the hamvoip version of all star.
this is the wrong starting point.
you need to start with ASL http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/


Allstarlink dvswitch raspberry pi 3 b+

Dennis Ramos
 

Hi i get stuck because some of the commands are not working. maybe someone can help me to figure out how to make it work. i am trying to install asl dmr bridge on raspberry pi 3 B+
and i not that expert, im just trying to follow those step by step instructions. many thanks in advance... 73


Re: dvswich.ini

Paul Nannery KC2VRJ
 

thank you that worked. I'm not sure why it did not work directly in the main script but your method works thank you for the help.

On Sat, Jul 21, 2018 at 5:32 PM, Steve N4IRS <szingman@...> wrote:
create a small script, call it bridge.sh

cd /opt/MMDVM_Bridge
/opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

Then run:
screen -d -m -S MMDVM /path/to/bridge.sh


On 07/21/2018 05:26 PM, Paul Nannery KC2VRJ wrote:
here is what I'm trying to do maybe im reinventing the wheel a little bit but I was looking for one script to start everything I'm looking for in one script and named screens.

#!/bin/bash
############################
#Kill any running reflector#
############################
killall YSFReflector
killall NXDNReflector
killall P25Reflector
killall Analog_Bridge
killall MMDVM_Bridge

##################
#Start Reflectors#
##################
screen -d -m -S YSFReflector /opt/YSFReflector/YSFReflector /opt/YSFReflector/YSFReflector.ini
screen -d -m -S NXDNReflector /opt/NXDNReflector/NXDNReflector /opt/NXDNReflector/NXDNReflector.ini
screen -d -m -S P25Reflector /opt/P25Reflector/P25Reflector /opt/P25Reflector/P25Reflector.ini
##############
#Bridge Start#
##############
screen -d -m -S Bridge /opt/Analog_Bridge/Analog_Bridge   /opt/Analog_Bridge/Analog_Bridge.ini

cd /opt/MMDVM_Bridge/
screen -d -m -S MMDVM /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

#end

however it still looks for the DVswich.ini 


On Sat, Jul 21, 2018 at 5:14 PM, Steve N4IRS <szingman@...> wrote:
In you script change directory to where MMDVM_Bridge and DVSwitch.ini are or use the existing systemd unit /lib/systemd/system/mmdvm_bridge.system
systemctl start mmdvm_bridge
systemctl status mmdvm_bridge
systemctl stop mmdvm_bridge

Steve n4IRS

On 07/21/2018 05:05 PM, Paul Nannery KC2VRJ wrote:
Ok guys I am making a script to start my bridge however MMDVM_Bridge sails as it can not find Dvswich.ini how can I get around this . 





Re: dvswich.ini

Steve N4IRS
 

create a small script, call it bridge.sh

cd /opt/MMDVM_Bridge
/opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

Then run:
screen -d -m -S MMDVM /path/to/bridge.sh


On 07/21/2018 05:26 PM, Paul Nannery KC2VRJ wrote:
here is what I'm trying to do maybe im reinventing the wheel a little bit but I was looking for one script to start everything I'm looking for in one script and named screens.

#!/bin/bash
############################
#Kill any running reflector#
############################
killall YSFReflector
killall NXDNReflector
killall P25Reflector
killall Analog_Bridge
killall MMDVM_Bridge

##################
#Start Reflectors#
##################
screen -d -m -S YSFReflector /opt/YSFReflector/YSFReflector /opt/YSFReflector/YSFReflector.ini
screen -d -m -S NXDNReflector /opt/NXDNReflector/NXDNReflector /opt/NXDNReflector/NXDNReflector.ini
screen -d -m -S P25Reflector /opt/P25Reflector/P25Reflector /opt/P25Reflector/P25Reflector.ini
##############
#Bridge Start#
##############
screen -d -m -S Bridge /opt/Analog_Bridge/Analog_Bridge   /opt/Analog_Bridge/Analog_Bridge.ini

cd /opt/MMDVM_Bridge/
screen -d -m -S MMDVM /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

#end

however it still looks for the DVswich.ini 


On Sat, Jul 21, 2018 at 5:14 PM, Steve N4IRS <szingman@...> wrote:
In you script change directory to where MMDVM_Bridge and DVSwitch.ini are or use the existing systemd unit /lib/systemd/system/mmdvm_bridge.system
systemctl start mmdvm_bridge
systemctl status mmdvm_bridge
systemctl stop mmdvm_bridge

Steve n4IRS

On 07/21/2018 05:05 PM, Paul Nannery KC2VRJ wrote:
Ok guys I am making a script to start my bridge however MMDVM_Bridge sails as it can not find Dvswich.ini how can I get around this . 




Re: dvswich.ini

Paul Nannery KC2VRJ
 

here is what I'm trying to do maybe im reinventing the wheel a little bit but I was looking for one script to start everything I'm looking for in one script and named screens.

#!/bin/bash
############################
#Kill any running reflector#
############################
killall YSFReflector
killall NXDNReflector
killall P25Reflector
killall Analog_Bridge
killall MMDVM_Bridge

##################
#Start Reflectors#
##################
screen -d -m -S YSFReflector /opt/YSFReflector/YSFReflector /opt/YSFReflector/YSFReflector.ini
screen -d -m -S NXDNReflector /opt/NXDNReflector/NXDNReflector /opt/NXDNReflector/NXDNReflector.ini
screen -d -m -S P25Reflector /opt/P25Reflector/P25Reflector /opt/P25Reflector/P25Reflector.ini
##############
#Bridge Start#
##############
screen -d -m -S Bridge /opt/Analog_Bridge/Analog_Bridge   /opt/Analog_Bridge/Analog_Bridge.ini

cd /opt/MMDVM_Bridge/
screen -d -m -S MMDVM /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

#end

however it still looks for the DVswich.ini 


On Sat, Jul 21, 2018 at 5:14 PM, Steve N4IRS <szingman@...> wrote:
In you script change directory to where MMDVM_Bridge and DVSwitch.ini are or use the existing systemd unit /lib/systemd/system/mmdvm_bridge.system
systemctl start mmdvm_bridge
systemctl status mmdvm_bridge
systemctl stop mmdvm_bridge

Steve n4IRS

On 07/21/2018 05:05 PM, Paul Nannery KC2VRJ wrote:
Ok guys I am making a script to start my bridge however MMDVM_Bridge sails as it can not find Dvswich.ini how can I get around this . 



Re: dvswich.ini

Steve N4IRS
 

In you script change directory to where MMDVM_Bridge and DVSwitch.ini are or use the existing systemd unit /lib/systemd/system/mmdvm_bridge.system
systemctl start mmdvm_bridge
systemctl status mmdvm_bridge
systemctl stop mmdvm_bridge

Steve n4IRS

On 07/21/2018 05:05 PM, Paul Nannery KC2VRJ wrote:
Ok guys I am making a script to start my bridge however MMDVM_Bridge sails as it can not find Dvswich.ini how can I get around this . 


dvswich.ini

Paul Nannery KC2VRJ
 

Ok guys I am making a script to start my bridge however MMDVM_Bridge sails as it can not find Dvswich.ini how can I get around this . 


Re: hblink BM talkgroups

Jim - K6JWN
 

Excellent, thank you very much for the help!


FYI, got HBmonitor running as well today.  Thanks for creating that, nice to see whats going on behind the scenes!


Jim, K6JWN


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: Friday, July 20, 2018 12:56:10 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] hblink BM talkgroups
 
hb_confbridge.py is your huckleberry for that goal.

multiple connections is the way to do it. 

On Jul 20, 2018, at 2:52 PM, Jim K6JWN <nessenj@...> wrote:

Hi Cort,

I am using hb_confbridge.py presently.

My end goal is to have a place to connect several bridges and repeaters that are not tied into BrandMeister, but still have the ability to bring a few BM TGs in and have the ability to route TGs between repeaters/hotspots. etc.  I guess its sort of like doing a cBridge for non motorola repeaters.  I hope that sheds some light on what I am trying to do.

My thinking was to create individual connections to BM and bring a single static TG across each connection, but I wasn't sure if that was frowned upon by BM (or it was the wrong way to do things).

Jim, K6JWN


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: Friday, July 20, 2018 10:39:16 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] hblink BM talkgroups
 
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206


Cort Buffington
785-865-7206


Re: hblink BM talkgroups

Cort N0MJS <n0mjs@...>
 

either/or

On Jul 20, 2018, at 2:53 PM, Jim K6JWN <nessenj@...> wrote:

I was thinking about spreading connections between masters, but wasn't sure if that was good practice.  Sounds like it's OK 😊


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, July 20, 2018 10:42:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] hblink BM talkgroups
 
To piggyback on Cort, one thing to consider is that Masters can go down. It does not happen too often, but it does happen. I can make a case for not putting all your eggs in one basket.

Steve, N4IRS

On 7/20/2018 1:39 PM, Cort N0MJS via Groups.Io wrote:
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206



Cort Buffington
785-865-7206


Re: hblink BM talkgroups

Cort N0MJS <n0mjs@...>
 

hb_confbridge.py is your huckleberry for that goal.

multiple connections is the way to do it. 

On Jul 20, 2018, at 2:52 PM, Jim K6JWN <nessenj@...> wrote:

Hi Cort,

I am using hb_confbridge.py presently.

My end goal is to have a place to connect several bridges and repeaters that are not tied into BrandMeister, but still have the ability to bring a few BM TGs in and have the ability to route TGs between repeaters/hotspots. etc.  I guess its sort of like doing a cBridge for non motorola repeaters.  I hope that sheds some light on what I am trying to do.

My thinking was to create individual connections to BM and bring a single static TG across each connection, but I wasn't sure if that was frowned upon by BM (or it was the wrong way to do things).

Jim, K6JWN


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: Friday, July 20, 2018 10:39:16 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] hblink BM talkgroups
 
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206


Cort Buffington
785-865-7206


Re: hblink BM talkgroups

Jim - K6JWN
 

I was thinking about spreading connections between masters, but wasn't sure if that was good practice.  Sounds like it's OK 😊



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Friday, July 20, 2018 10:42:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] hblink BM talkgroups
 
To piggyback on Cort, one thing to consider is that Masters can go down. It does not happen too often, but it does happen. I can make a case for not putting all your eggs in one basket.

Steve, N4IRS

On 7/20/2018 1:39 PM, Cort N0MJS via Groups.Io wrote:
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206



Re: hblink BM talkgroups

Jim - K6JWN
 

Hi Cort,


I am using hb_confbridge.py presently.


My end goal is to have a place to connect several bridges and repeaters that are not tied into BrandMeister, but still have the ability to bring a few BM TGs in and have the ability to route TGs between repeaters/hotspots. etc.  I guess its sort of like doing a cBridge for non motorola repeaters.  I hope that sheds some light on what I am trying to do.


My thinking was to create individual connections to BM and bring a single static TG across each connection, but I wasn't sure if that was frowned upon by BM (or it was the wrong way to do things).


Jim, K6JWN


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: Friday, July 20, 2018 10:39:16 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] hblink BM talkgroups
 
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206


Re: hblink BM talkgroups

Cort N0MJS <n0mjs@...>
 

Yep — there are reasons… just wanted to make sure you knew it’s not a “requirement"

On Jul 20, 2018, at 12:42 PM, Steve N4IRS <szingman@...> wrote:

To piggyback on Cort, one thing to consider is that Masters can go down. It does not happen too often, but it does happen. I can make a case for not putting all your eggs in one basket.

Steve, N4IRS

On 7/20/2018 1:39 PM, Cort N0MJS via Groups.Io wrote:
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206



Cort Buffington
785-865-7206


Re: hblink BM talkgroups

Steve N4IRS
 

To piggyback on Cort, one thing to consider is that Masters can go down. It does not happen too often, but it does happen. I can make a case for not putting all your eggs in one basket.

Steve, N4IRS

On 7/20/2018 1:39 PM, Cort N0MJS via Groups.Io wrote:
Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206



Re: hblink BM talkgroups

Cort N0MJS <n0mjs@...>
 

Jim,

You don’t have to connect to multiple different masters to do that (if you don’t want to). You should be able to use a different set of “credentials” and make a 2nd connection to the same one if you want.

As far as what is “best”, it kinda depends on what your goals are — and since you just said “hblink” but didn’t say whether you were using hb_confbridge.py or hb_bridge_all.py… It’s harder to try and surmise what you’re looking to do.

If you’re just looking to make this a “proxy” connection (with local fail-over), then I’d say do it with hb_bridge_all.py and  one BM connection.

But if you’re wanting to potentially connect different downstreams (hotspots & repeaters) to different upstream (BM) TGIDs at the same time, then you’ll find that you need multiple connections to BM with not more than a single static TGID per TS.

Does that help any?

0x49 DE N0MJS

On Jul 20, 2018, at 11:19 AM, Jim K6JWN <nessenj@...> wrote:

Greetings,

I successfully setup hblink yesterday and connected 3 hotspots to it (eventually I will connect a MMDVM repeater into the mix).  Along with the hotspots, I created a client connection to BM 3108 and piped in a static tg (3100 for now to test).  I am interested in bringing 3 static talkgroups in, would it be best to bring them in over the existing client connection, or would it be easier to setup multiple client connections to multiple BM masters and have each one be responsible for a static TG?

Hope my question makes sense, if not let me know.

Jim, K6JWN

Cort Buffington
785-865-7206

7901 - 7920 of 9820