Re: Installing DVswitch server on RPI from scratch - Question
Adrian Fewster <vk4tux@...>
Instead of below you can just do ;
mv Analog_Bridge.amd64 Analog_Bridge
Then there is nothing to remove
toggle quoted messageShow quoted text
On 20/11/19 8:56 pm, Carlos Minguela via Groups.Io wrote: cp Analog_Bridge.amd64 Analog_Bridge rm Analog_Bridge.amd64
|
|
Re: Installing DVswitch server on RPI from scratch - Question

Carlos Minguela
Hi, I was in the same situation last week. I just fount how to make it works. That tutorial you mention I found that is outdated. Here is what I did:
cd /tmp
wget http://dvswitch.org/install-dvswitch-repo
chmod +x install-dvswitch-repo
./install-dvswitch-repo
apt-get update
apt-get install dvswitch
cd /opt/Analog_Bridge
****Download DVSwitch server files
wget https://github.com/DVSwitch/Analog_Bridge/raw/master/bin/Analog_Bridge.armhf
wget https://github.com/DVSwitch/Analog_Bridge/raw/master/dvsm.macro
wget https://github.com/DVSwitch/Analog_Bridge/raw/master/dvswitch.sh
wget https://github.com/DVSwitch/Analog_Bridge/raw/master/parrot.sh
rm Analog_Bridge
cp Analog_Bridge.armhf Analog_Bridge
rm Analog_Bridge.armhf
chmod +x Analog_Bridge
chmod +x dvsm.macro
chmod +x dvswitch.sh
chmod +x parrot.sh
****** Modify your personal settings here
** Modify Analog_Bridge.ini
decoderFallBack = true
txPort = 31103
rxPort = 31100
gatewayDmrId = 312xxxxxxx(your DMR ID)
repeaterID = 312xxxxxx(your DMR ID plus 2 digits)
txPort = 50111
rxPort = 50111
aslAudio = AUDIO_USE_GAIN
agcGain = 6
dmrAudio = AUDIO_USE_GAIN
dmrGain = 0.35
** Modify MMDVM_Bridge.ini
cd /opt/MMDVM_Bridge
nano MMDVM_Bridge.ini
** Change this:
[General]
Callsign=EA2XXXXXX(your callsign)
Id=312xxxxxxx(your DMR ID)
Timeout=180
Duplex=0
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
[DMR Network]
Enable=1
Address=74.91.118.251(your favorite Brandmeister server)
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
**** Activate the system
systemctl enable md380-emu
systemctl start md380-emu
systemctl enable analog_bridge
systemctl start analog_bridge
systemctl enable mmdvm_bridge
systemctl start mmdvm_bridge
done
I hope this instruction help you.
73 Carlos KP4CA
|
|
Installing DVswitch server on RPI from scratch - Question
Hi everyone I'm trying to install DVS server from scratch on one of my PI's. Instead of using one of the available image with everything set up (immense work!) I want to learn. I know there's a pdf with step-by-step instructions but I think it's a little dated as some of the "wget...." commands to get for example ...dmr.ini gives a 404 error as if the files are not there. According to this I cant continue with the installation. It is my intuition (not knowledge) that that group of xxx.ini files are located some place else? Help/advice much appreciated as I cant go any further. Thanks in advance PS: the name of the document is DVSwitch 0725 updated on July 25 2019
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL
Steve, thank you for info
73 Waldek
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL

