Date   
Re: radioid.net URL update in dvswitch.sh

Giannis Giannakosian - SV4FFB
 

On Thu, Jun 4, 2020 at 07:35 AM, Jeffrey [K8JTK] wrote:
A pull of the DVSwitch-System-Builder has the old URL.  If an update is already available, it has the old url in that repo.
Hi Jeffrey

I have the same problem with the database.
Is it possible to upload the changes you made so that I can update the database manual until an update comes out?

Re: Multiple instances of Bridge

W8DSB
 

Hi Mike, I can’t get to the version number from work as I can’t login to Amazon without a private key. However looking at my dropbox at the .ini I have no TXport or RXport listed in the file. Can you please post a example and I will add it in.

Re: Multiple instances of Bridge

Mike Zingman - N4IRR
 

Do not use fromDMRPort and toDMRPort.  I asked you to use TXPort and RXPort in AB.  You should have gotten a nasty message in your AB log file, did you see it?
Also, just to make sure, what version of AB are you using?

Re: Multiple instances of Bridge

Steve N4IRS
 

Inline

On 6/9/2020 11:17 AM, W8DSB wrote:
Thanks Steve for your input. This is what I have now, I made it more simple until I get it working:

analog_bridge.ini
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103,31104,31105,31106     ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)

DVSwitch.ini #(from XLX1)
[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)

DVSwitch.ini #(from XLX2)
[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 = 31105                  ; Port to listen on (import)

Audio coming in from ASL goes out XLX1 & XLX2
Audio coming in XLX2 only goes out ASL
Does XLX 1 not go to ASL?

Anyway to bridge the return audio?
Not shure what you mean.

Is this better to use HBlink? I just learned about it this morning. Will it work with DDVSwitch or do I run it on a different device?
I don't think you need HBlink. Do you mean run with DVSwitch Mobile? If DVSM, I can make a case either way. I would do it after you get the bridges running.

Re: Multiple instances of Bridge

W8DSB
 

Thanks Steve for your input. This is what I have now, I made it more simple until I get it working:

analog_bridge.ini
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103,31104,31105,31106     ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)

DVSwitch.ini #(from XLX1)
[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)

DVSwitch.ini #(from XLX2)
[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 = 31105                  ; Port to listen on (import)

Audio coming in from ASL goes out XLX1 & XLX2
Audio coming in XLX2 only goes out ASL

Anyway to bridge the return audio?

Is this better to use HBlink? I just learned about it this morning. Will it work with DDVSwitch or do I run it on a different device? 

Re: Multiple instances of Bridge

Steve N4IRS
 

Only TX ports (or to) are multi-port.
If you are going to add descriptive text, comment it out. Example
; Source1 (Allstar):
If you are going to post from multiple files mark them as such:
; DVSwitch
; Analog_Bridge
I'm not commenting on the logic, only what jumps out.

Steve N4IRS

On 6/9/2020 9:27 AM, W8DSB wrote:
Just to follow up, it does not work, I might have done something wrong but I don't see where if I did. Here is the setup:

[AMBE_AUDIO]
server = 127.0.0.1                                                ; IP address of xx_Bridge.py
fromDMRPort = 31100,31101,31102,31103         ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31110,31111,31112,31113               ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)

Source1 (Allstar):
USRP Radio

Source2 (Brandmister Repeater TG):
[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 = 31110                  ; Port to listen on (import)

XLXa:
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31101                  ; Port to send AMBE TLV frames to (export)
RXPort = 31111                  ; Port to listen on (import)

XLXb:
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31102                  ; Port to send AMBE TLV frames to (export)
RXPort = 31112                  ; Port to listen on (import)

XLXc:
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31113                  ; Port to listen on (import)

The result was the source audio only worked once in a while, not reliable, and the three XLX's did not share the audio from the source.

Re: Multiple instances of Bridge

W8DSB
 

Just to follow up, it does not work, I might have done something wrong but I don't see where if I did. Here is the setup:

[AMBE_AUDIO]
server = 127.0.0.1                                                ; IP address of xx_Bridge.py
fromDMRPort = 31100,31101,31102,31103         ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31110,31111,31112,31113               ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)

Source1 (Allstar):
USRP Radio

