CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

GAG2A2D_MUL_BM.EXEThe sample program GAGEA2D_MUL_BM.EXE is provided with CompuScope SDK for C/C++ forWindows.GAGEA2D_MUL_BM sample program does a multiple record capture from a single CompuScope (dual orsingle channel mode), and bus-masters the data to PC memory. All the records from all the channels arethen written to the separate ASCII data files. In order to view the resulting files, you will have to runMicrosoft Excel or another program, which allows you to import ASCII data. You can also use any texteditor. In Microsoft Excel, the data files can be read by opening it from the File menu. Excel’s ImportWizard will guide you through importing the data. Select “Delimited” for the type of data, and “Tab” asthe delimiter for the data. Then you can plot the data.Flow Chart describing the sample program.StartInitialize Driver and HardwareSet Hardware ParametersAllocate Buffer(s)Start CaptureNTriggeredNTimeoutYForce CaptureYNTimeoutYYBusyNAbort CaptureGroup. Read Trigger,Start and EndaddressesTransfer data using scatter-gatherDMA for optimal speed.Save data to file(s)**Readable by ExcelYMore GroupsNEndPage 46CompuScope SDK Manual
Description of the Routines used by the sample programFollowing are the routines used by the sample program GAGEA2D_MUL_BM. A brief description for allthe Gage API routines used by each of the following routines is also given. For detailed description of allthe Gage API routines, please see the CompuScope API Reference Manual.For a complete description of the SetDefaultBoardLocation, InitBoard, SetBoard, One_SetBoard andboard_settings, refer to their description in the previous section, which describes the GAGEA2D_MS_BMsample program.int CALLBACK WinMain . . . . . . . .This is the main routine in GAGEA2D_MUL_BM.C. In this routine, we first initialize the CompuScopedriver and hardware and verify the board structure for the CompuScope boards.Next, we set the board setting variables by calling the board settings routine. These settings are actuallypassed to the hardware and the CompuScope boards are prepared for data capture by the SetBoard routine.We then start the acquisition. As in single record acquisition, the gage_triggered routine is used to detectwhen the first trigger occurs. In multiple record mode, however, gage_busy remains active until theCompuScope has captured all multiple records. This occurs when the requested number of records, as setby gage_multiple_record_acquisitions_32, has been acquired for CP500, single PCI or cPCICompuScopes. For older ISA and X12/PCI CompuScopes, however, multiple recording terminates andgage_busy becomes inactive only when on-board memory is full.We determine the relevant addresses by calling gage_calculate_mr_addresses for each group. Thegage_calculate_mr_addresses routine returns the addresses for a specific group. If the addresses are read,the return value is the group number that was passed to the routine. In this way, we can loop until all thegroups are read. When this occurs, we know that there are no more groups to be downloaded. Within thisloop we also check if the board supports embedded enhanced trigger bits (EETBs). If the board supportsEETBs, we then call the gage_calculate_mra_addresses routine to adjust the trigger address according tothe EETBs. The gage_calculate_mra_addresses routine is required due to the architecture of thehardware. Depending on the CompuScope model, some lower trigger address bits are not stored on theCompuScope but must be embedded in the data records, typically in the first sample of each multiplerecord group. Using the gage_calculate_mra_addresses routine, the sample program extracts the EETBsand corrects the trigger address as required.The CP500 CompuScopes have the capability of specifying the number of groups to capture rather thanfilling up all of the onboard memory. Each group from the specified channel is saved to an ASCII file inthe current working directory. The raw data from a CompuScope board has the most positive voltagerepresented as the least positive value and the least positive voltage represented as the most positive value.To change this for the purposes of plotting the data, we negate the raw values for the 12 bit boards andsubtract them from 255 for 8 bit boards.For example, in dual channel mode the file names are as follows:GAGE_MUL_BM_DUAL_CHANA_GR1.DAT, contains the data of group 1 of channel A.GAGE_MUL_BM_DUAL_CHANB_GR1.DAT, contains the data of group 1 of channel B.GAGE_MUL_BM_DUAL_CHANA_GR2.DAT, contains the data of group 2 of channel A.GAGE_MUL_BM_DUAL_CHANB_GR2.DAT, contains the data of group 2 of channel B.…….In single channel mode the file names are as follows:GAGE_MUL_BM_SINGLE_GR1.DAT, contains the data of group 1.GAGE_MUL_BM_SINGLE_GR2.DAT, contains the data of group 2.GAGE_MUL_BM_SINGLE_GR3.DAT, contains the data of group 3.…….CompuScope SDK Manual Page 47
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 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
show all

CompuScope SDK Manua.. - Egmont Instruments

Create successful ePaper yourself

Delete template?

Save as template?