Date   

Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Steve N4IRS
 

Are you on the same LAN? Is the Server exposed to the outside world?

On 7/1/21 4:51 PM, Fairfieldsteve@... wrote:
Yes same issue
73 
N1saf
Steve


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Fairfieldsteve@...
 

Yes same issue
73 
N1saf
Steve


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Steve N4IRS
 

Have you tried anyother TG or parrot?

On 7/1/21 11:42 AM, Stephen Fairfield wrote:
.I am running the ASL 2.0 on a SHAri rpi4 NODE. It works fine except for one issue:

If I use 50001 tx and receive ports in AB.ini and in the DVSWITCH mobile client config, I can connect to BM ie TG91 and I hear the audio on that TG91 fine on 
my android phone in the DVS client, but not on the Radio.
If I change AB.ini USRP stanza from 50001/50001 to 32001/34001 and in the DVS config on the phone, I hear the audio on that TG91 fine on the Radio, but nothing
in the audio on the DVS phone client.

Here is my AB.ini :

; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
 
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port andsystemctl status analog_bridge19
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
 
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
 
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
 
; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
transferRootDir = /tmp ; Export database files to USRP partner
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
 
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                      ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
 
;pcmPort = 2222 ; UDP port to send to the WebProxy saf
 
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Analog -> Digital Minimum time in MS for hang delay (0-10000)
 
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 3172638                  ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 317263811                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 317263                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
 
; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself, 
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Analog_Reflector, Allstar/Asterisk or another Analog_Bridge)
;txPort = 50001 ; Transmit USRP frames on this port
;rxPort = 50001 ; Listen for USRP frames on this port
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_USE_GAIN              ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 4.00                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAGC = -20,10,100                    ; Set the agc threshold (db), slope (db) and decay (ms)
tlvAudio = AUDIO_USE_GAIN               ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.25                          ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
 
[MACROS]
 
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
 
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
 
; For example using macro "5678" above would look like:
; *5678#9876
 
; Which would invoke:
; echo 9876
 
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using 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
[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

Can you please help ?
N1SAF
Steve
 


ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Stephen Fairfield
 

.I am running the ASL 2.0 on a SHAri rpi4 NODE. It works fine except for one issue:

If I use 50001 tx and receive ports in AB.ini and in the DVSWITCH mobile client config, I can connect to BM ie TG91 and I hear the audio on that TG91 fine on 
my android phone in the DVS client, but not on the Radio.
If I change AB.ini USRP stanza from 50001/50001 to 32001/34001 and in the DVS config on the phone, I hear the audio on that TG91 fine on the Radio, but nothing
in the audio on the DVS phone client.

Here is my AB.ini :

; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
 
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port andsystemctl status analog_bridge19
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
 
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
 
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
 
; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
transferRootDir = /tmp ; Export database files to USRP partner
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
 
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                      ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
 
;pcmPort = 2222 ; UDP port to send to the WebProxy saf
 
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Analog -> Digital Minimum time in MS for hang delay (0-10000)
 
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 3172638                  ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 317263811                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 317263                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
 
; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself, 
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Analog_Reflector, Allstar/Asterisk or another Analog_Bridge)
;txPort = 50001 ; Transmit USRP frames on this port
;rxPort = 50001 ; Listen for USRP frames on this port
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_USE_GAIN              ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 4.00                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAGC = -20,10,100                    ; Set the agc threshold (db), slope (db) and decay (ms)
tlvAudio = AUDIO_USE_GAIN               ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.25                          ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
 
[MACROS]
 
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
 
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
 
; For example using macro "5678" above would look like:
; *5678#9876
 
