CompuScope SDK Manua.. - Egmont Instruments

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