PicoScope 7 Software
Available on Windows, Mac and Linux
Unexpected Response of Automative Commads
-
Hailey7891
- Newbie
- Posts: 0
- Joined: Wed Sep 30, 2015 1:50 am
Unexpected Response of Automative Commads
1. In some unknown cases, with command of “Measurements.CSV?” sent, “Command Prompt” can not wait the string terminator, seemed like a continuous data flow containing only white-space coming. Just like this, “A, Maximum, 0.9230, ”, only part of the string is valid, all the rest are white-space. The point is that the valid part string is just also only part of the expected measurements results. What’s wrong, is it a bug?
2. With the command “Copy.AsText”, some unexpected string of “NaN” were always found in the waveform data. What does “NaN” mean? Or is it an error or a bug and what is the solution?
[img]NaN.BMP[/img]
2. With the command “Copy.AsText”, some unexpected string of “NaN” were always found in the waveform data. What does “NaN” mean? Or is it an error or a bug and what is the solution?
[img]NaN.BMP[/img]
- Attachments
-
[The extension bmp has been deactivated and can no longer be displayed.]
Re: Unexpected Response of Automative Commads
Hello,
What version of picscope 6 are you using?
You can find the version from the Help menu - About picoscope 6
I tried out "Measurements.CSV?" command with the current stable beta builds with no issues.
NaN, standing for not a number, is a numeric data type value representing an undefined value.
I not sure why piocoscope has returned this.
Do you have the psdata files that you could post here, with issues and the commands you have used?
Have you tried using the marco recorder?
It may be easier as you see the commands generated as click on each item.
You then save and open the macro file, to see the full command options.
You should be able to use the commands.
What version of picscope 6 are you using?
You can find the version from the Help menu - About picoscope 6
I tried out "Measurements.CSV?" command with the current stable beta builds with no issues.
NaN, standing for not a number, is a numeric data type value representing an undefined value.
I not sure why piocoscope has returned this.
Do you have the psdata files that you could post here, with issues and the commands you have used?
Have you tried using the marco recorder?
It may be easier as you see the commands generated as click on each item.
You then save and open the macro file, to see the full command options.
You should be able to use the commands.
Regards Andrew
Technical Specialist
Technical Specialist
-
Hailey7891
- Newbie
- Posts: 0
- Joined: Wed Sep 30, 2015 1:50 am
Re: Unexpected Response of Automative Commads
Hi,
Testing Environment:
1. PicoScope® 6 - PC Oscilloscope software version: 6.10.18.1052
Model: PicoScope 3403D
Serial Number: CO827/041
USB Version: 2.0
Calibration Date: Thursday, August 27, 2015
Hardware Version: 1
Driver Version: 1.4.4.59
Firmware Version: 1.2.0.0 / 1.0.21.0
2. Using external Power Supply.
Issues:
1. Please refer to the file "CMD wait infinitely.psdata" for the issue about "Measurements.CSV?".
2. Please refer to the file "NaN Happened.psdata" for the issue about "NaN".
Testing Environment:
1. PicoScope® 6 - PC Oscilloscope software version: 6.10.18.1052
Model: PicoScope 3403D
Serial Number: CO827/041
USB Version: 2.0
Calibration Date: Thursday, August 27, 2015
Hardware Version: 1
Driver Version: 1.4.4.59
Firmware Version: 1.2.0.0 / 1.0.21.0
2. Using external Power Supply.
Issues:
1. Please refer to the file "CMD wait infinitely.psdata" for the issue about "Measurements.CSV?".
2. Please refer to the file "NaN Happened.psdata" for the issue about "NaN".
- Attachments
-
- NaN Happened.psdata
- NaN Happened.psdata
- (13.4 KiB) Downloaded 494 times
-
- CMD wait infinitely.psdata
- CMD wait infinitely.psdata
- (13.61 KiB) Downloaded 478 times
Re: Unexpected Response of Automative Commads
Hello,
The command of Measurements.CSV? entered in Command Prompt, and running away. This issue does not happen with the beta version.
You can download the beta from the download page. If do find this issue with the beta please post the issue here again with the psdata file.
The NaN seem to to be related to picoscope decimating the data, as these are the last 5 values.
Note the number of samples reportedly captured in 'view properties' 3994 verse the number copied to the clip board 4000.
Picoscope actual takes a few more samples, these extra values are used to draw the last part of traces on the screen, hence 4000 vs 3994.
This does seen strange that it has has values for all the other channels but not channel B.
I will create bug in our ticket system and see wait see what our development team say.
The command of Measurements.CSV? entered in Command Prompt, and running away. This issue does not happen with the beta version.
You can download the beta from the download page. If do find this issue with the beta please post the issue here again with the psdata file.
The NaN seem to to be related to picoscope decimating the data, as these are the last 5 values.
Note the number of samples reportedly captured in 'view properties' 3994 verse the number copied to the clip board 4000.
Picoscope actual takes a few more samples, these extra values are used to draw the last part of traces on the screen, hence 4000 vs 3994.
This does seen strange that it has has values for all the other channels but not channel B.
I will create bug in our ticket system and see wait see what our development team say.
Regards Andrew
Technical Specialist
Technical Specialist