Once I figured out how to do it, it works fine.

Wes? N7WS

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

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?

Thanks, Erik!

I was able to get the error down to about 9 Hz.
--

On Wed, Dec 14, 2022 at 07:07 AM, Erik Kaashoek wrote:

It will correct both input full range and output below 800Mhz and "highest accuracy mode" above 800Mhz in the same way.
Cleanest signal mode above 800MHz is less frequency resolution.

? ?The tinySA Ultra has a minimum output frequency step-size of 44Hz as stated in the Wiki.? ?So, if for example, after frequency correction you are still 20Hz off you will not be able to get any closer because of the minimum output frequency step size. Above 800MHz, the minimum output frequency step-size is?much larger than 44Hz and the frequency correction does not apply to the "cleanest signal" RF output mode.

? The minimum output frequency step size is tied to the?ADF4350 and SI4468 chips used to generate the RF output.? Some frequency accuracy trade-off was necessary to meet the sub $150.00 USD price target.? I hope I got all the above correct.

Herb

It will correct both input full range and output below 800Mhz and "highest accuracy mode" above 800Mhz in the same way.
Cleanest signal mode above 800MHz is less frequency resolution.
I need to update the wiki on this....
--

I would like to calibrate the output frequency for my new TinySA Ultra when in Signal Generator Mode. I am using an amateur radio Flex-6700 for a receiver which is disciplined to a GPSDO. The Flex-6700 has a panadapter which shows the output of the TinySA Ultra to be approximately 100 Hz high at a frequency of 145.0 MHz. I "think" that I see how to make frequency corrections in the Spectrum Analyzer Mode of the TinySA Ultra using the Expert menu, but I am not sure about making frequency corrections in the Signal Generator Mode.

Any advice would be appreciated!
--

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

All very well. I liked the new text font, it greatly improved the visualization of the number in Big Number mode.
do you consider putting the marker frequency display in big number mode?

A tracking Generator is possible to be build but not for low span and resolution. Whenever I go below 1Mhz span I see chopping of the trace even if the external source and the IF are within a few khz. I don't see this with the original. I have not had time to look at the LO output to see if it is a steady swept signal or if it is chopped /? stepped.?

John

New ULTRA FW release
Version V1.3563
Changes:
- Improve touch defaults so touch calibration is not needed after FW update
- Marker ->Ref level now sets ref level to exact level of marker

WARNING: this FW update will reset your presets and config.

--

Version 559 on my TinySA is OK. I had to do a new TOUCH calibration and also a LEVEL calibration. Everything seems to be working as it should.

I have a small request, would it be possible when adjusting the brightness of the display to have some value displayed on the display so that the brightness can be adjusted repeatably?
Thanks!
Mirek

On Wed, Dec 14, 2022 at 04:08 AM, Erik Kaashoek wrote:

Can you test today's new FW?
Improved touch cal

? The improved touch calibration works as expected, however as others have pointed out, updating to the new FW loses the current screen calibration so it is necessary to use the jog switch to navigate to the "CALIBRATE" screen to restore correct touch screen operation.

? Most firmware updates do not lose touch screen calibration so using the jog switch to navigate to the "CALIBRATE" screen may be unfamiliar to some users.? It's an infrequent procedure but one that tinySA and tinySA Ultra users need to learn.

Herb?

开云体育

Can you test today's new FW?
Improved touch cal
--

Thanks Martin

I had the same issue on my tinySA with the latest FW v1.3-560-g88121a2 - my fix:

Enter the menu via jog wheel, go to CONFIG / TOUCH / TOUCH CAL and do a new touch calibration with the two snowflakes. Now the touch should work again.

Martin