Date   

Re: FM Repeater to DMR Talkgroup? #best_practices

Mike KB8JNM
 

I am sorry, I missed the most obvious reply.

Set-up a node as you would a radio with the sound FOB and just use the audio input in VOX mode. Unless you can achieve a COR signal from the receiver. If you are using a Pi, VOX may be easiest.  Just set it up for a private node.

You should consult the allstar documentation for all that.

On 2/29/2020 12:34 PM, Weller Rudolf wrote:
Hello,

I would like to connect an analog FM Relais (Scanner) to my local HBlink-Server and transmit the audio signals to a DMR talk group, e.g. 777. This is intended for a local server, with no DMRPlus etc. connected, private only. Is there a guide for this, which I could read, or can someone here help me?

It'd already be enough if only the analog RX signal is transmitted to the talk group. How can I make this happen without the use of Crosslink, ASL, Echolink or multiple devices?

I have available: Raspberry, DVThumb, UriX and all this stuff here. What can I do?

Thank you
Rudolf


Re: FM Repeater to DMR Talkgroup? #best_practices

Mike KB8JNM
 

I can not point to a guide or give you much advise outside of this.

Be sure your audio is clean before converting to digital. Little noticed noise in analog can be a big issue in digital. Humming, buzzing and pops are not going to give you readable audio converted to digital. It's hard to believe how much it matters.

I do know you have a option for a rtl softradio input to allstar/asterisk connection and it is documented out there somewhere. Perhaps others will chime in with that and more info than I.

Connect it to a private node for control so you can connect/disconnect at will/as needed.

On 2/29/2020 12:34 PM, Weller Rudolf wrote:
Hello,

I would like to connect an analog FM Relais (Scanner) to my local HBlink-Server and transmit the audio signals to a DMR talk group, e.g. 777. This is intended for a local server, with no DMRPlus etc. connected, private only. Is there a guide for this, which I could read, or can someone here help me?

It'd already be enough if only the analog RX signal is transmitted to the talk group. How can I make this happen without the use of Crosslink, ASL, Echolink or multiple devices?

I have available: Raspberry, DVThumb, UriX and all this stuff here. What can I do?

Thank you
Rudolf


FM Repeater to DMR Talkgroup? #best_practices

Weller Rudolf
 

Hello,

I would like to connect an analog FM Relais (Scanner) to my local HBlink-Server and transmit the audio signals to a DMR talk group, e.g. 777. This is intended for a local server, with no DMRPlus etc. connected, private only. Is there a guide for this, which I could read, or can someone here help me?

It'd already be enough if only the analog RX signal is transmitted to the talk group. How can I make this happen without the use of Crosslink, ASL, Echolink or multiple devices?

I have available: Raspberry, DVThumb, UriX and all this stuff here. What can I do?

Thank you
Rudolf


Re: Package 'chkconfig' has no installation candidate

Steve N4IRS
 

I do not see chkconfig anywhere in the install script. Please copy and paste the messages before and after.

Steve N4IRS

On 2/28/20 9:24 PM, ken@... wrote:
I have attempted to do an install with Debian 8 9 and 10, 9 and 10 continue to have the above error message when attempting to run the DV Switch system builder. Can you please advise?

Thank you,
Ken
KC2IDB


Package 'chkconfig' has no installation candidate

ken@...
 

I have attempted to do an install with Debian 8 9 and 10, 9 and 10 continue to have the above error message when attempting to run the DV Switch system builder. Can you please advise?

Thank you,
Ken
KC2IDB


Re: AMBE GPIO board #analog_bridge

HL5KY
 

Steve,
 
I didn't know about parameter very well for AMBEtest4.py. The result was without parameter. This time I tried with "AMBEtest4.py -e -v -n" and the baudrate was 460800 but it still doesn't seem to be properly working.

              Port name:      /dev/ttyAMA0

              Baudrate:       460800

              Byte size:      8

              Parity:         N

              Stop bits:      1

              Xon Xoff:       False

              RTS/CTS:        False

              DST/DTR:        False

              *********************

              Testing Reset DV3000

              Error, AMBE header was corrupt

 
I found a thread which has something to do with the error message "AMBE header was corrupt" and I read KI7SBI solved his issue with a bigger power supply. I don't fully understand the main issue of his but I just tried with a couple of other big enough power supplies but no luck, meaning same return from AMBEtest4.py and the audio crashes on Dstar.
 
