11.1 PtLogEntryDataType

Table 92 - PtLogEntryDataType Structure
NameTypeDescriptionOptional
PtLogEntryDataTypestructure
FaultSituationNumber0:ByteIdentification of fault situation. 0 means current fault situation. Usually, an operator acknowledge generates a new fault situation if the server maintains different fault situations or snapshots in the diagnosis system.False
EventNumber0:UInt32Unique number of event. LogEntries with the same EventNumber belong to different fault situations.False
EventTypePtEventTypeEnumerationCharacterization of the event (fault, warning, etc.), encoded as PtEventTypeEnumeration Must never have the value "UNSPECIFIED".False
EventClassPtEventClassEnumerationFault-code identifying a fault or warning, encoded as PtEventClassEnumeration. Must never have the value "UNSPECIFIED". False
VendorEventCode0:Int32Optional field containing the vendor specific fault code. Set to -1 if not used. -1 is reserved and may not be used as error code. In case of an existing definition of -1 as error code, it must be mapped to a different value. Clients should not expect this field to be present (backward compatibility).False
VendorEventSubcode0:UInt32Additional information specifying more detailed information for the VendorEventCode.True
EventText0:LocalizedTextBrief description of the fault or warning.False
EventComing0:DateTimeTime when the event appears.False
EventGoing0:DateTimeTime when the event disappears. May not be set when the log entry is created. The field shall be set to "1900-01-01T00:00:00Z" to indicate an "empty" value in this case. Must be set when the event disappears.False
EventAcknowledged0:DateTimeTime when the event is acknowledged. May not be set when the log entry is created. The field shall be set to "1900-01-01T00:00:00Z" to indicate an "empty" value in this case. Must be set when the event is acknowledged.False

Its representation in the AddressSpace is defined in Table 93

Table 93 - PtLogEntryDataType Definition
AttributeValue
BrowseNamePtLogEntryDataType
IsAbstractFalse
ReferencesNodeClassBrowseNameDataTypeTypeDefinitionOther
Subtype of the 0:Structure type defined in OPC 10000-3.
Conformance Units
Powertrain Logbook Readable

Note: EventType refers to the diagnosis of Axis function. In addition to this, asset component related health status is available in the asset model (see [OPC 40400-1]).

If the Server provides the LogObject, the LogRecords provided by this 0:LogObjectType Object shall make the same information as the PtLogEntryDataType elements of the Logbook Object's LogEntries array available for the Client. The necessary mapping of PtLogEntryDataType fields to 0:LogRecord fields is specified in Table 94.

Table 94 - Mapping of PtLogEntryDataTypeFields
LogRecord fieldPtLogEntryDataType field mappedUsed Value
TimeEventComing, EventGoing, EventAcknowledgedTime when the event appears, disappears or is acknowledged. Each of these generates a new event.
SeverityEventTypeSeverity mapped according to Table 95.
EventType-PtLogObjectEventType if a corresponding PtLogObjectEventType Event is generated, otherwise Null NodeId.
SourceNode-NodeId of the PtFunctionType Object representing the axis/drive affected.
SourceName-BrowseName of the SourceNode.
MessageEventText
TraceContext-
AdditionalData[]
{"LogEntry", Value}
Value = PtLogbookEventType.LogEntryUse LogEntry Property of corresponding PtLogObjectEventType. If Events are not supported, use corresponding element of the PtLogbook LogEntries component.

Table 95 maps the EventType fields' enumeration values of the PtLogEntryDataType to severity ranges specified in OPC 10000-26, "Table 9 - LogRecord Severity Mapping".

Table 95 - Mapping of EventType Field Value to Severity ranges
EventType Field ValueMapped Severity rangesSyslog Names
FAULT301 - 1000 Alert, Emergency
WARNING251 - 299Critical
MAINTENANCE230 - 250Error
MAINTENANCE_REQUIRED201 - 229Error
MAINTENANCE_DEMANDED151 - 200Warning
MAINTENANCE_CALIBRATION101 - 150Notice