Re: Signal Generator Frequency Calibration
#ultra
Herb,
Thank you for the "heads-up" regarding loss of the correction factor when a firmware update is executed.
Ed, K0KC
k0kc@...
http://k0kc.us/ --
Ed, K0KC
?
k0kc@...
http://k0kc.us/
|
To save me a lot of time: I will not be able to provide any support to people that want to create a TG for the tinySA Ultra except to explain how to enable the LO output. If you do not understand how to create a good TG please do not ask how to create one. It is simply too complicated. My current priority is to support the embedded functionality of the tinySA family
If you need a VNA function, please buy a VNA. --
For more info on the tinySA go to https://tinysa.org/wiki/
|
Correct. You leakage from the sweeping LO --
For more info on the tinySA go to https://tinysa.org/wiki/
|
|
|
I noticed that when I have the original TinySA the LOW IN mode, the unit is outputting a random freq signal from the HIGH IN SMA.
I am not exactly sure what it is, I have all of the OUTPUT settings off.
Any ideas?
Any way to stop it?
Rich
|
Re: New ULTRA FW release: improved touch defaults and marker->Ref level
Hello Martin, Could you please send me a link to your latest FW for the TinySA. I must have missed your notice of the update.? Thank you,? Clyde KC7BJE?
On Wed, Dec 14, 2022 at 02:10 PM, Erik Kaashoek wrote:
New ULTRA FW release
Version V1.3563
Thx Erik,
My build of v1.3-563-g1da836e for tinySA looks also good.
Martin
|
Re: New ULTRA FW release: improved touch defaults and marker->Ref level
|
Re: New ULTRA FW release: Improved font and touch cal
Same for me, ?with new touch cal process, the result is bad and not matching to the test cal point. A touch calibration offset ?is resulting with the new cal update. Was better and of course more precise before.
Le?mer. 14 d¨¦c. 2022 ¨¤?13:21, Wander Lucio < wanderlg@...> a ¨¦crit?: Erik. I did the update and really had the problem with the touch, now we have to use the jog to access the menu and calibrate the touch. this is no problem for me, just letting you know.
?
Another thing. now that we have a big screen, the big number mode has a lot of space left over, wouldn't it be interesting for you to take advantage of this space and include the frequency as well?
|
Re: Signal Generator Frequency Calibration
#ultra
Thanks Herb Erik has kindly told me Thanks Dave?
On Wed, Dec 14, 2022 at 11:19 AM, davebb123456 wrote:
Hi I have been reading this as I have just ordered the ultra yesterday,
Can you tell me what frequency does the main clock oscillator run at,
The hardware design for the tinySA Ultra is not open source so I really can't say.? Suffice to know that the CAL output derives from the main clock source, so by monitoring it while using Eriks frequency correction procedure you are adjusting the main source.
Herb
|
Re: Signal Generator Frequency Calibration
#ultra
On Wed, Dec 14, 2022 at 11:19 AM, davebb123456 wrote:
Hi I have been reading this as I have just ordered the ultra yesterday,
Can you tell me what frequency does the main clock oscillator run at,
The hardware design for the tinySA Ultra is not open source so I really can't say.? Suffice to know that the CAL output derives from the main clock source, so by monitoring it while using Eriks frequency correction procedure you are adjusting the main source. Herb
|
Re: Signal Generator Frequency Calibration
#ultra
Ok thanks Erik I can not wait until this ultra arrives,? as my spec an in my HP test set has only got a span of 10mhz, it does go up to 1ghz,? Thanks Dave 2E0DMB
On Wed, 14 Dec 2022, 20:03 Erik Kaashoek, < erik@...> wrote: 30MHz TCXO
--
For more info on the tinySA go to
|
Re: Signal Generator Frequency Calibration
#ultra
30MHz TCXO --
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: Signal Generator Frequency Calibration
#ultra
Search for the level correction menu in the wiki --
For more info on the tinySA go to https://tinysa.org/wiki/
|
To reach the required resolution both the LO and the IF are "tuned" where the LO does the course steps.
So you never can scan a small span wit a TG using a fixed IF frequency source
I do not recommend the add a TG unless for large spans and at an offset tuning to avoid reverse leakage. Main purpose is to test frequency conversion devices as shown in the wiki
--
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: Signal Generator Frequency Calibration
#ultra
I got within 4 Hz at 100 MHz.? Now, how do I calibrate the amplitude?
Wes? N7WS
|
Re: New ULTRA FW release: Improved font and touch cal
Once I figured out how to do it, it works fine.
Wes? N7WS
toggle quoted message
Show quoted text
On Wed, Dec 14, 2022 at 04:08 AM, Erik Kaashoek wrote:
Can you test today's new FW?
Improved touch cal
--
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: Signal Generator Frequency Calibration
#ultra
Hi I have been reading this as I have just ordered the ultra yesterday, Can you tell me what frequency does the main clock oscillator run at, Thanks Dave 2E0DMB
On Wed, Dec 14, 2022 at 08:13 AM, Ed Wilson wrote:
Thanks, Erik!
I was able to get the error down to about 9 Hz.
? The frequency correction setting is lost after each firmware update.? You can save yourself some time by writing down the CONFIG->MORE->EXPERT CONFIG->FREQ CORR value that got your error down to 9Hz and re-entering it after each firmware update.?
? The long-term stability of the tinySA Ultra's main clock has been very good after frequency correction on my devices.? That clock is used for both input and output frequency accuracy, which is why a single correction routine works for both modes.
Herb
|
My understanding is that any time there is a change in impedance, there is a reflected wave.? This is the definition of Gamma, the Reflection Coefficient.? The RF power amplifier has a certain impedance and by whatever method is used to remove that RF power, it also has an associated impedance.??
At that interface, there is reflected power unless both impedances are equal.? If you choose to calculate the efficiency of the power amplifier using RF power out divided by DC power input the power reflected by the interface impedance is already in the mix.??
That power amplifier efficiency can always be increased or decreased by changing either the output impedance of the power amplifier or the input impedance to whatever is on the other side of the interface.? Once those impedances are equal, there will be no reflected power and the calculated power efficiency will be at it's highest.
Every time there is a step in impedance, there is a reflected wave.? It doesn't matter where that impedance step is located, it will have it's effect on the final power delivered to the load.
Regards,
Jim
Logic: Method used to arrive at the wrong conclusion, with confidence.? Murphy
-----Original Message-----
From: Ho-Ro <linuxaudio@...>
To: [email protected]
Sent: Wed, Dec 14, 2022 4:02 am
Subject: Re: [tinysa] #tinysa Power Reading
On Wed, Dec 14, 2022 at 10:12 AM, G8HUL wrote:
Most Pas are not 50 ohm, they are designed to give a specified power 'into* a 50 ohm load.
Jeff,
?
That's right, impedance matching is necessary for sources that can only deliver a small amount of electrical power and whose power is to be passed on as comprehensively as possible. Such weak sources are, for example, antennas. With linear sources and sinks, in the best case only half of the available power is actually radiated; the efficiency is then 50 %. The other half is lost as power dissipation in the internal resistance of the source.
Electrical energy sources, e.g. a power station, but also a large PA - whether audio or high frequency - are therefore not designed for power matching, but for voltage matching (i.e. low source resistance); their nominal power would therefore be exceeded long before any (theoretical) power matching.
?
Martin
?
|
Re: Signal Generator Frequency Calibration
#ultra
On Wed, Dec 14, 2022 at 08:13 AM, Ed Wilson wrote:
Thanks, Erik!
I was able to get the error down to about 9 Hz.
? The frequency correction setting is lost after each firmware update.? You can save yourself some time by writing down the CONFIG->MORE->EXPERT CONFIG->FREQ CORR value that got your error down to 9Hz and re-entering it after each firmware update.? ? The long-term stability of the tinySA Ultra's main clock has been very good after frequency correction on my devices.? That clock is used for both input and output frequency accuracy, which is why a single correction routine works for both modes. Herb
|
Re: Which branch to use to compile the same firmware as Erik is releasing?
Hi Alex, I will try to explain my setup.
First a bit of background:
I am a professional firmware developer for many decades. I have been using SVN (TortoiseSVN) for many years without any issues.
I am quite well versed in using SVN, but am new to Git. Just learning it now.
Wanting/Needing to use Git, I decided to try out TortoiseSVN () which being familiar with TortoiseSVN I knew would be an easy learning curve for me.
After installing TortoiseGit, It stated/complained that I still needed to install the actual Git command line tools. I downloaded and installed the "Git For Windows" () tools to get it going.
The Git for Windows tools provides a "Git BASH emulation" command line environment. My assumption was that it would also allow me to run the "make" tool which is required to build the tinySA firmware.
I had previously installed the "ARM GNU Toolchain 11.2-2022.02" on my windows computer. (See:?)
The ARM GNU Toolchain provide the GNU make tool (Built for i686-w64-mingw32), which was in my windows PATH, so when I executed: "make" in the tinySA folder (in the Git local repository on my PC), it compiled the tinySA code.
NOTE: There is a newer version of the ARM GNU Toolchain availbe, but I have not yet downloaded it.
I see there are some issues getting the same actual firmware source code as Erik is using, so I will look at Ho-Ro's instructions to see if I can resolve that issue.
My Goal at this time is to clean-up all the firmware C compilers warnings being issued during the compile process. Not to make any function changes.
Reason for this is that you can ignore them (most are not important), but one of the warnings could be significant, indicating a real firmware issue/bug.
In my previous firmware development roles, I would always examine each C compiler warning message, and attempt to adjust the source file so the warning is removed. (Or fix the problem that is actually there)
Should eventually end up with a tinySA firmware build that is completely C compiler warning free.
Then, if a new C compiler warning shows up (after new source code changes), then the new "issue/warning" can be dealt with right away.
This is a method of improving the overall quality of the firmware.
I'm hoping that when I did have source code changes made (as explained above) that Erik will be able to take them into the main Git repository.
Hopefully this explains a bit of what I have done, and what I am doing.
I am just learning Git, and how to compile the tinySA firmware, so I am NOT an expert in this area at all! (Read my notes above with that in mind)
Lane
VE7IHL?
|
Clyde Lambert
Wes Stewart