{"data":{"slug":"serial-communication-basics","title":"Serial Communication Basics: RS-232, RS-422 and RS-485","summary":"Before Ethernet, there was serial: the point-to-point and multi-drop electrical interfaces (RS-232, RS-422, RS-485) that still connect printers, scales…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/serial-communication-basics","markdown_url":"https://wiki.aspotomasyon.com/article/serial-communication-basics.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/serial-communication-basics","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":804,"image":"https://wiki.aspotomasyon.com/assets/social/serial-communication-basics-50add0f7097b.png","html":"<p>Before Ethernet, there was serial: the point-to-point and multi-drop electrical interfaces (RS-232, RS-422, RS-485) that still connect printers, scales, barcode scanners, VFDs, and thousands of legacy instruments to control systems. Serial communication looks primitive — a few volts on two or four wires — but its electrical rules are precise, and most serial failures are electrical violations, not software bugs. Understanding the three standards and their practical behavior is still essential for every automation engineer.</p><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-context.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded.\"><figcaption>A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-context.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure>\n\n<h2 id=\"the-three-standards\">The Three Standards</h2>\n\n<table>\n  <thead>\n    <tr><th>Standard</th><th>Signal type</th><th>Topology</th><th>Distance</th><th>Typical use</th></tr>\n  </thead>\n  <tbody>\n    <tr><td>RS-232</td><td>Single-ended (voltage vs ground)</td><td>Point-to-point, one device</td><td>~15 m at low baud</td><td>Console ports, modems, short device links; simplest, most fragile.</td></tr>\n    <tr><td>RS-422</td><td>Differential, 4-wire (full duplex)</td><td>One transmitter, up to 10 receivers</td><td>~1,200 m</td><td>Instruments and systems needing longer, more robust point-to-multipoint receive links.</td></tr>\n    <tr><td>RS-485</td><td>Differential, 2-wire (half duplex) or 4-wire</td><td>Multi-drop bus, up to 32 unit loads</td><td>~1,200 m</td><td>Modbus RTU, PROFIBUS, and general multi-drop device buses — the industrial workhorse.</td></tr>\n  </tbody>\n</table>\n\n<p>The differential standards (RS-422/485) win on distance and noise immunity because the receiver measures the <em>difference</em> between two wires, not a level against ground — the interference cancels when it couples equally to both wires.</p>\n\n<h2 id=\"the-parameters-baud-data-parity-stop\">The Parameters: Baud, Data, Parity, Stop</h2>\n\n<p>Every serial link is configured with the same four parameters, and both ends must match exactly:</p>\n\n<ul>\n  <li><strong>Baud rate</strong> — bits per second (9600, 19200, 38400, 115200 typical). Both ends must agree; a mismatch produces garbage or silence.</li>\n  <li><strong>Data bits</strong> — usually 8 (7 for some legacy protocols with parity-based data).</li>\n  <li><strong>Parity</strong> — even, odd, or none: one error-detecting bit. Even/odd catches single-bit errors; none is common on modern links with CRC-based protocols (Modbus has its own CRC).</li>\n  <li><strong>Stop bits</strong> — 1 or 2, marking the end of a character.</li>\n</ul>\n\n<p>The configuration is the protocol's contract: Modbus RTU is typically 8N1 or 8E1; getting the parameters wrong is the most common \"serial doesn't work\" cause — and the easiest to verify (read the device's configuration label or its documentation).</p>\n\n<h2 id=\"handshaking-and-flow-control\">Handshaking and Flow Control</h2>\n\n<p>Hardware handshake lines (RTS/CTS, DTR/DSR on RS-232) manage flow between devices: the receiver asserts CTS when it can accept data. Many modern links run no handshaking (3-wire: TX, RX, GND) because the protocol itself (or the software) manages the flow — but the null-modem wiring (which pin talks to which) must match both ends. The classic failure: TX wired to TX, or a device waiting for CTS that never comes. When a link is silent, verify the wiring diagram of both connectors before suspecting the software.</p>\n\n<h2 id=\"practical-installation-rules\">Practical Installation Rules</h2>\n\n<ul>\n  <li>RS-232: keep it short, keep it away from power, and use a proper cable; long RS-232 runs at high baud are unreliable by physics.</li>\n  <li>RS-485: twisted pair, 120 Ω termination at both ends, biasing, common ground reference, daisy-chain topology — the full discipline from the Modbus RTU article applies to every RS-485 bus, whatever the protocol.</li>\n  <li>Use proper connectors and strain relief; serial cables are the most flexed, most abused cables in the plant.</li>\n  <li>Galvanic isolation (isolated converters) where devices are far apart or in different electrical environments — the fix for the ground-loop damage that kills serial ports.</li>\n</ul>\n\n<h2 id=\"diagnosing-serial-links\">Diagnosing Serial Links</h2>\n\n<ol>\n  <li><strong>Verify the configuration</strong> — baud/data/parity/stop against the device documentation.</li>\n  <li><strong>Verify the wiring</strong> — TX/RX crossed where required, ground connected, handshake lines correct.</li>\n  <li><strong>Loopback test</strong> — short the device's TX to RX (or use a loopback plug): if the port echoes, the port works; the fault is elsewhere.</li>\n  <li><strong>Monitor the traffic</strong> — a USB-serial analyzer (or the protocol tool) shows whether frames are flowing and whether the bytes look right; a repeating frame with a bad CRC is an electrical problem (termination, noise), not a configuration problem.</li>\n  <li><strong>Isolate by replacement</strong> — swap the cable (flexed cables fail intermittently), then the converter, then the device.</li>\n</ol>\n\n<h2 id=\"summary\">Summary</h2>\n\n<p>Serial communication is the oldest industrial network and still everywhere: RS-232 for short point-to-point, RS-422 for robust longer links, RS-485 for multi-drop buses. Match the parameters on both ends, wire the differential pairs with termination and grounding discipline, keep the cables short and clean, and diagnose with loopbacks and protocol analyzers. Serial links are simple — which is exactly why the details are unforgiving.</p><section class=\"engineering-check\"><h2 id=\"apply-this-to-your-project\">Apply this to your project</h2><ul><li>Specify payload structure, units, identity, time semantics, access permissions, and protocol versions.</li><li>Test backlog growth, connection loss, duplicate delivery, and restart behavior at the consuming application.</li><li>Document how operators see failures and how the system distinguishes replayed data from current process state.</li></ul><p><a href=\"https://wiki.aspotomasyon.com/guides\">Follow an ASP project guide</a> to connect the fundamentals with implementation and acceptance.</p></section><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-review.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration.\"><figcaption>Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-review.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure><h2 id=\"primary-references-and-further-reading\">Primary references and further reading</h2><p>Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.</p><ul><li><a href=\"https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html\" rel=\"noopener noreferrer\" target=\"_blank\">OASIS — MQTT 5.0 specification</a></li><li><a href=\"https://www.modbus.org/modbus-specifications\" rel=\"noopener noreferrer\" target=\"_blank\">Modbus Organization — Protocol specifications</a></li><li><a href=\"https://sparkplug.eclipse.org/specification/version/3.0/\" rel=\"noopener noreferrer\" target=\"_blank\">Eclipse Foundation — Sparkplug 3.0 specification</a></li></ul><!-- asp-editorial-202609 -->","markdown":"# Serial Communication Basics: RS-232, RS-422 and RS-485\n\n> Before Ethernet, there was serial: the point-to-point and multi-drop electrical interfaces (RS-232, RS-422, RS-485) that still connect printers, scales…\n\n- Canonical URL: https://wiki.aspotomasyon.com/article/serial-communication-basics\n- Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki)\n- Category: Modern Connectivity\n- Published: 2026-08-11 · Updated: 2026-09-13\n- Reading time: 4 min · Language: English\n\nBefore Ethernet, there was serial: the point-to-point and multi-drop electrical interfaces (RS-232, RS-422, RS-485) that still connect printers, scales, barcode scanners, VFDs, and thousands of legacy instruments to control systems. Serial communication looks primitive — a few volts on two or four wires — but its electrical rules are precise, and most serial failures are electrical violations, not software bugs. Understanding the three standards and their practical behavior is still essential for every automation engineer.\n\n![A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded.](https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-context.svg)\n\n*A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded.*\n\n## The Three Standards\n\n| Standard | Signal type | Topology | Distance | Typical use |\n| --- | --- | --- | --- | --- |\n| RS-232 | Single-ended (voltage vs ground) | Point-to-point, one device | ~15 m at low baud | Console ports, modems, short device links; simplest, most fragile. |\n| RS-422 | Differential, 4-wire (full duplex) | One transmitter, up to 10 receivers | ~1,200 m | Instruments and systems needing longer, more robust point-to-multipoint receive links. |\n| RS-485 | Differential, 2-wire (half duplex) or 4-wire | Multi-drop bus, up to 32 unit loads | ~1,200 m | Modbus RTU, PROFIBUS, and general multi-drop device buses — the industrial workhorse. |\n\nThe differential standards (RS-422/485) win on distance and noise immunity because the receiver measures the *difference* between two wires, not a level against ground — the interference cancels when it couples equally to both wires.\n\n## The Parameters: Baud, Data, Parity, Stop\n\nEvery serial link is configured with the same four parameters, and both ends must match exactly:\n\n- **Baud rate** — bits per second (9600, 19200, 38400, 115200 typical). Both ends must agree; a mismatch produces garbage or silence.\n- **Data bits** — usually 8 (7 for some legacy protocols with parity-based data).\n- **Parity** — even, odd, or none: one error-detecting bit. Even/odd catches single-bit errors; none is common on modern links with CRC-based protocols (Modbus has its own CRC).\n- **Stop bits** — 1 or 2, marking the end of a character.\n\nThe configuration is the protocol's contract: Modbus RTU is typically 8N1 or 8E1; getting the parameters wrong is the most common \"serial doesn't work\" cause — and the easiest to verify (read the device's configuration label or its documentation).\n\n## Handshaking and Flow Control\n\nHardware handshake lines (RTS/CTS, DTR/DSR on RS-232) manage flow between devices: the receiver asserts CTS when it can accept data. Many modern links run no handshaking (3-wire: TX, RX, GND) because the protocol itself (or the software) manages the flow — but the null-modem wiring (which pin talks to which) must match both ends. The classic failure: TX wired to TX, or a device waiting for CTS that never comes. When a link is silent, verify the wiring diagram of both connectors before suspecting the software.\n\n## Practical Installation Rules\n\n- RS-232: keep it short, keep it away from power, and use a proper cable; long RS-232 runs at high baud are unreliable by physics.\n- RS-485: twisted pair, 120 Ω termination at both ends, biasing, common ground reference, daisy-chain topology — the full discipline from the Modbus RTU article applies to every RS-485 bus, whatever the protocol.\n- Use proper connectors and strain relief; serial cables are the most flexed, most abused cables in the plant.\n- Galvanic isolation (isolated converters) where devices are far apart or in different electrical environments — the fix for the ground-loop damage that kills serial ports.\n\n## Diagnosing Serial Links\n\n1. **Verify the configuration** — baud/data/parity/stop against the device documentation.\n2. **Verify the wiring** — TX/RX crossed where required, ground connected, handshake lines correct.\n3. **Loopback test** — short the device's TX to RX (or use a loopback plug): if the port echoes, the port works; the fault is elsewhere.\n4. **Monitor the traffic** — a USB-serial analyzer (or the protocol tool) shows whether frames are flowing and whether the bytes look right; a repeating frame with a bad CRC is an electrical problem (termination, noise), not a configuration problem.\n5. **Isolate by replacement** — swap the cable (flexed cables fail intermittently), then the converter, then the device.\n\n## Summary\n\nSerial communication is the oldest industrial network and still everywhere: RS-232 for short point-to-point, RS-422 for robust longer links, RS-485 for multi-drop buses. Match the parameters on both ends, wire the differential pairs with termination and grounding discipline, keep the cables short and clean, and diagnose with loopbacks and protocol analyzers. Serial links are simple — which is exactly why the details are unforgiving.\n\n## Apply this to your project\n\n- Specify payload structure, units, identity, time semantics, access permissions, and protocol versions.\n- Test backlog growth, connection loss, duplicate delivery, and restart behavior at the consuming application.\n- Document how operators see failures and how the system distinguishes replayed data from current process state.\n\n[Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance.\n\n![Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration.](https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-review.svg)\n\n*Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration.*\n\n## Primary references and further reading\n\nUse the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.\n\n- [OASIS — MQTT 5.0 specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html)\n- [Modbus Organization — Protocol specifications](https://www.modbus.org/modbus-specifications)\n- [Eclipse Foundation — Sparkplug 3.0 specification](https://sparkplug.eclipse.org/specification/version/3.0/)\n\n---\n\nCite the canonical article: https://wiki.aspotomasyon.com/article/serial-communication-basics (Serial Communication Basics: RS-232, RS-422 and RS-485, ASP OTOMASYON, updated 2026-09-13).\n","headings":[{"id":"the-three-standards","title":"The Three Standards"},{"id":"the-parameters-baud-data-parity-stop","title":"The Parameters: Baud, Data, Parity, Stop"},{"id":"handshaking-and-flow-control","title":"Handshaking and Flow Control"},{"id":"practical-installation-rules","title":"Practical Installation Rules"},{"id":"diagnosing-serial-links","title":"Diagnosing Serial Links"},{"id":"summary","title":"Summary"},{"id":"apply-this-to-your-project","title":"Apply this to your project"},{"id":"primary-references-and-further-reading","title":"Primary references and further reading"}],"faq":[],"references":[{"name":"OASIS — MQTT 5.0 specification","url":"https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html"},{"name":"Modbus Organization — Protocol specifications","url":"https://www.modbus.org/modbus-specifications"},{"name":"Eclipse Foundation — Sparkplug 3.0 specification","url":"https://sparkplug.eclipse.org/specification/version/3.0/"}],"related":[{"slug":"modbus-tcpip-protocol-deep-dive","title":"Modbus TCP/IP Protocol: Deep Dive","summary":"Modbus is the oldest and most widely deployed industrial communication protocol in the world.","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/modbus-tcpip-protocol-deep-dive","markdown_url":"https://wiki.aspotomasyon.com/article/modbus-tcpip-protocol-deep-dive.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/modbus-tcpip-protocol-deep-dive","published":"2026-05-13T12:07:53+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":10,"word_count":2192,"image":"https://wiki.aspotomasyon.com/assets/social/modbus-tcpip-protocol-deep-dive-c377f0d645c1.png"},{"slug":"modbus-rtu-network-design","title":"Modbus RTU and RS-485 Network Design","summary":"Modbus RTU over RS-485 remains the most widespread industrial fieldbus in the world: simple, open, and present in everything from energy meters to VFDs and…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/modbus-rtu-network-design","markdown_url":"https://wiki.aspotomasyon.com/article/modbus-rtu-network-design.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/modbus-rtu-network-design","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":5,"word_count":881,"image":"https://wiki.aspotomasyon.com/assets/social/modbus-rtu-network-design-af7e36ee72b1.png"},{"slug":"kepware-driver-selection-architecture","title":"Kepware Driver Selection and Channel/Tag Architecture","summary":"KEPServerEX is the most widely deployed industrial connectivity platform: it converts dozens of native protocols — Siemens, Allen-Bradley, Modbus, DNP3…","category":{"slug":"opc-solutions","name":"OPC Solutions"},"url":"https://wiki.aspotomasyon.com/article/kepware-driver-selection-architecture","markdown_url":"https://wiki.aspotomasyon.com/article/kepware-driver-selection-architecture.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/kepware-driver-selection-architecture","published":"2026-08-11T13:05:19+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":5,"word_count":921,"image":"https://wiki.aspotomasyon.com/assets/social/kepware-driver-selection-architecture-22591e1f10b4.png"},{"slug":"cellular-iot-connectivity","title":"Cellular IoT Connectivity for Industrial Assets","summary":"Millions of industrial assets sit where no cable goes: remote pumps, tanks, substations, compressors, and machines in the field.","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/cellular-iot-connectivity","markdown_url":"https://wiki.aspotomasyon.com/article/cellular-iot-connectivity.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/cellular-iot-connectivity","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":875,"image":"https://wiki.aspotomasyon.com/assets/social/cellular-iot-connectivity-7ce625a4f9b7.png"}],"citation":"ASP OTOMASYON. Serial Communication Basics: RS-232, RS-422 and RS-485. Updated 2026-09-13. https://wiki.aspotomasyon.com/article/serial-communication-basics"}}