Date   

Re: MMDVM_BRIDGE Not Starting

fabio damiani
 

My raspberry PI3B+   armv7l.     File download is  https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.armv6l   ?


Re: Analog_Bridge remote control (TLV) commands exposed.

Steve N4IRS
 

We have pushed the initial of dvswitch.sh (V1.4) to the github repository for Analog_Bridge <https://github.com/DVSwitch/Analog_Bridge>
The example configuration files for ASL have been updated to reflect using the new script to change modes and TG/Reflectors.
We have also updated all binaries for Analog_Bridge and MMDVM_Bridge. In the future (Starting in December), We will update all of the apt packages for the DVSwitch programs. We will do this once a month.
In December, we will be adding a number of "support" programs that DVSwitch uses to github and the apt repository.

Please test out the new script and binaries. We need to hear of any issues that crop up BEFORE they are pushed to apt.

For DVSwitch,
Steve N4IRS and Mike N4IRR 


Re: Analog_Bridge remote control (TLV) commands exposed.

Steve N4IRS
 

Waldek,
I have pushed the initial release of dvswitch.sh to github.

73, Steve N4IRS

On 11/6/2019 4:36 AM, Waldek SP2ONG wrote:
Steve,

Thanks for updates Ananlog_Bridge and MMDVM_Brideg.

the script dvswitch.sh script not yet available?


On Tue, Nov 5, 2019 at 09:49 AM, Steve N4IRS wrote:
dvswitch.sh


Re: MMDVM_BRIDGE Not Starting

Steve N4IRS
 

Port= =/dev/null
Remove the second "=" and retest

On 11/6/2019 8:14 AM, fabio damiani wrote:
[General]
Callsign=IZ2BKS
Id=2222158
Timeout=180
Duplex=0
 