Source2 (Brandmister Repeater TG):
[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 = 31110                  ; Port to listen on (import)

XLXa:
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31101                  ; Port to send AMBE TLV frames to (export)
RXPort = 31111                  ; Port to listen on (import)

XLXb:
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31102                  ; Port to send AMBE TLV frames to (export)
RXPort = 31112                  ; Port to listen on (import)

XLXc:
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31113                  ; Port to listen on (import)

The result was the source audio only worked once in a while, not reliable, and the three XLX's did not share the audio from the source.

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

EA5GVK Joaquin
 

DVLINK image v.9.7 ready to be updated via internet for pi 2/3/4 versions

We have also created the same DVLINK V.9.7.0 image for virtual BOX multilanguage, with the sections "DVSWITCH, HBLINK SERVER and HOTSPOTS / DMOS".

http://ea5gvk-dmr.zigor.es/2020/06/09/imagen-dvlink-v-9-7-virtual-para-virtual-box/

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

Re: Multiple instances of Bridge

Mike Zingman - N4IRR
 

Also note that this will not cross connect the XLX servers with each other. That is possible by using the same technique on the dvswitch.ini [DMR] TXPorts. However I would take it one step at a time. 

Re: Multiple instances of Bridge

W8DSB
 

Surprisingly enough I understood his description. I will give it a try in the morning I work afternoons :)

ASL bridge to YSF

honda5603@...
 

I'm getting reports of audio coming from ASL to YSF via Analog Bridge that's too loud.

What are you preferred audio levels like on your servers?

Re: Multiple instances of Bridge

Steve N4IRS
 

This message will self-destruct in five seconds. Good luck Mr Phelps.

On 6/8/2020 2:25 PM, Mike Zingman - N4IRR wrote:
I will start by saying I know nothing about the limitation you are running into with XLX (or even if it can be configured to do what you want).  With that being said, let's assume you DO want multiple XLX servers being fed from a single ASL source.  If you want to be a pioneer (arrows and all) do this:

- Three instances of MB,  each pointing at the XLX instance to service.
- One instance of AB and MD380 point back at the ASL USRP ports ([USRP] TXPort and RXPort)
- In that AB.ini, set the [AMBE_AUDIO] TXPort to feed all three MB instances thus:
TXPort = MB1,MB2,MB3 ; Where MB1,2,3 are the port numbers for each MB [DMR] RXPort in their DVSwitch.ini files
- In each MB instance, set the [DMR] TXPort to point back at the AB [AMBE_AUDIO] RXPort

Here is the discussion:  AB and MB now support multiple transmit ports when exporting information from one component to another.   So, in this case all DMR TLV frames that are emitted by AB will go to all three instances on MB (each on its own listening port).  The return path does not need this since there are three instances of MB, so each one is feeding the same listener for AB.

This is how this is intended to work, but I have to admit that if you do it then you will be a pioneer as I have not tried the specific configuration I outlined above.  Good luck Mr Phelps.

Mike N4IRR

Re: Multiple instances of Bridge

Mike Zingman - N4IRR
 

I will start by saying I know nothing about the limitation you are running into with XLX (or even if it can be configured to do what you want).  With that being said, let's assume you DO want multiple XLX servers being fed from a single ASL source.  If you want to be a pioneer (arrows and all) do this:

- Three instances of MB,  each pointing at the XLX instance to service.
- One instance of AB and MD380 point back at the ASL USRP ports ([USRP] TXPort and RXPort)
- In that AB.ini, set the [AMBE_AUDIO] TXPort to feed all three MB instances thus:
TXPort = MB1,MB2,MB3 ; Where MB1,2,3 are the port numbers for each MB [DMR] RXPort in their DVSwitch.ini files
- In each MB instance, set the [DMR] TXPort to point back at the AB [AMBE_AUDIO] RXPort

Here is the discussion:  AB and MB now support multiple transmit ports when exporting information from one component to another.   So, in this case all DMR TLV frames that are emitted by AB will go to all three instances on MB (each on its own listening port).  The return path does not need this since there are three instances of MB, so each one is feeding the same listener for AB.

This is how this is intended to work, but I have to admit that if you do it then you will be a pioneer as I have not tried the specific configuration I outlined above.  Good luck Mr Phelps.

Mike N4IRR

Re: Multiple instances of Bridge

Steve N4IRS
 

I'm not sure I understand what you are trying to accomplish.
1: You want to supply the same XLX connection (reflector) to other AllStar nodes?
2: You want to provide a different XLX connection to another node. You=XLX001 Them=XLX002?
3: You want to provide reflector "agile" services to another AllStar node?

Steve N4IRS

On 6/8/2020 12:32 PM, W8DSB wrote:
All, thank you in advance for reading this.

What I have is this:

FM Repeater<> ASL Node (with DVSwitch) <> XLX (DMR it has AMBE chips for DSTAR) <> BM this works OK until we try to export our DSTAR to another clubs XLX
The interlink connection does not support bring the audio back into the first XLX from the second or third or fourth to the AMBE
So what I think I want to do is this

                    XLX
                      ^