; Which would invoke:
; echo 9876
 
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using 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
[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

Can you please help ?
N1SAF
Steve
 


Re: DVSwitch Client does not receive

Steve N4IRS
 

Here is a follow up to this.
I was able to connect to his VPS with DVSwitch Mobile. Gareth found a issue with his wifi / LAN configuration. I'll let him explain.
Gareth, to answer your other question, you can share your DVSwitch Server with your father. You will want to add Analog_Reflector.

Steve N4IRS

On 6/30/21 9:56 PM, steelegwds@... wrote:
I'm just adding my current testing results.

Ok in an effort to rule out even the absurd. I've gone and paid for a VPS server for a month just to install DVSwitch - I figured lets try a full Deban server outside my LAN really can't do more than that.

So Installed DV Switch and configured it. No problems there it all fired up first time.

Change the config on my Laptop for the pyUC client set the TX and RX ports correctly (TX 50111, RX 50112) this matches the cloud servers settings in Analog_Bridge.ini - as I said before I noticed that using the same port number for both on the mobile client it never registers but different ports it does register (why I have no idea).

Anyway fire up pyUC and bingo! it works first time no faults. I can watch the DVSwitch Dashboard, connect to Parrot system etc etc all works - Two way audio as expected.

So then we move on to the DVSwitch client, just to rule out every possible glitch I can think of IT wise, I connected my t320 to my next-door neighbours WiFi (yes I had permission) configured the App with the appropriate ports and the IP address of the cloud server. It registered! if I enter talk group numbers and press send, Looking at DVSwitch Dashboard sure enough the talk group changes.

Try to transmit, again DVSwitch Dashboard indicates its receiving me and doing it's thing. But when say Parrot system trys to replay my test transmission, it shows in DVSwitch Dashboard but the Mobile Client App stays totally quiet no sign of live, no messages on screen nothing.... Dead as a Dodo.

So wanting to rule out an issue with the t320, I've now gotten hold of both an older Android Phone and a Nvida Shield Android Tablet - Installed DVSwitch client on them both, settings etc - same test... same results, can TX fine, can control the DVSwitch ok. But receive anything from the DVSwitch = NOPE.

The last test I did showed how totally Bonkers this is - Connected Laptop to DVSwitch in the Cloud via the pyUC via one internet connection, then connected the Mobile Client via another internet connection.... Used the Mobile client to transmit to the Parrot system - again Dashboard showed the TX working. Then when parrot replayed my transmission - The mobile client just sat there an did nothing, but the pyUC Client played out my voice and showed me the appropriate data in it's log window.

Talk about weird ass problem lol, anyone have a suggestion here? Steve I know your busy but is anyone else out there that has any ideas?

Praying for a Miracle.
Gareth GM0WUR


Re: DVSwitch Client does not receive

Steve N4IRS
 

Set the 2 ports to the same value and send me the IP address direct szingman@...

On 6/30/21 9:56 PM, steelegwds@... wrote:
I'm just adding my current testing results.

Ok in an effort to rule out even the absurd. I've gone and paid for a VPS server for a month just to install DVSwitch - I figured lets try a full Deban server outside my LAN really can't do more than that.

So Installed DV Switch and configured it. No problems there it all fired up first time.

Change the config on my Laptop for the pyUC client set the TX and RX ports correctly (TX 50111, RX 50112) this matches the cloud servers settings in Analog_Bridge.ini - as I said before I noticed that using the same port number for both on the mobile client it never registers but different ports it does register (why I have no idea).

Anyway fire up pyUC and bingo! it works first time no faults. I can watch the DVSwitch Dashboard, connect to Parrot system etc etc all works - Two way audio as expected.

So then we move on to the DVSwitch client, just to rule out every possible glitch I can think of IT wise, I connected my t320 to my next-door neighbours WiFi (yes I had permission) configured the App with the appropriate ports and the IP address of the cloud server. It registered! if I enter talk group numbers and press send, Looking at DVSwitch Dashboard sure enough the talk group changes.

Try to transmit, again DVSwitch Dashboard indicates its receiving me and doing it's thing. But when say Parrot system trys to replay my test transmission, it shows in DVSwitch Dashboard but the Mobile Client App stays totally quiet no sign of live, no messages on screen nothing.... Dead as a Dodo.

So wanting to rule out an issue with the t320, I've now gotten hold of both an older Android Phone and a Nvida Shield Android Tablet - Installed DVSwitch client on them both, settings etc - same test... same results, can TX fine, can control the DVSwitch ok. But receive anything from the DVSwitch = NOPE.

The last test I did showed how totally Bonkers this is - Connected Laptop to DVSwitch in the Cloud via the pyUC via one internet connection, then connected the Mobile Client via another internet connection.... Used the Mobile client to transmit to the Parrot system - again Dashboard showed the TX working. Then when parrot replayed my transmission - The mobile client just sat there an did nothing, but the pyUC Client played out my voice and showed me the appropriate data in it's log window.

Talk about weird ass problem lol, anyone have a suggestion here? Steve I know your busy but is anyone else out there that has any ideas?

Praying for a Miracle.
Gareth GM0WUR


Re: DVSwitch Client does not receive

Gareth GM0WUR
 

I'm just adding my current testing results.

Ok in an effort to rule out even the absurd. I've gone and paid for a VPS server for a month just to install DVSwitch - I figured lets try a full Deban server outside my LAN really can't do more than that.

So Installed DV Switch and configured it. No problems there it all fired up first time.

Change the config on my Laptop for the pyUC client set the TX and RX ports correctly (TX 50111, RX 50112) this matches the cloud servers settings in Analog_Bridge.ini - as I said before I noticed that using the same port number for both on the mobile client it never registers but different ports it does register (why I have no idea).

Anyway fire up pyUC and bingo! it works first time no faults. I can watch the DVSwitch Dashboard, connect to Parrot system etc etc all works - Two way audio as expected.

So then we move on to the DVSwitch client, just to rule out every possible glitch I can think of IT wise, I connected my t320 to my next-door neighbours WiFi (yes I had permission) configured the App with the appropriate ports and the IP address of the cloud server. It registered! if I enter talk group numbers and press send, Looking at DVSwitch Dashboard sure enough the talk group changes.

Try to transmit, again DVSwitch Dashboard indicates its receiving me and doing it's thing. But when say Parrot system trys to replay my test transmission, it shows in DVSwitch Dashboard but the Mobile Client App stays totally quiet no sign of live, no messages on screen nothing.... Dead as a Dodo.

So wanting to rule out an issue with the t320, I've now gotten hold of both an older Android Phone and a Nvida Shield Android Tablet - Installed DVSwitch client on them both, settings etc - same test... same results, can TX fine, can control the DVSwitch ok. But receive anything from the DVSwitch = NOPE.

The last test I did showed how totally Bonkers this is - Connected Laptop to DVSwitch in the Cloud via the pyUC via one internet connection, then connected the Mobile Client via another internet connection.... Used the Mobile client to transmit to the Parrot system - again Dashboard showed the TX working. Then when parrot replayed my transmission - The mobile client just sat there an did nothing, but the pyUC Client played out my voice and showed me the appropriate data in it's log window.

Talk about weird ass problem lol, anyone have a suggestion here? Steve I know your busy but is anyone else out there that has any ideas?

Praying for a Miracle.
Gareth GM0WUR


Re: DVSwitch Client does not receive

Gareth GM0WUR
 

Hi Steve,

Sorry for the delay - got called away on an urgent matter.
Anyway just back in the shack now so here goes.


Re: DVSwitch Client does not receive

Steve N4IRS
 

I am going to be away from the computer for the next few hours. I'll look at your post when I return. Maybe someone else can look it over and comment.

On 6/30/2021 4:27 PM, steelegwds@... wrote:
Yes same network. The pi is on a lan port of the router the computer running pyUC and the t320 are using the same Wi-Fi which is direct to the router.


Re: DVSwitch Client does not receive

Steve N4IRS
 

Show me your Analog_Bridge .ini and a screen shot of the account settings in Android.

On 6/30/2021 4:27 PM, steelegwds@... wrote:
Yes same network. The pi is on a lan port of the router the computer running pyUC and the t320 are using the same Wi-Fi which is direct to the router.


Re: DVSwitch Client does not receive

Gareth GM0WUR
 

Yes same network. The pi is on a lan port of the router the computer running pyUC and the t320 are using the same Wi-Fi which is direct to the router.


Re: DVSwitch Client does not receive

Steve N4IRS
 

s the T320 on the same network as the DVSwitch Server?

On 6/30/2021 4:08 PM, steelegwds@... wrote:

Ok I’ve done that.
but something weird is going on.


with the RX and TX ports set to the same number, if I use the pyUC that works still.


However on the t320 using the android program it now comes up that it’s not registered and on the Home Screen pressing register has no effect.

Which means it can’t transmit or receive..



Re: DVSwitch Client does not receive

Gareth GM0WUR
 

Ok I’ve done that.
but something weird is going on.


with the RX and TX ports set to the same number, if I use the pyUC that works still.


However on the t320 using the android program it now comes up that it’s not registered and on the Home Screen pressing register has no effect.

Which means it can’t transmit or receive..


Re: DVSwitch Client does not receive

Steve N4IRS
 

Use the same port number in TX and RX Change port numbers in Analog_Bridge.ini and match in Android Client.

On 6/30/2021 3:12 PM, steelegwds@... wrote:
Hi Steve,

no using pyUC or DVSwitch client not trying both at same time as figured that would just confuse the server.

the port settings in pyUC.ini for TX and RX match exactly what’s in the android client (for sanity check I’ve even tested putting them the reverse way round)

Ports reversed - nothing works. No surprise it shouldn’t lol.

ports correct - client can talk / send to the server but never receives.

cheers

gareth


Re: DVSwitch Client does not receive

Gareth GM0WUR
 

Hi Steve,

no using pyUC or DVSwitch client not trying both at same time as figured that would just confuse the server.

the port settings in pyUC.ini for TX and RX match exactly what’s in the android client (for sanity check I’ve even tested putting them the reverse way round)

Ports reversed - nothing works. No surprise it shouldn’t lol.

ports correct - client can talk / send to the server but never receives.

cheers

gareth


Re: DVSwitch Client does not receive

Steve N4IRS
 

Gareth,
Do you have pyUC connected to the server while you are trying to use the Android client? Since you have setup pyUC are you sure you are using the same UDP ports for TX and RX as you are in pyUC?
Check the Analog_Bridge log in /var/log/dvswitch. Any errors?

Steve N4IRS

On 6/30/2021 2:02 PM, steelegwds@... wrote:

Hi All, 
I’m really hoping someone in this group can help me because I’m tearing my hair out. 

I’ve followed every version of the instructions I can find, every tutorial on YouTube yet I can’t make this system work.

ok so firstly I have DVSwitch server running on my Raspberry pi. It works - it’s connected to brandmister  no problems, I can connect the pyUC client via my Mac or PC and that works and I’ve even had one short QSO to the USA.

then we come to the client program on android. I’ve loaded the latest version on to my brand new t320 network radio from Moonraker. I’ve set it up as per the instructions.

and this is where it all goes a bit screwball.

the switch server sees the client, I can change talk groups, if I press PTT the servers diagnostic webpage shows PTT and if you enable the RX monitor function on the servers webpage I can hear my voice.

but…. Receive doesn’t work on the client. The Server is getting traffic, as I’ve said above but nothing is going to the DVSwitch client, it doesn’t show anything on screen, no indication of traffic, no receive audio nothing.

I am at a total loss . Can someone help me please.

many thanks Gareth GM0WUR



DVSwitch Client does not receive

Gareth GM0WUR
 

Hi All, 
I’m really hoping someone in this group can help me because I’m tearing my hair out. 

I’ve followed every version of the instructions I can find, every tutorial on YouTube yet I can’t make this system work.

ok so firstly I have DVSwitch server running on my Raspberry pi. It works - it’s connected to brandmister  no problems, I can connect the pyUC client via my Mac or PC and that works and I’ve even had one short QSO to the USA.

then we come to the client program on android. I’ve loaded the latest version on to my brand new t320 network radio from Moonraker. I’ve set it up as per the instructions.

and this is where it all goes a bit screwball.

the switch server sees the client, I can change talk groups, if I press PTT the servers diagnostic webpage shows PTT and if you enable the RX monitor function on the servers webpage I can hear my voice.

but…. Receive doesn’t work on the client. The Server is getting traffic, as I’ve said above but nothing is going to the DVSwitch client, it doesn’t show anything on screen, no indication of traffic, no receive audio nothing.

I am at a total loss . Can someone help me please.

many thanks Gareth GM0WUR


pyaudio error

Scott-N5HUM
 

While installing pip3 install pyaudio I get errors, I don't know what information you need from me to help troubleshoot, so I'm just going to give you some basics and hope it enough.

MacOS Big Sur

And here is the error I am getting

Collecting pyaudio
  Using cached PyAudio-0.2.11.tar.gz (37 kB)
Building wheels for collected packages: pyaudio
  Building wheel for pyaudio (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/local/opt/python@3.9/bin/python3.9 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/setup.py'"'"'; __file__='"'"'/private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-wheel-9cqmyxy8
       cwd: /private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/
  Complete output (13 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-11-x86_64-3.9
  copying src/pyaudio.py -> build/lib.macosx-11-x86_64-3.9
  running build_ext
  building '_portaudio' extension
  creating build/temp.macosx-11-x86_64-3.9
  creating build/temp.macosx-11-x86_64-3.9/src
  clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -DMACOSX=1 -I/usr/local/include -I/usr/local/opt/openssl@1.1/include -I/usr/local/opt/sqlite/include -I/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9/include/python3.9 -c src/_portaudiomodule.c -o build/temp.macosx-11-x86_64-3.9/src/_portaudiomodule.o
  clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11'
  error: command '/usr/bin/clang' failed with exit code 1
  ----------------------------------------
  ERROR: Failed building wheel for pyaudio
  Running setup.py clean for pyaudio
Failed to build pyaudio
Installing collected packages: pyaudio
    Running setup.py install for pyaudio ... error
    ERROR: Command errored out with exit status 1:
     command: /usr/local/opt/python@3.9/bin/python3.9 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/setup.py'"'"'; __file__='"'"'/private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-record-v1es6l4d/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.9/pyaudio
         cwd: /private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/
    Complete output (13 lines):
    running install
    running build
    running build_py
    creating build
    creating build/lib.macosx-11-x86_64-3.9
    copying src/pyaudio.py -> build/lib.macosx-11-x86_64-3.9
    running build_ext
    building '_portaudio' extension
    creating build/temp.macosx-11-x86_64-3.9
    creating build/temp.macosx-11-x86_64-3.9/src
    clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -DMACOSX=1 -I/usr/local/include -I/usr/local/opt/openssl@1.1/include -I/usr/local/opt/sqlite/include -I/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9/include/python3.9 -c src/_portaudiomodule.c -o build/temp.macosx-11-x86_64-3.9/src/_portaudiomodule.o
    clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11'
    error: command '/usr/bin/clang' failed with exit code 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/local/opt/python@3.9/bin/python3.9 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/setup.py'"'"'; __file__='"'"'/private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-install-zmgy9yaz/pyaudio_8560109972a04a4f8e84b168761fd52d/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/wd/ybl4w0v11l550xn89_ybzhxm0000gn/T/pip-record-v1es6l4d/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.9/pyaudio Check the logs for full command output.


Re: Trying to install and setup DV switch on android

Steve N4IRS
 

You made backups of the files before you modified them. You can restore the backups if you have a problem. Since you are running ClearNode, I would contact Gerry from ClearNode since he overwrites the config files from templates. I sent him the info months ago so that he could incorporate the changes needed into the templates.

Steve N4IRS

On 6/27/21 3:25 PM, Joe Quinn wrote:
Given the fact that I’m really not sure what I’m doing, and I just wanna make sure that my files are the way they’re supposed to be, is there a place that I could email you my files so you could see if they’re correct? Would you mind doing that?


Re: Trying to install and setup DV switch on android

Joe Quinn
 

Given the fact that I’m really not sure what I’m doing, and I just wanna make sure that my files are the way they’re supposed to be, is there a place that I could email you my files so you could see if they’re correct? Would you mind doing that?

1001 - 1020 of 10557