Open topic with navigation
Interpreting The PIPE's History Log
Last Updated: 2019-09-24
- The PIPE II
- The Stubby PIPE
The PIPE II and The Stubby PIPE record specific events in an internal Event History log. This log can be used to determine when a PIPE was last downloaded, or to identify abuse of the PIPE.
The History log can be viewed with the USB Downloader Application’s PIPE Settings tab or the IP Downloader’s PIPE Activity page.
Viewing the History Log
You can view the log with the USB Downloader Application or the IP Downloader Management webpage.
The following History log fields are displayed by the USB Downloader Application:
- #: Event sequence number. Usually # 1 to 24, 96 and 97 are important.
- Timestamp: Date and time of the specific PIPE event.
- Event Type: The specific type of event being recorded.
- Value: The event’s recorded value.
- Units: The Value’s unit of measure (e.g. Volt).
- Event Description: A plain text explanation of the entry.
The upper pane displays the 35 most critical events that have occurred since the PIPE was last initialized.
The lower pane shows the most recent 4096 events in chronological order with the most recent at the top.
The following History Log fields are displayed by the IP Downloader’s PIPE Activity page:
- Level: Information or Critical.
- Date and Time: Date and time of the specific PIPE event.
- Message: A plain text explanation of the entry.
- Details: The event’s recorded value.
Most of the PIPE’s Event log entries, recorded in Event #s 98 and higher, will be for normal PIPE operations. For example, this sequence is typical and occurs every time the PIPE is downloaded:
- ReadBufferCleared: The PIPE’s memory was cleared after the button data was transferred to the host software.
- OptionBitsChanged: The host software verified the PIPE’s settings.
- TimeChanged: The host software updated the PIPE’s time counter.
Other Event Types
- The top 24 events are summarized in Event #s 0 to 23.
- The PIPE records impact events using three accelerometers for X, Y and Z axis measurements. When the PIPE collides with a hard surface, the accelerometers record the impact as a voltage value. The higher the value, the harder the impact. See the table below.
- OverVoltage and UnderVoltage
- The top 24 events are summarized in Event #s 24 to 47.
- The PIPE has circuitry to detect positive and negative voltages applied to the read tip. If an external source (e.g. a 9V battery) applies voltage to the tip, the voltage level and duration is recorded.
- There is a known issue with this metric where the log can show a sequence of increasingly larger Overvoltage events ranging from 0V to 500V.
- Typically, these events are spurious and meaningless. If you see these types of events contact Technical Support for an evaluation of their veracity.
- The top 24 events are summarized in Event #s 72 to 95.
- The PIPE records when a conductor (e.g. a coin or paper clip) connects the read tip’s inner pin to the outer housing.
- Tip shorts are common and occur whenever the PIPE is docked in a Downloader. They are generally of no concern for PIPE II. However, Stubby PIPE’s battery will drain faster when the tip is shorted, and therefore Stubby PIPE should only be left docked in the USB Downloader for 10-15 minutes after each download.
- Very long-term tip shorts can have a deleterious effect on battery life, especially in Stubby PIPE.
- FactoryReset and PowerUpReset
- Recorded in Event #s 96 and 97. NOTE: these two lines may be overwritten with other information over time.
- FactoryReset is the initialization of the PIPE during manufacturing. It is normal for this entry to be present.
- PowerUpReset indicates that battery power was temporarily interrupted. This condition should not occur in the field, and will result in corrupted data and data loss. Potential causes of PowerUpReset:
- Abusive handling of the PIPE resulting in MechanicalImpact events.
- Issues with the battery or solder connections.
- Circuit board failure.
- Damaged or faulty wiring.
- When a PowerUpReset occurs, the PIPE will emit a six-note “musical” beep. The PIPE’s memory will be filled with simulated and invalid button reads, and attempting to scan a button will result in a “full” beep.
- If a PowerUpReset event occurs, the PIPE must be returned for depot service. Request an RMA.
The History log tells you how the PIPE has been handled. The presence of the event types below could indicate handling outside the expected usage conditions of The PIPE.
• Placing a metal object across the tip
• Submerging the PIPE II in water
• Connecting the PIPE II to an external power source (negative terminal)
• Connecting the PIPE II to an external power source (positive terminal)
• Dropping the PIPE II deliberately with an undue amount of force
||Equivalent Drop to Concrete
|1.2V – 1.4V
|1.4V – 1.8V
|1.8V – 2.1V
Copyright © TimeKeeping Systems, Inc.
Open topic with navigation