Topics

MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

Waldek SP2ONG
 

Hi,

Is it possible  connect mmdvm_bridgeto to  XLX reflector with the selected module just like DMRgateway?

73 Waldek

Steve KC1AWV
 

XLX modules use TGs in the 4000 range. 4001 for module A, 4002 for module B ... 4026 for module Z if you want to change it on the fly from a radio.

The other option is for MMDVM_Bridge to take the Module option in the stanza you use to connect to the XLX server.

Module=D

Will connect MMDVM_Bridge to XLX module D on connect. You can use my document as a guide.



On Wed, Oct 2, 2019 at 1:20 AM Waldek SP2ONG <sp2ong@...> wrote:
Hi,

Is it possible  connect mmdvm_bridgeto to  XLX reflector with the selected module just like DMRgateway?

73 Waldek



--
Steve Miller
KC1AWV

Waldek SP2ONG
 

Yes, I would like to use MMDVM_BRIDGE to connect the YSF Reflector bridge with the XLX reflector.

I don't want to use DMR Gateway, my idea is to reduce the number of applications that DV audio travels through for this reason I am asking about how to connect to XLX reflector on selected Module D use MMDVM_Bridge only

73 Waldek

Steve KC1AWV
 

> Steve, I wonder why you call the module id's TG's
> I do recognise XLX and openspot accept link id's as group contact protocol, whereas usually they would be private call.
You answered your own question there. Call it whatever you want, but placing a call to 4001-4026 will switch MB to the module you want.

> I think the question refers to using mmdvm_bridge without DMRGateway to connect to a XLX module. You document shows DMRGateway in the mix, however you did not show DMRgateway in your flow line in this thread   ?
That's an oversight on my part, it's been a while since I've touched that document. MB does not need DMRGateway to connect to an XLX server.

> AFAIK the Options= for mmdvm_bridge is only relevant to DMR+? if it worlks with XLX please let me know, I have not seen it work.
Well, that's the Options line. What I mentioned was the Module line. The Module line is what initially connects MB to an XLX module.

> A mmdvm_bridge config supporting XLX module link would be great.
That's what my document shows. I didn't say copy my document exactly, just use it as a guide.

[XLX Network]

Enabled=1

File=/var/lib/mmdvm/XLXHosts.txt

Port=62030

Password=passw0rd

ReloadTime=60

# Local=3351

Slot=1

TG=6

Base=64000

Startup=123

Relink=10

Debug=0

Module=D

On Wed, Oct 2, 2019 at 10:23 AM Adrian Fewster <vk4tux@...> wrote:

Steve, I wonder why you call the module id's TG's   ? The only numbers I call TG's have group call contacts and you can group qso using that group call contact.

I refer to reflector and XLX module id's as PC's which only use usually private call id's to link not qso on, thus negating then as a TG.

I do recognise XLX and openspot accept link id's as group contact protocol, whereas usually they would be private call.


I think the question refers to using mmdvm_bridge without DMRGateway to connect to a XLX module. You document shows DMRGateway in the mix,

however you did not show DMRgateway in your flow line in this thread   ?

AFAIK the Options= for mmdvm_bridge is only relevant to DMR+? if it worlks with XLX please let me know, I have not seen it work.

If the hblink peer style option for xlx could be adapted for mmdvm_bridge config that would be great, to make the flow simpler, with dmrgateway not required.

I have setup a script in the past to use two stages of (DMR side) analog bridge session, the first running 4004 to link , then killed and the second stage analog bridge using TG9 to then qso,

and that works well. however using DMRGateway works quite well here with my P25<>XLX bridge. A mmdvm_bridge config supporting XLX module link would be great.


Adrian ... vk4tux






On 2/10/19 11:10 pm, Steve KC1AWV wrote:
XLX modules use TGs in the 4000 range. 4001 for module A, 4002 for module B ... 4026 for module Z if you want to change it on the fly from a radio.

The other option is for MMDVM_Bridge to take the Module option in the stanza you use to connect to the XLX server.

