Date   

Re: Analog_Bridge for the Raspberry Pi

Matthew 2E0SIP
 

Does this include ThumbDV dongles?

If it's solely power related, maybe using a powered USB hub will help?

Thanks


Analog_Bridge for the Raspberry Pi

Steve N4IRS
 

Due to ongoing issues with the DV3000 and the Raspberry Pi, I have removed Analog_Bridge for the Pi from the repository. 


Re: Preparing to Build

Steve N4IRS
 

They are close enough. At some point I will edit.We are testing the DV3000u on a Pi with mixed results. Mike is building a validation program. As of right now, the DV3000u is not supported on the Pi.

Steve

On 6/22/2017 8:02 AM, Steve Siesel [K4KSA] wrote:
Steve and all,

I will begin to build this weekend my ASL to DMR gateway and want to know if
the DV3000 install instructions in the file "Draft DMRGateway Install notes"
found in the
DVSwitch files area is still valid?

Thanks,

Steve
K4KSA






Preparing to Build

Steve Siesel [K4KSA]
 

Steve and all,

I will begin to build this weekend my ASL to DMR gateway and want to know if
the DV3000 install instructions in the file "Draft DMRGateway Install notes"
found in the
DVSwitch files area is still valid?

Thanks,

Steve
K4KSA


Re: Analog_Bridge overview

G7RPG - Peter Kendall
 

X86 Atom N570, Linux Mint 18.1


On 21/06/2017 22:07, Steve N4IRS wrote:
Peter,
What hardware are you running the DV3000u on?


Re: Analog_Bridge overview

Steve N4IRS
 

Peter,
What hardware are you running the DV3000u on?


Re: Testing HBlink

Mike Zingman - N4IRR
 

What hardware/computer are you running the Analog_Bridge on?  Is the DV3000 connected locally or is it on an AMBE server?
We have seen that the DV3000 is very sensitive to power from the USB port and looking to see if yours is producing proper voltage levels.


Re: Testing HBlink

Steve N4IRS
 

Richard,
Please show us the output of Analog_Audio at startup.

Steve


Testing HBlink

 

Here are my observations:

 

Running  setup

 

        à34001                                à31003                                             62031

AST ß       à  Analog_Bridge ß        à HB_Bridge ß   àhblink>ß      à MMDVM

        ß32001                                ß31000

 

 

Allstar  node connected  to  IaxRpt console

 

All  IaxRpt consoles messages are OK .

 

PTT from  DMR radio shows  the following  on HB-Bridge console ( Seems OK)

 

                INFO 2017-06-21 13:53:27,368 Voice Transmission Start on TS 1 and TG BrandMeister (9) from VE2DJE

 

PTT from  DMR radio shows OK on Analog_Bridge console

 

                I: 2017-06-21 17:55:43.642 Begin TX: src=3022368 rpt=302236 dst=9 slot=1 cc=1

                Begin TX: src=3022368 rpt=302236 dst=9 slot=1 cc=1

 

Audio received on IAxrpt console is  white noise only….

 

TX from  IAXrpt Allstar console  shows OK on Analog_Bridge console

 

                M: 2017-06-21 17:58:53.474 PTT on

                M: 2017-06-21 17:58:56.542 PTT off (keyed for 3068 ms)

 

TX from  IAXrpt Allstar console  shows OK on  HB-Bridge console

 

                INFO 2017-06-21 13:59:49,675 (MASTER-1) Begin AMBE encode STREAM ID: 387864                                                                                                  7194 SUB: 3022387 (3022387) REPEATER: 302238 (302238) TGID BrandMeister (9)                                                                                                  , TS 1

                DEBUG 2017-06-21 13:59:49,801 (MASTER-1) import_datagramReceived

                /

                /

                /

                /

                DEBUG 2017-06-21 13:59:51,931 (MASTER-1) import_datagramReceived

                DEBUG 2017-06-21 13:59:51,936 (MASTER-1) End AMBE encode STREAM ID: 3878647                                                                                                  194 FRAMES: 31

 

Receiving  Callsign properly on DMR radio,  No audio…..

 

Tried to change  ambeSize  from 49 to 72 in Analog_Bridge.ini …..

Checked for TS1 TG9 ok in radio