Any other suggestions?
 
p.s. When I set for a separate AMBE server with the proper address and port on Analog_Bridge.ini it works ok and the audio is very good.


Re: First release of USRP Client (pyUC)

ve6gcd@...
 

I just caught a glitch: Transmit is disabled after double clicking the Transmit Button twice right after opening the app.


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

MIKE Parie <aa1pr@...>
 

OK like this gentleman I too am having issues
it seems my node is communicating with brandmesiter & echolink, both are connected & reporting
all the test steps along the process were verified as instructed in the pdf
however the node will not pass audio as far as I can tell trying to access it from my 2nd echolink app on the cell using cell data
I need to get someone on the outside world to connect in for me & test

can I add a node radio to this I dont see anyone doing that from my online research so far
Ive added my usb radio fob script accordingly to the simpleusb_tune_usb_42282.conf
I see the new software doesnt have simpleusb-tune-menu
so how does one set audio levels

I also tried to setup a script/command so when the node is turned on it connects to 1999  with     startup_macro =*9531999 will this still work with the new software?

can I also install the zoiper script in iax.conf & extensions.conf like the crompton image to gain iax access?

any help is greatly appreciated, thanks






Re: First release of USRP Client (pyUC)

ve6gcd@...
 

Thanks Steve,

This is interesting, might also try pursuing this route. I will reconfugure rpt.conf as advised and let you know.

73,
Geoffrey VE6GCD


Re: First release of USRP Client (pyUC)

Steve N4IRS
 

Sorry for the delay, it took me a bit to figure out what I think is your issue.
In rpt.conf for the node you are connecting to via USRP you have something like this:

rxchannel = USRP/127.0.0.1:34001:32001; GNU Radio interface USRP

What this says is that chan_usrp is listening on port 32001 This is how your audio gets from pyUC to ASL
127.0.0.1:34001 tells CHAN_USRP to send audio to IP 127.0.0.1 on port 34001. Well unless you have pyUC running on the same machine as the ASL node, you will hear no audio from pyUC.
So, change 127.0.0.1 to the IP of the machine running pyUC.

Steve N4IRS
 


On 2/25/2020 10:55 PM, ve6gcd@... wrote:
Hi Steve,

I was able to transmit from USRP Client in ASL mode but was unable to receive anything. Is there anything I missed in the settings? Config file below.

[DEFAULTS]
myCall = VE6GCD             ; You callsign
subscriberID = 3026122      ; Your DMR/CCS7 ID
repeaterID = 3026122        ; Your repeater ID
ipAddress = <omitted>  ; IP address or hostname of DVSwitch Server (AB)
usrpTxPort = 34001          ; Port on which AB is listening
usrpRxPort = 32001          ; Local port to listen for packets from AB
defaultServer = YSF         ; Start up UI on this mode (AB will override)
slot = 2                    ; Slot to transmit on for DMR
in_index = Default          ; pyaudio  index for input device (0-N or -1 to disable)
out_index = Default         ; pyaudio  index for output device (0-N or Default) 
loopback = 0                ; NOT USED
dongleMode = 0              ; NOT USED
micVol = 50                 ; NOT USED
spVol = 50                  ; NOT USED
voxEnable = 0               ; Enable = 1, disable = 0
voxThreshold = 200          ; This seems to be a good value for me
voxDelay = 50               ; 50 samples (which is 1 second)
aslMode = 1                 ; For VERY limited use with chan_usrp (ASL experimental).


Re: AMBE GPIO board #analog_bridge

Kevin Ku
 


2020년 2월 27일 (목) 19:54, Steve N4IRS <szingman@...>님이 작성:

Joe,
Analog_Bridge does support a Pi-Hat type of DV3000. Both Mike and a regularly run the NWDigital Pi-Hat DV3000. What parameter are you using to run AMBEtest4.py? It should be

AMBEtest4.py --error --verbose  -n --serial /dev/ttyAMA0

73, Steve N4IRS


On 2/27/20 1:26 AM, onetree9@... wrote:

Thank you for the great work of DVSwitch. I am trying to hook up my AMBE GPIO board which was made in Japan and similar to DV3000 GPIO board. It was working ok for AMBE server on RPI3B+ with the following setup:

          device port : /dev/ttyAMA0

          baudrate : 460800

 

