Date   

BM<->XLX noob question

Andy M0VVA
 

I am trying to bridge a BM TG23594 to my XLX994 reflector, following the guide "BM to XLX via MMDVM Bridge (DV Switch distribution) on Debian 9.pdf" to the letter (I believe).

I can see the XLX side connected fine in the reflector dashboard and there is no error in the log on the BM DMRGateway side.  I am not seeing any traffic from either direction routing through this setup.  I can only imagine I need to create inbound firewall rules to my server but cannot find documented the exact ports I need to open.

Can anyone offer any advice?

For reference the logs are:

-- DMRGateway XLX--

I: 2020-04-24 14:47:29.565 This software is for use on amateur radio networks only,

I: 2020-04-24 14:47:29.566 it is to be used for educational purposes only. Its use on

I: 2020-04-24 14:47:29.566 commercial networks is strictly prohibited.

I: 2020-04-24 14:47:29.566 Copyright(C) 2017-2020 by Jonathan Naylor, G4KLX and others

M: 2020-04-24 14:47:29.566 DMRGateway-20200418 is starting

M: 2020-04-24 14:47:29.566 Built 12:34:06 Apr 24 2020 (GitID #00342c7)

I: 2020-04-24 14:47:29.566 MMDVM Network Parameters

I: 2020-04-24 14:47:29.567     Rpt Address: 127.0.0.1

I: 2020-04-24 14:47:29.567     Rpt Port: 62042

I: 2020-04-24 14:47:29.567     Local Address: 127.0.0.1

I: 2020-04-24 14:47:29.567     Local Port: 62041

M: 2020-04-24 14:47:29.567 MMDVM Network, Opening

M: 2020-04-24 14:47:29.567 Waiting for MMDVM to connect.....

M: 2020-04-24 14:47:38.174 MMDVM has connected

I: 2020-04-24 14:47:38.174 Rule trace: no

I: 2020-04-24 14:47:38.174 Loaded 510 XLX reflectors

I: 2020-04-24 14:47:38.174 XLX Network Parameters

I: 2020-04-24 14:47:38.174     Id: 2348140

I: 2020-04-24 14:47:38.174     Hosts file: /var/lib/mmdvm/XLXHosts.txt

I: 2020-04-24 14:47:38.174     Reload time: 60 minutes

I: 2020-04-24 14:47:38.174     Local: random

I: 2020-04-24 14:47:38.174     Port: 62030

I: 2020-04-24 14:47:38.174     Slot: 1

I: 2020-04-24 14:47:38.174     TG: 6

I: 2020-04-24 14:47:38.174     Base: 64000

I: 2020-04-24 14:47:38.174     Startup: XLX994

I: 2020-04-24 14:47:38.174     Relink: 10 minutes

I: 2020-04-24 14:47:38.174     User Control: disabled

I: 2020-04-24 14:47:38.174      Module: D

I: 2020-04-24 14:47:38.174 XLX: Using original configuration message: MX0ONL  000000000000000000010151.70999-0.075600000Herfordshire,IO91XR MMDVM_Bridge       4https://onlineradioclub.org                                                                                                 20191105_V1.4.1                         MMDVM_DMO                               

M: 2020-04-24 14:47:38.174 XLX, Opening DMR Network

M: 2020-04-24 14:47:38.174 XLX, Connecting to XLX994

I: 2020-04-24 14:47:38.174 Voice Parameters

I: 2020-04-24 14:47:38.174     Enabled: yes

I: 2020-04-24 14:47:38.174     Language: en_GB

I: 2020-04-24 14:47:38.174     Directory: ./Audio

E: 2020-04-24 14:47:38.174 Unable to open the index file - ./Audio/en_GB.indx

M: 2020-04-24 14:47:38.174 DMRGateway-20200418 is running

D: 2020-04-24 14:47:48.184 XLX, Sending authorisation

D: 2020-04-24 14:47:48.194 XLX, Sending configuration

M: 2020-04-24 14:47:48.204 XLX, Logged into the master successfully

M: 2020-04-24 14:47:48.204 XLX, Linking to reflector XLX994 D


--MMDVM_Bridge_XLX--
I: 2020-04-24 14:48:59.643 MMDVM_Bridge:
I: 2020-04-24 14:48:59.643 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2020-04-24 14:48:59.643 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-04-24 14:48:59.644 =
I: 2020-04-24 14:50:02.508 This software is for use on amateur radio networks only,
I: 2020-04-24 14:50:02.508 it is to be used for educational purposes only. Its use on
I: 2020-04-24 14:50:02.508 commercial networks is strictly prohibited.
I: 2020-04-24 14:50:02.508 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-04-24 14:50:02.508 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2020-04-24 14:50:02.508 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac)
I: 2020-04-24 14:50:02.509 General Parameters
I: 2020-04-24 14:50:02.509     Callsign: MX0ONL
I: 2020-04-24 14:50:02.509     Id: 234814010
I: 2020-04-24 14:50:02.510     Duplex: no
I: 2020-04-24 14:50:02.510     Timeout: 180s
I: 2020-04-24 14:50:02.510     D-Star: disabled
I: 2020-04-24 14:50:02.510     DMR: enabled
I: 2020-04-24 14:50:02.510     YSF: disabled
I: 2020-04-24 14:50:02.510     P25: disabled
I: 2020-04-24 14:50:02.511     NXDN: disabled
I: 2020-04-24 14:50:02.511 Modem Parameters
I: 2020-04-24 14:50:02.511     Port: /dev/null
I: 2020-04-24 14:50:02.511     RX Invert: no
I: 2020-04-24 14:50:02.511     TX Invert: no
I: 2020-04-24 14:50:02.511     PTT Invert: no
I: 2020-04-24 14:50:02.512     TX Delay: 100ms
I: 2020-04-24 14:50:02.512     RX Offset: 0Hz
I: 2020-04-24 14:50:02.512     TX Offset: 0Hz
I: 2020-04-24 14:50:02.512     RX DC Offset: 0
I: 2020-04-24 14:50:02.512     TX DC Offset: 0
I: 2020-04-24 14:50:02.512     RF Level: 100.0%
I: 2020-04-24 14:50:02.513     DMR Delay: 0 (0.0ms)
I: 2020-04-24 14:50:02.513     RX Level: 50.0%
I: 2020-04-24 14:50:02.513     CW Id TX Level: 50.0%
I: 2020-04-24 14:50:02.513     D-Star TX Level: 50.0%
I: 2020-04-24 14:50:02.513     DMR TX Level: 50.0%
I: 2020-04-24 14:50:02.514     YSF TX Level: 50.0%
I: 2020-04-24 14:50:02.514     P25 TX Level: 50.0%
I: 2020-04-24 14:50:02.514     NXDN TX Level: 50.0%
I: 2020-04-24 14:50:02.514     RX Frequency: 0Hz (0Hz)
I: 2020-04-24 14:50:02.514     TX Frequency: 0Hz (0Hz)
M: 2020-04-24 14:50:02.514 Opening the MMDVM
I: 2020-04-24 14:50:02.515 Display Parameters
I: 2020-04-24 14:50:02.515     Type: 
I: 2020-04-24 14:50:02.515 DMR Network Parameters
I: 2020-04-24 14:50:02.515     Address: 127.0.0.1
I: 2020-04-24 14:50:02.515     Port: 62051
I: 2020-04-24 14:50:02.515     Local: 62052
I: 2020-04-24 14:50:02.515     Jitter: 360ms
I: 2020-04-24 14:50:02.516     Slot 1: enabled
I: 2020-04-24 14:50:02.516     Slot 2: enabled
I: 2020-04-24 14:50:02.516     Mode Hang: 3s
I: 2020-04-24 14:50:02.516 Info Parameters
I: 2020-04-24 14:50:02.516     Callsign: MX0ONL
I: 2020-04-24 14:50:02.516     RX Frequency: 0Hz
I: 2020-04-24 14:50:02.516     TX Frequency: 0Hz
I: 2020-04-24 14:50:02.517     Power: 1W
I: 2020-04-24 14:50:02.517     Latitude: 51.709999deg N
I: 2020-04-24 14:50:02.517     Longitude: -0.075600deg E
I: 2020-04-24 14:50:02.517     Height: 0m
I: 2020-04-24 14:50:02.517     Location: "Herfordshire,IO91XR"
I: 2020-04-24 14:50:02.517     Description: "MMDVM_Bridge"
I: 2020-04-24 14:50:02.517     URL: "https://onlineradioclub.org"
M: 2020-04-24 14:50:02.517 DMR, Opening DMR Network
I: 2020-04-24 14:50:02.517 RSSI
I: 2020-04-24 14:50:02.517     Mapping File: RSSI.dat
W: 2020-04-24 14:50:02.517 Cannot open the RSSI data file - RSSI.dat
I: 2020-04-24 14:50:02.518 DMR Id Lookups
I: 2020-04-24 14:50:02.518     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-04-24 14:50:02.518     Reload: 24 hours
I: 2020-04-24 14:50:02.811 Loaded 162409 Ids to the DMR callsign lookup table
I: 2020-04-24 14:50:02.812 DMR RF Parameters
I: 2020-04-24 14:50:02.813     Id: 234814010
I: 2020-04-24 14:50:02.813     Color Code: 1
I: 2020-04-24 14:50:02.813     Self Only: no
I: 2020-04-24 14:50:02.813     Embedded LC Only: yes
I: 2020-04-24 14:50:02.813     Dump Talker Alias Data: no
I: 2020-04-24 14:50:02.814     Prefixes: 0
I: 2020-04-24 14:50:02.814     Call Hang: 3s
I: 2020-04-24 14:50:02.814     TX Hang: 3s
I: 2020-04-24 14:50:02.814     Mode Hang: 10s
M: 2020-04-24 14:50:02.814 DMR, Opening INI file: DVSwitch.ini
M: 2020-04-24 14:50:02.815 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-04-24 14:50:02.815 DMR, Setting [DMR] TXPort -> 31100
M: 2020-04-24 14:50:02.815 DMR, Setting [DMR] RXPort -> 31103
M: 2020-04-24 14:50:02.815 DMR, Setting [DMR] Slot -> 2
M: 2020-04-24 14:50:02.816 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-04-24 14:50:02.816 MMDVM_Bridge-20191105_V1.4.1 is running
I: 2020-04-24 14:50:02.816 Started the DMR Id lookup reload thread
D: 2020-04-24 14:50:12.826 DMR, Sending authorisation
D: 2020-04-24 14:50:12.838 DMR, Sending configuration
M: 2020-04-24 14:50:12.848 DMR, Logged into the master successfully

