CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

The DelayHigh parameter is reserved for future use. Return Value Returns a 0 if the delay values are passed correctly. Returns an unsigned 32 bit integer otherwise. See also None Examples C: gage_delay_trigger_32 (GAGE_SET_DELAY_TIME, &Delay_Time, &Delay_High); Visual BASIC: gage_delay_trigger_32 (GAGE_SET_DELAY_TIME, DelayLowAddr, DelayHighAddr); CompuScope API Reference Manual 27
gage_driver_initialize Syntax C: int16 GAGEAPI gage_driver_initialize (uInt16 far *records, uInt16 memory); Visual BASIC: function gage_driver_initialize (records As Integer, ByVal memory As Integer) As Integer Remarks The gage_driver_initialize routine fully configures each CompuScope found in the system and initializes the drivers. From then on, a call to gage_select_board will be required to access any CompuScope. Below is a detailed description of the values returned by gage_driver_initialize. These values are used internally by other CompuScope API subroutines. Understanding these values is not necessary for most users who need only call gage_driver_initialize once and move on. The records parameter is a word (2 byte) array, which must be provided by the calling program. Before the gage_driver_initialize routine is called, the first half of the records variable must have been previously initialized to contain the segment / index for each CompuScope in the system. This is best done with a call to the gage_read_config_file routine. Also before the gage_driver_initialize routine is called, the second half of the records variable should contain all zeros. The array gage_board_location has been made available within the drivers to be passed as the records parameter and is GAGE_B_L_BUFFER_SIZE words long. CompuScope gage_board_location (defined in GAGE_DRV.H file) array “pseudo structure” GAGE_B_L_ELEMENT_SIZE GAGE_B_L_STATUS_SIZE array index: 0 1 2 3 ... 30 31 32 33 34 35 ... 62 63 meaning: S1 I1 S2 I2 ... S16 I16 B1 E1 B2 E2 ... B16 E16 GAGE_B_L_STATUS_START where: Sx = segment for CompuScope x, Ix = index for CompuScope x, Bx = returned board type for CompuScope x, Ex = returned status error for CompuScope x. /* CompuScope definitions for gage_board_location sizing. */ #define GAGE_B_L_MAX_CARDS 16 #define GAGE_B_L_SIZEOF_ELEMENT 2 #define GAGE_B_L_ELEMENT_SIZE 2 #define GAGE_B_L_STATUS_SIZE 2 #define GAGE_B_L_STATUS_START (GAGE_B_L_MAX_CARDS * GAGE_B_L_ELEMENT_SIZE) CompuScope API Reference Manual 28
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: gage_delay_trigger_32 Syntax C: uIn
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 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?