Date   

Bang Head Here (mine, not yours)

kb3cs
 

i have two small DVSwitch-using projects in mind. for both projects, i have already obtained permission to connect a bridge.

my first try used the blog post "Hosting an AllStar Node and an AllStarDMR bridge in the cloud" as the basis, and i thought i might be able to follow along and end up at my ultimate goal of bridging from a low traffic BM TG to an Echolink Conference.

what i have learned so far is it seems since the time when KV4S wrote the blog post and now, there are no separate allstarlink and dvswitch repositories. it is enough to add just the dvswitch repo, thus:

$ pushd /tmp
/tmp ~/Software/DVSwitch
$ wget http://dvswitch.org/install-dvswitch-repo
--2020-03-28 09:22:14-- http://dvswitch.org/install-dvswitch-repo
Resolving dvswitch.org (dvswitch.org)... 44.103.34.4
Connecting to dvswitch.org (dvswitch.org)|44.103.34.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 782
Saving to: ‘install-dvswitch-repo’

install-dvswitch-repo 100%[================================================>] 782 --.-KB/s in 0s

2020-03-28 09:22:14 (22.0 MB/s) - ‘install-dvswitch-repo’ saved [782/782]

$ sudo bash
# . ./install-dvswitch-repo
--2020-03-28 09:22:23-- http://dvswitch.org/ASL_Repository/dvswitch.list
Resolving dvswitch.org (dvswitch.org)... 44.103.34.4
Connecting to dvswitch.org (dvswitch.org)|44.103.34.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 92
Saving to: ‘dvswitch.list’

dvswitch.list 100%[================================================>] 92 --.-KB/s in 0s

2020-03-28 09:22:23 (405 KB/s) - ‘dvswitch.list’ saved [92/92]

--2020-03-28 09:22:23-- http://dvswitch.org/ASL_Repository/dvswitch.gpg.key
Resolving dvswitch.org (dvswitch.org)... 44.103.34.4
Connecting to dvswitch.org (dvswitch.org)|44.103.34.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1678 (1.6K) [application/pgp-keys]
Saving to: ‘STDOUT’

- 100%[================================================>] 1.64K --.-KB/s in 0s

2020-03-28 09:22:23 (77.9 MB/s) - written to stdout [1678/1678]

OK
Get:1 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
.
.
Fetched 1,878 kB in 4s (458 kB/s)
Reading package lists... Done
Installed repositories:
.
.
http://dvswitch.org/ASL_Repositorystretch/hamradio
.
.
# exit

(now how the heck did the text color and paragraph margin color get set?!)
(okay fixed: click "Source code" in the groups.io editor and throw away the css style bits that got automagically inserted)
(right. back to my post .. "what i have learned so far")

secondly, attempting to install the allstarlink package runs right into a problem:

$ sudo apt install allstarlink asl-asterisk libcurl3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcurl3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
However the following packages replace it: libcurl4:i386 libcurl4

E: Package 'libcurl3' has no installation candidate

