Using with PicoScope for Windows

To ensure that your picoScope 6000 Series PC Oscilloscope operates correctly, you must have a computer with at least the minimum system requirements to run one of the supported operating systems, as shown in the following table. The performance of the oscilloscope will be better with a more powerful PC, and will benefit from a multi-core processor.

Please note the PicoScope software is not installed as part of the SDK.

* While the driver will run on a 64 bit operating system, the driver itself is 32 bit, and therefore will run as 32 bit.

** The oscilloscope will run slowly on a USB 1.1 port. This configuration is not recommended.

Using with custom applications

Drivers are available for Windows XP (SP3 or later), Windows Vista, Windows 7 and Windows 8.

Procedure

1. Follow the instructions in the Installation Guide included with your product package.
2. Connect your oscilloscope to the PC using the USB cable supplied.

Checking the installation

Once you have installed the software and connected the oscilloscope to the PC, start the picoScope software. PicoScope should now display any signal connected to the scope inputs. If a probe is connected to your oscilloscope, you should see a small 50 or 60 hertz signal in the oscilloscope window when you touch the probe tip with your finger.

Moving your PicoScope oscilloscope to another USB port

Windows XP When you first installed the oscilloscope by plugging it into a USB port, Windows associated the pico driver with that port. If you later move the oscilloscope to a different USB port, Windows will display the New Hardware Found Wizard again. When this occurs, just click Next in the wizard to repeat the installation. If Windows gives a warning about Windows Logo Testing, clickContinue Anyway. As all the software you need is already installed on your computer, there is no need to insert the pico Software CD again.

Windows Vista/7/8 The process is automatic. When you move the device from one port to another, Windows displays an Installing device driver software message followed by a picoScope 6000 series oscilloscope message. The oscilloscope is then ready for use.

3.5.1 Block mode

In block mode, the computer prompts a picoScope 6000 series oscilloscope to collect a block of data into its internal memory. When the oscilloscope has collected the whole block, it signals that it is ready and then transfers the whole block to the computer s memory through the USB port.

1. Block size. The maximum number of values depends upon the size of the oscilloscope s memory. The memory buffer is shared between the enabled channels, so if two channels are enabled, each receives half the memory. These features are handled transparently by the driver. The block size also depends on the number of memory segments in use (seeps6000MemorySegments ).
2. Sampling rate. A picoScope 6000 Series oscilloscope can sample at a number of different rates according to the selected timebase and the combination of channels that are enabled. See the picoScope 6000 Series User s Guide for the specifications that apply to your scope model.
3. Setup time. The driver normally performs a number of setup operations, which can take up to 50 milliseconds, before collecting each block of data. If you need to collect data with the minimum time interval between blocks, use rapid block mode and avoid calling setup functions between calls to ps6000RunBlock , ps6000Stop and ps6000GetValues .

Downsampling. When the data has been collected, you can set an optional downsampling factor and examine the data. Downsampling is a process that reduces the amount of data by combining adjacent samples. It is useful for zooming in and out of the data without having to repeatedly transfer the entire contents of the scope s buffer to the PC.

Memory segmentation. The scope s internal memory can be divided into segments so that you can capture several waveforms in succession. Configure this usingps6000MemorySegments.

Data retention. The data is lost when a new run is started in the same segment, the settings are changed, or the scope is powered down.

See Using block mode for programming details.

3.5.1.1 Using block mode

This is the general procedure for reading and displaying data in block mode using a single memory segment:

1. Open the oscilloscope using ps6000OpenUnit.
2. Select channel ranges and AC/DC coupling using ps6000SetChannel.
3. Using ps6000GetTimebase , select timebases until the required nanoseconds per sample is located.
4. Use the trigger setup functions ps6000SetTriggerChannelConditions , ps6000SetTriggerChannelDirections and ps6000SetTriggerChannelProperties to set up the trigger if required.
5. Start the oscilloscope running using ps6000RunBlock.
6. Wait until the oscilloscope is ready using the ps6000BlockReady callback (or poll using ps6000IsReady ).
7. Use ps6000SetDataBuffer to tell the driver where your memory buffer is.
8. Transfer the block of data from the oscilloscope using ps6000GetValues.
9. Display the data.
10. Repeat steps 5 to 9.
11. Stop the oscilloscope using ps6000Stop .
12. Request new views of stored data using different downsampling parameters: see Retrieving stored data.

3.5.2 Rapid block mode

In normal block mode, the picoScope 6000 Series scopes collect one waveform at a time. You start the the device running, wait until all samples are collected by the device, and then download the data to the PC or start another run. There is a time overhead of tens of milliseconds associated with starting a run, causing a gap between waveforms. When you collect data from the device, there is another minimum time overhead which is most noticeable when using a small number of samples.

Rapid block mode allows you to sample several waveforms at a time with the minimum time between waveforms. It reduces the gap from milliseconds to less than 1 microsecond.

See Using rapid block mode for details.

3.5.3 ETS (Equivalent Time Sampling)

ETS is a way of increasing the effective sampling rate of the scope when capturing repetitive signals. It is a modified form of block mode, and is controlled by the ps6000SetTrigger andps6000SetEts functions.

Overview. ETS works by capturing several cycles of a repetitive waveform, then combining them to produce a composite waveform that has a higher effective sampling rate than the individual captures. The scope hardware accurately measures the delay, which is a small fraction of a single sampling interval, between each trigger event and the subsequent sample. The driver then shifts each capture slightly in time and overlays them so that the trigger points are exactly lined up. The result is a larger set of samples spaced by a small fraction of the original sampling interval. The maximum effective sampling rates that can be achieved with this method are listed in the User s Guide for the scope device.

Trigger stability. Because of the high sensitivity of ETS mode to small time differences, the trigger must be set up to provide a stable waveform that varies as little as possible from one capture to the next.

Callback. ETS mode returns data to your application using the ps6000BlockReady callback function.

Applicability Available in block mode only. Not suitable for one-shot (non-repetitive) signals. Aggregation and oversampling are not supported. Edge-triggering only. Auto trigger delay(autoTriggerMilliseconds) is ignored.

