Profibus and User talk:61.213.94.203: Difference between pages

From Wikipedia, the free encyclopedia
(Difference between pages)
Content deleted Content added
SieBot (talk | contribs)
m robot Adding: it:PROFIBUS
 
blocked
 
Line 1: Line 1:
[[Image:Stop hand nuvola.svg|30px]] This is the '''only warning''' you will receive for your disruptive edits.<br />If you [[Wikipedia:Vandalism|vandalize]] Wikipedia again{{#if:List of shipwrecks in 2006|, as you did to [[:List of shipwrecks in 2006]]}}, you '''will''' be [[Wikipedia:Blocking policy|blocked]] from editing. {{#if:|{{{2}}}|}}<!-- Template:uw-vandalism4im -->
{{Infobox Fieldbus Protocol
:You have been blocked for a period of two weeks, as this IP address is being used to circumvent an already-applied block. [[User:Chase me ladies, I&#39;m the Cavalry|Chase me ladies, I&#39;m the Cavalry]] ([[User talk:Chase me ladies, I&#39;m the Cavalry|talk]]) 13:54, 12 October 2008 (UTC)
| Name = PROFIBUS
| Type_of_Network = Device Bus, Process Control
| Physical_Media = Twisted pair, fiber
| Network_Topology = Bus
| Device_Addressing = DIP Switch or hardware/software
| Governing_Body = PROFIBUS&PROFINET International (PI)
| URL = [http://www.profibus.com/ www.profibus.com]
}}

'''PROFIBUS''' (Process Field Bus) is a standard for field bus communication in automation technology and was first promoted (1989) by [[BMBF]] (German department of education and research). It should not be confused with the [[PROFINET]] standard for industrial Ethernet.

== Origin ==
The history of PROFIBUS goes back to a publicly promoted plan for an association started in Germany in 1987 and for which 21 companies and institutes devised a master project plan called "field bus". The goal was to implement and spread the use of a bit-serial field bus based on the basic requirements of the field device interfaces. For this purpose, respective company members agreed to support a common technical concept for production and process automation. First, the complex communication protocol Profibus FMS (Field bus Message Specification), which was tailored for demanding communication tasks, was specified. Subsequently in 1993, the specification for the simpler and thus considerably faster protocol PROFIBUS DP (Decentralized Peripherals) was completed. It replaced FMS.

== Use ==
There are two variations of PROFIBUS; the most commonly used DP, and the lesser used PA variations:
* '''PROFIBUS DP''' (Decentralized Peripherals) is used to operate sensors and actuators via a centralized controller in production technology. The many standard diagnostic options, in particular, are focused on here. Other areas of use include the connection of "distributed intelligence", i.e. the networking of multiple controllers to one another (similar to PROFIBUS FMS). Data rates up to 12 Mbit/s on twisted pair cables and/or fiber optics are possible.
* '''PROFIBUS PA''' (Process Automation) is used to monitor measuring equipment via a process control system in process engineering. This PROFIBUS variant is ideal for explosion-hazardous areas (Ex-zone 0 and 1). Here, a weak current flows through bus lines in an intrinsically safe circuit so that explosive sparks are not created, even if a malfunction occurs. The disadvantage of this variant is the slower data transmission rate of 31.25 kbit/s.
PROFIBUS is the only field bus that can be used in equal measure in production automation and process automation and has since become a global market leader. Worldwide, over 20 million PROFIBUS devices are in use (as of 2007).

== Technology ==
<center>
'''PROFIBUS Protocol (OSI reference model)'''
{| border="0" cellspacing="3"
|-----
! colspan="2" | OSI-Layer
! colspan="5" align="center" | PROFIBUS
|-----
| align="center" bgcolor="#ffff99" | 7
| align="center" bgcolor="#ffff99" | Application
| align="center" bgcolor="#ffcc99" |
| align="center" bgcolor="#ffcc99" | DPV0
| align="center" bgcolor="#ffcc99" | DPV1
| align="center" bgcolor="#ffcc99" | DPV2
| align="center" bgcolor="#ffcc99" |
| rowspan="7" align="center" bgcolor="#cccccc" | Management
|-----
| align="center" bgcolor="#ffff99" | 6
| align="center" bgcolor="#ffff99" | Presentation
| colspan="5" rowspan="4" align="center" bgcolor="#dddddd" | --
|-----
| align="center" bgcolor="#ffff99" | 5
| align="center" bgcolor="#ffff99" | Session
|-----
| align="center" bgcolor="#ffff99" | 4
| align="center" bgcolor="#ffff99" | Transport
|-----
| align="center" bgcolor="#ffff99" | 3
| align="center" bgcolor="#ffff99" | Network
|-----
| align="center" bgcolor="#ffff99" | 2
| align="center" bgcolor="#ffff99" | Data Link
| colspan="5" align="center" bgcolor="#ffcc99" | FDL
|-----
| align="center" bgcolor="#ffff99" | 1
| align="center" bgcolor="#ffff99" | Physical
| colspan="2" align="center" bgcolor="#ffcc99" | [[EIA-485]]
| align="center" bgcolor="#ffcc99" | Optical
| colspan="2" align="center" bgcolor="#ffcc99" | MBP
|}
<br />
</center>


=== Application layer ===
To utilize these functions, various service levels of the DP protocol were defined:
* DP-V0 for cyclic exchange of data and diagnosis
* DP-V1 for acyclic and cyclic data exchange and alarm handling
* DP-V2 for isochronous mode and data exchange broadcast (slave-to-slave communication)

=== Security layer ===
The security layer '''FDL''' (Field bus Data Link) works with a hybrid access method that combines token passing with a master-slave method. In a PROFIBUS DP network, the controllers or process control systems are the masters and the sensors and actuators are the slaves.


Various telegram types are used. They can be differentiated by their start delimiter (SD):

No data:
SD1 = 0x10
{| border = "1"
|bgcolor="#ffff99"|SD1
|bgcolor="#ffcc99"|DA
|bgcolor="#ffcc99"|SA
|bgcolor="#77ffff"|FC
|bgcolor="#ff7777"|FCS
|bgcolor="#ffff99"|ED
|}
Variable length data:

SD2 = 0x68

{| border = "1"
|bgcolor="#ffff99"|SD2||LE||LEr||bgcolor="#ffff99" |SD2
|bgcolor="#ffcc99"|DA
|bgcolor="#ffcc99"|SA
|bgcolor="#77ffff"|FC
||PDU
|bgcolor="#ff7777"|FCS
|bgcolor="#ffff99"|ED
|}
Fixed length data:

SD3 = 0xA2

{| border = "1"
|bgcolor="#ffff99"|SD3
|bgcolor="#ffcc99"|DA
|bgcolor="#ffcc99"|SA
|bgcolor="#77ffff"|FC
||PDU
|bgcolor="#ff7777"|FCS
|bgcolor="#ffff99"|ED
|}
Token:

SD4 = 0xDC

{| border = "1"
|bgcolor="#ffff99"|SD4
|bgcolor="#ffcc99"|DA
|bgcolor="#ffcc99"|SA
|}

Brief acknowledgement:

SC = 0xE5

{| border = "1"
|bgcolor="#ffff99"|SC
|}


SD: Start Delimiter

LE: Length of protocol data unit, (incl. DA,SA,FC,DSAP,SSAP)

LEr: Repetition of protocol data unit, (Hamming distance = 4)

FC: Function Code

DA: Destination Address

SA: Source Address


DSAP: Destination [[Service Access Point]]

SSAP: Source [[Service Access Point]]


PDU: Protocol Data Unit (protocol data)

FCS: Frame Checking Sequence

ED: End Delimiter (= 0x16 !)

The FCS is calculated by simply adding up the bytes within the specified length. An overflow is ignored here. Each byte is saved with an even parity and transferred asynchronously with a start and stop bit.
There may not be a pause between a stop bit and the following start bit when the bytes of a telegram are transmitted. The master signals the start of a new telegram with a SYN pause of at least 33 bits (logical "1" = bus idle).

=== Bit-transmission layer ===
Three different methods are specified for the bit-transmission layer:
* With electrical transmission pursuant to [[EIA-485]], twisted pair cables with a wave impedances of 150 ohms are used in a bus topology. Bit rates from 9.6 kbit/s to 12 Mbit/s can be used. The cable length between two repeaters is limited to 100 to 1200 m, depending on the bit rate used. This transmission method is primarily used with PROFIBUS DP.
* With optical transmission via fiber optics, star-, bus- and ring-topologies are used. The distance between the repeaters can be up to 15 km. The ring topology can also be executed redundantly.
* With MBP (Manchester Bus Powered) transmission technology, data and field bus power are fed through the same cable. The power can be reduced in such a way that use in explosion-hazardous environments is possible. The bus topology can be up to 1900 m long and permits branching to field devices (max. 60 m branches). The bit rate here is a fixed 31.25 kbit/s. This technology was specially established for use in process automation for PROFIBUS PA.

For data transfer via sliding contacts for mobile devices or optical or radio data transmission in open spaces, products from various manufacturers can be obtained, however they do not conform to any standard.

== Standardization ==
PROFIBUS was defined in 1991/1993 in DIN 19245, was then included in EN 50170 in 1996 and, since 1999, established in IEC 61158/IEC 61784.

== Organization ==
The PROFIBUS Nutzerorganisation e.V. (PROFIBUS User Organization) (PNO) was created in 1989. This group is comprised of manufacturers and users from Germany. In 1992, the first regional PROFIBUS organization was founded (PROFIBUS Schweiz in Switzerland). In the following years, additional RPAs (Regional PROFIBUS & PROFINET Associations) were added. Today, PROFIBUS is represented by 25 RPAs around the world. In 1995, all the RPAs joined together into the international umbrella association PROFIBUS & PROFINET International (PI).

== References ==
{{reflist}}
* [http://www.profibus.com/pall/meta/downloads/article/00454/] PROFIBUS system description

==External links==
* [http://www.profibus.com PROFIBUS & PROFINET International]
* [http://www.agilicom.fr/index2.html AGILiCOM - Profibus France]
* [http://www.rpingenieria.cl RP INGENIERIA - Profibus Chile]


[[Category:Automation]]
[[Category:Industrial computing]]
[[Category:Production and manufacturing]]

[[ca:Profibus]]
[[cs:Profibus]]
[[de:Profibus]]
[[es:Profibus]]
[[fr:Profibus]]
[[it:PROFIBUS]]
[[nl:Profibus]]
[[pl:Profibus]]
[[pt:Profibus]]
[[ru:PROFIBUS]]

Revision as of 13:54, 12 October 2008

This is the only warning you will receive for your disruptive edits.
If you vandalize Wikipedia again, as you did to List of shipwrecks in 2006, you will be blocked from editing.

You have been blocked for a period of two weeks, as this IP address is being used to circumvent an already-applied block. Chase me ladies, I'm the Cavalry (talk) 13:54, 12 October 2008 (UTC)