(i give up trying to use the editor. it messes up when there's more than one blockquote. "Source code" editing it is..)

here's the list of libcurl* packages available to me (Ubuntu 19.10, soon to be 20.04 LTS):

$ apt search libcurl | grep -E "^libcu"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libcupt4-2-downloadmethod-curl/eoan 2.10.3 amd64
libcurl-ocaml/eoan 0.8.2-1build3 amd64
libcurl-ocaml-dev/eoan 0.8.2-1build3 amd64
libcurl3-gnutls/eoan,now 7.65.3-1ubuntu3 amd64 [installed]
libcurl3-nss/eoan 7.65.3-1ubuntu3 amd64
libcurl4/eoan,now 7.65.3-1ubuntu3 amd64 [installed]
libcurl4-doc/eoan,eoan 7.65.3-1ubuntu3 all
libcurl4-gnutls-dev/eoan 7.65.3-1ubuntu3 amd64
libcurl4-nss-dev/eoan 7.65.3-1ubuntu3 amd64
libcurl4-openssl-dev/eoan,now 7.65.3-1ubuntu3 amd64 [installed]
libcurlpp-dev/eoan 0.8.1-2build1 amd64
libcurlpp0/eoan 0.8.1-2build1 amd64

i can make no more forward progress. my wagon's axle is lodged on the remainder of a cut-down tree in the road: i am "stumped."
if someone can guide me clear of this obstacle, i'd very much appreciate it.

. chris KB3CS . - 0x49 -


Re: MMDVM Duplicating #mmdvm_bridge

 

Analog_Bridge and MMDVM_Bridge usually starts on boot up.
If you want them to run in a terminal you need to stop them.
systemctl stop analog_bridge
system stop mmdvm_bridge


MMDVM Duplicating #mmdvm_bridge

Dexter Harroo
 

Hi guys I have a single instance MMDVM_Bridge running, It connects a ysf network to DMR, lately i have been noticing that there is a echo or reverb at the end of transmissions, when i look at the ysf dashboard it shows 2 connected gateways with my call sign, its suppose to be one, i have tried stopping MMDVM_Bridge and disabling it but the other instance wont disconnect. Has anyone else had this issue and if so mind sharing how it was solved?

thanks 
9Y4C


Re: Average DMR VS YSF audio level

 

Dmr radios are usually  louder than C4fm Radios. Turn mic gain down on Dmr and up on C4fm.

I have tried this and it works Dmr MB to AB to AB to MB Ysf. You can alter the audio on one AB.

 


Average DMR VS YSF audio level

Skyler Fennell
 

I have DMR bridged directly to YSFN using HBLINK as a central server.

I have noticed that DMR audio for our little group of users tends to be significantly louder than YSFN audio.

Is the standard for YSFN supposed to equal the level of DMR, or are these levels different?

I only have one setting since I am only running one instance of analog bridge, so I am constantly fighting to get it to a good level that compromises DMR and YSFN.

Maybe it's just operator error that they don't know how to use a mic / gain setting properly.

w0sky


P25Reflector-Dashboard - Repeated Entries

mike@...
 

My "Connected Gateways" section shows duplicate entries for certain gateways. Anyone know why this may be happening? 
Timestamps are about 2 minutes apart for each dupe - the section looks like this: 

2020-03-25 17:54:07  Callsign#1
2020-03-25 17:54:07  Callsign#2
2020-03-25 17:54:07  Callsign#3
2020-03-25 17:54:07  Callsign#4
2020-03-25 17:52:07  Callsign#4

Appreciate the help! 

73
N6MIK


Re: MMDVM_Bridge segfaulting on RPi 1B with Debian Buster

정성환
 

Hi Florian

Would you let me know to install Analog_bridge.armv6l and mmdvm_bridge. armv6l on Raspi zero w ?


Stay at Home SALE on the ThumbDV™

 

The “Stay at Home” order by Governor Inslee of Washington State, has impacted some of our vendors, delaying the DRAWS™ run. We will keep you apprised.

So it’s time for a sale on the ThumbDV™ !

Might as well contact Hams on the reflectors using DSTAR, DMR or Fusion from your PC at home.

Normally $119.95, on Sale NOW for $99.95 at least until the order is lifted, or we run out of inventory.

Price Protection Policy: If you ordered a ThumbDV™ in the last 30 days, email sales@... for a $20 refund.

http://nwdigitalradio.com/product/thumbdv/  


Re: NXDN not passing thru to Dstar

Kevin Halton
 

It appears to have corrected itself. Tried this morning and audio passing thru all modes! THANKS FOR ALL THE HELP!!


Re: Connecting more that 2 Analog_Bridges #analog_bridge

Jeff DePolo WN3A
 

Port address, not IP.
As same with each P25 NXDN DMR etc service instance that is on the same server.
A separate PORT ADDRESS will be needed for each instance of a service running on the same server.
You're typing "port address" when you mean port number. I think that's why you are confusing JJ et al. Assuming they're all running on the same host, they will all use the localhost IP ADDRESS (127.0.0.1), but different PORT NUMBERS.

--- Jeff WN3A






--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: Connecting more that 2 Analog_Bridges #analog_bridge

Steve N4IRS
 

If only it were so. In the diagram below (if I understand it) you have NXDN, DMR and YSFn all enabled. That's fine but NXDN is going to need to point it's TX and RX UDP ports at another mode (or Analog_Bridge)  But only one partner. MMDVM_Bridge does not mix all the modes and then output to AB. It's a one to one relationship. Look at DVSwitch.ini:

; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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)

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32100                  ; Port to send AMBE TLV frames to (export)
RXPort = 32103                  ; Port to listen on (import)

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 33100                  ; Port to send AMBE TLV frames to (export)
RXPort = 33103                  ; Port to listen on (import)

; Configure the P25 Partner
; Audio format is IMBE 88 bit
[P25]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34100                  ; Port to send AMBE TLV frames to (export)
RXPort = 34103                  ; Port to listen on (import)

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)

For a DMR to NXDN bridge it require to "cross connect the DMR and NXDN ports like this:

[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)