3.5.3.1 Using ETS mode

This is the general procedure for reading and displaying data in ETS mode using a single memory segment:

1. Open the oscilloscope using ps6000OpenUnit.
2. Select channel ranges and AC/DC coupling using ps6000SetChannel.
3. Using ps6000GetTimebase , select timebases until the required nanoseconds per sample is located.
4. Use the trigger setup functions ps6000SetTriggerChannelConditions , ps6000SetTriggerChannelDirections and ps6000SetTriggerChannelProperties to set up the trigger if required.
5. Start the oscilloscope running using ps6000RunBlock.
6. Wait until the oscilloscope is ready using the ps6000BlockReady callback (or poll using ps6000IsReady ).
7. Use ps6000SetDataBuffer to tell the driver where your memory buffer is.
8. Transfer the block of data from the oscilloscope using ps6000GetValues.
9. Display the data.
10. While you want to collect updated captures, repeat steps 6-9.
11. Stop the oscilloscope using ps6000Stop .
12. Repeat steps 5 to 11.

3.5.4 Streaming mode

Streaming mode can capture data without the gaps that occur between blocks when using block mode.

With USB 2.0 it can transfer data to the PC at speeds of at least 13.33 million samples per second (75 nanoseconds per sample), depending on the computer s performance. With USB 3.0 this speed increases to 78 million samples per second (12 nanoseconds per sample). This makes it suitable for high-speed data acquisition, allowing you to capture long data sets limited only by the computer s memory.

Aggregation. The driver returns aggregated readings while the device is streaming. If aggregation is set to 1 then only one buffer is returned per channel. When aggregation is set above 1 then two buffers (maximum and minimum) per channel are returned.

Memory segmentation. The memory can be divided into segments to reduce the latency of data transfers to the PC. However, this increases the risk of losing data if the PC cannot keep up with the device s sampling rate.

See Using streaming mode for programming details.

3.5.4.1 Using streaming mode

This is the general procedure for reading and displaying data in streaming mode using a single memory segment :

1. Open the oscilloscope using ps6000OpenUnit .
2. Select channels, ranges and AC/DC coupling using ps6000SetChannel .
3. Use the trigger setup functions ps6000SetTriggerChannelConditions , ps6000SetTriggerChannelDirections and ps6000SetTriggerChannelProperties to set up the trigger if required.
4. Call ps6000SetDataBuffer to tell the driver where your data buffer is.
5. Set up aggregation and start the oscilloscope running using ps6000RunStreaming .
6. Call ps6000GetStreamingLatestValues to get data.
7. Process data returned to your application s function. This example is using Auto Stop, so after the driver has received all the data points requested by the application, it stops the device streaming.
8. Call ps6000Stop, even if Auto Stop is enabled.
9. Request new views of stored data using different downsampling parameters: see Retrieving stored data .

3.5.5 Retrieving stored data

You can collect data from the picoScope 6000 driver with a different downsampling factor when ps6000RunBlock or ps6000RunStreaming has already been called and has successfully captured all the data. Use ps6000GetValuesAsync .

3.9.1 ps6000BlockReady

typedef void (CALLBACK *ps6000BlockReady)

( short handle, pico_STATUS status, void * pParameter

)

This callback function is part of your application. You register it with the picoScope 6000 series driver using ps6000RunBlock, and the driver calls it back when block-mode data is ready. You can then download the data using the ps6000GetValues function.

3.9.2 ps6000CloseUnit

pico_STATUS ps6000CloseUnit( short handle )

This function shuts down a PicoScope 6000 oscilloscope.

3.9.3 ps6000DataReady

typedef void (CALLBACK *ps6000DataReady)

( short handle, Pico_STATUS status, unsigned long noOfSamples, short overflow, void * pParameter

)

This is a callback function that you write to collect data from the driver. You supply a pointer to the function when you call ps6000GetValuesAsync , and the driver calls your function back when the data is ready.

3.9.4 ps6000EnumerateUnits

pico_STATUS ps6000EnumerateUnits

( short * count, char * serials, short * serialLth

)

This function counts the number of PicoScope 6000 units connected to the computer, and returns a list of serial numbers as a string.

3.9.5 ps6000FlashLed

Pico_STATUS ps6000FlashLed

( short handle, short start

)

This function flashes the LED on the front of the scope without blocking the calling thread. Calls to ps6000RunStreaming and ps6000RunBlock cancel any flashing started by this function. It is not possible to set the LED to be constantly illuminated, as this state is used to indicate that the scope has not been initialized.

3.9.6 ps6000GetAnalogueOffset

Pico_STATUS ps6000GetAnalogueOffset

( short handle, PS6000_RANGE, range PS6000_COUPLING coupling float * maximumVoltage, float * minimumVoltage

)

This function is used to get the maximum and minimum allowable analog offset for a specific voltage range.

3.9.7 ps6000GetMaxDownSampleRatio

Pico_STATUS ps6000GetMaxDownSampleRatio

( short handle, unsigned long noOfUnaggregatedSamples, unsigned long * maxDownSampleRatio, PS6000_RATIO_MODE downSampleRatioMode, unsigned long segmentIndex

)

This function returns the maximum downsampling ratio that can be used for a given number of samples in a given downsampling mode.

3.9.8 ps6000GetNoOfCaptures

Pico_STATUS ps6000GetNoOfCaptures

( short handle, unsigned long * nCaptures

)

This function finds out how many captures are available after ps6000RunBlock has been called when either the collection completed or the collection of waveforms was interrupted by calling ps6000Stop . The returned value (nCaptures) can then be used to iterate through the number of segments using ps6000GetValues , or in a single call tops6000GetValuesBulk where it is used to calculate the toSegmentIndex parameter.

3.9.9 ps6000GetStreamingLatestValues

Pico_STATUS ps6000GetStreamingLatestValues

( short handle, ps6000StreamingReady lpPs6000Ready, void * pParameter

)

This function instructs the driver to return the next block of values to your ps6000StreamingReady callback function. You must have previously called ps6000RunStreaming beforehand to set up streaming.

3.9.10 ps6000GetTimebase

Pico_STATUS ps6000GetTimebase

