Date   

Re: Analog_Bridge Allstar Link Guidance

Steve N4IRS
 

OK,
Let us know the result of the long term test and the console output from Analog_Bridge.

On 12/28/2017 10:54 PM, Corey Badgley KC7MRQ wrote:
I am running the serial connection.


Re: Analog_Bridge Allstar Link Guidance

Corey Badgley KC7MRQ
 

I am running the serial connection.


Re: Analog_Bridge Allstar Link Guidance

Steve N4IRS
 

Corey,
Are you running ambeserver or serial connection to the ThumbDV?

Steve

On 12/28/2017 08:08 PM, Corey Badgley KC7MRQ wrote:
I've noticed a couple issues playing with the setup. The first was the thumbDV resetting after about 5 minutes of audio. I raised the input voltage and the reset problem appeared to go away. 

The second issue is audio artifacts from DMR > ASL. The audio is broken like there are packet drops and a pretty large delay from the time the DMR station un keys till the audio is complete on the ASL side. for example, a 50+ second DMR transmission will have least a 10 second delay. 

Any suggestions about the broken and delayed audio coming onto the ASL side?

Corey


Re: Analog_Bridge Allstar Link Guidance

Steve N4IRS
 

Also, run AMBETest4.py with the -e option. It will stop on error.

On 12/28/2017 08:08 PM, Corey Badgley KC7MRQ wrote:
I've noticed a couple issues playing with the setup. The first was the thumbDV resetting after about 5 minutes of audio. I raised the input voltage and the reset problem appeared to go away. 

The second issue is audio artifacts from DMR > ASL. The audio is broken like there are packet drops and a pretty large delay from the time the DMR station un keys till the audio is complete on the ASL side. for example, a 50+ second DMR transmission will have least a 10 second delay. 

Any suggestions about the broken and delayed audio coming onto the ASL side?

Corey


Re: Analog_Bridge Allstar Link Guidance

JJ Cummings
 

I have also seen clipping like behavior when the gain values were not correctly adjusted.

Sent from the iRoad

On Dec 28, 2017, at 18:31, Steve N4IRS <szingman@...> wrote:

Corey,
I'm betting you are still having issues with the ThumbDV on a RPi. I can suggest a few things.
Try a powered USB hub.
Try running on a X86 machine
Run Analog_Bridge in the foreground so you can watch the output. Analog_Bridge will report errors from the ThumbDV. I'm betting reset errors.
Run a LONG term test with AMBEtest4.py Run it verbose and take a look at line 198 to increase the number of iterations.

73, Steve N4IRS

On 12/28/2017 08:08 PM, Corey Badgley KC7MRQ wrote:
I've noticed a couple issues playing with the setup. The first was the thumbDV resetting after about 5 minutes of audio. I raised the input voltage and the reset problem appeared to go away. 

The second issue is audio artifacts from DMR > ASL. The audio is broken like there are packet drops and a pretty large delay from the time the DMR station un keys till the audio is complete on the ASL side. for example, a 50+ second DMR transmission will have least a 10 second delay. 

Any suggestions about the broken and delayed audio coming onto the ASL side?

Corey


Re: Analog_Bridge Allstar Link Guidance

Steve N4IRS
 

Corey,
I'm betting you are still having issues with the ThumbDV on a RPi. I can suggest a few things.
Try a powered USB hub.
Try running on a X86 machine
Run Analog_Bridge in the foreground so you can watch the output. Analog_Bridge will report errors from the ThumbDV. I'm betting reset errors.
Run a LONG term test with AMBEtest4.py Run it verbose and take a look at line 198 to increase the number of iterations.

73, Steve N4IRS

On 12/28/2017 08:08 PM, Corey Badgley KC7MRQ wrote:
I've noticed a couple issues playing with the setup. The first was the thumbDV resetting after about 5 minutes of audio. I raised the input voltage and the reset problem appeared to go away. 

The second issue is audio artifacts from DMR > ASL. The audio is broken like there are packet drops and a pretty large delay from the time the DMR station un keys till the audio is complete on the ASL side. for example, a 50+ second DMR transmission will have least a 10 second delay. 

Any suggestions about the broken and delayed audio coming onto the ASL side?

Corey


Re: Analog_Bridge Allstar Link Guidance

Corey Badgley KC7MRQ
 

I've noticed a couple issues playing with the setup. The first was the thumbDV resetting after about 5 minutes of audio. I raised the input voltage and the reset problem appeared to go away. 

The second issue is audio artifacts from DMR > ASL. The audio is broken like there are packet drops and a pretty large delay from the time the DMR station un keys till the audio is complete on the ASL side. for example, a 50+ second DMR transmission will have least a 10 second delay. 

Any suggestions about the broken and delayed audio coming onto the ASL side?

Corey


