Date   

Re: Missing Link

David KE6UPI
 

Thanks Dylan, So all I needed was /opt/Analog_Bridge and /opt/HB_Bridge.

Time to play with this.

David
KE6UPI


Re: Missing Link

Dylan KI7SBI
 

I think you match these lines in Analog_Bridge.ini

; Information for xx_Bridge.py
[AMBE_AUDIO]
server = 127.0.0.1 ; IP address of xx_Bridge.py
fromDMRPort = 31000 ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31003 ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)

to these lines in HB_Bridge.cfg

[DEFAULTS]
gateway = 127.0.0.1 # IP address of Partner Application (IPSC_Bridge, Analog_Bridge)
fromGatewayPort = 31003 # Port HB_Bridge is listening on for data (HB_Bridge <--- Partner)
toGatewayPort = 31000 # Port Partner is listening on for data (HB_Bridge ---> Partner)

And run HB_Bridge.py not hblink.py
The default config seems like it would work, if both HB_Bridge and Analog_Bridge and running on the same host.

KI7SBI Dylan


On Mon, Jan 15, 2018 at 10:38 AM, David KE6UPI <shawpbx@...> wrote:

Hello Everyone, I'm missing something. 

Foreground:
ThumbDV passed AMBEtest3

ASL:
I have ASL running with rpt.conf 1999 USRP working and connected to /opt/Analog_Bridge.
I have node 2083 connected to 1999. I can see that I'm keying 2083 and passing it to 1999 to Analog_Bridge

HBlink:
I have /opt/HBlink configured and connected to BM.

Need help to configure /opt/HB_Bridge to connect to Analog_Bridge and HBlink. What files need to be edited and do I start by using python hblink.py in the /opt/HB_Bridge directory?

Thanks, David
KE6UPI



Missing Link

David KE6UPI
 

Hello Everyone, I'm missing something. 

Foreground:
ThumbDV passed AMBEtest3

ASL:
I have ASL running with rpt.conf 1999 USRP working and connected to /opt/Analog_Bridge.
I have node 2083 connected to 1999. I can see that I'm keying 2083 and passing it to 1999 to Analog_Bridge

HBlink:
I have /opt/HBlink configured and connected to BM.

Need help to configure /opt/HB_Bridge to connect to Analog_Bridge and HBlink. What files need to be edited and do I start by using python hblink.py in the /opt/HB_Bridge directory?

Thanks, David
KE6UPI


Re: Analog_Bridge Help

Ed W8VT
 

Richard,

Says I don't have permission to access file.

Ed


On 01/14/2018 03:36 PM, Richard (Joseph) VE2DJE wrote:

Here is a Block diagramme of our setup. Qui te similarités to what you want to do.
It can help to have a clear view of all the modules. Ports number to use etc 

With Steve to help you are in good hand. 
Richard
Ve2dje

Le 14 janv. 2018 15:29, "Ed W8VT" <vacuumtubesforever@...> a écrit :
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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT






Re: Analog_Bridge Help

 

Go ahead. If it can be of any help....

Richard Ve2dje

Le 14 janv. 2018 17:20, "Steve N4IRS" <szingman@...> a écrit :
Richard,
Looks good. I think if people look at the area of interest, they can pick out the info they need. I would like to post the file on the wiki with your permission.

Steve

On 01/14/2018 03:36 PM, Richard (Joseph) VE2DJE wrote:

Here is a Block diagramme of our setup. Qui te similarités to what you want to do.
It can help to have a clear view of all the modules. Ports number to use etc 

With Steve to help you are in good hand. 
Richard
Ve2dje

Le 14 janv. 2018 15:29, "Ed W8VT" <vacuumtubesforever@...> a écrit :
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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT






Re: Analog_Bridge Help

Steve N4IRS
 

Richard,
Looks good. I think if people look at the area of interest, they can pick out the info they need. I would like to post the file on the wiki with your permission.

Steve

On 01/14/2018 03:36 PM, Richard (Joseph) VE2DJE wrote:

Here is a Block diagramme of our setup. Qui te similarités to what you want to do.
It can help to have a clear view of all the modules. Ports number to use etc 

