Event Type and Event Detail Glossary
In the portal event log, Event Type is the classification of what happened. Event Detail is the related code, such as PFault, TFault, SOTF, or Fault <50. Some events have no separate detail. Use the table to jump to an event.
Fault and load events
Event type
Permanent
Event detail
PFault
PFault means the device saw normal load, then detected a current spike, immediately followed by a line outage. After waiting 5 minutes, the device retested the line and did not see load again.
This usually means there is a permanent outage as the result of a fuse blowing or a recloser locking out.
Per the device’s time-current curve settings, a current spike only meets the trip threshold if both conditions are satisfied: the current level is high enough, and it stays at that level long enough.
Event detail
SOTF
SOTF means Switch Onto Fault. This means the device saw no load or very little load – it understands that it is installed on a de-energized line, then detected a current spike, immediately followed by a line outage. After waiting 5 minutes, the device retested the line and did not see load again.
This typically indicates that the line was energized onto an existing fault condition causing a fuse to blow or a recloser to lock out, and the device to register the event as a fault.
Related Event Log Entries
In some cases, the event log may include a separate companion entry with a blank Event Type and Fault <50 in Event Detail before the Permanent Fault is registered. Fault <50 means the device was on a line with steady-state load, detected a current spike, and then saw the load drop by more than 50% within 15 seconds without dropping to 0 A.
If the line then drops to 0 A within 5 minutes after the Fault <50 event, the device will register a Permanent Fault. When this happens, the event log will include two new entries:
- Blank in Event Type with Fault <50 in Event Detail
- Permanent Fault in Event Type with PFault in Event Detail
Event type
Temporary
Event detail
TFault
TFault means the device saw normal load, then detected a current spike, immediately followed by a line outage. After waiting 5 minutes, the device retested the line and saw load again.
This usually means the fault was cleared by a recloser and the line was restored.
Related Event Log Entries
In some cases, the event log may include a separate companion entry with a blank Event Type and Fault <50 in Event Detail before the Temporary Fault is registered. Fault <50 means the device was on a line with steady-state load, detected a current spike, and then saw the load drop by more than 50% within 15 seconds without dropping to 0 A.
If the line then has a load greater than 3 A within 5 minutes after the Fault <50 event, the device will register a Temporary Fault. When this happens, the event log will include two new entries:
- Blank in Event Type with Fault <50 in Event Detail
- Temporary Fault in Event Type with PFault in Event Detail
Event type
Probable Temporary Fault - Low Load
Event detail
PFault
A Probable Temporary Fault – Low Load event means the device detected a fault sequence that based on experience is presumed to be temporary but could be permanent – this presumption is based on the line historically carrying very low load.
Because the normal load on the line is already low, the device may read near-zero amps after the event even though the line is not de-energized. The Event Detail may still appear as PFault, but the system uses the line’s historical load behavior to determine that the event is more likely a temporary than a permanent fault.
Event type
Over-Current
Event detail
Overcurrent
An Over-Current event means the device detected a current spike. A current spike does not necessarily mean a fault occurred. It only means the device’s trip threshold was met.
This event will only register if the Overcurrent Alert feature is enabled, in which case the device will send an overcurrent alert when this occurs.
After 5 minutes, if the event qualifies as a fault, the customer may receive a fault notification in addition to the earlier overcurrent alert. The events that register and the alerts that are issued depend on the device configuration and portal alert settings.
Event type
Probable Cold Load Pickup
A Probable Cold Load Pickup event means the device:
- Detected a current spike when the line had been dead or carrying very little load for an extended period.
- Saw the load remain steady in the 15 seconds following the current spike.
- Saw the load continue to remain steady 5 minutes after the current spike.
A Probable Cold Load Pickup will typically appear as either two or three event log entries, depending on the device configuration.
Typical event log entries:
- Probable Cold Load Pickup in Event Type with Fault <50 in Event Detail
- Probable Cold Load Pickup in Event Type with SOTF in Event Detail
If the Overcurrent Alert feature is enabled, the event log will also include an Over-Current entry:
- Probable Cold Load Pickup in Event Type with Fault <50 in Event Detail
- Over-Current in Event Type with Overcurrent in Event Detail
- Probable Cold Load Pickup in Event Type with SOTF in Event Detail
Event type
Current Reset
Event detail
Current Reset
Current Reset means the device saw sufficient steady-state load on the line to reset its fault indication.
Event type
Over-Current/No Fault
Event detail
RTFault
Over-Current/No Fault means the device was on a loaded line and detected a current spike. After the current spike, the load at the device’s location dropped between 1% and 49%.
We interpret this as a fault that occurred downstream and was cleared by a downstream protection device.
This event is only issued when the device has the ride-through program enabled when shipped from the factory. If the ride-through program is not enabled, the event will be issued as an Over-Current event if the overcurrent configuration is enabled, or as a Fault Like event if the overcurrent configuration is not enabled.
Other Events
Event type
Fault Like
Event detail
Fault Like
Fault Like means the device detected a current spike, but there was no loss of power afterward or no substantial loss of load.
A Fault Like event means there was steady-state load on the line before the current spike. At the device’s installation location and after the current spike, the line stayed energized and did not lose a substantial amount of load. Therefore, the system does not classify it as a true fault.
This will not appear in the portal until the next successful check-in.
Event type
Ride Recover
Event detail
Ride Recover
Ride Recover means the device was on a loaded line and detected a current spike. After the current spike, the load at the device’s location increased or stayed the same.
We interpret this as inrush from a large load coming online, causing a current spike without a fault occurring.
This will not appear in the portal until the next successful check-in.
This event only registers when the device has the ride-through program enabled when shipped from the factory. If the ride-through program is not enabled, the event will issue as an Over-Current event if the overcurrent configuration is enabled, or as a Fault Like event if the overcurrent configuration is not enabled.
Device Status Events
Event type
Device Reset (Magnet)
Event detail
Device Reset (Magnet)
Device Reset (Magnet) means the device rebooted. This most often will occur when the device is reset using its magnet reset/test tool. When this happens, the device will check in to the portal.
Event type
Reset Pin Reset Event
Event detail
Reset Pin Reset Event
Reset Pin Reset Event generally means the device experienced a power interruption and then restarted.
This may indicate that a lightning strike or other EMI-related event caused the device’s processor to reset.
This will not appear in the portal until the next successful check-in.
Event type
GNSS Bad Lock
Event detail
GNSS Bad Lock
GNSS Bad Lock means the device attempted to obtain a GPS lock, but the lock was unsuccessful or the lock quality was poor.
This will not appear in the portal until the next successful check-in.
Event type
Failed to Hit Cell Tower
Event detail
Failed to Hit Cell Tower
Failed to Hit Cell Tower means the device attempted to connect through the cellular network but was unsuccessful.
This event may appear multiple times if the device made multiple connection attempts.
This will not appear in the portal until the next successful check-in.
Event type
No Data Response Error
Event detail
No Data Response Error
No Data Response Error means the device attempted to send a packet, but the connection was poor or timed out before the device received confirmation that the server successfully received it.
This will not appear in the portal until the next successful check-in.
Event type
Power Down On Reset
Event detail
Power Down On Reset
Power Down On Reset means the device experienced a loss of power, usually due to a physical event. This causes the processor to lose all power and clears the activity logs saved on the device – but these activity logs will remain memorialized and available on the cloud-based database.
This will not appear in the portal until the next successful check-in.
Event type
Device Reset (Watchdog)
Event detail
Device Reset (Watchdog)
Device Reset (Watchdog) means the device’s software became unresponsive or encountered an issue, prompting an automatic reset to restore normal operation.
This will not appear in the portal until the next successful check-in.