开云体育

I hate to say this, but you may have a bad clone. I have ran the self test on my two SA's after updating the firmware and they both passed all tests.
The other thing could be a bad solder connection on the board.
Just a thought.
Clyde KC7BJE?

What exactly is it that is failing, as all clones seem to have the same screenshot which should be a bandpass but looks like a flat response with a kink in it.

Are the 400mhz saw filters missing?

Can they be inserted, as presumably the circuit board will have been copied from original, so presumably there would be space to insert them.

Steve L

I know that Eric has already ID this as a clone. Can you take a photo of the back of the unit. This will also help others IDing clones. I think Eric said that clones do not have S/N on the back of the unit. Would be interesting to see what the back of your unit looks like..

Thanks,
Brian D
KF6BL

One more here

I am amazed to see how good this is working for the price. The PC software is also working great.

Thank you Erik!

This is normal
The stairs come from the stepwise increase of internal amplifications of the auto AGC algorithm
If you want to measure very weak signals below 1MHz I suggest to set the AGC to on? (not automatic) and the LNA also on (not automatic)
See this video with very detailed explanation:?

--

Hi2all.

My TinySA Fail at first on Test 7.

I also look at the BFS in the Expert Menue.

Is it an Hardwaredefekt?
Does anyone have any advice on why?

Michael.

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