Date   

Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Uli
 

Thanks Eric,
I´ll give it a try

Uli


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Eric-K6KWB
 

Uli, 
Just to be clear, this is a YSF Ref <-> XLX Ref modul A

See sample below - this will connect to XLX??? module A

MB.ini

[DMR Network]
Enable=1
Address=ip or DNS of XLX reflector
Port=62030
Jitter=360
Local=62032  >>> pay attention to this port will interfere if duplicate somewhere in the same server.
Password=passw0rd
# 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=XLX:4001  >>>>module A
Slot1=0
Slot2=1
Debug=1

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.0
LocalPort=0
GatewayAddress=ip address or DNS of Ref
GatewayPort=42000  >>> YSF port
Debug=1

DVSwitch.ini

[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

[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 = your id            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = tg9                 ; Which TG to export 
Slot = 2                        ; Export slot

73, Eric


Re: HBlink Questions

Steve N4IRS
 

Matthew,
I think you will get a better response in the HBlink subgroup <https://dvswitch.groups.io/g/HBlink>

73, Steve N4IRS

On 5/2/20 4:06 PM, Matthew Miller via groups.io wrote:
Ok so in my last I figured out how to get a mmdvm to connect to the cbridge using dmrlink, hbridge,hblink. 
Now question is, can I build a HBlink master that only has certain talk groups on it and only those would forward down the line to the cbridge?

So say I have 6 mmdvms that I want to connect to hblink. have that hblink connect to the master hblink and that forwards everything down the line?

if so how do you setup hblink as a client to another hblink?

Or am I just confusing myself?
Thanks KD2CFH


HBlink Questions

Matthew Miller
 

Ok so in my last I figured out how to get a mmdvm to connect to the cbridge using dmrlink, hbridge,hblink. 
Now question is, can I build a HBlink master that only has certain talk groups on it and only those would forward down the line to the cbridge?

So say I have 6 mmdvms that I want to connect to hblink. have that hblink connect to the master hblink and that forwards everything down the line?

if so how do you setup hblink as a client to another hblink?

Or am I just confusing myself?
Thanks KD2CFH


Re: Bluetooth PTT Button

David - W9DWH/4
 

Thanks.


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

EA5GVK Joaquin
 

The update for DVLink V9.2.0 has just been released. It can be updated via OTA or we have provided a link to download images directly from the current version 9.2.0.
Here is a link to download and information as well as CHANGELOG.

http://ea5gvk-dmr.zigor.es/dvlink-v9-change-log/

73 EA5GVK & EA7JCL.


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Uli
 

Hi Eric,
here is my MMDVM_Bridge.ini and the DVSwitch.ini
This setup currently bridges a YSF Reflector to a Brandmeister TG (defined in DVSwitch.ini) and works fine
What I have in mind is to replace the existing YSF-only Reflector with the XLX Reflector.
YSF Reflector and Bridge are currently running on 2 separate RPIs
The XLX Reflector runs on another machine, all are in the same network
The XLX Reflector is this one:
https://github.com/n5amd/xlxd-debian-installer
I´m also running AMBED with Vocoder Chip Hardware attached für D-Star

thanks and 73
Uli

******************************MMDVM_Bridge.ini **************************
[General]
Callsign=DJ5UW
Id=263857408
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
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/mmdvm
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/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=master2.bm262.de
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# 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=1

[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=192.168.10.125
GatewayPort=42004
Debug=1

[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

***********************************  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,$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 = 31100                  ; Port to send AMBE TLV frames to (export)
RXPort = 31103                  ; 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 = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31100                  ; Port to listen on (import)
FallbackID = 2638574            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 26283                 ; Which TG to export 
Slot = 2                        ; Export slot

**********************************************************************


Re: #dmrlink #hblink #best_practices <cbridge><IPSEC><HBLINK3> #dmrlink #hblink #best_practices

KB5PBM
 

Correct.  Is your cbridge ipsc connection a master or client.  I set all my hblink connections as master in cbridge and client in dmrlink.cfg.   Execute IPSC_Bridge and watch the log console.  Make sure UDP ports match on your master IPSC config and dmrlink.cfg Client section.  On the cbridge dont add a password to each IPSC timeslot. Just enable.  


Re: #dmrlink #hblink #best_practices <cbridge><IPSEC><HBLINK3> #dmrlink #hblink #best_practices

area51now@...
 

I never played with C-bridge but I believe what your trying accomplish would be something l like this

IPSC_Bridge<->HB_Bridge <->hblink3

Bob


#dmrlink #hblink #best_practices <cbridge><IPSEC><HBLINK3> #dmrlink #hblink #best_practices

Matthew Miller
 

I have a couple of questions that are just causing my mind not to wrap around a few things.
Right now I have IPsec talking to the cbridge and things are flowing in from the cbridge and I see talk groups, Problem I am having is how do I connect HBLink3 to the IPsec? I have tried a few different ways but I get an error saying that HBlink cannot auth with IPsec. I get the following warning
WARNING 2020-05-01 19:47:21,839 (MAIN) AuthError: IPSC packet failed authentication. Type 52: Peer: 1347699532, 127.0.0.1:50002
I am running IPSec_bridge.py and Hblink.py
Also including the config files
Any Help would be great!

Kd2cfh


Re: Changelog

Tom Corcoran
 

Very nice deliverable. Earlier comment is right on … "cabin fever" can have some side benefits!!

AGC function makes a big difference. Is there any source you can point me at that describes how to use the AUDIO_BPF option?
--
Tom VE3NY


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Eric-K6KWB
 

Uli,
I had my XLX and YSF reflector set up this way one instances of MB and its working. Do you have a copy of your MB.ini that we can take a look?
best and 73, Eric


Re: Bluetooth PTT Button

Steve N4IRS
 

David,
I have used Button Mapper to determine what code a button sends. <https://play.google.com/store/apps/details?id=flar2.homebutton>

73, Steve N4IRS

On 5/1/2020 1:18 PM, David - W9DWH/4 via groups.io wrote:
I have a 2013 Ford Edge with the SYNC 2 entertainment system.  On Zello I can use the Play/Pause button, on the steering wheel, as my PTT when connected to bluetooth audio.  Setting it up on Zello was easy. All I had to was just press the button I wanted to use as my PTT and it saved it.  It's a little more difficult on DVSwitch.  It wants a numeric code for the PTT.  I have searched for documentation that would tell me which bluetooth buttons sends which numeric codes or an app that would sniff out the numeric codes when the buttons are pressed. I haven't had any luck on either count. Does anyone have ideas how I can find the numeric code, for my steering wheel play/pause button, so that I can use DVSwitch hands free?


Bluetooth PTT Button

David - W9DWH/4
 

I have a 2013 Ford Edge with the SYNC 2 entertainment system.  On Zello I can use the Play/Pause button, on the steering wheel, as my PTT when connected to bluetooth audio.  Setting it up on Zello was easy. All I had to was just press the button I wanted to use as my PTT and it saved it.  It's a little more difficult on DVSwitch.  It wants a numeric code for the PTT.  I have searched for documentation that would tell me which bluetooth buttons sends which numeric codes or an app that would sniff out the numeric codes when the buttons are pressed. I haven't had any luck on either count. Does anyone have ideas how I can find the numeric code, for my steering wheel play/pause button, so that I can use DVSwitch hands free?


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Uli
 

Hi Steve
I have tried various settings in the MMDVM_Bridge.ini but it does not work.

The XLX Reflector is the latest from Jan. 2020 which is running the new Wires-X mode (instead of YSF)

Is there a MMDVM_Bridge.ini that contains all necessary entries for this connection?
E.g- the Part that connects to the Brandmeister TG and the part that connects to the XLX Reflector ?
Especially how to connect to Modul A on the reflector and what ports are needed and where exactly to put the IP Adress of the reflector.
The reflector runs on a different machine in the same local net as the bridge 192.168.xx.xx
Are there special entries in the DVSwitch.ini necessary

Uli


Re: Changelog

SP2ONG Waldek
 

Hi Mike,

Thank you very much for the extensive description which is very useful and allows you to better understand how to use it. Yes, I know that we can use a direct connection with MMDM_Bridge with YSF reflector but surely there are differences in audio levels between for example C4FM and DMR and so users with YSF Reflector are heard quieter on DMR and DMR users on YSF Reflector are heard too loud compared to a station with C4FM. For this reason, for YSFN I would also like to use two Analog_Bridge  to be able to compensate for audio levels. Unless there is another way? The same problem is with NXDN.


73 Waldek, SP2ONG


Re: Changelog

Mike Zingman - N4IRR
 

Hello Waldek,

So, this is a BIG topic which covers several ways you may want to use the DVSwitch components.  The multiple transmit ports in general will allow you to have a much richer assortment of networks/modes bridged.  We will cover this is a very long message to come later.

The YSF change was actually done a while ago (before multi-ports), but did not get released until this last build.  Its original intent was to allow both wide and narrow YSF variants to be bridged to another mode.  As you may understand, MB can only bridge like modes together and all others must be transcoded before they can be bridged.  What this addition lets you do is to have BOTH a like mode bridge AND a transcoded bridge at the same time.  This is mostly unique to YSF, but has other uses as well.

So lets take an example DMR <--> YSF bridge.  Before the last release you could bridge the AMBE directly between the two modes and all would work well.  However, if a transmission on YSF wide was seen, the bridge would drop those voice packets since they were not of the proper data type for DMR.  Now you "could" have transcoded ALL (narrow and wide) and then re-encoded them, but this is a bad solution because of the loss of quality.

Now, what we can do is this:
DMR <--- > YSFN (direct mode bridge)
DMR <-- AB_AMBE <-- AB_IMBE <-- YSFW (transcoded bridge)

The only change you need is to define the TXWidePort to point at AB_IMBE and make the AB_AMBE point to the same port as the direct mode bridge.  The above diagram looks like two separate bridge instances, but it is not!  There is an an instance of MB and two instances of AB.  That is all.  The rest is just port mapping.

I did not use any port numbers in my example on purpose.  They do not matter.  As long as they match on each side.  So you "could"
DMR = 30001
YSFN = 3002
AB_AMBE = 3003
AB_IMBE = 3004
YSFW = 3005

I do not care what the numbers as long as the RX port for each mode is unique and the transmit ports match it.  Lets follow the data as it moves from mode to mode.  First the like modes are simple.  A transmission on DMR will be exported to the YSFN listener and sent to the network.  Good.  Same for the reverse direction.  Now a YSFW transmission is sent to the TXWidePort.  AB_IMBE is listening to that port, gets the TLV, decodes it to PCM, sends it to AB_AMBE to encode into AMBE and then sends the TLV to the same YSFN port.  Done. And lastly, please notice that the transcode for YSFW to DMR is only one way.  Why?  Because 1) it would be bad to have both modes arrive at the same time and 2) It is not needed. The YSF radio will decode the narrow transmission just fine.

All of this was done with only a single transmit port for each mode defined.  In future posts we will discuss how multiple transmit ports adds to this discussion.

Hope this made some sense
73, Mike N4IRR


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Steve N4IRS
 

Correct, Andy publishes his code on github just like we do.

Steve

On 4/30/2020 1:32 PM, ve6gcd@... wrote:
Hi Steve,

I guess my info is incorrect. Last time I experimented with YSF2DMR, I downloaded it from Github:

https://github.com/juribeparada/YSF2DMR

73,
Geoffrey VE6GCD


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

ve6gcd@...
 

Hi Steve,

I guess my info is incorrect. Last time I experimented with YSF2DMR, I downloaded it from Github:

https://github.com/juribeparada/YSF2DMR

73,
Geoffrey VE6GCD


Re: Is there a simple way for Bridging a YSF Reflector to an XLX Reflector (new 2020 Version)

Steve N4IRS
 

Geoff,
No, YSF2DMR is a program by Andy CA6JAU. He built it as part of his excellent work on the MMDVM Hotspot code.

Steve N4IRS

On 4/30/2020 1:23 PM, ve6gcd@... wrote:
YSF2DMR code was derived from MMDVM Bridge.

So if you already have MMDVM Bridge installed, know how to configure and got it working previously, then there is no need to install YSF2DMR.

73,
Geoffrey VE6GCD