CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

uInt32 sample_rate;void far *memptr;int16trigger_level_2;int16trigger_slope_2;int16trigger_source_2;int16imped_a;int16imped_b;uInt16 external_clock_adjust;int16trigger_step;uInt16 board_version;uInt32 ee_options;uInt16 index_offset;int32sample_offset_32;int32sample_resolution_32;int16diff_input_a;int16diff_input_b;uInt32 multiple_record_count;uInt32 real_time_active;int16trigger_enable_control;int16trigger_sensitivity;int16trigger_bandwidth;int16trigger_sensitivity_2;int16trigger_bandwidth_2;uInt16 max_trigger_sensitivity;uInt16 trigger_address_offset;uInt16 user_buffer_padding;int16bus_master_support;} gage_driver_info_type;;Page 56 Appendix A CompuScope SDK Manual
Description of Parameters for gage_driver_info_type StructureValues of the constants used below can be found in GAGE_DRV.H or in GAGE_LOW.H file.indexsegmentBoard_typemax_memorymax_available_memorybank_offset_valuemodeenable_aenable_bratemultipliercoupling_acoupling_extgain_again_bgain_exttrigger_depthbase I/O port index of CompuScope, used to transfer data from theCompuScope card. The value is typically read from the configurationfile GAGESCOP.INC. For PCI CompuScope boards, the value is0xffff.absolute address of memory segment, typically read fromGAGESCOP.INC. For PCI CompuScope boards, the value is 0xffff.numeric constant representing the board type as defined in theGAGE_DRV.H file.memory size of CompuScope board (in samples).available memory (in samples) in current mode, i.e. max_memory insingle channel, max_memory / 2 in dual channel.block number where the data for channel B starts.current mode of the board, which can be GAGE_SINGLE_CHAN orGAGE_DUAL_CHAN or GAGE_QUAD_CHAN. Mode is set bygage_capture_mode routine.current enable status of channel A. On board CompuScope memory iseither connected or disconnected to the transceiver by callinggage_input_control routine with either GAGE_INPUT_ENABLE orGAGE_INPUT_DISABLE.current enable status of channel B. On board CompuScope memory iseither connected or disconnected to the transceiver by callinggage_input_control routine with either GAGE_INPUT_ENABLE orGAGE_INPUT_DISABLE.set by gage_capture_mode routine.set by gage_capture_mode routine. The constants are GAGE_HZ,GAGE_KHZ, GAGE_MHZ, GAGE_GHZ and GAGE_EXT_CLK.status of the coupling for channel A, either GAGE_AC or GAGE_DC.status of the coupling for the external trigger. Use GAGE_AC orGAGE_DC with gage_trigger_control_2 routine.status of the gain value for channel A. One of the predefined constants,such as GAGE_PM_5_V, defined in GAGE_DRV.H file should beused with gage_input_control routine to set this parameter:status of the gain value for channel B. One of the predefined constants,such as GAGE_PM_1_V, defined in GAGE_DRV.H file should beused with gage_input_control routine to set this parameter:status of the gain for the external trigger. To set, use eitherGAGE_PM_5_V or GAGE_PM_1_V with gage_trigger_control_2routine.number of points captured after the trigger event set bygage_trigger_control_2 routine.CompuScope SDK Manual Appendix A Page 57
Page 1 and 2:
Volume I:CompuScope C/C++Software D
Page 3 and 4:
Gage Applied Technologies, Inc. Sof
Page 5:
Global Table of ContentsVolume I Co
Page 8 and 9:
Chapter 5: Sample ProgramsWindows S
Page 11 and 12:
PrefaceImportant Notes:• The Comp
Page 13: Chapter 2: BasicCompuScopeOperation
Page 16 and 17: CompuScope A/D cards generally oper
Page 18 and 19: Multiple CompuScope SystemsThe Comp
Page 20 and 21: Plug-n-Play is an inherent part of
Page 22 and 23: On-Board MemoryOrganization of theC
Page 24 and 25: memory counter overflow rolls over
Page 26 and 27: If during the data acquisition the
Page 28 and 29: On-board Memory: A Programmer’s V
Page 30 and 31: CompuScope RepetitiveCapture Perfor
Page 32 and 33: depth portion of the single channel
Page 34 and 35: Page 26CompuScope SDK Manual
Page 36 and 37: Sample Programs Folder Structure us
Page 38 and 39: • Gage_drv.hGage_drv.h contains g
Page 41 and 42: Writing a C Application forCompuSco
Page 43 and 44: The last routine, gage_trigger_cont
Page 45: Chapter 5:Sample Programs
Page 48 and 49: Program NameA2D_PAGED_TRANSFER.EXED
Page 50 and 51: Flow Chart describing the sample pr
Page 52 and 53: gage_trigger_control_2:gage_set_ext
Page 54 and 55: GAG2A2D_MUL_BM.EXEThe sample progra
Page 56 and 57: Gage API routines used:gage_get_dri
Page 58 and 59: DIGITAL_INPUT.EXEThe sample program
Page 61: Chapter 6:Appendices
Page 66 and 67: trigger_level level at which trigge
Page 68 and 69: trigger_sensitivitytrigger_bandwidt
Page 70 and 71: Settings for boarddef structure fie
Page 72 and 73: 10 KHz SRTI_10_KHZ5 KHz SRTI_5_KHZ2
Page 74 and 75: • couple_eThe parameter couple_e
Page 76 and 77: Example:Below is illustrated a typi
Page 79 and 80: Appendix C: CompilingCompuScope SDK
Page 81: Creating a new LabWindows CVI proje
Page 84 and 85: Arbitrary Waveform GenerationOne co
Page 86 and 87: Technical SupportGage Applied Techn
show all

CompuScope SDK Manua.. - Egmont Instruments

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

Delete template?

Save as template?