Steve N4IRS
Waldek,
That is the correct version. We did not update the version or date
information for those binaries. The next push will have updated
version and date information.
Steve
toggle quoted messageShow quoted text
On 11/19/2019 11:13 AM, Waldek SP2ONG
wrote:
Steve
I have updated Ananlog_Bridge i386 (github show that file was
updated 22 hours) but in log show me
I: 2019-11-19 16:09:17.351 Analog Bridge Version 1.4.1
Mon Nov 11 14:23:21 EST 2019
I: 2019-11-19 16:09:17.351 Copyright (C) 2018 DVSwitch, INAD.
it looks like on github is the version which I have download 14
November
On Mon, Nov 18, 2019 at 10:18 AM, Steve N4IRS wrote:
I have pushed the update to Analog_Bridge for all
architectures to github. <https://github.com/DVSwitch/Analog_Bridge>
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL
Steve
I have updated Ananlog_Bridge i386 (github show that file was updated 22 hours) but in log show me
I: 2019-11-19 16:09:17.351 Analog Bridge Version 1.4.1 Mon Nov 11 14:23:21 EST 2019 I: 2019-11-19 16:09:17.351 Copyright (C) 2018 DVSwitch, INAD.
it looks like on github is the version which I have download 14 November
toggle quoted messageShow quoted text
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL
So far, the new version of Analog_Bridge, connected to a remote
AMBEserver, is working well. I've had it up for a few hours with a
reasonable amount of cross-mode traffic, and it hasn't fallen over
yet. Sometimes, with the old version, it wouldn't last an hour
with heavy traffic. I'll report back if this changes.
toggle quoted messageShow quoted text
On 11/18/2019 1:18 PM, Steve N4IRS
wrote:
I have pushed the update to Analog_Bridge for all architectures to
github. <https://github.com/DVSwitch/Analog_Bridge>
Steve N4IRS
On 11/18/2019 11:23 AM, Mike Zingman
- N4IRR wrote:
Partick,
I just wanted to say thank you! I decided to go back and
inspect the code for UDP encode and decode to a remote AMBE
server. What I found was that there was an error in the logic
that was causing your AB to stop listening for new packets from
the remote server. I have fixed that error and when Steve
releases a new build to github, I would love for you to re-test
and verify that you no longer have to stop and start your AB
instance on regular intervals.
However, the architecture that Steve pointed you at will also
work and you may want to implement that anyway. Your call.
Again, thank you!
Mike N4IRR
|
|
After several weeks testing and check I am near to goal installing Dmrlink in following way:
(snipping commands to install all python library needed...)
"sudo python -m pip install --user dmr_utils"
I found that normal commands to install dmr_utils python library seems not working
you can try to use folowing commands too:
git clone https://github.com/n0mjs710/dmr_utils.git cd dmr_utils/ pip install .
Using mk\sh didn't work for me.
73
|
|
Re: DMR to YSF Weird Issue

