Date   

Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Steve N4IRS
 

I was wondering if you could connect to a "real" DCS reflector. I wanted to talk XLX out of the mix for the test.

On 5/31/20 12:02 PM, Matthew 2E0SIP wrote:

Ok, is the Talk Group significant? I tried connecting to another XLX server via DCS but same issue, I appear as connected, I see a stream of packets to the server when I Tx, but nothing appears on the XLX Server. I can receive DStar transmissions on the DMR side without any issues.


Does anyone have a known good Analog_Bridge.ini, MMDVM_Bridge.ini and DVSwitch.ini for a link to XLX / DStar ?  

And for what it's worth, I know in theory I could connect directly to XLX with DMR, but this server doesn't have any transcoding capability at present.

Cheers



Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Matthew 2E0SIP
 

Ok, is the Talk Group significant? I tried connecting to another XLX server via DCS but same issue, I appear as connected, I see a stream of packets to the server when I Tx, but nothing appears on the XLX Server. I can receive DStar transmissions on the DMR side without any issues.


Does anyone have a known good Analog_Bridge.ini, MMDVM_Bridge.ini and DVSwitch.ini for a link to XLX / DStar ?  

And for what it's worth, I know in theory I could connect directly to XLX with DMR, but this server doesn't have any transcoding capability at present.

Cheers


Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Steve N4IRS
 

As far as IDs go, I don't THINK there is any validation for XLX. the DMR instance of AB will try to lookup a DMRID to callsign and pass that on through the bridge. Check the D-Star MB log and make sure the callsigns are being sent on to XLX.

On 5/31/20 11:43 AM, Matthew 2E0SIP wrote:
Hi Steve,

Good Idea, I'll give it a go. 

I don't see much in the ircddblog, other than Gateway and User updates. This seems to be only relevant line:

M: 2020-05-31 15:32:43: From RF
M: 2020-05-31 15:32:43: 0000:  32 36 42 30 30 43 33 20 20                         *26B00C3  *

A few things spring to mind, is there any validation on the IDs used? They're registered as DMR IDs but I don't know if something special is required for D-Star.
 
Secondly, for the DStar instance of Analog_Bridge, does the following work? Should I be using a specific TG etc to get into XLX? 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 2348479                  ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 234847911                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 4003                          ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

Thanks
Matthew


Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Matthew 2E0SIP
 

Hi Steve,

Good Idea, I'll give it a go. 

I don't see much in the ircddblog, other than Gateway and User updates. This seems to be only relevant line:

M: 2020-05-31 15:32:43: From RF
M: 2020-05-31 15:32:43: 0000:  32 36 42 30 30 43 33 20 20                         *26B00C3  *

A few things spring to mind, is there any validation on the IDs used? They're registered as DMR IDs but I don't know if something special is required for D-Star.
 
Secondly, for the DStar instance of Analog_Bridge, does the following work? Should I be using a specific TG etc to get into XLX? 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 2348479                  ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 234847911                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 4003                          ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

Thanks
Matthew


Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Steve N4IRS
 

Matt,
Have you tried connecting to a DCS reflector as a test? Anything in the ircDDBGateway log?

Steve

On 5/31/20 10:05 AM, Matthew 2E0SIP wrote:

[Edited Message Follows]

Thanks both! I think it was just a case of not seeing the logs, but it was working in the background.
 
Mike - I've updated the Modules to match.

I've got a bit further and I'm now running :
 
DMR <-> MMDVM_Bridge <-> Analog Bridge <-> Analog Bridge <-> MMDVM_Bridge <-> ircddbgateway <-> DStar XLX

I can DStar to DMR is working, but DMR to DStar is not. Transcoding seems to be working, both Analog Bridge instances are showing Ptt Up etc, and AMBE frames are reaching both dongles.

I see packets get as far as XLX, but nothing is showing in the Dashboard. Am I missing something? - ircddbgateway is showing as logged in on the dashboard.
 
Thanks again
 
