¿ªÔÆÌåÓý

Date

Re: Antenna Replacement? #tinysa #ultra

 

You can choose any length you like.For low frequency RFI hunting a long antenna is betterThe length determines the "optimal" frequency range it will receive.A quarter wavelength is optimal.
Thanks. I am hunting a few signals ranging from about 10MHz to around 10GHz. Will do my calculations.


Re: Antenna Replacement? #tinysa #ultra

 

I would hesitate to put a longer antenna on the tinysa or nanovna from a mechanical point of view - it will put a lot of strain on the sma and could ultimately break the connector from the pcb.

What I have tried is using my RTL-SDR antenna which has a soft cable link from the SMA to the antenna. So at least less strain but it is unwieldy. And that is a dipole antenna so I am also having to read up on what effect that has.


Re: Antenna Replacement? #tinysa #ultra

 

On Fri, Jan 13, 2023 at 04:39 PM, Tim Ostley wrote:
I would hesitate to put a longer antenna on the tinysa or nanovna from a mechanical point of view - it will put a lot of strain on the sma and could ultimately break the connector from the pcb.
?
Tim
M0CZP

Makes sense. I think I'll buy short and long in doubles.


Re: Antenna Replacement? #tinysa #ultra

 

See my quick NanoVNA screenshots, measured with the?tinaSA original antenna:
I must admit I am not sure what these diagrams show. I will do some studying up on VNAs.


Re: Antenna Replacement? #tinysa #ultra

 

Thanks. Aliexpress is easier for me so I'm glad they have them.

On Fri, 13 Jan 2023 at 14:05, Toni Ciscar <aciscar@...> wrote:
Not at all you are the first, the antenna is a very weak part and exposed to everything, no matter how careful you are.
The cheapest ones, you can find them on Aliexpress, for example:




Toni


Re: TinySA ULTRA LEVEL CAL -> Signal Level incorrect #ultra

 

¿ªÔÆÌåÓý

Erik-san

?

  1. The soldering on C74 appeared to be short-circuited and has been corrected.
  2. Replaced LNA on U14.
  3. Update firmware tinySA4_v1.4-40-g2f63e1c.bin
  4. Do caliblate and selftest check

CLEAR CONFIG -> CALIBLATE 100kHz to 3.54GHZ PASS

SELF TEST PASS

?

There was also a change in the value of lna in Level offset.

Before LNA Replace????????????????????? After LNA Replace

ch> correction low????????????????????? ch> correction low

index frequency value?????????????????? index frequency value

correction low 0 10000 12.2???????????? correction low 0 10000 12.2

correction low 1 50000 7.6????????????? correction low 1 50000 7.6

correction low 2 200000 4.5???????????? correction low 2 200000 4.5

correction low 3 400000 2.2???????????? correction low 3 400000 2.2

correction low 4 900000 0.4???????????? correction low 4 900000 0.4

correction low 5 20000000 -0.4????? ????correction low 5 20000000 -0.4

correction low 6 30000000 0.0?????????? correction low 6 30000000 0.0

correction low 7 100000000 -0.8???????? correction low 7 100000000 -0.8

correction low 8 160000000 -0.4???????? correction low 8 160000000 -0.4

correction low 9 230000000 0.5????????? correction low 9 230000000 0.5

correction low 10 290000000 0.3???????? correction low 10 290000000 0.3

correction low 11 400000000 1.0???????? correction low 11 400000000 1.0

correction low 12 520000000 0.1???????? correction low 12 520000000 0.1

correction low 13 600000000 0.5???????? correction low 13 600000000 0.5

correction low 14 660000000 0.4???????? correction low 14 660000000 0.4

correction low 15 740000000 1.5???????? correction low 15 740000000 1.5

correction low 16 790000000 3.0???????? correction low 16 790000000 3.0

correction low 17 810000000 4.7???????? correction low 17 810000000 4.7

correction low 18 820000000 6.3???????? correction low 18 820000000 6.3

correction low 19 830000000 8.7???????? correction low 19 830000000 8.7

?

ch> leveloffset???????????????????????? ch> leveloffset

leveloffset low 0.0???????????????????? leveloffset low -1.2

leveloffset low output 0.0??????? ??????leveloffset low output 0.0