Module=D

Will connect MMDVM_Bridge to XLX module D on connect. You can use my document as a guide.



On Wed, Oct 2, 2019 at 1:20 AM Waldek SP2ONG <sp2ong@...> wrote:
Hi,

Is it possible  connect mmdvm_bridgeto to  XLX reflector with the selected module just like DMRgateway?

73 Waldek


--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV

Steve KC1AWV
 

Wait, I see the confusion. Even I get a little mixed up here. I was reading the DMRGateway config. Oops.

Try this for MB:

[DMR Network]

Enable=1

Address=[xlx server ip]

Port=62030

Jitter=360

Local=62031

Password=passw0rd

Slot1=1

Slot2=1

Debug=0

Module=D


On Wed, Oct 2, 2019 at 10:35 AM Waldek SP2ONG <sp2ong@...> wrote:
Yes, I would like to use MMDVM_BRIDGE to connect the YSF Reflector bridge with the XLX reflector.

I don't want to use DMR Gateway, my idea is to reduce the number of applications that DV audio travels through for this reason I am asking about how to connect to XLX reflector on selected Module D use MMDVM_Bridge only

73 Waldek



--
Steve Miller
KC1AWV

Waldek SP2ONG
 

Hi Steve

Thank you for the info, my question was because on GitHub in MMDVM_Bridge.ini there is no example that you display

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/MMDVM_Bridge.ini

Steve KC1AWV
 

I think the config file on GitHub is a carry over from a previous version. From what I know, adding the Module line to the DMR Network stanza should connect you to a module when established.

There's no official documentation on GitHub covering all the possible iterations of use, but many of us are attempting to come up with some as time goes on.


On Wed, Oct 2, 2019 at 10:39 AM Waldek SP2ONG <sp2ong@...> wrote:
Hi Steve

Thank you for the info, my question was because on GitHub in MMDVM_Bridge.ini there is no example that you display

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/MMDVM_Bridge.ini



--
Steve Miller
KC1AWV

Waldek SP2ONG
 

Ok, maybe it would be good to update the .ini file because many of us download from github mmdvm_bridge

I will be try use mmdvm_bridge with your example, like in DMR Gateway configuration

73 Waldek

Steve N4IRS
 

Check the doc directory on GitHub.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Waldek SP2ONG <sp2ong@...>
Sent: Wednesday, October 2, 2019 10:49:06 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge
 
Ok, maybe it would be good to update the .ini file because many of us download from github mmdvm_bridge

I will be try use mmdvm_bridge with your example, like in DMR Gateway configuration

73 Waldek

Steve KC1AWV
 

> Then why do you quote DMRGateway config # for Module =  D ? 

That was my mistake, I was looking fast through my docs and made the mistake of quoting the wrong part.


On Wed, Oct 2, 2019 at 11:02 AM Adrian Fewster <vk4tux@...> wrote:


On 3/10/19 12:38 am, Steve KC1AWV wrote:
> Steve, I wonder why you call the module id's TG's
> I do recognise XLX and openspot accept link id's as group contact protocol, whereas usually they would be private call.
You answered your own question there. Call it whatever you want, but placing a call to 4001-4026 will switch MB to the module you want.
Technically 4001 - 4026 are not TG's , however i get that you dont care what you call them.

> I think the question refers to using mmdvm_bridge without DMRGateway to connect to a XLX module. You document shows DMRGateway in the mix, however you did not show DMRgateway in your flow line in this thread   ?
That's an oversight on my part, it's been a while since I've touched that document. MB does not need DMRGateway to connect to an XLX server. <$

I understand that, however module connect is needed, after the server connect from MMDVM_Bridge direct.


$ Then why do you quote DMRGateway config # for Module =  D ?  How does mmdvm_bridge connect to a module   ?



> AFAIK the Options= for mmdvm_bridge is only relevant to DMR+? if it worlks with XLX please let me know, I have not seen it work.
Well, that's the Options line. What I mentioned was the Module line. The Module line is what initially connects MB to an XLX module.

