CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

system to trigger. This is useful, for instance, in some nuclear particle detection experiments, where a particle pulse can occur on any channel of a multi-channel system. Please note that, whatever causes the trigger event in a Master/Slave CompuScope system, all CompuScopes in the Master/Slave system will always be triggered together. Return Value A one is returned if execution of the routine was successful. A zero is returned when the routine fails, and gage_get_error_code may be called to obtain the error code. See also gage_capture_mode, gage_input_control and see the Appendix: Data Structures Used by Gage Drivers in the CompuScope C/C++SDK Manual. Examples: C: gage_trigger_control_2 (GAGE_CHAN_A, GAGE_EXTERNAL, GAGE_DC, GAGE_PM_1_V, GAGE_POSITIVE, GAGE_NEGATIVE, 160, 100, GAGE_POST_16K, TRUE, TRUE ); Visual BASIC: dummy = gage_trigger_control_2 (GAGE_CHAN_A, GAGE_EXTERNAL, GAGE_DC, GAGE_PM_1_V, GAGE_POSITIVE, GAGE_NEGATIVE, 160, 100, GAGE_POST_16K, TRUE, TRUE ) CompuScope API Reference Manual 57
gage_triggered Syntax C: int16 GAGEAPI gage_triggered (void); Visual BASIC: Function gage_triggered () As Integer Remarks gage_triggered determines if a trigger event has occurred on the CompuScope hardware Return Value A non-zero or true value is returned if the CompuScope hardware has been triggered, otherwise a false value is returned. See also gage_busy Examples C: triggered = gage_triggered (); Visual BASIC: triggered = gage_triggered CompuScope API Reference Manual 58
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: slope_1 and slope_2 are the trigger
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?