The aver16 is a 1/16 running average so it will be a bit like a qpd
--

Has their been any discussion on adding a Quasi-Peak Detector (QPD) algorithm in addition to the averaging/min/max detection algorithms?

If so, would it likely go into the tinySA app?

One of the projects I was asked to 'covertly' develop (one of those jobs where we weren't allowed to share any info with co-workers in the same room what I had been tasked with) was a system to transfer wireless power together with a low data rate (4800bits/s) communications channel to operate across the gap between a door frame and the door (which contained a solenoid lock).

Because it was 4 decades or so ago RF tech wasn't as it is today, so I decided to use cheap readily available parts (costs are always a main concern) which happen to be a couple of 6"ish ferrite rods (as used in LW/MW radios) because they would also easily fit inside a door frame and the door side by side (energy across the 1" gap), I decided on a frequency of 125kHz for the wireless power transfer and comms frequency - might give you a clue as to what it later turned into ;)

/g/tinysa/message/2215 iain wrote:
> heres another great load of videos about tinySA and other stuff
> Imsai Guy,,his videos are great

> iain MM6IXE

Hello iain,
It would be fair to Erik to not only link the first video of Imsay Guy,
where he did not understood (or read) the specified limits of the tinySA.

You should link also/or from Imsay Guy:
#536c TinySA Update: Works well below -30dbm


73, Rudi DL5FA

I never have NFC enabled but thought I'd see how well a tiny RF loop works at NFC frequencies (13.56MHz in this case) ..

开云体育

?hi Bjorn
heres another great load of videos about tinySA and other stuff
Imsai Guy,,his videos are great



iain
MM6IXE

Or a different computer, my Dell i5 wouldn't recognize the ID of the tinySA but both my Acer and Toshiba i3 computers had no problems. All have W10.?

Have you tried using STCube?

Did you use a USB 3.0 port? If so please try a USB 2.0 port
--

I have Windows 10 64bit home on a full desktop; I have tried repeatedly to connect with my tinySA to no avail; what are the proper steps to do this? I'm not getting a new com port connection, and the tinysa APP com interface shows repeats of timeout, no connection

Thank you Bernie!? I wil !!

Bjorn

Welcome to this great group!

Have a look at Erik’s YouTube channel for his excellent videos on the TinySa.
--
73, Bernie, VE3FWF
(most typos in this message were generated by highly sophisticated auto-correction software)

Hello everybody! I just purchased a tinySA and joined this group today. Looking forward to work with the group.

73 de Bjorn
LA1BN

I experienced a similar problem, very slow using DfuSe, never completed the erase stage, after multiple aborted attempts I got the white screen.
Not content with doing that, I did the same thing to a second tinySA unit. The computer being used was a Dell Inspiron 3693 core i5 10th gen.
I spent a considerable amount of time trying the two USB 3.0 and single USB 2.0 ports with 2.0 and 3.0 cords to restore these units using
DfuSe 3.0.4 & 3.0.6 and none were successful. After a good amount of research I then downloaded STCube and tried that - it also failed.

Finally, in desperation I downloaded STCube onto my i3 Acer tablet that I use as a HTPC, it worked like a charm, upgraded to 1.1-32 very quickly.
Then I tried to read the units using STCube on the Dell i5 and was constantly greeted by the error message "flashloader cannot be loaded".
I then downloaded STCube to a Toshiba Satellite L755-S5344 i3 and it read both devices with no problems. The Acer & Toshiba have only USB2.0 .

In looking at STCube, the failure on the Dell is in the software being unable to determine the "device ID" and returning the term "unknown",
which in turn causes the failure to load the flashloader because it cannot load the 0x448 database profile for the STM32F072.
So this begs the question, why is STCube able to read the deviceID of the tinySA on the Acer & Toshiba computers but fails on the Dell,
even when using the USB2.0 port? I have tried purging the Dell of all ST programs and drivers and re-loading STCube multiple times but it still fails.

If anybody else has run into this issue and found the solution I would love to hear about it.

I thank both Herb and Erik for their prompt replies,

larry

Some more explanation:
The optimal value of the capacitors is a balance between the speed of the serial communication bus and the spurs the bus is creating.
The optimal capacitor values could only be decided after testing with a larger quantity of products by a broader set of users and this took some time as you can imagine.
Once the testing came to a conclusion we adapted the capacitors in production and I decided to publish the information on how buyers of the limited quantity early products could, if they felt the need, adapt their tinySA to have a bit? less spurs at the 48MHz harmonics.
If you are not bothered by the already fairly low level? of the 48MHz harmonics or find it difficult to add the tiny components I suggest not to add the capacitors as these harmonics can be easily recognized because they are on a 48MHz grid and have some FM modulation.

On Thu, Nov 26, 2020 at 03:15 AM, Lawrance A. Schneider wrote:

I have version H0.3 . ?But again, the terminals are there so why not populated? ?My 75 year old eyes and hands will be having a hard time. ?Plus, I have 0 (zero) SMD caps.

Larry,
? ?There are other pads on the board that are unpopulated also.? Designers usually add areas like that for future features or increased performance.? The tinySA meets its specifications without the caps and most users won't even be bothered by the 48MHz harmonics which are greater than -80dBm.? For those users who have a need for slightly greater noise performance the caps offer a way of achieving that.

?All currently manufactured tinySA's are version 0.3, in later production runs it looks like the caps were added based on the feedback of early users.? Sometimes being an early adopter has its disadvantages.

?- Herb

One of the feedbacks i have found on Banggood for the unit with display:

Fast delivery It did not exactly fit my needs and expectations. The analyzer needs at least a 30dB amplifier otherwise it is as deaf as a stone. It does not even indicate a a local FM radio station with an VHF antenna attached to it - unless an 30dB amplifier is in series with the antenna. I intended it to use on the IF exiting my FT1000D as a spectrum display but the bandwidth and resolution are not sufficient for such an application. The lowest span is 3Mhz and the lowest RBW is 5Khz /Kc. The?display is bright and clear and very good to read. It might be a good idea to buy an additional rechargeable lithium battery for it

Hello Herb,

> Hugen probably started installing the capacitors on later production runs at Erik's suggestion.

I have version H0.3 . ?But again, the terminals are there so why not populated? ?My 75 year old eyes and hands will be having a hard time. ?Plus, I have 0 (zero) SMD caps. ?I'll ask my friend Andy at the Uni if he has some. ?The problem is 'she who must be obeyed' will not allow me anywhere near the Uni. ?Last I heard, there were 47 cases there.

Thank you for your reply, ? ? ? ?larry ? ??