Commented out  all [RULES] in HB_Bridge.conf

 

I suspect my Thumbdv , I have ordered  another one ……

 

Any clue on what I should check …..


Richard VE2DJE

 

.

 

 

 

 

 

Provenance : Courrier pour Windows 10

 


Re: Analog_Bridge overview

Santu OTTAVI (TK1BI)
 

Hi all,

I'd like to try connecting our Asterisk network with our D-Star network, in a way that would remain compatible with future "DVSwitch".

Is the source code of Analog_Bridge available ?

73 de TK1BI

Le 20/06/2017 à 20:40, G7RPG - Peter Kendall a écrit :
Hi Steve,

Would you be able to give me a brief overview of the setup process to
link ASL <> BM using the new programs.


Thanks

Peter
G7RPG


Re: Analog_Bridge overview

Steve N4IRS
 

Peter,
Great to hear. Sorry for the problem in hblink.cfg. To follow up a little Here is a section of the output from HBlink:
 
INFO 2017-06-20 23:07:26,778 (REPEATER-1) Sending login request to master 1.2.3.4:62031 <---------------- Login sent 
INFO 2017-06-20 23:07:26,803 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1721087229 <------------- OK, the login was accepted
INFO 2017-06-20 23:07:26,834 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:26,835 (REPEATER-1) Repeater Configuration Sent <----------- Configuration sent 
WARNING 2017-06-20 23:07:26,856 (REPEATER-1) MSTNAK Received <----------- OOPS! Something is wrong!

ACK == good NAK == bad!
 


Re: Analog_Bridge overview

G7RPG - Peter Kendall
 

BINGO!

That's got it.

Thank you.


Peter

On 20/06/2017 23:44, Steve N4IRS wrote:
SOFTWARE_ID: 20170529
PACKAGE_ID: MMDVM_HBlink


Re: Analog_Bridge overview

Steve N4IRS
 

Peter:
SOFTWARE_ID: 20170529
PACKAGE_ID: MMDVM_HBlink


On 06/20/2017 06:09 PM, G7RPG - Peter Kendall wrote:

NC110 HBlink-HB_Bridge # ./hblink.py
DEBUG 2017-06-20 23:07:26,775 Logging system started, anything from here on gets logged
INFO 2017-06-20 23:07:26,775 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2017-06-20 23:07:26,777 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:26,778 (REPEATER-1) Sending login request to master 91.121.101.163:62031
DEBUG 2017-06-20 23:07:26,779 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0xb6851a6c>
INFO 2017-06-20 23:07:26,803 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1721087229
INFO 2017-06-20 23:07:26,834 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:26,835 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:26,856 (REPEATER-1) MSTNAK Received
DEBUG 2017-06-20 23:07:31,779 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:31,780 (REPEATER-1) Sending login request to master 91.121.101.163:62031
INFO 2017-06-20 23:07:31,808 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1776249007
INFO 2017-06-20 23:07:31,836 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:31,837 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:31,865 (REPEATER-1) MSTNAK Received
DEBUG 2017-06-20 23:07:36,782 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:36,783 (REPEATER-1) Sending login request to master 91.121.101.163:62031
INFO 2017-06-20 23:07:36,812 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1330675359
INFO 2017-06-20 23:07:36,843 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:36,844 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:36,869 (REPEATER-1) MSTNAK Received
DEBUG 2017-06-20 23:07:41,782 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:41,783 (REPEATER-1) Sending login request to master 91.121.101.163:62031
INFO 2017-06-20 23:07:41,814 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1297483179
INFO 2017-06-20 23:07:41,846 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:41,847 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:41,874 (REPEATER-1) MSTNAK Received



On 20/06/2017 23:01, Steve N4IRS wrote:
Run hblink.py show us the first 10 lines in the console.

On 06/20/2017 05:53 PM, G7RPG - Peter Kendall wrote:

That seems to have made a difference, I've made the change in the config (SOFTWARE_ID: MMDVM_HBlink), I can now see it on the last heard and looks like its working but its not making it through to the hoseline or my repeater. If I tx on my repeater on 23525 I can hear myself ok on hoseline.

Its still not showing up in selfcare OR being logged into the master even though when I TX on ASL I can see it transmitting on the dashboard.