> A mmdvm_bridge config supporting XLX module link would be great.
That's what my document shows. I didn't say copy my document exactly, just use it as a guide.

[XLX Network] << #

Enabled=1

File=/var/lib/mmdvm/XLXHosts.txt

Port=62030

Password=passw0rd

ReloadTime=60

# Local=3351

Slot=1

TG=6

Base=64000

Startup=123

Relink=10

Debug=0

Module=D



--
Steve Miller
KC1AWV

Steve N4IRS
 

On 10/2/2019 10:49 AM, Waldek SP2ONG wrote:
Ok, maybe it would be good to update the .ini file because many of us download from github mmdvm_bridge

I will be try use mmdvm_bridge with your example, like in DMR Gateway configuration

73 Waldek

Waldek SP2ONG
 


> Options=StartRef=4004  << will this work with XLX from  MMDVM_BRIDGE dmr network config to link module D ? This would be great if it works, if not could it be enabled ?


The documnet:

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

it is for DMRPlus not for XLX Network


Steve N4IRS
 

Has anyone tried Options=StartRef=4004 in the [DMR Network] stanza?

On 10/2/2019 2:25 PM, Adrian Fewster wrote:

Yes that was my point with the test example question below, however XLX is mentioned on the

commit for some reason, being a bridge of course we don't need a choice of networks.

Hopefully some talented coder can do for MMDVM_BRIDGE  as was done for HBlink peers re XLX module option.



On 3/10/19 2:45 am, Waldek SP2ONG wrote:

> Options=StartRef=4004  << will this work with XLX from  MMDVM_BRIDGE dmr network config to link module D ? This would be great if it works, if not could it be enabled ?


The documnet:

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

it is for DMRPlus not for XLX Network



Steve KC1AWV
 

Sorry Steve, I can feel the frustration. I have tested with the Options line, and nothing happens on the XLX side.

