dvswitch / analog_bridge

Bridge AMBE / IMBE to PCM

Analog_Bridge

Note: dvswitch.sh has been moved to the MMDVM_Bridge repository

Enviorment Variables AnalogBridgeLogDir = Where to put Analog_Bridge.log

Example tune values for each mode.

DSTAR: (Reflector type, Number, Module, L)

REF030CL

XRF012AL

DCS006ZL

DMR, P25, NXDN: (Just the tg number)

10200

310

3166

YSF: (IP:PORT)

amlink.alabamalink.info:42001

96.47.95.121:42000

analog_bridge's Issues

Add support for DVMega AMBE 3000

Copied from Previous Repo

Hi All,

I have recently been experimenting with the DVMega AMBE 3000 and Analog Bridge.

By default the DVMega AMBE 3000 defaults to CODEC mode with Comfort Noise and Voice Activity Detection enabled, causing it to to spit out AMBE packets unprompted.

Overriding this hardware setting is fairly simple, it's just a case of sending a 'PKT_RESETSOFTCFG' packet in the following format-

61 00 07 00 34 05 00 00 0F 00 00

and waiting for the corresponding 'PKT_READY' response-

61 00 01 00 39

If possible could we get this merged into Analog_Bridge? I attempted to create a 'proxy' to sit in between Analog_Bridge and the AMBE Chip, but I can't get the code running fast enough.

Analog_Bridge would need to send the PKT_RESETSOFTCFG when it first connects to the AMBE 3000, and if it subsequently looses connection or resets.

Thanks!

Error when using "fancy dongle" functions

Hello. Im using Debian 10 and I want to use the old "fancy dongle" function.
When enabling it:

; Audio devices are normally not needed when in gateway service. These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/dsp ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/dsp ; Only used for dongle mode

; Below values are for using this as a local DMR dongle (no ASL needed)
useMicrophone = true ; Use app as just a fancy dongle for DMR
useVox = true ; If using dongle mode (useMicrophone), enable VOX

And executing, I got an alsa error. I think you are looking a unknown alsa device:

M: 2020-03-16 02:31:45.100 Audio In/Out Device: /dev/dsp
I: 2020-03-16 02:31:45.100 Begin reading audio from microphone vox enabled
I: 2020-03-16 02:31:45.100 Open UDP listener on 127.0.0.1:31100
I: 2020-03-16 02:31:45.101 Open USRP on 127.0.0.1:32001
D: 2020-03-16 02:31:45.101 Attempt to init DV3000 in DMR mode
M: 2020-03-16 02:31:45.101 Connecting to DV3000 hardware......
hyper-3.0.2-x86_64.AppImage: simple.c:346: snd_mixer_selem_has_playback_switch: Assertion `elem' failed.

Please, as the source code is not open to the public, can give any kind of workaround?

Thanks in advance.

Open Source?

Are there plans to release the source code for Analog_Bridge?

DVSwitch configurations assumed shared

The Analog_Bridge binary appears to assume it's being ran on the same host reading the same DVSwitch.ini file as the MMDVM_Bridge binary which causes confusion when both are running individually (say in their own containers).

The Analog_Bridge binary looks at the TX port configuration in it's DVSwitch.ini file for it's RX port, and this is not really documented anywhere.

Is the source code available so that these small nuances can be addressed within a fork?

Analog_Bridge.ini Syntax

Hi All,

The DV3000 section in the included Analog_Bridge.ini looks like this:

[DV3000]
address = 127.0.0.1                     ; IP address of AMBEServer
rxPort = 2460                           ; Port of AMBEServer
; address = /dev/ttyUSB0                ; Device of DV3000U on this machine
; baud = 460800                         ; Baud rate of the dongle (230400 or 460800)
; serial = true                         ; Use serial=true for direct connect or serial=false for AMBEServer

I'm using a physically attached AMBE chip, so I configured it like this:

[DV3000]
address = /dev/ttyUSB0                ; Device of DV3000U on this machine
baud = 230400                         ; Baud rate of the dongle (230400 or 460800)
serial = true                         ; Use serial=true for direct connect or serial=false for AMBEServer

However I see the following in the logs:

W: 2018-06-04 20:34:23.963 Unknown section/name in .ini file: DV3000/address
W: 2018-06-04 20:34:23.964 Unknown section/name in .ini file: DV3000/baud
M: 2018-06-04 20:34:23.966 Setting [DV3000] serial -> true

If I use the following syntax:

[DV3000]
server = /dev/ttyUSB0                ; Device of DV3000U on this machine
port = 230400                             ; Baud rate of the dongle (230400 or 460800)
serial = true                                 ; Use serial=true for direct connect or serial=false for AMBEServer

It works:

M: 2018-06-04 20:44:35.945 Setting [DV3000] server -> /dev/ttyUSB0
M: 2018-06-04 20:44:35.947 Setting [DV3000] port -> 230400
M: 2018-06-04 20:44:35.949 Setting [DV3000] serial -> true

I'd submit a PR as it seems like a simple change, but I'm not sure If I'm missing something

Thanks

Add support for TEAM6160 / Bao "USB VOCO"

Hi All,

I recently purchased a TEAM6160 / Bao "USB VOCO" AMBE transcoder. It's working great with BlueDV, but Analog_Bridge fails to initialise it.

If I run the AMBEtest4.py, I get the following:

Setting serial port
Serial port parameters:
Port name:      /dev/ttyUSB0
Baudrate:       460800
Byte size:      8
Parity:         N
Stop bits:      1
Xon Xoff:       False
RTS/CTS:        False
DST/DTR:        False
*********************
Silent testing mode.....
In test Get Product ID
Error, did not get expected value from DV3000.  Got: 0AMBE3000F expected 0AMBE3000R
30414d4245333030304600
In test Get Version
Error, did not get expected value from DV3000.  Got: 1V120.E100.XXXX.C106.G514.R007.A0030608.C0020208 expected 1V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
31563132302e453130302e585858582e433130362e473531342e523030372e41303033303630382e433030323032303800
Error count =  2

When someone gets chance, please could they amend the validation in Analog_Bridge, so the Product ID and Version pass and it starts up correctly?

If anyone needs access to the device let me know.

Thanks again
Matthew

Misconfigured Radio, ID 0 causing Analog_Bridge to exit, not respawn

While playing with TGIF, when someone with a misconfigured radio comes on with ID 0 it crashes Analog_Bridge. I believe I've seen ID 0 with other cross mode projects, so this would be a normal thing to pop up from time to time.

MMDVM_Bridge log:
M: 2020-05-25 21:47:08.927 DMR Slot 2, received network voice header from 0 to TG 31665
M: 2020-05-25 21:47:10.430 DMR Slot 2, network watchdog has expired, 0.1 seconds, 0% packet loss, BER: 0.0%

Analog_Bridge.log:
F: 2020-05-25 21:47:08.927 Repeater ID (0) can not be the same as subscriber ID (0). Fatal error exiting

Problem with gatewayDmrID

Hi Steve,

Is it possible to correct the problem with use DMRiD + SSID in gatewayDmrId ?
We have run Allstralink with EchoLink/USRP to DMR link and we need use DMRID+SSID in "gatewayDmrId"
When we put DMRId repeater (260454)+ SSID (99) for example
26045499 Analog_Bridge send ID which is used to transmitting
for example 9268283

It will be nice to possible use in gatewayDmrId
DmrID repeater + SSID
and
DmrId private +SSID
The problem is in Analog_Bridge v1.4.1 and MMDVM_Bridge in log show

Begin TX: src=9268283 rpt=26045440 dst=40 slot=2 cc=1 metadata=26045499