Received mine today (Holland) Never been able to buy an SA, this little beauty makes me extremely happy After switching it on. Thanks for making this possible.?

Huub

Received mine in Houston today, 12 days after placing order.

--
John AE5X

On Wed, Aug 5, 2020 at 12:05 AM, Erik Kaashoek wrote:

On Tue, Aug 4, 2020 at 05:20 PM, hwalker wrote:

Prior to the version 1.0-49 FW update a level calibration on my v0.3 tinySA would set leveloffset low to '0' which gave me a measurement error of < 1dB across the board measured against an external signal source.? With v1.0-49 a level calibration is now setting leveloffset low to '1.7' and my measurements against an external signal source are off by about that amount.? I have to manually set 'leveloff low 0' to regain my <1dB accuracy.? This using the new correction table.

Herb,
Can you check if the same is happening when you manually calibrate using the 30MHz cal output, center = 30MHz and span=10MHz and then an ACTUAL POWER set to -25?
If that gives a good result can you manually calibrate using? the 30MHz cal output, center = 30MHz and span=60MHz and then an ACTUAL POWER set to -25?
I'm most interested in the difference in calibrating powerlevel using ACTUAL POWER using a span of 10MHz versus a span of 60MHz.

Erik,
? ?My calibrator signal level (-26.7dBm)?is low by 1.7dB? which explains the leveloffset low issue. If I enter CONFIG->EXPERT CONFIG->ACTUAL POWER: -26.7 ?then my leveloffset low value is '0' as expected.? I did not experience this issue prior to v1.0-49, at least not that I can recall.? I changed inter-connecting cables to verify that my cable was not at fault by 1.7dB.

30MHz@10MHz?Span.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 30MHz@60MHz?Span.
? ??

In any event, manually entering the actual powered measured at 30MHz, using a 10MHz span, is a satisfactory alternative level calibration procedure -? if the 30MHz calibrator level differs from -25dBm by more than a dB or so.

- Herb

开云体育

On Tue, Aug 4, 2020 at 11:06 PM, DuWayne Schmidlkofer wrote:

Herb
I hope you don't mind, but i plan on using a couple of your pictures on my blog.? I received my TinySA today, and have been having some problems with my camera.? Your pictures of the packaging is much nicer than I was able to get.? This packaging is much nicer than I have found in similarly priced products of any type.

DuWayne,
? ? I'm glad you found the pictures useful.? Be my guest to use them as you wish.

- Herb

On Tue, Aug 4, 2020 at 05:20 PM, hwalker wrote:

Prior to the version 1.0-49 FW update a level calibration on my v0.3 tinySA would set leveloffset low to '0' which gave me a measurement error of < 1dB across the board measured against an external signal source.? With v1.0-49 a level calibration is now setting leveloffset low to '1.7' and my measurements against an external signal source are off by about that amount.? I have to manually set 'leveloff low 0' to regain my <1dB accuracy.? This using the new correction table.

Herb,
Can you check if the same is happening when you manually calibrate using the 30MHz cal output, center = 30MHz and span=10MHz and then an ACTUAL POWER set to -25?
If that gives a good result can you manually calibrate using? the 30MHz cal output, center = 30MHz and span=60MHz and then an ACTUAL POWER set to -25?
I'm most interested in the difference in calibrating powerlevel using ACTUAL POWER using a span of 10MHz versus a span of 60MHz.

Herb
I hope you don't mind, but i plan on using a couple of your pictures on my blog.? I received my TinySA today, and have been having some problems with my camera.? Your pictures of the packaging is much nicer than I was able to get.? This packaging is much nicer than I have found in similarly priced products of any type.
DuWayne KV4QB

Mine just arrived, looks great so far.? I can see where it will take some time to get familiar with all the features and settings.

On Tue, Aug 4, 2020 at 08:57 AM, Erik Kaashoek wrote:

New FW released
version v1.0-49

Changes:
- Corrected a rounding error in the level calibration causing up to 1dB level error

