Search

17 result(s) for Controllers

• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.3 Compute
  hardware platforms Note 1 to entry: Example Compute hardware platforms include edge gateways, Controllers , or blade servers in the cloud. Note 2 to entry: Compute examples include SCADA
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.4 Controller
  inputs, performs logic, and writes outputs in real-time. Note 2 to entry: Modern Controllers can also produce alarms, send emails, communicate with SCADA and HMI systems, and amongst themselves
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.6 Controller-to-Compute
  Controller-to-Compute interaction model involving Controllers exchanging data with Computes
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.7 Controller-to-Controller
  Controller-to-Controller interaction model involving Controllers exchanging data with one another
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.8 Controller-to-Device
  Controller-to-Device interaction model involving Controllers exchanging data with devices
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.3 Interaction Model
  typically implemented in a PLC or DCS controller. Today, Devices may be connected to Controllers and can be as simple as an inductive proximity switch or as complex ... many ways, but each category will include interactions unique to its use cases. Controllers and devices may have vastly different functions and roles; however, their functionality is modelled
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.4.3 Application engineering
  Engineer B may import additional Descriptors describing components used with their Controller or other Controllers to be connected. Engineer B then adds the Connection configuration needed to exchange the data ... design and commissioning Engineer A and Engineer B deploy their applications to their respective Controllers and deliver them to the site. Initial network address assignment is a precondition
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.4.4 Security configuration
  Security configuration Using a Security Provisioning Entity, the Security Administrator configures the Controllers for OPC UA security and rolls out the security policy required for the site per Controller
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.4.5 Network configuration
  Network configuration The Network Engineer commissions the Controllers with a hostname, DNS information, and an IP address or address acquisition mechanism such as DHCP. The Network Engineer may apply firmware
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.1 Controller-to-Controller communication
  from multiple vendors in today's modern plants. Successfully integrating products like PLCs, DCS controllers, or PAS applications from different vendors can require a great deal of effort. Industrial automation ... communication The UAFX specification addresses multi-controller environments, as shown in Figure 9 . The Controllers in this illustration may be an IPC with visualisation, a PLC, a DCS controller
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.3.2 HostName resolution using DNS
  related RFCs) in the establishment of a UAFX C onnection between two UAFX Controllers . Figure 2 - Client/server with DNS resolution Controller A, with ConnectionManager (CM), has a DNS client
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.4 Server announcement and discovery using mDNS
  Server announcement and discovery using mDNS To enable Clients to discover the UAFX Server , Controllers shall support an mDNS responder and include the defined UAFX capability in its mDNS announcements ... responses as defined in OPC 10000‑12 . Controllers are required to support a minimal mDNS responder and include the defined UAFX capability in its mDNS announcements and responses. Note This
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.2 Traffic Priority
  data with UAFX. Figure 5 shows an example of an application running on two Controllers using different priorities on a network. One priority carries OPC UA PubSub messages with
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.1 General
  clause illustrates the configuration and start-up of a single communication flow between two Controllers , i.e., data is only shared in one direction, requiring a single Descriptor describing this data ... exported from an engineering tool describing one of the Controllers . UAFX Applications will typically be sharing data in both directions between the Controllers, thus requiring Descriptors to be shared
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.2 Application and QoS engineering
  Controller. Next, Controls Engineers set up the Connection configurations needed for sharing data between Controllers . As a final step, Connection configurations are transferred to a ConnectionManager that establishes the Connections ... Controller A, Controller B's engineering tool contains the UAFX Information Model for both Controllers, including the configuration of both Controllers' AutomationComponent's PublisherCapabilities and SubscriberCapabilities, PriorityMappingTable , and IetfBaseNetworkInterfaces . With
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.3 Descriptor with configuration information
  next Controls Engineer. When a Connection needs to be defined between two Controllers , the two Controls Engineers may provide information about the communication interfaces to each other using a Descriptor
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  8.4 Example workflow for sharing a Descriptor in OfflineEngineering
  data is exchanged between Controller A and Controller B. It is assumed that the Controllers may be from different vendors or the same vendor. In Figure 23 , Descriptors are shared ... Descriptors by the engineering tools and downloaded together with the user programs into the Controllers . The yellow FunctionalEntity and Asset boxes represent the Information Model of the AutomationComponent