CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

Flow Chart describing the sample program.StartInitialize Driver and HardwareSet Hardware ParametersAllocate Buffer(s)Start CaptureNTriggeredNTimeoutYForce CaptureYNTimeoutYYBusyNAbort CaptureRead Trigger, Startand End addressesTransfer data using scatter-gatherDMA for optimal speed.Save data to file(s)**Readable by ExcelYMore boardsNEndDescription of the Routines used by the sample programFollowing are the routines used by the sample program GAGEA2D_MS_BM. Brief descriptions of theGage API routines used by each of the following routines are also given. For a detailed description of allthe Gage API routines, please refer to the CompuScope API Reference Manual.voidSetDefaultBoardLocation (uInt16 seg, uInt16 ind)This routine is in app_supp.c and is called if the DLL routine gage_read_config_file returns false whichindicates that the board location configuration file is corrupted or missing. A default segment and index arepassed to this routine. The global data structure gage_board_location, which contains the addresses of thememory segments and I/ O addresses, is updated prior to calling the DLL gage_driver_initialize routine.For the CP500 family of CompuScopes, the memory segment and I/ O addresses are set to 0xFFFF.Page 42CompuScope SDK Manual
Gage API routines used:gage_set_records:Sets the values for the memory segment and I/O address in thegage_board_location array.intInitBoard (void)This routine is in APP_SUPP.C and does all the necessary calls in the proper order to initialize the driver.Some modifications to this routine are necessary if the programmer does not want the progress messagesdisplayed.Gage API routines used:gage_get_config_filename:gage_read_config_file:gage_driver_initialize:gage_board_type_size_to_text:gage_get_driver_info_structure:gage_get_driver_info:gage_get_boards_found:gage_initialize_start_capture:gage_select_board:gage_detect_multiple_record:Determines the complete path to the configuration file that containsthe board location data.Reads the configuration file and stores the data in an array of words.Fully configures each board found in the system.This routine returns a pointer to a string with the parameters thatcontain information about the CompuScope board(s) installed in thesystem.Returns the size of the main structure used by the driver and alsoretrieves the driver version and number.Fills a structure with the relevant information from the drivervariables about the current settings on the current CompuScopeboard.Determines the number of the CompuScope boards found.Sets up the gage_start_capture routine.Sets the driver so that the current board is the board identified bythe number passed to the routine.Used to determine if a CompuScope board has multiple recordcapability.void SetBoard (void)This routine is in APP_SUPP.C. It uses the boarddef structure named board, which was previously loadedwith the desired capture parameters. The sample program initializes these parameters statically.Note that the order in which SetDefaultBoardLocation, InitBoard and SetBoard are called is importantfor the proper operation of the CompuScope hardware. The order is also important if the user wants thedriver to correctly maintain such information as the amount of memory available for each channel. Thevalues of the GAGE constants are defined in GAGE_DRV.H.Gage API routines used:gage_get_driver_info:gage_select_board:gage_capture_mode:gage_input_control:Fills a structure or record with the relevant information from thedriver variables about the current CompuScope board settings.Sets the driver so that the current board is the board identified bythe number passed to the routine.Sets the data capture mode and the sampling rate.Used to set up the input channels on the CompuScope boards. Thisroutine must be called for each channel in the system.CompuScope SDK Manual Page 43
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 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 64 and 65: uInt32 sample_rate;void far *memptr
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

CompuScope SDK Manua.. - Egmont Instruments

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

Delete template?

Save as template?