With Steve to help you are in good hand. 
Richard
Ve2dje

Le 14 janv. 2018 15:29, "Ed W8VT" <vacuumtubesforever@...> a écrit :
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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT






Re: Analog_Bridge Help

Ed W8VT
 

When trying to start hblink, I get:

root@penguin3:/opt/HBlink# python hblink.py
Traceback (most recent call last):
  File "hblink.py", line 502, in <module>
    CONFIG = hb_config.build_config(cli_args.CONFIG_FILE)
  File "/opt/HBlink/hb_config.py", line 98, in build_config
    'PORT': config.getint(section, 'PORT'),
  File "/usr/lib/python2.7/ConfigParser.py", line 359, in getint
    return self._get(section, int, option)
  File "/usr/lib/python2.7/ConfigParser.py", line 356, in _get
    return conv(self.get(section, option))
ValueError: invalid literal for int() with base 10: ''


On 01/14/2018 03:34 PM, Steve N4IRS wrote:
In the hblink.cfg:
Disable MASTER-1
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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT







Re: Analog_Bridge Help

 


Here is a Block diagramme of our setup. Qui te similarités to what you want to do.
It can help to have a clear view of all the modules. Ports number to use etc 

With Steve to help you are in good hand. 
Richard
Ve2dje

Le 14 janv. 2018 15:29, "Ed W8VT" <vacuumtubesforever@...> a écrit :
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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT





Re: Analog_Bridge Help

Steve N4IRS
 

In the hblink.cfg:
Disable MASTER-1
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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT






Re: Analog_Bridge Help

Ed W8VT
 

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 appreciated.

Ed

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT





Re: Analog_Bridge Help

Steve N4IRS
 

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 private node.
Configure Analog_Bridge to communicate with AllStarLink
Since it's a private node, connect the private node to your public node.
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 foreground. 

Steve


On 01/14/2018 02:41 PM, JJ Cummings wrote:
Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT




Re: Analog_Bridge Help

JJ Cummings
 

Have you gotten HBlink working independent of Analog_Bridge?

Sent from the iRoad

On Jan 14, 2018, at 12:31, Ed W8VT <vacuumtubesforever@...> wrote:

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT



Re: Analog_Bridge Help

Ed W8VT
 

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 needed.

Currently have this on a Raspberry Pi 2 with USB AMBE dongle.

Ed



On 01/14/2018 02:24 PM, Steve N4IRS wrote:
Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT



Re: Analog_Bridge Help

Steve N4IRS
 

Ed,
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 W8VT wrote:
At this 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?

Thanks,

Ed W8VT


Analog_Bridge Help

Ed W8VT
 

At this 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?

Thanks,

Ed W8VT


Re: Allstar to DMR ID

Steve N4IRS
 

The DMR IDs for repeaters are 6 digit, we are up to 5 digits. Our node numbers do not fit within the DMR ID system.
There are some possibilities that could be explored. The big issue is that when a user radio displays a DMR ID it is the transmitting station, not the repeater. For ASL that data is not available.
The best we can do is to get the node number of the ASL node originating the transmission.

As it happens, Mike and I started a conversation just today about a method to transmit ASL node data with each transmission. Stay tuned.

73, Steve N4IRS

 


On 01/08/2018 07:07 PM, David KE6UPI wrote:
It would be nice to register a DMR ID for the ASL node. i.e. ASL 2060 Then a DMR user could lookup the node number.

David
KE6UPI



--
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 Wed, Jan 3, 2018 at 7:39 PM, Steve N4IRS <szingman@...> wrote:
David,
I usually my own radio id. My wife is a ham so I have been known to use hers.

Steve




On 01/03/2018 10:25 PM, David wrote:
Hi

What is everyone running for a ID from analog when you do a allstar to dmr bridge.   0 was giving me troubles on my radio.


_._,_._,_




Re: Allstar to DMR ID

David KE6UPI
 

It would be nice to register a DMR ID for the ASL node. i.e. ASL 2060 Then a DMR user could lookup the node number.

David
KE6UPI