Edited: ( I can actually see packets reaching XLX, but nothing on the Dash, and DStar users don't receive anything) 


Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Matthew 2E0SIP
 
Edited

Thanks both! I think it was just a case of not seeing the logs, but it was working in the background.
 
Mike - I've updated the Modules to match.

I've got a bit further and I'm now running :
 
DMR <-> MMDVM_Bridge <-> Analog Bridge <-> Analog Bridge <-> MMDVM_Bridge <-> ircddbgateway <-> DStar XLX

I can DStar to DMR is working, but DMR to DStar is not. Transcoding seems to be working, both Analog Bridge instances are showing Ptt Up etc, and AMBE frames are reaching both dongles.

I see packets get as far as XLX, but nothing is showing in the Dashboard. Am I missing something? - ircddbgateway is showing as logged in on the dashboard.
 
Thanks again
 
Edited: ( I can actually see packets reaching XLX, but nothing on the Dash, and DStar users don't receive anything) 


attenuating USRP gain post-AGC processing

Patrick Perdue
 

Hi:

I have a bridge set up using AGC with the following parameters:

usrpAudio = AUDIO_USE_AGC                 ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 0.50                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAgc = -19,10,200                    ; Set the agc threshold (db), slope (db) and decay (ms)
This sounds great, but I want to reduce the output of the processed audio by just a couple DB going into ASL. It doesn't appear that the usrpGain value does anything when set to usrpAudio = AUDIO_USE_AGC, which, I believe, is expected behavior.

Yes, I could raise the threshold to something closer to 0, but I want the processing as-is, just with a trim on the output. Actually, I would like to possibly make the processing even more aggressive (lower threshold and longer release) to comp for some lower levels and keep higher ones in check), but then reduce that output by, say, 3 to 6 db coming into ASL's USRP driver. Is this at all possible with one instance of A_B, or can I use a second instance of A_B just as an attenuater? With older versions of A_B, this could be done, but the AGC algorithm was practically useless.


Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Mike Zingman - N4IRR
 

Make your Modules match. You have “C” and “G”


Re: MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Steve N4IRS
 

Matthew,
What I see here depends on which of the two components is start first. If I start MB then ircDDBGateway I see indication in the MB log when ircDDBGateway initializes.

MB:
M: 2020-05-31 11:05:55.799 D-Star, received network header from N4IRS   /INFO to CQCQCQ 
M: 2020-05-31 11:05:58.284 D-Star, received network end of transmission, 2.5 seconds, 0% packet loss, BER: 0.0%

After I issue a remotecontrold command this is logged in MB:

M: 2020-05-31 11:16:06.641 D-Star link status set to "Linking to REF078 B "
M: 2020-05-31 11:16:06.678 D-Star link status set to "Linked to REF078 B  "

If ircddbgatewayd is run first. I see no indication in the MB log. When I issue a remotecontrold command:

M: 2020-05-31 11:20:39.219 D-Star link status set to "Linking to REF078 B "
M: 2020-05-31 11:20:39.261 D-Star link status set to "Linked to REF078 B  "
M: 2020-05-31 11:20:41.272 D-Star, received network header from N4IRS   /INFO to CQCQCQ   via REF078 B
M: 2020-05-31 11:20:48.317 D-Star, received network end of transmission, 7.1 seconds, 0% packet loss, BER: 0.0%


I would also turn on debug in the [D-Star Network] stanza.

hope this helps,
Steve N4IRS


On 5/31/20 6:09 AM, Matthew 2E0SIP wrote:

Hi All,

I've recently been playing with the DVSwitch software again after a bit a hiatus . The pre-compiled packages are a dream so thanks to everyone involved. 

I am in the process of setting up a D-Star to DMR bridge. I've got ircddbgateway up and working, but when I start MMDVM_Bridge I don't see any notification in the logs to indicate it's connected to ircddbgateway, and if I run a packet capture I only see very occasional packets going to port 20010 and nothing back. With MMDVMHost and ircddbgateway on pi-star with a similar configuration I get the more affirmative log line `D-Star link status set to "Linking to DCS061"`


Am I missing something?

Thanks, Matthew 2E0SIP

MMDMV_Bridge.ini

[General]
Callsign=2E0SIP
Id=234326505
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_DStar

[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=1
Module=C

[DMR]
Enable=0
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

[D-Star Network]
Enable=1
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=1

[DMR Network]
Enable=0
Jitter=360
Local=62032
Address=87.117.229.173
Password="passw0rd"
Port=62031

# 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=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
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


/etc/ircddbgateay

gatewayType=1
gatewayCallsign=M0OUK
gatewayAddress=0.0.0.0
icomAddress=172.16.0.20
icomPort=20000
hbAddress=127.0.0.1
hbPort=20010
latitude=50.00
longitude=-3.00
description1=Watford, IO91
description2=United Kingdom
url=http://www.mw0mwz.co.uk/pi-star/
repeaterCall1=M0OUK
repeaterBand1=G
repeaterType1=0
repeaterAddress1=127.0.0.1
repeaterPort1=20011
reflector1=DCS061 C
atStartup1=1
reconnect1=0
frequency1=438.80000
offset1=0.0000
rangeKms1=1.000
latitude1=50.00
longitude1=-3.00
agl1=3.000
description1_1=Watford, IO91
description1_2=United Kingdom
url1=
band1_1=0
band1_2=0
band1_3=0
repeaterCall2=
repeaterBand2=
repeaterType2=0
repeaterAddress2=127.0.0.1
repeaterPort2=20012
reflector2=
atStartup2=0
reconnect2=0
frequency2=0.00000
offset2=0.0000
rangeKms2=0.000
latitude2=0.000000
longitude2=0.000000
agl2=0.000
description2_1=
description2_2=
url2=
band2_1=0
band2_2=0
band2_3=0
repeaterCall3=
repeaterBand3=
repeaterType3=0
repeaterAddress3=127.0.0.1
repeaterPort3=20013
reflector3=
atStartup3=0
reconnect3=0
frequency3=0.00000
offset3=0.0000
rangeKms3=0.000
latitude3=0.000000
longitude3=0.000000
agl3=0.000
description3_1=
description3_2=
url3=
band3_1=0
band3_2=0
band3_3=0
repeaterCall4=
repeaterBand4=
repeaterType4=0
repeaterAddress4=127.0.0.1
repeaterPort4=20014
reflector4=
atStartup4=0
reconnect4=0
frequency4=0.00000
offset4=0.0000
rangeKms4=0.000
latitude4=0.000000
longitude4=0.000000
agl4=0.000
description4_1=
description4_2=
url4=
band4_1=0
band4_2=0
band4_3=0
ircddbEnabled=1
ircddbHostname=rr.openquad.net
ircddbUsername=M0OUK
ircddbPassword=
ircddbEnabled2=0
ircddbHostname2=group1-irc.ircddb.net
ircddbUsername2=
ircddbPassword2=
ircddbEnabled3=0
ircddbHostname3=
ircddbUsername3=
ircddbPassword3=
ircddbEnabled4=0
ircddbHostname4=
ircddbUsername4=
ircddbPassword4=
aprsEnabled=1
aprsPassword=14500
aprsHostname=euro.aprs2.net
aprsPort=14580
dextraEnabled=1
dextraMaxDongles=5
dplusEnabled=1
dplusMaxDongles=5
dplusLogin=M0OUK
dcsEnabled=1
ccsEnabled=1
ccsHost=CCS706
xlxEnabled=0
xlxOverrideLocal=0
xlxHostsFileUrl=
starNetBand1=B
starNetCallsign1=
starNetLogoff1=
starNetInfo1=
starNetPermanent1=
starNetUserTimeout1=
starNetGroupTimeout1=
starNetCallsignSwitch1=1
starNetTXMsgSwitch1=1
starNetReflector1=
starNetBand2=B
starNetCallsign2=
starNetLogoff2=
starNetInfo2=
starNetPermanent2=
starNetUserTimeout2=
starNetGroupTimeout2=
starNetCallsignSwitch2=1
starNetTXMsgSwitch2=1
starNetReflector2=
starNetBand3=A
starNetCallsign3=
starNetLogoff3=
starNetInfo3=
starNetPermanent3=
starNetUserTimeout3=
starNetGroupTimeout3=
starNetCallsignSwitch3=0
starNetTXMsgSwitch3=1
starNetReflector3=
starNetBand4=A
starNetCallsign4=
starNetLogoff4=
starNetInfo4=
starNetPermanent4=
starNetUserTimeout4=
starNetGroupTimeout4=
starNetCallsignSwitch4=0
starNetTXMsgSwitch4=1
starNetReflector4=
starNetBand5=A
starNetCallsign5=
starNetLogoff5=
starNetInfo5=
starNetPermanent5=
starNetUserTimeout5=
starNetGroupTimeout5=
starNetCallsignSwitch5=0
starNetTXMsgSwitch5=1
starNetReflector5=
remoteEnabled=1
remotePassword=raspberry
remotePort=10022
language=0
infoEnabled=1
echoEnabled=1
logEnabled=1
dratsEnabled=1
dtmfEnabled=1
mobileGPSEnabled=0
mobileGPSAddress=127.0.0.1
mobileGPSPort=7834
windowX=-1
windowY=-1


MMDVM_Bridge doesn't appear to be connecting to ircddbgateway

Matthew 2E0SIP
 

Hi All,

I've recently been playing with the DVSwitch software again after a bit a hiatus . The pre-compiled packages are a dream so thanks to everyone involved. 

I am in the process of setting up a D-Star to DMR bridge. I've got ircddbgateway up and working, but when I start MMDVM_Bridge I don't see any notification in the logs to indicate it's connected to ircddbgateway, and if I run a packet capture I only see very occasional packets going to port 20010 and nothing back. With MMDVMHost and ircddbgateway on pi-star with a similar configuration I get the more affirmative log line `D-Star link status set to "Linking to DCS061"`


Am I missing something?

Thanks, Matthew 2E0SIP

MMDMV_Bridge.ini

[General]
Callsign=2E0SIP
Id=234326505
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_DStar

[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=1
Module=C

[DMR]
Enable=0
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

[D-Star Network]
Enable=1
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=1

[DMR Network]
Enable=0
Jitter=360
Local=62032
Address=87.117.229.173
Password="passw0rd"
Port=62031

# 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=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
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


/etc/ircddbgateay

gatewayType=1
gatewayCallsign=M0OUK
gatewayAddress=0.0.0.0
icomAddress=172.16.0.20
icomPort=20000
hbAddress=127.0.0.1
hbPort=20010
latitude=50.00
longitude=-3.00
description1=Watford, IO91
description2=United Kingdom
url=http://www.mw0mwz.co.uk/pi-star/
repeaterCall1=M0OUK
repeaterBand1=G
repeaterType1=0
repeaterAddress1=127.0.0.1
repeaterPort1=20011
reflector1=DCS061 C
atStartup1=1
reconnect1=0
frequency1=438.80000
offset1=0.0000
rangeKms1=1.000
latitude1=50.00
longitude1=-3.00
agl1=3.000
description1_1=Watford, IO91
description1_2=United Kingdom
url1=
band1_1=0
band1_2=0
band1_3=0
repeaterCall2=
repeaterBand2=
repeaterType2=0
repeaterAddress2=127.0.0.1
repeaterPort2=20012
reflector2=
atStartup2=0
reconnect2=0
frequency2=0.00000
offset2=0.0000
rangeKms2=0.000
latitude2=0.000000
longitude2=0.000000
agl2=0.000
description2_1=
description2_2=
url2=
band2_1=0
band2_2=0
band2_3=0
repeaterCall3=
repeaterBand3=
repeaterType3=0
repeaterAddress3=127.0.0.1
repeaterPort3=20013
reflector3=
atStartup3=0
reconnect3=0
frequency3=0.00000
offset3=0.0000
rangeKms3=0.000
latitude3=0.000000
longitude3=0.000000
agl3=0.000
description3_1=
description3_2=
url3=
band3_1=0
band3_2=0
band3_3=0
repeaterCall4=
repeaterBand4=
repeaterType4=0
repeaterAddress4=127.0.0.1
repeaterPort4=20014
reflector4=
atStartup4=0
reconnect4=0
frequency4=0.00000
offset4=0.0000
rangeKms4=0.000
latitude4=0.000000
longitude4=0.000000
agl4=0.000
description4_1=
description4_2=
url4=
band4_1=0
band4_2=0
band4_3=0
ircddbEnabled=1
ircddbHostname=rr.openquad.net
ircddbUsername=M0OUK
ircddbPassword=
ircddbEnabled2=0
ircddbHostname2=group1-irc.ircddb.net
ircddbUsername2=
ircddbPassword2=
ircddbEnabled3=0
ircddbHostname3=
ircddbUsername3=
ircddbPassword3=
ircddbEnabled4=0
ircddbHostname4=
ircddbUsername4=
ircddbPassword4=
aprsEnabled=1
aprsPassword=14500
aprsHostname=euro.aprs2.net
aprsPort=14580
dextraEnabled=1
dextraMaxDongles=5
dplusEnabled=1
dplusMaxDongles=5
dplusLogin=M0OUK
dcsEnabled=1
ccsEnabled=1
ccsHost=CCS706
xlxEnabled=0
xlxOverrideLocal=0
xlxHostsFileUrl=
starNetBand1=B
starNetCallsign1=
starNetLogoff1=
starNetInfo1=
starNetPermanent1=
starNetUserTimeout1=
starNetGroupTimeout1=
starNetCallsignSwitch1=1
starNetTXMsgSwitch1=1
starNetReflector1=
starNetBand2=B
starNetCallsign2=
starNetLogoff2=
starNetInfo2=
starNetPermanent2=
starNetUserTimeout2=
starNetGroupTimeout2=
starNetCallsignSwitch2=1
starNetTXMsgSwitch2=1
starNetReflector2=
starNetBand3=A
starNetCallsign3=
starNetLogoff3=
starNetInfo3=
starNetPermanent3=
starNetUserTimeout3=
starNetGroupTimeout3=
starNetCallsignSwitch3=0
starNetTXMsgSwitch3=1
starNetReflector3=
starNetBand4=A
starNetCallsign4=
starNetLogoff4=
starNetInfo4=
starNetPermanent4=
starNetUserTimeout4=
starNetGroupTimeout4=
starNetCallsignSwitch4=0
starNetTXMsgSwitch4=1
starNetReflector4=
starNetBand5=A
starNetCallsign5=
starNetLogoff5=
starNetInfo5=
starNetPermanent5=
starNetUserTimeout5=
starNetGroupTimeout5=
starNetCallsignSwitch5=0
starNetTXMsgSwitch5=1
starNetReflector5=
remoteEnabled=1
remotePassword=raspberry
remotePort=10022
language=0
infoEnabled=1
echoEnabled=1
logEnabled=1
dratsEnabled=1
dtmfEnabled=1
mobileGPSEnabled=0
mobileGPSAddress=127.0.0.1
mobileGPSPort=7834
windowX=-1
windowY=-1


Re: ASL_node_list.txt

Tom Corcoran
 

Got it. Tnx. will test after dinner. 


on a related point, the macros that are programmed by  the Configuration drop down cover 6 of the 10 items that I see on the Dialler macro drop down. Connect Parrot and Disconnect Parrot aren’t adjusted by the Configuration page. How can I access the Parrot Disconnect/Connect Parrot options? I’m using the Configuration macros to initiate ad hoc menus. This app is getting better and better. Tnx guys --

 Tom VE3NY


Re: ASL_node_list.txt

Steve N4IRS
 

root@omv:/opt/MMDVM_Bridge# ./dvswitch.sh collectProcessDataFiles
Processing NXDN
Processing P25
Processing DMR
Processing YSF
Processing DStar
Processing ASL
root@omv:/opt/MMDVM_Bridge# ls -la /tmp
-rw-r--r--  1 root     root       565 May 30 16:25 ABInfo_12345.json
-rw-r--r--  1 root     root       339 May 26 09:47 bm-cli.json
-rw-r--r--  1 root     root     27178 May 30 18:00 DMR_node_list.txt
-rw-r--r--  1 root     root       330 May 30 18:00 DSTAR_node_list.txt
-rw-------  1 root     root         4 May 25 07:24 ircDDB_Gateway
-rw-r--r--  1 root     root    533601 May 30 18:00 node_list.txt
-rw-r--r--  1 root     root      4209 May 30 18:00 NXDN_Hosts.txt
-rw-r--r--  1 root     root      2217 May 30 18:00 NXDN_node_list.txt
-rw-r--r--  1 root     root      5422 May 30 18:00 P25_Hosts.txt
-rw-r--r--  1 root     root      3346 May 30 18:00 P25_node_list.txt
-rw-r--r--  1 root     root     47341 May 30 18:00 TGList_BM.txt
-rw-------  1 root     root     35734 May 25 07:24 XLX_Hosts_4DvdtI
-rw-r--r--  1 root     root     65375 May 30 18:00 YSF_Hosts.txt
-rw-r--r--  1 root     root     27557 May 30 18:00 YSF_node_list.txt

The file you want is node_list.txt

Steve N4IRS


On 5/30/20 5:54 PM, Tom Corcoran wrote:
downloaded new dvswitch.sh … no longer getting error message regarding ASL … all nodes/lists get updated except I see no reference to ASL_node_list.txt file in /tmp directory. Is it stored somewhere else?
--
tnx .. Tom VE3NY


Re: ASL_node_list.txt

Tom Corcoran
 

downloaded new dvswitch.sh … no longer getting error message regarding ASL … all nodes/lists get updated except I see no reference to ASL_node_list.txt file in /tmp directory. Is it stored somewhere else?
--
tnx .. Tom VE3NY


Multiple FCS rooms bridging with one DVSwitch instance

David Young
 

I would like to bridge FCS rooms from 2 or more FCS servers using just one installed instance of the DVSwitch modules on a raspberry pi4.  Is this possible?  If so what would I need to modify or add?
 I am currently bridging one FCS server 4 room and would like to add a second, third and fourth room from different FCS servers to the bridge.
--
Dave WB6DTB


Re: ASL_node_list.txt

Steve N4IRS
 

I have updated dvswitch.sh on github.

On 5/30/20 2:22 PM, Mike Zingman - N4IRR wrote:
It appears that the ASL node list moved from its  old location in Feb, and I missed it.
I have changed the dvswitch.sh script, and when Steve merges the change, it will be available.


Re: ASL_node_list.txt

Mike Zingman - N4IRR
 

It appears that the ASL node list moved from its  old location in Feb, and I missed it.
I have changed the dvswitch.sh script, and when Steve merges the change, it will be available.


Re: ASL_node_list.txt

Tom Corcoran
 

Do I have to build my own file and pushfile to DVSM? If so, what’s the syntax for ASL modes?
--
Tom VE3NY


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge #mmdvm_bridge >> Intruder Problem #mmdvm_bridge

Uli
 

Hi Rudy,
I have done that and have setup  all ini files the same way you did but it does not work. I can hear others talking on the Brandmeister TG but when I talk into the DMR HT connected to this TG nothing to hear on the XLX Reflector side and when I talk into the HT connected to the XLX side nothing comes up on the DMR side.


Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge #mmdvm_bridge >> Intruder Problem #mmdvm_bridge

Rudy N6DOZ
 
Edited

Steve suggested using BrandMeister SelfCare and placing a static TG to the DMRid (+SSid) that you use.

I ended up setting something like 313540499 (99 being the SSid) to be used for my purpose and placed the TG that it bridges to.


ASL_node_list.txt

Tom Corcoran
 

Where do I find the ASL_node_list.txt file? I would like to make some modifications but when I do the ./dvswitch.sh collectProcessDataFiles  command, it doesn't appear in /tmp and I get a "ASL node list is not valid, ignoring" message
tnx .. 
--
Tom VE3NY

3121 - 3140 of 9600