Dexter Harroo
toggle quoted messageShow quoted text
On Mon, Nov 18, 2019, 2:26 PM Steve N4IRS < szingman@...> wrote:
amd64. See below.
On 11/18/2019 1:22 PM, Dexter Harroo
wrote:
4.9.0-11-amd64 #1 SMP Debian
4.9.189-3+deb9ul (2019-9-20) x86_GNU/Linux
On Mon, Nov 18, 2019 at 1:25
PM Steve N4IRS < szingman@...> wrote:
What is the result of uname -a?
On 11/18/2019 12:23 PM, Dexter Harroo wrote:
my processor is intel xeon 3430, which
package should i download?
On Mon, Nov 11, 2019
at 7:52 PM Steve N4IRS < szingman@...>
wrote:
<https://dvswitch.groups.io/g/main/message/5289>
On 11/11/19 5:28 PM, Dexter Harroo wrote:
What did you do to resolve the
issue? I seem to be having the same problem
Actually, I think I got it
Steve. The logs are back to normal. Thanks
so much for the guidance. So the executable
that I was running, I take it that must have
been an older one?
On Fri,
Nov 8, 2019 at 10:40 PM Jake Litwin via
Groups.Io <litwinjwi= gmail.com@groups.io>
wrote:
Thanks Steve
All seems to be working on the
mobiles now but I'm seeing this
output in the logs. Is this
normal?
: 2019-11-09
04:39:31.410 YSF, received
network data from N7VDR/JIMI
to ALL at N7VDR
I: 2019-11-09
04:39:31.410 YSF, Lookup call
N7VDR returned id 3108345
-> 3108345
M: 2019-11-09
04:39:31.415 DMR, TX state =
ON
I: 2019-11-09
04:39:31.415 DMR, Begin TX:
src=3108345 rpt=0 dst=420
slot=2 cc=0 metadata=N7VDR
D: 2019-11-09
04:39:32.041 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:32.041 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.134 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:32.134 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:32.833 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:32.833 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.941 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:32.941 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:33.639 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:33.639 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:33.736 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:33.736 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:34.437 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:34.437 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:34.534 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:34.534 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:35.263 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:35.263 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:35.340 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:35.340 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.032 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:36.032 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:36.136 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:36.136 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.839 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:36.839 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
M: 2019-11-09
04:39:36.932 YSF, received
network end of transmission,
5.7 seconds, 0% packet loss,
BER: 0.0%
M: 2019-11-09
04:39:36.937 DMR, TX state =
OFF, DMR frame count was 93
frames
M: 2019-11-09
04:39:39.645 YSF, received
network data from WD0HDR/DAV
to ALL at WD0HDR
I: 2019-11-09
04:39:39.645 YSF, Lookup call
WD0HDR returned id 3108613
-> 3108613
M: 2019-11-09
04:39:39.650 DMR, TX state =
ON
I: 2019-11-09
04:39:39.651 DMR, Begin TX:
src=3108613 rpt=0 dst=420
slot=2 cc=0 metadata=WD0HDR
D: 2019-11-09
04:39:40.343 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:40.344 0000: 2F 22 62
5F 25 54 30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:40.462 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:40.462 0000: 59 70 46
5D 6C 20 50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.158 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:41.158 0000: 2F 22 62
5F 25 54 30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:41.246 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:41.246 0000: 59 70 46
5D 6C 20 50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.943 V/D Mode 2 Data,
DT1
On
Fri, Nov 8, 2019 at 10:13 PM Steve
N4IRS < szingman@...>
wrote:
There
is no TX offset on s bridge.
Sent
via smoke signal (AT&T)
Try adjusting TX offset in
modem section to suit all.
On 9/11/19 1:53 pm, Jake
Litwin wrote:
Just
curious to see if anyone has
experienced this.. I have YSF
bridged to DMR with MMDVM with
the instructions provided here
on the DVSwitch group.
Everything seems to be fine
except when mobile YSF radios
receive a transmission from the
DMR side, there's only about a
second or two of audio and then
nothing. The blue light on the
YSF mobile blinks. YSF handhelds
like the FT-3's, FT-2's, receive
DMR just fine without any
issues. Not sure why my setup
would be affecting the mobile
YSF radios only and not the YSF
handhelds.
--
--
|
|
Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.
I am sorry to say all I have is dmr and ysf no luck on dstar
toggle quoted messageShow quoted text
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Tom Corcoran Sent: Monday, November 18, 2019 9:48 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you. Hello Charles,
what modes are using? I have DMR, YSF & P25 up but not luck with NXDN or DStar yet Also, I found Debian 9 seemed to be the only version that worked. Your experience? -- Tom VE3NY
|
|
Re: DMR to YSF Weird Issue