( short handle, unsigned long timebase, unsigned long noSamples, long * timeIntervalNanoseconds, short oversample, unsigned long * maxSamples unsigned long segmentIndex

)

This function calculates the sampling rate and maximum number of samples for a given timebase under the specified conditions. The result will depend on the number of channels enabled by the last call to ps6000SetChannel.

This function is provided for use with programming languages that do not support the float data type. The value returned in the timeIntervalNanoseconds argument is restricted to integers. If your programming language supports the float type, then we recommend that you use ps6000GetTimebase2 instead.

To use ps6000GetTimebase or ps6000GetTimebase2, first estimate the timebase number that you require using the information in the timebase guide. Pass this timebase to the GetTimebase function and check the returned timeIntervalNanoseconds argument. If necessary, repeat until you obtain the time interval that you need.

3.9.11 ps6000GetTimebase2

Pico_STATUS ps6000GetTimebase2

( short handle,

unsigned long timebase,

unsigned long noSamples,

float * timeIntervalNanoseconds,

short oversample,

unsigned long * maxSamples

unsigned long segmentIndex )

This function is an upgraded version of ps6000GetTimebase , and returns the time interval as a float rather than a long. This allows it to return sub-nanosecond time intervals. Seeps6000GetTimebase for a full description.

3.9.12 ps6000GetTriggerTimeOffset

pico_STATUS ps6000GetTriggerTimeOffset

( short handle unsigned long * timeUpper unsigned long * timeLower PS6000_TIME_UNITS * timeUnits unsigned long segmentIndex

)

This function gets the time, as two 4-byte values, at which the trigger occurred. Call it after block-mode data has been captured or when data has been retrieved from a previous block-mode capture. A 64-bit version of this function, ps6000GetTriggerTimeOffset64 , is also available.

3.9.13 ps6000GetTriggerTimeOffset64

Pico_STATUS ps6000GetTriggerTimeOffset64

( short handle, __int64 * time, PS6000_TIME_UNITS * timeUnits, unsigned long segmentIndex

)

This function gets the time, as a single 64-bit value, at which the trigger occurred. Call it after block-mode data has been captured or when data has been retrieved from a previous block-mode capture. A 32-bit version of this function, ps6000GetTriggerTimeOffset, is also available.

3.9.14 ps6000GetUnitInfo

Pico_STATUS ps6000GetUnitInfo

( short handle, char * string, short stringLength, short * requiredSize Pico_INFO info

)

This function retrieves information about the specified oscilloscope. If the device fails to open, only the driver version and error code are available to explain why the last open unit call failed.

3.9.15 ps6000GetValues

Pico_STATUS ps6000GetValues

( short handle, unsigned long startIndex, unsigned long * noOfSamples, unsigned long downSampleRatio, PS6000_RATIO_MODE downSampleRatioMode, unsigned long segmentIndex, short * overflow

)

This function returns block-mode data, with or without downsampling , starting at the specified sample number. It is used to get the stored data from the driver after data collection has stopped.

Applicability Block mode , rapid block mode

Arguments handle, the handle of the required device.

startIndex, a zero-based index that indicates the start point for data collection. It is measured in sample intervals from the start of the buffer.

noOfSamples, on entry, the number of samples required. On exit, the actual number retrieved. The number of samples retrieved will not be more than the number requested, and the data retrieved always starts with the first sample captured.

downSampleRatio, the downsampling factor that will be applied to the raw data.

downSampleRatioMode, which downsampling mode to use. The

available values are: PS6000_RATIO_MODE_NONE (downSampleRatio is ignored) PS6000_RATIO_MODE_AGGREGATE PS6000_RATIO_MODE_AVERAGEPS6000_RATIO_MODE_DECIMATE

AGGREGATE, AVERAGE, and DECIMATE are single-bit constants that can be ORed to apply multiple downsampling modes to the same data. DISTRIBUTION mode is not implemented.

segmentIndex, the zero-based number of the memory segment where the data is stored.

overflow, on exit, a set of flags that indicate whether an overvoltage has occurred on any of the channels. It is a bit field with bit 0 denoting Channel A.

Returns pico_OK Pico_INVALID_HANDLE Pico_NO_SAMPLES_AVAILABLE Pico_DEVICE_SAMPLING Pico_NULL_PARAMETER Pico_SEGMENT_OUT_OF_RANGE Pico_INVALID_PARAMETER Pico_TOO_MANY_SAMPLES Pico_DATA_NOT_AVAILABLE Pico_STARTINDEX_INVALID Pico_INVALID_SAMPLERATIO Pico_INVALID_CALL Pico_NOT_RESPONDING Pico_MEMORY Pico_RATIO_MODE_NOT_SUPPORTED Pico_DRIVER_FUNCTION

3.9.16 ps6000GetValuesAsync

pico_STATUS ps6000GetValuesAsync

( short handle, unsigned long startIndex, unsigned long noOfSamples, unsigned long downSampleRatio, PS6000_RATIO_MODE downSampleRatioMode,unsigned long segmentIndex, void * lpDataReady, void * pParameter

)

This function returns data either with or without downsampling , starting at the specified sample number. It is used to get the stored data from the scope after data collection has stopped. It returns the data using a callback .

3.9.17 ps6000GetValuesBulk

Pico_STATUS ps6000GetValuesBulk

( short handle, unsigned long * noOfSamples, unsigned long fromSegmentIndex, unsigned long toSegmentIndex, unsigned long downSampleRatio,PS6000_RATIO_MODE downSampleRatioMode, short * overflow

)

This function retrieves waveforms captured using rapid block mode. The waveforms must have been collected sequentially and in the same run. This method of collection does not supportdownsampling.

3.9.18 ps6000GetValuesBulkAsync

Pico_STATUS ps6000GetValuesBulkAsync

( short handle, unsigned long startIndex, unsigned long * noOfSamples, unsigned long downSampleRatio, PS6000_RATIO_MODE downSampleRatioMode, unsigned long fromSegmentIndex, unsigned long toSegmentIndex, short * overflow

)

This function retrieves more than one waveform at a time in rapid block mode after data collection has stopped. The waveforms must have been collected sequentially and in the same run. The data is returned using a callback .

