Page 4 of 5

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 9:02 am
by VK3KYY
IK8JHL wrote:
Tue Mar 03, 2020 8:23 am
There is a bug :
Start scan
Click left arrow --> scan its inverted to down frequency
stop scan with any key
click arrow UP---> the frequency decreases instead of increasing


NB but it was not possible to use the up and down arrows for more than 2 seconds for start scan ,thus leave free orange key :?: ?
I will investigate the bug

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 9:18 am
by VK3KYY
Its now fixed

Download the Latest version

https://github.com/rogerclarkmelbourne/ ... latest.sgl

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 9:32 am
by IK8JHL
Yes now its OK
;)

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 9:40 am
by VK3KYY
IK8JHL wrote:
Tue Mar 03, 2020 9:32 am
Yes now its OK
;)
It was my mistake, I checked the wrong setting. I should have checked whether the scan as "active", but instead I check the scan phase.

i.e I did consider this could happen, but didn't do the correct thing to prevent the bug.

The code in the VFO screen is now very complicated ;-)

Its now over 1500 lines of code

https://github.com/rogerclarkmelbourne/ ... iVFOMode.c

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 9:46 am
by IK8JHL
You are doing a great job, the bugs are part of the experimentation ;)

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 7:08 pm
by G0NHF
I’m experiencing a strange click in the speaker ever time I TX on DMR. I think this might be related to the TX beep tone that’s been added in recent releases, but I have the beep volume set at -24dB in the options menu. Despite this the speaker gives an irritating click on each start of TX. The previous build I was using didn’t do this (26 Feb 20)

Tony G0NHF

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 7:16 pm
by SQ7PTE
Oh, there is the first person dissatisfied with the new function. However, there should probably be a choice to enable or disable this option.

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 7:18 pm
by SQ7PTE
G0NHF wrote:
Tue Mar 03, 2020 7:08 pm
I’m experiencing a strange click in the speaker ever time I TX on DMR. I think this might be related to the TX beep tone that’s been added in recent releases, but I have the beep volume set at -24dB in the options menu. Despite this the speaker gives an irritating click on each start of TX. The previous build I was using didn’t do this (26 Feb 20)

Tony G0NHF
Oh, there is the first person dissatisfied with the new function. However, there should probably be a choice to enable or disable this option.
Personally, a fantastic option.
Greetings to the creators - great work. Thank you.

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 9:37 pm
by G0NHF
Not dissatisfied, but just pointing out what I have noted compared to the 26 Feb release that I was using previously. My post wasn’t intended as a criticism. I always turn the beep volume as low as possible because I don’t personally find keypad beeps useful as the physical keypad feedback clicks are loud enough for me on their own. I wasn’t suggesting the TX beep isn’t useful but when the beep volume is set low, the TX beep does appear to cause a pop/click on the speaker on every TX. This click is only present on DMR not FM, which suggests it is related to the TX beep on DMR. Certainly not a criticism, but just what I have noted when using this version of the firmware.

Regards, Tony G0NHF

Re: Experimental versions to fix potential speaker hiss

Posted: Tue Mar 03, 2020 10:03 pm
by VK3KYY
Tony

The click is unavoidable as its caused by a hardware design fault in the audio amp.
But the Tx Permit beep could be added as an option to disable.

The whole Options probably needs to be overhauled and split onto different sections, as its already larger than is optimal for one screen.
There probably needs to be a Sound Options subsection, and the Display Options would then be moved to be a sub section of the options
And we'd need Scan Options and version other categories

This level of changes would probably need to be done by community agreement and design.