root@test:/opt/MMDVM_Bridge_2# ./MMDVM_Bridge MMDVM_Bridge.ini
I: 2019-10-02 18:50:28.154 MMDVM_Bridge:
I: 2019-10-02 18:50:28.155 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-10-02 18:50:28.155 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-10-02 18:50:28.155 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-10-02 18:50:28.155 This software is for use on amateur radio networks only,
I: 2019-10-02 18:50:28.155 it is to be used for educational purposes only. Its use on
I: 2019-10-02 18:50:28.155 commercial networks is strictly prohibited.
I: 2019-10-02 18:50:28.155 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-10-02 18:50:28.155 MMDVM_Bridge-20180423 is starting
M: 2019-10-02 18:50:28.155 Built 10:47:32 Jun 24 2019 (GitID #30648ec)
I: 2019-10-02 18:50:28.155 General Parameters
I: 2019-10-02 18:50:28.155     Callsign: KC1AWV
I: 2019-10-02 18:50:28.155     Id: 3122790
I: 2019-10-02 18:50:28.155     Duplex: no
I: 2019-10-02 18:50:28.155     Timeout: 180s
I: 2019-10-02 18:50:28.155     D-Star: disabled
I: 2019-10-02 18:50:28.155     DMR: enabled
I: 2019-10-02 18:50:28.155     YSF: disabled
I: 2019-10-02 18:50:28.155     P25: disabled
I: 2019-10-02 18:50:28.155     NXDN: disabled
I: 2019-10-02 18:50:28.155 Modem Parameters
I: 2019-10-02 18:50:28.155     Port: /dev/null
I: 2019-10-02 18:50:28.156     RX Invert: no
I: 2019-10-02 18:50:28.156     TX Invert: no
I: 2019-10-02 18:50:28.156     PTT Invert: no
I: 2019-10-02 18:50:28.156     TX Delay: 100ms
I: 2019-10-02 18:50:28.156     RX Offset: 0Hz
I: 2019-10-02 18:50:28.156     TX Offset: 0Hz
I: 2019-10-02 18:50:28.156     RX DC Offset: 0
I: 2019-10-02 18:50:28.156     TX DC Offset: 0
I: 2019-10-02 18:50:28.156     RF Level: 100.0%
I: 2019-10-02 18:50:28.156     DMR Delay: 0 (0.0ms)
I: 2019-10-02 18:50:28.156     RX Level: 50.0%
I: 2019-10-02 18:50:28.156     CW Id TX Level: 50.0%
I: 2019-10-02 18:50:28.156     D-Star TX Level: 50.0%
I: 2019-10-02 18:50:28.156     DMR TX Level: 50.0%
I: 2019-10-02 18:50:28.156     YSF TX Level: 50.0%
I: 2019-10-02 18:50:28.156     P25 TX Level: 50.0%
I: 2019-10-02 18:50:28.156     NXDN TX Level: 50.0%
I: 2019-10-02 18:50:28.156     RX Frequency: 0Hz (0Hz)
I: 2019-10-02 18:50:28.156     TX Frequency: 0Hz (0Hz)
M: 2019-10-02 18:50:28.156 Opening the MMDVM
I: 2019-10-02 18:50:28.156 Display Parameters
I: 2019-10-02 18:50:28.156     Type:
I: 2019-10-02 18:50:28.156 DMR Network Parameters
I: 2019-10-02 18:50:28.156     Address: 173.208.200.180
I: 2019-10-02 18:50:28.156     Port: 62030
I: 2019-10-02 18:50:28.156     Local: 62331
I: 2019-10-02 18:50:28.157     Jitter: 360ms
I: 2019-10-02 18:50:28.157     Slot 1: enabled
I: 2019-10-02 18:50:28.157     Slot 2: enabled
I: 2019-10-02 18:50:28.157     Mode Hang: 3s
I: 2019-10-02 18:50:28.157     Options: StartRef=4004
I: 2019-10-02 18:50:28.157 Info Parameters
I: 2019-10-02 18:50:28.157     Callsign: KC1AWV
I: 2019-10-02 18:50:28.157     RX Frequency: 0Hz
I: 2019-10-02 18:50:28.157     TX Frequency: 0Hz
I: 2019-10-02 18:50:28.157     Power: 1W
I: 2019-10-02 18:50:28.157     Latitude: 41.733299deg N
I: 2019-10-02 18:50:28.157     Longitude: -50.399899deg E
I: 2019-10-02 18:50:28.157     Height: 0m
I: 2019-10-02 18:50:28.157     Location: "Test Bridge"
I: 2019-10-02 18:50:28.157     Description: "MMDVM_Bridge"
I: 2019-10-02 18:50:28.157     URL: "https://www.erdn.net"
M: 2019-10-02 18:50:28.157 DMR, Opening DMR Network
I: 2019-10-02 18:50:28.157 RSSI
I: 2019-10-02 18:50:28.157     Mapping File: RSSI.dat
W: 2019-10-02 18:50:28.157 Cannot open the RSSI data file - RSSI.dat
I: 2019-10-02 18:50:28.157 DMR Id Lookups
I: 2019-10-02 18:50:28.157     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-10-02 18:50:28.157     Reload: 24 hours
I: 2019-10-02 18:50:28.259 Loaded 145028 Ids to the DMR callsign lookup table
I: 2019-10-02 18:50:28.259 DMR RF Parameters
I: 2019-10-02 18:50:28.259     Id: 3122790
I: 2019-10-02 18:50:28.259     Color Code: 1
I: 2019-10-02 18:50:28.259     Self Only: no
I: 2019-10-02 18:50:28.259     Embedded LC Only: yes
I: 2019-10-02 18:50:28.259     Dump Talker Alias Data: no
I: 2019-10-02 18:50:28.259     Prefixes: 0
I: 2019-10-02 18:50:28.259     Call Hang: 3s
I: 2019-10-02 18:50:28.259     TX Hang: 3s
I: 2019-10-02 18:50:28.259     Mode Hang: 10s
M: 2019-10-02 18:50:28.259 DMR, Opening INI file: DVSwitch.ini
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] TXPort -> 33100
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] RXPort -> 33103
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] Slot -> 2
M: 2019-10-02 18:50:28.260 DMR, Transmitting on 127.0.0.1:33100 and listening on port 33103.  Result = 1
M: 2019-10-02 18:50:28.260 MMDVM_Bridge-20180423 is running
I: 2019-10-02 18:50:28.260 Started the DMR Id lookup reload thread
D: 2019-10-02 18:50:38.276 DMR, Sending authorisation
D: 2019-10-02 18:50:38.291 DMR, Sending configuration
D: 2019-10-02 18:50:38.306 DMR, Sending options
M: 2019-10-02 18:50:38.322 DMR, Logged into the master successfully

