¿ªÔÆÌåÓý

New FW release: Reduced CPU clock spurs and scanraw progress bar


 

New FW release
Version v1.1-88

Changes:
- The spurs caused by the 48MHz MCU clock have been reduced.
- The scanraw command progress is displayed using the green progress bar.

tinySA-App uses the scanraw command and with a large number of points and a low RBW it often is not obvious if the tinySA is still? scanning or how long? it would take till the end of the scan. The green progress bar give better insight in scanraw progress.

The mechanism used to reduce the MCU spurs makes some assumptions which I would like to see verified by some users.
Can some of you test this using the console command:
selftest 6
In reply you get a list of frequencies.
I'm interested in the frequencies listed after 12 to 20
This is what I get.
12:? ?94.602M
13:? ?94.989M
14:? ?95.377M
15:? ?95.764M
16:? ?96.069M
17:? ?96.456M
18:? ?96.844M
19:? ?97.231M
20:? ?97.536M
?
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

To give an impression of the spur improvements

v1.1-86 spurs when using an RBW of 10kHz


Same using the new v1.1-88 FW

--
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

¿ªÔÆÌåÓý



This is what I get.
12:? ?94.602M
13:? ?94.989M
14:? ?95.377M
15:? ?95.764M
16:? ?96.069M
17:? ?96.456M
18:? ?96.844M
19:? ?97.231M
20:? ?97.536M
?

my list is:

12:??? 96.484M

13:??? 95.211M

14:??? 95.626M

15:??? 95.958M

16:??? 96.373M

17:??? 96.705M

18:??? 97.093M

19:??? 97.397M

20:??? 96.650M?


Greetings

Sven Hegewisch

------------------------------------------
For more info on the tinySA go to


 

Erik,
I ca not seem to get seftest 6 to work. Using the console command interface it says the correct syntax is: selftest (1-3) [arg]. I am on 1.1-85
Gary


 

One user reported a small selftest failure starting after upgrading to v1.1-88
This failure can not be caused by the upgrade to v1.1-88 but the coincidence is a bit worrying.

All that upgrade to v1.1-88, please be sure to run the selftest before and after the upgrade and report any differences in the selftest you notice after the upgrade to v1.1-88

------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

Selftest 6 is? only available in v1.1-88 and only relevant after upgrading to v1.1-88

--
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

On Wed, Feb 17, 2021 at 06:32 AM, Erik Kaashoek wrote:
To give an impression of the spur improvements using the new v1.1-88 FW ....

Erik,
I had already installed the recommended bypass capacitors on the pcb to knock down the 48MHz spurs.? With the new v1.1-88 FW,?I saw further improvement.? I would suggest anyone considering installing the bypass capacitors first install? v1.1-88 FW and see if that resolves their issues.

? ??

Results of my self-test 6.

selftest 6
59.384 rx: 12:? ?94.574M
59.634 rx: 13:? ?94.961M
59.900 rx: 14:? ?98.505M
00.166 rx: 15:? ?98.560M
00.431 rx: 16:? ?96.124M
00.681 rx: 17:? ?96.484M
00.947 rx: 18:? ?98.505M
01.197 rx: 19:? ?98.477M
01.462 rx: 20:? ?98.532M

- Herb


 

Installed 33pF capacitors (long time ago)

All test complete
Command:
selftest 6
ch> 0:? ?97.397M
1:? ?98.006M
2:? ?98.892M
3:? ?92.083M
4:? ?92.442M
5:? ?92.802M
6:? ?93.217M
7:? ?93.577M
8:? ?93.079M
9:? ?93.467M
10:? ?93.882M
11:? ?94.214M
12:? ?94.574M
13:? ?94.934M
14:? ?95.321M
15:? ?95.681M
16:? ?96.207M
17:? ?96.595M
18:? ?96.955M
19:? ?97.342M
20:? ?97.674M
21:? ?98.062M
22:? ?98.422M
23:? ?98.782M
24:? ?98.062M
25:? ?98.449M
26:? ?98.809M
27:? ?99.169M
28:? ?99.557M
29:? ?99.916M
30:? ?99.363M

But after run selftest from console, device hang after power on, clearconfig not help


 

Hmm, i restore back to work after push CPU, look like bad soldering


 

Hello Erik,

selftest 6
ch> 0:?? 96.678M
1:?? 96.705M
2:?? 96.705M
3:?? 96.678M
4:?? 96.705M
5:?? 92.608M
6:?? 96.705M
7:?? 96.678M
8:?? 93.743M
9:?? 94.159M
10:?? 96.705M
11:?? 94.906M
12:?? 95.266M
13:?? 95.626M
14:?? 95.349M
15:?? 95.737M
16:?? 96.124M
17:?? 96.512M
18:?? 96.844M
19:?? 97.204M
20:?? 97.591M
21:?? 97.979M
22:?? 98.394M
23:?? 98.782M
24:?? 99.141M
25:?? 99.474M
26:?? 99.861M
27:?? 96.705M
28:?? 94.408M
29:?? 96.678M
30:?? 96.705M

Attached are 2 screenshots with firmware 86 and 88, no spurs.
Installed 33pF capacitors some time ago.

73, Rudi DL5FA
????


 


Spoors at 25.432M and 9.688M


 

Check if there is another device close by.
Even a PC keyboard or mouse can cause problems
--
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

Thanks for the selftes 6 output.
All confirm what I was hoping for.
No more needed
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

Attached are 2 screenshots with firmware 86 and 88, no spurs.
Installed 33pF capacitors some time ago.
73, Rudi DL5FA



 

Please notice the RBW I used in my screen grabs
--
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/


 

Hello,
where is the topic? 33pF capacitors modification description? I want to try to improve the spurious.


 

My test.
Thank you for your work !!
73.


 

On Wed, Feb 17, 2021 at 09:27 PM, Erik Kaashoek wrote:
Please notice the RBW I used in my screen grabs
Thank you Eric,
now with RBW 10 kHz, no longer so good.

73, Rudi DL5FA


 

Hello Eric,
After some measures it looks very good:
Firmware v1.1-88
RBW 10 kHz
33pF capacitors soldered
Input LOW shorted
USB cabel connected

Just the local FM Radio station on 105.845 MHz is visible.

73, Rudi DL5FA


 

SN 20070285

03.297 rx: 12: 95.266M
03.549 rx: 13: 94.934M
03.797 rx: 14: 95.294M
04.052 rx: 15: 95.681M
04.297 rx: 16: 96.069M
04.610 rx: 17: 96.429M
04.859 rx: 18: 96.816M
05.109 rx: 19: 97.204M
05.358 rx: 20: 97.564M

On Wed, 17 Feb 2021 06:05:24 -0800
"Erik Kaashoek" <erik@...> wrote:

New FW release
Version v1.1-88

Changes:
- The spurs caused by the 48MHz MCU clock have been reduced.
- The scanraw command progress is displayed using the green progress bar.

tinySA-App uses the scanraw command and with a large number of points and a low RBW it often is not obvious if the tinySA is still? scanning or how long? it would take till the end of the scan. The green progress bar give better insight in scanraw progress.

The mechanism used to reduce the MCU spurs makes some assumptions which I would like to see verified by some users.
Can some of you test this using the console command:
selftest 6
In reply you get a list of frequencies.
I'm interested in the frequencies listed after 12 to 20
This is what I get.
12:? ?94.602M
13:? ?94.989M
14:? ?95.377M
15:? ?95.764M
16:? ?96.069M
17:? ?96.456M
18:? ?96.844M
19:? ?97.231M
20:? ?97.536M

------------------------------------------
For more info on the tinySA go to