Date   

Re: Setup of dmrlink and hblink

Florian Wolters
 

Ah right. I will stop the experiments on those TGs.


Re: Setup of dmrlink and hblink

Steve N4IRS
 

I did not want to come across as being negative. I really think DMRlink / HBlink can be a positive for DMR-MARC. With the existing interconnects to DMR+, they do not have the finite control of what MMDVM based system are connected. Anybody that can connect to a DMR+ server will be connected to DMR-MARC. With DMR/HB it's a more 1 to 1 relationship. A BIG plus for the c-Bridge is that DMR / HB is MUCH more stable then a DMR+ server. Oh, and did I mention it's Open Source.

If anybody has contacts within the DMR-MARC community, talk to them. This can be much better solution for connecting MMDVM to c-Bridge.

Again, these are my thoughts and do NOT reflect the thoughts of anyone else involved.  


Re: Setup of dmrlink and hblink

Florian Wolters
 

Hi Steve,

no worries. I fully understand and was reminded of the MARC policy by your post. Had forgotten that after month fiddling around with MMDVM, BM and XLX :-)

In fact I have contacts to the German DMR-DL / MARC core team. That is where I got my experimental account on cBridge from. Will have a chat with them about this topic at the next opportunity.

vy73 de Florian DF2ET


Re: Setup of dmrlink and hblink

 

Steve, 

I personally see this project as a huge asset to c-Bridge based networks.  

Beyond the technical gains, it can dovetail far better in EmComm and Public Service or Community Service events.  As many of the EmComm or SAR operations tend to receive grant money from State or Federal agencies, there are other concerns as well.

This project has the potential to melt away all those concerns, IMHO.  

As to MARC, the same once they realize that they can maintain control of the resources.  Just them embracing the Sand Box approach demonstrates their general interest.

Unfortunately, I'm not a Linux guy, nor Python for that matter and must plod through this, but still very exciting to see this work being done...by many old and new hands.  We are all fortunate having this talent focused here.

-- Mike, NO7RF,  Mazama, Washington

On Tue, Jun 20, 2017 at 9:49 AM, Steve N4IRS <szingman@...> wrote:
I did not want to come across as being negative. I really think DMRlink / HBlink can be a positive for DMR-MARC. 


Re: How cleanly stop bride.py

Bob N1XBM <N1XBM@...>
 

Steve,

From reading your post, I need Analog_Audio and HB_Bridge. I like this idea because I can control it from my dashboard on BM. 

When the software becomes available is your github the place too look? Is this also the place to look for all software offerings?


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

On Jun 16, 2017 3:20 PM, "Steve N4IRS" <szingman@...> wrote:
Setup dmrlink.cfg to connect to BM
run ambe_audio.py instead of bridge.

The version of dmrlink and ambe_audio you are running does work for the most part. We did find some MAJOR problems in how ASL communicated loss of COS to DMRGateway. This is fixed in what is now called Audio_Bridge and IPSC_Bridge.
I hope to release Audio_Bridge to testing next week. With Audio_Bridge and IPSC_Bridge connected to BM, you will use the same SmartPTT connection. With Analog_Audio and HB_Bridge, it looks to BM like a MMDVM repeater, so not admin intervention required.

Take a look at the Wiki for more info. I still have a LOT of work to do on the Wiki!

Steve

On 6/16/2017 3:10 PM, Bob N1XBM wrote:
I recently directly connected my repeaters to Brandmeister. As far as I can tell I no longer need to use the bridge function of dmrlink. I found out setting the connections to false in dmrlink.cfg causes bridge to not run by crashing. 

What would be the best suggested way to stop the bridge from running?

I am still using ambe_audio for my dmr-analog gateway which appears fine.

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


Re: How cleanly stop bride.py

Steve N4IRS
 

Robert,
The software is available now. Analog_Bridge is at https://github.com/N4IRS/Analog_Bridge and HB_Bridge is in a branch of HBlink at <https://github.com/n0mjs710/HBlink/tree/HB_Bridge>

Steve


Analog_Bridge overview

G7RPG - Peter Kendall
 

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: DMRmonitor

Cort N0MJS <n0mjs@...>
 

I’m leaving an “air gap” on DMRlink and HBlink core stacks for the time being as Mike continues his work — it’s so important I want to stay well clear of it. The completion of the AMBE handling components now in the dmr_utils package give me a boost in making some needed updates to how confbridge works on both sides too!

In the meantime, I am having a TON of fun working on the monitor. I’ve got a side branch now that has the hooks in for RCM-based live-updates on what repeaters are doing (I’ve mentioned this before).

Attached is a screenshot (if it works) of what that table looks like. You’ll see the “master” device is shows in the dark orange type, the stuff in the current DMRmonitor is all there, but “squished” into the lefthand side, and space on the right for live activity updates.

I’m looking for two things right now: Community discussion about this — but please limited to IPSC at this point. And also anyone who has experience with javascript for the browser side who wants to help with that part of it.

So…. discussion now open! If anyone is interested in this, let’s talk on the forum here about it?

On Jun 20, 2017, at 10:52 AM, Steve N4IRS <szingman@...> wrote:

DMRMonitor just pointed out why I was talking to myself on a connected TG. I have a User Activated (PTT) TG bridged for 31201. I know it's a active TG but over the last few weeks whenever I throw out my call sign, I get no reply.
Looking at the DMRmonitor Bridge Group Status Tables, I found that I was connected to the wrong Master! Yes, I could have found it by reading the confbridge rules. With DMRmonitor it stuck out like a sore thumb.

 

Cort Buffington
785-865-7206


Re: Analog_Bridge overview

Steve N4IRS
 
Edited

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.
Or, maybe better yet. Build ASL <---> Analog_Bridge then build HB_Bridge <---> BM Then link Analog_Bridge to HB_Bridge


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


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: 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

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

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
 

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
 

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
 

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,
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

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

121 - 140 of 9795