Bad/poor Audio report

iu2ezb
Posts: 7
Joined: Thu Sep 07, 2017 10:33 am

Bad/poor Audio report

Post by iu2ezb » Mon Sep 11, 2017 7:19 am

Good Mornig to all,
after have searched and read quite all (I hope) posts regarding poor audio report, I'm still receive a poor audio report from my friends during a QSO.
Many time I've performed Auto call or changed manually the demod parameter!
Using a echo test with only SharkRF (private call on 9999) in effect there is a problem.
Sometimes give a optimal response but other time you can heard some "glitches" and not clearly audio. I'm using a HYTERA AR685G.
Using a Shark of friends's of mine this not happen (same my configurartion and my same radio I'm their, let me say, radio manager, because I'm their testing man for radio and more)
I've tried to change inner deviation from default of 648Hz to 650Hz and set the modulation to 4FSK (raised cosine) to pure 4FSK.....in practice I tried them all!
I start thinking that my SharkRF is defective on DMR side!
Please do you have other IDEAs or parameter(s) to try to change?

73 de IU2EZB Silvio

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 2820
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: Bad/poor Audio report

Post by HA2NON » Mon Sep 11, 2017 7:46 am

Please do local echo tests with latest beta fw v127.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

iu2ezb
Posts: 7
Joined: Thu Sep 07, 2017 10:33 am

Re: Bad/poor Audio report

Post by iu2ezb » Mon Sep 11, 2017 10:12 am

HA2NON wrote:
Mon Sep 11, 2017 7:46 am
Please do local echo tests with latest beta fw v127.
Ok Norbert,
I've just upgrated with beta 0127 and after a first echo test with only sharkRf and than with BM seems to be gioing better in next QSO and days I hope to receive a better report

thanks a lot

73 de IU2EZB Silvio

iu2ezb
Posts: 7
Joined: Thu Sep 07, 2017 10:33 am

Re: Bad/poor Audio report

Post by iu2ezb » Tue Sep 12, 2017 8:03 am

Hi Norbert,

regarding the audio issue, I'm noting tha same problem also with firmware v127. the audio is not clearly as per local echo as per BM echo test.
Performed some differents setting in "DMR demodulation mode" and autocal but substantially the result not change. With Autocal the better value found is D.

any other suggestion! I'm going crazy :-)

Tyrbiter
Posts: 253
Joined: Thu Dec 22, 2016 11:25 pm

Re: Bad/poor Audio report

Post by Tyrbiter » Tue Sep 12, 2017 10:08 am

You could try setting the frequency trim to medium in the channel settings, the 4FSK modulation is quite narrow and the error rate may be higher if you have an trim set to low (seems to be the default in CPS)
Brian

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 2820
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: Bad/poor Audio report

Post by HA2NON » Tue Sep 12, 2017 1:35 pm

Do you mean that the local echo and BM echo test results are different?
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

iu2ezb
Posts: 7
Joined: Thu Sep 07, 2017 10:33 am

Re: Bad/poor Audio report

Post by iu2ezb » Wed Sep 13, 2017 5:18 pm

HA2NON wrote:
Tue Sep 12, 2017 1:35 pm
Do you mean that the local echo and BM echo test results are different?
Hi Norbert,

sorry for my late in answering but I've used this time, to try, try and try over again. I've same result as per local echo test (only shark by 9999) and also with BM echotest!!!
Anyway also during my last qso my correspondent reporting me a non perfect audio, reporting the tendence to quite continuosly "slip". This happens both with ADSL and 4G connection.

thanks Again for your support

iu2ezb
Posts: 7
Joined: Thu Sep 07, 2017 10:33 am

Re: Bad/poor Audio report

Post by iu2ezb » Wed Sep 13, 2017 5:21 pm

Tyrbiter wrote:
Tue Sep 12, 2017 10:08 am
You could try setting the frequency trim to medium in the channel settings, the 4FSK modulation is quite narrow and the error rate may be higher if you have an trim set to low (seems to be the default in CPS)
Hi trybiter I'm using an hytera Ar685g e not TYT380/RT3 where it possible change those parameters (I mean)

Thank Silvio

Tyrbiter
Posts: 253
Joined: Thu Dec 22, 2016 11:25 pm

Re: Bad/poor Audio report

Post by Tyrbiter » Wed Sep 13, 2017 6:26 pm

iu2ezb wrote:
Wed Sep 13, 2017 5:21 pm
Tyrbiter wrote:
Tue Sep 12, 2017 10:08 am
You could try setting the frequency trim to medium in the channel settings, the 4FSK modulation is quite narrow and the error rate may be higher if you have an trim set to low (seems to be the default in CPS)
Hi trybiter I'm using an hytera Ar685g e not TYT380/RT3 where it possible change those parameters (I mean)

Thank Silvio
I believe you can use some Hytera tuning software to adjust this. There were some problems with Hytera 6xx series handhelds, it's in one of the many other threads on the forum.
Brian

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 2820
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: Bad/poor Audio report

Post by HA2NON » Thu Sep 14, 2017 6:56 am

One of our customers had issues with his PD680s. The working ones transmitted on 435.0011 MHz, and non-working ones on 435.0005 MHz to openSPOT at 435.0000Mhz. He used the tuner software from Hytera and copied the reference frequency of a working PD680 (value 2037) to non-working PD680s (they were set to 1976) and then all of his PD680s started working.

The easier way is to modify openSPOT's RX and TX frequencies in 100Hz steps and maybe it helps.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

Post Reply