If you are using a operating system with a language that uses a comma “,” as a decimal point “.” (French, German, Swedish, Italian, etc.),
then you will find that then using maths channels with decimal points you will have some issues.
This is because the software uses the operating system to break the numbers but it also use comma to separate variables when using function such as the high pass filter.
Maths Channel Wizard (High Pass filter Example)
Unfortunately as this requires a major rewrite for the maths channel it may take a while before we are able to fix this issue.
While we are currently looking at this issue you can work around it by changing the decimal symbol of your language settings
Please go to Start > Control Panel > ...
Windows XP : Regional and Language Options>Customise
Windows Vista : Languages and Region > Customise this format.
Windows 7 : Region and Language > Additional settings
Windows 8 : Language> Change date, time or number formats > Additional Settings
And changing the Decimal symbol from a comma to a full stop.
Please accept my apologises for any inconvenience this may cause.
Windows Regional settings are now supported in PicoScope 6.11.10.
So for most European languages ie French, German etc
You can now use a comma symbol ',' for the decimal place and a semicolon symbol ';' for the list separator, in maths channels.
An other issue is the export of a serial decoded list into a csv-file. With a German windows-installation you get commas as separator and also a comma as "decimal point". So all my first exports are unusable, because all numbers with a comma as decimal point are separated into two rows. For example a -0.321 is stored in the csv-file as -0,321 and will be stored in a spreadsheet as RowA -0 and RowB 321.
It would be very useful if the character to separate the rows could be selected.
Just to report that in software version: 6.13.2.3439 (beta) on Croatian locale the workaround with semicolon symbol ';' for the list separator, in maths channels doesn't work. We also have comma as a decimal point.
As far as CSV delimiter, good choice is semicolon. That way both decimal point or decimal comma are supported for numbers.
I've the same issue. I'm exporting data to a .csv and the decimal char is confused as separator
I'm using Win10 and the separator in regional settings is set to ';'
In case you were wondering, the issue is not solved in the current software (6.13.15 - Just updated from 6.12.2667 because i had to throw away half an our of data because of this issue).
System Culture: Italian (comma as decimal point), Application Language English.
Csv export of protocol decoder window use comma as decimal point and comma as separator.
To find out the decimal point character is trivial, to ask the user which character to use for separation before the file is generated is even more trivial.
Also, some parts of the UI still use the system language and not the application language
In serial decoding table and export: Packet, Start Time, End Time.
Also if i use the numpad dot it's a dot and not a comma
Also if i use the dot in the trigger level it doesn't get recognized but the comma is (correct but meh). At least now the math channel Setup doesn't care if you use a dot or a comma and produce the expected output, which is nice.
This had been fixed in recent versions, but due to an unrelated change with csv exports it has resurfaced in the current release. The development team have made the necessary changes which will be rolled out in a new release once testing has been completed.
Hi Support-Team,
I just have the same problem that the decimal places and the seperator are commas in the csv export. Are there any news when the problem will be fixed?
in january it was said that the problem should be solved with the next rollout?
The development team have made the necessary changes which will be rolled out in a new release once testing has been completed.