Steve N4IRS
amd64. See below.
toggle quoted messageShow quoted text
On 11/18/2019 1:22 PM, Dexter Harroo
wrote:
4.9.0-11-amd64 #1 SMP Debian
4.9.189-3+deb9ul (2019-9-20) x86_GNU/Linux
On Mon, Nov 18, 2019 at 1:25
PM Steve N4IRS < szingman@...> wrote:
What is the result of uname -a?
On 11/18/2019 12:23 PM, Dexter Harroo wrote:
my processor is intel xeon 3430, which
package should i download?
On Mon, Nov 11, 2019
at 7:52 PM Steve N4IRS < szingman@...>
wrote:
<https://dvswitch.groups.io/g/main/message/5289>
On 11/11/19 5:28 PM, Dexter Harroo wrote:
What did you do to resolve the
issue? I seem to be having the same problem
Actually, I think I got it
Steve. The logs are back to normal. Thanks
so much for the guidance. So the executable
that I was running, I take it that must have
been an older one?
On Fri,
Nov 8, 2019 at 10:40 PM Jake Litwin via
Groups.Io <litwinjwi= gmail.com@groups.io>
wrote:
Thanks Steve
All seems to be working on the
mobiles now but I'm seeing this
output in the logs. Is this
normal?
: 2019-11-09
04:39:31.410 YSF, received
network data from N7VDR/JIMI
to ALL at N7VDR
I: 2019-11-09
04:39:31.410 YSF, Lookup call
N7VDR returned id 3108345
-> 3108345
M: 2019-11-09
04:39:31.415 DMR, TX state =
ON
I: 2019-11-09
04:39:31.415 DMR, Begin TX:
src=3108345 rpt=0 dst=420
slot=2 cc=0 metadata=N7VDR
D: 2019-11-09
04:39:32.041 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:32.041 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.134 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:32.134 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:32.833 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:32.833 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.941 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:32.941 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:33.639 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:33.639 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:33.736 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:33.736 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:34.437 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:34.437 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:34.534 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:34.534 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:35.263 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:35.263 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:35.340 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:35.340 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.032 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:36.032 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:36.136 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:36.136 0000: 55 71 5F
2F 6C 21 52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.839 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:36.839 0000: 1D 22 62
5F 29 54 30 53 52 52
*."b_)T0SRR*
M: 2019-11-09
04:39:36.932 YSF, received
network end of transmission,
5.7 seconds, 0% packet loss,
BER: 0.0%
M: 2019-11-09
04:39:36.937 DMR, TX state =
OFF, DMR frame count was 93
frames
M: 2019-11-09
04:39:39.645 YSF, received
network data from WD0HDR/DAV
to ALL at WD0HDR
I: 2019-11-09
04:39:39.645 YSF, Lookup call
WD0HDR returned id 3108613
-> 3108613
M: 2019-11-09
04:39:39.650 DMR, TX state =
ON
I: 2019-11-09
04:39:39.651 DMR, Begin TX:
src=3108613 rpt=0 dst=420
slot=2 cc=0 metadata=WD0HDR
D: 2019-11-09
04:39:40.343 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:40.344 0000: 2F 22 62
5F 25 54 30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:40.462 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:40.462 0000: 59 70 46
5D 6C 20 50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.158 V/D Mode 2 Data,
DT1
D: 2019-11-09
04:39:41.158 0000: 2F 22 62
5F 25 54 30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:41.246 V/D Mode 2 Data,
DT2
D: 2019-11-09
04:39:41.246 0000: 59 70 46
5D 6C 20 50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.943 V/D Mode 2 Data,
DT1
On
Fri, Nov 8, 2019 at 10:13 PM Steve
N4IRS < szingman@...>
wrote:
There
is no TX offset on s bridge.
Sent
via smoke signal (AT&T)
Try adjusting TX offset in
modem section to suit all.
On 9/11/19 1:53 pm, Jake
Litwin wrote:
Just
curious to see if anyone has
experienced this.. I have YSF
bridged to DMR with MMDVM with
the instructions provided here
on the DVSwitch group.
Everything seems to be fine
except when mobile YSF radios
receive a transmission from the
DMR side, there's only about a
second or two of audio and then
nothing. The blue light on the
YSF mobile blinks. YSF handhelds
like the FT-3's, FT-2's, receive
DMR just fine without any
issues. Not sure why my setup
would be affecting the mobile
YSF radios only and not the YSF
handhelds.
--
--
|
|
Re: DMR to YSF Weird Issue