[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31103                  ; Port to send AMBE TLV frames to (export)
RXPort = 31100                  ; Port to listen on (import)

To mix everything in analog, you will need an ASL node for each mode. That's 5 copies of AB and 5 ASL nodes on the server. But I'll say again, you do not want to convert each mode to analog due to the loss of quality as compared to like vocoders.

Steve N4IRS


On 3/24/2020 12:45 PM, davek wrote:
Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar



Re: Connecting more that 2 Analog_Bridges #analog_bridge

Mike KB8JNM
 

Port address, not IP.

As same with each P25 NXDN DMR etc service instance that is on the same server.

A separate PORT ADDRESS will be needed for each instance of a service running on the same server.

They can not be shared unless something has changed that I was not aware of.

On 3/24/2020 1:11 PM, JJ Cummings wrote:
Maybe it's just a matter of what you and I are calling thing?

I read "address" as an IP Address which does not need to be unique at all.  All that needs to happen is each mode has an ASL node which listens for and sends USRP on a given set of ports.  Those ports need to be unique per node, but note the IP Address.

On Tue, Mar 24, 2020 at 11:03 AM Mike KB8JNM <groupio@...> wrote:

I was referring to the USRP address. One address set for each node.

On 3/24/2020 12:57 PM, JJ Cummings wrote:
You are correct with your design.  Not sure what "address" needs to be different.. but each would require it's own node entry in your ASL config and then you would need to link those ASL nodes together.  We accomplish this by having each mode have it's own node (as noted already) and then link each of those into a central ASL hub node where we can connect/disconnect at will.

On Tue, Mar 24, 2020 at 10:54 AM Mike KB8JNM <groupio@...> wrote:

The only thing I can see to note is that you will need 3 nodes. One for EACH AB you are showing.

Each will need a unique address on the same server. Perhaps there is more I am over looking.

On 3/24/2020 12:45 PM, davek wrote:
Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar


Re: Connecting more that 2 Analog_Bridges #analog_bridge

JJ Cummings
 

Maybe it's just a matter of what you and I are calling thing?

I read "address" as an IP Address which does not need to be unique at all.  All that needs to happen is each mode has an ASL node which listens for and sends USRP on a given set of ports.  Those ports need to be unique per node, but note the IP Address.

On Tue, Mar 24, 2020 at 11:03 AM Mike KB8JNM <groupio@...> wrote:

I was referring to the USRP address. One address set for each node.

On 3/24/2020 12:57 PM, JJ Cummings wrote:
You are correct with your design.  Not sure what "address" needs to be different.. but each would require it's own node entry in your ASL config and then you would need to link those ASL nodes together.  We accomplish this by having each mode have it's own node (as noted already) and then link each of those into a central ASL hub node where we can connect/disconnect at will.

On Tue, Mar 24, 2020 at 10:54 AM Mike KB8JNM <groupio@...> wrote:

The only thing I can see to note is that you will need 3 nodes. One for EACH AB you are showing.

Each will need a unique address on the same server. Perhaps there is more I am over looking.

On 3/24/2020 12:45 PM, davek wrote:
Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar


Re: Connecting more that 2 Analog_Bridges #analog_bridge

Mike KB8JNM
 

I was referring to the USRP address. One address set for each node.

On 3/24/2020 12:57 PM, JJ Cummings wrote:
You are correct with your design.  Not sure what "address" needs to be different.. but each would require it's own node entry in your ASL config and then you would need to link those ASL nodes together.  We accomplish this by having each mode have it's own node (as noted already) and then link each of those into a central ASL hub node where we can connect/disconnect at will.

On Tue, Mar 24, 2020 at 10:54 AM Mike KB8JNM <groupio@...> wrote:

The only thing I can see to note is that you will need 3 nodes. One for EACH AB you are showing.

Each will need a unique address on the same server. Perhaps there is more I am over looking.

On 3/24/2020 12:45 PM, davek wrote:
Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar


Re: Connecting more that 2 Analog_Bridges #analog_bridge

JJ Cummings
 

You are correct with your design.  Not sure what "address" needs to be different.. but each would require it's own node entry in your ASL config and then you would need to link those ASL nodes together.  We accomplish this by having each mode have it's own node (as noted already) and then link each of those into a central ASL hub node where we can connect/disconnect at will.


On Tue, Mar 24, 2020 at 10:54 AM Mike KB8JNM <groupio@...> wrote:

The only thing I can see to note is that you will need 3 nodes. One for EACH AB you are showing.

Each will need a unique address on the same server. Perhaps there is more I am over looking.

On 3/24/2020 12:45 PM, davek wrote:
Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar


Re: Connecting more that 2 Analog_Bridges #analog_bridge

Mike KB8JNM
 

The only thing I can see to note is that you will need 3 nodes. One for EACH AB you are showing.

Each will need a unique address on the same server. Perhaps there is more I am over looking.

On 3/24/2020 12:45 PM, davek wrote:
Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar


Re: Connecting more that 2 Analog_Bridges #analog_bridge

davek
 

Would this seem like a appropriate all mode solution? Or am i over complicating this? I am not sure on the DStar


Re: Connecting more that 2 Analog_Bridges #analog_bridge

davek
 

Exactly what i needed to know, thanks Steve


Re: Connecting more that 2 Analog_Bridges #analog_bridge

Steve N4IRS
 

The only way to bridge USRP across more then 2 connections is with ASL.
The other issue to consider is that you don't ALWAYS want to go analog for conversion. Consider this:
DMR, NXDN, YSFn.  No conversion required. All 3 are AMBE so it's a simple cross connected MMDVM single instance for 2 modes.
YSFw and P25. No conversion required. All 3 ar IMBE so it's a simple cross connected MMDVM single instance for 2 modes.
D-Star is stand alone.

So, for example if you used 2 instances of AB to bridge DMR to NXDN you would loose quality by going to analog when it's not needed.

 Steve N4IRS

On 3/24/2020 11:40 AM, davek wrote:
Bridge more than one (all?) digital modes together


Re: Connecting more that 2 Analog_Bridges #analog_bridge

davek
 

Bridge more than one (all?) digital modes together

3301 - 3320 of 9299