Once logged in, XLX does not move the client to the requested module.

I think the reason I am confused was that a few months ago, I switched to hblink - which can take a XLX module in the 4000s.

On Wed, Oct 2, 2019 at 2:36 PM Steve N4IRS <szingman@...> wrote:
Has anyone tried Options=StartRef=4004 in the [DMR Network] stanza?

On 10/2/2019 2:25 PM, Adrian Fewster wrote:

Yes that was my point with the test example question below, however XLX is mentioned on the

commit for some reason, being a bridge of course we don't need a choice of networks.

Hopefully some talented coder can do for MMDVM_BRIDGE  as was done for HBlink peers re XLX module option.



On 3/10/19 2:45 am, Waldek SP2ONG wrote:

> Options=StartRef=4004  << will this work with XLX from  MMDVM_BRIDGE dmr network config to link module D ? This would be great if it works, if not could it be enabled ?


The documnet:

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

it is for DMRPlus not for XLX Network





--
Steve Miller
KC1AWV

Steve N4IRS
 

I could have sworn we tested this. I will look when I get a chance. My time is very limited because:
1: I am moving after 22 years to a temporary apartment. (Until the new house is ready)
2: I am replacing 2 fiber switches in my SAN
3: I am upgrading enterprise to O365. (upgrade?)



On 10/2/2019 2:58 PM, Steve KC1AWV wrote:
Sorry Steve, I can feel the frustration. I have tested with the Options line, and nothing happens on the XLX side.