3.9.19 ps6000GetValuesOverlapped

Pico_STATUS ps6000GetValuesOverlapped

( short handle, unsigned long startIndex, unsigned long * noOfSamples, unsigned long downSampleRatio, PS6000_RATIO_MODE downSampleRatioMode,unsigned long segmentIndex, short * overflow

)

This function allows you to make a deferred data-collection request, which will later be executed, and the arguments validated, when you call ps6000RunBlock in block mode. The advantage of this function is that the driver makes contact with the scope only once, when you call ps6000RunBlock , compared with the two contacts that occur when you use the conventional ps6000RunBlock ,ps6000GetValues calling sequence. This slightly reduces the dead time between successive captures in block mode.

After calling ps6000RunBlock , you can optionally use ps6000GetValues to request further copies of the data. This might be required if you wish to display the data with different data reduction settings.

3.9.20 ps6000GetValuesOverlappedBulk

Pico_STATUS ps6000GetValuesOverlappedBulk

( short handle,

unsigned long startIndex,

unsigned long * noOfSamples,

unsigned long downSampleRatio,

PS6000_RATIO_MODE downSampleRatioMode,

unsigned long fromSegmentIndex,

unsigned long toSegmentIndex,

short * overflow

)

This function allows you to make a deferred data-collection request, which will later be executed, and the arguments validated, when you call ps6000RunBlock in rapid block mode. The advantage of this method is that the driver makes contact with the scope only once, when you call ps6000RunBlock , compared with the two contacts that occur when you use the conventional ps6000RunBlock, ps6000GetValues calling sequence. This slightly reduces the dead time between successive captures in rapid block mode.

After calling ps6000RunBlock , you can optionally use ps6000GetValues to request further copies of the data. This might be required if you wish to display the data with different data reduction settings.

3.9.21 ps6000GetValuesTriggerTimeOffsetBulk

Pico_STATUS ps6000GetValuesTriggerTimeOffsetBulk

( short handle, unsigned long * timesUpper, unsigned long * timesLower, PS6000_TIME_UNITS * timeUnits, unsigned long fromSegmentIndex,unsigned long toSegmentIndex

)

This function retrieves the time offsets, as lower and upper 32-bit values, for waveforms obtained in rapid block mode .

This function is provided for use in programming environments that do not support 64-bit integers. If your programming environment supports this data type, it is easier to useps6000GetValuesTriggerTimeOffsetBulk64.

3.9.22 ps6000GetValuesTriggerTimeOffsetBulk64

Pico_STATUS ps6000GetValuesTriggerTimeOffsetBulk64

( short handle, __int64 * times, PS6000_TIME_UNITS * timeUnits, unsigned long fromSegmentIndex, unsigned long toSegmentIndex

)

This function retrieves the 64-bit time offsets for waveforms captured in rapid block mode.

A 32-bit version of this function, ps6000GetValuesTriggerTimeOffsetBulk , is available for use with programming languages that do not support 64-bit integers.

3.9.23 ps6000IsReady

Pico_STATUS ps6000IsReady

( short handle, short * ready

)

This function may be used instead of a callback function to receive data from ps6000RunBlock . To use this method, pass a NULL pointer as the lpReady argument tops6000RunBlock . You must then poll the driver to see if it has finished collecting the requested samples.

3.9.24 ps6000IsTriggerOrPulseWidthQualifierEnabled

pico_STATUS ps6000IsTriggerOrPulseWidthQualifierEnabled

(

short handle,

short * triggerEnabled,

short * pulseWidthQualifierEnabled

)

This function discovers whether a trigger, or pulse width triggering, is enabled.

3.9.25 ps6000MemorySegments

Pico_STATUS ps6000MemorySegments

( short handle unsigned long nSegments, unsigned long * nMaxSamples

)

This function sets the number of memory segments that the scope will use.

When the scope is opened, the number of segments defaults to 1, meaning that each capture fills the scope s available memory. This function allows you to divide the memory into a number of segments so that the scope can store several waveforms sequentially.

3.9.26 ps6000NoOfStreamingValues

Pico_STATUS ps6000NoOfStreamingValues

( short handle, unsigned long * noOfValues

)

This function returns the number of samples available after data collection in streaming mode. Call it after calling ps6000Stop .

3.9.27 ps6000OpenUnit

Pico_STATUS ps6000OpenUnit

( short * handle, char * serial

)

This function opens a PicoScope 6000 Series scope attached to the computer. The maximum number of units that can be opened depends on the operating system, the kernel driver and the computer.

3.9.28 ps6000OpenUnitAsync

Pico_STATUS ps6000OpenUnitAsync

( short * status char * serial

)

This function opens a scope without blocking the calling thread. You can find out when it has finished by periodically calling ps6000OpenUnitProgress until that function returns a non-zero value.

3.9.29 ps6000OpenUnitProgress

Pico_STATUS ps6000OpenUnitProgress

( short * handle, short * progressPercent, short * complete

)

This function checks on the progress of a request made to ps6000OpenUnitAsync to open a scope.

3.9.30 ps6000RunBlock

Pico_STATUS ps6000RunBlock

( short handle, unsigned long noOfPreTriggerSamples, unsigned long noOfPostTriggerSamples, unsigned long timebase, short oversample, long * timeIndisposedMs, unsigned long segmentIndex, ps6000BlockReady lpReady, void * pParameter

)

This function starts collecting data in block mode. For a step-by-step guide to this process, see Using block mode .

The number of samples is determined by noOfPreTriggerSamples and noOfPostTriggerSamples (see below for details). The total number of samples must not be more than the size of the segment referred to by segmentIndex.

* pParameter, a void pointer that is passed to the ps6000BlockReady callback function. The callback can use this pointer to return arbitrary data to the application.

