CompuScope SDK Manua.. - Egmont Instruments

op_mode, float tbs, int32 far *trig, int32 far *start, int32 far *end, int16 data);
Note that the chan parameter in this routine is 0-based. That is, channel A is specified by 0 and channel B
is specified by 1. The data variable is the data located at the raw trigger address. This must have been
previously downloaded as described above.
The recommended way of calculating Multiple Record addresses using the embedded ETBs in order to
correct the trigger address and then downloading the record data is shown below:
gage_get_driver_info (&gdi);
tbs = 1000000000 / sample_rate; /* tbs is time between samples in nanoseconds. The correct value must
be passed to address calculation routines for correct operation */
group = 1;
while (group == gage_calculate_mr_addresses (group, gdi.board_type, gdi.depth,
gdi.max_available_memory, chan, gdi.mode, tbs, &trig, &start, &end) {
}
data = gage_mem_read_master (trig);
gage_calculate_mra_addresses (gdi.board_type, gdi.board_version, chan-1, gdi.mode, tbs, &trig,
&start, &end, data);
size = (end - trig) +1;
offset=gage_transfer_buffer_3(trig, GAGE_CHAN_A, buffer, size);
display_data(offset); /*User-supplied routine that displays buffer, beginning at offset*/
group++;
Due to varying amounts of inter-record padding throughout a Multiple Record Acquisition, the groups
differ in size after embedded ETBs have been used to adjust the trigger addresses.
An application program can check if Enhanced ETBs are available on the current CompuScope hardware
by comparing the ee_options field of the gage_driver_info_type structure and comparing it against the
EEPROM_OPTIONS_MULREC_ADJUST constant (defined in the EEPROM.H file). For example:
gage_get_driver_info (&gdi);
if (gdi.ee_options & EEPROM_OPTIONS_MULREC_ADJUST)
printf ("embedded trigger bits available\n");
Notes
If you are using Multiple Record, you should generally not use a busy timeout. A busy timeout is usually
used to abort a capture if it is not finished within a predefined amount of time. Because a Multiple Record
capture is actually a series of captures, the Multiple Record acquisition can last a long and perhaps
indeterminate amount if time. Consequently, an incorrect busy timeout value may prematurely abort
Multiple Record acquisition before all the captures are complete. If you must use a busy timeout, make
sure that the timeout value exceeds the longest possible total Multiple Record acquisition time.
CompuScope API Reference Manual
107