It doesn't work for DVSwitch with the following setup(s) in Analog_Bridge.ini:

          device port : /dev/ttyAMA0

          baudrate : 460800   or   230400 (AMBEtest4.py showed this baudrate)

          serial : true

 

Interestingly, I get the different baudrate from the AMBEtest4.py on RPI3B+

Here is the result:

 

          Setting serial port

          Serial port parameters:

          Port name:      /dev/ttyAMA0

          Baudrate:       230400

          Byte size:      8

          Parity:         N

          Stop bits:      1

          Xon Xoff:       False

          RTS/CTS:        False

          DST/DTR:        False

          *********************

          Silent testing mode.....

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Reset DV3000

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Get Product ID

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Get Version

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Set DSTAR Mode

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Reset DV3000

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Set DMR Mode

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Decode AMBE

          Error, decode AMBE to PCM return no results

          Error, AMBE header was corrupt

          ..........

          ..........

 

Questions:

1. Does DVSwitch only support USB serial device ?

 

2. If it supports GPIO serial, is there other way of setup for GPIO device on Analog_Bridge.ini ?

 

73,

Joe, HL5KY.



Re: AMBE GPIO board #analog_bridge

Steve N4IRS
 

Joe,
Analog_Bridge does support a Pi-Hat type of DV3000. Both Mike and a regularly run the NWDigital Pi-Hat DV3000. What parameter are you using to run AMBEtest4.py? It should be

AMBEtest4.py --error --verbose  -n --serial /dev/ttyAMA0

73, Steve N4IRS


On 2/27/20 1:26 AM, onetree9@... wrote:

Thank you for the great work of DVSwitch. I am trying to hook up my AMBE GPIO board which was made in Japan and similar to DV3000 GPIO board. It was working ok for AMBE server on RPI3B+ with the following setup:

          device port : /dev/ttyAMA0

          baudrate : 460800

 

It doesn't work for DVSwitch with the following setup(s) in Analog_Bridge.ini:

          device port : /dev/ttyAMA0

          baudrate : 460800   or   230400 (AMBEtest4.py showed this baudrate)

          serial : true

 

Interestingly, I get the different baudrate from the AMBEtest4.py on RPI3B+

Here is the result:

 

          Setting serial port

          Serial port parameters:

          Port name:      /dev/ttyAMA0

          Baudrate:       230400

          Byte size:      8

          Parity:         N

          Stop bits:      1

          Xon Xoff:       False

          RTS/CTS:        False

          DST/DTR:        False

          *********************

          Silent testing mode.....

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Reset DV3000

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Get Product ID

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Get Version

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Set DSTAR Mode

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Reset DV3000

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Set DMR Mode

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Decode AMBE

          Error, decode AMBE to PCM return no results

          Error, AMBE header was corrupt

          ..........

          ..........

 

Questions:

1. Does DVSwitch only support USB serial device ?

 

2. If it supports GPIO serial, is there other way of setup for GPIO device on Analog_Bridge.ini ?

 

73,

Joe, HL5KY.



AMBE GPIO board #analog_bridge

HL5KY
 

Thank you for the great work of DVSwitch. I am trying to hook up my AMBE GPIO board which was made in Japan and similar to DV3000 GPIO board. It was working ok for AMBE server on RPI3B+ with the following setup:

          device port : /dev/ttyAMA0

          baudrate : 460800

 

It doesn't work for DVSwitch with the following setup(s) in Analog_Bridge.ini:

          device port : /dev/ttyAMA0

          baudrate : 460800   or   230400 (AMBEtest4.py showed this baudrate)

          serial : true

 

Interestingly, I get the different baudrate from the AMBEtest4.py on RPI3B+

Here is the result:

 

          Setting serial port

          Serial port parameters:

          Port name:      /dev/ttyAMA0

          Baudrate:       230400

          Byte size:      8

          Parity:         N

          Stop bits:      1

          Xon Xoff:       False

          RTS/CTS:        False

          DST/DTR:        False

          *********************

          Silent testing mode.....

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Reset DV3000

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Get Product ID

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Get Version

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Set DSTAR Mode

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Reset DV3000

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Set DMR Mode

          Error, AMBE header was corrupt

          Error, no reply from DV3000.  Command issued was: Decode AMBE

          Error, decode AMBE to PCM return no results

          Error, AMBE header was corrupt

          ..........

          ..........

 

Questions:

1. Does DVSwitch only support USB serial device ?

 

