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.

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

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

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

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

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

I am running the serial connection.