leveloffset switch 0.0????????????????? leveloffset switch 0.0

leveloffset receive_switch 0.0????????? leveloffset receive_switch 0.1

leveloffset out_switch 0.0????????????? leveloffset out_switch 0.0

leveloffset lna 0.0?? ??????????????????leveloffset lna -0.9

leveloffset harmonic 10.5?????????????? leveloffset harmonic 10.5

leveloffset shift1 -0.1???????????????? leveloffset shift1 -0.1

leveloffset shift2 2.4????????????????? leveloffset shift2 2.4

leveloffset shift3 -0.4 ????????????????leveloffset shift3 -0.5

leveloffset drive1 0.0????????????????? leveloffset drive1 0.0

leveloffset drive2 -1.0???????????????? leveloffset drive2 -0.9

leveloffset drive3 -0.1???????????????? leveloffset drive3 -0.1

leveloffset direct 30.0? ???????????????leveloffset direct 29.4

leveloffset direct_lna 0.0????????????? leveloffset direct_lna 30.9

leveloffset ultra 0.0?????????????????? leveloffset ultra -1.6

leveloffset ultra_lna 0.0?????????????? leveloffset ultra_lna -1.0

leveloffset adf 0.0???????????????????? leveloffset adf 0.0

leveloffset direct output 0.0?????????? leveloffset direct output 0.0

?

?

The problem of passing with the old firmware and failing with the new v1.4

has been resolved with LNA replacement. I will close this issue.

?

Thanks.

?

Masahiro Kusunoki/JP3SRS

?

From: [email protected] <[email protected]> On Behalf Of Masahiro Kusunoki
Sent: Tuesday, January 10, 2023 8:06 PM
To: [email protected]
Subject: Re: [tinysa] TinySA ULTRA LEVEL CAL -> Signal Level incorrect #ultra

?

Erik-san

?

Thank you for taking a look at the caliblation results.

I will replace the parts for U14 BGA2817 as advised.

It will take some time for the parts to arrive so I will work on it next week.

?

Thanks.

Masahiro Kusunoki/JP3SRS

?

From: [email protected] <[email protected]> On Behalf Of Erik Kaashoek
Sent: Tuesday, January 10, 2023 7:42 PM
To: [email protected]
Subject: Re: [tinysa] TinySA ULTRA LEVEL CAL -> Signal Level incorrect #ultra

?

The calibration did partially complete, the LNA level calibration seems to have failed.
And selftest 13 fails, this is the LNA test.
It seems the LNA is not working correctly
The reason the older FW did not show this error is because the check of the signal level during LNA calibration was only introduced in newer FW version.
You can try yo replace the LNA, this has previously been done by someone so it seems to be possible.
The LNA is U14 and it is a?BGA2817, available from many suppliers for acceptable price.
Or you can contact the supplier for replacement.
--

For more info on the tinySA go to


Re: Antenna Replacement? #tinysa #ultra

George Dukish
 

Now you can all see why I buy 'multiples' of everything I buy! Had he bought like I do then, he would have spare parts in which to cannibalize, like we all had to in my earlier 'Air Force' days. Hell, even buying a 'cloned' unit should never be thrown away, for that particular reason of needing spare parts. GOOD DAY Erik and the designing team, for producing this beautiful piece of equipment.
On Friday, January 13, 2023, 05:08:27 AM CST, Erik Kaashoek <erik@...> wrote:


On Fri, Jan 13, 2023 at 02:58 AM, KESAHZ wrote:
Does the length, number of sections, etc matter when selecting an antenna?
You can choose any length you like.
For low frequency RFI hunting a long antenna is better
The length determines the "optimal" frequency range it will receive.
A quarter wavelength is optimal.

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

--
George Dukish


#ultra #firmware_update #ultra #firmware_update

 

Erik, I just installed the latest software update (1.4 40) and I am now getting an error message when trying to load a previous "Preset from the SD card".
It says "Format error". Am I doing something wrong? This worked perfectly with the previous version.?

Fred (KB1BU)


Re: File Notifications #file-notice

 

Thanks for those suggestions; I will implement those in my next revision.? Glad to see the empty grey buttons on those keypad entries instead of the transparent areas :-)

