Byte Position
173 88 bytes - Number of valid rows of data (starting at byte 591) for each pod.
Bytes 173 through 228 are unused.
Byte Position Bytes 229 through 232 - contain the number of valid rows of data for pod 8.
Bytes 233 through 236 - contain the number of valid rows of data for pod 7.
Bytes 237 through 240 - contain the number of valid rows of data for pod 6.
Bytes 241 through 244 - contain the number of valid rows of data for pod 5.
Bytes 245 through 248 - contain the number of valid rows of data for pod 4.
Bytes 249 through 252 - contain the number of valid rows of data for pod 3.
Bytes 253 through 256 - contain the number of valid rows of data for pod 2.
Bytes 257 through 260 - contain the number of valid rows of data for pod 1.
261 88 bytes - The trace point location for each pod. This byte group is organized
in the same way as the data rows (starting at byte 173 above). These
numbers are base zero numbers which start from the first sample stored for
a specific pod. For example, if bytes 341 and 344 contain the value 101008,
the data in row 101008 for that pod is the trigger. There are 101008 rows of
pre-trigger data as shown below.
row 0
row 1
.
row 101007
row 101008 – trigger point
row 101009
row 101010
349 234 bytes - Unused
583 2 bytes - Real Time Clock (RTC) year at time of acquisition. Year value is
equal to the current year minus 1990.
585 1 byte - RTC month (1 = January . . . 12 = December ) at time of acquisition.
586 1 byte - RTC day of the month at time of acquisition.
587 1 byte - RTC day of the week at time of acquisition.
588 1 byte - RTC hour (0 through 23) at time of acquisition.
589 1 byte - RTC minutes at time of acquisition.
590 1 byte - RTC seconds at time of acquisition.
DATA and SETup Commands
Data Preamble Description
27–9