CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

gage_trigger_control Syntax C: int16 GAGEAPI gage_trigger_control (int16 source, int16 ext_coupling, int16 ext_gain, int16 slope, int16 level, int32 depth); Visual BASIC: Function gage_trigger_control (ByVal source As Integer, ByVal ext_coupling As Integer, ByVal ext_gain As Integer, ByVal slope As Integer, ByVal level As Integer, ByVal depth As Long) As Integer Remarks gage_trigger_control is used to set up the trigger parameters of the CompuScope. source can be either channel A, EXTERNAL or SOFTWARE and the constants GAGE_CHAN_A, GAGE_EXTERNAL and GAGE_SOFTWARE should be used to indicate their respective sources. ext_coupling can be either DC or AC for the external trigger input as indicated by the constants GAGE_DC and GAGE_AC respectively. The CS512 and CS512/PCI have TTL external trigger input, therefore this parameter has no effect. ext_gain can be either of the constants GAGE_PM_5_V or GAGE_PM_1_V for the external trigger input. The CS512 and CS512/PCI have TTL external trigger input therefore this parameter has no effect. slope is the trigger slope and can be either positive or negative. The constants GAGE_POSITIVE or GAGE_NEGATIVE should be used. level can be any value between 0 and 255. The values are scaled internally to match the trigger input range selected. The minimum input level is 0 while the maximum trigger level is 255 (these correspond to -1V and +1V respectively for the x1 input gain). The CS512 and CS512/PCI have TTL external trigger input, therefore this parameter has no effect. The depth parameter sets the trigger depth, that is, the number of samples captured after the trigger event. The minimum value is 0. This can help reduce the capturing overhead when only a few points of data are required. Several defined constants are available to the application programmer to illustrate the use of this parameter. The constants GAGE_POST_0K, GAGE_POST_1K, GAGE_POST_2K, GAGE_POST_4K, GAGE_POST_8K, GAGE_POST_16K, GAGE_POST_32K, GAGE_POST_64K and GAGE_POST_128K, GAGE_POST_256K, GAGE_POST_512K, GAGE_POST_1M, GAGE_POST_2M, GAGE_POST_4M and GAGE_POST_8M are for the trigger depths of 0, 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144, 524288, 1048576, 2097152, 4194304 and 8388608 bytes respectively. Other values besides these constants can be used. The depth parameter should be a multiple of the trigger resolution. If the depth is not a multiple of the trigger resolution, it is rounded up to the nearest multiple. Note: If external trigger is not used, some parameters such as ext_gain and ext_coupling have no effect. All the parameters, however, should be set to the valid values for the CompuScope board in use. CompuScope API Reference Manual 87
Return Value A one is returned if successful and a zero is returned when the routine fails, and gage_get_error_code may be called to obtain the error code. The application program should always check the return values. See also gage_capture_mode, gage_input_control, gage_trigger_control_2 and see the Appendix: Data Structures Used by Gage Drivers in the CompuScope SDK Manual. Examples C: gage_trigger_control (GAGE_CHAN_A, GAGE_DC, GAGE_PM_1_V, GAGE_POSITIVE, 160, GAGE_POST_16K); Visual BASIC: dummy = gage_trigger_control (GAGE_CHAN_A, GAGE_DC, GAGE_PM_1_V, GAGE_POSITIVE, 160, GAGE_POST_16K) CompuScope API Reference Manual 88
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: gage_trigger_address Syntax C: int3
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?