--
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 Wed, Jan 3, 2018 at 7:39 PM, Steve N4IRS <szingman@...> wrote:
David,
I usually my own radio id. My wife is a ham so I have been known to use hers.

Steve




On 01/03/2018 10:25 PM, David wrote:
Hi

What is everyone running for a ID from analog when you do a allstar to dmr bridge.   0 was giving me troubles on my radio.



Re: Bridging AllStarLink to other modes.

 

Could not agree more .  I had to do  a couple of conferences to get  some acceptance about the idea of a Bridge between DMR and Analog Allstar ....

Even after that ,  there is still  some  mumbling about the  implementation . My answer is that DMR fans can surely spare 1 TG amongst the thousand there is on the system.

Analog Bridge is only using the CALL HOME  TG (  Repeater DMR ID ) .

I installed  2 systems , one in my region  that is lets say "accepted"  ... Another in  a region that  did not bother to explain the concept ..... All hell broke loose .....

 Ham radio programmers and more technically oriented colaborators are not very  good at selling their approach . More at ease in  getting the job done.

 Get out and speak to club meetings and to on the air gathering .  It's part of selling the amazing work that is being done  by  all of you .....


 Not enough words to express my thanks to all you guys who made it all happen.....


Richard VE2DJE

 
Le 06/01/2018 à 13:09, Peter M0NWI a écrit :

Hi Steve,

Couldn't agree more, in the UK our Ham licence actually says for educational purposes, and it's something us Amateurs have always done, including bending commercial systems to our needs be that a retuned ex Police radio to operate 2m or DMR networks.

In the UK on the hubNet, Peter G7RPG has used DVSwitch to link in DMR from BM into AllStar and it works well, and expands the reach to others, a worthwhile thing.

73,
Peter

Sent from Outlook
From: DVSwitch@groups.io <DVSwitch@groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: 05 January 2018 20:45:34
To: DVSwitch@groups.io
Subject: [DVSwitch] Bridging AllStarLink to other modes.
 
 I was forwarded a post from Doug WA3DSP concerning interconnection to
other services/modes on the HAMVOIP list. I have seen in the past that
Doug considers himself the guardian of all good audio and AllStarLink.
That is open to discussion. I think this needs to be addressed in the
community. Great audio quality is a hallmark of AllStarLink and no one
wants to compromise that. Another feature that singles out AllStarLink
is flexibility. People have done some amazing things with AllStarLink.
There are nodes and hubs that control what type of traffic pass through
the node or hub. There are quite a few nodes and hubs that welcome
experimentation. Connecting a foreign mode or service to a AllStarLink
node is never a good idea without prior discussion.

  One of the many features of AllStarLink that drew me in over 10 years
ago, was the ability to add features and devices. One very important
fact is that it is open source. Well, at least the official AllStarLink
distribution is. Channel drivers are available for EchoLink, D-Star, TLB
and USRP. If it's not there, it can be added. AllStarLink welcomes
people to add to and modify the open source available in github. If you
have an idea, bring it up, submit a pull request and let's see how it fits.

  People are going to extend the capabilities of AllStarLink, that is a
given. Those extensions may not be to everyone's liking. Under the
banner of DVSwitch, a few of us have been building tools for bridging
between different voice networks. One of those is AllStarLink. It does
not matter if the purpose of the bridge is to expose analog users to the
capabilities of a digital network or to display the capabilities of
AllStarLink to a group of digital voice users that are not aware of a
large network of open source analog nodes. There are quite a few hams
that do not know about AllStarLink. This gives them a taste. I'm pretty
sure every one of the digital voice radios in use support analog. Do we
really want to display a negative attitude to other communities? I can
tell you that not everyone on the digital voice networks want to see a
bridge to analog. They don't want "those noisy analog signals" on their
network. This is not a discussion of which voice mode is better. Nor is
it about how to make digital voice sound better. I tell people building
bridges the same thing, Don't just drop a analog bridge onto a digital
channel without discussion first. One digital network I have seen is
reporting over 10K calls per hour. (That might be a interesting stat to
collect for AllStarLink)

  Bridging networks is not the purpose of AllStarLink and I would rather
