CompuScope SDK Manua.. - Egmont Instruments

More documents

Recommendations

Info

gage_trigger_control_2:gage_set_ext_clock_variables:gage_multiple_record:Takes the advantage of certain CompuScope board’s ability to have2 different trigger inputs (source, slope and level) and is used to setup the trigger parameters on the CompuScope boards.Sets the variables required for use of an external clock.Allows the application program to force the CompuScope hardwareto capture only the depth specified when the trigger event occurs.The card then re-arms itself automatically to accept another triggerevent and record that data immediately following the first capture inon-board memory.gage_multiple_record_acquisitions: Sets the number of multiple record groups that will be taken by theCompuScope hardware.voidboard_settings(void)This routine is in GAGEA2D_MS_BM.C. It is used to change any of the board parameters. For example,the default value for board.slope is now GAGE_POSITIVE. If you want the slope to be negative, simplychange GAGE_POSITIVE to GAGE_NEGATIVE and then re-compile your application. This routinemust be called before SetBoard routine.For the detailed description of the board parameters and their legal settings for the CompuScope boards,please see the Appendix: Data Structures Used by Gage Drivers.int CALLBACK WinMain . . . . . . . .This is the main routine in GAGEA2D_MS_BM.C. In this routine, we first initialize the CompuScopedriver and hardware and then verify the board structure for the CompuScope boards. Next, we set theboard setting variables by calling the board settings routine. These settings are actually passed to thehardware and the CompuScope boards are prepared for data capture by the SetBoard routine. We thenstart the acquisition. Two driver routines, gage_triggered and gage_busy, are used to monitor the progressof the trigger event and the completion of the current data acquisition, respectively.Once the acquisition is complete, we determine the relevant addresses by callinggage_calculate_addresses and read samples from each channel into a buffer. After a channel’s data hasbeen read, we save the raw data from the channel to a separate ASCII data file in the current workingdirectory. The raw data from a CompuScope board has the most positive voltage represented as the leastpositive value and the least positive voltage represented as the most positive value. To change this for thepurposes of plotting the data, we negate the raw values for the 12 bit boards and subtract them from 255 for8 bit boards. This continues until the data from all the channels are stored.For example in dual channel mode, for 2 boards (1 Master and 1 Slave) the file names are as follows:GAGE_MS_BM1.DAT, contains the data of channel A of master board.GAGE_MS_BM2.DAT, contains the data of channel B of master board.GAGE_MS_BM3.DAT, contains the data of channel A of slave board.GAGE_MS_BM4.DAT, contains the data of channel B of slave board.Gage API routines used:gage_get_driver_info:gage_start_capture:gage_triggered:Fills a structure or record with the relevant information from thedriver variables about the current CompuScope board settings.Prepares the CompuScope hardware for data acquisition.Determines if the CompuScope hardware has encountered a triggerevent.Page 44CompuScope SDK Manual
gage_force_capture:gage_busy:gage_abort_capture:gage_calculate_addresses:gage_select_board:gage_transfer_buffer_3:How the Memory is ReadForces the capture of data by the CompuScope board(s).Determines if the CompuScope board is busy capturing the data.Used to regain control of the CompuScope board(s).Returns the starting, trigger and ending addresses.Sets the driver so that the current board is the board identified bythe number passed to the routine.Copies the number of sample points in the CompuScope board’smemory space, from the specified channel to the supplied bufferusing bus-mastering. This routine returns an offset to the beginningof the d-word aligned buffer that the driver uses.The memory is read from the boards in a for loop using the gage_transfer_buffer_3 routine. The syntaxfor gage_transfer_buffer_3 is as follows:-Syntax:uInt32 GAGEAPI gage_transfer_buffer_3 (int32 ta, int16 channel, void far *buffer, int32 nsamples);gage_transfer_buffer_3 is used to copy nsamples points from the specified channel to the supplied bufferbeginning from address ta. The channel can be either GAGE_CHAN_A or GAGE_CHAN_B. Therelevant addresses can be obtained by calling gage_calculate_addresses routine. The buffer should betype cast to the appropriate size before accessing it. CompuScope 8-bit boards should be typecast to uInt8.CompuScope 12 and 16 bit boards should be typecast to int16. The CompuScope PCI boards will use busmasteringif available, otherwise this routine is the same as gage_transfer_buffer. The buffer must beslightly longer than the size required to store nsample samples. The extra buffer space required isdetermined by the variable board_info-> user_buffer_padding which is returned by the driver.The application does not need to interleave the data when the acquisition has been performed in singlechannel mode, as is the case with gage_transfer_buffer and gage_transfer_buffer_2.gage_transfer_buffer_3 returns an offset in Bytes to the beginning of the D-word aligned buffer that thedriver uses. The offset is the difference in Bytes between the pointer passed to the driver and the bufferthat the driver uses.Each board is selected in sequence by calling the routine gage_select_board.By default, all the post trigger data are read starting from the trigger address (the address where the triggerevent occurred). You can easily change this address in order to download data starting from anotheraddress. For example, by default the program has the following line:location = trigger; points = board.depth;where trigger contains the trigger address. If you change the code to:location = trigger - 100; points = 200;The program will read 200 samples starting from 100 points before the trigger address. In this way, theuser will download 100 points of pre-trigger data. Note that the start address determines the startingaddress of the valid pre-trigger data. If the difference between the trigger address and the starting addressis less then 100, then there will not be 100 valid pre-trigger data points. If you subtract the starting addressfrom the trigger address, you must take into account the fact that the memory is configured as a circularbuffer. The gage routine gage_normalize_addresses can be used to determine the difference between thetwo addresses taking into account the circular buffer.CompuScope SDK Manual Page 45
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 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

Create successful ePaper yourself

Delete template?

Save as template?