User:Felser/sandbox

= Selected templates =
 * user:felser/Profisafe


 * https://en.wikipedia.org/wiki/Template:Lowercase_title
 * https://en.wikipedia.org/wiki/Wikipedia:Citing_sources


 * https://en.wikipedia.org/wiki/Template:Infobox_technology_standard


 * Doi as a link: 10.1109/JPROC.2005.849720

https://www.incase2seas.eu/s/O6_PROFIenergy_Saving_Report_final_HiRes.pdf

= Actual Projects =
 * Draft:Omlox to be published soon
 * User:Felser/Profisafe New project just startet

Make reference
IEC Standards:

PI documents:

Books:

Mögliche Erweiterungen
Outline of automation

Process_automation_system

https://ieeexplore.ieee.org/xpl/aboutJournal.jsp?punumber=9424


 * OPC Foundation
 * ETSI
 * UWB Alliance


 * https://secureservercdn.net/45.40.150.47/ebt.244.myftpupload.com/wp-content/uploads/2021/01/UWBA-and-omlox-Formalize-Liaison-Final-Web.pdf
 * https://secureservercdn.net/45.40.150.47/ebt.244.myftpupload.com/wp-content/uploads/2021/01/UWBA-and-omlox-Formalize-Liaison-Final-Web.pdf

Basics:



Organisation:

Applications:

Others:
 * https://www.automationworld.com/process/iiot/article/21307274/pi-north-america-find-yourself-with-a-realtime-location-system
 * https://processandcontrolmag.co.uk/update-on-omlox-the-worlds-first-positioning-standard-for-industry/
 * https://assetverificationtagging.com/omlox-is-the-worlds-first-open-locating-standard/
 * https://www.processindustryinformer.com/omlox-industrial-location-standard-takes-off
 * https://profinews.com/2022/06/omlox-news-wrap-up-lots-to-announce/

= Ethernet-APL =
 * Advanced Physical Layer der aktuelle Eintrag
 * Ethernet-APL (noch) nicht definiert
 * Ethernet APL Weiterleitung auf Eintrag

Erweiterungen

 * Link to APL Website: add in further reading or references (same applies to landing pages of standard organizations or industry partners)
 * Reference to further articles, e.g. Process, etc.
 * Official graphics by APL project (e.g. for ISO OSI, topologies, etc.) (Copyright!!!)
 * Explaining APL topologies (e.g. APL components like switches, etc.)



Port profile specifications

 * Conformance Test Specification: add to the chapter “port profiles”

Use cases

 * Benefits? E.g. adding some use cases in comparison to traditional technologies like fieldbus or 4-20mA + HART

Organizational structure

 * APL Project (4 SDOs + 12 Industry Partners): explaining the organizational structure how Ethernet-APL is steered
 * Roadmap? E.g. finalization of all specifications? Availability of products?

= PROFINET =

See actual version: Profinet

https://en.wikipedia.org/wiki/Template:Infobox_networking_protocol

https://en.wikipedia.org/wiki/Template:Infobox_fieldbus_protocol

Link to OPC UA with PN

Overview
Profinet implements the interfacing to peripherals. It defines the communication with field connected peripheral devices. Its basis is a cascading real-time concept. Profinet defines the entire data exchange between controllers (called "IO-Controllers") and the devices (called "IO-Devices"), as well as parameter setting and diagnosis. IO-Controllers are typically a PLC, DCS, or IPC; whereas IO-Devices can be varied: I/O blocks, drives, sensors, or actuators. The Profinet protocol is designed for the fast data exchange between Ethernet-based field devices and follows the provider-consumer model. Field devices in a subordinate Profibus line can be integrated in the Profinet system seamlessly via an IO-Proxy (representative of a subordinate bus system).

https://profinetuniversity.com/category/profinet-features/

A device developer can implement Pprofinet with any commercially available Ethernet controller. It is well-suited for the data exchange with bus cycle times of a few ms. The configuration of an IO-System is similar to Profibus.

Features
Fieldbuses are designed with different sets of features and performances to fullfill the requirements of different application fields as listed in the table below.

In the table below the importance of the different requirements for an application field is indicated.

It is difficult to make a general comparison of fieldbus performance because of fundamental differences in data transfer methodology. In the comparison table below it is simply noted if the fieldbus in question typically supports data update cycles of 1 millisecond or faster.

Bus power
Is it possible to transmit over a two wire cable not only the data, but also the power for the operation of the field device? For Ethernet based fieldbuses Ethernet APL is here a possible solution.

System and media redundancy
High availability is one of the most important requirements in industrial automation. The availability of an automation system can be increased by adding redundancy for critical elements like the fieldbus. A distinction can be made between system and media redundancy.


 * With system redundancy controllers and devices can be dublicated to increase the availability of the system. Does the fieldbus support the adressing and switchover mechanisme for redundant devices?


 * With media redundancy the transmission media (e.g. the cable) is dublicated or used in a ring topology to increase the availability. Does the fieldbus support redundant medias?

