<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: RS485 Cables - Why you need 3 wires for 2 (two) wire RS485</title>
	<atom:link href="http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485/feed" rel="self" type="application/rss+xml" />
	<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485</link>
	<description>Resources and News for industrial automation</description>
	<pubDate>Sat, 05 Jul 2008 18:20:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Andy Despres</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-139</link>
		<dc:creator>Andy Despres</dc:creator>
		<pubDate>Wed, 11 Jun 2008 20:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-139</guid>
		<description>Wow, a lot of information on RS-485.
Still confused as to what to do -
Do I tie the Chassis of the Transmitter device's ground terminal specifically for RS-485 to BOTH the 12V power supply negative or ground, and the Shield Terminal located on each of the the 485 Devices? Each device can be connected in Star/Home run or daisy chain with termination at the end of each run (1 for Daisy, 2 for 2 device star, not sure about 3 in star connect...)
What is a foolproof way to ensure there are no issues?
I heard a rumor that if this is done that it pulls the floating RS-485 signal to a common ground.

Exceptions??: The ground's of each the send device can't always be tied together, as they may be on separate electrical systems entirely. But in this system, each recieve device is usually tied to the send device so this isn't as much of an issue, they are treated like 2 separate systems. However, When they are connected as in a network A and network B, it is best to have a autmoatic switch to toggle which device they are connected to at any given time, and the switch should be grounded how? TO both systems?. To one system? Still confused...</description>
		<content:encoded><![CDATA[<p>Wow, a lot of information on RS-485.<br />
Still confused as to what to do -<br />
Do I tie the Chassis of the Transmitter device&#8217;s ground terminal specifically for RS-485 to BOTH the 12V power supply negative or ground, and the Shield Terminal located on each of the the 485 Devices? Each device can be connected in Star/Home run or daisy chain with termination at the end of each run (1 for Daisy, 2 for 2 device star, not sure about 3 in star connect&#8230;)<br />
What is a foolproof way to ensure there are no issues?<br />
I heard a rumor that if this is done that it pulls the floating RS-485 signal to a common ground.</p>
<p>Exceptions??: The ground&#8217;s of each the send device can&#8217;t always be tied together, as they may be on separate electrical systems entirely. But in this system, each recieve device is usually tied to the send device so this isn&#8217;t as much of an issue, they are treated like 2 separate systems. However, When they are connected as in a network A and network B, it is best to have a autmoatic switch to toggle which device they are connected to at any given time, and the switch should be grounded how? TO both systems?. To one system? Still confused&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-131</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 01 May 2008 14:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-131</guid>
		<description>Hi guys. This is a great discussion, and I hope one of you (or many!) might be able to help me with a problem I have with a 485 deployment.

I am trying to remote a single serial sensor (232) about 100 meters from a PC. For this purpose, I purchased two 232/485 converters. The PC's serial port is connected to one, which is connected via 3 wires (A, B and Ground) to the other (and out comes the 232 to the sensor).

I am also passing power to the remote converter and sensor on the same cable that caries the signal (4 wires in total, 3   one 5v supply).

The problem is, that this setup "basically" works. Meaning, it can be up for an entire day, but at some time it will fail. Sometimes a simple power cycling (off/on) will restore communications, and sometimes it will not. Sometimes I have no idea why, it just comes back on! Then, often, it stays off for hours. I really don't get it.

What might be wrong? This is the first time I am using 485.

Might it be a problem to pass power along with the signal? Maybe the fact that the ground of the power is common to the ground of the signal? (but anyway they are shorted in the converter box so I don't see how it might mater).

Help!

Thanks guys.

PS - Ah yes, the in-built terminators on the converters are enabled.
PPS - I have not connected the shielding of the 485 cable to ground
PPPS - I am using regular 4 core shielded wire, not twisted...</description>
		<content:encoded><![CDATA[<p>Hi guys. This is a great discussion, and I hope one of you (or many!) might be able to help me with a problem I have with a 485 deployment.</p>
<p>I am trying to remote a single serial sensor (232) about 100 meters from a PC. For this purpose, I purchased two 232/485 converters. The PC&#8217;s serial port is connected to one, which is connected via 3 wires (A, B and Ground) to the other (and out comes the 232 to the sensor).</p>
<p>I am also passing power to the remote converter and sensor on the same cable that caries the signal (4 wires in total, 3   one 5v supply).</p>
<p>The problem is, that this setup &#8220;basically&#8221; works. Meaning, it can be up for an entire day, but at some time it will fail. Sometimes a simple power cycling (off/on) will restore communications, and sometimes it will not. Sometimes I have no idea why, it just comes back on! Then, often, it stays off for hours. I really don&#8217;t get it.</p>
<p>What might be wrong? This is the first time I am using 485.</p>
<p>Might it be a problem to pass power along with the signal? Maybe the fact that the ground of the power is common to the ground of the signal? (but anyway they are shorted in the converter box so I don&#8217;t see how it might mater).</p>
<p>Help!</p>
<p>Thanks guys.</p>
<p>PS - Ah yes, the in-built terminators on the converters are enabled.<br />
PPS - I have not connected the shielding of the 485 cable to ground<br />
PPPS - I am using regular 4 core shielded wire, not twisted&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Vaughn</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-129</link>
		<dc:creator>Rick Vaughn</dc:creator>
		<pubDate>Thu, 24 Apr 2008 15:08:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-129</guid>
		<description>Great information by everyone! I manage several thousand RS-485 devices in an oil refinery setting (control for Valves, pumps, and alarms). Our original vendor (in 1990) installed the networks without the 3rd wire for ground. I can tell you from experience, ALWAYS install a ground wire or you will have problems. But what if you don't have a 3rd wire and can't retrofit and existing installation? I use isolating repeaters and this has solved my grounding problems. Make sure the repeater is "isolating". These can be purchased from most vendors (www.bb-elec.com, www.rs485.com, black box, etc..). You must also bias the RS-485 lines (a-b). Remember, only bias the line at one point on the network. The isolating repeaters have a bias option via dip switch (typically, 4.7k resistors to  5v and GND). B&#38;B Electronics is a very good resource for RS-485 information "http://www.bb-elec.com/technical_library.asp".
Also, you do not need to add terminating resistors if your baud rate is 9600 or lower (any reflections are dampened out before the center-bit time at 9600 baud). Termination resistors will do more harm than good if your baud rate is low.</description>
		<content:encoded><![CDATA[<p>Great information by everyone! I manage several thousand RS-485 devices in an oil refinery setting (control for Valves, pumps, and alarms). Our original vendor (in 1990) installed the networks without the 3rd wire for ground. I can tell you from experience, ALWAYS install a ground wire or you will have problems. But what if you don&#8217;t have a 3rd wire and can&#8217;t retrofit and existing installation? I use isolating repeaters and this has solved my grounding problems. Make sure the repeater is &#8220;isolating&#8221;. These can be purchased from most vendors (www.bb-elec.com, <a href="http://www.rs485.com" rel="nofollow">http://www.rs485.com</a>, black box, etc..). You must also bias the RS-485 lines (a-b). Remember, only bias the line at one point on the network. The isolating repeaters have a bias option via dip switch (typically, 4.7k resistors to  5v and GND). B&amp;B Electronics is a very good resource for RS-485 information &#8220;http://www.bb-elec.com/technical_library.asp&#8221;.<br />
Also, you do not need to add terminating resistors if your baud rate is 9600 or lower (any reflections are dampened out before the center-bit time at 9600 baud). Termination resistors will do more harm than good if your baud rate is low.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-128</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Tue, 15 Apr 2008 19:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-128</guid>
		<description>I have been struggling with the 2- versus 3-wire, grounded versus ungrounded, shielded versus unshielded issue with RS485 wiring for 20 years.  Steven says pretty much the same as I have been saying for over 15 of those 20 (I was a slow learner).
Comments:
1) Shielding is always good. This can be proven theoretically and in practice. Double shielding is even better.  Single shields must be grounded at one end, double (insulated from each other) are grounded one at each end.  This prevents currents from flowing through the shield and inducing currents into the signal lines via the transfer impedance between the two.
2) Bigger may be better but there is a very serious law of diminishing returns as the gauge of the wire gets larger.  High frequencies are carried on the surface of a conductor and the more surface area the lower the impedance -- this is good.  18ga is overkill.  20ga is OK for very long runs, 22ga is good enough for pretty much every application.
3) There are RS485-specific cables out there.  They have a shield &#38; drain wire (ground at one end), a ground wire and a twisted pair for the signal.  Belden 3106A is a good example.

I wish I could get more people to understand that carrying a third wire between RS485 devices was necessary.  I wish everyone who implemented an RS485 device had put the third wire on the connector so you could connect to it.

Apropos PROFIBUS:  Profibus may be RS485, but the reason it works is because the purple cable and connector is EXACTLY DEFINED and full network performance is only achievable using EXACTLY THAT CABLE (and connector).  If you grab any old twisted pair cable use it to hook up your Profibus network, you deserve the problems you have.</description>
		<content:encoded><![CDATA[<p>I have been struggling with the 2- versus 3-wire, grounded versus ungrounded, shielded versus unshielded issue with RS485 wiring for 20 years.  Steven says pretty much the same as I have been saying for over 15 of those 20 (I was a slow learner).<br />
Comments:<br />
1) Shielding is always good. This can be proven theoretically and in practice. Double shielding is even better.  Single shields must be grounded at one end, double (insulated from each other) are grounded one at each end.  This prevents currents from flowing through the shield and inducing currents into the signal lines via the transfer impedance between the two.<br />
2) Bigger may be better but there is a very serious law of diminishing returns as the gauge of the wire gets larger.  High frequencies are carried on the surface of a conductor and the more surface area the lower the impedance &#8212; this is good.  18ga is overkill.  20ga is OK for very long runs, 22ga is good enough for pretty much every application.<br />
3) There are RS485-specific cables out there.  They have a shield &amp; drain wire (ground at one end), a ground wire and a twisted pair for the signal.  Belden 3106A is a good example.</p>
<p>I wish I could get more people to understand that carrying a third wire between RS485 devices was necessary.  I wish everyone who implemented an RS485 device had put the third wire on the connector so you could connect to it.</p>
<p>Apropos PROFIBUS:  Profibus may be RS485, but the reason it works is because the purple cable and connector is EXACTLY DEFINED and full network performance is only achievable using EXACTLY THAT CABLE (and connector).  If you grab any old twisted pair cable use it to hook up your Profibus network, you deserve the problems you have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Andrews</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-122</link>
		<dc:creator>Trevor Andrews</dc:creator>
		<pubDate>Fri, 11 Apr 2008 17:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-122</guid>
		<description>Hi All,

I agree with Douglas, a third wire is not always necessary.
As long as the difference in ground potential between all the devices, including noise, is within the common mode range for TIA485 specification then it should work without a ground.
In this situation is side A more positive than B or vice versa, this is what is meant by differential signals.
This common mode range of TIA485 was mentioned early in the article, -7 volts to  12 volts.
If this is exceeded in the system than one or more isolation devices will be needed.
Though personally I would always use a ground.

Biasing resistors, not to be confused with terminating resistors, only need to be small enough so that noise on the signal line does not get through the receiver, at least 200mV.
This has become confusing over time as the original specification required the receiver chips to have a defined input resistance which means that there is always going to be current flowing into the input pins. This limited a bus to 16 devices owing to the drive available from the driver chips.
Since then there has been quarter power, eighth power and even sixteenth power devices, so resistors for biasing with early devices are now too low in value to work properly in large systems, the driver will become overloaded. This means that later systems will have higher value resistors, and can lead to providing insufficient bias for older chips allowing noise through the receiver and affecting the integrity of the communications.


Trevor</description>
		<content:encoded><![CDATA[<p>Hi All,</p>
<p>I agree with Douglas, a third wire is not always necessary.<br />
As long as the difference in ground potential between all the devices, including noise, is within the common mode range for TIA485 specification then it should work without a ground.<br />
In this situation is side A more positive than B or vice versa, this is what is meant by differential signals.<br />
This common mode range of TIA485 was mentioned early in the article, -7 volts to  12 volts.<br />
If this is exceeded in the system than one or more isolation devices will be needed.<br />
Though personally I would always use a ground.</p>
<p>Biasing resistors, not to be confused with terminating resistors, only need to be small enough so that noise on the signal line does not get through the receiver, at least 200mV.<br />
This has become confusing over time as the original specification required the receiver chips to have a defined input resistance which means that there is always going to be current flowing into the input pins. This limited a bus to 16 devices owing to the drive available from the driver chips.<br />
Since then there has been quarter power, eighth power and even sixteenth power devices, so resistors for biasing with early devices are now too low in value to work properly in large systems, the driver will become overloaded. This means that later systems will have higher value resistors, and can lead to providing insufficient bias for older chips allowing noise through the receiver and affecting the integrity of the communications.</p>
<p>Trevor</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mohsen Roshandel</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-121</link>
		<dc:creator>Mohsen Roshandel</dc:creator>
		<pubDate>Wed, 09 Apr 2008 08:28:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-121</guid>
		<description>Hello Wilfried.
I think that the receiver side isolator output is measured by its ground. therefore receiver device can read data correctly.but the third wire is required as shield to reduce the noise.</description>
		<content:encoded><![CDATA[<p>Hello Wilfried.<br />
I think that the receiver side isolator output is measured by its ground. therefore receiver device can read data correctly.but the third wire is required as shield to reduce the noise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pchipkin</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-117</link>
		<dc:creator>pchipkin</dc:creator>
		<pubDate>Thu, 27 Mar 2008 18:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-117</guid>
		<description>Hello Douglas,

Your point about Profibus is a good one but I think it re-inforces the the fact that rs485 requires 3 conductors.

The reason I say this is that Profibus is a standard that encapuslates RS485 and imposes other electrical requirments on it (like the isolation). Thus you get a bus with devices with a uniform electrical interface.

This is not the case with other RS485 applications. For example BACnet MSTP merely references the RS485 standard and does not impose other physical layer requirements.

I have to agree with Wilfried, viasing resistor calcs should not be required for field installations.</description>
		<content:encoded><![CDATA[<p>Hello Douglas,</p>
<p>Your point about Profibus is a good one but I think it re-inforces the the fact that rs485 requires 3 conductors.</p>
<p>The reason I say this is that Profibus is a standard that encapuslates RS485 and imposes other electrical requirments on it (like the isolation). Thus you get a bus with devices with a uniform electrical interface.</p>
<p>This is not the case with other RS485 applications. For example BACnet MSTP merely references the RS485 standard and does not impose other physical layer requirements.</p>
<p>I have to agree with Wilfried, viasing resistor calcs should not be required for field installations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wilfried Kramer</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-113</link>
		<dc:creator>Wilfried Kramer</dc:creator>
		<pubDate>Tue, 25 Mar 2008 13:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-113</guid>
		<description>Hello Douglas,

I'm sorry but basically you are wrong.
Voltages are not defined by themselves, they are only defined as the difference in the force of the electrical field. To measure a voltage you always need two points to put your probes on.

In RS485 one point is the signal wire A or B, and the second is the local ground of the receiver circuit. When you have an isolated device, the voltage of the isolated ground compared to the local ground of your device is undefined. This is especially true for the voltage difference between the signals and the isolated ground, because the signals are generated in respect to the local (isolated?) ground of the *transmitter* circuit. When these two grounds are completely isolated, there is no guarantee the receiver understands the data. It often happens the difference is too big. One proof of that is the real-world experience, transmissions become successful when you just add the ground line.

Biasing resistors do not really help, because for the purpose you describe you have to attach them to *every* device connected to the bus. This requires a recalculation of their values every time you add or remove a device from the bus.
(fact: calculation of resistors is not done by average customers.)
And in fact in this way you use the data lines to clear all voltage differences between the isolated grounds of the devices. At least you connect them via the resistors and the Data- line, which is pull-downed.
Even without bias resistors there may be some kind of parasitic connection between the data lines and the receivers ground, which also clears the differences between isolated components. That may also be the reason why in many applications the communication is fine with only two wires.

I agree, when using bias resistors as you describe it, there is only a reasonable current when a new isolated device is attached to the network. Later the isolated ground planes share the same electric potential, and there are only very small currents, if any.

By the way, even maxim-ic says the ground wire is required.</description>
		<content:encoded><![CDATA[<p>Hello Douglas,</p>
<p>I&#8217;m sorry but basically you are wrong.<br />
Voltages are not defined by themselves, they are only defined as the difference in the force of the electrical field. To measure a voltage you always need two points to put your probes on.</p>
<p>In RS485 one point is the signal wire A or B, and the second is the local ground of the receiver circuit. When you have an isolated device, the voltage of the isolated ground compared to the local ground of your device is undefined. This is especially true for the voltage difference between the signals and the isolated ground, because the signals are generated in respect to the local (isolated?) ground of the *transmitter* circuit. When these two grounds are completely isolated, there is no guarantee the receiver understands the data. It often happens the difference is too big. One proof of that is the real-world experience, transmissions become successful when you just add the ground line.</p>
<p>Biasing resistors do not really help, because for the purpose you describe you have to attach them to *every* device connected to the bus. This requires a recalculation of their values every time you add or remove a device from the bus.<br />
(fact: calculation of resistors is not done by average customers.)<br />
And in fact in this way you use the data lines to clear all voltage differences between the isolated grounds of the devices. At least you connect them via the resistors and the Data- line, which is pull-downed.<br />
Even without bias resistors there may be some kind of parasitic connection between the data lines and the receivers ground, which also clears the differences between isolated components. That may also be the reason why in many applications the communication is fine with only two wires.</p>
<p>I agree, when using bias resistors as you describe it, there is only a reasonable current when a new isolated device is attached to the network. Later the isolated ground planes share the same electric potential, and there are only very small currents, if any.</p>
<p>By the way, even maxim-ic says the ground wire is required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Forst</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-95</link>
		<dc:creator>Douglas Forst</dc:creator>
		<pubDate>Tue, 18 Mar 2008 20:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-95</guid>
		<description>RS485 is a 2 wire network if done right. Profibus is a typical example of a true 2 wire RS485 system. The secret to trouble free RS485 is to use isolated power supplies to run the RS485 transeiver. Low cost, low current, high speed non optical isolators are now available from Analog Devices (the ADUM1300 series) and simple to implement power supply isolators are also available from Maxim (MAX253 &#38; MAX845). Combining these parts with any standard RS485 transeiver builds you a fully isolated interface that truely needs only 2 wires. You must provide biasing resistors with this setup to center the RS485 signals within the isolated interface common mode range. A sample of an isolated interface can be found in the booklet "The rapid way to Profibus" or I can send you as sample circuit if you are interested.</description>
		<content:encoded><![CDATA[<p>RS485 is a 2 wire network if done right. Profibus is a typical example of a true 2 wire RS485 system. The secret to trouble free RS485 is to use isolated power supplies to run the RS485 transeiver. Low cost, low current, high speed non optical isolators are now available from Analog Devices (the ADUM1300 series) and simple to implement power supply isolators are also available from Maxim (MAX253 &amp; MAX845). Combining these parts with any standard RS485 transeiver builds you a fully isolated interface that truely needs only 2 wires. You must provide biasing resistors with this setup to center the RS485 signals within the isolated interface common mode range. A sample of an isolated interface can be found in the booklet &#8220;The rapid way to Profibus&#8221; or I can send you as sample circuit if you are interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: malonic</title>
		<link>http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-71</link>
		<dc:creator>malonic</dc:creator>
		<pubDate>Wed, 12 Sep 2007 05:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipkin.com/articles/rs485-cables-why-you-need-3-wires-for-2-two-wire-rs485#comment-71</guid>
		<description>thank you.</description>
		<content:encoded><![CDATA[<p>thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