Re: Analog_Bridge Allstar Link Guidance

Corey Badgley KC7MRQ
 

I am up and running thanks to Gescio, WH6AV, remoting into my system and making the necessary changes to enable the bridge. 

Thanks again Gescio for taking time out of your day to help me and give me some training on the use. 

Have a great day,

Corey


Re: Analog_Bridge Allstar Link Guidance

JJ Cummings
 

Corey,

I’ll provide an example of how I’m doing it for 310815 <-> the fun machine (k0jsc.com) in Colorado when I get home this evening.

J Cummings
N0PKT

Sent from the iRoad

On Dec 28, 2017, at 11:12, Corey Badgley KC7MRQ <kc7mrq@...> wrote:

Steve,
I'm doing the same thing as Ed, but just don't understand what I am doing and need some hand-holding guidance.
So far I have updated rpt.conf file and have a node number using the USRP channel and its loaded in the manager.conf file.

I have the thumbDV connected to the pi and Initial testing AMBETest4 failed until I changed to a higher current power supply. Then, the test succeeded.

I followed the instructions per the DMRGateway notes and installed the files in the /opt folder and edited the Ini file.
All the testing was successful per the instructions.

I git cloned your response above into the /opt folder and followed those instructions.

I edited the hblink.cfg by enabling the client stanza and changed the lines that seemed applicable. 

So how do I "turn it all on" to bridge ASL 29847 to TG31304?

Thanks,
Corey 
KC7MRQ





Re: Analog_Bridge Allstar Link Guidance

Corey Badgley KC7MRQ
 

Steve,
I'm doing the same thing as Ed, but just don't understand what I am doing and need some hand-holding guidance.
So far I have updated rpt.conf file and have a node number using the USRP channel and its loaded in the manager.conf file.

I have the thumbDV connected to the pi and Initial testing AMBETest4 failed until I changed to a higher current power supply. Then, the test succeeded.

I followed the instructions per the DMRGateway notes and installed the files in the /opt folder and edited the Ini file.
All the testing was successful per the instructions.

I git cloned your response above into the /opt folder and followed those instructions.

I edited the hblink.cfg by enabling the client stanza and changed the lines that seemed applicable. 

So how do I "turn it all on" to bridge ASL 29847 to TG31304?

Thanks,
Corey 
KC7MRQ





Re: Analog_Bridge Allstar Link Guidance

Steve N4IRS
 

clone dmr_utils from this:
https://github.com/n0mjs710/dmr_utils.git
run the install.sh in dmr_utils

clone HB_Bridge from this:
git clone -b HB_Bridge https://github.com/n0mjs710/HBlink.git

copy hblink-SAMPLE.cfg to hblink.cfg
edit hblink.cfg

See this:
https://groups.io/g/DVSwitch/files/HB_AB_ASL.txt
and this:
https://groups.io/g/DVSwitch/files/HB_Bridge_Diagram.pdf

73, Steve N4IRS


On 12/26/2017 02:27 PM, Ed W8VT wrote:
At this point have a fresh install of DIAL on a RPi2. Have Analog_Bridge running and communicating with the DV3000 per the DMRGateway install notes.

I guess next step is HBLink. Could use some assistance at this point.

The goal is to have private Allstar node bridge to BM TG 313938, which is a cluster of repeaters in SE OH operated by my buddies.

Any assistance greatly appreciated. Thanks.


Analog_Bridge Allstar Link Guidance

Ed W8VT
 

At this point have a fresh install of DIAL on a RPi2. Have Analog_Bridge running and communicating with the DV3000 per the DMRGateway install notes.

I guess next step is HBLink. Could use some assistance at this point.

The goal is to have private Allstar node bridge to BM TG 313938, which is a cluster of repeaters in SE OH operated by my buddies.

Any assistance greatly appreciated. Thanks.


Re: HBLink: Adhoc clients with routing rules, conferences etc

Nicola IT9FXF <onetechct@...>
 

When active confbride take configuration ip from hblink.cfg and all traffic pass trought confbridge ?
For parrot need to start also the service ? Or if start parrot, confbridge and hblink are active togheter ?
Tomorrow I will test better. I need a very simple configuration, just for a working parrot. I have 3 xmmdvm  repeaters clients in the master but want open just 9990 por the parrot.
Thank you !
merry christmas


Re: Where To Start

stevecast2024@...
 

Alright. I'm waiting on an MMDVM to come in to interface to the other repeater. Once I have it I'll let you know of audio is truly passing. Thank you.


Re: Where To Start

Mike Zingman - N4IRR
 

If audio is passing I would like you to try editing the IPSC_Bridge.py file, line 148.  It needs to be an 8 bit value (like HB)
so change it from
_seq = int_id(_data[20:22])
 

