PROFIBUS | ||
---|---|---|
Protocol Information | ||
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) | |
Website | www.profibus.com |
PROFIBUS (Process Field Bus) is a standard for field bus communication in automation technology and was first promoted in 1989 by BMBF (German department of education and research). It should not be confused with the PROFINET standard for Industrial Ethernet.
Contents |
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, member companies agreed to support a common technical concept for production (i.e discrete or factory automation) 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. Profibus FMS is used for (non deterministic) communication of data between Profibus Masters. Profibus DP is a protocol made for (deterministic) communication between Profibus masters and their remote I/O slaves.
There are two variations of PROFIBUS in use today; the most commonly used PROFIBUS DP, and the lesser used, application specific, PROFIBUS PA:
In excess of 30 million PROFIBUS nodes were installed by the end of 2009. 5 million of these are in the process industries.
PROFIBUS Protocol (OSI reference model)
OSI-Layer | PROFIBUS | ||||
---|---|---|---|---|---|
7 | Application | DPV0 | DPV1 | DPV2 | Management |
6 | Presentation | -- | |||
5 | Session | ||||
4 | Transport | ||||
3 | Network | ||||
2 | Data Link | FDL | |||
1 | Physical | EIA-485 | Optical | MBP |
To utilize these functions, various service levels of the DP protocol were defined:
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
SD1 | DA | SA | FC | FCS | ED |
Variable length data:
SD2 = 0x68
SD2 | LE | LEr | SD2 | DA | SA | FC | DSAP | SSAP | PDU | FCS | ED |
Fixed length data:
SD3 = 0xA2
SD3 | DA | SA | FC | PDU | FCS | ED |
Token:
SD4 = 0xDC
SD4 | DA | SA | ED |
Brief acknowledgement:
SC = 0xE5
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
SAP (Decimal) | SERVICE |
---|---|
Default 0 | Cyclical Data Exchange (Write_Read_Data) |
54 | Master-to-Master SAP (M-M Communication) |
55 | Change Station Address (Set_Slave_Add) |
56 | Read Inputs (Rd_Inp) |
57 | Read Outputs (Rd_Outp) |
58 | Control Commands to a DP Slave (Global_Control) |
59 | Read Configuration Data (Get_Cfg) |
60 | Read Diagnostic Data (Slave_Diagnosis) |
61 | Send Parameterization Data (Set_Prm) |
62 | Check Configuration Data (Chk_Cfg) |
Note: SAP55 is optional and may be disabled if the slave doesn't provide non-volatile storage memory for the station address.
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).
Three different methods are specified for the bit-transmission layer:
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.
Profiles are pre-defined configurations of the functions and features available from PROFIBUS for use in specific devices or applications. They are specified by PI working groups and published by PI. Profiles are important for openness, interoperability and interchangeability, so that the end user can be sure that similar equipments from different vendors perform in a standardised way. User choice also encourages competition that drives vendors towards enhanced performance and lower costs.
There are PROFIBUS profiles for Encoders, Laboratory instruments, Intelligent Pumps, Robots and Numerically Controlled machines, for example. Profiles also exist for applications such as using HART and wireless with PROFIBUS, and process automation devices via PROFIBUS PA. Other profiles have been specified for Motion Control (PROFIdrive) and Functional Safety (PROFIsafe).
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.
The PROFIBUS Nutzerorganisation e.V. (PROFIBUS User Organization, or PNO) was created in 1989. This group was composed mainly of manufacturers and users from Europe. In 1992, the first regional PROFIBUS organization was founded (PROFIBUS Schweiz in Switzerland). In the following years, additional Regional PROFIBUS & PROFINET Associations (RPAs) were added.
In 1995, all the RPAs joined together under the international umbrella association PROFIBUS & PROFINET International (PI). Today, PROFIBUS is represented by 25 RPAs around the world (including PNO) with over 1400 members, including most if not all major automation vendors and service suppliers, along with many end users.
|