¿ªÔÆÌåÓý

Date
TinySA Ultra Menu-Tree Chart pdf file in landscape mode
Hi All I have created the TinySA Ultra Menu-Tree Chart in Landscape format. David issued it in portrait format not so easy to use. Kind regards Kurt
By Kurt Poulsen · #10339 ·
Re: TinySA Ultra
I would understand that this is not possible due to copyright limitations so as not to make it easy for cloners, but a TECHNICAL DESCRIPTION with simplified block diagram, like the one for TinySA
By Toni Ciscar · #10338 ·
Re: Ultra Battery
The charging circuit of tinySA ULTRA is designed for a 3.7V battery and will stop charging when the battery is charged to 4.2V. If you plug in a 3.8V lithium battery, you can only use about 80% of the
By Hugen · #10337 ·
Re: Ultra Battery
My question would be can the charging circuit in the TinySA handle the bigger battery?
By John Cunliffe W7ZQ · #10336 ·
Re: TinySA Ultra
If you mean AD8317 Logarithmic Detector.?The tinySA ultra does not have a discrete power detector. The power detector is inside the SI4468 IC, after the selectable resolution bandwidth filter. The
By hwalker · #10335 ·
Re: TinySA Ultra
I meant inside tinis ultra.
By §³§Ó§ñ§ä§à§ã§Ý§Ñ§Ó §®§Ñ§ç§Ñ§ß§î§Ü§à§Ó · #10334 ·
Re: TinySA Ultra
Why can't I use the ad8317 logarithmic amplifier IC for calibration?
By §³§Ó§ñ§ä§à§ã§Ý§Ñ§Ó §®§Ñ§ç§Ñ§ß§î§Ü§à§Ó · #10333 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
Martin, thanks for the clarification. Erik, you specified the threshold very precisely. 6.22mVp-p (-40dBm), actually displayed as -39dBm: Single spikes are visible and indicates a red AM. 5.09mVp-p
By Ctoyan Dombarov · #10332 ·
Re: #tinysa What do you use your TinySA for what applications or purposes? #tinysa
I mostly try to use it for Phase Noise measurements of my SHF oscillators. i2NDT Claudio
By i2NDT Claudio · #10331 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
Try to keep the input signal below -40dBm This may solve the problem with the spikes -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #10330 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
The Tiny SA is only specified for frequencies >100 kHz. I notice the sweep is from 3 kHz to 103 kHz. I'm surprised you have been able to obtain a trace that looks anything as good as the ones you
By Martin · #10329 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
Hello Erik, you're absolutely right. I have periodic access to the HP3588A spectrum analyzer, on which I tested my HP3314A function generator. This 3314A served as a source in previous experiments.
By Ctoyan Dombarov · #10328 ·
Re: TinySA Ultra
pe1hwo 12:30 #10318 /g/tinysa/message/8079 prompted, just missed this topic. yes it works, thanks Erik Kaashoek. 9
By §³§Ó§ñ§ä§à§ã§Ý§Ñ§Ó §®§Ñ§ç§Ñ§ß§î§Ü§à§Ó · #10327 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
He is measuring the maxhold of a frequency sweep to try to see the flatness of the level measurement over frequency -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #10326 ·
Re: TinySA Ultra
The correction tables are generic for all same model tinySA and may improve over time. Unless you have created your own correction tables, you should never need to save/restore them over a FW update
By Erik Kaashoek · #10325 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
What are the characteristics of the input signal? -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #10324 ·
Re: TinySA Ultra
Depth error is a warning that with the currently requested output levels there is insufficient headroom to perform the requested AM modulation. The device is not faulty but you are running into a
By Erik Kaashoek · #10323 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
Hello, I don't have a clue what you try to measure or demonstrate. I can't identify any signal. Can you please tell us what signal you measure and what you expect? All the Best, Isidro Am 04.03.2023
By Isidro Berniol · #10322 ·
Re: #tinysa_TinySA2.8_Red_AM_indication
The measurements continued. 1 swiping cycle of source took 1000 seconds. Accumulated 4 cycles:
By Ctoyan Dombarov · #10321 ·
Re: TinySA Ultra
Thank you. I seem to have missed this thread. There was a question on correction. Is it worth using the previously recorded correction factors in the new firmware?
By §³§Ó§ñ§ä§à§ã§Ý§Ñ§Ó §®§Ñ§ç§Ñ§ß§î§Ü§à§Ó · #10320 ·