After a few minutes it seems to stop working all together, the process are still running, no errors displayed but TX from ASL goes nowhere.


On 20/06/2017 22:02, Steve N4IRS wrote:
change the
SOFTWARE_ID: HBlink to
SOFTWARE_ID: MMDVM_HBlink

in the client section. I ma going to edit the default in the repository now.

Steve


On 06/20/2017 04:20 PM, G7RPG - Peter Kendall wrote:

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.







Re: Analog_Bridge overview

G7RPG - Peter Kendall
 

NC110 HBlink-HB_Bridge # ./hblink.py
DEBUG 2017-06-20 23:07:26,775 Logging system started, anything from here on gets logged
INFO 2017-06-20 23:07:26,775 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2017-06-20 23:07:26,777 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:26,778 (REPEATER-1) Sending login request to master 91.121.101.163:62031
DEBUG 2017-06-20 23:07:26,779 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0xb6851a6c>
INFO 2017-06-20 23:07:26,803 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1721087229
INFO 2017-06-20 23:07:26,834 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:26,835 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:26,856 (REPEATER-1) MSTNAK Received
DEBUG 2017-06-20 23:07:31,779 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:31,780 (REPEATER-1) Sending login request to master 91.121.101.163:62031
INFO 2017-06-20 23:07:31,808 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1776249007
INFO 2017-06-20 23:07:31,836 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:31,837 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:31,865 (REPEATER-1) MSTNAK Received
DEBUG 2017-06-20 23:07:36,782 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:36,783 (REPEATER-1) Sending login request to master 91.121.101.163:62031
INFO 2017-06-20 23:07:36,812 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1330675359
INFO 2017-06-20 23:07:36,843 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:36,844 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:36,869 (REPEATER-1) MSTNAK Received
DEBUG 2017-06-20 23:07:41,782 (REPEATER-1) Client maintenance loop started
INFO 2017-06-20 23:07:41,783 (REPEATER-1) Sending login request to master 91.121.101.163:62031
INFO 2017-06-20 23:07:41,814 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 1297483179
INFO 2017-06-20 23:07:41,846 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-06-20 23:07:41,847 (REPEATER-1) Repeater Configuration Sent
WARNING 2017-06-20 23:07:41,874 (REPEATER-1) MSTNAK Received



On 20/06/2017 23:01, Steve N4IRS wrote:
Run hblink.py show us the first 10 lines in the console.

On 06/20/2017 05:53 PM, G7RPG - Peter Kendall wrote:

That seems to have made a difference, I've made the change in the config (SOFTWARE_ID: MMDVM_HBlink), I can now see it on the last heard and looks like its working but its not making it through to the hoseline or my repeater. If I tx on my repeater on 23525 I can hear myself ok on hoseline.

Its still not showing up in selfcare OR being logged into the master even though when I TX on ASL I can see it transmitting on the dashboard.

After a few minutes it seems to stop working all together, the process are still running, no errors displayed but TX from ASL goes nowhere.


On 20/06/2017 22:02, Steve N4IRS wrote:
change the
SOFTWARE_ID: HBlink to
SOFTWARE_ID: MMDVM_HBlink

in the client section. I ma going to edit the default in the repository now.

Steve


On 06/20/2017 04:20 PM, G7RPG - Peter Kendall wrote:

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.






Re: Analog_Bridge overview

Steve N4IRS
 

Run hblink.py show us the first 10 lines in the console.

On 06/20/2017 05:53 PM, G7RPG - Peter Kendall wrote:

That seems to have made a difference, I've made the change in the config (SOFTWARE_ID: MMDVM_HBlink), I can now see it on the last heard and looks like its working but its not making it through to the hoseline or my repeater. If I tx on my repeater on 23525 I can hear myself ok on hoseline.

Its still not showing up in selfcare OR being logged into the master even though when I TX on ASL I can see it transmitting on the dashboard.

After a few minutes it seems to stop working all together, the process are still running, no errors displayed but TX from ASL goes nowhere.


On 20/06/2017 22:02, Steve N4IRS wrote:
change the
SOFTWARE_ID: HBlink to
SOFTWARE_ID: MMDVM_HBlink

in the client section. I ma going to edit the default in the repository now.

Steve


On 06/20/2017 04:20 PM, G7RPG - Peter Kendall wrote:

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.





