Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Tinysa
- Messages
Search
Re: TinySA Ultra vs. SDRplay
On Wed, Apr 12, 2023 at 12:25 PM, <hans13@...> wrote:
I own the TinySA Ultra but have recently come across what may be an alternative.Completely different things.? SDRplay sells SDR receivers that work from VLF to 2 GHz.? You can use them as a spectrum analyzer (SA) using their program SDRuno or with a 3rd party SA application but the features are very limited.? There is no signal generator capability in SDRplay products. Roger |
Re: Setting the Date/time on a New Tiny SA Ultra
¿ªÔÆÌåÓýI¡¯ll be DARN.?? ? ? ? ? ? ? ? ? ? ? EUREKA it works!!! Thanks for all your help. And thanks for the quick response. Mark On Apr 12, 2023, at 12:06 PM, Paul via groups.io <w8aef@...> wrote:
|
Re: #tinysa selftest
#tinysa
I have been upgrading the firmwares on the NanoVNA, NanoVnaH4, the tinySA, and the tinysa ultra since they first came out and have never had any troubles using Windows 7. I don't have to rename files or any of the convoluted stuff you talked about in the iOS system. The only problem I have had is with a new HP laptop that has Windows 11 and only three USB 3.0 ports which makes the uploading of the firmware very slow. The dfu demo program makes it as easy as turning on your machine.
|
Re: Noise Figure measurement procedures for the tinySA ULTRA
#ultra
On Wed, Apr 12, 2023 at 07:49 AM, Erik Kaashoek wrote:
We learn the most from what we can not explainSure? !! Jos |
Re: Setting the Date/time on a New Tiny SA Ultra
Paul
¿ªÔÆÌåÓýI did the same thing with the same results.? RTFM !? (Instructions in this case) ? de Paul, W8AEF ? From: [email protected] [mailto:[email protected]]
On Behalf Of DiSlord
Sent: Wednesday, April 12, 2023 9:01 AM To: [email protected] Subject: Re: [tinysa] Setting the Date/time on a New Tiny SA Ultra ? On input date screen at left you can see |
Re: Setting the Date/time on a New Tiny SA Ultra
¿ªÔÆÌåÓýHi Eric,I set the date by entering 2023 04 11 ?No luck then I tried 04 11 2023 No luck again Then I tried 11 04 2023 zip, nadda, nothing. Always goes back to the original date.? Mark On Apr 12, 2023, at 1:38 AM, Erik Kaashoek <erik@...> wrote:
|
Re: Level Discrepancy Between 2 TinySA Ultras
On Wed, Apr 12, 2023 at 07:26 AM, Ed Wilson wrote:
Am I correct in assuming that I need to increase the "generic" value in dB if I want the display value to increase at a particular frequency?Ed, ? I'm sure Erik or Kurt will correct me if I'm wrong, but from the way the table values trend upwards at the high end of the frequency range, it looks like the "generic" values in dB are added to the raw measured values to correct for loss.? So, if the displayed value is low, then as you said, you would need to increase the generic value in dB by the amount of the displayed value error. Herb |
Re: Noise Figure measurement procedures for the tinySA ULTRA
#ultra
We learn the most from what we can not explain
-- For more info on the tinySA go to https://tinysa.org/wiki/ |
Re: Level Discrepancy Between 2 TinySA Ultras
Thanks, Herb!
I will wait to see of anyone with experience chimes in before I attempt any edits. Am I correct in assuming that I need to increase the "generic" value in dB if I want the display value to increase at a particular frequency? -- Ed, K0KC
?
k0kc@...
http://k0kc.us/
|
Re: Noise Figure measurement procedures for the tinySA ULTRA
#ultra
On Mon, Apr 10, 2023 at 07:43 AM, Erik Kaashoek wrote:
Yes, any oscillation could cause weird results.Eric, I finally found the cause of the problem : The LNA was not oscillating but despite the 20dB attenuator it was still overloaded ! So I addad an extra 6dB attenuator and now I measure the amplifier to have 27.99 dB's of amplification . Performing th NF procedure @ 100MHz, the result now is 0dB +/- 0.1 So sorry that I bothered you with this ! Jos |
Re: Level Discrepancy Between 2 TinySA Ultras
On Wed, Apr 12, 2023 at 03:48 AM, Ed Wilson wrote:
I do not recall seeing information on editing the correction tables in the Wiki...can you point me to some documentation on the procedure?Ed, ? If you type the command "correction" with the Ultra connected via a serial terminal (tinySA-App, PuTTY, etc) you will get the following response: correction
usage: correction low|lna|ultra|ultra_lna|direct|direct_lna|out|out_direct|out_adf|out_ultra|off|on 0-19 frequency(Hz) value(dB)
Those are all the correction tables used by the Ultra and which are editable by the user.? The tables are for both input (specan) and output (sigen).? Erik and Kurt Poulsen developed each of the tables and are the "goto" experts on making changes to a particular table.? I don't recall either of them creating a document or video describing the process of editing a table but several users have reported doing so with success. Your discrepancy appears to be in the Ultra range (>800MHz) so that is the table you will probably need to edit.? If you type "correction ultra" you will get the following response, which are the generic correction table values for the ultra mode: correction ultra
index frequency value
correction ultra 0 30000000 0.0
correction ultra 1 700000000 0.6
correction ultra 2 980000000 1.7
correction ultra 3 1440000000 4.5
correction ultra 4 1590000000 4.5
correction ultra 5 1900000000 3.2
correction ultra 6 2810000000 4.6
correction ultra 7 3340000000 6.3
correction ultra 8 3390000000 5.7
correction ultra 9 3930000000 7.0
correction ultra 10 4230000000 8.8
correction ultra 11 4300000000 7.0
correction ultra 12 4340000000 8.3
correction ultra 13 4810000000 11.4
correction ultra 14 5070000000 11.6
correction ultra 15 5110000000 13.3
correction ultra 16 5300000000 12.4
correction ultra 17 5510000000 12.6
correction ultra 18 5850000000 15.8
correction ultra 19 6000000000 15.9
I believe the format for editing a table entry is: correction ultra index(0-19) frequency(Hz) value(dB) I also believe you have to send a "saveconfig" command after the completion of all entries to make the changes "stick".? If I recall correctly, the entry with value 0(30000000Hz) should not be edited. Rather than using a serial terminal to make changes to the tables another method is to use the Ultra itself.? Select Config>More>Level Correction and the following screen will appear allowing the user to select a table for editing: Perhaps one of the users who has actually edited one of the Ultra's tables can start a separate topic and document their procedure for you. Herb |
Re: Behavior of SPEEDUP feature
#bug_report
Thanks Erik for your response. No need to spend time on this. Just wondered if the behavior is known or not. I also thought that the arithmetic (unsigned char) overflow is worth mentioning...
|
to navigate to use esc to dismiss