--DMRGateway BM--
I: 2020-04-24 14:50:58.530 Copyright(C) 2017-2020 by Jonathan Naylor, G4KLX and others
M: 2020-04-24 14:50:58.530 DMRGateway-20200418 is starting
M: 2020-04-24 14:50:58.530 Built 12:34:06 Apr 24 2020 (GitID #00342c7)
I: 2020-04-24 14:50:58.530 MMDVM Network Parameters
I: 2020-04-24 14:50:58.530     Rpt Address: 127.0.0.1
I: 2020-04-24 14:50:58.530     Rpt Port: 62052
I: 2020-04-24 14:50:58.530     Local Address: 127.0.0.1
I: 2020-04-24 14:50:58.530     Local Port: 62051
M: 2020-04-24 14:50:58.531 MMDVM Network, Opening
M: 2020-04-24 14:50:58.531 Waiting for MMDVM to connect.....
M: 2020-04-24 14:51:05.146 MMDVM has connected
I: 2020-04-24 14:51:05.146 Rule trace: no
I: 2020-04-24 14:51:05.146 Voice Parameters
I: 2020-04-24 14:51:05.146     Enabled: yes
I: 2020-04-24 14:51:05.146     Language: en_GB
I: 2020-04-24 14:51:05.146     Directory: ./Audio
I: 2020-04-24 14:51:05.146 DMR Network 1 Parameters
I: 2020-04-24 14:51:05.146     Name: BM
I: 2020-04-24 14:51:05.146     Id: 234814010
I: 2020-04-24 14:51:05.146     Address: 3102.repeater.net
I: 2020-04-24 14:51:05.146     Port: 62031
I: 2020-04-24 14:51:05.146     Local: random
I: 2020-04-24 14:51:05.146     Location Data: yes
I: 2020-04-24 14:51:05.148 BM: Using original configuration message: MX0ONL  000000000000000000010151.70999-0.075600000Herfordshire,IO91XR MMDVM_Bridge       4https://onlineradioclub.org                                                                                                 20191105_V1.4.1                         MMDVM_DMO                               
M: 2020-04-24 14:51:05.148 BM, Opening DMR Network
I: 2020-04-24 14:51:05.148     Rewrite RF: 1:TG9 -> 1:TG9
I: 2020-04-24 14:51:05.148     Rewrite Net: 1:TG9 -> 1:TG9
I: 2020-04-24 14:51:05.149     Rewrite RF: 2:TG9 -> 2:TG9
I: 2020-04-24 14:51:05.149     Rewrite Net: 2:TG9 -> 2:TG9
I: 2020-04-24 14:51:05.149     Rewrite RF: 2:TG6 -> 2:TG23594
I: 2020-04-24 14:51:05.149     Rewrite Net: 2:TG23594 -> 2:TG6
I: 2020-04-24 14:51:05.149     Rewrite RF: 2:94000-95000 -> 2:4000-5000
I: 2020-04-24 14:51:05.150     Rewrite RF: 1:TG9990 -> 1:9990
I: 2020-04-24 14:51:05.150     Rewrite Net: 1:9990 -> 1:TG9990
I: 2020-04-24 14:51:05.150     Rewrite Net: 2:4000-5000 -> 2:TG9
I: 2020-04-24 14:51:05.150     Pass All PC: 1
I: 2020-04-24 14:51:05.151     Pass All PC: 2
M: 2020-04-24 14:51:05.151 DMRGateway-20200418 is running
D: 2020-04-24 14:51:15.265 BM, Sending authorisation
D: 2020-04-24 14:51:15.377 BM, Sending configuration
M: 2020-04-24 14:51:15.499 BM, Logged into the master successfully

Thanks and 73
Andy M0VVA


Analog_Bridge log files

 

I am running 2 instances of  Analog_Bridge and  MMDVM_Bridge on  a Debian9   VPS server installation.

They have their own log file  .

All log files are  are running OK  but  size of Analog_Bridge.log  and number  of files  for MMDVM_Bridge-2020-mm-dd.log  are getting out of hand .

Can   anyone tell me if there is  some logrotate files  avalable to put in /etc/logrotate.d  to  clean up these  log files.



Thanks  Richard VE2DJE


pop and jitter at the start of transmissions from DMR

Patrick Perdue
 

Hi:

This is nothing new, but I'm trying to figure out where it's coming from.

At the start of each DMR transmission, when listening on Allstar, there is a small pop sound. I've been on some other Allstar nodes that appear to be using a similar configuration, though I don't know for sure, which don't exhibit this behavior. This occurs regardless of whether or not I am using hardware or software AMBE vocoding.

Perhaps related, but maybe not, lately, at the start of DMR transmissions, there is sometimes severe jitter for about the first second of audio, then everything is fine for the rest of the transmission. This is a problem if someone quickly keys to give a callsign, then unkeys again. Perfectly understandable with a DMR radio, but these very short transmissions end up completely broken on the other side of Analog_Bridge.

This could very well be attributed to the Brandmeister server I'm using. I'll investigate this some more. It may even be an ASL issue. This bridge is off-site, connecting to a larger Allstar node on a VPS, but directly connecting to the private node hosting the bridge through iaxrpt suggests that the connection to my larger node is not the problem.

I'm using the latest versions of MMDVM_Bridge and Analog_Bridge from Github as of this writing. Analog_Bridge.ini is all defaults, with the exception of txTg and AGC setting ,which are not relevant to this set of problems as far as I can tell.

Raspberry Pi 2 running ASL and DVSwitch, ThumbDV via AMBEserver. I also tried using a direct serial connection to the dongle from A_B, which worked about the same as using AMBEserver as far as I could tell. I have also tried playing with the jitter parameter of MMDVM_Bridge, but ended up setting it back to 360.


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

mfj_986
 

Ok Joaquim
Thanks for all i will  install your last image 
73 Raymond 



Envoyé depuis mon smartphone.


-------- Message d'origine --------
De : EA5GVK Joaquin <ea5gvk@...>
Date : 22/04/2020 21:12 (GMT+01:00)
À : main@dvswitch.groups.io
Objet : Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Hi, Ray.

Version 8 was reported to be no longer active.  Since v9 is out. And it's not viable to keep both versions.  Also, v8 had an old DVSwitch.

You can't upgrade via OTA from v8 to v9. Since it's got deep changes.  It must record image v9.

Greetings.


El mié., 22 abr. 2020 19:54, mfj_986 <f6jig@...> escribió:
Hi Joaquim,
I put you a direct message concerning upgrade from DVlink V8 to V9 but i have no receive any answer.
Could you verified if you have it

73 Ray F6JIG


De: "EA5GVK Joaquin" <ea5gvk@...>
À: main@DVSwitch.groups.io
Envoyé: Mercredi 22 Avril 2020 19:21:17
Objet: Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Sorry, I didn't put the username and password to enter by SSH or VNC to the DVLINK V9 image.
ssh port 22
user: pi
pass: dvlink

For VNC port 5900
user: pi
pass: dvlink.

We are already working to convert the DVlink V9 image, in multilanguage (English, French, German, Portuguese and Italian). Thanks to our partners.
Greetings.


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

EA5GVK Joaquin
 

Caballero es no es el link de la nueva versión.
Miré en los últimos mensaje está el link. De Drive. Saludos

El mié., 22 abr. 2020 19:51, Tito Lopez <OBUSTOS01@...> escribió:
El Link para descargar esa imagen esta caido. Mega es una mierda, Venga Venga

On Thu, Dec 19, 2019 at 7:19 AM Peter Buckley via Groups.Io <SkierInAvon=Yahoo.com@groups.io> wrote:
Looking forward to the English version.
Downloaded the current (Spanish) version...ran it on the Pi.
Looks good, wish I knew more Spanish...
Thanks for your efforts - N0ECT - Pensacola.

On Thursday, September 12, 2019, 3:18:01 AM CDT, EA5GVK Joaquin <ea5gvk@...> wrote:


Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful


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

EA5GVK Joaquin
 

Hi, Ray.

Version 8 was reported to be no longer active.  Since v9 is out. And it's not viable to keep both versions.  Also, v8 had an old DVSwitch.

You can't upgrade via OTA from v8 to v9. Since it's got deep changes.  It must record image v9.

Greetings.


El mié., 22 abr. 2020 19:54, mfj_986 <f6jig@...> escribió:
Hi Joaquim,
I put you a direct message concerning upgrade from DVlink V8 to V9 but i have no receive any answer.
Could you verified if you have it

73 Ray F6JIG


De: "EA5GVK Joaquin" <ea5gvk@...>
À: main@DVSwitch.groups.io
Envoyé: Mercredi 22 Avril 2020 19:21:17
Objet: Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Sorry, I didn't put the username and password to enter by SSH or VNC to the DVLINK V9 image.
ssh port 22
user: pi
pass: dvlink

For VNC port 5900
user: pi
pass: dvlink.

We are already working to convert the DVlink V9 image, in multilanguage (English, French, German, Portuguese and Italian). Thanks to our partners.
Greetings.


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

mfj_986
 

Hi Joaquim,
I put you a direct message concerning upgrade from DVlink V8 to V9 but i have no receive any answer.
Could you verified if you have it

73 Ray F6JIG


De: "EA5GVK Joaquin" <ea5gvk@...>
À: main@DVSwitch.groups.io
Envoyé: Mercredi 22 Avril 2020 19:21:17
Objet: Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Sorry, I didn't put the username and password to enter by SSH or VNC to the DVLINK V9 image.
ssh port 22
user: pi
pass: dvlink

For VNC port 5900
user: pi
pass: dvlink.

We are already working to convert the DVlink V9 image, in multilanguage (English, French, German, Portuguese and Italian). Thanks to our partners.
Greetings.


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

Tito Lopez - YN1OB
 

El Link para descargar esa imagen esta caido. Mega es una mierda, Venga Venga


On Thu, Dec 19, 2019 at 7:19 AM Peter Buckley via Groups.Io <SkierInAvon=Yahoo.com@groups.io> wrote:
Looking forward to the English version.
Downloaded the current (Spanish) version...ran it on the Pi.
Looks good, wish I knew more Spanish...
Thanks for your efforts - N0ECT - Pensacola.

On Thursday, September 12, 2019, 3:18:01 AM CDT, EA5GVK Joaquin <ea5gvk@...> wrote:


Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful


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

EA5GVK Joaquin
 

Sorry, I didn't put the username and password to enter by SSH or VNC to the DVLINK V9 image.
ssh port 22
user: pi
pass: dvlink

For VNC port 5900
user: pi
pass: dvlink.

We are already working to convert the DVlink V9 image, in multilanguage (English, French, German, Portuguese and Italian). Thanks to our partners.
Greetings.


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

Steve N4IRS
 

A one to many configuration uses "like" modes. DMR, YSFn, NXDN are like modes since they are all AMBE. P25 and YSFw are like mode since they are both IMBE. D-Star stands alone. Any time you want to bridge to a different mode, you will need a transcoder,
We are working on example configs now.

Steve N4IRS

On 4/22/2020 11:33 AM, Jon KM8V wrote:
Is it possible to do P25 with this one to many as well? Is there a solid example?

Thanks & 73 de KM8V


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

Jon KM8V
 

Is it possible to do P25 with this one to many as well? Is there a solid example?

Thanks & 73 de KM8V


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

andrew delgado
 

Thanks a lot Eric, i was able to setup this,  73!


Re: Changelog

Mike Zingman - N4IRR
 

Patrick,

Thanks for the feedback.  
A great thanks go out to Moe AE4JY.  His code for AGC is awesome.  Check out the incredible discussion in this doc if you want to know more:
https://sourceforge.net/projects/cutesdr/files/doc/CuteSDR102.pdf/download


Re: Changelog

Patrick Perdue
 

I installed the new A_B yesterday morning, and enabled AGC. What a difference! Very smooth, and gets through analog a lot better with certain radios.

Thanks for the great work.


On 4/20/2020 1:26 PM, Mike Zingman - N4IRR wrote:

[Edited Message Follows]

We just posted some changes to the components, here is the. changelog.  Several of these changes will require significant doc for you to use so more to come:
AB:
  • Add AGC update including new settings
        • In AB.ini you can now set usrpAgc to adjust the threshold, slope and decay of the AGC
        • "Threshold" specifies AGC Knee in dB if AGC is active.( nominal range -160 to 0dB)

        • "Slope" specifies dB reduction in output at knee from maximum output level(nominal range 0 to 10dB) 
        • "Decay" is AGC decay value in milliseconds ( nominal range 20 to 5000 milliSeconds)

      • Add reloadDatabase remote command
        • This command (issued from dvswitch.sh) will cause AB to reload its internal database of users from disk.  This is normally done once every 24h
  • Add menu command (does not popup menu on mobile)
        • Like the "macro" menu for DVSM/pyUC, the menu command loads a transient menu into the client. 
        • Unlike the "macro" command (which now popups up immediately) the menu command just loads the menu
        • This command is most useful in conjunction with the OnRegister macro
  • Support USRP ping back (NAT keep alive)
        • Allow AB to respect a reverse keep alive from the mobile client for some NAT situations
  • Multiport transmit to support better bridge creation
        • This requires a full post all by itself, but the quick description is that a comma delimited list of transmit ports is now supported by AB and MB
        • The main purpose of this is to support better bridge architectures
        • Other uses include logging and streaming 
  • Allow macro variables with substitution
        • Again a single change that requires a full post.
        • Variables are now supported in the macro section of AB.ini
        • The variables are substituted by the shell before command. execution
        • The variables allow for much more concise command line strings
        • The variables make for much more readable macro definitions
        • Less dedicated scripts will. be needed as the macro definition can be defined in the section alone
        • Variables are exported to the environment and be used by client scripts for context
  • Better ini parsing error messages
        • When an error. is encountered in the parsing of the ini files, a better error message is. generated to. help diagnose the problem
  • Add warning if call not found in database (DSTAR)
        • DSTAR/ircddbGateway is picky and wants a valid callsign to operate.
        • This warning tells you that a call can not be found in the database that matches the DMR ID/CCS7 provided in "gatewayDmrId"
  • Add name lookup and metadata export
        • Metadata exported from the USRP interface now includes the first name and callsign of the DMR ID
        • The information comes from the database file loaded by "subscriberFile"
  • Change default transferRoot to /tmp
        • Change the default so that users who fail to set this parameter still function as expected
  • Make tune command able to invoke macros
        • The dvswitch.sh tune command/AB now supports invocation of AB macros using the same syntax (*) as DVSM/pyUC
dvswitch.sh
  • Inherit dir names from environment
        • Along with the variable support in AB, dvswitch.sh can now use AB_DIR, MMDVM_DIR and NODE_DIR from the environment
  • Use awk and not jq
        • On small machines (older Raspberry Pi) using jq would choke on large database files (DMR)
        • We moved bac to using awk which performs MUCH better and does not choke
  • Change ASL validation to a more visible node
      • Allow several commands to execute without ABInfo being present.
  • Add download and validation of user database files.
      • Support new AB commands reloadDatabase, AGC settings, etc
MB:
  • Change DMR networks on the fly.
        • The DMR tune command now support network selection.
        • The tune syntax. is PPPPP@AAAAA:###:OOOO
        • Where
          • PPPPP is the password for the DMR server
          • AAAA is the. FQDN (ip address) of the server
          • #### is the port that the DMR server is listening on
          • OOOO is any options that may be needed (XLX and DMR+)
  • Comma delimited set of transmit ports for each mode.
        • This will take a whole post to describe!  Maybe even two
        • The transmit ports in DVSWITCH.INI now take a comma delimited list of ports
        • These ports will allow you to set up single instance bridges with like mode partners with greater than two networks
      • NXDN remote command error silence (Just a bug fix)
      • DSTAR remote command was dropping into END_TX case. (just a bug fix)
  • Better error message for dvswitch.ini file parsing.
        • When an error. is found while parsing the ini files, a better error message is generated
  • DMR support for talker alias. DVSWITCH.ini has a new tag (TalkerAlias) in the DMR section.
        • This setting will be transmitted to the network on each transmission and can include your name, rig, location, etc
  • P25 Soft Id transmit and receive
        • Still a work in progress, but it is functional on decode
  • YSF split of narrow and wide TLV export to support transcode.
        • Wide mode YSF packets can now be sent to its own list of transmit ports using TXWidePort
        • This is independent of the narrow transmit ports
        • This allows you to transcode one side of YSF while keeping the other format free from conversion
  • YSF uses the latitude and longitude from MMDVM_Bridge.ini for the GPS location.
        • All transmissions will include GPS locations from the MB.ini file if non-zero
  • DSTAR slow data fix DSTAR ini file addition: message
  • Force MB to begin transmission if we did not see one (FCS bug)
  • Make MB return MMDVM and not _Unknown


Re: Changelog

ea7jcl@...
 

Wow! Good job. Thanks


Re: Changelog

HL5KY
 
Edited

Thank you for the great work.
 
Here I have some issue with the new update. After updating binaries, I can't transmit on DSTAR. Connecting DSTAR reflector seems to be ok, as I could hear the other's voice. Pressing PTT made it red but no real TX was carried out. And in about 5~10 seconds, it became unregistered.
 
Please find the attached files, a part of MMDVM_Bridge.log and the result of './dvswitch.sh show'. As you can see, after pressing PTT, it changes to DMR by itself.
 
Joe, HL5KY.
 
p.s. TG450 is a static TG.


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

Eric-K6KWB
 

You dont need Hblink in between. 

Here is the working sample config:
MB.ini
[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62033   >>>> make sure change this, it will interfere with your first MB instance if NOT change.
Password=passw0rd
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=0
GatewayAddress=ip or dns ysf reflector
GatewayPort=42000  >>>port YSFReflector

DVSwitch.ini

[DMR]
Address = 127.0.0.1             
TXPort = 35103                  
RXPort = 35100                  
Slot = 2               
[YSF]
Address = 127.0.0.1             
TXPort = 35100                  
RXPort = 35103                  
FallbackID = your id      
ExportTG = your TG               
Slot = 2 

Log in to BM self care and set the talk group.

73, Eric             


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

Steve N4IRS
 

The one to one bridge was the first method we came up with. What always bothered us was the complexity of a one to many bridge. Mike came up with a elegant "simple" way of making that happen. It is pretty much limited to "like modes" in this case, DMR, YSFn and NXDN which are all AMBE. Everything we do is to add power to the "partners" As we have said over and over "With great power, comes some complexity" (with apologies to Stan lee)

Steve, N4IRS

On 4/20/20 8:04 PM, andrew delgado via groups.io wrote:
wow thanks Steve, this is what i have in mind that i thought be working then i think that it will not work so i created a new instance but still no luck because of im mixing ports conflict :)

Thanks Steve looking forward to that kind of simple but rock setup!
Andrew
73!


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

andrew delgado
 

wow thanks Steve, this is what i have in mind that i thought be working then i think that it will not work so i created a new instance but still no luck because of im mixing ports conflict :)

Thanks Steve looking forward to that kind of simple but rock setup!
Andrew
73!


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

Steve N4IRS
 

Andrew,
I would suggest you wait a few days. We just updated to allow MB to bridge or connect to all like modes in a single instance of MB. We are putting a document in the next few days.
It will look something like this:

ASL <-> AB <-> MB <-> DMR
               | <--> YSF

(best I can do with ASCII graphics)

73, Steve N4IRS

On 4/20/20 7:40 PM, andrew delgado via groups.io wrote:
Hi all,

i was able to work successfully the both experiments ASL <> AB <> MB <> DMR using the link provided by steve n4irs, and also the YSFReflector <> MB <> DMR..

i have the idea of having a new instance but im mixing the ports or do i really need hblink3 in between? im setting this up on a single debian box.

Regards,
Andrew

3761 - 3780 of 9925