Search

Scope: Core (OPC-10000-*) All specs

16 result(s) for End

OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.2.2 Generating intervals

read Historical Aggregates , OPC clients shall specify three time parameters: startTime (Start) endTime (End) ProcessingInterval (Int) The OPC Server shall use these three parameters to generate a sequence of time ... intervals are generated. Table 49 provides information on the intervals for each Start and End time combination. The range is defined to be |End - Start|. All Aggregates return a timestamp
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.26 End

End The End Aggregate defined in Table 74 retrieves the latest raw value within the interval, and returns that value and status with the timestamp at which that value occurs ... values are in the interval then the StatusCode is Bad_NoData . Table 74 - End Aggregate summary End Aggregate Characteristics Type Calculated Data Type Same as Source Use Bounds None Timestamp
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

1 Scope

requirements for UAFX. This release includes definitions for functional networking requirements, including Bridge Component , End Station Component , IA-station , and UAFX Station , and network services, including remote management, topology discovery ... synchronisation for Ethernet networks. Future releases will add additional requirements, including additional definitions for End Station Components and NETCONF-based remote management. Definitions for additional physical layer protocols such
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

3.1.9 IA-station

station material element or assembly composed of one or more End Station Components and zero or more Bridge Components
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.1 General

with this release, vendor-specific means are required for all networking-related End Station and Bridge Component configurations, including VLAN configuration, time synchronisation, and QoS. The engineering workflow described ... thus requiring Descriptors to be shared in both directions. The default networking configuration of End Station Component s defined in the application and QoS engineering phase
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.1 General

selection of functional networking features. This component model consists of Bridge Component (see 6.2 ), End Station Component (see 6.3 ), IA-station (see 6.4 ), and UAFX Station
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.3.1 Overview

Overview An End Station Component is the source or destination of network traffic
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.3.2 End Station Component feature selection

End Station Component feature selection An End Station Component may support the following features: Transmission and reception of C-VLAN tagged frames. NOTE A future release of this document will ... define additional End Station Component requirements
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.4.1 Overview

Overview IA-stations can be a simple End Station Component (see 6.3 ) acting as the source or destination for industrial data traffic. IA-stations may also include a Bridge Component ... More complex IA-stations incorporating several End Station Components and Bridge Components within one device can also be found in industrial automation (e.g., a Controller with multiple modules
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.4.2 IA-station requirements

station requirements An IA-station shall: comprise at least one conformant End Station Component as defined in 6.3 , support topology discovery as defined in clause 7.3 . An IA-station
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.2.2 NETCONF

components of a UAFX Station. Figure 16 shows a UAFX Station comprised of two End Station Components and one Bridge Component , all controlled by a single management entity. Figure
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.3.2.1 Overview

LLDP agents and their management in a UAFX Station consisting of a single End Station Component , an IA-station , and a UAFX Station with an End Station Component
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.3.2.2.2 Operational control parameters

systems. A UAFX Station shall support LLDP transmit mode (adminStatus enabledTxOnly) on an external End Station Component port and may support transmit and receive mode (adminStatus enabledRxTx) on that port
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.3.2.2.4.4 System Capabilities TLV

System Capabilities TLV A UAFX Station consisting of only one or more End Station Components shall set the system and enabled capabilities fields to Station Only ... transmitted LLDPDUs. A UAFX Station with at least one End Station Component and at least one Bridge Component shall set the system and enabled capabilities fields to Station Only
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.4.2.1.4 Examples of PTP in a UAFX Station

events). Figure 20 shows an example of a UAFX Station consisting of a single End Station Component supporting one gPTP domain. Figure 21 shows an example of a UAFX Station ... consisting of a single End Station Component supporting two gPTP domains. Each gPTP domain has an associated PTP End Instance , which connects via a PTP Port to an Ethernet port
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

7.4.2.1.5 Engineered time synchronisation spanning tree

Relay Instances (hops) between the Grandmaster PTP Instance and any given PTP End Instance is within the limit prescribed by an external sync tree management entity; Verify per PTP link