Now that I understand. the -40 of the external amplifier is already installed in the calculation. That is, when I re-enter -20, the system assumes the highest value that would be -6 and since I am -40, it now displays -46. got it. The confusion is because of the default -76 ..- 6.

yea. perfect, but enter LEVEL at -20 and External at -40 and do this twice.

As you can see the stop band critical message can be ignored as it's too far away from the BPF center to be of any concern.
Will see if I can make a small adjustment to avoid this message,

Thanks for the quick response:

I also noticed another anomaly about the update. I usually update using dfu-util to upload the "dfu" file on MacOS (which works fine for all my other devices and always worked fine before for the TinySA).?

This time I got an error message indicating the file was in the wrong format for this device (Sorry, I can't remember the message exactly). I had no problem updating using the "bin" file.?

I retried again after the self test bug was found and the same thing happened - I could not upload using the dfu file, only the bin file.

I don't know if this is anything to do with the problem or not...

---------------

Interestingly enough, the problem disappears when I connect the device to my laptop running TinySA-App and run the self-test!

I was able to capture it by running the self test and THEN connecting the laptop. The second image is a run with the laptop connected.

thanks,

M

The level show is the level after the external amp
The maximum output level is -6dBm. External amp of -40dB makes new max output level -46dBm
If you need -60 you enter -60
--

In the RF generator mode, there is a small bug in the relationship between (LEVEL: and EXTERNAL AMP) If you enter LEVEL at -20 and an EXTERNAL AMP at -40, it will change LEVEL to -60, Perfect. But if you go back to LEVEL and enter -20, you should have minus -60, but LEVEL will stick to -46 until you enter any value above -46. EX: -47 and it will show -47 instead of showing -87

Could you post a picture of the test #7?

After this update, my unit is failing the self-test #7 "stopband critical". Does anyone have any ideas?

M

On Mon, Dec 21, 2020 at 11:19 AM, Robert Entwistle wrote:

I just upgraded to the V1-1.59 version of the firmware.?

V1.1.-59 does contain the old slider SW, which is more like? a accelerated jog button. Difficult to control
v1.1-65 (in beta) contains the new frequency and level sliders
--

You could also use TinySA-app or NanoVNA-app to grab a screen cap directly from the device.

73

-Jim
NU0C


On Mon, 21 Dec 2020 23:43:58 +0000
"G8DQX list" <list@...> wrote:

John,

because the image as posted to the group is a mere 488 by 366 pixels in
size! If one really wants to post a pic of a screen, it helps to have
the camera *fully* square-on to the screen. Even your iPhone8 can't work
miracles. It may well have been an email client that reduced the image
to that small a size.

Meanwhile, we can probably both be grateful that no Polaroid film, plus
the squeegee, was necessary for this operation! [exeunt, shaking at the
尘别尘辞谤测…闭

73, Stay Safe,

Robin, G8DQX


On 21/12/2020 23:08, John Cunliffe W7ZQ (x-N2NEP) wrote:

I wonder why the text gets screwed up this way when I post a picture

开云体育

John,

because the image as posted to the group is a mere 488 by 366 pixels in size! If one really wants to post a pic of a screen, it helps to have the camera fully square-on to the screen. Even your iPhone8 can't work miracles. It may well have been an email client that reduced the image to that small a size.

Meanwhile, we can probably both be grateful that no Polaroid film, plus the squeegee, was necessary for this operation! [exeunt, shaking at the 尘别尘辞谤测…闭

73, Stay Safe,

Robin, G8DQX

I wonder why the text gets screwed up this way when I post a picture

Herb,
You are correct. I did a few more minor changes and swept a 144Mhz band pass filter with a span of 200Mhz and a RBW of 11khz.? As you can see from the picture, the dynamic range of this setup reaches close to 90db Not too shabby for a 50 dollar analyzer and a handful of parts from the junk box.

On Mon, Dec 21, 2020 at 09:06 AM, John Cunliffe W7ZQ (x-N2NEP) wrote:

If I understand the normalization process right,..and I confess I might be wrong... if I would normalize a -20dbm signal it would set that as 0dbm reference but also take 20db of the dynamic range

? ?Normalization doesn't affect your dynamic range, it just normalizes your set-up to 0dB so that you can measure the actual gain or attenuation of a device under test (DUT) without having to do any mental math.? Its like using the Level->External Amp setting, but it compensates for for the actual gain or attenuation of your set-up using a through calibration instead of assuming a flat numeric value.

? So with the output of your external mixer/amp/attenuator connected directly to the LOW input, after you select Display->Normalize you can then insert your DUT and the actual gain/attenuation will be displayed.

? - Herb

Hi Erik,

Thank you once again for the EXCELLENT features that you continue to add to the TinySA!

I just upgraded to the V1-1.59 version of the firmware.? From what I am seeing, it appears that you have changed the slider function to no longer having a slider triangle.? If I have figured it out correctly, you slide a little from either side of the center of the frequency bar to move slowly.? The further you move from the center, the faster the frequency change rate becomes.? Do I have this correct?? Are there any other behaviors of this new feature implementation that users should be aware of?

Thank you and 73,

Robert, WA2T

Herb,
I am aware of that, the trough signal is pretty it flat only has a small amount of ripple < 2db over full span. I still want to get the output signal as close to 0 dbm as possible. am thinking around -5dbm. If I understand the normalization process right,..and I confess I might be wrong... if I would normalize a -20dbm signal it would set that as 0dbm reference but also take 20db of the dynamic range

Eric, thank you for the reminder of different frequency offset. For the start, this is just something to play with, I was bored last night so I build this for fun to see how it would compare to my HP.?

For those that are building? tracking generator extensions keep in mind to allow for a frequency offset to enable measurement of mixer conversion loss as described in the tinySA wiki measurement example
--

On Sun, Dec 20, 2020 at 11:42 PM, John Cunliffe W7ZQ (x-N2NEP) wrote:

I did something similar today, just a preliminary mock up on a pad board. The frequency of the oscillator can be adjusted about 150kc with the pot on the modulation input.I have a lot of attenuation in the sweep path to get the isolation so the output overall is only about -20dbm but that can be fixed with small adjustable amp to adjust the trace between -10 and -40dbm for small amplifier testing. So far for a first go it looks nice. This high pass filter looks identical on the tracking generator on my HP analyzer.

Looks good John.? Just in case you are not aware, you can normalize your through measurement to 0dB using Display->Normalize to correct for your mock up configuration.

- Herb

I think the best in this case is to use the resource that consumes less flash memory, but if this resource will consume the same amount of memory then it will be more beautiful to use the keyboard, as it will be standard as in low result. I voted for option 2, but this feature alone does not consume more flash memory, as I know you will still want to add more features.

I did something similar today, just a preliminary mock up on a pad board. The frequency of the oscillator can be adjusted about 150kc with the pot on the modulation input.I have a lot of attenuation in the sweep path to get the isolation so the output overall is only about -20dbm but that can be fixed with small adjustable amp to adjust the trace between -10 and -40dbm for small amplifier testing. So far for a first go it looks nice. This high pass filter looks identical on the tracking generator on my HP analyzer.