Returns pico_OK Pico_INVALID_HANDLE Pico_USER_CALLBACK Pico_SEGMENT_OUT_OF_RANGE Pico_INVALID_CHANNEL Pico_INVALID_TRIGGER_CHANNEL Pico_INVALID_CONDITION_CHANNEL Pico_TOO_MANY_SAMPLES Pico_INVALID_TIMEBASE Pico_NOT_RESPONDING Pico_CONFIG_FAIL Pico_INVALID_PARAMETER Pico_NOT_RESPONDING Pico_TRIGGER_ERROR Pico_DRIVER_FUNCTION Pico_EXTERNAL_FREQUENCY_INVALIDPico_FW_FAIL Pico_NOT_ENOUGH_SEGMENTS (in Bulk mode) Pico_TRIGGER_AND_EXTERNAL_CLOCK_CLASH Pico_PWQ_AND_EXTERNAL_CLOCK_CLASHPico_PULSE_WIDTH_QUALIFIERPico_SEGMENT_OUT_OF_RANGE (in Overlapped mode) Pico_STARTINDEX_INVALID (in Overlapped mode) Pico_INVALID_SAMPLERATIO (in Overlapped mode) Pico_CONFIG_FAIL

3.9.31 ps6000RunStreaming

Pico_STATUS ps6000RunStreaming

( short handle, unsigned long * sampleInterval, PS6000_TIME_UNITS sampleIntervalTimeUnits unsigned long maxPreTriggerSamples, unsigned long maxPostTriggerSamples, short autoStop, unsigned long downSampleRatio, PS6000_RATIO_MODE downSampleRatioMode, unsigned long overviewBufferSize

)

This function tells the oscilloscope to start collecting data in streaming mode . When data has been collected from the device it is downsampled if necessary and then delivered to the application. Call ps6000GetStreamingLatestValues to retrieve the data. See Using streaming mode for a step-by-step guide to this process.

When a trigger is set, the total number of samples stored in the driver is the sum of maxPreTriggerSamples and maxPostTriggerSamples. If autoStop is false then this will become the maximum number of samples without downsampling.

Applicability Streaming mode

Arguments handle, the handle of the required device.

* sampleInterval, on entry, the requested time interval between samples; on exit, the actual time interval used.

sampleIntervalTimeUnits, the unit of time used for sampleInterval. Use one of these values:

PS6000_FS PS6000_PS PS6000_NS PS6000_US PS6000_MS PS6000_S

maxPreTriggerSamples, the maximum number of raw samples before a trigger event for each enabled channel. If no trigger condition is set this argument is ignored.

maxPostTriggerSamples, the maximum number of raw samples after a trigger event for each enabled channel. If no trigger condition is set, this argument states the maximum number of samples to be stored.

autoStop, a flag that specifies if the streaming should stop when all of maxSamples have been captured.

downSampleRatio: see ps6000GetValues downSampleRatioMode: see ps6000GetValues

3.9.32 ps6000SetChannel

Pico_STATUS ps6000SetChannel

( short handle, PS6000_CHANNEL channel, short enabled, PS6000_COUPLING type, PS6000_RANGE range, float analogueOffset,PS6000_BANDWIDTH_LIMITER bandwidth

)

This function specifies whether an input channel is to be enabled, its input coupling type, voltage range, analog offset and bandwidth limit. Some of the arguments within this function have model-specific values. Please consult the relevant section below according to the model you have.

3.9.33 ps6000SetDataBuffer

Pico_STATUS ps6000SetDataBuffer

( short handle, PS6000_CHANNEL channel, short * buffer, unsigned long bufferLth, PS6000_RATIO_MODE downSampleRatioMode

)

This function tells the driver where to store the data, either unprocessed or downsampled , that will be returned after the next call to one of the GetValues functions. The function allows you to specify only a single buffer, so for aggregation mode, which requires two buffers, you need to call ps6000SetDataBuffers instead.

You must allocate memory for the buffer before calling this function.

3.9.34 ps6000SetDataBufferBulk

Pico_STATUS ps6000SetDataBufferBulk ( short handle, PS6000_CHANNEL channel, short * buffer, unsigned long bufferLth, unsigned long waveform,PS6000_RATIO_MODE downSampleRatioMode )

This function allows you to associate a buffer with a specified waveform number and input channel in rapid block mode . The number of waveforms captured is determined by the nCapturesargument sent to ps6000SetNoOfCaptures . There is only one buffer for each waveform because the only downsampling mode that requires two buffers, aggregation mode, is not available in rapid block mode. Call one of the GetValues functions to retrieve the data after capturing.

3.9.35 ps6000SetDataBuffers

Pico_STATUS ps6000SetDataBuffers

( short handle, PS6000_CHANNEL channel, short * bufferMax, short * bufferMin, unsigned long bufferLth, PS6000_RATIO_MODE downSampleRatioMode

)

This function tells the driver the location of one or two buffers for receiving data. You need to allocate memory for the buffers before calling this function. If you do not need two buffers, because you are not using aggregate mode, then you can optionally use ps6000SetDataBuffer instead.

3.9.36 ps6000SetDataBuffersBulk

Pico_STATUS ps6000SetDataBuffersBulk ( short handle, PS6000_CHANNEL channel, short * bufferMax, short * bufferMin, unsigned long bufferLth,unsigned long waveform, PS6000_RATIO_MODE downSampleRatioMode )

This function tells the driver where to find the buffers for aggregated data for each waveform in rapid block mode . The number of waveforms captured is determined by the nCapturesargument sent to ps6000SetNoOfCaptures . Call one of the GetValues functions to retrieve the data after capture. If you do not need two buffers, because you are not using aggregatemode, then you can optionally use ps6000SetDataBufferBulk instead.

3.9.37 ps6000SetEts

Pico_STATUS ps6000SetEts

( short handle, PS6000_ETS_MODE mode, short etsCycles, short etsInterleave, long * sampleTimePicoseconds

)

This function is used to enable or disable ETS (equivalent-time sampling) and to set the ETS parameters. See ETS overview for an explanation of ETS mode.

3.9.38 ps6000SetEtsTimeBuffer

Pico_STATUS ps6000SetEtsTimeBuffer

( short handle, __int64 * buffer, unsigned long bufferLth

)

This function tells the driver where to find your application s ETS time buffers. These buffers contain the 64-bit timing information for each ETS sample after you run a block-mode ETS capture.

3.9.39 ps6000SetEtsTimeBuffers

