¿ªÔÆÌåÓý

Hello Linuxers, I have problems with TinySA-Saver in my Debian 10 LXDE installation. Please look at following dump, you possibly discover what I missed. TNX, 73 Martin,

Modern EMI receiver (e.g. ~100k€) do the quasi-peak detection inside an FFT scan but it also costs more scan time than normal average/peak detection. The problem with quasi-peak is, that it should

Ok I have noted it. I was just about to throw it away so gave it the old faithful. Pete Waters

The quasi-peak bandwidths and sweep times are specialized resulting in very slow scan times.? Usual procedure is to first do a peak scan and if all emissions are below the limit no quasi-peak scan is

Dirt and dust sticks to 3 in one, and it gets thicker and less "lubey" over time.? There are two products I highly recommend for that sort of thing, both from Caig: Deoxit D5 and MCL Moving Contact

So quick attack and slow decay per frequency? Or only in zero span mode? Which attack and decay times? -- ------------------------------------------ For more info on the tinySA go to

Or another USB cable? -- ------------------------------------------ For more info on the tinySA go to https://tinysa.org/wiki/

Quasi-peak detection works more like pulse-width modulation (PWM), the higher the repetition rate the greater the output.? A high repetition rate emission will be close to the value of a peak

I worked in EMC for a number of years and don't remember there being a DSP algorithm for quasi-peak detection.? All our receivers used physical quasi-peak detectors.? That was a number of years ago

And that was before he updated to the new FW -- ------------------------------------------ For more info on the tinySA go to https://tinysa.org/wiki/

The aver16 is a 1/16 running average so it will be a bit like a qpd -- ------------------------------------------ For more info on the tinySA go to https://tinysa.org/wiki/

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

/g/tinysa/message/2215 iain wrote: 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

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) .. https://youtu.be/wpl6UPnVl-U

I live under a dark cloud.. and bought two TinySA¡­ both had a problem of not continuing the sequence of touch commands.. I fixed one after a lot of physical messing.. as the select switch to the

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

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 -- ------------------------------------------ For more info on the tinySA go to https://tinysa.org/wiki/