not see discussions of various networks on the AllStarLink user list.
There are other places for that. The open source nature of AllStarLink
lends itself to extension. Just be aware what you are doing and who it
will effect.

73, Steve N4IRS




Virus-free. www.avg.com


Re: Bridging AllStarLink to other modes.

Peter M0NWI
 

Hi Steve,

Couldn't agree more, in the UK our Ham licence actually says for educational purposes, and it's something us Amateurs have always done, including bending commercial systems to our needs be that a retuned ex Police radio to operate 2m or DMR networks.

In the UK on the hubNet, Peter G7RPG has used DVSwitch to link in DMR from BM into AllStar and it works well, and expands the reach to others, a worthwhile thing.

73,
Peter

Sent from Outlook
From: DVSwitch@groups.io <DVSwitch@groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: 05 January 2018 20:45:34
To: DVSwitch@groups.io
Subject: [DVSwitch] Bridging AllStarLink to other modes.
 
 I was forwarded a post from Doug WA3DSP concerning interconnection to
other services/modes on the HAMVOIP list. I have seen in the past that
Doug considers himself the guardian of all good audio and AllStarLink.
That is open to discussion. I think this needs to be addressed in the
community. Great audio quality is a hallmark of AllStarLink and no one
wants to compromise that. Another feature that singles out AllStarLink
is flexibility. People have done some amazing things with AllStarLink.
There are nodes and hubs that control what type of traffic pass through
the node or hub. There are quite a few nodes and hubs that welcome
experimentation. Connecting a foreign mode or service to a AllStarLink
node is never a good idea without prior discussion.

  One of the many features of AllStarLink that drew me in over 10 years
ago, was the ability to add features and devices. One very important
fact is that it is open source. Well, at least the official AllStarLink
distribution is. Channel drivers are available for EchoLink, D-Star, TLB
and USRP. If it's not there, it can be added. AllStarLink welcomes
people to add to and modify the open source available in github. If you
have an idea, bring it up, submit a pull request and let's see how it fits.

  People are going to extend the capabilities of AllStarLink, that is a
given. Those extensions may not be to everyone's liking. Under the
banner of DVSwitch, a few of us have been building tools for bridging
between different voice networks. One of those is AllStarLink. It does
not matter if the purpose of the bridge is to expose analog users to the
capabilities of a digital network or to display the capabilities of
AllStarLink to a group of digital voice users that are not aware of a
large network of open source analog nodes. There are quite a few hams
that do not know about AllStarLink. This gives them a taste. I'm pretty
sure every one of the digital voice radios in use support analog. Do we
really want to display a negative attitude to other communities? I can
tell you that not everyone on the digital voice networks want to see a
bridge to analog. They don't want "those noisy analog signals" on their
network. This is not a discussion of which voice mode is better. Nor is
it about how to make digital voice sound better. I tell people building
bridges the same thing, Don't just drop a analog bridge onto a digital
channel without discussion first. One digital network I have seen is
reporting over 10K calls per hour. (That might be a interesting stat to
collect for AllStarLink)

  Bridging networks is not the purpose of AllStarLink and I would rather
not see discussions of various networks on the AllStarLink user list.
There are other places for that. The open source nature of AllStarLink
lends itself to extension. Just be aware what you are doing and who it
will effect.

73, Steve N4IRS




Re: Allstar USRP host

Steve N4IRS
 

Mike,
What error do you get?
What is in the log?
Do you have the USRP node in the node stanza?

Steve

On 01/05/2018 09:46 PM, Mike Swiatkowski via Groups.Io wrote:
I'm having problems connecting my allstar USRP nodes (i.e node number that interfaces to analog_bridge) to other USRP nodes.  I have no problem connecting the USRP to a URIx hardware node.  But, I cannot do it the other way around, like hardware URIx to USRP.  So, does anyone have any idea why I am having this problem of not being able to connect my USRP nodes to anything but a physical hardware node (like a URIx interface) and how I can fix it?

Mike, AA9VI

8881 - 8900 of 9595