EasyParse format events markers

Events are records of non-sample incidents, and can be used to aid interpretation of the deployment data, or for diagnostic purposes. EasyParse events are stored in dataset-0, separate from the sample data in dataset-1.

In EasyParse format, all events have the same structure; this helps to make the stream of events easier to parse because they all have the same, fixed size: 16-bytes. Compared to Standard events, the format of the timestamp is different, and all events have an extended data field, or payload. If the payload is not applicable to a particular event type, its content is not defined, and no attempt to interpret it should be made.

For consistency, the Type Codes are the same as used for Basic (F7) and Extended (F5) events in Standard data storage format, and all are listed below for completeness. However, note that some type codes should never be encountered in EasyParse events; for example, 0x01 used for time synchronization is completely redundant, as all samples and events have their own timestamp.

Bytes 0,116-bit byte-swapped CCITT CRC of Bytes 2..15
Byte 2Type Code
Byte 30xF4 marker byte
Bytes 4..1164-bit unsigned number of milliseconds since 1970-01-01 00:00:00
Bytes 12..1532-bit (4-byte) payload dependent on 'T ype Code'

The event payloads depend on the event Type Code:

  1. Most event types have no payload and the content is not defined; it should be ignored.
  2. A separate time-stamp field for milliseconds is redundant and never used.
  3. For regime bin events (0x20), the payload is the number of reading values in the reported average.
  4. For cast events, the payload is the address of the sample in dataset-1, where the actual sample data is stored.


In the case of event 0x23 (End of profiling cast), the sample address given is that of the next sample, ie. the first sample which is not in the cast.

Hex CodeDescriptionPayload
0x00Unknown or unrecognized eventsundefined
0x01Time synchronization markerundefined
0x02stop command receivedundefined
0x03Run-time error encounteredundefined
0x04CPU reset detectedundefined
0x05One or more parameters recovered after resetundefined
0x06Restart failed : Real Time Clock/Calendar contents not validundefined
0x07Restart failed : logger status not validundefined
0x08Restart failed : primary schedule parameters not be recovered.undefined
0x09Unable to load alarm time for next sampleundefined
0x0ASampling restarted after resetting Real Time Clock (RTC)undefined
0x0BParameters recovered, sampling restarted after resetting RTC.undefined
0x0CSampling stopped, end time reachedundefined
0x0DStart of a recorded burstundefined
0x0EStart of a wave burstundefined
0x0F( reserved )undefined
0x10Streaming now OFF for both portsundefined
0x11Streaming ON for USB, OFF for serialundefined
0x12Streaming OFF for USB, ON for serialundefined
0x13Streaming now ON for both portsundefined
0x14Sampling started, threshold condition satisfiedundefined
0x15Sampling paused, threshold condition not metundefined
0x16Power source switched to internal batteryundefined
0x17Power source switched to external batteryundefined
0x18Twist activation started samplingundefined
0x19Twist activation paused samplingundefined
0x1AWiFi module detected and activatedundefined
0x1BWiFi module de-activated; removed or activity timeoutundefined
0x1CRegimes enabled, but not yet in a regimeundefined
0x1DEntered regime 1undefined
0x1EEntered regime 2undefined
0x1FEntered regime 3undefined
0x20Start of regime binnumber of readings in average; see note below
0x21Begin profiling 'up' castaddress of sample in dataset-1
0x22Begin profiling 'down' castaddress of sample in dataset-1
0x23End of profiling castaddress of first sample not in cast
0x24Battery failed, schedule finished.undefined
0x25Directional dependent sampling, beginning of fast sampling modeundefined
0x26Directional dependent sampling, beginning of slow sampling modeundefined
0x27Energy used marker, internal batteryenergy consumed from power source since last accumulator reset
0x28Energy used marker, external power sourceenergy consumed from power source since last accumulator reset
0x29Device control action resultresult of control action

Logger configuration may also include a derived data channel, type cnt_00, which contains the same value as event 0x20 when in the regimes sampling mode. The benefit of turning it on when storing data in EasyParse format is that the value is then available in the main sample data in dataset-1; the dataset containing these events does not have to be retrieved. Refer to the Section "Integrating with a profiling float" for further details.