XLX  <>    FM Repeater    <>     XLX

All the XLX's need a separate connection via its own copy of the DVSwitch

I understand I need to make three copies of the MD380 and MMDVM folders and start them as separate services however what about the Analog_Bridge?  Do I need three copies of that also? I think I do to port the audio out to different versions of MD380 but does that mean I need three USRP radios in ALLSTAR?

How far back do I need three copies of everything?
Three USRP's?
Three Analog_Bridges? If so what do I need to change in each one? Just this emulatorAddress = 127.0.0.1:2470 or also all the audio ports also?

Re: Multiple instances of Bridge

 

All you need is Xlx to Mb to Mb to Xlx


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of W8DSB <w8dsb@...>
Sent: Monday, June 8, 2020 5:32:59 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Multiple instances of Bridge
 
All, thank you in advance for reading this.

What I have is this:

FM Repeater<> ASL Node (with DVSwitch) <> XLX (DMR it has AMBE chips for DSTAR) <> BM this works OK until we try to export our DSTAR to another clubs XLX
The interlink connection does not support bring the audio back into the first XLX from the second or third or fourth to the AMBE
So what I think I want to do is this

                    XLX
                      ^
XLX  <>    FM Repeater    <>     XLX

All the XLX's need a separate connection via its own copy of the DVSwitch

I understand I need to make three copies of the MD380 and MMDVM folders and start them as separate services however what about the Analog_Bridge?  Do I need three copies of that also? I think I do to port the audio out to different versions of MD380 but does that mean I need three USRP radios in ALLSTAR?

How far back do I need three copies of everything?
Three USRP's?
Three Analog_Bridges? If so what do I need to change in each one? Just this emulatorAddress = 127.0.0.1:2470 or also all the audio ports also?

Multiple instances of Bridge

W8DSB
 

All, thank you in advance for reading this.

What I have is this:

FM Repeater<> ASL Node (with DVSwitch) <> XLX (DMR it has AMBE chips for DSTAR) <> BM this works OK until we try to export our DSTAR to another clubs XLX
The interlink connection does not support bring the audio back into the first XLX from the second or third or fourth to the AMBE
So what I think I want to do is this

                    XLX
                      ^
XLX  <>    FM Repeater    <>     XLX

All the XLX's need a separate connection via its own copy of the DVSwitch

I understand I need to make three copies of the MD380 and MMDVM folders and start them as separate services however what about the Analog_Bridge?  Do I need three copies of that also? I think I do to port the audio out to different versions of MD380 but does that mean I need three USRP radios in ALLSTAR?

How far back do I need three copies of everything?
Three USRP's?
Three Analog_Bridges? If so what do I need to change in each one? Just this emulatorAddress = 127.0.0.1:2470 or also all the audio ports also?

Re: ASL <>MMDVM<>XLX<>BM/DStar

Nomis Bayan Jr.
 

HI Steve, Thank you so much.

On 6/6/2020 8:35 PM, Steve N4IRS wrote:
you may need to update it.

On 6/6/20 10:25 PM, Nomis Bayan Jr. wrote:

HI Steve,

I just found out that there was nothing on the DMRIds.dat. No data.

On 6/6/2020 7:24 PM, Steve N4IRS wrote:
Check your /var/lib/mmdvm/DMRIds.dat you may need to update it.

Steve

On 6/6/20 9:29 PM, Nomis Bayan Jr. wrote:

HI Steve,

Could not figure out why the callsign will not show up instead it is the DMR id....it was not like this before when I first started.

What I noticed was that I am missing this on the log:


I: 2020-05-15 07:06:48.383 Loaded 164301 Ids to the DMR callsign lookup table


DMR and Dstar will show the correct Callsign except for YSF, it will display the DMR ID.

Anything I am missing.

here is my set up