root@test:/opt/MMDVM_Bridge_2# ./MMDVM_Bridge MMDVM_Bridge.ini
I: 2019-10-02 18:50:28.154 MMDVM_Bridge:
I: 2019-10-02 18:50:28.155 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-10-02 18:50:28.155 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-10-02 18:50:28.155 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-10-02 18:50:28.155 This software is for use on amateur radio networks only,
I: 2019-10-02 18:50:28.155 it is to be used for educational purposes only. Its use on
I: 2019-10-02 18:50:28.155 commercial networks is strictly prohibited.
I: 2019-10-02 18:50:28.155 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-10-02 18:50:28.155 MMDVM_Bridge-20180423 is starting
M: 2019-10-02 18:50:28.155 Built 10:47:32 Jun 24 2019 (GitID #30648ec)
I: 2019-10-02 18:50:28.155 General Parameters
I: 2019-10-02 18:50:28.155     Callsign: KC1AWV
I: 2019-10-02 18:50:28.155     Id: 3122790
I: 2019-10-02 18:50:28.155     Duplex: no
I: 2019-10-02 18:50:28.155     Timeout: 180s
I: 2019-10-02 18:50:28.155     D-Star: disabled
I: 2019-10-02 18:50:28.155     DMR: enabled
I: 2019-10-02 18:50:28.155     YSF: disabled
I: 2019-10-02 18:50:28.155     P25: disabled
I: 2019-10-02 18:50:28.155     NXDN: disabled
I: 2019-10-02 18:50:28.155 Modem Parameters
I: 2019-10-02 18:50:28.155     Port: /dev/null
I: 2019-10-02 18:50:28.156     RX Invert: no
I: 2019-10-02 18:50:28.156     TX Invert: no
I: 2019-10-02 18:50:28.156     PTT Invert: no
I: 2019-10-02 18:50:28.156     TX Delay: 100ms
I: 2019-10-02 18:50:28.156     RX Offset: 0Hz
I: 2019-10-02 18:50:28.156     TX Offset: 0Hz
I: 2019-10-02 18:50:28.156     RX DC Offset: 0
I: 2019-10-02 18:50:28.156     TX DC Offset: 0
I: 2019-10-02 18:50:28.156     RF Level: 100.0%
I: 2019-10-02 18:50:28.156     DMR Delay: 0 (0.0ms)
I: 2019-10-02 18:50:28.156     RX Level: 50.0%
I: 2019-10-02 18:50:28.156     CW Id TX Level: 50.0%
I: 2019-10-02 18:50:28.156     D-Star TX Level: 50.0%
I: 2019-10-02 18:50:28.156     DMR TX Level: 50.0%
I: 2019-10-02 18:50:28.156     YSF TX Level: 50.0%
I: 2019-10-02 18:50:28.156     P25 TX Level: 50.0%
I: 2019-10-02 18:50:28.156     NXDN TX Level: 50.0%
I: 2019-10-02 18:50:28.156     RX Frequency: 0Hz (0Hz)
I: 2019-10-02 18:50:28.156     TX Frequency: 0Hz (0Hz)
M: 2019-10-02 18:50:28.156 Opening the MMDVM
I: 2019-10-02 18:50:28.156 Display Parameters
I: 2019-10-02 18:50:28.156     Type:
I: 2019-10-02 18:50:28.156 DMR Network Parameters
I: 2019-10-02 18:50:28.156     Address: 173.208.200.180
I: 2019-10-02 18:50:28.156     Port: 62030
I: 2019-10-02 18:50:28.156     Local: 62331
I: 2019-10-02 18:50:28.157     Jitter: 360ms
I: 2019-10-02 18:50:28.157     Slot 1: enabled
I: 2019-10-02 18:50:28.157     Slot 2: enabled
I: 2019-10-02 18:50:28.157     Mode Hang: 3s
I: 2019-10-02 18:50:28.157     Options: StartRef=4004
I: 2019-10-02 18:50:28.157 Info Parameters
I: 2019-10-02 18:50:28.157     Callsign: KC1AWV
I: 2019-10-02 18:50:28.157     RX Frequency: 0Hz
I: 2019-10-02 18:50:28.157     TX Frequency: 0Hz
I: 2019-10-02 18:50:28.157     Power: 1W
I: 2019-10-02 18:50:28.157     Latitude: 41.733299deg N
I: 2019-10-02 18:50:28.157     Longitude: -50.399899deg E
I: 2019-10-02 18:50:28.157     Height: 0m
I: 2019-10-02 18:50:28.157     Location: "Test Bridge"
I: 2019-10-02 18:50:28.157     Description: "MMDVM_Bridge"
I: 2019-10-02 18:50:28.157     URL: "https://www.erdn.net"
M: 2019-10-02 18:50:28.157 DMR, Opening DMR Network
I: 2019-10-02 18:50:28.157 RSSI
I: 2019-10-02 18:50:28.157     Mapping File: RSSI.dat
W: 2019-10-02 18:50:28.157 Cannot open the RSSI data file - RSSI.dat
I: 2019-10-02 18:50:28.157 DMR Id Lookups
I: 2019-10-02 18:50:28.157     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-10-02 18:50:28.157     Reload: 24 hours
I: 2019-10-02 18:50:28.259 Loaded 145028 Ids to the DMR callsign lookup table
I: 2019-10-02 18:50:28.259 DMR RF Parameters
I: 2019-10-02 18:50:28.259     Id: 3122790
I: 2019-10-02 18:50:28.259     Color Code: 1
I: 2019-10-02 18:50:28.259     Self Only: no
I: 2019-10-02 18:50:28.259     Embedded LC Only: yes
I: 2019-10-02 18:50:28.259     Dump Talker Alias Data: no
I: 2019-10-02 18:50:28.259     Prefixes: 0
I: 2019-10-02 18:50:28.259     Call Hang: 3s
I: 2019-10-02 18:50:28.259     TX Hang: 3s
I: 2019-10-02 18:50:28.259     Mode Hang: 10s
M: 2019-10-02 18:50:28.259 DMR, Opening INI file: DVSwitch.ini
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] TXPort -> 33100
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] RXPort -> 33103
M: 2019-10-02 18:50:28.260 DMR, Setting [DMR] Slot -> 2
M: 2019-10-02 18:50:28.260 DMR, Transmitting on 127.0.0.1:33100 and listening on port 33103.  Result = 1
M: 2019-10-02 18:50:28.260 MMDVM_Bridge-20180423 is running
I: 2019-10-02 18:50:28.260 Started the DMR Id lookup reload thread
D: 2019-10-02 18:50:38.276 DMR, Sending authorisation
D: 2019-10-02 18:50:38.291 DMR, Sending configuration
D: 2019-10-02 18:50:38.306 DMR, Sending options
M: 2019-10-02 18:50:38.322 DMR, Logged into the master successfully