I got my unit a few weeks ago and haven't tried but a small fraction of the features and capabilities yet!? Heck, I just discovered yesterday a feature on my car that I've owned for almost four years now! "What is this button on the steering wheel and I wonder what it's for?" LOL!

You're doing a great job with the firmware.


Re: File Notifications #file-notice

 

David
Some suggestions for the menu chart
  • Go one level deeper on the two calibration menu entries
  • Use the data prompt text in the keypad as the large font title above the keypad. The helps to understand the logic of data entry
  • All 4 input curve menus and the output curve menus have many more sub menus. Showing these will help to understand how they work

That for the current nice documentation!

--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: File Notifications #file-notice

 

david, thank you, congrads job well done, excellent.


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

On Fri, Jan 13, 2023 at 07:34 PM, Erik Kaashoek wrote:
When you have measured and calculated your own correction tables you should keep those.
If you did not do your own tables you should use the correction tables in the new FW
OK, this sounds good. I now spent many days of work to optimize the correction table and calibrate it, because there has to be a bug in the correction function. Every time I reached the end of the correction table and wobbled the tinysa I had to see that the correction has an aberration of 5dB. It seems that there will be overwritten the done calibration points in the further calibration. As I corrected the points by console it works now. But this I have to analyze next week. At the moment I'm happy that the curve is nearly perfectly (except the hook at 2.115GHz). But now the level is +-1dB until 3.2GHz. Unfortunately the signal generator could not generate higher signals.
?
--
Klaus, DL5KV


File Notifications #file-notice

Group Notification
 

The following files and folders have been uploaded to the Files area of the [email protected] group.

By: David Massey <wd4owa@...>

Description:
TinySA Ultra Menu-Tree Chart - v1.4-40.pdf I've put the final changes in my Menu-Tree Chart draft document and officially release it to the public domain! I will also upload the Visio document that this PDF file was created from for those of you with Visio and would like to customize the document for your use. Enjoy!


The following files and folders have been uploaded to the Files area of the [email protected] group.

By: David Massey <wd4owa@...>

Description:
This is the master Visio file I will be modifying as changes happen to the menu selections with firmware updates.


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

On Fri, Jan 13, 2023 at 09:56 AM, Klaus W?rner wrote:
Does it mean, that if I use my old correction values the get wrong measurements with the new firmware?
Klaus,
? If you created a custom correction table using your own measurement equipment, then you then you will always lose the table values if you do a "CLEAR CONFIG" or update to a firmware that clears the configuration.? You either have to re-enter and save your custom values or save the custom table to a ".cmd" file and load it from the "STORAGE" menu.

?If you did not create a custom correction table, then updating to the new firmware should result in improved measurement linearity up to at least 6GHz.

Herb


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

When you have measured and calculated your own correction tables you should keep those.
If you did not do your own tables you should use the correction tables in the new FW
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

Does it mean, that if I use my old correction values the get wrong measurements with the new firmware?
--
Klaus, DL5KV


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

The calibration, or better called correction tables correct for frequency dependent deviations
These are independent of what a calibration does.
After a FW update the turns the ref level indicator red you should always do a calibration.
I will not list which of the 120 numbers in the tables changed
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

Well done Erik!!

73
Jeff G8HUL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Erik Kaashoek
Sent: 13 January 2023 17:01
To: [email protected]
Subject: [tinysa] New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

New FW release
Version V1.4.040
Changes:
- Lever will change span after doing MARKER->CENTER
- Updated input calibration tables (ULTRA only)
--

For more info on the tinySA go to


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

Erik,

Can you describe the change in the correction tables?

I don't know if it is necessary but I always un a CONFIG LEVEL CAL after upgrading firmware followed by a SELF TEST.

Mike N2MS

On 01/13/2023 12:06 PM Erik Kaashoek <erik@...> wrote:


A special thanks goes to Kurt as he did all the work for creating these updated correction tables.
Without his attention for detail the performance of the tinySA would be much worse.
--

For more info on the tinySA go to


Re: New FW release: Lever works on span after MARKER->CENTER and improved input calibration tables for Ultra

 

A special thanks goes to Kurt as he did all the work for creating these updated correction tables.
Without his attention for detail the performance of the tinySA would be much worse.
--
For more info on the tinySA go to https://tinysa.org/wiki/