Previous in Forum: Instrumnt junction boxes with captive clams and screw   Next in Forum: Welding Work Effecting Skid Cable
Close
Close
Close
6 comments
Rate Comments: Nested
Active Contributor

Join Date: May 2011
Posts: 12

Ethernet vs Serial Communication

07/13/2011 1:24 PM

Hi all,

Hey i have got a basic doubt....

I am looking for basic difference (Physical not about protocols) between Ethernet communication (using RJ45) and serial communication (RS485, 232, etc.).

Also I want to know why Ethernet is not a type of serial communication as here also data will be transmitted in bits (though in a frame format) only. What makes the difference..?

Waiting for replies....

Regards,

Shyam

Register to Reply
Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.

Good Answers:

These comments received enough positive votes to make them "good answers".
Anonymous Poster #1
#1

Re: Ethernet vs Serial communication

07/13/2011 2:53 PM

Simplifying, what makes the big difference is that Ethernet uses biger and addressable data chunks plus continous negotiation so data verifying and resending if needed is done easier (regardless the distance that gives varied signal latencies) if that's what you ask. S.M.

Register to Reply
2
Guru
Engineering Fields - Electrical Engineering - Been there, done that. Engineering Fields - Control Engineering - New Member

Join Date: Dec 2008
Location: Long Island NY
Posts: 15600
Good Answers: 981
#2

Re: Ethernet vs Serial Communication

07/13/2011 7:12 PM

Ethernet is a type of serial communication. There are many differences between Ethernet and other serial protocols though. The voltage levels and cable impedances are different but the primary difference is that Ethernet is an intelligent communication while RS422, RS232 are not. Because of this intelligence, two units on an Ethernet network do not have to be directly connected to each other with a wire for communication to happen between them.

__________________
"Don't disturb my circles." translation of Archimedes last words
Register to Reply Good Answer (Score 2)
2
Power-User
Popular Science - Weaponology - New Member

Join Date: Jun 2011
Location: Berkeley, CA USA
Posts: 128
Good Answers: 4
#3

Re: Ethernet vs Serial Communication

07/14/2011 12:49 AM

basic difference (Physical not about protocols)

You can actually find RS232/485 with RJ45 connectors. The data rate on 232 and 485 tends to be below 1Mb/sec which allows for much lower impedance requirements on the cabling. The big differences between 232 and 485 is a Voltage signal level for 232 vs a current for 485. 232 is also point to point vs up to 32 devices on a single channel for 485. Good basic articles on 485 is http://en.wikipedia.org/wiki/EIA-485

and for 232 see http://en.wikipedia.org/wiki/Rs232

__________________
Working to end the use of carbon for energy
Register to Reply Good Answer (Score 2)
Guru

Join Date: Aug 2005
Location: Hemel Hempstead, UK
Posts: 5826
Good Answers: 322
#4
In reply to #3

Re: Ethernet vs Serial Communication

07/14/2011 6:01 AM

Voltage signal level for 232 vs a current for 485

I'd have to disagree there. the main difference between RS232 and RS422/RS485 is that RS232 uses single signal wires (one for Tx and one for Rx), whereas, RS 422/485 uses differential signalling.

__________________
If you spend all your time looking for people and things to complain about: trust me, you will find plenty to complain about.
Register to Reply Off Topic (Score 5)
Guru

Join Date: Dec 2010
Posts: 1686
Good Answers: 116
#5

Re: Ethernet vs Serial Communication

07/17/2011 6:57 PM

Posts #3 and #4 have got down to the physical differences between Ethernet and the other serial standards [Ethernet is definitely serial].

RS232 used positive and negative potentials on the transmit wire, relative to a common wire. Transmit levels were 7 to 30 volts, while the minimum receive level was 3 volts. Transmitters were short circuit proof basically by having a lot of series resistance (2kohm comes to mind). Because of the high source resistance, much higher than cable natural impedance, cable capacitance attenuated the signal and slowed the + to - transitions so much that even 9600 baud could be a problem over 10 metre run. The standard was meant for just one transmitter and one receiver on a run - no provision for isolating transmitter or multiple receiver loadings. It was designed for connecting to a telephone modem, with multiple hardware handshake wires as well as transmit and receive. For other purposes, it was total pain - unless all the handshakes were provided or fooled - even a simple direct connection would not work. To add to the trouble, connecting a wire to the same connector pin number at both ends was OK for computer to modem, but you had to have "cross-over" connection for computer to computer. Also, the standard did not define connectors, not even to the extent that modems had female or male connectors!

RS422 recognized that cable pairs carry AC signals with minimum attenuation and reflections (echos cause data errors) if driven and loaded at their characteristic impedance and required a 100 ohm line impedance. Transmitters were differential, essentially connecting one wire to +5V and the other to 0 V for "space" (logic 1) [practicalities of drivers on 5 volt supply meant actual minimum differential transmit level was 2V] and swapping the polarities for "mark" (logic 0). A receiver sensitivity of +/- 200 mV and the differential signal allowed 10 Mbits/sec over short distances and 100 kbits/sec over 1200 metres. Up to 10 receivers could be connected to one transmitter/line.

RS485 extended RS422 with "open circuit" mode for transmitters, allowing up to 30 transmitter/receiver points on one line.

Ethernet also drives lines at their proper impedance (originally 50 ohm coax) but had another physical difference in that AC transformer coupling/isolation was practical because of Manchester coding (the signal polarity is always swapped at the end of each bit and a swap in the middle of the bit differentiates between mark and space). Also the high basic bit rate of 10 Mbit/s meant the transformer size was small.

In contrast, the RS serial link standards [100 bit/s up] assumed a DC wired connection without isolation, so a string of 64 zeroes is no problem. RS are hardware standards, word lengths of 64 bits plus start/stop or more are not excluded!

Register to Reply
Active Contributor

Join Date: May 2011
Posts: 12
#6

Re: Ethernet vs Serial Communication

07/24/2011 9:44 AM

Hi friends....

Thank you very much for all these information.....

All re really helpful...

Skasnl

Register to Reply
Register to Reply 6 comments

Good Answers:

These comments received enough positive votes to make them "good answers".
Copy to Clipboard

Users who posted comments:

67model (1); Anonymous Poster (1); Randall (1); redfred (1); regsoft (1); skasnl (1)

Previous in Forum: Instrumnt junction boxes with captive clams and screw   Next in Forum: Welding Work Effecting Skid Cable
You might be interested in: Serial Communications Products, Serial Interfaces

Advertisement