Dexter Harroo
4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9ul (2019-9-20) x86_GNU/Linux
toggle quoted messageShow quoted text
On Mon, Nov 18, 2019 at 1:25 PM Steve N4IRS < szingman@...> wrote:
What is the result of uname -a?
On 11/18/2019 12:23 PM, Dexter Harroo
wrote:
my processor is intel xeon 3430, which package
should i download?
On Mon, Nov 11, 2019 at 7:52
PM Steve N4IRS < szingman@...> wrote:
<https://dvswitch.groups.io/g/main/message/5289>
On 11/11/19 5:28 PM, Dexter Harroo wrote:
What did you do to resolve the issue? I
seem to be having the same problem
Actually, I think I got it Steve. The
logs are back to normal. Thanks so much for the
guidance. So the executable that I was running, I
take it that must have been an older one?
On Fri, Nov 8,
2019 at 10:40 PM Jake Litwin via Groups.Io
<litwinjwi= gmail.com@groups.io>
wrote:
Thanks Steve
All seems to be working on the mobiles
now but I'm seeing this output in the
logs. Is this normal?
: 2019-11-09
04:39:31.410 YSF, received network
data from N7VDR/JIMI to ALL at
N7VDR
I: 2019-11-09
04:39:31.410 YSF, Lookup call N7VDR
returned id 3108345 -> 3108345
M: 2019-11-09
04:39:31.415 DMR, TX state = ON
I: 2019-11-09
04:39:31.415 DMR, Begin TX:
src=3108345 rpt=0 dst=420 slot=2 cc=0
metadata=N7VDR
D: 2019-11-09
04:39:32.041 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:32.041 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.134 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:32.134 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:32.833 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:32.833 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.941 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:32.941 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:33.639 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:33.639 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:33.736 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:33.736 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:34.437 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:34.437 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:34.534 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:34.534 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:35.263 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:35.263 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:35.340 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:35.340 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.032 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:36.032 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:36.136 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:36.136 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.839 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:36.839 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
M: 2019-11-09
04:39:36.932 YSF, received network end
of transmission, 5.7 seconds, 0%
packet loss, BER: 0.0%
M: 2019-11-09
04:39:36.937 DMR, TX state = OFF, DMR
frame count was 93 frames
M: 2019-11-09
04:39:39.645 YSF, received network
data from WD0HDR/DAV to ALL at
WD0HDR
I: 2019-11-09
04:39:39.645 YSF, Lookup call WD0HDR
returned id 3108613 -> 3108613
M: 2019-11-09
04:39:39.650 DMR, TX state = ON
I: 2019-11-09
04:39:39.651 DMR, Begin TX:
src=3108613 rpt=0 dst=420 slot=2 cc=0
metadata=WD0HDR
D: 2019-11-09
04:39:40.343 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:40.344 0000: 2F 22 62 5F 25 54
30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:40.462 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:40.462 0000: 59 70 46 5D 6C 20
50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.158 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:41.158 0000: 2F 22 62 5F 25 54
30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:41.246 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:41.246 0000: 59 70 46 5D 6C 20
50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.943 V/D Mode 2 Data, DT1
On Fri, Nov 8,
2019 at 10:13 PM Steve N4IRS < szingman@...>
wrote:
There
is no TX offset on s bridge.
Sent
via smoke signal (AT&T)
Try adjusting TX offset in modem
section to suit all.
On 9/11/19 1:53 pm, Jake Litwin
wrote:
Just curious to
see if anyone has experienced this.. I
have YSF bridged to DMR with MMDVM with
the instructions provided here on the
DVSwitch group. Everything seems to be
fine except when mobile YSF radios
receive a transmission from the DMR
side, there's only about a second or two
of audio and then nothing. The blue
light on the YSF mobile blinks. YSF
handhelds like the FT-3's, FT-2's,
receive DMR just fine without any
issues. Not sure why my setup would be
affecting the mobile YSF radios only and
not the YSF handhelds.
--
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL

Steve N4IRS
toggle quoted messageShow quoted text
On 11/18/2019 11:23 AM, Mike Zingman -
N4IRR wrote:
Partick,
I just wanted to say thank you! I decided to go back and inspect
the code for UDP encode and decode to a remote AMBE server. What
I found was that there was an error in the logic that was causing
your AB to stop listening for new packets from the remote server.
I have fixed that error and when Steve releases a new build to
github, I would love for you to re-test and verify that you no
longer have to stop and start your AB instance on regular
intervals.
However, the architecture that Steve pointed you at will also work
and you may want to implement that anyway. Your call.
Again, thank you!
Mike N4IRR
|
|
Re: DMR to YSF Weird Issue

