Glitch Data Description
In the glitch mode, each pod has two bytes assigned to indicate where
glitches occur in the acquired data. For each row of acquired data there will
be a corresponding row of glitch data. The glitch data is organized in the
same way as the acquired data. The glitch data is grouped in 18-byte rows
for the 1660A. The number of rows is stored in byte positions 101 through
126. The starting byte of the glitch data is an absolute starting point
regardless of the number of rows of acquired data.
A binary 1 in the glitch data indicates a glitch was detected. For example, if a
glitch occurred on bit 1 of pod 8 in data row 1 of an 1660A, bytes 37043 and
37044 would contain:
0000 0000 0000 0010
Byte Position
clock
lines
Pod 81Pod 71pod 62pod 52pod 43pod 33pod 2 pod 14
37041 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes
37059 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes
. .........
. .........
. .........
(x) 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes
1 – unused in the 1661A, 1662A, and 1663A
2 – also unused in the 1662A and 1663 A
3 – also unused in the 1663A
4 – The headings are not a part of the returned data.
Byte 37043 Byte 37044
Bit 15 Bit 1
DATA and SETup Commands
Glitch Data De scription
26–14