Date   

how to link hblink with Echolink

cn8vx.ma@...
 

Hi and thank you in advance for your help
I recently mounted an HBlink server that here is its link http://dnsrjyouness.ddns.net:8080/.
I would like to know how to link my HBlink server with Echolink from an OM who offers me there.
Knowing that I am not a LINUX expert but I manage if someone can help me step by step
Thank you and 73 from CN8VX


RE : Re: [DVSwitch] Link DMR <==> FCSXXX

Bruno
 

Hi Doug,

 

I used a connection  MMDVM_Bridge + YSFGateway FCSXXX

 

HBlink-Fr <===>MMDVM_Bridge <====> YSFGateway FCSxxxx

 

File configuration DVSwitch.ini

/opt/MMDVM_Bridge_FCS# more DVSwitch.ini

; MMDVM_Bridge export / import configuration file.

;   This file should be placed along side of MMDVM_Bridge or it can be

;   supplied as a path on the MMDVM_BRIDGE environment variable.

 

; Configure the Quantar Repeater Partner

; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge

[QUANTAR]

logFilePath = /var/log/Quantar_Bridge.log

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 34103                  ; Port to send AMBE TLV frames to (export)

RXPort = 34100                  ; Port to listen on (import)

quantarPort = 1994              ; HDLC frames To/From the Quantar repeater

logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

 

; Configure the DMR Partner

; Audio format is AMBE 72 bit