Steve N4IRS
What is the result of uname -a?
toggle quoted messageShow quoted text
On 11/18/2019 12:23 PM, Dexter Harroo
wrote:
my processor is intel xeon 3430, which package
should i download?
On Mon, Nov 11, 2019 at 7:52
PM Steve N4IRS < szingman@...> wrote:
<https://dvswitch.groups.io/g/main/message/5289>
On 11/11/19 5:28 PM, Dexter Harroo wrote:
What did you do to resolve the issue? I
seem to be having the same problem
Actually, I think I got it Steve. The
logs are back to normal. Thanks so much for the
guidance. So the executable that I was running, I
take it that must have been an older one?
On Fri, Nov 8,
2019 at 10:40 PM Jake Litwin via Groups.Io
<litwinjwi= gmail.com@groups.io>
wrote:
Thanks Steve
All seems to be working on the mobiles
now but I'm seeing this output in the
logs. Is this normal?
: 2019-11-09
04:39:31.410 YSF, received network
data from N7VDR/JIMI to ALL at
N7VDR
I: 2019-11-09
04:39:31.410 YSF, Lookup call N7VDR
returned id 3108345 -> 3108345
M: 2019-11-09
04:39:31.415 DMR, TX state = ON
I: 2019-11-09
04:39:31.415 DMR, Begin TX:
src=3108345 rpt=0 dst=420 slot=2 cc=0
metadata=N7VDR
D: 2019-11-09
04:39:32.041 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:32.041 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.134 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:32.134 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:32.833 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:32.833 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:32.941 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:32.941 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:33.639 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:33.639 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:33.736 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:33.736 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:34.437 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:34.437 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:34.534 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:34.534 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:35.263 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:35.263 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:35.340 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:35.340 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.032 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:36.032 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
D: 2019-11-09
04:39:36.136 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:36.136 0000: 55 71 5F 2F 6C 21
52 20 03 FA
*Uq_/l!R ..*
D: 2019-11-09
04:39:36.839 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:36.839 0000: 1D 22 62 5F 29 54
30 53 52 52
*."b_)T0SRR*
M: 2019-11-09
04:39:36.932 YSF, received network end
of transmission, 5.7 seconds, 0%
packet loss, BER: 0.0%
M: 2019-11-09
04:39:36.937 DMR, TX state = OFF, DMR
frame count was 93 frames
M: 2019-11-09
04:39:39.645 YSF, received network
data from WD0HDR/DAV to ALL at
WD0HDR
I: 2019-11-09
04:39:39.645 YSF, Lookup call WD0HDR
returned id 3108613 -> 3108613
M: 2019-11-09
04:39:39.650 DMR, TX state = ON
I: 2019-11-09
04:39:39.651 DMR, Begin TX:
src=3108613 rpt=0 dst=420 slot=2 cc=0
metadata=WD0HDR
D: 2019-11-09
04:39:40.343 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:40.344 0000: 2F 22 62 5F 25 54
30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:40.462 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:40.462 0000: 59 70 46 5D 6C 20
50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.158 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:41.158 0000: 2F 22 62 5F 25 54
30 52 52 59
*/"b_%T0RRY*
D: 2019-11-09
04:39:41.246 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:41.246 0000: 59 70 46 5D 6C 20
50 20 03 23
*YpF]l P .#*
D: 2019-11-09
04:39:41.943 V/D Mode 2 Data, DT1
On Fri, Nov 8,
2019 at 10:13 PM Steve N4IRS < szingman@...>
wrote:
There
is no TX offset on s bridge.
Sent
via smoke signal (AT&T)
Try adjusting TX offset in modem
section to suit all.
On 9/11/19 1:53 pm, Jake Litwin
wrote:
Just curious to
see if anyone has experienced this.. I
have YSF bridged to DMR with MMDVM with
the instructions provided here on the
DVSwitch group. Everything seems to be
fine except when mobile YSF radios
receive a transmission from the DMR
side, there's only about a second or two
of audio and then nothing. The blue
light on the YSF mobile blinks. YSF
handhelds like the FT-3's, FT-2's,
receive DMR just fine without any
issues. Not sure why my setup would be
affecting the mobile YSF radios only and
not the YSF handhelds.
--
|
|
Re: DMR to YSF Weird Issue

