CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

Multiple Record Mode Routines Name of the Routine gage_calculate_mra_addresses gage_calculate_mr_addresses gage_multiple_record gage_multiple_record_acquisitions_32 Description Corrects the trigger address based on the ETB bit information located in the data acquired from the card at the raw calculated trigger address. Returns the starting, trigger and ending addresses for the specified channel of the current board to the calling routine. Allows the application program to force the CompuScope hardware to capture only the depth specified when the trigger event occurs. The card then re-arms automatically itself to accept another trigger event and record that data immediately following the first capture. Sets the number of Multiple Record groups that will be taken by the CompuScope hardware. Miscellaneous Routines Name of the Routine gage_abort gage_abort_capture gage_board_type_size_to_text gage_busy gage_force_capture gage_get_error_code gage_need_ram gage_normalize_address gage_power_control gage_software_trigger gage_start_capture gage_triggered Description Used to regain control of the CompuScope board(s). Used to regain control of the CompuScope board(s). Returns the pointer to the string that contains the information about the installed CompuScope board. Determines if CompuScope board is busy capturing the data or not. Forces the capture of data by the CompuScope board(s). Returns the error code associated with the last call to the CompuScope driver. Allows the application program to access the CompuScope hardware’s RAM buffers. Calculates the logical address for the CompuScope hardware. Used to control the automatic power management available on the CompuScopes equipped with this feature. Will trigger the hardware when the trigger source has been set to GAGE_SOFTWARE. Prepares the CompuScope hardware for data acquisition. Determines if the CompuScope hardware has encountered a trigger event or not. CompuScope API Reference Manual 9
Recommended API Routines that Support CompuScope 85G and 85GC Gage API subroutines were created for CompuScopes that have traditional CompuScope architecture. The CompuScope 85G and 85GC has drastically different internal architecture since it was created from Tektronix chipsets with their own software protocols. Consequently, support for the CS85G and CS85GC was added by “wrapping” existing 85G chipset protocols with existing Gage API subroutine calls. Only a subset of the Recommended API subroutines is supported for the CS85G and CS85GC. None of the Legacy subroutines are supported for the CS85G and CS85GC. Please note that the CS85G and CS85GC do not support PCI bus-mastering data transfer. Consequently, the PCI bus-mastering data transfer routines, do not actually do bus-mastering for these CompuScope models. Below is a list of the recommended subroutines that are supported for the CS85G and CS85GC. gage_abort_capture gage_busy gage_calculate_addresses gage_capture_mode gage_delay_trigger_32 gage_driver_initialize gage_driver_remove gage_force_capture gage_get_driver_info gage_input_control gage_start_capture gage_transfer_buffer gage_transfer_buffer_3 gage_triggered gage_trigger_control_2 CompuScope API Reference Manual 10
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: Data Transfer Routines Name of the
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 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?