Same situation here, Alan. It goes up maybe 8%-10% when the squelch is set
above threshold. No noticeable effect on either PSDR or the (usually
several) other apps I have running at the same time.
Bill
On Sat, Jul 23, 2011 at 9:40 PM, Alan NV8A n...@charter.net wrote:
On 07/23/11 11:16 am,
...@charter.net
To: FlexRadio Reflector FlexRadio@flex-radio.biz
Cc: W1AEX - Rob w1aex.f...@cox.net
Sent: Saturday, July 23, 2011 8:40 PM
Subject: Re: [Flexradio] Ver 2.1.5: FM mode + squelch = high CPU utilization
On 07/23/11 11:16 am, W1AEX - Rob wrote:
My installation of version 2.1.5 went very
My installation of version 2.1.5 went very smoothly, and it's working
great, however, I have run into one anomaly:
Using a fresh database, while operating in FM mode, when the squelch
slider is moved above the threshold point, my CPU utilization rises from
20% to 70%. At that level PowerSDR
When you say above the threshold point do you mean in a positive (going
to the right) position so that the signal is squelched? Is that where
you see the high CPU?
I do not see any difference between non-squelched and squelched FM in
regards to the CPU utilization.
-Tim
Tim Ellison, W4TME
I also see the big increase in CPU utilization with the radio in
squelched mode (15% goes to70%). Also the Squelch button is always on
when selecting FM mode.
Radio: SDR1000
OS XP Pro SP3
Regards,
Ignacio, EB4APL
Onl 23/07/2011 17:25, Tim Ellison, W4TME wrote:
When you say above the
FM Squelch is always on. You can not turn it off as it is integral part
of the FM RX signal chain. You need to set it to a value of 0 to
un-squelch.
-Tim
---
Tim Ellison, W4TME
Internet Systems Admin. Customer Support Engineer
FlexRadio Systems^(TM)
4616 W Howard Ln Ste 1-150
Austin, TX
OK. We'll investigate this further.
-Tim
---
Tim Ellison, W4TME
Internet Systems Admin. Customer Support Engineer
FlexRadio Systems^(TM)
4616 W Howard Ln Ste 1-150
Austin, TX 78728
Phone: 512-535-4713 Ext. 223
Email: t...@flexradio.com mailto:t...@flexradio.com
Web: www.flexradio.com
Yes, that is correct Tim. Here's a shaky little video showing the anomaly:
http://www.youtube.com/watch?v=BUxtC39w2fA
Rob - W1AEX
-
When you say above the threshold point do you mean in a positive (going
to the right) position so that the signal is
Tim
Confirmation of the FM Squelch issue here
Unsquelched ( SQ=0) - CPU = 16%
Squelched (SQ = 20) - CPU = 74 - 70%
As soon as you move the slider back to a value that opens the Squelch
the CPU value returns to normal (16%)
Two minor items re the new Memory form:
1. previously with 2.022
We are investigating. Thanks for the video. That helps a lot.
-Tim
---
Tim Ellison, W4TME
Internet Systems Admin. Customer Support Engineer
FlexRadio Systems^(TM)
4616 W Howard Ln Ste 1-150
Austin, TX 78728
Phone: 512-535-4713 Ext. 223
Email: t...@flexradio.com mailto:t...@flexradio.com
Web:
Great info. I added it to the bug text.
1. previously with 2.022 double clicking on the selector (Grey Box at
LHS) for a memory row implemented the memory selection and closed the
form now you have to select the Memory press the Select button and then
exit the form - Is this intentional?
On 07/23/11 11:16 am, W1AEX - Rob wrote:
My installation of version 2.1.5 went very smoothly, and it's working
great, however, I have run into one anomaly:
Using a fresh database, while operating in FM mode, when the squelch
slider is moved above the threshold point, my CPU utilization rises
12 matches
Mail list logo
