开云体育

Zero span in tinySA-App has not been tested yet so I'm not surprised it fails

Hello All, Newbie alert - I only received my TinySA three days ago and still finding my way around it. I have updated the firmware and also downloaded the latest version of the TinySA App onto a PC

Also, it sounds like you're using linux or mac-os, if so then you can install that OS's version of the development software (c++ builder) and compile TinySA-App program to work directly in the OS of

If you want to give the user a settings to alter the decimal point then go for it, though it can be made so that they don't need too. If any user has any more problems with the CSV files then ask

Excellent

The program saves the CSV file according to the machines locale settings, so loading the file back into another program in the same locale should be flawless ? If you're trying to load CSV files with

Tested with this small file: # tinySA # Date: 2020-10-08 20:47:48 "430000000";"2,176104e-05" "430025000","2.008500e-05" the first line uses the European locale, the second line the USA variant If

I am neither a noob nor a luddite, nor am I a programmer, but I do really like this philosophy! Thank you! 73 -Jim NU0C "OneOfEleven" <cmoss296@...> wrote:

If excel is any good it should, no guarantee though, have to try it and see. Using double quotes around each param is quite normal in CSV files (to over come the decimal point ambiguity).

The intention is to load the .csv file into excel for further analysis Will this work with double quotes?

I've just set the CSV save function to surround each parameter (value) in the CSV file with double quotes (the CSV load function removes them) - this solves the decimal point problem.

Adding settings for the user to have to set complicates things (decimal point and field char) for them, their are often far better ways really (though not always), you can auto-detect what the file is

I sometimes cut some corners in my self inflicted urgency... While you are making changes, can I kindly ask you to make the "S11" and "S21" part of the displayed graph names coming from a #define or a

Had a quick look through your CSV code and found source code problems that will cause range check error pop ups. I'll create a new function purely for .CSV file loading/saving and fix the source

If you add a file named .gitattributes to the folder where the nanoVNA-App .git subfolder and all the working sources are located, with only one line in it with: * text=auto the line endings should

An excellent idea!? I often have to go through the calibration procedure more than once before I get it right.

Yes sure. No idea where the github line endings settings is, I just use GitHub Desktop to push any file changes.

Never had any problems updating my tinySAs or my NanoVNAs.? Go ahead and do it.? My Windows policy is very similar to yours.

jim@jimT450:~$ sudo dfu-util? -a 0 -s 0x08000000:leave -D tinySA_v1.0-52-g1167bde.bin

If OK with you I will push my branch to you so you can easily see the changes I made Would it be possible for you to enable normalization of line endings in your github repository? Windows is driving