Pico_STATUS ps6000SetEtsTimeBuffers

( short handle, unsigned long * timeUpper, unsigned long * timeLower, unsigned long bufferLth

)

This function tells the driver where to find your application s ETS time buffers. These buffers contain the timing information for each ETS sample after you run a block- mode ETS capture. There are two buffers containing the upper and lower 32-bit parts of the timing information, to allow programming languages that do not support 64-bit data to retrieve the timings.

3.9.40 ps6000SetExternalClock

Pico_STATUS ps6000SetExternalClock

( short handle, PS6000_EXTERNAL_FREQUENCY frequency, short threshold

)

This function tells the scope whether or not to use an external clock signal fed into the AUX input. The external clock can be used to synchronise one or more PicoScope 6000 units to an external source.

When the external clock input is enabled, the oscilloscope relies on the clock signal for all of its timing. The driver checks that the clock is running before starting a capture, but if the clock signal stops after the initial check, the oscilloscope will not respond to any further commands until it is powered down and back up again.

Note: if the AUX input is set as an external clock input then it cannot also be used as an external trigger input.

3.9.41 ps6000SetNoOfCaptures

Pico_STATUS ps6000SetNoOfCaptures

( short handle, unsigned long nCaptures

)

This function sets the number of captures to be collected in one run of rapid block mode . If you do not call this function before a run, the driver will capture only one waveform.

3.9.42 ps6000SetPulseWidthQualifier

Pico_STATUS ps6000SetPulseWidthQualifier

( short handle, PS6000_PWQ_CONDITIONS * conditions, short nConditions, PS6000_THRESHOLD_DIRECTION direction, unsigned long lower, unsigned long upper, PS6000_PULSE_WIDTH_TYPE type

)

This function sets up pulse-width qualification, which can be used on its own for pulse-width triggering or combined with window triggering to produce more complex triggers. The pulse-width qualifier is set by defining one or more structures that are then ORed together. Each structure is itself the AND of the states of one or more of the inputs. This AND-OR logic allows you to create any possible Boolean function of the scope s inputs.

Applicability All modes Arguments handle, the handle of the required device

* conditions, an array of PS6000_PWQ_CONDITIONS structures specifying the conditions that should be applied to each channel. In the simplest case, the array consists of a single element. When there are several elements, the overall trigger condition is the logical OR of all the elements. If conditions is NULL then the pulse-width qualifier is not used.

nConditions, the number of elements in the conditions array. If nConditions is zero then the pulse-width qualifier is not used. Range: 0 toPS6000_MAX_PULSE_WIDTH_QUALIFIER_COUNT .

direction, the direction of the signal required for the trigger to fire. See ps6000SetTriggerChannelDirections for the list of possible values. Each channel of the oscilloscope (except the AUX input) has two thresholds for each direction—for example, PS6000_RISING and PS6000_RISING_LOWER —so that one can be used for the pulse-width qualifier and the other for the level trigger. The driver will not let you use the same threshold for both triggers; so, for example, you cannot use PS6000_RISING as the direction argument for both ps6000SetTriggerConditions and ps6000SetPulseWidthQualifier at the same time. There is no such restriction when using window triggers.

lower, the lower limit of the pulse-width counter

upper, the upper limit of the pulse-width counter. This parameter is used only when the type is set to PS6000_PW_TYPE_IN_RANGE or PS6000_PW_TYPE_OUT_OF_RANGE .

3.9.43 ps6000SetSigGenArbitrary

pico_STATUS ps6000SetSigGenArbitrary

( short handle, long offsetVoltage, unsigned long pkToPk unsigned long startDeltaPhase, unsigned long stopDeltaPhase, unsigned long deltaPhaseIncrement, unsigned long dwellCount, short * arbitraryWaveform, long arbitraryWaveformSize, PS6000_SWEEP_TYPE sweepType, PS6000_EXTRA_OPERATIONS operation, PS6000_INDEX_MODE indexMode, unsigned long shots, unsigned long sweeps, PS6000_SIGGEN_TRIG_TYPE triggerType, PS6000_SIGGEN_TRIG_SOURCE triggerSource, short extInThreshold

)

This function programs the signal generator to produce an arbitrary waveform.

The arbitrary waveform generator uses direct digital synthesis (DDS). It maintains a phase accumulator of phaseAccum ulatorSize bits (see parameter table below) that indicates the present location in the waveform. The top bufferAddressWidth bits of the counter are used as an index into a buffer containing the arbitrary waveform. The remaining bits act as the fractional part of the index, enabling high-resolution control of output frequency and allowing the generation of lower frequencies.

The generator steps through the waveform by adding a deltaPhase between 1 and 2^{phaseAccumulatorSize}-1 to the phase accumulator every clock period (dacPeriod). If the deltaPhase is constant, the generator produces a waveform at a constant frequency that can be calculated as follows:

dacFrequency deltaPhase outputFrequency= ×

_{arbitraryWaveformSize 2}(phaseAccumulatorSize-bufferAddressWidth)

It is also possible to sweep the frequency by continually modifying the deltaPhase. This is done by setting up a deltaPhaseIncrement that the oscilloscope adds to the deltaPhase at specified intervals.

Applicability picoScope 6402/3/4, including B and D variants

Arguments handle, the handle of the required device

offsetVoltage, the voltage offset, in microvolts, to be applied to the waveform

pkToPk, the peak-to-peak voltage, in microvolts, of the waveform signal

startDeltaPhase, the initial value added to the phase counter as the generator begins to step through the waveform buffer

stopDeltaPhase, the final value added to the phase counter before the generator restarts or reverses the sweep

deltaPhaseIncrement, the amount added to the delta phase value every time the dwellCount period expires. This determines the amount by which the generator sweeps the output frequency in each dwell period.

dwellCount, the time, in units of dacPeriod, between successive additions of deltaPhaseIncrement to the delta phase counter. This determines the rate at which the generator sweeps the output frequency. Minimum value: PS6000_MIN_DWELL_COUNT

* arbitraryWaveform, a buffer that holds the waveform pattern as a set of samples equally spaced in time. If pkToPk is set to its maximum (4 V) and offsetVoltage is set to 0, then:

