Keyboard Shortcuts
Likes
Search
New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Wed, Oct 7, 2020 at 04:52 AM, Bill Cromwell wrote:
I have been reluctant to install any of the "upgrades". I can now afford to risk one of the tinySA units to try installing the "new, improved, giant economy size" software. I am not using PC software for these yet and may decide to not use it. I will not have Windows in my home - actually my computer. So updates to exe files have no appeal unless they will run under WINE. Never had any problems updating my tinySAs or my NanoVNAs.? Go ahead and do it.? My Windows policy is very similar to yours. |
¿ªÔÆÌåÓýHi Erik, I'm still trying to find clues to help in the the error due to Windows regional settings, when the decimal separator is a comma. I has been playing with OneOfEleven's NanoVNA -App v 1.0.244 and this program doesn't give any problem when writing its S1P and S2P output files. As there is not a function for choosing the decimal separator in the program, it always uses dot, but it doesn't interfere with the writing operation, so it could be a clue about the error found in tinySA-App. Let me know if you want any further tests, I'm eager to
collaborate. Kind regards, Ignacio EB4APL
El 07/10/2020 a las 1:06, EB4APL via
groups.io escribi¨®:
|
Hi,
toggle quoted message
Show quoted text
Thanks for the comments. I have lived by the idea that newer is not always *better*. Clearly there are some advantages now to installing a later version of software in the instruments. My comment about "giant economy size" is not about the size of the program but is a mockery of Madison Avenue (advertising) hype:) I will dig into information I can find on youtube, WIKI, and the io file section and then ask questions here if I have to. Thanks to Erik for pointing to the command line options. I can probably wrap those in a script but that looks like overkill for the task. I have been doing some things with Arduino systems and it is time to add some new branches. 73, Bill KU8H bark less - wag more On 10/7/20 8:18 AM, Tripp K5TRP wrote:
The firmware DFU files are not big really, about 100kb. I guess that¡¯s getting close to filling up the internal storage. On Linux there is tinySA-Saver but I¡¯ve been told it barely functions. For flashing the firmware on Linux it looks like there is some command line programs. |
For updating using linux there is a program call dfu-util
It also runs under windows, this is my commandline c:\work\DFU\dfu-util? -a 0 -s 0x08000000:leave -D c:\work\VNA\tinySA\build\tinySA.bin under linux this should be something similar remember: you can NOT brick a nanoVNA or tinySA. If the update goes wrong, worst case you have to open the housing and connect two contact while powering on and you always can try again |
The firmware DFU files are not big really, about 100kb. I guess that¡¯s getting close to filling up the internal storage. On Linux there is tinySA-Saver but I¡¯ve been told it barely functions. For flashing the firmware on Linux it looks like there is some command line programs. On Wed, Oct 7, 2020 at 6:52 AM Bill Cromwell <wrcromwell@...> wrote: Hi, --
73, Tripp Sanders K5TRP |
Hi,
toggle quoted message
Show quoted text
I have a nanoVNA H4 and now 2 of the tinySA. I have been reluctant to install any of the "upgrades". I can now afford to risk one of the tinySA units to try installing the "new, improved, giant economy size" software. I am not using PC software for these yet and may decide to not use it. I will not have Windows in my home - actually my computer. So updates to exe files have no appeal unless they will run under WINE. I will go to the files and WIKIs to get a handle on what to do. 73, Bill KU8H bark less - wag more On 10/6/20 11:42 PM, josephlevy via groups.io wrote:
Hi Erik |
¿ªÔÆÌåÓýHi Erik, I regret to say that the localization problem still exist. I'm using comma as decimal separator in the Windows regional configuration and the program throws this error: "Range check errors" when trying to leave the program (it is due to live.csv file writing attempt). The same happens when trying to save any CSV file. The problem is also in v 1.0.240.3 where is was tried to fix. I found another remaining text from the cousin program:? The Marker info shows S11 instead of tLevel when in Log Power(dBm). It is shown ok when in Lin Power (Watt). Best regards, Ignacio EB4APL
El 06/10/2020 a las 11:34, Erik
Kaashoek escribi¨®:
Release tinySA-App 1.0.240.4 |
On Tue, Oct 6, 2020 at 06:49 PM, Erik Kaashoek wrote:
It should change when you? hit enter or when you do a scan Hi Erik So for me it does not... (other things appear to work fine!) Will wait for the next versions... Thanks for all the great work on the HW and SW ( you and OneofEleven) ??????????????????????????????? Joe |
On Tue, Oct 6, 2020 at 02:34 AM, Erik Kaashoek wrote:
Changes: - Added localization changes from OneOfEleven - Updated 3 small errors reported by Herb - Added External Amp setting ====================================================== Erik, ? Looks like you can take a breather for a while.? TinySA-App now feels like a native tinySA application rather than a port from Cathy's NanoVNA-App (wish I could say the same for VNA-QT for the V2).? ? Thanks to Cathy for developing the base application and you for delivering the tinySA specific version to your users. ? Two very minor issues to address in a future release: ? 1.? Marker display mode s11 reference. ? ? ?? ? 2. As previously reported by another user, the "Save Image" automatically created file name has an s11 reference (tinysa_LOGMAG_S11_2020-10-06_08-18-09.png).? The "Save CSV" file name is fine (tinysa_2020-10-06_08-19-35.csv). ? All other tested software features continue to work as expected.? I used the "External Amp" setting this morning with an external attenuator and it also worked as expected. ? Best regards, - Herb |