Dexter Harroo
my processor is intel xeon 3430, which package should i download?
toggle quoted messageShow quoted text
On Mon, Nov 11, 2019 at 7:52 PM Steve N4IRS < szingman@...> wrote:
<https://dvswitch.groups.io/g/main/message/5289>
On 11/11/19 5:28 PM, Dexter Harroo
wrote:
What did you do to resolve the issue? I seem to be
having the same problem
Actually, I think I got it Steve. The logs are
back to normal. Thanks so much for the guidance. So the
executable that I was running, I take it that must have been
an older one?
On Fri, Nov 8, 2019 at
10:40 PM Jake Litwin via Groups.Io <litwinjwi= gmail.com@groups.io>
wrote:
Thanks Steve
All seems to be working on the mobiles now but
I'm seeing this output in the logs. Is this
normal?
: 2019-11-09
04:39:31.410 YSF, received network data from
N7VDR/JIMI to ALL at N7VDR
I: 2019-11-09
04:39:31.410 YSF, Lookup call N7VDR returned
id 3108345 -> 3108345
M: 2019-11-09
04:39:31.415 DMR, TX state = ON
I: 2019-11-09
04:39:31.415 DMR, Begin TX: src=3108345 rpt=0
dst=420 slot=2 cc=0 metadata=N7VDR
D: 2019-11-09
04:39:32.041 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:32.041 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
D: 2019-11-09
04:39:32.134 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:32.134 0000: 55 71 5F 2F 6C 21 52 20 03
FA *Uq_/l!R ..*
D: 2019-11-09
04:39:32.833 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:32.833 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
D: 2019-11-09
04:39:32.941 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:32.941 0000: 55 71 5F 2F 6C 21 52 20 03
FA *Uq_/l!R ..*
D: 2019-11-09
04:39:33.639 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:33.639 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
D: 2019-11-09
04:39:33.736 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:33.736 0000: 55 71 5F 2F 6C 21 52 20 03
FA *Uq_/l!R ..*
D: 2019-11-09
04:39:34.437 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:34.437 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
D: 2019-11-09
04:39:34.534 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:34.534 0000: 55 71 5F 2F 6C 21 52 20 03
FA *Uq_/l!R ..*
D: 2019-11-09
04:39:35.263 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:35.263 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
D: 2019-11-09
04:39:35.340 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:35.340 0000: 55 71 5F 2F 6C 21 52 20 03
FA *Uq_/l!R ..*
D: 2019-11-09
04:39:36.032 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:36.032 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
D: 2019-11-09
04:39:36.136 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:36.136 0000: 55 71 5F 2F 6C 21 52 20 03
FA *Uq_/l!R ..*
D: 2019-11-09
04:39:36.839 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:36.839 0000: 1D 22 62 5F 29 54 30 53 52
52 *."b_)T0SRR*
M: 2019-11-09
04:39:36.932 YSF, received network end of
transmission, 5.7 seconds, 0% packet loss,
BER: 0.0%
M: 2019-11-09
04:39:36.937 DMR, TX state = OFF, DMR frame
count was 93 frames
M: 2019-11-09
04:39:39.645 YSF, received network data from
WD0HDR/DAV to ALL at WD0HDR
I: 2019-11-09
04:39:39.645 YSF, Lookup call WD0HDR returned
id 3108613 -> 3108613
M: 2019-11-09
04:39:39.650 DMR, TX state = ON
I: 2019-11-09
04:39:39.651 DMR, Begin TX: src=3108613 rpt=0
dst=420 slot=2 cc=0 metadata=WD0HDR
D: 2019-11-09
04:39:40.343 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:40.344 0000: 2F 22 62 5F 25 54 30 52 52
59 */"b_%T0RRY*
D: 2019-11-09
04:39:40.462 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:40.462 0000: 59 70 46 5D 6C 20 50 20 03
23 *YpF]l P .#*
D: 2019-11-09
04:39:41.158 V/D Mode 2 Data, DT1
D: 2019-11-09
04:39:41.158 0000: 2F 22 62 5F 25 54 30 52 52
59 */"b_%T0RRY*
D: 2019-11-09
04:39:41.246 V/D Mode 2 Data, DT2
D: 2019-11-09
04:39:41.246 0000: 59 70 46 5D 6C 20 50 20 03
23 *YpF]l P .#*
D: 2019-11-09
04:39:41.943 V/D Mode 2 Data, DT1
On Fri, Nov 8, 2019 at
10:13 PM Steve N4IRS < szingman@...>
wrote:
There
is no TX offset on s bridge.
Sent
via smoke signal (AT&T)
Try adjusting TX offset in modem section to
suit all.
On 9/11/19 1:53 pm, Jake Litwin wrote:
Just curious to see if
anyone has experienced this.. I have YSF bridged
to DMR with MMDVM with the instructions provided
here on the DVSwitch group. Everything seems to
be fine except when mobile YSF radios receive a
transmission from the DMR side, there's only
about a second or two of audio and then nothing.
The blue light on the YSF mobile blinks. YSF
handhelds like the FT-3's, FT-2's, receive DMR
just fine without any issues. Not sure why my
setup would be affecting the mobile YSF radios
only and not the YSF handhelds.
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL
Mike:
I'll probably end up implementing another instance of ASL, but testing that once it's available is easier in the short-term. So, I'll do that, too.
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL

Mike Zingman - N4IRR
Partick,
I just wanted to say thank you! I decided to go back and inspect the code for UDP encode and decode to a remote AMBE server. What I found was that there was an error in the logic that was causing your AB to stop listening for new packets from the remote server. I have fixed that error and when Steve releases a new build to github, I would love for you to re-test and verify that you no longer have to stop and start your AB instance on regular intervals.
However, the architecture that Steve pointed you at will also work and you may want to implement that anyway. Your call.
Again, thank you! Mike N4IRR
|
|
Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Steve N4IRS
Debian 8, 9 or 10 should be fine. Let me know of problems so I can
test and fix.
Steve
toggle quoted messageShow quoted text
On 11/18/2019 10:48 AM, Tom Corcoran
wrote:
Hello Charles,
what modes are using? I have DMR, YSF & P25 up but not luck
with NXDN or DStar yet
Also, I found Debian 9 seemed to be the only version that
worked. Your experience?
--
Tom VE3NY
|
|
Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Tom Corcoran
Hello Charles,
what modes are using? I have DMR, YSF & P25 up but not luck with NXDN or DStar yet
Also, I found Debian 9 seemed to be the only version that worked. Your experience? -- Tom VE3NY
|
|
Re: Analog_Bridge, one-way audio from DMR to ASL
Sounds reasonable. As I am moving soon, I'll set up an identical
private node with a second AMBE dongle in another location, then
just switch to that for the duration of downtime.
toggle quoted messageShow quoted text
On 11/17/2019 8:09 PM, Steve N4IRS
wrote:
I'm going to suggest a alternative configuration.
Put your public ASL node on your VPS No radio interface needed.
Setup a private node at your house. Add AB, MB etc. Setup a full
time IAX connection between the 2 nodes.
Done...
On 11/17/19 7:43 PM, Mike Zingman -
N4IRR wrote:
Here is what I suspect (of course I could be wrong). USRP uses
UDP as its transport.
If you are using DVSM, you set the mobile client to talk to AB
on a single port. This setting in AB (where TX and RX ports are
the same) tells AB to use an enhanced protocol to talk to the
client. This enhancement is used to keep the NAT traversal path
open to the client. The trick is that AB will send keep alive
packets back to DVSM to tell the router/firewall that the NAT
connection should be maintained. As long as the keep alive
packets are sent often enough the router will maintain the
connection.
If you are using ASL as your USRP client to AB, you are using
two ports (TX and RX). AB does not try to tell ASL to keep
the connection open (since ASL would not understand the keep
alives). So, if you are using ASL on a different machine than
AB and there is a NAT between them, you will have problems.
Any of the above make sense?
|
|