Re: Analog_Bridge overview

G7RPG - Peter Kendall
 

That seems to have made a difference, I've made the change in the config (SOFTWARE_ID: MMDVM_HBlink), I can now see it on the last heard and looks like its working but its not making it through to the hoseline or my repeater. If I tx on my repeater on 23525 I can hear myself ok on hoseline.

Its still not showing up in selfcare OR being logged into the master even though when I TX on ASL I can see it transmitting on the dashboard.

After a few minutes it seems to stop working all together, the process are still running, no errors displayed but TX from ASL goes nowhere.


On 20/06/2017 22:02, Steve N4IRS wrote:
change the
SOFTWARE_ID: HBlink to
SOFTWARE_ID: MMDVM_HBlink

in the client section. I ma going to edit the default in the repository now.

Steve


On 06/20/2017 04:20 PM, G7RPG - Peter Kendall wrote:

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.




Re: Analog_Bridge overview

Steve N4IRS
 
Edited

Sorry, I did not see the included files until after I replied.
change the
SOFTWARE_ID: HBlink to
SOFTWARE_ID: MMDVM_HBlink

in the client section. I ma going to edit the default in the repository now.

Steve


On 06/20/2017 04:20 PM, G7RPG - Peter Kendall wrote:

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.


Re: Analog_Bridge overview

Steve N4IRS
 

So,
The first problem you have to figure out is why are you now showing up in selfcare, assuming that you are sysop of 2342425.
hblink in this configuration is a client connected to the Master server. Since HB_Bridge uses hblink to connect, just start hblink in the foreground. You should see it connect to the BM server.
Check your client configuration in hblink.cfg.

Steve 

On 06/20/2017 04:20 PM, G7RPG - Peter Kendall wrote:

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.



Re: Analog_Bridge overview

G7RPG - Peter Kendall
 

Hi Steve

Pretty much got everything set, when I start HB_Bridge I'm seeing this in the log when I TX on ASL

DEBUG 2017-06-20 21:13:46,087 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:13:46,096 (REPEATER-1) End AMBE encode STREAM ID: 2766688308 FRAMES: 37
DEBUG 2017-06-20 21:14:12,096 (REPEATER-1) Client maintenance loop started
DEBUG 2017-06-20 21:14:15,119 (REPEATER-1) import_datagramReceived
INFO 2017-06-20 21:14:15,121 (REPEATER-1) Begin AMBE encode STREAM ID: 825742713 SUB: G7RPG (2342425) REPEATER: 2342425 (2342425) TGID 23525 (23525), TS 2
DEBUG 2017-06-20 21:14:15,253 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,255 (REPEATER-1) import_datagramReceived
DEBUG 2017-06-20 21:14:15,272 (REPEATER-1) import_datagramReceived

I'm not seeing anything on the BM dashboard, if I TX on DMR TG23525 nothing is showing in logs or making it to ASL. If I look in selfcare I can't see 2342425 as being logged on.

Peter


On 20/06/2017 19:59, Steve N4IRS wrote:
Peter,
It's pretty basic.
Analog_Bridge needs 2 files, Analog_Bridge and Analog_Bridge.ini You will of course also need a Vocoder (ThumbDV)
From the repository, choose the executable you will run ARM, x64 etc. rename it to Analog_Bridge
Edit Analog_Bridge.ini to taste

For HB_Bridge you will need to edit HB_Bridge.cfg and hblink.cfg
hblink.cfg deals with your connection to BM
HB_Bridge.cfg deals with the connection to the Partner application. In this case, Analog_Bridge.

Your system will look something like this:
ASL <---> Analog_Bridge <---> HB_Bridge <---> BM 

You are working with 3 programs, ASL, Analog_Bridge and HB_Bridge. Take them 1 at a time. You can build from right to left or left to right.


Re: How cleanly stop bride.py

Bob N1XBM <N1XBM@...>
 

Thanks Steve,

I think I'll try like Corey suggested and do something like /opt/dmrlinknew while I get things built and then I can temporarily shut down my existing software to test the new stuff so I'm not off air long.

N1XBM
Apparare Scientor
Paratus Communicare
Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
www.radioguysrepeaternetwork.com

9441 - 9460 of 9589