CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

actually passes through zero and the CompuScope is never triggered. To resolve this problem, simply raise the trigger level to one that corresponds to 1 Volt or so. Using the wrong external trigger input range can also cause this problem. Q: The program runs, but why is the data capture incorrect? A: The order in which CompuScope parameter setup routines are called for data capture is important. gage_trigger_control should be called after gage_input_control, which should be called after gage_capture_mode. It is recommended that the programmer use the SetBoard() routine to implement CompuScope settings, since this routine calls all setup routines in the correct order. The SetBoard () routine resides in app_supp.c , which is included with every C sample program. Q: Why is Multiple Record mode behaving erratically in my program? A: The order in which the driver routines are called is important. gage_multiple_record should be called before gage_capture_mode, gage_input_control or gage_trigger_control. Also, if you change the Multiple Record settings, gage_trigger_control must be called again. . It is recommended that the programmer use the SetBoard() routine to implement CompuScope settings, since this routine calls all setup routines in the correct order. The SetBoard () routine resides in app_supp.c , which is included with every C sample program. Q: Why I am not able to properly capture the data with an external clock? A: There can be several reasons for this. The nature of the required external clock signal is different for each CompuScope model. The voltage levels, signal shape, duty cycle and allowed frequency range must also be respected. Please see your hardware manual for these details. Many CompuScopes terminate the external clock input with a 50 Ohm load for good signal propagation. The users signal must then be capable of driving a 50 Ohm load. Finally, the external clock function is optional on some models, so make sure that your CompuScope is actually equipped with the external clock option. Most CompuScopes have a minimum operating frequency. Consequently, the clock signal cannot be turned off while the CompuScope is operating. It is best to have a free-running clock source that is always active. Another important point is to correctly set the external clock frequency in your application program. The drivers have no other means of knowing this frequency. The drivers need to know the external clock frequency in order to internally set low level timing delays on the CompuScope. If you tell the drivers the incorrect external clock frequency, this may lead to incorrect CompuScope operation. CompuScope API Reference Manual 99
Appendix C Multiple/Independent Mode Operation In cases where there is more than one CompuScope board installed in one host computer. This is called a Multi-card CompuScope system. There are two types of Multi-card CompuScope systems: a Master/Slave CompuScope system and a Multiple/Independent CompuScope system. A Master/Slave CompuScope system consists of identical CompuScopes working in a synchronous manner for true simultaneous sampling and triggering on all channels in the system. The Master/Slave configuration must be specified at the time of order. The CompuScopes are then prepared as a Master/Slave system at the factory. The CompuScopes can no longer then be operated as independent CompuScopes unless they are reconfigured at the factory. All CompuScopes in the system, Master and Slaves, share start and trigger signals, as well as the sampling clock. The Master CompuScope provides all these timing signals to the Slaves. All capture parameters, such as the post-trigger depth and sampling rate, are set to the same value for all CompuScopes in the system. Only the CompuScope channel parameters (i.e. input range, coupling and impedance) can be set independently for each CompuScope. ] A Multiple/Independent CompuScope system consists of different single CompuScopes that can be operated independently, with completely different sampling rates and trigger conditions. This system allows, for example, capturing a signal with one CompuScope at a very high sampling rate to see high frequency signal components, and capturing the same signal at a lower sample rate with another CompuScope to see low frequency signal components. These are the only two types of systems that are currently supported by the CompuScope Windows drivers. So, while the drivers can operate a single Master/Slave system or a Multiple/Independent system consisting of many independent CompuScopes, the two types of systems cannot be combined. So, for instance, the drivers do not support operation of two Master/Slave systems in the same PC. Similarly, the drivers do not support a Master/Slave system installed in the same PC with a single independent CompuScope. The only way to make use of such a system is to use the CP500_ED.EXE utility. CP500_ED can be used to disable CompuScope models so that only one system is recognized and operated by the drivers. By default, the CompuScope drivers assume Master/Slave Multi-Card operation. In order to use the boards in the Multiple/Independent mode of operation, the routine gage_set_independant_operation must be called before initializing Multiple/Independent CompuScopes. The CompuScope board order can be determined using a CompuScope configuration utility, such as Gage Config or Instrument Manager. The application program is able to select to which CompuScope it communicates by calling the gage_select_board routine with the board number as a parameter. This routine is used to then configure each board separately using standard configuration routines. Gage drivers provide special routines for starting the capture, forcing a trigger and aborting the capture for the a system of Multiple Independent CompuScopes. These routines are called CompuScope API Reference Manual 100
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: gage_trigger_view_transfer, gage_tr
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?