CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

gage_get_trigger_view_offset Syntax C: void GAGEAPI gage_get_trigger_view_offset (int32 far *offset); Visual BASIC: Sub get_trigger_view_offset (offset As Long) Remarks gage_get_trigger_view_offset can be used to get the current trigger view offset when using the routines gage_trigger_view_transfer, gage_trigger_view_transfer_2 and gage_trigger_view_transfer_3. The default value of the offset parameter is 0, which means that capture will start at the trigger address. This value can be changed to transfer pre-trigger data, for example by using the routine gage_set_trigger_view_offset. Return Value None. See also gage_set_trigger_view_offset Examples C: gage_get_trigger_view_offset ((int32 far *)offset); Note: the typecast is unnecessary if the application program is large model Visual BASIC: Call gage_get_trigger_view_offset (offset) CompuScope API Reference Manual 69
gage_gpib_command Syntax C: int32 GAGEAPI gage_gpib_command (char* strCommand, int nByteSize, char* rvBuffer, int nBufferSize); Remarks gage_gpib_command allows the application program to access functionality built into the on-board digitization module, that is not available through the standard Gage API, FOR THE COMPUSCOPE 85G OR 85GC ONLY. For instance, gage_gpib_command is used to implement TV triggering on the CS85GC. strCommand is a string, initialized by the user, that contains the command to be sent to the CS85G or 85GC digitization module. nByteSize is the length, initialized by the user, of the string that contains the command to be sent (the strCommand argument above). rvBuffer is a string that may be returned by the CS85G or 85GC digitization module, upon execution of the latest command. This string is often empty. nBufferSize is the length of the string that may be returned by the CS85G or 85GC digitization module (the rvBuffer argument above). Return Value The return value is a signed 32 bit integer. A return value of 0 indicates that the gage_gpib_command routine has been implemented properly. Any other value signifies an error while implementing the routine. Examples C: gage_gpib_command (strCmd, strlen(strCmd), strQueryInf, sizeof(strQueryInf)); CompuScope API Reference Manual 70
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: gage_get_trigger_address Syntax C:
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

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

Delete template?

Save as template?