a sample of 32768 corresponds to 2 V a sample of +32767 corresponds to +2 V

arbitraryWaveformSize, the size of the arbitrary waveform buffer, in samples, from PS6000_MIN_SIG_GEN_BUFFER_SIZE to PS6000_MAX_SIG_GEN_BUFFER_SIZE.

sweepType, determines whether the startDeltaPhase is swept up to the stopDeltaPhase, or down to it, or repeatedly swept up and down. Use one of these values:

PS6000_UP PS6000_DO WN PS6000_UPDO WN PS6000_DOWNUP

operation, see ps6000SigGenBuiltIn

indexMode, specifies how the signal will be formed from the arbitrary waveform data. Single, dual and quad index modes are possible. Use one of these constants:

PS6000_SINGLE PS6000_DUAL PS6000_QUAD

shots, see ps6000SigGenBuiltIn sweeps, see ps6000SigGenBuiltIn triggerType, see ps6000SigGenBuiltIn triggerSource, see ps6000SigGenBuiltInextInThreshold, see ps6000SigGenBuiltIn

Returns pico_OK Pico_INVALID_HANDLE Pico_SIG_GEN_PARAM Pico_SHOTS_SWEEPS_WARNING Pico_NOT_RESPONDING Pico_WARNING_AUX_OUTPUT_CONFLICT Pico_WARNING_EXT_THRESHOLD_CONFLICT Pico_NO_SIGNAL_GENERATOR Pico_SIGGEN_OFFSET_VOLTAGE Pico_SIGGEN_PK_TO_PK Pico_SIGGEN_OUTPUT_OVER_VOLTAGE Pico_DRIVER_FUNCTION Pico_SIGGEN_WAVEFORM_SETUP_FAILED

Pico_AWG_NOT_SUPPORTED (e.g. if device is a 6402/3/4 A/C)

3.9.43.1 AWG index modes

The arbitrary waveform generator supports single, dual and quad index modes to help you make the best use of the waveform buffer.

Single mode. The generator outputs the raw contents of the buffer repeatedly. This mode is the only one that can generate asymmetrical waveforms. You can also use this mode forsymmetrical waveforms, but the dual and quad modes make more efficient use of the buffer memory.

Dual mode. The generator outputs the contents of the buffer from beginning to end, and then does a second pass in the reverse direction through the buffer. This allows you to specify only the first half of a waveform with twofold symmetry, such as a Gaussian function, and let the generator fill in the other half.

Quad mode. The generator outputs the contents of the buffer, then on its second pass through the buffer outputs the same data in reverse order. On the third and fourth passes it does the same but with a negative version of the data. This allows you to specify only the first quarter of a waveform with fourfold symmetry, such as a sine wave, and let the generator fill in the other three quarters.

3.9.44 ps6000SetSigGenBuiltIn

pico_STATUS ps6000SetSigGenBuiltIn

( short handle, long offsetVoltage, unsigned long pkToPk short waveType float startFrequency, float stopFrequency, float increment, float dwellTime, PS6000_SWEEP_TYPE sweepType, PS6000_EXTRA_OPERATIONS operation, unsigned long shots, unsigned long sweeps,PS6000_SIGGEN_TRIG_TYPE triggerType, PS6000_SIGGEN_TRIG_SOURCE triggerSource, short extInThreshold

)

This function sets up the signal generator to produce a signal from a list of built-in waveforms. If different start and stop frequencies are specified, the device will sweep either up, down or up and down.

3.9.45 ps6000SetSimpleTrigger

Pico_STATUS ps6000SetSimpleTrigger

( short handle, short enable, PS6000_CHANNEL source, short threshold, THRESHOLD_DIRECTION direction, unsigned long delay, short autoTrigger_ms

)

This function simplifies arming the trigger. It supports only the LEVEL trigger types and does not allow more than one channel to have a trigger applied to it. Any previous pulse width qualifier is cancelled.

3.9.46 ps6000SetTriggerChannelConditions

Pico_STATUS ps6000SetTriggerChannelConditions

( short handle, PS6000_TRIGGER_CONDITIONS * conditions, short nConditions

)

This function sets up trigger conditions on the scope s inputs. The trigger is defined by one or more PS6000_TRIGGER_CONDITIONS structures that are then ORed together. Each structure is itself the AND of the states of one or more of the inputs. This ANDOR logic allows you to create any possible Boolean function of the scope s inputs.

If complex triggering is not required, use ps6000SetSimpleTrigger .

3.9.47 ps6000SetTriggerChannelDirections

pico_STATUS ps6000SetTriggerChannelDirections

( short handle,PS6000_THRESHOLD_DIRECTION channelA,PS6000_THRESHOLD_DIRECTION channelB,PS6000_THRESHOLD_DIRECTION channelC,PS6000_THRESHOLD_DIRECTION channelD,PS6000_THRESHOLD_DIRECTION ext,PS6000_THRESHOLD_DIRECTION aux

)

This function sets the direction of the trigger for each channel.

PS6000_THRESHOLD_DIRECTION constants PS6000_ABOVE for gated triggers: above the upper threshold PS6000_ABOVE_LOWER for gated triggers: above the lower threshold PS6000_BELOW for gated triggers: below the upper threshold PS6000_BELOW_LOWER for gated triggers: below the lower threshold PS6000_RISING for threshold triggers: rising edge, using upper threshold PS6000_RISING_LOWER for threshold triggers: rising edge, using lower threshold PS6000_FALLING for threshold triggers: falling edge, using upper threshold PS6000_FALLING_LOWER for threshold triggers: falling edge, using lower threshold PS6000_RISING_OR_FALLING for threshold triggers: either edge PS6000_INSIDE for window-qualified triggers: inside window PS6000_OUTSIDE for window-qualified triggers: outside window PS6000_ENTER for window triggers: entering the window PS6000_EXIT for window triggers: leaving the window PS6000_ENTER_OR_EXIT for window triggers: either entering or leaving the windowPS6000_POSITIVE_RUNT for window-qualified triggers PS6000_NEGATIVE_RUNT for window-qualified triggers PS6000_NONE no trigger