[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port= =/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=C
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=0
 
[P25]
Enable=0
NAC=293
 
[NXDN]
Enable=0
RAN=1
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0
 
[DMR Network]
Enable=1
Address=212.237.14.126
Port=62031
Jitter=360
Local=62032
Password=radioamatore
Slot1=1
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020
 


Re: MMDVM_BRIDGE Not Starting

fabio damiani
 
Edited

[General]
Callsign=IZ2BKS
Id=2222158
Timeout=180
Duplex=0
 
[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port= /dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=C
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=0
 
[P25]
Enable=0
NAC=293
 
[NXDN]
Enable=0
RAN=1
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0
 
[DMR Network]
Enable=1
Address=212.237.14.126
Port=62031
Jitter=360
Local=62032
Password=radioamatore
Slot1=1
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020
 


Re: MMDVM_BRIDGE Not Starting

Steve N4IRS
 

Fabio,
I'm going to guess here:
In MMDVM_Bridge.ini
In the [Modem] stanza
set Port=/dev/null

If this does not work, please post your MMDVM_Bridge.ini

73, Steve N4IRS

On 11/6/2019 7:17 AM, fabio damiani wrote:
Thanks, a problem solved, but the troubles never come alone! this is another problem.

pi@raspberrypi:/opt/MMDVM_Bridge $ ./MMDVM_Bridge DVSwitch.ini
MMDVM_Bridge: SerialController.cpp:230: CSerialController::CSerialController(const string&, SERIAL_SPEED, bool): Assertion `!device.empty()' failed.
Aborted
 


Re: MMDVM_BRIDGE Not Starting

Brad N8PC
 

Try cd /opt/MMDVM_Bridge first then run ./MMDVM_Bridge MMDVM_Bridge.ini you need to be in that directory to run it.


On Wed, Nov 6, 2019, 12:22 AM fabio damiani <iz2bks@...> wrote:
root@raspberrypi:/opt/MMDVM_Bridge# ./MMDVM_Bridge MMDVM_Bridge.ini
./MMDVM_Bridge: line 1: !DOCTYPE: No such file or directory
./MMDVM_Bridge: line 2: html: No such file or directory
./MMDVM_Bridge: line 3: head: No such file or directory
./MMDVM_Bridge: line 4: meta: No such file or directory
./MMDVM_Bridge: line 5: meta: No such file or directory
./MMDVM_Bridge: line 6: meta: No such file or directory
./MMDVM_Bridge: line 7: !--: No such file or directory
./MMDVM_Bridge: line 8: meta: No such file or directory
./MMDVM_Bridge: line 9: $'\r': command not found
./MMDVM_Bridge: line 10: meta: No such file or directory
./MMDVM_Bridge: line 11: meta: No such file or directory
./MMDVM_Bridge: line 12: meta: No such file or directory
./MMDVM_Bridge: line 13: $'\r': command not found
./MMDVM_Bridge: line 14: base: No such file or directory
./MMDVM_Bridge: line 15: syntax error near unexpected token `<'
'/MMDVM_Bridge: line 15: `        <!--[if lt IE 10]><script type="text/javascript">
root@raspberrypi:/opt/MMDVM_Bridge#
 


Re: MMDVM_BRIDGE Not Starting

fabio damiani
 

Thanks, a problem solved, but the troubles never come alone! this is another problem.

pi@raspberrypi:/opt/MMDVM_Bridge $ ./MMDVM_Bridge DVSwitch.ini
MMDVM_Bridge: SerialController.cpp:230: CSerialController::CSerialController(const string&, SERIAL_SPEED, bool): Assertion `!device.empty()' failed.
Aborted
 


Re: Analog_Bridge remote control (TLV) commands exposed.

Steve N4IRS
 

Waldek,
We have a few additions to make. I will push it to github in the next day or so.

73, Steve

On 11/6/19 4:36 AM, Waldek SP2ONG wrote:
Steve,

Thanks for updates Ananlog_Bridge and MMDVM_Brideg.

the script dvswitch.sh script not yet available?


On Tue, Nov 5, 2019 at 09:49 AM, Steve N4IRS wrote:
dvswitch.sh


Re: Analog_Bridge remote control (TLV) commands exposed.

SP2ONG Waldek
 

Steve,

Thanks for updates Ananlog_Bridge and MMDVM_Brideg.

the script dvswitch.sh script not yet available?


On Tue, Nov 5, 2019 at 09:49 AM, Steve N4IRS wrote:
dvswitch.sh


Re: MMDVM_BRIDGE Not Starting

SP2ONG Waldek
 

Hi Fabio

It looks like you have download not correctly binary file

Try download

wget https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.armhf

or

wget  https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.armv6l

depends on your RPI version


Re: MMDVM_BRIDGE Not Starting

fabio damiani
 

root@raspberrypi:/opt/MMDVM_Bridge# ./MMDVM_Bridge MMDVM_Bridge.ini
./MMDVM_Bridge: line 1: !DOCTYPE: No such file or directory
./MMDVM_Bridge: line 2: html: No such file or directory
./MMDVM_Bridge: line 3: head: No such file or directory
./MMDVM_Bridge: line 4: meta: No such file or directory
./MMDVM_Bridge: line 5: meta: No such file or directory
./MMDVM_Bridge: line 6: meta: No such file or directory
./MMDVM_Bridge: line 7: !--: No such file or directory
./MMDVM_Bridge: line 8: meta: No such file or directory
./MMDVM_Bridge: line 9: $'\r': command not found
./MMDVM_Bridge: line 10: meta: No such file or directory
./MMDVM_Bridge: line 11: meta: No such file or directory
./MMDVM_Bridge: line 12: meta: No such file or directory
./MMDVM_Bridge: line 13: $'\r': command not found
./MMDVM_Bridge: line 14: base: No such file or directory
./MMDVM_Bridge: line 15: syntax error near unexpected token `<'
'/MMDVM_Bridge: line 15: `        <!--[if lt IE 10]><script type="text/javascript">
root@raspberrypi:/opt/MMDVM_Bridge#
 


Re: MMDVM_BRIDGE Not Starting

Steve N4IRS
 

Try this as root:
cd /opt/MMDVM_Bridge
,/MMDVM_Bridge MMDVM_Bridge.ini

Please report the results.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of fabio damiani <iz2bks@...>
Sent: Tuesday, November 5, 2019 5:17:43 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] MMDVM_BRIDGE Not Starting
 
Hi everyone, I need a favor, I installed on raspberry DV-Switch, but the MMDVM_BRIDGE does not start and gives me this error.

mmdvm_bridge.service - MMDVM_Bridge Service
   Loaded: loaded (/lib/systemd/system/mmdvm_bridge.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-11-05 22:11:44 GMT; 18s ago
  Process: 551 ExecStart=/opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini (code=exited, status=203/EXEC)
 Main PID: 551 (code=exited, status=203/EXEC)
 
Nov 05 22:11:44 raspberrypi systemd[1]: Started MMDVM_Bridge Service.
Nov 05 22:11:44 raspberrypi systemd[1]: mmdvm_bridge.service: Main process exited, code=exited, status=203/EXEC
Nov 05 22:11:44 raspberrypi systemd[1]: mmdvm_bridge.service: Unit entered failed state.
Nov 05 22:11:44 raspberrypi systemd[1]: mmdvm_bridge.service: Failed with result 'exit-code'.
root@raspberrypi:~#
Thanks for help


MMDVM_BRIDGE Not Starting

fabio damiani
 

Hi everyone, I need a favor, I installed on raspberry DV-Switch, but the MMDVM_BRIDGE does not start and gives me this error.

mmdvm_bridge.service - MMDVM_Bridge Service
   Loaded: loaded (/lib/systemd/system/mmdvm_bridge.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-11-05 22:11:44 GMT; 18s ago
  Process: 551 ExecStart=/opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini (code=exited, status=203/EXEC)
 Main PID: 551 (code=exited, status=203/EXEC)
 
Nov 05 22:11:44 raspberrypi systemd[1]: Started MMDVM_Bridge Service.
Nov 05 22:11:44 raspberrypi systemd[1]: mmdvm_bridge.service: Main process exited, code=exited, status=203/EXEC
Nov 05 22:11:44 raspberrypi systemd[1]: mmdvm_bridge.service: Unit entered failed state.
Nov 05 22:11:44 raspberrypi systemd[1]: mmdvm_bridge.service: Failed with result 'exit-code'.
root@raspberrypi:~#
Thanks for help


Re: Analog_Bridge remote control (TLV) commands exposed.

Steve N4IRS
 

I have received a few direct questions about this topic. I would prefer questions be asked here so all can learn from the question / answer but I'll try to cover the subject here.

Some people are under the impression that the changes to Analog_Bridge and the addition of dvswitch.sh are for DVSwitch Mobile(DVSM) and USRP Client(UC). This could not be further from the truth. The first version of Analog_Bridge was built to provide a method of bridging AllStarLink(ASL) to the DMR networks. Analog_Bridge has it's roots in ASL and we always consider the impact of any change.

I believe most of the ASL to Digital bridges in use today are single mode. I expect mostly DMR but I'm sure there are other modes in use. To build a multi-mode ASL bridge required some script  jiu jitsu to change modes. The same method I used for the example multi-mode DVSM was used to change modes in a ASL to Digital bridge.
Create 5 copies of Analog_Bridge.ini (DMR.ini, YSF.ini, NXDN.ini, P25INI and DSTAR.ini
Edit each mode ini file to reflect the mode. Don't forget to set the TX and RX ports to match those defined in DVSwitch.ini.
Create 5 macros for ASL that copies the proper .ini file over Analog_Bridge.ini and restart Analog_Bridge.
Not elegant, but it works. I'll say it again, don't forget to set the proper TX and RX ports! 

Now let's do the same thing with dvswitch.sh:
Create 5 macros in ASL, each with a a single command and a parameter. dvswitch.sh mode DMR or dvswitch.sh mode YSF. You get the idea.
That's it. dvswitch.sh will read DVSwitch.ini then find the desired mode. dvswitch.sh will tell Analog_Bridge to change mode and ports to match the running instance of MMDVM_Bridge. That's it, you are now on a new mode.
So, you want to change to a different Talk Group or Reflector? Create a macro for ASL with the command dvswitch.sh tune 3112138 or dvswitch.sh tune ysfreflector.net:42000 and you are on the new Talk Group or Reflector.

Now let's get cute. I want ASL to tell me what mode and TG it's currently pointed at. dvswitch.sh is your friend here too. I won't build the whole script but in pseudo code:
ask dvswitch the current mode with dvswitch.sh mode (no parameter)
ask dvswitch.sh the current Talk Group with dvswitch.sh tune (no parameter)
take the results of those 2 commands and ask ASL to say "tuned to Talk Group $tg on mode $mode"

You get the idea. 

As we move forward with the fork of AllStarLink, we will expand the ability of AllStarLink to interact with Analog_Bridge. The first project will be to expand chan_usrp. The channel driver is simple and perfect to communicate more to Analog_Bridge. Some scripting will always be required but USRP has a lot of room to expand. If you have some ideas for what you would like to see join us in the subgroup for the fork <https://dvswitch.groups.io/g/DVSwitch-ASL>. Your ideas are welcome.


Re: AMBEserver on rPI for Analog_Bridge

Patrick Perdue
 

I did all the same stuff again a few hours later, with the ThumbDV connected to the Pi, and it works without break-ups this time. Don't know what changed. Oh well.

On 11/4/2019 9:27 PM, Steve N4IRS wrote:
I can tell you that both Mike and I have run a DV3000 on a remote Pi. Though only on a LAN on the same segment.

On 11/4/19 9:25 PM, Patrick Perdue wrote:
I did, and it was.

FWIW, I also tried the dongle on another x86 machine running Debian with the same results. I have not yet tried everything locally on that machine.


On 11/4/2019 9:23 PM, Steve N4IRS wrote:
Can I assume you verified on the machine with the DV3000, operation with AMBEtest4.py and the latency is 1?

Steve N4IRS

On 11/4/19 8:51 PM, Patrick Perdue wrote:
Got it working, but audio is extremely jittery (pretty much useless) between the remote AMBEserver and the Analog_Bridge. Latency is a very solid 3 MS across the internet between the box in my apartment and the server running DVSwitch. If I used BlueDV locally for DMR and D-STAR, all seems fine. I even tried it from my iPhone's hotspot, and it was good there, too.

I guess I can run DVSwitch locally, but was trying to avoid doing that.



On 11/3/2019 8:00 PM, Steve N4IRS wrote:
Patrick,
I would not suggest you use a powered hub. Plug the ThumbDV directly into the Pi.
The ThumbDV is very sensitive to power dips.
See this: <https://dvswitch.groups.io/g/main/message/315?p=,,,20,0,0,0::relevance,,DV3000U,20,2,0,5521534>

Fore USB latency:
As root:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
I expect it will return 16

Try this:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

If that works, add:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
to /etc/rc.local before the last line (exit 0)

73, Steve N4IRS

On 11/3/19 7:47 PM, Patrick Perdue wrote:
Hi:

A while back, I saw something on this group to the affect of changing timing to make the ThumbDV+AMBEserver combo work better on a Raspberry Pi, but I can't find it now after searching the archives for an hour.

Note that I haven't set this up yet -- still waiting for dongles to arrive. They should be here tomorrow.

I have DVSwitch and ASL running in the cloud, and want to use AMBEserver on a remote Raspberry Pi 4 2GB instead of md380-emu. I'm using a 3.5A power supply on the Pi 4. I'd like to host two dongles for two different, completely unrelated connection points, each with it's own AMBEserver, of course. This is just a dongle host, and won't be running DVSwitch itself.

The Pi is running stock Raspbian.

What should be done in order to optimize things with this setup? Should I still use a powered USB hub, as some have suggested? What about timing?

Thanks and 73

KE4DYI











Re: AMBEserver on rPI for Analog_Bridge

Steve N4IRS
 

I can tell you that both Mike and I have run a DV3000 on a remote Pi. Though only on a LAN on the same segment.

On 11/4/19 9:25 PM, Patrick Perdue wrote:
I did, and it was.

FWIW, I also tried the dongle on another x86 machine running Debian with the same results. I have not yet tried everything locally on that machine.


On 11/4/2019 9:23 PM, Steve N4IRS wrote:
Can I assume you verified on the machine with the DV3000, operation with AMBEtest4.py and the latency is 1?

Steve N4IRS

On 11/4/19 8:51 PM, Patrick Perdue wrote:
Got it working, but audio is extremely jittery (pretty much useless) between the remote AMBEserver and the Analog_Bridge. Latency is a very solid 3 MS across the internet between the box in my apartment and the server running DVSwitch. If I used BlueDV locally for DMR and D-STAR, all seems fine. I even tried it from my iPhone's hotspot, and it was good there, too.

I guess I can run DVSwitch locally, but was trying to avoid doing that.



On 11/3/2019 8:00 PM, Steve N4IRS wrote:
Patrick,
I would not suggest you use a powered hub. Plug the ThumbDV directly into the Pi.
The ThumbDV is very sensitive to power dips.
See this: <https://dvswitch.groups.io/g/main/message/315?p=,,,20,0,0,0::relevance,,DV3000U,20,2,0,5521534>

Fore USB latency:
As root:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
I expect it will return 16

Try this:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

If that works, add:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
to /etc/rc.local before the last line (exit 0)

73, Steve N4IRS

On 11/3/19 7:47 PM, Patrick Perdue wrote:
Hi:

A while back, I saw something on this group to the affect of changing timing to make the ThumbDV+AMBEserver combo work better on a Raspberry Pi, but I can't find it now after searching the archives for an hour.

Note that I haven't set this up yet -- still waiting for dongles to arrive. They should be here tomorrow.

I have DVSwitch and ASL running in the cloud, and want to use AMBEserver on a remote Raspberry Pi 4 2GB instead of md380-emu. I'm using a 3.5A power supply on the Pi 4. I'd like to host two dongles for two different, completely unrelated connection points, each with it's own AMBEserver, of course. This is just a dongle host, and won't be running DVSwitch itself.

The Pi is running stock Raspbian.

What should be done in order to optimize things with this setup? Should I still use a powered USB hub, as some have suggested? What about timing?

Thanks and 73

KE4DYI









Re: AMBEserver on rPI for Analog_Bridge

Patrick Perdue
 

I did, and it was.

FWIW, I also tried the dongle on another x86 machine running Debian with the same results. I have not yet tried everything locally on that machine.

On 11/4/2019 9:23 PM, Steve N4IRS wrote:
Can I assume you verified on the machine with the DV3000, operation with AMBEtest4.py and the latency is 1?

Steve N4IRS

On 11/4/19 8:51 PM, Patrick Perdue wrote:
Got it working, but audio is extremely jittery (pretty much useless) between the remote AMBEserver and the Analog_Bridge. Latency is a very solid 3 MS across the internet between the box in my apartment and the server running DVSwitch. If I used BlueDV locally for DMR and D-STAR, all seems fine. I even tried it from my iPhone's hotspot, and it was good there, too.

I guess I can run DVSwitch locally, but was trying to avoid doing that.



On 11/3/2019 8:00 PM, Steve N4IRS wrote:
Patrick,
I would not suggest you use a powered hub. Plug the ThumbDV directly into the Pi.
The ThumbDV is very sensitive to power dips.
See this: <https://dvswitch.groups.io/g/main/message/315?p=,,,20,0,0,0::relevance,,DV3000U,20,2,0,5521534>

Fore USB latency:
As root:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
I expect it will return 16

Try this:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

If that works, add:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
to /etc/rc.local before the last line (exit 0)

73, Steve N4IRS

On 11/3/19 7:47 PM, Patrick Perdue wrote:
Hi:

A while back, I saw something on this group to the affect of changing timing to make the ThumbDV+AMBEserver combo work better on a Raspberry Pi, but I can't find it now after searching the archives for an hour.

Note that I haven't set this up yet -- still waiting for dongles to arrive. They should be here tomorrow.

I have DVSwitch and ASL running in the cloud, and want to use AMBEserver on a remote Raspberry Pi 4 2GB instead of md380-emu. I'm using a 3.5A power supply on the Pi 4. I'd like to host two dongles for two different, completely unrelated connection points, each with it's own AMBEserver, of course. This is just a dongle host, and won't be running DVSwitch itself.

The Pi is running stock Raspbian.

What should be done in order to optimize things with this setup? Should I still use a powered USB hub, as some have suggested? What about timing?

Thanks and 73

KE4DYI








Re: AMBEserver on rPI for Analog_Bridge

Steve N4IRS
 

Can I assume you verified on the machine with the DV3000, operation with AMBEtest4.py and the latency is 1?

Steve N4IRS

On 11/4/19 8:51 PM, Patrick Perdue wrote:
Got it working, but audio is extremely jittery (pretty much useless) between the remote AMBEserver and the Analog_Bridge. Latency is a very solid 3 MS across the internet between the box in my apartment and the server running DVSwitch. If I used BlueDV locally for DMR and D-STAR, all seems fine. I even tried it from my iPhone's hotspot, and it was good there, too.

I guess I can run DVSwitch locally, but was trying to avoid doing that.



On 11/3/2019 8:00 PM, Steve N4IRS wrote:
Patrick,
I would not suggest you use a powered hub. Plug the ThumbDV directly into the Pi.
The ThumbDV is very sensitive to power dips.
See this: <https://dvswitch.groups.io/g/main/message/315?p=,,,20,0,0,0::relevance,,DV3000U,20,2,0,5521534>

Fore USB latency:
As root:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
I expect it will return 16

Try this:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

If that works, add:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
to /etc/rc.local before the last line (exit 0)

73, Steve N4IRS

On 11/3/19 7:47 PM, Patrick Perdue wrote:
Hi:

A while back, I saw something on this group to the affect of changing timing to make the ThumbDV+AMBEserver combo work better on a Raspberry Pi, but I can't find it now after searching the archives for an hour.

Note that I haven't set this up yet -- still waiting for dongles to arrive. They should be here tomorrow.

I have DVSwitch and ASL running in the cloud, and want to use AMBEserver on a remote Raspberry Pi 4 2GB instead of md380-emu. I'm using a 3.5A power supply on the Pi 4. I'd like to host two dongles for two different, completely unrelated connection points, each with it's own AMBEserver, of course. This is just a dongle host, and won't be running DVSwitch itself.

The Pi is running stock Raspbian.

What should be done in order to optimize things with this setup? Should I still use a powered USB hub, as some have suggested? What about timing?

Thanks and 73

KE4DYI






Re: AMBEserver on rPI for Analog_Bridge

Patrick Perdue
 

Got it working, but audio is extremely jittery (pretty much useless) between the remote AMBEserver and the Analog_Bridge. Latency is a very solid 3 MS across the internet between the box in my apartment and the server running DVSwitch. If I used BlueDV locally for DMR and D-STAR, all seems fine. I even tried it from my iPhone's hotspot, and it was good there, too.

I guess I can run DVSwitch locally, but was trying to avoid doing that.

On 11/3/2019 8:00 PM, Steve N4IRS wrote:
Patrick,
I would not suggest you use a powered hub. Plug the ThumbDV directly into the Pi.
The ThumbDV is very sensitive to power dips.
See this: <https://dvswitch.groups.io/g/main/message/315?p=,,,20,0,0,0::relevance,,DV3000U,20,2,0,5521534>

Fore USB latency:
As root:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
I expect it will return 16

Try this:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

If that works, add:
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
to /etc/rc.local before the last line (exit 0)

73, Steve N4IRS

On 11/3/19 7:47 PM, Patrick Perdue wrote:
Hi:

A while back, I saw something on this group to the affect of changing timing to make the ThumbDV+AMBEserver combo work better on a Raspberry Pi, but I can't find it now after searching the archives for an hour.

Note that I haven't set this up yet -- still waiting for dongles to arrive. They should be here tomorrow.

I have DVSwitch and ASL running in the cloud, and want to use AMBEserver on a remote Raspberry Pi 4 2GB instead of md380-emu. I'm using a 3.5A power supply on the Pi 4. I'd like to host two dongles for two different, completely unrelated connection points, each with it's own AMBEserver, of course. This is just a dongle host, and won't be running DVSwitch itself.

The Pi is running stock Raspbian.

What should be done in order to optimize things with this setup? Should I still use a powered USB hub, as some have suggested? What about timing?

Thanks and 73

KE4DYI