to
_seq = int_id(_data[20:22]) & 0xff
 


But only do this if audio is passing and this is a logging error.


Re: Where To Start

Steve N4IRS
 

Even though the log is showing high loss rate, how is the audio passing?

Steve


Re: HBLink: Adhoc clients with routing rules, conferences etc

Steve N4IRS
 

The system in hb_confbridge_rules must match the stanza name in hblink.cfg in the example:
'WORLDWIDE': [
            {'SYSTEM': 'LSMFT-1',    'TS': 1, 'TGID': 1,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON',  'ON': [2,], 'OFF': [9,10]},
            {'SYSTEM': 'ABCDE-1',    'TS': 1, 'TGID': 3100, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON',  'ON': [2,], 'OFF': [9,10]},
        ],
You must have a stanza LSMFT-1 and a stanza ABCDE-1

Steve


On 12/24/2017 07:57 AM, Nicola IT9FXF via Groups.Io wrote:
Hello Steve, thanks!
Must I put same name on hblink.cfg for the hblink side?
I used this cfg :

PARROT
[MASTER-1] 
MODE: MASTER ENABLED: True 
REPEAT: True EXPORT_AMBE: False 
IP: 127.0.0.1 PORT: 54001 P
ASSPHRASE: passw0rd 
GROUP_HANGTIME: 5
 
hblink receive from repeaters
 
[MASTER-1]
MODE: MASTER
ENABLED: True
REPEAT: True
EXPORT_AMBE: False
IP:
PORT: 62031
PASSPHRASE: passw0rd
GROUP_HANGTIME: 5
 
hb_confbridge
 
[PARROT]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP: 127.0.0.1
PORT: 54011
MASTER_IP: 127.0.0.1
MASTER_PORT: 54001
PASSPHRASE: passw0rd
CALLSIGN: XXXXX
RADIO_ID: 312001
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 8
SLOTS: 2
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75
LOCATION: Anywhere, USA
DESCRIPTION: This is a cool repeater
SOFTWARE_ID: HBlink
PACKAGE_ID: v0.1
GROUP_HANGTIME: 5
OPTIONS:
 
[MASTER]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP: 127.0.0.1
PORT: 54010
MASTER_IP: 127.0.0.1
MASTER_PORT: 54000
PASSPHRASE: passw0rd
CALLSIGN: XXXXX
RADIO_ID: 312002
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75
LOCATION: Anywhere, USA
DESCRIPTION: This is a cool repeater
SOFTWARE_ID: HBlink
PACKAGE_ID: v0.1
GROUP_HANGTIME: 5
OPTIONS:
 


Re: Merry Christmas and a happy new year!

Nicola IT9FXF <onetechct@...>
 

Buon Natale a tutti !


Re: HBLink: Adhoc clients with routing rules, conferences etc

Nicola IT9FXF <onetechct@...>
 

Hello Steve, thanks!
Must I put same name on hblink.cfg for the hblink side?
I used this cfg :

PARROT
[MASTER-1] 
MODE: MASTER ENABLED: True 
REPEAT: True EXPORT_AMBE: False 
IP: 127.0.0.1 PORT: 54001 P
ASSPHRASE: passw0rd 
GROUP_HANGTIME: 5
 
hblink receive from repeaters
 
[MASTER-1]
MODE: MASTER
ENABLED: True
REPEAT: True
EXPORT_AMBE: False
IP:
PORT: 62031
PASSPHRASE: passw0rd
GROUP_HANGTIME: 5
 
hb_confbridge
 
[PARROT]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP: 127.0.0.1
PORT: 54011
MASTER_IP: 127.0.0.1
MASTER_PORT: 54001
PASSPHRASE: passw0rd
CALLSIGN: XXXXX
RADIO_ID: 312001
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 8
SLOTS: 2
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75
LOCATION: Anywhere, USA
DESCRIPTION: This is a cool repeater
URL: www.w1abc.org
SOFTWARE_ID: HBlink
PACKAGE_ID: v0.1
GROUP_HANGTIME: 5
OPTIONS:
 
[MASTER]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP: 127.0.0.1
PORT: 54010
MASTER_IP: 127.0.0.1
MASTER_PORT: 54000
PASSPHRASE: passw0rd
CALLSIGN: XXXXX
RADIO_ID: 312002
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75
LOCATION: Anywhere, USA
DESCRIPTION: This is a cool repeater
URL: www.w1abc.org
SOFTWARE_ID: HBlink
PACKAGE_ID: v0.1
GROUP_HANGTIME: 5
OPTIONS:
 


Re: HBLink: Adhoc clients with routing rules, conferences etc

Steve N4IRS
 

I have posted a example from my running ConfBridge https://groups.io/g/DVSwitch/files/N4IRS_confbridge_rules.py

8861 - 8880 of 9532