Operating instructions

M300USERSGUIDE SEA
SETUP  109
for each acquisition event type. When you use the acquisition setup dialog in the M300, the data size
will get filled automatically for most acquisition events. There are some acquisition events where the
data size must be provided by the user. If the size of the data is overridden care must be taken to
ensure that a large enough value is specified.
WARNING:NotspecifyingalargeenoughdatasizeisaseriousproblemwhichmightcausetheM300tocrash.
Attheveryleastthedatawillbemissingorincorrect.
Type
This is a drop down menu that lists all of the available acquisition types for the specific acquisition
board the acquisition event is being added to.
The M300 is smart when presenting the list of acquisition types. It will only list the types that are
valid for the selected board. This prevents setting up invalid acquisitions to the incorrect board type.
WARNING:Awordofcau tionwhensettinguptheacq.300tab lemanuallywi ththeeditor.Th eusermust
ensureproperacquisitionisdonetothecorrectboardtypes.
Note: Foracompletelistoftheacquisitiontyp es,consulttheM 300ReferenceGuide,acquisitionsection.
http://www.scieng.com/pdf/M300Reference.pdf
Para1,Para2andPara3
These are extra configuration/setup parameters for the acquisition event. The meaning of these
parameters changes from acquisition type to acquisition type. Consult the acquisition type reference
manual for information on the valid parameter values for each acquisition event type. In the M200
system, these parameters sometimes configured how a particular interface card was setup. Since we
now have entries for each interface in the board table, some of these parameter values are not the
same as in the case of the M200. When a parameter is used to configure the acquisition event, we
have kept the same configuration values as the M200 system.
Offset
The sample offset select in which acquisition tick the acquisition event gets acquired. In the past all
synchronous acquisition events got done in the first tick. This can overload the first tick. Usually the
duration in the proxy was longest for the first acquisition tick. We can balance the acquisition load
over several ticks (allowing us to do more).
This only applies to synchronous acquisition events. For asynchronous acquisition events, leave it at
zero.
Home
Moves the selected item to the top of the list. This changes the order of the acquisition event in the
acq.300 file. This is not the order in which the acquisition events will get acquired. The order for the
acquisition events is set in the buffer setup.
End
Moves the selected item to the bottom of the list. This changes the order of the acquisition event in
the acq.300 file. This is not the order in which the acquisition events will get acquired. The order for