root@dvswitch:/opt/MMDVM_Bridge_BM# ./MMDVM_Bridge MMDVM_Bridge.ini
I: 2020-06-06 23:57:54.348 MMDVM_Bridge:
I: 2020-06-06 23:57:54.348 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-06-06 23:57:54.348 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-06-06 23:57:54.348 =
I: 2020-06-07 00:01:19.854 This software is for use on amateur radio networks only,
I: 2020-06-07 00:01:19.854 it is to be used for educational purposes only. Its use on
I: 2020-06-07 00:01:19.854 commercial networks is strictly prohibited.
I: 2020-06-07 00:01:19.854 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-06-07 00:01:19.854 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2020-06-07 00:01:19.854 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac)
I: 2020-06-07 00:01:19.854 General Parameters
I: 2020-06-07 00:01:19.854     Callsign: N0MIS
I: 2020-06-07 00:01:19.854     Id: 3156418
I: 2020-06-07 00:01:19.854     Duplex: no
I: 2020-06-07 00:01:19.854     Timeout: 180s
I: 2020-06-07 00:01:19.854     D-Star: disabled
I: 2020-06-07 00:01:19.854     DMR: enabled
I: 2020-06-07 00:01:19.854     YSF: disabled
I: 2020-06-07 00:01:19.854     P25: disabled
I: 2020-06-07 00:01:19.854     NXDN: disabled
I: 2020-06-07 00:01:19.854 Modem Parameters
I: 2020-06-07 00:01:19.854     Port: /dev/null
I: 2020-06-07 00:01:19.855     RX Invert: no
I: 2020-06-07 00:01:19.855     TX Invert: no
I: 2020-06-07 00:01:19.855     PTT Invert: no
I: 2020-06-07 00:01:19.855     TX Delay: 100ms
I: 2020-06-07 00:01:19.855     RX Offset: 0Hz
I: 2020-06-07 00:01:19.855     TX Offset: 0Hz
I: 2020-06-07 00:01:19.855     RX DC Offset: 0
I: 2020-06-07 00:01:19.855     TX DC Offset: 0
I: 2020-06-07 00:01:19.855     RF Level: 100.0%
I: 2020-06-07 00:01:19.855     DMR Delay: 0 (0.0ms)
I: 2020-06-07 00:01:19.855     RX Level: 50.0%
I: 2020-06-07 00:01:19.855     CW Id TX Level: 50.0%
I: 2020-06-07 00:01:19.855     D-Star TX Level: 50.0%
I: 2020-06-07 00:01:19.855     DMR TX Level: 50.0%
I: 2020-06-07 00:01:19.855     YSF TX Level: 50.0%
I: 2020-06-07 00:01:19.855     P25 TX Level: 50.0%
I: 2020-06-07 00:01:19.855     NXDN TX Level: 50.0%
I: 2020-06-07 00:01:19.855     RX Frequency: 222340000Hz (222340000Hz)
I: 2020-06-07 00:01:19.855     TX Frequency: 224940000Hz (224940000Hz)
M: 2020-06-07 00:01:19.855 Opening the MMDVM
I: 2020-06-07 00:01:19.855 Display Parameters
I: 2020-06-07 00:01:19.855     Type:
I: 2020-06-07 00:01:19.855 DMR Network Parameters
I: 2020-06-07 00:01:19.855     Address: 45.22.199.202
I: 2020-06-07 00:01:19.855     Port: 62030
I: 2020-06-07 00:01:19.855     Local: 62033
I: 2020-06-07 00:01:19.855     Jitter: 360ms
I: 2020-06-07 00:01:19.855     Slot 1: disabled
I: 2020-06-07 00:01:19.855     Slot 2: enabled
I: 2020-06-07 00:01:19.855     Mode Hang: 3s
I: 2020-06-07 00:01:19.855     Options: XLX:4002
I: 2020-06-07 00:01:19.856 Info Parameters
I: 2020-06-07 00:01:19.856     Callsign: N0MIS
I: 2020-06-07 00:01:19.856     RX Frequency: 222340000Hz
I: 2020-06-07 00:01:19.856     TX Frequency: 224940000Hz
I: 2020-06-07 00:01:19.856     Power: 1W
I: 2020-06-07 00:01:19.856     Latitude: 32.785198deg N
I: 2020-06-07 00:01:19.856     Longitude: -117.029503deg E
I: 2020-06-07 00:01:19.856     Height: 0m
I: 2020-06-07 00:01:19.856     Location: "La Mesa, San Diego, CA"
I: 2020-06-07 00:01:19.856     Description: "MMDVM_Bridge"
I: 2020-06-07 00:01:19.856     URL: "https://groups.io/g/DVSwitch"
M: 2020-06-07 00:01:19.856 DMR, Opening DMR Network
I: 2020-06-07 00:01:19.856 RSSI
I: 2020-06-07 00:01:19.856     Mapping File: RSSI.dat
W: 2020-06-07 00:01:19.856 Cannot open the RSSI data file - RSSI.dat
I: 2020-06-07 00:01:19.856 DMR Id Lookups
I: 2020-06-07 00:01:19.856     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-06-07 00:01:19.856     Reload: 24 hours
I: 2020-06-07 00:01:19.856 DMR RF Parameters
I: 2020-06-07 00:01:19.856 Started the DMR Id lookup reload thread
I: 2020-06-07 00:01:19.856     Id: 3156418
I: 2020-06-07 00:01:19.856     Color Code: 1
I: 2020-06-07 00:01:19.856     Self Only: no
I: 2020-06-07 00:01:19.856     Embedded LC Only: yes
I: 2020-06-07 00:01:19.856     Dump Talker Alias Data: no
I: 2020-06-07 00:01:19.856     Prefixes: 0
I: 2020-06-07 00:01:19.857     Call Hang: 3s
I: 2020-06-07 00:01:19.857     TX Hang: 3s
I: 2020-06-07 00:01:19.857     Mode Hang: 10s
M: 2020-06-07 00:01:19.857 DMR, Opening INI file: DVSwitch.ini
M: 2020-06-07 00:01:19.857 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-06-07 00:01:19.857 DMR, Setting [DMR] TXPort -> 32100
M: 2020-06-07 00:01:19.857 DMR, Setting [DMR] RXPort -> 32103
M: 2020-06-07 00:01:19.857 DMR, Setting [DMR] Slot -> 2
M: 2020-06-07 00:01:19.857 DMR, Transmitting on 127.0.0.1:32100 and listening on port 32103.  Result = 1
M: 2020-06-07 00:01:19.857 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-06-07 00:01:29.863 DMR, Sending authorisation
D: 2020-06-07 00:01:29.869 DMR, Sending configuration
M: 2020-06-07 00:01:39.874 DMR, Logged into the master successfully
D: 2020-06-07 00:01:39.874 DMR, Sending XLX options
M: 2020-06-07 00:01:39.874 DMR, Remote CMD: txTg=4000
M: 2020-06-07 00:01:39.874 DMR, Tune: id=3156418, tg=4000, mode=Group
M: 2020-06-07 00:01:39.874 DMR, Remote CMD: txTg=4002
M: 2020-06-07 00:01:39.874 DMR, Tune: id=3156418, tg=4002, mode=Group
M: 2020-06-07 00:01:39.895 DMR Slot 2, received network voice header from 3156418 to TG 9
M: 2020-06-07 00:01:39.900 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%

