Date   

Re: Setting up a YSF Reflector <---> XLX (DMR) Reflector

Steve N4IRS
 

We don't use YSF2DMR. If you want to bridge the 2 networks use MMDVM_Bridge.

Steve N4IRS

On 6/12/20 8:50 PM, Adrianm0glj@... wrote:
Hi All

I'm trying to setup a YSF Reflecter to XLX(DMR) reflector. The YSFReflector is working. From what I have read I should be able to use YSF2DMR to bridge the 2 networks.
I have followed the instructions on https://github.com/juribeparada/MMDVM_CM/blob/master/YSF2DMR/service/README.md to setup the unit file and I have the XLXHosts.txt file downloaded from http://xlxapi.rlx.lu/api.php?do=GetXLXDMRMaster

However, I am getting and error when I start the unit file.

--->snip<---
root@vps-4a62c445:/usr/local/bin# sudo systemctl status ysf2dmr
● ysf2dmr.service - YSF2DMR Service
   Loaded: loaded (/lib/systemd/system/ysf2dmr.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-06-13 01:49:01 BST; 5s ago
  Process: 2374 ExecStop=/usr/local/sbin/ysf2dmr.service stop (code=exited, status=1/FAILURE)
  Process: 2362 ExecStart=/usr/local/sbin/ysf2dmr.service start (code=exited, status=0/SUCCESS)
 Main PID: 2362 (code=exited, status=0/SUCCESS)

Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: I: 2020-06-13 00:49:01.354 General Parameters
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: I: 2020-06-13 00:49:01.354     Remote Gateway: no
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: I: 2020-06-13 00:49:01.354     Hang Time: 1000 ms
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: M: 2020-06-13 00:49:01.354 Opening YSF network connection
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: M: 2020-06-13 00:49:01.355 Trying to find non existent XLX reflector with an id of 5
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: E: 2020-06-13 00:49:01.355 Cannot open DMR Network
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: YSF2DMR started as PID
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2374]: YSF2DMR is not running
Jun 13 01:49:01 vps-4a62c445 systemd[1]: ysf2dmr.service: Control process exited, code=exited status=1
Jun 13 01:49:01 vps-4a62c445 systemd[1]: ysf2dmr.service: Failed with result 'exit-code'.
root@vps-4a62c445:/usr/local/bin#

 
--->snip<---

Could someone give me some tips on where to look for the obvious mistake that I have made the is not hitting me on the head please?

Thanks in Advance
Adrian M0GLJ


Setting up a YSF Reflector <---> XLX (DMR) Reflector

Adrianm0glj@...
 

Hi All

I'm trying to setup a YSF Reflecter to XLX(DMR) reflector. The YSFReflector is working. From what I have read I should be able to use YSF2DMR to bridge the 2 networks.
I have followed the instructions on https://github.com/juribeparada/MMDVM_CM/blob/master/YSF2DMR/service/README.md to setup the unit file and I have the XLXHosts.txt file downloaded from http://xlxapi.rlx.lu/api.php?do=GetXLXDMRMaster

However, I am getting and error when I start the unit file.

--->snip<---
root@vps-4a62c445:/usr/local/bin# sudo systemctl status ysf2dmr
● ysf2dmr.service - YSF2DMR Service
   Loaded: loaded (/lib/systemd/system/ysf2dmr.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-06-13 01:49:01 BST; 5s ago
  Process: 2374 ExecStop=/usr/local/sbin/ysf2dmr.service stop (code=exited, status=1/FAILURE)
  Process: 2362 ExecStart=/usr/local/sbin/ysf2dmr.service start (code=exited, status=0/SUCCESS)
 Main PID: 2362 (code=exited, status=0/SUCCESS)

Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: I: 2020-06-13 00:49:01.354 General Parameters
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: I: 2020-06-13 00:49:01.354     Remote Gateway: no
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: I: 2020-06-13 00:49:01.354     Hang Time: 1000 ms
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: M: 2020-06-13 00:49:01.354 Opening YSF network connection
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: M: 2020-06-13 00:49:01.355 Trying to find non existent XLX reflector with an id of 5
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: E: 2020-06-13 00:49:01.355 Cannot open DMR Network
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2362]: YSF2DMR started as PID
Jun 13 01:49:01 vps-4a62c445 ysf2dmr.service[2374]: YSF2DMR is not running
Jun 13 01:49:01 vps-4a62c445 systemd[1]: ysf2dmr.service: Control process exited, code=exited status=1
Jun 13 01:49:01 vps-4a62c445 systemd[1]: ysf2dmr.service: Failed with result 'exit-code'.
root@vps-4a62c445:/usr/local/bin#

 
--->snip<---

Could someone give me some tips on where to look for the obvious mistake that I have made the is not hitting me on the head please?

Thanks in Advance
Adrian M0GLJ


Re: YSF <> BM DMR Bridging - Best Way?

J M
 

After doing even more reading and experimenting, I got this all worked out. I ended up switching XLX back to serving D-STAR + DMR, C4FM using YSFReflector, and tying those two together with MMDVM_Bridge. Everything seems to be working.


YSF <> BM DMR Bridging - Best Way?

J M
 

Hello all,

Is there any document/guidance on building a YSF to DMR (BM) connection the right way? Here's the situation.... I run XLX330 using xlxd + ambed. At one point it was working across all three modes (D-STAR, DMR, YSF) but something recently changed (seems like with BM DMR, but can't figure it out precisely) and the ambed process was exhausting the 3 channels available for transcoding. So I disabled our transcode link with BM3103 (TG #311070) and everything works fine with D-STAR <> YSF transcoding as it did before. D-STAR is public as DCS/XRF/REF330A and YSF is public as #83603. I want to re-add the DMR transcoding to the mix. I've tried MMDVM_Bridge to connect to the XLXD process using YSF and BM3103 for DMR. However I cannot get the connection to login whether using my personal ID or one of the repeater IDs. I also know that connecting to BM directly with MMDVM_Bridge isn't really supposed to be done, but I wanted to get stuff back on the air temporarily until we get a permanent solution. I can't find any further debugging/troubleshooting on the login process to tell me what is actually wrong. I can see the packets going back and forth in tcpdump but all I get is "DMR, Connection to the master has timed out, retrying connection". So I'm looking for different options.

Anyway, all that being said, is there a best way to do this? I was considering re-enabling DMR interlinking on XLX try to go the other way to another YSF service, but I'm not entirely clear how to host the YSF gateway in a separate application.

Anyone able to help?

Thanks in advance,
Jason N8EI


Re: radioid.net URL update in dvswitch.sh

Jeffrey [K8JTK]
 

Edit dvswitch.sh changing
from: www.radioid.net
to: database.radioid.net
After changing, run the script manually to immediately update the subscribers file or wait until it runs automatically.


Re: Multiple instances of Bridge

W8DSB
 

Version 1.4.2


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?

2941 - 2960 of 9518