On Thu, Mar 30, 2023 at 07:59 AM, Erik Kaashoek wrote:

? ?Have you given thought to?/g/tinysa/message/10852 and adding DiSlord's NanoVNA modification to TinySA-App?

Thought yes, but too many projects at the moment and working on tinySA-App is not my favorite job, to say the least

:-) Maintaining code that was originally written by someone else would not be at the top of my list of things to do either.? I'm happy the shared code base for NanoVNA-App and TinySA-App allow users to take advantage of DiSlord's modifications.

Herb

I will not change the ham bands except to make then part of the config and editable using console commands.
--

开云体育

Please don’t forget to expand the HAM BANDS to include the U.S. allocations. Thanks!

On Thu, Mar 30, 2023 at 06:48 AM, hwalker wrote:

?I've been doing my frequency correction at 1GHz and entering the correction in ppb.? Does the new k and M modifiers mean the frequency offset is now entered in +/- Hz?? If so, what would be the conversion from -1200pps to Hz?

My error, the previous keypad will return

? ?Have you given thought to?/g/tinysa/message/10852 and adding DiSlord's NanoVNA modification to TinySA-App?

Thought yes, but too many projects at the moment and working on tinySA-App is not my favourite job, to say the least

?
--

开云体育

开云体育

On Thu, Mar 30, 2023 at 02:19 AM, Erik Kaashoek wrote:

New FW release
Version 1.4078

Changes

... Frequency correction keypad now includes k and M modifiers

Erik,
? ?I've been doing my frequency correction at 1GHz and entering the correction in ppb.? Does the new k and M modifiers mean the frequency offset is now entered in +/- Hz?? If so, what would be the conversion from -1200pps to Hz?

? ?Have you given thought to?/g/tinysa/message/10852 and adding DiSlord's NanoVNA modification to TinySA-App?

Herb?

New FW release
Version 1.4078

Changes
- AUTO NAME is off after a clear config
- Frequency correction keypad now includes k and M modifiers
--

On Wed, Mar 29, 2023 at 03:20 PM, Brian Donaldson wrote:

....That looks like release notes for the Ultra. I don't have an Ultra. But do appreciate the response. I will look them over anyway as I might get an Ultra later.

Here's a link by the same author for release notes for the tinySA 2.8" ...?/g/tinysa/message/10037

Herb?

Couldn’t agree more with everything hwalker just said above. thank you for taking my request of 10 grid lines to a vote and making such a fast firmware upgrade to implemented it. I’m flabbergasted with your capacity of development of this tiny apparatus we all use and love best, Diogo.

Thanks, Herb. That looks like release notes for the Ultra. I don't have an Ultra. But do appreciate the response. I will look them over anyway as I might get an Ultra later.

Just as a hint:

When it comes to measuring FM deviation with a spectrum analizer or an (already existing) SDR, then these three word should ringing a bell:

"Bessel Null Methode"

There are some nice videos on YT describing the background of it without ugly maths and showing setups. But there are two things two make sure to keep them outta the signal path
1. is the above mentioned emphasis and
2. audio processing circuits like filters, compressors or just limiters in transceivers.
The videos like will show the process using signal generators, but these aren't real radios.
Anyhow, after watching it or an other one too you should be fimiliar with it.

On Mon, Mar 27, 2023 at 03:38 PM, Bill Cromwell wrote:

Anything beyond a nonjudgmental suggestion should be left out. I am a long time Linux user and I can testify that Linux has its own pitfalls, just as the other popular operating systems.

I'll leave the 9600 baud until later!? All of the radio's that we would press into 9600 baud service either have a port wired from the factory or are easily modified based on documentation (like the Alinco DR-1200).

So far on my 1200 baud testing, Paul's (psehorne) pic for setting the AFSK level on modems to match the received spectrum on the SA Ultra has worked.? We had one sight down to fire damage (radio and PK-12 were burned badly, along with some of the coax) and needed to be back on the air as a digipeater.? We had a NIB PK-12(!), and a Yaesu FT-2800M, and all new cabling.? We set it up with the SA Ultra as per Paul's pic and the digi is back on the air.

The tinySA Ultra sure is much easier to take to a site than the big Heathkit!? No power supply required either :-)

Jim Allyn - we would pay you to check out the Heathkit if you're interested?

Hank
K4HYJ

Hi Vitaliy,

Your problem sounds somewhat similar to a problem I previously had, and below is the copy of my posting that documents my solution.
———————-
Thought I should close this post with the procedure that eventually worked great for me.? I posted this in a different post/thread but thought it might help others in the future that stumble upon this post/thread.

Sorry about the graphics not showing up in my post, and I believe you can find the graphics showing this in post #5577 by Steven Reed, and below is the process I used based on Steven Reeds graphics.

What finally worked for me is as follows.

I used device manager to see what device my TinySA was showing up as with my TinySA connected to my computers USB port and when I then selected the DFU mode on the TinySA.? In my case my device showed up under "Other devices, and under that it said STM BOOTLOADER"? Then using device manager I right clicked on "STM BOOTLOADER" and selected "Update driver", then I selected "Browse my computer for drivers", and then I gave it the following path for the search "C:\Program Files (x86)\STMicroelectronics" and told it to include subfolders for the search.? Windows then successfully found the correct deriver and then DfuSe Demo had no problem recognizing my TinySA when I put the TinySA in DFU mode and I was then able to update the firmware in my TinySA using DfuSe Demo.

The above procedure worked great, whereas everything else I tried failed.

Don (wd8dsb)
——————
Don

I'll give a go.? Thank you.

I've been reading this thread and haven't put in my two-cents yet so, for what it's worth, here's my two cents . . .

I use both a Dell laptop with Windows 10 Pro and a Dell desktop with Windows 10 Pro.? I learned a long time ago to make backup image files of my C: drive for various computer configurations so I can reload the image if something gets corrupted installing new software or experimenting with system settings or a virus infects my computer.

One of my backup images is set up for my custom software I use for my part-time work supporting a custom product for a customer.? It also happens to work with zero problems with updating my TinySA Ultra using DfuSe Demo (v3.0.6).? Then I have another backup image configured for things not work related and is used for my video editing and other "fun" things.? And that configuration will not work with DfuSe Demo no matter how hard I try.? I have no idea why the difference and I really don't worry about it since I have a backup image that works with the DfuSe Demo utility program.

I also have a backup image of just a fresh install of Windows 10 Pro in case I want to try installing new software and not have to deal with the possibilities of other software drivers or configurations causing issues with a new software install.

I use Acronis for my backup images but there are other programs out there that will allow you to make an exact backup image too and boot off a thumb drive or CD instead of your hard drive to make images or recover images.

Don't rely on the Windows recovery utility built into the OS!? You'll not get reliable results like you will with an actual recovery image of a known working system.

I have tried about everything proposed in this topic and others at the NanoVNA forum and have given up trying to use my WIN-11 tablet to update the Ultra. Lucky, I still have a WIN7 computer that I use to run some older test equipment and that one, combined with the tinySA-app works like a charm. New OS software is not always better.

John

On Tue, Mar 28, 2023 at 10:54 AM, DiSlord wrote:

right click on any of the files to save them to the PC.

I add only button, real save not work yet :(

DiSlord,
? Thanks for clarifying.? At least image files on the Sandisk card can be saved by double clicking on their name and saving them from the pop-up screen shot window.

Herb