For Ethernet based fieldbusses exist the standard IEC 62439 with a selection of media redundancy protocols. Most of these redundancy protocols can be combined with most of the fieldbus protocols.
 * High-availability Seamless Redundancy (HSR)
 * Media Redundancy Protocol (MRP)
 * Parallel Redundancy Protocol (PRP)
 * Cross-network Redundancy Protocol (CRP)
 * Beacon Redundancy Protocol (BRP)

Synchronization
Devicenet Bus power => 4 wire solution! https://literature.rockwellautomation.com/idc/groups/literature/documents/um/dnet-um072_-en-p.pdf

Fieldbus for building automation
https://www.auto.tuwien.ac.at/~gneugsch/procieee-csbac.pdf

PROCEEDINGS OF THE IEEE, VOL. 93, NO. 6, JUNE 2005

Communication Systems for BuildingAutomation and Control WOLFGANG KASTNER, GEORG NEUGSCHWANDTNER, STEFAN SOUCEK,ANDH. MICHAEL NEWMAN

Figure 2
 * Management level - Management network
 * Automation Level - Automation Network
 * Field Level - Field network

The one and only fieldbus
Despite each technology sharing the generic name of fieldbus the various fieldbus are not readily interchangeable. The differences between them are so profound that they cannot be easily connected to each other. To understand the differences among fieldbus standards, it is necessary to understand how fieldbus networks are designed. With reference to the OSI model, fieldbus standards are determined by the physical media of the cabling, and layers one, two and seven of the reference model.

For each technology the physical medium and the physical layer standards fully describe, in detail, the implementation of bit timing, synchronization, encoding/decoding, band rate, bus length and the physical connection of the transceiver to the communication wires. The data link layer standard is responsible for fully specifying how messages are assembled ready for transmission by the physical layer, error handling, message-filtering and bus arbitration and how these standards are to be implemented in hardware. The application layer standard, in general defines how the data communication layers are interfaced to the application that wishes to communicate. It describes message specifications, network management implementations and response to the request from the application of services. Layers three to six are not described in fieldbus standards.

CC-Link
"Control and Communications Link", or CC-Link for short, was designed by Mitsubishi Electric in 1996 as a proprietary fieldbus network to link their own plant automation products. Due to increasing customer demand, CC-Link was launched in 1999 as an open network. "Open" means that the protocols for data transmission are available to any company that wishes to develop its own interfaces. To ensure that network technology in an open environment is constantly being developed and disseminated as an efficient solution for industrial applications, the CC-Link Partner Association (CLPA) was founded.

APL
Two wire fieldbus is back again...

https://www.profibus.com/download/apl-white-paper/

Standartisation
65C/1058/INF "Fieldbus specifications and Profiles - Type 28 elements and CPF 22 (AUTBUS)"

Although fieldbus technology has been around since 1988, with the completion of the ISA S50.02 standard, the development of the international standard took many years. In 1999, the IEC SC65C/WG6 standards committee met to resolve difference in the draft IEC fieldbus standard. The result of this meeting was the initial form of the IEC 61158 standard with eight different protocol sets called "Types".

This form of standard was first developed for the European Common Market, concentrates less on commonality, and achieves its primary purpose&mdash;elimination of restraint of trade between nations. Issues of commonality are now left to the international consortia that support each of the fieldbus standard types. Almost as soon as it was approved, the IEC standards development work ceased and the committee was dissolved. A new IEC committee SC65C/MT-9 was formed to resolve the conflicts in form and substance within the more than 4000 pages of IEC 61158. The work on the above protocol types is substantially complete. New protocols, such as for safety fieldbuses or real-time Ethernet fieldbuses are being accepted into the definition of the international fieldbus standard during a typical 5-year maintenance cycle. In the 2008 version of the standard, the fieldbus types are reorganized into Communication Profile Families (CPFs).

Both Foundation Fieldbus and Profibus technologies are now commonly implemented within the process control field, both for new developments and major refits.

Process Fieldbus vs. device networks
Requirements of Fieldbus networks for process automation applications (flowmeters, pressure transmitters, and other measurement devices and control valves in industries such as hydrocarbon processing and power generation) are different from the requirements of Fieldbus networks found in discrete manufacturing applications such as automotive manufacturing, where large numbers of discrete sensors are used including motion sensors, position sensors, and so on. Discrete Fieldbus networks are often referred to as "device networks".

Ethernet and Fieldbus
Recently a number of Ethernet-based industrial communication systems have been established, most of them with extensions for real-time communication. These have the potential to replace the traditional fieldbuses in the long term.

Here is a partial list of the new Ethernet-based industrial communication systems:


 * AFDX
 * EtherCAT
 * EtherNet/IP
 * Ethernet Powerlink
 * FOUNDATION HSE
 * BACnet
 * PROFINET
 * SafetyNET p
 * SERCOS III
 * TTEthernet
 * VARAN
 * RAPIEnet
 * HD-PLC

For details, see the article on Industrial Ethernet.