CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

Like in Single Record mode, there is a minimum post-trigger depth of each Multiple Record that can be specified for a given CompuScope model. The depth can then be increased from this minimum in specific increments. See your CompuScope hardware manual for minimum depth and depth increment values in Multiple Record Mode. The total number of Multiple Records that can be acquired is slightly less than the total acquisition memory available divided by the post trigger depth. For instance, for a CompuScope with 1 MegaSamples of onboard memory capturing 2048 point Multiple Records in single channel mode, almost 1 MegaSample / 2048 = 512 Multiple Records can be acquired (Note. 1 MegaSample = 1024 ×1024 Samples). The CompuScope cannot capture exactly 512 records, since a few points of inter-Record padding is required between sequential records. So, slightly more than 2048 points are acquired for each record and , consequently, less than 512 records can be acquired. The amount of padding is small (less than 10 points for most CompuScope models), but slightly reduces the number of records that can be captured As with Normal Single Record Acquisition, the GET DATA signal is strobed low to initiate a Multiple Record acquisition. This clears the TRIGGER and RAM FULL signals and their status bits and initializes the data acquisition counters to zero. The BUSY signal and status bit are now set to high. The data conversion process does not begin until a trigger event occurs. When a trigger event does occur, the sample depth counter begins to decrement. When this counter expires, it clears both the TRIGGER signal and its status bit, (instead of the BUSY signal as in Single record Mode). This allows another trigger event to again start the data capture process and acquired another record. A minimal number of sample clocks is required to reset the TRIGGER signal before another trigger event will be recognized. This number varies with CompuScope model number but is under 20 for all current models. The Multiple Record process continues until all of the requested records have been acquired. This event clears the BUSY signal, thus ending the Multiple Record acquisition. The following figure is a detailed timing diagram for a Multiple Record acquisition. CompuScope API Reference Manual 103
Illustration of a Multiple Record acquisition for the capture of three groups. The top illustrates a timing diagram and CompuScope memory usage is illustrated below. CompuScope API Reference Manual 104
Page 1 and 2:
Volume II: CompuScope Applications
Page 3 and 4:
Gage Applied Technologies, Inc. Sof
Page 5:
Global Table of Contents Volume I C
Page 8 and 9:
gage_normalize_address 43 gage_powe
Page 11 and 12:
III CompuScope API Routines This se
Page 13 and 14:
Recommended Routines - Quick Summar
Page 15 and 16:
Data Transfer Routines Name of the
Page 17 and 18:
Recommended API Routines that Suppo
Page 19 and 20:
gage_abort Syntax C: void GAGEAPI g
Page 21 and 22:
gage_board_abort_capture Syntax C:
Page 23 and 24:
gage_board_start_capture Syntax C:
Page 25 and 26:
gage_busy Syntax C: int16 GAGEAPI g
Page 27 and 28:
gage_calculate_mra_addresses Syntax
Page 29 and 30:
gage_calculate_mr_addresses Syntax
Page 31 and 32:
gage_capture_mode Syntax C: int16 G
Page 33 and 34:
gage_delay_trigger_32 Syntax C: uIn
Page 35 and 36:
gage_driver_initialize Syntax C: in
Page 37 and 38:
The constant GAGE_MEMORY_SIZE_TEST
Page 39 and 40:
gage_force_capture Syntax C: void G
Page 41 and 42:
gage_get_driver_info Syntax C: void
Page 43 and 44:
gage_get_error_code Syntax C: int16
Page 45 and 46:
gage_input_control Syntax C: int16
Page 47 and 48:
gage_multiple_record Syntax C: void
Page 49 and 50:
gage_need_ram Syntax C: void GAGEAP
Page 51 and 52:
gage_power_control Syntax C: int16
Page 53 and 54:
#define GAGE_B_L_STATUS_START (GAGE
Page 55 and 56:
gage_set_ext_clock_variables Syntax
Page 57 and 58:
gage_software_trigger Syntax C: voi
Page 59 and 60: gage_transfer_buffer Syntax C: void
Page 61 and 62: C: offset = gage_transfer_buffer_3(
Page 63 and 64: slope_1 and slope_2 are the trigger
Page 65 and 66: gage_triggered Syntax C: int16 GAGE
Page 67 and 68: gage_acquire_average Syntax C: int3
Page 69 and 70: GAGE_AA_INVALID_SAMPLE_NUM GAGE_AA_
Page 71 and 72: gage_get_boards_found Syntax C: int
Page 73 and 74: gage_get_records Syntax C: int16 GA
Page 75 and 76: gage_get_trigger_address Syntax C:
Page 77 and 78: gage_gpib_command Syntax C: int32 G
Page 79 and 80: gage_mem_read_chan_a Syntax C: int1
Page 81 and 82: gage_mem_read_dual Syntax C: int16
Page 83 and 84: gage_multiple_record_acquisitions S
Page 85 and 86: gage_read_cal_table Syntax C: int16
Page 87 and 88: gage_set_delay_trigger Syntax C: uI
Page 89 and 90: gage_set_trigger_depth Syntax C: in
Page 91 and 92: gage_support_to_text Syntax C: LPST
Page 93 and 94: gage_trigger_address Syntax C: int3
Page 95 and 96: Return Value A one is returned if s
Page 97 and 98: gage_trigger_view_transfer_2 Syntax
Page 99 and 100: gage_use_cal_table Syntax C: int16
Page 101 and 102: Appendix A Comparison of Various Da
Page 103 and 104: the data whose address was specifie
Page 105 and 106: gage_trigger_view_transfer, gage_tr
Page 107 and 108: Appendix C Multiple/Independent Mod
Page 109: Appendix D Multiple Record Mode Ope
Page 113 and 114: as long the group number is less th
Page 115 and 116: Technical Support Gage Applied Tech
show all

CompuScope SDK Manua.. - Egmont Instruments

Create successful ePaper yourself

Delete template?

Save as template?