CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

gage_init_clock Syntax C: void GAGEAPI gage_init_clock (void); Visual BASIC: Sub init_clock () Remarks gage_init_clock is used to initialize the CompuScope clock circuitry. This routine should be called before initiating data capture with gage_get_data. It is recommended that the gage_start_capture routine, which calls gage_init_clock internally, be used instead. gage_init_clock can be used, in some cases, in conjunction with gage_get_data in order to speed up the re-arming of the CompuScope hardware. Note that using this method does not allow the amount of pretrigger data to be ensured. Pre-trigger data will only be captured until an event fulfilling the trigger conditions occurs. Ensuring a specific number of pre-trigger data points can only be done by setting this number of points using the gage_delay_trigger_32 routine and then calling gage_start_capture. Using this method, gage_start_capture will ignore triggers until the specified amount of pre-trigger data has been acquired. Return Value None. See also gage_get_data and gage_start_capture Examples C: gage_init_clock (); Visual BASIC: Call gage_init_clock () CompuScope API Reference Manual 71
gage_mem_read_chan_a Syntax C: int16 GAGEAPI gage_mem_read_chan_a (int32 location); Visual BASIC: Function gage_mem_read_chan_a (ByVal location As Long) As Integer Remarks gage_mem_read_chan_a reads one sample out of the CompuScope memory for channel A in dual channel mode and returns it as an integer. It is usually used in a loop to retrieve data from a range of addresses from a CompuScope board. location is an address in the CompuScope memory and usually starts at the trigger address. It can precede and/or follow the trigger address as set by the current trigger depth. The gage_calculate_addresses routine is very useful for determining the valid addresses and should be used instead of directly invoking the gage_trigger_address routine for future compatibility with the CompuScope drivers. When using the gage_mem_read_chan_a routine, access to the CompuScope memory must be obtained by calling gage_need_ram(1) beforehand, and released by calling gage_need_ram(0) when finished. Return Value The byte (or integer) corresponding to the specified location for channel A is returned as an unsigned integer (0 - 255) for 8 bit CompuScopes, a signed 12 bit integer (-2048 - 2047) for the 12 bit CompuScopes and a signed 16 bit integer (-32768 to 32767) for the 16 bit CompuScopes. See also gage_mem_read_chan_b, gage_mem_read_dual, gage_mem_read_single, gage_need_ram, gage_calculate_addresses and Appendix: Comparison of Various Data Transfer Routines. Examples C: data = gage_mem_read_chan_a (address); Visual BASIC: data = gage_mem_read_chan_a (address) CompuScope API Reference Manual 72
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: gage_gpib_command Syntax C: int32 G
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 and 110: Appendix D Multiple Record Mode Ope
Page 111 and 112: Illustration of a Multiple Record a
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?