2. If it supports GPIO serial, is there other way of setup for GPIO device on Analog_Bridge.ini ?

 

73,

Joe, HL5KY.


Re: What DMR ID's? #analog_bridge

Alejandro Pereida
 

Thanks Steve, well this is the idea hopefully we can make it work:

I built two repeaters for our Mexican radio club, both in the same rack on a mountain top, one is using a Rasperry Pi 4 running PI-STAR, two Motorola CDM1500 on the 438.025 Mhz (- 5Mhz) frequency pair
I only enabled DMR and D-Star on the Pi-Star for that repeater (Call: XE2SJN DMR id: 334217).

The other is an analog VHF repeater using a Raspberry pi 3 running Asterisk as the controller and two Motorola CDM1500. So the idea is to be able to link the analog repeater to TG 334217 using the Analog_bridge,MMDVM_bridge and MD380 emulator programs as shown on some youtube videos.

Will this setup work if both repeaters are behind the same public IP?
Is it possible to link/unlink  the analog repeater from the DMR network via DTMF?

Thanks in advance

Alex N2IX / XE2BSS


Re: What DMR ID's? #analog_bridge

Steve N4IRS
 

Alex,
The gatewayDmrId is the ID sent by Analog_Bridge if it has no other choice. Depending on how you are using Analog_Bridge, it may never be used.

Hope this helps,

73, Steve N4IRS

On 2/25/20 8:41 PM, Alejandro Pereida via Groups.Io wrote:
Hello, in the Analog_Bridge.ini file under [AMBE AUDIO] and for the parameters:

gatewayDmrId = xxxxxx                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 3342045                ; ID of source repeater

Which DMR id's should I use for the gatewayDmrId? considering that this is a repeater with DMR ID = 3342045

Thanks

Alex N2IX / XE2BSS


What DMR ID's? #analog_bridge

Alejandro Pereida
 

Hello, in the Analog_Bridge.ini file under [AMBE AUDIO] and for the parameters:

gatewayDmrId = xxxxxx                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 3342045                ; ID of source repeater

Which DMR id's should I use for the gatewayDmrId? considering that this is a repeater with DMR ID = 3342045

Thanks

Alex N2IX / XE2BSS


Re: First release of USRP Client (pyUC)

ve6gcd@...
 

Thanks Steve,

I will try to play with it and see how I can use it to interface ASL and S-COM 7330.

73,
Geoffrey VE6GCD


Re: DVSwitch Server Dying once a day

Steve N4IRS
 

Jay,
We are looking at a possible cause / solution.

Steve

On 2/25/2020 12:01 PM, Jay wrote:
Maybe someone has a solution.  I have Raspberry Pi 3 with DVSwitch built from the most current instructions.  It works great but sometime overnight, every night, the device becomes unreachable.  By that I mean I VNC into it and it will not conned until it is rebooted.  Its like it went to sleep and doesn't want to wake up.  

Has anyone else experienced this.  The OS is fully up to date.  All IP addresses are static.  No other software has been installed.  I just enabled VNC and started using it.  I do not believe it is DVSwitch software that is the cause but I have a bunch of Pi3 devices running without this occurring on them.

Any suggestions or hints would be helpful.

--

jb   N4NQY


Re: First release of USRP Client (pyUC)

Steve N4IRS
 

Geoff,
You can leave the default server alone, it will not be used when connecting to ASL.
Set aslMode=1
Setup you ASL node using the USRP channel driver. Set the ports to the same value
rxchannel = USRP/127.0.0.1:12345:12345

Please be aware that you can not control the node (*70 etc) from pyUC. All you can do is transmit and receive.

Steve N4IRS

 

On 2/25/2020 1:58 PM, ve6gcd@... wrote:
Hi Steve,

Can you tell me how to set this up for ASL USRP node?

The downloaded pyUC.ini file has

defaultServer=DMR. 
aslMode=0

For AllStarLink Do I need to set defaultServer to blank, while aslMode=1? 

73,
Geoffrey VE6GCD


Re: First release of USRP Client (pyUC)

ve6gcd@...
 

Hi Steve,

Can you tell me how to set this up for ASL USRP node?

The downloaded pyUC.ini file has

defaultServer=DMR. 
aslMode=0

For AllStarLink Do I need to set defaultServer to blank, while aslMode=1? 

73,
Geoffrey VE6GCD

3261 - 3280 of 9151