Due to a data format change you will lose your configuration information. If you have made any changes you should redoc these after updating.
Both high and low mode level calibration should be re-done using either the built-in calibration source or an external known level signal.
The calibration error off factory should be less then 2dB so after this FW update your levels should be within 2dB without calibration.

Erik,
? Prior to the version 1.0-49 FW update a level calibration on my v0.3 tinySA would set leveloffset low to '0' which gave me a measurement error of < 1dB across the board measured against an external signal source.? With v1.0-49 a level calibration is now setting leveloffset low to '1.7' and my measurements against an external signal source are off by about that amount.? I have to manually set 'leveloff low 0' to regain my <1dB accuracy.? This using the new correction table.

?The v0.2 beta unit has benefited from the FW update. Level calibration sets 'leveloffset low' to a value of -0.7 which resulted in??a measurement error of < 1dB across the board measured against an external signal source. This using the new correction table.

?FW updates including 'clearconfig 1234' set 'leveloffset low' to 100 and measurements at some frequencies in this uncalibrated state exceeded 2 dB at the limits of the measurement range.? In this case a level calibration is necessary and then possibly some fudging of the leveloffset low value.

?In the end, I used the leveloffset low value the level calibration calculated for my beta unit, but had to manually restore my previous leveoffset low value for the production unit.

- Herb

开云体育

New FW released
version v1.0-49

Changes:
- Corrected a rounding error in the level calibration causing up to 1dB level error

Due to a data format change you will lose your configuration information. If you have made any changes you should redoc these after updating.
Both high and low mode level calibration should be re-done using either the built-in calibration source or an external known level signal.
The calibration error off factory should be less then 2dB so after this FW update your levels should be within 2dB without calibration.

I assume the VAT hurt but the "etc" hurt more. How much does DHL charge in "brokerage" (or whatever) fees in the UK?

My TinySA arrived today. I unpacked it in front of the DHL driver while he waited as I told him, it it was damaged I wanted to show him. It came in a TyVAC envelope inside a TYVAC envelope. Then 1 wrap of small bubble, and a brown cardboard box. Inside it was wrapped again in small bubble wrap, and the presentation box was perfect. I signed and went inside. I had read that you need to check it before signing. And I did.

I immediately put it on a charger 5V @ 0.240A measured.. In 2 hours it was fully charged. I took it over to a friend to show him, and found the only negative so far..

THE SCREEN IS TOTALLY WASHED OUT IN KANSAS SUNLIGHT.

Yet in my truck it was readable on the dash..? So if planning to use it in the field better devise a "viewing box."

Now time to read everything about it..as my intention is to first do some cable leakage testing in the area.

Make sure to run selftest!

just? delivered. Nice.

DHL added (to UK) ?21.36 vat etc.

Quick check with a few sig gens and certainly responsive.

72

Dom
M1KTA

1: Is clear. It will depend on available memory. Not sure yet
2: Occupied bandwidth is clear. Specify center freq and channel width and calculate the power inside and outside channel. probably use maxhold to get the curve.

On Sat, Aug 1, 2020 at 12:50 PM, Erik Kaashoek wrote:

On Fri, Jul 31, 2020 at 07:41 AM, hwalker wrote:

editable transducer factor table
? ?3.?automatic OCBW (occupied bandwidth) measurement

Can you give a bit of background on these

Erik,
?1.? I would envision the editable transducer factor table being similar to your level correction table.? The main difference would be a menu option allowing the user to enter up to 9(?)? freq/value pair that are added to the displayed values as conversion or correction factors.? There may not be sufficient memory in the firmware to allow this with all the other features you have provided.? The other problem would be changing the display units, if say, the factors converted units from dBuV to dBuA.? Maybe something to consider adding to TinySA.exe instead.

2. The automated occupied bandwidth measurement is a feature one of my club members demonstrated on Siglent spectrum analyzer.??Occupied bandwidth measurements are used to measure the power of the occupied channel as a percentage to the power of the channel.? I 'm not sure what algorithm was used for the measurement. Jim Allyn?has a Siglent specan and might be able to shed light on the measurement procedure.?

- Herb