¿ªÔÆÌåÓý

New tinySA-App.exe: only some cleaning


 

After some further cleaning (no new functionality yet) a new release of tinySA-App.exe
instead of .s1p files the saving goes to .csv files.
Let me know if I still missed (nano)VNA references

The file is no longer available in the files section of the group but only here:?


 

On Sat, Oct 3, 2020 at 03:45 AM, Erik Kaashoek wrote:
After some further cleaning (no new functionality yet) a new release of tinySA-App.exe
instead of .s1p files the saving goes to .csv files.
Let me know if I still missed (nano)VNA references

The file is no longer available in the files section of the group but only here:?
Erik,
? The code clean-up looks much, much better.? Confusing references to NanoVNA-App, other than appropriate credits to OneOfEleven (A.K.A Cathy), have been been pretty much eliminated.

? I have the following comments:

?1. The change to .csv format is working, but....? ?The actual file format appears to be space-delimited instead of comma-delimited.
? ? ? ? ? 100000? 0.209080010653? 0.000000000000
? ? ? ? ? 801202? 0.001625314821? 0.000000000000
? ? ? ? ? 1502405? 0.000216739223? 0.000000000000
? ? ? ? ? 2203607? 0.000076902012? 0.000000000000
? ? ? ? ? ......
? ? ?Looks like the actual values are frequency_Hz, level_watts and an unused column.

2. If the display format is selected as Lin Power instead of the default Log Power then the s11/s21 designations re-appear.


? I look forward to future tinySA specific functions being added to tinySA-App.? Cathy has built a good foundation and you have done a good job of tweaking the app to make it feel like a native tinySA application.?

?My first recommendation for your future tinySA-App to do list addresses the request by Charlie to send the tinySA-App sweep settings back to the tinySA:

? Maybe divide the current button with 4 right arrow heads into two buttons.? One button with 2 right arrow heads that retain the current function.? A second button with 2 left arrow heads that send the the tinySA-App sweep settings back to the tinySA.? I think the current button takes up too much real-estate for a single function anyway.


- Herb?


 

Hi Erik,

I found one of this: when saving an image the file names are "tinysa_LOGMAG_S11_2020-10-03_13-27-58.png" and "tinysa_LINMAG_S11_2020-10-03_13-33-09.png" instead of "Log Power ..." and "Lin Power ...".

Also in the Settings window still is "vswr 2 line" color setting option.

Best regards,

Ignacio EB4APL

El 03/10/2020 a las 12:45, Erik Kaashoek escribi¨®:
After some further cleaning (no new functionality yet) a new release of tinySA-App.exe
instead of .s1p files the saving goes to .csv files.
Let me know if I still missed (nano)VNA references

The file is no longer available in the files section of the group but only here:

--
El software de antivirus Avast ha analizado este correo electr¨®nico en busca de virus.


 

¿ªÔÆÌåÓý


El 03/10/2020 a las 14:48, hwalker wrote:
On Sat, Oct 3, 2020 at 03:45 AM, Erik Kaashoek wrote:
After some further cleaning (no new functionality yet) a new release of tinySA-App.exe
instead of .s1p files the saving goes to .csv files.
Let me know if I still missed (nano)VNA references

The file is no longer available in the files section of the group but only here:?
Erik,
? The code clean-up looks much, much better.? Confusing references to NanoVNA-App, other than appropriate credits to OneOfEleven (A.K.A Cathy), have been been pretty much eliminated.

? I have the following comments:

?1. The change to .csv format is working, but....? ?The actual file format appears to be space-delimited instead of comma-delimited.
? ? ? ? ? 100000? 0.209080010653? 0.000000000000
? ? ? ? ? 801202? 0.001625314821? 0.000000000000
? ? ? ? ? 1502405? 0.000216739223? 0.000000000000
? ? ? ? ? 2203607? 0.000076902012? 0.000000000000
? ? ? ? ? ......
? ? ?Looks like the actual values are frequency_Hz, level_watts and an unused column.

I favor this space as field separator instead of comma, because in many countries the comma is used as decimal separator which confuses the importer.

I would suggest for the future an option for choosing the separators, both between fields and decimals. This would make it truly universal.

Regards,

Ignacio EB4APL



Libre de virus.


 

New version uploaded.
Now the tinySA range is set identical to the tinySA-App when requesting a scan.
The points are NOT set
For the csv I added the non-standard "sep=," pragma and changed to "," as separator.
I know about the EUropean/USA "."/"," difference and the only solution is to make this configurable but did not implement.
No other changes.

B.t.w. Is there someone that wants to help with tinySA-App? It deserves some more attention than I am currently able to provide.
Or even better: with tiniSA-Saver (the python version) as this will help the Linux users


 

Nicely done, Erik. Thank you for all you do.

It would be nice if you could bring back trace smoothing. I found it to be very useful.

FWIW I was ok with space delimiting. Any modern spreadsheet can handle it. :)

73

-Jim
NU0C

On Sat, 03 Oct 2020 08:23:14 -0700
"Erik Kaashoek" <erik@...> wrote:

New version uploaded.
Now the tinySA range is set identical to the tinySA-App when requesting a scan.
The points are NOT set
For the csv I added the non-standard "sep=," pragma and changed to "," as separator.
I know about the EUropean/USA "."/"," difference and the only solution is to make this configurable but did not implement.
No other changes.

B.t.w. Is there someone that wants to help with tinySA-App? It deserves some more attention than I am currently able to provide.
Or even better: with tiniSA-Saver (the python version) as this will help the Linux users