[DMR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 36100                  ; Port to send AMBE TLV frames to (export)

RXPort = 36103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

 

; Configure the D-Star Partner

; Audio format is AMBE 48 bit (DSAMBE)

[DSTAR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 32100                  ; Port to send AMBE TLV frames to (export)

RXPort = 32103                  ; Port to listen on (import)

FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one

ExportTG = 9                    ; Which TG to export

Slot = 2                        ; Export slot

 

; Configure the NXDN Partner

; Audio format is AMBE 72 bit

[NXDN]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 33100                  ; Port to send AMBE TLV frames to (export)

RXPort = 33103                  ; Port to listen on (import)

FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one

NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database

Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)

Slot = 2                        ; Export slot

 

; Configure the P25 Partner

; Audio format is IMBE 88 bit

[P25]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 34100                  ; Port to send AMBE TLV frames to (export)

RXPort = 34103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

 

; Configure the Yaesu Fusion Partner

; Audio format is AMBE 72 bit

; Audio format is IMBE 88 bit

[YSF]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 36103                  ; Port to send AMBE TLV frames to (export)

RXPort = 36100                  ; Port to listen on (import)

; FallbackID = 208011           ; In case we can not find a valid DMR id in the database, export this one

ExportTG = 133                  ; Which TG to export =>  TG133 in DMR

Slot = 2                        ; Export slot

 

 

 

File Configuration MMDVM_Bridge.ini

/opt/MMDVM_Bridge_FCS# more  MMDVM_Bridge_FCS.ini

[General]

Callsign=DVSFCS

Id=208XXXXXX

Timeout=240

Duplex=0

 

[Info]

RXFrequency=434500000

TXFrequency=434500000

Power=1

Latitude=41.7333

Longitude=-50.3999

Height=10

Location=FCS133 <=> DMR

Description=MMDVM_Bridge_FCS

URL=https://groups.io/g/DVSwitch

 

[Log]

# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

DisplayLevel=1

FileLevel=2

FilePath=/var/log

FileRoot=MMDVM_Bridge_FCS

 

[DMR Id Lookup]

File=/home/toto/ref/DMRIds.dat

Time=24

 

[NXDN Id Lookup]

File=/home/toto/ref/NXDN.csv

Time=24

 

[Modem]

Port=/dev/null

RSSIMappingFile=RSSI.dat

Trace=0

Debug=0

 

[D-Star]

Enable=0

Module=C

 

[DMR]

Enable=1

ColorCode=1

EmbeddedLCOnly=1

DumpTAData=0

 

[System Fusion]

Enable=1

 

[P25]

Enable=0

NAC=293

 

[NXDN]

Enable=0

RAN=1

Id=12345

 

[D-Star Network]

Enable=0

GatewayAddress=127.0.0.1

GatewayPort=20010

LocalPort=20011

Debug=0

 

[DMR Network]

Enable=1

Address=SRV-HBlink3 @IP

Port=54200

Jitter=360

# Local=62032

Password=tototititata

# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

# for XLX the syntax is: Options=XLX:4009

# Options=

Slot1=0

Slot2=1

Debug=0

 

[System Fusion Network]

Enable=1

LocalAddress=0

LocalPort=3250

GatewayAddress=127.0.0.1

GatewayPort=4250

Debug=0

 

[P25 Network]

Enable=0

GatewayAddress=127.0.0.1

GatewayPort=42020

LocalPort=32010

Debug=0

 

[NXDN Network]

Enable=0

#LocalAddress=127.0.0.1

Debug=0

LocalPort=14021

GatewayAddress=127.0.0.1

GatewayPort=14020

 

 

 

File Configuration YSFGateway.ini

more YSFGateway_FCS.ini

[General]

Callsign=DVSFCS

Suffix=ND

Id=208XXXX

RptAddress=127.0.0.1

RptPort=3250

LocalAddress=127.0.0.1

LocalPort=4250

WiresXMakeUpper=1

WiresXCommandPassthrough=0

Daemon=0

 

[Info]

RXFrequency=434500000

TXFrequency=434500000

Power=1

Latitude=0.0

Longitude=0.0

Height=0

Name=Link FCS <=> DMR

Description=Link YSFGateway

 

[Log]

# Logging levels, 0=No logging

DisplayLevel=1

FileLevel=2

FilePath=/var/log

FileRoot=YSFGateway_FCS

 

[aprs.fi]

Enable=0

# Server=noam.aprs2.net

Server=euro.aprs2.net

Port=14580

Password=9999

Description=APRS Description

Suffix=Y

 

[Network]

Startup=FCS00133

InactivityTimeout=0

Revert=0

Debug=0

 

[YSF Network]

Enable=0

Port=42000

Hosts=/home/teambvc/ref/YSFHosts.txt

ReloadTime=60

ParrotAddress=127.0.0.1

ParrotPort=42012

YSF2DMRAddress=127.0.0.1

YSF2DMRPort=42013

YSF2NXDNAddress=127.0.0.1

YSF2NXDNPort=42014

YSF2P25Address=127.0.0.1

YSF2P25Port=42015

 

[FCS Network]

Enable=1

Rooms=/home/toto/ref/FCSRooms.txt

Port=42001

 

[Mobile GPS]

Enable=0

Address=127.0.0.1

Port=7834

 

 

73’s

F1PTL Bruno

 

Provenance : Courrier pour Windows 10

 

De : Doug - W4DBG
Envoyé le :samedi 7 mars 2020 00:49
À : main@dvswitch.groups.io
Objet :Re: [DVSwitch] Link DMR <==> FCSXXX

 

I have searched and searched.. Just seeing if there is an update or a certain configuration that is needed to do DMR <> FCS ?

 

Thanks,

 

Doug

W4DBG

 

 

 

On Fri, Dec 7, 2018 at 10:44 AM Bruno <ff1ptl@...> wrote:

Hi,

 

Super thank you very much for the developments. Congratulations for your work.

 

73's

 

F1PTL Bruno

 

Le ven. 7 déc. 2018 à 15:03, Steve N4IRS <szingman@...> a écrit :

We have identified a bug. It is being worked on now. I will post when you can update.

Steve N4IRS

On 12/4/2018 4:41 PM, Bruno wrote:

Starting logging, please wait...
M: 2018-12-04 21:39:55.381 YSF, network watchdog has expired, 152.4 seconds, 0% packet loss, BER: 0.0%

M: 2018-12-04 21:39:58.946 YSF, received network data from N4IRR to ALL at FCS001-33 

 



--

Doug Gooden
troytrojan@...

 




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com



--
Hello everyone,
I want to set up a Link between HBLink and a room Wires-X from Yeasu in C4FM. Is there a possibility to set up the type of editing.
73 to all.
F1PTL Bruno


Re: Link DMR <==> FCSXXX

Doug - W4DBG
 

I have searched and searched.. Just seeing if there is an update or a certain configuration that is needed to do DMR <> FCS ?

Thanks,

Doug
W4DBG



On Fri, Dec 7, 2018 at 10:44 AM Bruno <ff1ptl@...> wrote:
Hi,

Super thank you very much for the developments. Congratulations for your work.

73's

F1PTL Bruno

Le ven. 7 déc. 2018 à 15:03, Steve N4IRS <szingman@...> a écrit :
We have identified a bug. It is being worked on now. I will post when you can update.

Steve N4IRS

On 12/4/2018 4:41 PM, Bruno wrote:
Starting logging, please wait...
M: 2018-12-04 21:39:55.381 YSF, network watchdog has expired, 152.4 seconds, 0% packet loss, BER: 0.0%
M: 2018-12-04 21:39:58.946 YSF, received network data from N4IRR to ALL at FCS001-33 



--
Doug Gooden
troytrojan@...


Re: I want to link DMR and WIRES-X with Allstarlink.

Skyler Fennell
 

I haven’t messed much with system confusion wires X

If you run the wiresX box in analog, can you connect to digital nodes? Or just analog nodes? Is there an AMBE chip in those HRI200 boxes to cross-over a to d, is that what makes them so expensive? 

Skyler 

On Fri, Mar 6, 2020 at 2:47 PM Mike, AA9VI via Groups.Io <mjswiatk=yahoo.com@groups.io> wrote:
See the first two pages.  Hope this helps.

Mike, AA9VI


Re: Documentation

Tom Corcoran
 

enabled various networks in DMRGateway.ini … but DVSwitch still stays in BM. Will check out Pi-Star to see if there are any clues.
--
Tom VE3NY


Re: I want to link DMR and WIRES-X with Allstarlink.

Mike, AA9VI
 

See the first two pages.  Hope this helps.

Mike, AA9VI


Re: I want to link DMR and WIRES-X with Allstarlink.

Mike, AA9VI
 

Patrick,
It is totally possible and I have it working on allstarlink node 46625, wires-X 40911.  I connected the URI-x interface to the wires-X box. You do need a pull up on one of the lines and the Wires-X has to be set for analog mode.  I forget which line has to be pulled high.  I'll have to look at my documentation and send it along when I get a chance.

Mike, AA9VI


Re: I want to link DMR and WIRES-X with Allstarlink.

ve6gcd@...
 

It is possible to link AllStarLink to a Wires-X round room, not very straightforward though. It all depends on the interface you are using. For example, an ASL sound fob may not be able to transmit to Wires-X due to signaling incompatibility between the ASL fob's PTT and the HRI-200's COS pin. Take note that at least 3.5V is needed to key up the HRI-200 COS pin.


Re: I want to link DMR and WIRES-X with Allstarlink.

Patrick Perdue
 

AFAIK, if you want to link Wires-X to anything, you need an RF link between YSF and Wires-X using a hotspot and a radio connected to the HRI-200 for hosting a Wires-X room. You can't connect an HRI-200 directly to ASL.


On 3/5/2020 5:53 PM, hopeseoul@... wrote:

I want to link DMR and WIRES-X with Allstarlink.
WIRES-X uses an ARiUSB interface.
I modified the Allstarlink setup file but it shouldn't.
Please help me.
Thank you.

 


I want to link DMR and WIRES-X with Allstarlink.

hopeseoul@...
 

I want to link DMR and WIRES-X with Allstarlink.
WIRES-X uses an ARiUSB interface.
I modified the Allstarlink setup file but it shouldn't.
Please help me.
Thank you.

 


Re: Overdriven P25 audio

Heiko DL1BZ
 

I'm running "in production" a DMR<>P25 bridge long time. Beware, there are two ways (DMR>P25 and P25>DMR) you need to adjust.:
Here my settings:
analog_bridge DMR:
usrpAudio = AUDIO_USE_GAIN               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.0                           ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_USE_GAIN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.6                           ; Gain factor of audio from ASL (0.0-1.0)

analog_bridge P25:
usrpAudio = AUDIO_USE_GAIN               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.0                           ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_USE_GAIN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 1.0                           ; Gain factor of audio from ASL (0.0-1.0)

WIth this setup all is ok, the audio level are good and acceptable.

73 Heiko, DL1BZ


Re: Overdriven P25 audio

Steve N4IRS
 

No change. Remember there are 2 level settings:

usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

On 3/5/2020 11:04 AM, Kevin N9OIG wrote:
Was there a change from the default? Mine from default is .35 on both Analog_Bridge_DME.ini and P25.


Re: Overdriven P25 audio

Kevin N9OIG
 

Was there a change from the default? Mine from default is .35 on both Analog_Bridge_DME.ini and P25.


Re: Documentation

Steve N4IRS
 

I don't see why not. I have not used DMRGateway.

On 3/5/2020 8:50 AM, Tom Corcoran wrote:
Steve,

I'm familiar with use of DMRGateway from pistar experience. If I enable networks In DMRGateway.ini, can I access them using same protocol (ex. 84639 for DMRplus reflector 4639)? More to be done in DVSwitch?
--
Tom VE3NY


Re: Documentation

Tom Corcoran
 

Steve,

I'm familiar with use of DMRGateway from pistar experience. If I enable networks In DMRGateway.ini, can I access them using same protocol (ex. 84639 for DMRplus reflector 4639)? More to be done in DVSwitch?
--
Tom VE3NY


Re: DStar on Cloud Server

Tom Corcoran
 

Hello Patrick,

I think it's the latency between the cloud server and the ambeserver/rpi that is causing the problem. It is interesting that when everything is fired up audio sounds fine. It's only after 10 - 20 minutes that the audio on all modes (including dstar) degrades. Cloud server and RPI/AMBEServer are both here in Miami.
--
Tom VE3NY


Re: DStar on Cloud Server

Patrick Perdue
 

How is the latency between your AMBEserver and the cloud VPS?

I ran a setup like that for a while, where pings were only about 2/4 MS between my home internet connection and the VPS, and all was fine. However, on another connection where latency was around 20 MS, things started to become choppy after a while. In my case, I was transcoding ASL/DMR, so not quite the same thing. I got better results running Analog_Bridge on the machine hosting the AMBE than connecting AMBE to a remote Analog_Bridge, even though I was just turning the packets around to the VPS again anyway.


On 3/4/2020 11:24 AM, Tom Corcoran wrote:
All,

I have used W8RIK's excellent install document to set up an image on a cloud server. Works great on DMR, YSF, NXDN and P25. When I connect an ThumbDV/ambeserver on a RPi at my home, everything seems to work ok on all modes. Audio sounds good on all modes, including DStar. However, over time (20 minutes), the audio becomes choppy. The ambeserver rpi has the latency code installed. Anyone have success with this approach? Advice??


-- 
Tom VE3NY
--
Tom VE3NY


DStar on Cloud Server

Tom Corcoran
 

All,

I have used W8RIK's excellent install document to set up an image on a cloud server. Works great on DMR, YSF, NXDN and P25. When I connect an ThumbDV/ambeserver on a RPi at my home, everything seems to work ok on all modes. Audio sounds good on all modes, including DStar. However, over time (20 minutes), the audio becomes choppy. The ambeserver rpi has the latency code installed. Anyone have success with this approach? Advice??


-- 
Tom VE3NY
--
Tom VE3NY


Re: Access to a Fusion FCS room #dmrlink

Steve N4IRS
 

If I remember correctly, at this time you can auto connect to a FCS room. (When YSFGateway starts) but you can not dial a arbitrary FCS room. This will be changing.

On 3/4/2020 10:44 AM, Tom Corcoran wrote:
I note that FCS is enabled in YSFGateway.ini. Not sure if this is new. 

does this mean that MB can now connect directly to FCS rooms?
--
Tom VE3NY


Re: Access to a Fusion FCS room #dmrlink

Tom Corcoran
 

I note that FCS is enabled in YSFGateway.ini. Not sure if this is new. 

does this mean that MB can now connect directly to FCS rooms?
--
Tom VE3NY

3861 - 3880 of 9797