Just received one TinySA from R&L and testing the unit, updated firmware and calibrated.
I have a question - I see an increased noise floor at 1Mhz and below on the LOW input, it does look the same unconnected or with a 50ohm termination.
Does it look similar on most units or is something specific to this one? Is normal to have spike around zero that will decrease rapidly but I try to understand the specifics for Tiny SA and could not find an example. Just power on the unit and set center freq to 1Meg. Also if someone does know the explanation for the stairs like visible structure.
Thank you for a great little SA.

I have the same Errors.

Sorry, i thing you have a clone just like me.

The tinySA app is not ready for high mode
--

So I have been experimenting with the TinySA, got it for christmas, yes I know not suppose to open till 25th, wife let me.?? So using it on the low input with the app software it works just fine, I have been testing it with our country transmitters and validating the calibration tools.? But trying to get it to go to the high side input and activated it on the SA app it does nothing except lock up.? What is the cause or is it just not ready for this abuse yet?? thanks.

Its already implemented (but not released)
--

Thanks for the responsive support!

I already assumed it was just an overly strict test, but it'll be good to have that corrected.

As ever - thanks for all the work you do!

M

Erik, a less tiring suggestion to solve this, would be to remove the constants -76 ..- 6 in case someone inserts any value into the external amplifier. Then you change the constant of -76 ..- 6 for any other information. Ex: EXTERNAL AMPLIFIER ACTIVATED.

I still need to make the help text depend on the amp setting
--

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