3.9.48 ps6000SetTriggerChannelProperties

pico_STATUS ps6000SetTriggerChannelProperties

( short handle,PS6000_TRIGGER_CHANNEL_PROPERTIES * channelPropertiesshort nChannelProperties short auxOutputEnable, long autoTriggerMilliseconds

)

This function is used to enable or disable triggering and set its parameters.

3.9.49 ps6000SetTriggerDelay

pico_STATUS ps6000SetTriggerDelay

( short handle, unsigned long delay

)

This function sets the post-trigger delay, which causes capture to start a defined time after the trigger event.

3.9.50 ps6000SigGenSoftwareControl

Pico_STATUS ps6000SigGenSoftwareControl

( short handle, short state

)

This function causes a trigger event, or starts and stops gating. It is used when the signal generator is set to SIGGEN_SOFT_TRIG .

3.9.51 ps6000Stop

Pico_STATUS ps6000Stop ( short handle )

This function stops the scope device from sampling data. If this function is called before a trigger event occurs, the oscilloscope may not contain valid data.

Always call this function after the end of a capture to ensure that the scope is ready for the next capture.

3.9.52 ps6000StreamingReady

typedef void (CALLBACK *ps6000StreamingReady)

( short handle, unsigned long noOfSamples, unsigned long startIndex, short overflow, unsigned long triggerAt, short triggered, short autoStop, void * pParameter

)

This callback function is part of your application. You register it with the driver using ps6000GetStreamingLatestValues, and the driver calls it back when streaming-mode data is ready. You can then download the data using the ps6000GetValuesAsync function.

3.10.1 C

The C example program is a comprehensive console mode program that demonstrates all of the facilities of the driver.

To compile the program, create a new project for an Application containing the following files:

ps6000con.c

and:

ps6000bc.lib (Borland 32-bit applications) or

ps6000.lib (Microsoft Visual C 32-bit applications)

The following files must be in the compilation directory:

ps6000Api.h

picoStatus.h

and the following file must be in the same directory as the executable:

ps6000.dll

3.10.2 Visual Basic

The Examples/ps6000/ subdirectory of your picoScope installation contains the following files:

ps6000.vbp -project file

ps6000.bas -procedure prototypes

ps6000.frm -form and program

Note: The functions which return a TRUE/FALSE value, return 0 for FALSE and 1 for TRUE, whereas Visual Basic expects 65 535 for TRUE. Check for >0 rather than =TRUE.

3.10.3 Excel

1. Load the spreadsheet ps6000.xls
2. Select Tools | Macro
3. Select GetData
4. Select Run

Note: The Excel macro language is similar to Visual Basic. The functions which return a TRUE/FALSE value, return 0 for FALSE and 1 for TRUE, whereas Visual Basic expects 65 535 forTRUE. Check for >0 rather than =TRUE.

3.10.4 LabVIEW

The SDK contains a library of VIs that can be used to control the picoScope 6000 and some simple examples of using these VIs in streaming mode , block mode and rapid block mode.

The LabVIEW library (picoScope6000.llb) can be placed in the user.lib subdirectory to make the VIs available on the ‘User Libraries’ palette. You must also copy ps6000.dll andps6000wrap.dll to the folder containing your LabView project.

The library contains the following VIs:

picoErrorHandler.vi -takes an error cluster and, if an error has occurred, displays a message box indicating the source of the error and the status code returned by the driver

picoScope6000AdvancedTriggerSettings.vi -an interface for the advanced trigger features of the oscilloscope

This VI is not required for setting up simple triggers, which are configured using

PicoScope6000Settings.vi.

For further information on these trigger settings, see descriptions of the trigger

functions:

ps6000SetTriggerChannelConditionsps6000SetTriggerChannelDirectionsps6000SetTriggerChannelPropertiesps6000SetPulseWidthQualifierps6000SetTriggerDelay

picoScope6000AWG.vi -controls the arbitrary waveform generator

Standard waveforms or an arbitrary waveform can be selected under ‘Wave Type’. There are three settings clusters: general settings that apply to both arbitrary and standard waveforms, settings that apply only to standard waveforms and settings that apply only to arbitrary waveforms. It is not necessary to connect all of these clusters if only using arbitrary waveforms or only using standard waveforms.

When selecting an arbitrary waveform, it is necessary to specify a text file containing the waveform. This text file should have a single value on each line in the range -1 to 1. For further information on the settings, see descriptions of ps6000SetSigGenBuiltIn and ps6000SetSigGenArbitrary.

picoScope6000Close.vi -closes the oscilloscope

Should be called before exiting an application.

picoScope6000GetBlock.vi -collects a block of data from the oscilloscope

This can be called in a loop in order to continually collect blocks of data. The oscilloscope should first be set up by using PicoScope6000Settings.vi. The VI outputs data arrays in two clusters (max and min). If not using aggregation, ‘Min Buffers’ is not used.

picoScope6000GetRapidBlock.vi -collects a set of data blocks or captures from the oscilloscope in rapid block mode

This VI is similar to picoScope6000GetBlock.vi. It outputs two-dimensional arrays for each channel that contain data from all the requested number of captures.

picoScope6000GetStreamingValues.vi -used in streaming mode to get the latest values from the driver

This VI should be called in a loop after the oscilloscope has been set up using picoScope6000Settings.vi and streaming has been started by callingPicoScope6000StartStreaming.vi. The VI outputs the number of samples available and the start index of these samples in the array output by PicoScope6000StartStreaming.vi.

picoScope6000Open.vi -opens a PicoScope 6000 and returns a handle to the device

picoScope6000Settings.vi -sets up the oscilloscope

The inputs are clusters for setting up channels and simple triggers. Advanced triggers can be set up using PicoScope6000AdvancedTriggerSettings.vi.

picoScope6000StartStreaming.vi -starts the oscilloscope streaming

It outputs arrays that will contain samples once picoScope6000GetStreamingValues.vi has returned.

picoStatus.vi -checks the status value returned by calls to the driver

If the driver returns an error, the status member of the error cluster is set to ‘true’ and the error code and source are set.