This technical article cover the eventlog.txt file on the T3 device in detail. The T3 exposes its interface as a Removable Disk flash drive in the Windows operating system. All operations on the T3 are in the form of copying files to and from the flash drive.
Each line in the event log file is a device event. These events include such operation and turning on the display or connecting to a bluetooth device. The line is comprised of an event id, time stamp in ISO format and a description (in english). An example of a device event is as follows: 0120;20120116T144026;Display Turned On, Display Turned On event occurring on 16.01.2012 at 14:40:26.
Below is a list of all device events available in the event log file:
- Manual Start (110) - Device has been manually started by the user.
- Auto Start (111) - Device has been automatically started by a scheduled start time.
- Device Restart (112) - If the device needs to restart for some reason, e.g. user changes battery or some internal device fault.
- Recording Started (114) - The recording has started successfully.
- Recording Stopped (113) - The recording has stopped successfully.
- Manual Stop (115) - The recording has been stopped manually by pressing and holding the middle button for 3 seconds.
- Auto Stop (116) - The device has been stopped automatically, without manual input. This is either a scheduled recording which is stopping or a manually started recording which only records for a fixed duration.
- Battery Stop (117) - Recording has been stopped because the battery status is too low to continue.
- Low Disk Space Stop (118) - Recording has been stopped because there is less than 10MB of free memory available.
- Display Turned On (120) - The device display has been turned on by the user by pressing the middle button.
- Display Turned Off (121) - The device display has been turned off which happens 40 seconds after the last button pressed event on the device.
- Scheduled Recording Duration (122) - Duration of the recording in seconds. This event is only available if there is a scheduled stop.
- Oximeter Probe Not on Finger (210) - This event is relayed from the oximeter device and occurs when the probe is off the finger.
- Oximeter Sensor Fault (211) - This event is also relayed from the oximeter and occurs when the probe is on the finger but is not aligned correctly.
- Oximeter Device Off (212) - Oximeter device has disconnected and has most likely turned off. The T3 device will continue its reconnect efforts and the device will reconnect when turned back on.
- Oximeter Device On (213) Oximeter device has connected with the T3.
- Oximeter Battery Low (214) - The battery on the oximeter is low. This means that the oximeter has about 30 minutes left before it turns off. This event is relayed from the oximeter device.
- Oximeter Battery Ctritical (215) - The oximeter sends this message and then turns itself off due to low battery status. This message is relayed from the oximeter device.
- EtCO2 Device Off (216) - EtCO2 device has disconnected and most likely turned off or the bluetooth serial adapter has fallen off. The T3 device will continue its reconnect efforts and the device will reconnect when turned back on.
- EtCO2 Device On (217) - EtCO2 device has connected with the T3.
- EtCO2 Trap Full (224) - The moisture trap on the EtCO2 device is full and needs to be cleaned out.
- EtCO2 Occlusion (220) - There is an occlusion in the nasal cannula, moisture trap or the air input to the EtCO2 device.
- EtCO2 Battery Low (226) - If the EtCO2 unit is being used on batteries then this event is relayed from the device when the battery is low.