CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

gage_transfer_buffer_3 Syntax C: uInt32 GAGEAPI gage_transfer_buffer_3 (int32 ta, int16 channel, void far *buffer, int32 nsamples); Visual BASIC: Function gage_transfer_buffer_3 (ByVal ta As Long, ByVal channel As Integer, buffer As Integer, ByVal nsamples As Integer) As Integer Remarks gage_transfer_buffer_3 is used to copy nsamples points from the specified channel to the supplied buffer beginning from address ta. The channel can be either GAGE_CHAN_A or GAGE_CHAN_B. The relevant addresses can be obtained by calling gage_calculate_addresses. . The buffer must have been previously typecast to the appropriate size. For 8 bit CompuScopes, the buffer should typecast for uInt8 values. For CompuScopes with more than 8 bit resolution, the buffer should typecast for int16 values. The CompuScope PCI boards will use PCI bus-mastering if available in hardware, otherwise a CPU mediated PCI data transfer method is used. PCI bus-mastering is the fastest possible PCI data transfer method. The buffer must be padded so that it is slightly longer than the memory required to store nsample samples. The required amount of padding is different for different CompuScope models. The best padding method is to use the variable user_buffer_padding, which is returned by the drivers and is the amount of extra padding in Bytes required for the current CompuScope model.. Simply add user_buffer_padding to the amount of memory to be allocated. Unlike gage_transfer_buffer, in single channel mode gage_transfer_buffer_3 automatically downloads data from both CompuScope A/D converter memories and internally interleaves them. Consequently, the user application does not need to interleave the data when the acquisition has been performed in single channel mode using gage_transfer_buffer_3. In single channel mode, gage_transfer_buffer_3 need only be called once with channel equal to GAGE_CHAN_A Return Value Returns an offset from the beginning of the dword-aligned buffer that the driver uses. Internally using PCI bus-mastering, PCI CompuScope hardware can only transfer data from a d-word (4 byte) boundary in CompuScope on-board memory. For instance, data can be downloaded starting from hexadecimal addresses 0x3000 or 3004, but not starting from hexadecimal addresses 0x3001. The returned offset gives the byte address location of the address ta, specified in the call to gage_transfer_buffer_3. For instance, if ta were equal to hex 0x3003, then the CompuScope would be forced to download data from hexadecimal addresses 0x3000. The offset would then be returned as 0x3003 – 0x3000 = 3. See also: gage_transfer_buffer and Appendix: Comparison of Various Data Transfer Routines. Examples: CompuScope API Reference Manual 53
C: offset = gage_transfer_buffer_3(current_address, GAGE_CHAN_A, (uInt8 far *)(buffer), 512); new_ptr = (uInt8 *)(buffer+offset); first_value = new_ptr[0]; Visual BASIC: gage_transfer_buffer_3 (ByVal ta As Long, ByVal channel As Integer, buffer As Integer, ByVal nsamples As Integer) CompuScope API Reference Manual 54
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: gage_transfer_buffer Syntax C: void
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

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

Delete template?

Save as template?