CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

gage_trigger_view_transfer_3 Syntax C: uInt32 GAGEAPI gage_trigger_view_transfer_3 (int16 channel, void far *buffer, int32 nsamples); Visual BASIC: This routine is currently not supported under Visual BASIC. Remarks gage_trigger_view_transfer_3 is used to copy nsample points of the CompuScope memory space, from the channel specified in the parameter channel, to the supplied buffer array buffer starting with the trigger address of the most recent data capture. The CompuScope PCI boards will use bus-mastering if available; otherwise this routine is the same as gage_trigger_view_transfer. The buffer must be at least two dwords longer than the required size to store nsample samples. The calling program should typecast this buffer to the appropriate type before accessing the data. The application does not need to interleave the data when the acquisition has been performed in single channel mode, as is the case with gage_transfer_buffer, gage_trigger_view_transfer, gage_transfer_buffer_2 and gage_trigger_view_transfer_2. These routines should be used for new development when they are available. Return Value Returns an offset to the beginning of the dword-aligned buffer that the driver uses. The offset is the difference between the buffer passed to the driver and the buffer the driver uses. See also gage_trigger_view_transfer and Appendix B: Comparison of Various Data Transfer Routines. Examples C: offset = gage_trigger_view_transfer_3 (GAGE_CHAN_A, (uInt8 far *)(buffer), 512); new_ptr = (uInt8 *)(buffer+offset); first_value = new_ptr[0]; Examples C: gage_trigger_view_transfer_3 (GAGE_CHAN_A, (uInt8 far *)(buffer), 512); CompuScope API Reference Manual 91
gage_use_cal_table Syntax C: int16 gage_use_cal_table (int16 action); Visual BASIC: Function gage_use_cal_table (ByVal action As Integer) As Integer Remarks This routine sets an internal driver variable that controls whether or not a CompuScope 12 bit board will be autocalibrated when the gain is changed. If action is 1, the driver variable is set and the board will use the internal DAC table rather than autocalibrate. The new value of the driver variable is returned. If action is 0, the variable is cleared and autocalibration is performed. This is the default value. If action is not 1 or 0, the current value is returned but nothing is changed. Also note that the DAC table should be set, by reading in a calibration file containing the proper values with gage_read_cal_table. Return Value The return value is the current state of the driver variable. See also gage_read_cal_table Examples C: gage_use_cal_table (1); Visual BASIC: gage_use_cal_table (1) CompuScope API Reference Manual 92
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 and 94: gage_trigger_address Syntax C: int3
Page 95 and 96: Return Value A one is returned if s
Page 97: gage_trigger_view_transfer_2 Syntax
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?