Search
27 result(s) for EventTypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.1 Overviewdefines details on the type model for ObjectTypes and VariableTypes . Standard ReferenceTypes , DataTypes and EventTypes are defined in Clauses 7 to 8.61 . The informative Annex A describes general considerations
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.7.2 EventTypesEventTypes Each Event is of a specific EventType . A Server may support many types. This part defines the BaseEventType that all other EventTypes derive from. It is expected that other ... companion specifications will define additional EventTypes deriving from the base types defined in this part. The EventTypes supported by a Server are exposed in the AddressSpace of a Server . EventTypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.7.3 Event CategorizationEvent Categorization Events can be categorised by creating new EventTypes which are subtypes of existing EventTypes but do not extend an existing type. They are used only to identify
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.15 GeneratesEventMethod InstanceDeclaration . The TargetNode of this ReferenceType shall be an ObjectType representing EventTypes , that is, the BaseEventType or one of its subtypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.16 AlwaysGeneratesEventMethod InstanceDeclaration . The TargetNode of this ReferenceType shall be an ObjectType representing EventTypes , that is, the BaseEventType or one of its subtypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model9.1 GeneralGeneral The remainder of 8.61 defines EventTypes . Their representation in the AddressSpace is specified in OPC 10000-5 . Other parts of this series of standards may specify additional EventTypes . Figure ... informally describes the hierarchy of these EventTypes. Figure 43 - Standard EventType Hierarchy
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model9.2 BaseEventTypeBaseEventType The BaseEventType defines all general characteristics of an Event . All other EventTypes derive from it. There is no other semantic associated with this type
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modeleither ModelChangeEvent type depending on circumstances. It may also define subtypes of these EventTypes adding additional information. To ensure interoperability, the following guidelines for Events should be observed
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.13.1.1 OverviewSourceNode , Time and Description . OPC 10000-3 describes the Event model and the base EventTypes . The Properties of the base EventTypes and the representation of the base EventTypes
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.22.3 EventFilterfully inherited EventType where the Node is also the source of a HasModellingRule reference. EventTypes , InstanceDeclarations and Modelling Rules are described completely in OPC 10000-3 . In some cases ... same SimpleAttributeOperand . browsePath will apply to multiple EventTypes . If the Client specifies the BaseEventType in the SimpleAttributeOperand.typeDefinitionId then the Server shall evaluate the SimpleAttributeOperand.browsePath without considering the SimpleAttributeOperand.typeDefinitionId . Each InstanceDeclaration
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model6.4.1 GeneralGeneral This document defines standard EventTypes . They are represented in the AddressSpace as ObjectTypes . The EventTypes are already defined in OPC 10000-3 . The following subclauses specify their representation
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model8.2.6 ObjectTypesindirectly references the BaseEventType defined in 6.4.2 , which is the base type of all EventTypes . Thereby it is the entry point for all EventTypes provided by the Server ... required that the Server expose all its EventTypes , so a client can usefully subscribe to Events . The " ObjectTypes " Object is formally defined in Table 104 . Table 104 - ObjectTypes
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model8.2.10 EventTypesEventTypes This standard Object Node is the browse entry point for EventType Nodes . Figure 7 illustrates the structure beneath this Node showing some of the standard EventTypes defined in Clause ... Only Organizes References are used to relate Objects and ObjectTypes to the " EventTypes " standard Object . The " EventTypes " Object shall not reference any other NodeClasses . Figure
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information ModelA.1 Overviewmade while modelling the Server Object . General DataTypes , VariableTypes and ObjectTypes such as the EventTypes described in this standard are not taken into account
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionsnoted in this clause. To ensure a Client is always informed, the three special EventTypes ( RefreshEndEventType , RefreshStartEventType and RefreshRequiredEventType ) ignore the Event content filtering associated with a Subscription and will
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.1 Generaldescribes the AlarmConditionType, its sub-types and where it is in the hierarchy of Event Types . Figure 14 - AlarmConditionType Hierarchy Model
-
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs5.2.3.1 Overviewcomponents consist of a set of References to the Object instances of StateTypes , TransitionTypes , EventTypes and the Methods that collectively define the Program FiniteStateMachine. Figure 5 - Program FSM References Figure
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsMethods cause or trigger the specified transitions. The transition effects are the specified EventTypes which notify the Client of Program activity. Table A.1 - DomainDownload states No. Transition name Cause From
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsA.2.5.1 GeneralA.2.5.1 General A ProgramTransitionEventType is specified for each of the DomainDownload Program transitions. The EventTypes trigger a specific Event notification to the Client when the associated state transition occurs
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsA.2.6.2 DomainDownloadTypeportions of the DomainDownloadType model. In each figure, the referenced tates, Methods , transitions, and EventTypes are identified for one or two state transitions. Figure A.4 - Ready To Running model Figure
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Accessstream of Events each Event can have a different list of fields. EventTypes are defined in a hierarchical manner, where each EventType inherits fields from its parent type ... Historian that stores Events , shall be configurable to store all mandatory fields for any EventTypes that it historizes. If it receives for storage an EventType that it does not support
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical AccessAttribute Value BrowseName HistoricalEventConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule HasComponent Object EventTypes -- FolderType Mandatory HasProperty Variable StartOfArchive UtcTime PropertyType Optional HasProperty Variable StartOfOnlineArchive UtcTime PropertyType Optional HasProperty ... Variable SortByEventFields SimpleAttributeOperand[] PropertyType Optional ConformanceUnits Historical Access Events EventTypes is an entry point to browse to all EventTypes that can be stored by the Historian . For all EventTypes listed
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.2.1 Simple state machineform of specifying Methods that have to be called and effects in form of EventTypes of Events that are generated. However, the defined infrastructure allows extending this to support additional
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.15 HasEffectwill be effected when the Transition is triggered. In this specification we only define EventTypes as Effects . However, the ReferenceType is not restricted to point to EventTypes . The SourceNode
-
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model4.1 Overviewexamples of LogObjects and possible Client uses and Server implementations. This specification defines ObjectTypes , EventTypes , ConditionClass and instances (see Figure 2 ). Not all of the illustrated types/instances are required
-
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Modelstandard EventType ( see OPC 10000-3 , OPC 10000-5 and OPC 10000-9 EventTypes ) Figure 6 illustrates the event fields that are mapped to the LogRecordStructure . Any Object that ... Reference to one of these EventTypes shall generate LogRecords in the LogObject related to the defined BaseLogEventType. Figure 6 - BaseLogEventType Additional EventTypes can be defined as needed for specific
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model8.1 OverviewOverview OPC UA FX extends the Standard EventType hierarchy by several EventTypes defined in this clause. Figure 50 informally describes the hierarchy of these EventTypes . Figure