<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chipkin Automation Systems - Articles &#187; PROFIBUS</title>
	<atom:link href="http://www.chipkin.com/articles/category/profibus/feed" rel="self" type="application/rss+xml" />
	<link>http://www.chipkin.com/articles</link>
	<description>Resources and News for industrial automation</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:30:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Cable Specifications for RS485 Networks &#8211; Profibus</title>
		<link>http://www.chipkin.com/articles/cable-specifications-for-rs485-networks-profibus</link>
		<comments>http://www.chipkin.com/articles/cable-specifications-for-rs485-networks-profibus#comments</comments>
		<pubDate>Wed, 08 Oct 2008 23:47:08 +0000</pubDate>
		<dc:creator>pchipkin</dc:creator>
				<category><![CDATA[Cables]]></category>
		<category><![CDATA[PROFIBUS]]></category>
		<category><![CDATA[RS485]]></category>

		<guid isPermaLink="false">http://www.chipkin.com/articles/?p=181</guid>
		<description><![CDATA[The PROFIBUS standard defines two variations of the bus cable. However it is recommended to use cable Type A in all new installations. Type A is especially recommended for high transmission speeds (&#62;500 kBaud) and permits doubling of the network distance in comparison to Type B. Technical specification: Impedance: 35 up to 165 Ohm at [...]]]></description>
			<content:encoded><![CDATA[<p>The PROFIBUS standard defines two variations of the bus cable. However it is recommended to use cable Type A in all new installations.</p>
<p>Type A is especially recommended for high transmission speeds (&gt;500 kBaud) and permits doubling of the network distance in comparison to Type B.</p>
<p><strong>Technical specification:</strong></p>
<p>Impedance: 35 up to 165 Ohm at frequencies from 3 to 20 Mhz.</p>
<p>Cable capacity: &lt; 30 pF per meter.</p>
<p>Core diameter: &gt; 0,34 mm², corresponds to AWG 22.</p>
<p>Cable type: twisted pair cable. 1&#215;2 or 2&#215;2 or 1&#215;4 lines.</p>
<p>Resistance: &lt; 110 Ohm per km.</p>
<p>Signal attenuation: max. 9 dB over total length of line section.</p>
<p>Shielding: CU shielding braid or shielding braid and shielding foil</p>
<p>Max. Bus length: 200 m at 1500 kbit/s, up to 1,2 km at 93,75 kbit/s. Extendable by repeaters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chipkin.com/articles/cable-specifications-for-rs485-networks-profibus/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hilscher’s dual-port memory message interface</title>
		<link>http://www.chipkin.com/articles/hilscher%e2%80%99s-duel-port-memory-message-interface</link>
		<comments>http://www.chipkin.com/articles/hilscher%e2%80%99s-duel-port-memory-message-interface#comments</comments>
		<pubDate>Mon, 14 Jul 2008 07:59:24 +0000</pubDate>
		<dc:creator>pchipkin</dc:creator>
				<category><![CDATA[PROFIBUS]]></category>

		<guid isPermaLink="false">http://www.chipkin.com/articles/?p=164</guid>
		<description><![CDATA[The message that needs to be transmitted is a data structure containing instructions from the transmitter to the receiver. The message structure can be divided into three parts, message header (8 bytes), telegram header (8 bytes) and user data (247 bytes). These messages are used to transmit data from one task to another. For all [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">The message that needs to be transmitted is a data structure containing instructions from the transmitter to the receiver. The message structure can be divided into three parts, message header (8 bytes), telegram header (8 bytes) and user data (247 bytes). These messages are used to transmit data from one task to another. For all protocol tasks the structure stays the same, but some applications use the messages for parameter passing and these messages don’t have a telegram header but begins immediately with the data.</p>
<p class="MsoNormal">The two types of messages used are request messages and confirmation messages. The request message causes an action in a task and the confirmation message confirms the performing of that action or task (answer).</p>
<p class="MsoNormal">For the transmitter to send the message it needs to write it into the receiver’s mailbox and notify the receiver by inverting one of its mailbox bits. The receiver then reads the mail and releases the mailbox in response to the corresponding mail. Only one mailbox is used in each direction. The receiver of the message is thus responsible to quickly read the message in order to release the mailbox again for the next available message.</p>
<p class="MsoNormal">The messages that cannot immediately be transferred to the Host application are placed in a queue mechanism with a standard configuration of 31 available segments. The actual available segments can be read from the SegmentCount location inside the dual-port memory. If the available number of segments fall bellow a protocol dependent value, the device won’t be able to access messages from its mailbox. The Host application is thus responsible to read out its mailbox messages to ensure that no Host messages are in the queue witch will reduces the available segment count.</p>
<p class="MsoNormal"><strong>Synchronization of message delivery:</strong></p>
<p class="MsoNormal">The procedure chosen for message synchronization allows the Host to operate in interrupt mode as well as polling mode. The device can cause an interrupt to the Host application by writing into the interrupt capable handshake cell. The hardware has only one interrupt line for each handshake register, indicating different events. The event can be identified by reading the corresponding handshake register in the dual-port memory. The two reserved handshake registers in the duel-port memory are the DevFlags and HostFlags registers. The DevFlags register can only be written to by the Host application and read from by the device. The HostFlags register on the other hand can only be written to by the device and read from by the Host application.</p>
<p class="MsoNormal">Both these registers contain a command and acknowledgement bit. A command gets activated when the command and acknowledgement bit has opposite values and acknowledged when they have the same value. It is important to note that a new command can only be activated if the preceding command was acknowledged.</p>
<p class="MsoNormal">In polling mode the Host application monitors the difference between the command and acknowledgement flag bits. The Host application will then be able to send messages or received messages depending on the status of these bits.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chipkin.com/articles/hilscher%e2%80%99s-duel-port-memory-message-interface/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PROFIBUS The Field Bus Communication Standard</title>
		<link>http://www.chipkin.com/articles/profibus-the-field-bus-communication-standard</link>
		<comments>http://www.chipkin.com/articles/profibus-the-field-bus-communication-standard#comments</comments>
		<pubDate>Fri, 11 Jul 2008 08:17:38 +0000</pubDate>
		<dc:creator>pchipkin</dc:creator>
				<category><![CDATA[PROFIBUS]]></category>

		<guid isPermaLink="false">http://www.chipkin.com/articles/?p=163</guid>
		<description><![CDATA[PROFIBUS is the abbreviation for Process Field Bus and is the standard for field bus communication in automation technology. The PROFIBUS communication protocol was created in 1989 by a consortium of companies and institutions and promoted by the BMBF (german department of education and research). PROFIBUS has since become the most popular fieldbus in discreet [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">PROFIBUS is the abbreviation for Process Field Bus and is the standard for field bus communication in automation technology. The PROFIBUS communication protocol was created in 1989 by a consortium of companies and institutions and promoted by the BMBF (german department of education and research). PROFIBUS has since become the most popular fieldbus in discreet manufacturing and process control with over 20 million installed devices world wide.</p>
<p class="MsoNormal">
<p class="MsoNormal">PROFIBUS is divided into two variations, the more commonly used DP (Decentralized Peripheral) version that replaced the first complex communication protocol version FMS (Fieldbus Message Specification) in 1993 and the less commonly used PA (Process Automation) protocol version.</p>
<p class="MsoNormal">
<p class="MsoNormal">PROFIBUS DP is the high speed solution of PROFIBUS. It has been designed and optimized especially for communication between automation systems and decentralized devices. It can operate at data rates of up to 12Mbit/s over twisted pair cables or fiber optic links. The communication is via cyclic data traffic exclusively and each field device need to exchange its data with the control device (Master) within a given cycle time. Operation and monitoring tasks for a visualization device separate from the control device was not supported by this specification and appropriate function extensions were defined in 1997. The new extended version is referred to as PROVIBUS-DPV1 and is compatible with all earlier versions of the existing DP protocol. PROVIBUS-DPV1 also offers in addition to the cyclic DP communication services, an acyclic service for alarm messages, diagnostics and control of field devices.</p>
<p class="MsoNormal">
<p class="MsoNormal">PROFIBUS AP is used to monitor measuring equipment via a process control system. It also meets the two special requirements of process automation, an intrinsically safe transmission technique and field device power over bus cable. The disadvantage of this protocol is its slow data rate of only 31.25kbit/s. Weak current flow through the bus lines makes it intrinsically safe and ideal for use in explosion-hazardous areas.<span> </span></p>
<p class="MsoNormal">
<p class="MsoNormal" style="text-align: center;" align="center"><strong>The FROFIBUS protocol (OSI reference model)</strong></p>
<p class="MsoNormal">
<div>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0">
<tbody>
<tr>
<td style="padding: 0.75pt;" colspan="2">
<p class="MsoNormal" style="text-align: center;" align="center"><strong>OSI</strong><strong>-Layer</strong></p>
</td>
<td style="padding: 0.75pt;" colspan="5">
<p class="MsoNormal" style="text-align: center;" align="center"><strong>PROFIBUS</strong></p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">User Interface</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">DPV0</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">DPV1</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">DPV2</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">7</p>
</td>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Application</p>
</td>
<td style="padding: 0.75pt; background: #b3b3b3 none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" colspan="5" rowspan="5">
<p class="MsoNormal" style="text-align: center;" align="center">&#8211;</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">6</p>
</td>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Presentation</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">5</p>
</td>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Session</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">4</p>
</td>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Transport</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">3</p>
</td>
<td style="padding: 0.75pt; background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Network</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">2</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Data Link</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" colspan="5">
<p class="MsoNormal" style="text-align: center;" align="center">FDL</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">1</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Physical</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" colspan="2">
<p class="MsoNormal" style="text-align: center;" align="center">EIA-485</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
<p class="MsoNormal" style="text-align: center;" align="center">Optical</p>
</td>
<td style="padding: 0.75pt; background: aqua none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" colspan="2">
<p class="MsoNormal" style="text-align: center;" align="center">MBP</p>
</td>
</tr>
</tbody>
</table>
</div>
<p><strong>User Interface:</strong></p>
<p>For the User Interface of PROFIBUS various service levels were defined for the DP protocol:</p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span>·<span style="font-family: "> </span></span></span><!--[endif]-->DP-V0 provides the service for cyclic exchange of data and diagnosis.</p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span>·<span style="font-family: "> </span></span></span><!--[endif]-->DP-V1 provides the service for acyclic and cyclic exchange and alarm handling.</p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span>·<span style="font-family: "> </span></span></span><!--[endif]-->DP-V2 provides the service for isochronous mode data exchange broadcast (slave-to-slave communication).</p>
<p><strong>Data Link layer:</strong></p>
<p>The Field Bus Data Link Layer (FDL) work with a hybrid bus access protocol. It combines token passing with a master slave method. The token passing procedure guarantees that the bus access gets assigned to a specific master node for a defined time frame. In this time frame the master node can access the bus and request data from any master or slave device. After the time frame expires the current master node will pass the token to the next master node on the bus. This layer also includes the handling of data security and the transmission protocol of telegrams.</p>
<p><strong>Physical layer or bit-transmission layer:</strong></p>
<p>Three different methods are specified for the physical layer of FROFIBUS</p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span>·<span style="font-family: "> </span></span></span><!--[endif]-->Electrical wire transmission EIA-485, twisted wire pair with impedance of 150 ohms. Specified for Bit rates 9.6 kbit/s to 12Mbit/s. This transmission method is usually used with PROFIBUS DP. The cable length between repeaters is limited from 100 to 1200 m, depending on the bit rate.</p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span>·<span style="font-family: "> </span></span></span><!--[endif]--><span> </span>Fiber optical transmission uses, star-, bus- and ring topologies and the distance between repeaters can be up to 15 km.</p>
<p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span>·<span style="font-family: "> </span></span></span><!--[endif]-->With Manchester Bus Powered transmission technology the data and device power are fed through the same cable. The bit rate is a fixed 31.25 kbit/s. This technology was specifically developed for PROFIBUS PA.</p>
<p style="margin-left: 0.25in;">Other transmission mediums products like radio waves, sliding contacts etc. can be obtained from various manufacturers but this does not mean they conform to any standards.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chipkin.com/articles/profibus-the-field-bus-communication-standard/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