Once logged in, XLX does not move the client to the requested module.

I think the reason I am confused was that a few months ago, I switched to hblink - which can take a XLX module in the 4000s.

On Wed, Oct 2, 2019 at 2:36 PM Steve N4IRS <szingman@...> wrote:
Has anyone tried Options=StartRef=4004 in the [DMR Network] stanza?

On 10/2/2019 2:25 PM, Adrian Fewster wrote:

Yes that was my point with the test example question below, however XLX is mentioned on the

commit for some reason, being a bridge of course we don't need a choice of networks.

Hopefully some talented coder can do for MMDVM_BRIDGE  as was done for HBlink peers re XLX module option.



On 3/10/19 2:45 am, Waldek SP2ONG wrote:

> Options=StartRef=4004  << will this work with XLX from  MMDVM_BRIDGE dmr network config to link module D ? This would be great if it works, if not could it be enabled ?


The documnet:

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

it is for DMRPlus not for XLX Network





--
Steve Miller
KC1AWV

Waldek SP2ONG
 

Steve KC1AWV

Did you try connect to XLX and slected Modlue via MMDVM_Bridge with your example  ?

[XLX Network]

Enabled=1

File=/var/lib/mmdvm/XLXHosts.txt

Port=62030

Password=passw0rd

ReloadTime=60

# Local=3351

Slot=1

TG=6

Base=64000

Startup=123

Relink=10

Debug=0

Module=D

Steve KC1AWV
 

Not with that configuration, the one you pasted is for DMRGateway. This is what I used for MB:

[DMR Network]
Enable=1
Address=[ip address of xlx server]
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=StartRef=4004
Slot1=1
Slot2=1
Debug=1

On Wed, Oct 2, 2019 at 3:16 PM Waldek SP2ONG <sp2ong@...> wrote:
Steve KC1AWV

Did you try connect to XLX and slected Modlue via MMDVM_Bridge with your example  ?

[XLX Network]

Enabled=1

File=/var/lib/mmdvm/XLXHosts.txt

Port=62030

Password=passw0rd

ReloadTime=60

# Local=3351

Slot=1

TG=6

Base=64000

Startup=123

Relink=10

Debug=0

Module=D



--
Steve Miller
KC1AWV

Waldek SP2ONG
 

Hi

On Wed, Oct 2, 2019 at 12:35 PM, Steve KC1AWV wrote:
Options=StartRef=4004
But if I understood from your previous posts now the option StarRef = 4004 does not work in MMDVM_Bridge to transfer for example to module D ???

Mike Zingman - N4IRR
 

Correct syntax for MB is

Options
=XLX:4009

Steve N4IRS
 

On 10/3/2019 12:11 PM, Mike Zingman - N4IRR wrote:
Correct syntax for MB is

Options
=XLX:4009