CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

op_mode, float tbs, int32 far *trig, int32 far *start, int32 far *end, int16 data); Note that the chan parameter in this routine is 0-based. That is, channel A is specified by 0 and channel B is specified by 1. The data variable is the data located at the raw trigger address. This must have been previously downloaded as described above. The recommended way of calculating Multiple Record addresses using the embedded ETBs in order to correct the trigger address and then downloading the record data is shown below: gage_get_driver_info (&gdi); tbs = 1000000000 / sample_rate; /* tbs is time between samples in nanoseconds. The correct value must be passed to address calculation routines for correct operation */ group = 1; while (group == gage_calculate_mr_addresses (group, gdi.board_type, gdi.depth, gdi.max_available_memory, chan, gdi.mode, tbs, &trig, &start, &end) { } data = gage_mem_read_master (trig); gage_calculate_mra_addresses (gdi.board_type, gdi.board_version, chan-1, gdi.mode, tbs, &trig, &start, &end, data); size = (end - trig) +1; offset=gage_transfer_buffer_3(trig, GAGE_CHAN_A, buffer, size); display_data(offset); /*User-supplied routine that displays buffer, beginning at offset*/ group++; Due to varying amounts of inter-record padding throughout a Multiple Record Acquisition, the groups differ in size after embedded ETBs have been used to adjust the trigger addresses. An application program can check if Enhanced ETBs are available on the current CompuScope hardware by comparing the ee_options field of the gage_driver_info_type structure and comparing it against the EEPROM_OPTIONS_MULREC_ADJUST constant (defined in the EEPROM.H file). For example: gage_get_driver_info (&gdi); if (gdi.ee_options & EEPROM_OPTIONS_MULREC_ADJUST) printf ("embedded trigger bits available\n"); Notes If you are using Multiple Record, you should generally not use a busy timeout. A busy timeout is usually used to abort a capture if it is not finished within a predefined amount of time. Because a Multiple Record capture is actually a series of captures, the Multiple Record acquisition can last a long and perhaps indeterminate amount if time. Consequently, an incorrect busy timeout value may prematurely abort Multiple Record acquisition before all the captures are complete. If you must use a busy timeout, make sure that the timeout value exceeds the longest possible total Multiple Record acquisition time. CompuScope API Reference Manual 107
Technical Support Gage Applied Technologies, Inc. offers technical support for all its Software Development Kits. In order to serve you better, we have created a web-based technical support system that is available to you 24 hours a day. By utilizing the internet to the fullest, we are able to provide you better than ever technical support without increasing our costs, thereby allowing us to provide you the best possible product at the lowest possible price. To obtain technical support, simply visit: www.gage-applied.com/support.asp Please complete this form and submit it. Our form processing system will intelligently route your request to the Technical Support Specialist (TSS) most familiar with the intricacies of your product. This TSS will be in contact with you within 24 hours of form submittal. In the odd case that you have problems submitting the form on our web site, please e-mail us at support@gage-applied.com As opposed to automatic routing of technical support requests originating from the Gage web site, support requests received via e-mail or telephone calls are routed manually by our staff. Providing you with high quality support may take an average of 2 to 3 days if you do not use the web-based technical support system. Please note that Technical Support Requests received via e-mail or by telephone will take an average of 2 to 3 days to process. It is faster to use the web site! When calling for support we ask that you have the following information available: 1. Version and type of your CompuScope SDK and drivers. (The version numbers are indicated on the distribution media. Version numbers can also be obtained by looking in the appropriate README.TXT files) 2. Type, version and memory depth of your CompuScope card. 3. Type and version of your operating system. 4. Type and speed of your computer and bus. 5. Any extra hardware peripherals (i.e. CD-ROM, joystick, network card, etc.) 6. Were you able to reproduce the problem with standalone Gage Software (e.g. GageScope, GageBit, etc)?
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 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: as long the group number is less th
show all

CompuScope SDK Manua.. - Egmont Instruments

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

Delete template?

Save as template?