On 6/6/2020 3:43 PM, Steve N4IRS wrote:
As in, you have it working now?

On 6/6/20 6:32 PM, W8DSB wrote:
Thanks, this is the working example:

[DMR Network]
Enable=1
Address=68.36.42.150
Port=62030
Jitter=750
Local=62032
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0




Re: Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Hi All, 

I think i got it working for the most part. 

I have since done a complete reinstall of the OS using the mini ubuntu iso. basically is so cut back that it boots really quickly. 

All the configs setup from the DMR to P25 example port mappings.

export the environment variable using "export ABINFO=/tmp/ABInfo_32001.json" so DV switch only controls the P25 side of AB.

But the problem seemed to be there and only when dvswitch.sh sent an info packet.

so for the time being, I have commented out the send info packet line in dvswitch.sh. Probably not the best approach but it works and now I can change P25 talkgroups on the fly.

Next question... Is the info packet needed for talk group changing on AB?

Re: ASL_node_list.txt

Steve N4IRS
 

The file has been moved to better align it with it's "parent"
wget https://github.com/DVSwitch/MMDVM_Bridge/raw/master/dvswitch.sh


On 6/6/20 11:33 PM, W Paul Mills AC0HY wrote:

On 6/4/20 11:45 PM, Eric-K6KWB wrote:

Steve N4IRS, I downloaded this the other day got error "page not found". sorry I cant remember the date looks like a week ago. wget https://github.com/DVSwitch/Analog_Bridge/raw/master/dvswitch.sh

73, Eric


-- 
/**************************************************
* Amateur Radio Station AC0HY                     *
* W. Paul Mills         SN807                     *
* Assistant EC Alpha-1 ARES Shawnee/Wabaunsee, KS *
* President Kaw Valley Amateur Radio Club         *
**************************************************/

Re: ASL_node_list.txt

W Paul Mills AC0HY
 


On 6/4/20 11:45 PM, Eric-K6KWB wrote:

Steve N4IRS, I downloaded this the other day got error "page not found". sorry I cant remember the date looks like a week ago. wget https://github.com/DVSwitch/Analog_Bridge/raw/master/dvswitch.sh

73, Eric


-- 
/**************************************************
* Amateur Radio Station AC0HY                     *
* W. Paul Mills         SN807                     *
* Assistant EC Alpha-1 ARES Shawnee/Wabaunsee, KS *
* President Kaw Valley Amateur Radio Club         *
**************************************************/