RS-485 - User contributions [en]

RS-485

2026-04-30T21:29:25Z

Admin:

= RS-485 Standard Overview =

== Introduction ==
'''RS-485''' (also known as '''TIA-485-A''' or '''EIA-485''') is a balanced differential serial communication standard introduced in 1983 by the Telecommunications Industry Association (TIA). It defines only the physical layer (electrical characteristics), making it protocol-agnostic and highly flexible.

RS-485 is widely adopted in industrial automation, embedded systems, building management, and instrumentation networks due to its robustness, long-distance capability, and resilience to electromagnetic interference (EMI).

Unlike higher-level communication protocols, RS-485 does not define data framing, addressing, or error handling — these are implemented by protocols such as Modbus, BACnet, or proprietary systems.

== Core Principles ==
* Differential signaling over twisted pair
* Multi-drop bus architecture
* Half-duplex dominant communication (full-duplex optional)
* Shared medium with controlled access (via protocol)

== Key Features ==
; Balanced Differential Signaling
: Uses two lines (A and B). Signal is represented as voltage difference (Vdiff = VA − VB). Rejects common-mode noise.

; Multipoint Capability
: Standard supports 32 unit loads. Modern ICs allow 128, 256 or more nodes. Depends on receiver input impedance (1/8 UL, 1/4 UL, etc.)

; Unit Load (UL) and Node Calculation
: 1 UL = 12 kΩ input impedance. Formula: <code>Max nodes = 32 / (receiver UL rating)</code>
: Examples:
:* 1 UL receivers → 32 nodes
:* 1/4 UL (48 kΩ) → 128 nodes
:* 1/8 UL (96 kΩ) → 256 nodes

; Data Rate vs Distance Tradeoff
:* 10 Mbps up to ~10–15 meters
:* 1 Mbps up to ~100 meters
:* 100 kbps up to ~1200 meters

; Slew Rate Control
: Some transceivers offer limited slew rate to reduce reflections and EMI on long cables or low-speed applications.

; Topology
: Linear bus (daisy chain) is REQUIRED for stability. Stub length should be minimized (< 30 cm typical). Star topology causes reflections and is strongly discouraged.

; Termination
: 120 Ω resistors at BOTH ends of the bus. Matches cable impedance → reduces reflections.

== Electrical Characteristics ==
; Differential Voltage
:* Logic 1 (MARK): Vdiff > +200 mV
:* Logic 0 (SPACE): Vdiff < -200 mV
:* Typical driver output: ±1.5V to ±5V

; Common-Mode Voltage Range
: -7 V to +12 V (receiver must tolerate this range)

; Receiver Sensitivity
: Must detect signals as low as ±200 mV

; Driver Output
: Must provide at least 1.5 V across 54 Ω load

; Driver Output Current
: Up to 250 mA typical (check specific transceiver datasheet)

; Three-State Drivers
: High-Z (tri-state) allows bus sharing. Enables multiple transmitters without conflict.

=== Bus State Table ===
{| class="wikitable"
|+ RS-485 Bus States
! State !! Vdiff (A−B) !! Driver Logic !! Receiver Output
|-
| Mark (1) || > +200 mV || High || 1
|-
| Space (0) || < -200 mV || Low || 0
|-
| Idle (Open, with biasing) || approx 0 V (biased to > +200 mV typically) || Not defined || 1 (if failsafe)
|}

== Bus Biasing (Failsafe) ==
Biasing ensures a defined logic state when no driver is active.

Typical implementation:
* Pull-up resistor on line A (to VCC)
* Pull-down resistor on line B (to GND)

Example resistor values: 680 Ω – 4.7 kΩ depending on system.

Without biasing: bus floats → noise → false triggering.

Modern transceivers often include '''failsafe receivers''' internally (guarantee logic 1 on open/short/idle bus).

== Transmission Line Effects ==
At higher speeds or longer distances, RS-485 behaves as a transmission line:
* Signal reflections occur if impedance mismatch exists
* Propagation delay matters (~5 ns/m typical cable)
* Ringing and overshoot can corrupt data

Best practices:
* Always terminate correctly
* Avoid stubs
* Use controlled impedance cable (~120 Ω)

== Grounding and Isolation ==
RS-485 is differential but NOT fully immune to ground differences.

Options:
* Shared signal ground (recommended for small systems)
* Isolated transceivers for:
** Industrial environments
** Long-distance links
** Different power domains

Isolation methods:
* Optocouplers
* Digital isolators (e.g., ADuM series)

== Half-Duplex vs Full-Duplex ==
; Half-Duplex (2 wires)
: Single pair (A/B). One device transmits at a time. Most common implementation.

; Full-Duplex (4 wires)
: Two differential pairs (A/B for TX, Z/Y for RX). Simultaneous TX/RX. Less common due to extra wiring.

== Collision Avoidance ==
RS-485 does NOT include collision detection. Handled by protocol:
* Master-slave (e.g., Modbus RTU)
* Token passing
* Time-slot scheduling

Incorrect handling leads to:
* Bus contention
* Signal corruption
* Potential driver damage

== Common Transceiver Chips ==
{| class="wikitable"
|+ Popular RS-485 Transceivers
! Model !! Unit Load !! Max Speed !! Special Feature
|-
| MAX485 || 1 || 2.5 Mbps || Classic, widely available
|-
| SP485 || 1 || 5 Mbps || Low cost
|-
| MAX487 || 1/4 || 250 kbps || 128 nodes
|-
| MAX1487 || 1/4 || 2.5 Mbps || 128 nodes
|-
| ADM2483 || 1/8 || 500 kbps || Isolated, 256 nodes
|}

== Cable Selection ==
Recommended:
* Twisted pair (mandatory)
* Characteristic impedance: 100–120 Ω
* Shielded cable for noisy environments

Examples:
* CAT5e / CAT6 (works well)
* Industrial RS-485 cable (e.g., Belden 9841)

== Connectors ==
Common connector types:
* Screw terminals
* DB9 (industrial legacy – pinout NOT standardized!)
* RJ45 (structured cabling reuse)

'''Warning:''' RS-485 does NOT define a connector or pinout. Always verify documentation.

== Advantages ==
* High immunity to EMI/RFI
* Long cable lengths
* Multi-drop capability
* Low cost implementation
* Widely supported hardware

== Limitations ==
* No built-in protocol
* Requires careful wiring
* Sensitive to topology errors (no star)
* No automatic arbitration
* Ground potential differences can cause issues

== Applications ==
* Industrial automation (Modbus RTU, PROFIBUS DP)
* PLC and SCADA systems
* Building automation (HVAC, lighting, access control)
* Energy meters and smart grids
* CNC machines and robotics
* Remote sensor networks
* Elevator and security systems

== Comparison with Other Standards ==
{| class="wikitable"
! Feature !! RS-232 !! RS-422 !! RS-485
|-
| Signaling || Single-ended || Differential || Differential
|-
| Max Distance || ~15 m || ~1200 m || ~1200 m
|-
| Nodes || 1 driver, 1 receiver || 1 driver, 10 receivers || 32 drivers, 32 receivers (up to 256)
|-
| Noise Immunity || Poor || Good || Excellent
|-
| Duplex || Full (3 wires) || Full (4 wires) || Half (2 wires) or Full (4 wires)
|}

== Common Mistakes ==
* Missing termination resistors
* Using star topology
* Long stubs
* No biasing resistors
* Mixing A/B polarity
* Ignoring grounding
* Using wrong cable (non-twisted)

== Design Best Practices ==
* Use termination ONLY at bus ends
* Keep stubs as short as possible
* Add biasing resistors if needed (one location only)
* Use isolated transceivers in harsh environments
* Validate signal with oscilloscope
* Label A/B clearly (vendors may swap naming!)

== Typical Network Layout ==
<pre>
[Master] --- Term --- Device --- Device --- Device --- Term ---
120Ω (last device) 120Ω
|
(biasing optional, one location only)
</pre>

== Debugging Tips ==
* Measure differential voltage (A-B)
* Check idle state (should be stable, typically >200 mV with biasing)
* Look for reflections on oscilloscope
* Verify polarity consistency (A to A, B to B throughout)
* Disconnect nodes to isolate faults
* Verify termination resistance across A-B (should be ~60 Ω if both ends terminated)

== Conclusion ==
RS-485 remains one of the most reliable and widely used physical layer standards for industrial and embedded communication. Its simplicity, robustness, and flexibility ensure its continued relevance even in modern systems alongside Ethernet and wireless technologies.

Proper design — especially topology, termination, and grounding — is critical to achieving stable and high-performance communication.

''This page serves as the central reference for RS-485 and links to detailed subtopics such as termination, biasing, isolation, and protocol implementations.''

== See Also ==
* [[Modbus]]
* [[RS-232]]
* [[RS-422]]
* [[Differential signaling]]
* [[Serial communication]]

== External References ==
* TIA/EIA-485-A Standard (1998)
* Application notes: Texas Instruments (SLLA272D), Analog Devices (AN-960), Maxim (AN-723)

RS-485

2026-04-30T21:28:28Z

Admin:

= RS-485 (TIA-485-A) Standard Overview =

== Introduction ==
'''RS-485 (TIA-485-A / EIA-485)''' is a physical layer standard for balanced multipoint serial communication introduced in 1983 by the Telecommunications Industry Association (TIA).

It defines only electrical characteristics of drivers and receivers, making it protocol-independent. Higher-level protocols such as Modbus, BACnet, Profibus, and proprietary systems define framing and addressing.

RS-485 is widely used in industrial automation, building management systems, embedded networks, and instrumentation systems due to its robustness, long distance capability, and noise immunity.

== Core Concept ==
RS-485 is based on differential signaling over a twisted pair and a shared bus architecture with tri-state drivers.

Signal is defined by voltage difference:

<math>V_{diff} = V_A - V_B</math>

== Electrical Characteristics ==

; Logic Levels
: Logic 1 (MARK): <math>V_{diff} < -200\ \text{mV}</math>
: Logic 0 (SPACE): <math>V_{diff} > +200\ \text{mV}</math>
: Undefined: −200 mV to +200 mV

; Receiver Sensitivity
: ±200 mV minimum differential detection

; Driver Output
: ≥ 1.5 V across 54 Ω load

; Common-mode range
: −7 V to +12 V

== Bus Architecture ==
Supported topologies:
* Linear bus (recommended)
* Multi-drop bus
* Point-to-point

Not recommended:
* Star topology (reflections)
* Ring topology

RS-485 must be implemented as a terminated transmission line.

== Transmission Line Behavior ==
At higher speeds, RS-485 behaves as a transmission line.

Propagation delay:

<math>t_{prop} \approx 5\ \text{ns/m}</math>

Effects:
* reflections
* ringing
* overshoot
* signal distortion

== Cable Length vs Speed ==
Real-world constraints depend on cable quality and capacitance:

* 10 Mbps → ~10–30 m
* 1 Mbps → ~100–300 m
* 100 kbps → up to ~1200 m

Rule of thumb:

<math>\text{bit rate} \cdot \text{distance} \lesssim 10^8</math>

== Termination ==
Termination must match cable impedance:

<math>R_{termination} = Z_0 \approx 120\ \Omega</math>

Rules:
* termination at both ends only
* no intermediate termination
* required to reduce reflections

== Biasing (Failsafe) ==
Biasing ensures a defined idle state when no driver is active.

Target condition:

<math>V_{diff} > 200\ \text{mV (idle)}</math>

Modern transceivers often include internal failsafe circuitry, making external biasing optional in many designs.

== A/B Line Polarity ==
RS-485 standard defines only differential signaling; it does not assign logic meaning to A and B lines.

Important:
* A/B labeling may differ between manufacturers
* polarity must be verified in practice
* oscilloscope measurement is recommended

== Grounding and Common Mode ==
RS-485 supports differential signaling but requires a valid common-mode range:

Allowed:
* −7 V to +12 V

Considerations:
* long cable runs may introduce ground potential differences
* optional reference ground (SC/GND) may be used
* isolation recommended in industrial environments

== Protection ==
Recommended protection methods:
* TVS diodes (ESD protection)
* common-mode chokes (EMI suppression)
* optional series resistors (10–50 Ω)

Relevant standards:
* IEC 61000-4-2 (ESD)
* IEC 61000-4-4 (EFT)
* IEC 61000-4-5 (surge)

== Duplex Modes ==

; Half-duplex
: 2-wire system, most common, one transmitter active at a time

; Full-duplex
: 4-wire system, separate TX and RX pairs

== Collision Handling ==
RS-485 does not define arbitration.

Handled by higher protocols:
* master-slave (Modbus RTU)
* token passing
* time-slot scheduling

Bus contention leads to data corruption.

== Network Topology ==
Correct topology:

<pre>
[Master]—120Ω—Device—Device—Device—120Ω
</pre>

Rules:
* linear bus only
* short stubs (< 20–30 cm recommended)
* termination only at ends

== Common Mistakes ==
* missing termination
* star topology wiring
* long stubs
* missing grounding strategy
* swapped A/B polarity
* no biasing in legacy systems

== Troubleshooting ==
Steps:
# measure differential voltage (A-B)
# verify idle state stability
# check termination resistance (~60 Ω total)
# inspect reflections using oscilloscope
# isolate nodes one by one

== Applications ==
* industrial automation (Modbus, Profibus)
* PLC systems
* SCADA networks
* building automation (HVAC, lighting)
* CNC and robotics
* energy meters
* security systems
* DMX512 lighting control

== Comparison with Other Standards ==
{| class="wikitable"
! Feature !! RS-232 !! RS-422 !! RS-485
|-
| Signaling || Single-ended || Differential || Differential
|-
| Nodes || 1 || 10 || 32–256
|-
| Distance || short || long || long
|-
| Noise immunity || low || high || very high
|-
| Topology || point-to-point || point-to-point || multipoint
|}

== Advantages ==
* high noise immunity
* long distance support
* multi-node capability
* low cost implementation
* industrial robustness

== Limitations ==
* no built-in protocol
* requires careful wiring
* no arbitration mechanism
* sensitive to topology errors

== Conclusion ==
RS-485 remains one of the most widely used physical layer standards in industrial communication systems.

Its reliability depends heavily on correct implementation of:
* termination
* topology
* grounding
* biasing

Proper engineering design is required to achieve stable and high-performance communication.

MediaWiki:Mainpage

2026-04-30T21:17:17Z

Admin: Created page with "RS-485"

RS-485

UART

2026-04-30T21:14:40Z

Admin: Created page with "= UART (Universal Asynchronous Receiver-Transmitter) = == Introduction == '''UART''' (Universal Asynchronous Receiver-Transmitter) is a hardware communication module used for asynchronous serial communication between devices. It is one of the simplest and most widely used serial interfaces in embedded systems, microcontrollers, and communication modules. UART defines only the data framing and timing at the logic level and requires a separate physical layer such as TTL-..."

= UART (Universal Asynchronous Receiver-Transmitter) =

== Introduction ==
'''UART''' (Universal Asynchronous Receiver-Transmitter) is a hardware communication module used for asynchronous serial communication between devices. It is one of the simplest and most widely used serial interfaces in embedded systems, microcontrollers, and communication modules.

UART defines only the data framing and timing at the logic level and requires a separate physical layer such as TTL-level signaling, RS-232, or RS-485.

== Core Principle ==
UART transmits data serially (bit by bit) without a shared clock signal between devices. Instead, both devices agree on a fixed baud rate.

Each data frame is synchronized using:
* Start bit (synchronization)
* Data bits (payload)
* Optional parity bit (error detection)
* Stop bit(s) (frame end)

== UART Frame Structure ==

A standard UART frame consists of:

<pre>
| Start | Data Bits | Parity (optional) | Stop Bits |
| 0 | 7–9 bits | 0 or 1 bit | 1–2 bits |
</pre>

; Start Bit
: Always logic 0. Signals the beginning of transmission.

; Data Bits
: Typically 7, 8, or 9 bits. Most common is 8-bit data.

; Parity Bit (Optional)
: Used for simple error detection:
* Even parity
* Odd parity
* None

; Stop Bits
: Logic 1 state used to mark end of frame (1, 1.5, or 2 bits)

== Baud Rate ==

UART communication depends on a pre-agreed baud rate.

:contentReference[oaicite:0]{index=0}

Common baud rates:
* 9600
* 19200
* 38400
* 57600
* 115200
* 921600 (high-speed UART)

Timing accuracy is critical:
* Typical tolerance: ±2% to ±5%

== UART vs Serial Communication ==
UART is a specific implementation of asynchronous serial communication.

* Serial communication = general concept
* UART = hardware implementation of asynchronous serial

UART is often used as:
* Data link layer inside microcontrollers
* Interface to physical standards (RS-232, RS-485 via transceivers)

== Electrical Levels ==

UART itself does NOT define electrical voltage levels.

It can operate on different physical layers:

; TTL UART
* Logic levels: 0 V (LOW), 3.3 V or 5 V (HIGH)
* Used inside microcontrollers

; RS-232 UART
* Uses ± voltage levels (inverted logic)
* Requires level shifting (e.g., MAX232)

; RS-485 UART
* Uses differential signaling (A/B lines)
* Requires transceiver (e.g., MAX485)

== Signal Lines ==

Minimal UART connection:

* TX (Transmit)
* RX (Receive)
* GND (Ground)

Cross-connection:
* TX → RX
* RX → TX

Optional:
* RTS / CTS (hardware flow control)

== Full-Duplex Operation ==
UART supports full-duplex communication:

* TX and RX operate independently
* Data can be sent and received simultaneously

== Flow Control ==

To prevent buffer overflow, UART may use flow control:

; Hardware Flow Control
* RTS (Request To Send)
* CTS (Clear To Send)

; Software Flow Control
* XON / XOFF characters

== Timing and Sampling ==
Since there is no clock line, timing is critical:

* Receiver detects start bit edge
* Samples data bits at center of bit period
* Uses baud rate to estimate timing

Clock drift between devices can cause:
* Framing errors
* Bit misalignment

== Error Detection ==

UART provides limited error detection:

* Parity bit (optional)
* Framing error (invalid stop bit)
* Overrun error (buffer overflow)

UART does NOT provide:
* Retransmission
* Acknowledgement
* Strong error correction

== Common Errors ==

* Baud rate mismatch
* Incorrect parity settings
* Reversed TX/RX wiring
* Missing ground reference
* Noise on long cables
* Wrong stop bit configuration

== Physical Layer Relationship ==
UART is NOT a physical standard. It requires external interfaces:

* TTL UART → microcontroller pins
* RS-232 → PC serial ports (legacy)
* RS-485 → industrial networks
* RS-422 → long-distance links

UART defines only:
* Frame structure
* Timing
* Bit-level protocol

== Applications ==
UART is widely used in:

* Microcontroller debugging (serial console)
* GPS modules
* Bluetooth modules (HC-05, HC-06)
* Wi-Fi modules (ESP8266/ESP32 AT commands)
* Industrial sensors
* Embedded device communication
* Bootloaders and firmware flashing

== Advantages ==
* Extremely simple hardware implementation
* Low resource usage
* Wide compatibility
* Flexible baud rate configuration
* Easy debugging and testing
* Works with multiple physical layers

== Limitations ==
* No built-in addressing
* No robust error correction
* Sensitive to timing mismatch
* Limited distance (depends on physical layer)
* No native multi-device bus support

== Debugging Tips ==
* Verify TX/RX crossover
* Check baud rate and frame settings
* Ensure shared ground reference
* Use logic analyzer for signal inspection
* Test loopback mode (TX → RX shorted)
* Reduce baud rate for stability testing
* Check for noise on long cables

== Typical UART Waveform ==
A UART frame appears as:

* Idle state: HIGH (logic 1)
* Start bit: LOW
* Data bits: sequential LSB first
* Stop bit: HIGH

== Relationship to Other Standards ==
UART is commonly used with:

* [[RS-232]] (PC serial ports)
* [[RS-485]] (industrial multi-drop networks)
* [[RS-422]] (long-distance point-to-multipoint)
* [[Modbus]] (protocol over UART/RS-485)

== Conclusion ==
UART is one of the most fundamental building blocks of digital communication systems. While simple in design, it forms the foundation for many industrial and embedded communication protocols when combined with appropriate physical layers such as RS-232 or RS-485.

Understanding UART is essential for working with microcontrollers, embedded systems, and serial communication in general.

== See Also ==
* [[Serial communication]]
* [[RS-232]]
* [[RS-422]]
* [[RS-485]]
* [[Modbus]]
* [[Differential signaling]]

== External References ==
* Microcontroller UART datasheets (STM32, AVR, ESP32)
* Texas Instruments UART application notes
* ARM Cortex-M serial communication documentation

Serial communication

2026-04-30T21:14:06Z

Admin: Created page with "= Serial Communication = == Introduction == '''Serial communication''' is a method of transmitting data one bit at a time over a single communication channel or pair of channels. It is one of the most fundamental forms of digital communication and is widely used in embedded systems, industrial automation, computer peripherals, and telecommunications. Serial communication can operate over short distances (e.g., UART between microcontrollers) or long distances (e.g., RS-..."

= Serial Communication =

== Introduction ==
'''Serial communication''' is a method of transmitting data one bit at a time over a single communication channel or pair of channels. It is one of the most fundamental forms of digital communication and is widely used in embedded systems, industrial automation, computer peripherals, and telecommunications.

Serial communication can operate over short distances (e.g., UART between microcontrollers) or long distances (e.g., RS-485 networks).

== Core Principle ==
Data is transmitted sequentially over time rather than in parallel.

Instead of sending multiple bits simultaneously (parallel communication), serial communication sends:

* One bit per clock interval (synchronous), or
* One bit per timing interval defined by baud rate (asynchronous)

== Types of Serial Communication ==

=== Asynchronous Communication ===
No shared clock signal is used between devices.

Key features:
* Start and stop bits define each frame
* Timing is based on agreed baud rate
* Common in UART-based systems

Examples:
* UART
* RS-232
* RS-485 (with Modbus RTU)

=== Synchronous Communication ===
A shared clock signal is used to synchronize transmission.

Key features:
* Higher efficiency (no start/stop overhead)
* More complex hardware required
* Precise timing control

Examples:
* SPI
* I2C (clocked variant)
* Synchronous serial links in industrial systems

== Basic Serial Frame (Asynchronous) ==

A typical UART-style frame:

* Start bit (0)
* Data bits (7–9 bits)
* Optional parity bit
* Stop bit(s)

Example structure:

<pre>
| Start | Data Bits | Parity | Stop |
| 0 | 8 bits | optional | 1–2 |
</pre>

== Baud Rate ==

Baud rate defines the number of signal changes per second.

:contentReference[oaicite:0]{index=0}

In most UART systems:
* 1 symbol = 1 bit → baud rate = bit rate

Common baud rates:
* 9600 bps
* 19200 bps
* 115200 bps
* 1 Mbps (high-speed UART)

== Key Parameters ==

; Bit Rate
: Number of bits transmitted per second.

; Frame Format
: Structure of data packet (start, data, parity, stop bits).

; Parity
: Error detection method:
* Even
* Odd
* None

; Stop Bits
: Signal end of frame (1, 1.5, or 2 bits)

== Serial vs Parallel Communication ==
{| class="wikitable"
! Feature !! Serial !! Parallel
|-
| Number of wires || Few (1–2 pairs) || Many (8+ lines)
|-
| Distance || Long || Short
|-
| Complexity || Low || High
|-
| EMI susceptibility || Lower (especially differential serial) || Higher
|-
| Speed (modern systems) || Very high || Limited by skew
|}

== Electrical Implementations ==
Serial communication can be implemented using different electrical standards:

; Single-Ended Serial
* RS-232
* TTL UART (microcontrollers)

; Differential Serial
* RS-422
* RS-485
* CAN bus
* USB (high-speed variants)

Differential implementations offer:
* Higher noise immunity
* Longer cable distance
* Better signal integrity

== Synchronous Serial Examples ==

; SPI (Serial Peripheral Interface)
* Full-duplex
* Master-driven clock
* High-speed short-range communication

; I2C (Inter-Integrated Circuit)
* Two-wire bus (SCL, SDA)
* Multi-device support
* Lower speed than SPI

== Asynchronous Serial Example (UART) ==
UART is the most common serial interface in embedded systems.

Features:
* No clock line
* Configurable baud rate
* Simple wiring (TX, RX, GND)

Common usage:
* Debug consoles
* GPS modules
* Serial sensors
* Communication between MCUs

== Timing Considerations ==
Serial communication relies heavily on timing accuracy:

* Baud rate mismatch causes framing errors
* Clock drift can accumulate over long transmissions
* Higher speeds require tighter tolerance

Typical tolerance:
* ±2% to ±5% baud rate mismatch acceptable

== Noise and Signal Integrity ==
Serial communication performance depends on physical layer:

Factors affecting reliability:
* Cable length
* EMI environment
* Ground potential differences
* Signal type (single-ended vs differential)

Mitigation:
* Shielded cables
* Differential signaling (RS-485, RS-422)
* Proper termination
* Ground reference management

== Common Errors ==
* Baud rate mismatch
* Incorrect frame format (parity/stop bits)
* Reversed TX/RX lines
* Missing ground connection
* Noise interference on long cables
* Using UART over RS-232 without level shifting

== Applications ==
Serial communication is used in:

* Embedded microcontrollers (UART debugging)
* Industrial automation (Modbus over RS-485)
* Networking equipment configuration
* Sensors and measurement devices
* Automotive systems (CAN bus, LIN)
* Computer peripherals (USB internally serial-based)
* Robotics and control systems

== Advantages ==
* Simple hardware implementation
* Low wiring complexity
* Scalable over different physical layers
* Reliable for long-distance communication (with differential signaling)
* Flexible speed configuration

== Limitations ==
* Lower raw throughput compared to parallel (historically)
* Timing-sensitive
* Requires protocol layer for addressing and structure
* Susceptible to noise (especially single-ended systems)

== Relationship to Physical Standards ==
Serial communication is an abstraction layer that depends on physical interfaces:

* UART → logic-level serial
* RS-232 → single-ended electrical standard
* RS-485 → differential multi-drop bus
* RS-422 → differential point-to-multipoint
* USB / Ethernet → high-speed serial protocols

== Debugging Tips ==
* Verify baud rate and frame settings
* Check TX/RX wiring direction
* Confirm shared ground (if single-ended)
* Use logic analyzer or oscilloscope
* Test loopback mode if available
* Reduce cable length for troubleshooting
* Switch to lower baud rate for stability testing

== Conclusion ==
Serial communication is a foundational concept in digital systems, enabling efficient data transfer using minimal wiring. Its flexibility allows it to scale from simple UART links to complex industrial networks such as RS-485-based systems.

Understanding serial communication is essential for working with embedded systems, industrial automation, and modern communication protocols.

== See Also ==
* [[UART]]
* [[RS-232]]
* [[RS-422]]
* [[RS-485]]
* [[Differential signaling]]
* [[Modbus]]

== External References ==
* Texas Instruments UART and serial communication guides
* Analog Devices interface design notes
* IEEE communication standards documentation

Differential signaling

2026-04-30T21:13:29Z

Admin: Created page with "= Differential Signaling = == Introduction == '''Differential signaling''' is an electrical signaling method in which information is transmitted using the voltage difference between two complementary проводников (A and B), rather than a single wire referenced to ground. This technique is widely used in high-speed and noise-sensitive communication systems, including RS-422, RS-485, USB, Ethernet, LVDS, and many industrial interfaces. The main advantage of di..."

= Differential Signaling =

== Introduction ==
'''Differential signaling''' is an electrical signaling method in which information is transmitted using the voltage difference between two complementary проводников (A and B), rather than a single wire referenced to ground.

This technique is widely used in high-speed and noise-sensitive communication systems, including RS-422, RS-485, USB, Ethernet, LVDS, and many industrial interfaces.

The main advantage of differential signaling is its strong immunity to electromagnetic interference (EMI) and ground potential differences.

== Core Principle ==
Instead of sending a signal on one wire, differential signaling uses two wires:

* One wire carries the original signal (A)
* The other carries the inverted signal (B)

The receiver interprets data based on the voltage difference:

* Vdiff = VA − VB

== How It Works ==

At the transmitter side:
* When sending logic 1 → A > B
* When sending logic 0 → A < B

At the receiver side:
* Only the difference between A and B matters
* External noise affecting both wires equally is rejected

== Key Concept: Common-Mode Noise Rejection ==
One of the most important advantages is immunity to common-mode interference.

If noise affects both wires equally:
* VA increases by +1V
* VB also increases by +1V
* Vdiff remains unchanged

This allows stable communication even in electrically noisy environments.

== Electrical Representation ==

:contentReference[oaicite:0]{index=0}

Where:
* VA = voltage on positive line
* VB = voltage on negative line
* Vdiff = differential signal seen by receiver

== Signal States ==
{| class="wikitable"
! State !! Condition !! Interpretation
|-
| Logic 1 (MARK) || VA > VB || Positive differential voltage
|-
| Logic 0 (SPACE) || VA < VB || Negative differential voltage
|-
| Undefined || VA ≈ VB || Noise region / idle state
|}

== Advantages ==

; High Noise Immunity
: External noise affects both wires equally and is rejected by the receiver.

; Long Distance Communication
: Suitable for hundreds or thousands of meters depending on protocol.

; Higher Data Rates
: Supports much higher speeds than single-ended signaling.

; Reduced EMI Emission
: Currents flow in opposite directions, cancelling electromagnetic fields.

; Ground Independence
: Less sensitive to ground potential differences between devices.

== Disadvantages ==

; Increased Wiring Complexity
: Requires two conductors per signal instead of one.

; More Complex Transceivers
: Requires differential drivers and receivers.

; Cable Requirements
: Works best with controlled impedance twisted pair cables.

== Comparison with Single-Ended Signaling ==
{| class="wikitable"
! Feature !! Single-Ended (RS-232) !! Differential (RS-422/RS-485)
|-
| Signal reference || Ground || Voltage difference (A-B)
|-
| Noise immunity || Low || High
|-
| Cable requirement || 1 wire + ground || 2 wires (twisted pair)
|-
| Distance || Short (~15 m) || Long (~1200 m)
|-
| EMI resistance || Poor || Excellent
|}

== Transmission Line Behavior ==
At higher frequencies, differential pairs behave as transmission lines:

* Controlled impedance is required (typically 100–120 Ω)
* Reflections occur if impedance is mismatched
* Proper termination is required to preserve signal integrity

Termination resistor:

:contentReference[oaicite:1]{index=1}

Where:
* Z₀ = characteristic impedance of cable

== Termination ==
To prevent signal reflections:

* A resistor matching cable impedance is placed across A and B
* Typically located at one or both ends of the communication line

Effects of improper termination:
* Signal ringing
* Data corruption
* Reduced maximum cable length

== Common Applications ==
Differential signaling is used in many systems:

* RS-422 / RS-485 (industrial communication)
* USB (data lines D+ / D−)
* Ethernet (twisted pair PHY layers)
* LVDS (high-speed internal links)
* CAN bus (automotive networks)
* HDMI / Display interfaces (high-speed differential pairs)

== Grounding Considerations ==
Although differential signaling reduces sensitivity to ground differences:

* A reference ground is still recommended
* Large ground potential differences can exceed receiver limits
* Isolation may be required in industrial environments

== Isolation Techniques ==
To improve robustness:

* Digital isolators (high-speed IC isolators)
* Optocouplers (lower-speed systems)
* Isolated DC-DC converters (for full galvanic isolation)

== Common Mistakes ==
* Treating differential pairs as independent single wires
* Reversing polarity (A/B swap)
* Using untwisted cables
* Missing termination resistors
* Mixing cable impedance values
* Ignoring ground reference in long systems

== Design Best Practices ==
* Always use twisted pair cabling
* Maintain consistent A/B labeling across system
* Match cable impedance to termination resistors
* Keep stubs as short as possible
* Avoid star topology in high-speed systems
* Use shielding in noisy environments
* Validate signals with differential oscilloscope probe

== Debugging Tips ==
* Measure Vdiff (not individual wires)
* Check for polarity inversion (signal appears inverted)
* Inspect waveform for reflections or ringing
* Verify termination resistance (~60 Ω total in dual-end termination)
* Disconnect nodes to isolate faults
* Check ground potential differences between devices

== Why It Matters ==
Differential signaling is the foundation of modern robust communication systems. It enables:

* Industrial networks (RS-485, CAN)
* High-speed data transfer (USB, Ethernet)
* Long-distance communication in harsh environments

Without differential signaling, most modern industrial and high-speed digital communication systems would not be reliable.

== Conclusion ==
Differential signaling is a fundamental electrical principle that significantly improves noise immunity, transmission distance, and signal integrity. It is the basis for many modern communication standards used in industrial, automotive, and consumer electronics systems.

Understanding differential behavior is essential for designing reliable RS-422, RS-485, and high-speed digital interfaces.

== See Also ==
* [[RS-485]]
* [[RS-422]]
* [[RS-232]]
* [[Transmission line theory]]
* [[Modbus]]
* [[Serial communication]]

== External References ==
* Texas Instruments differential signaling guides
* Analog Devices high-speed interface application notes
* IEEE and TIA communication standards documentation

Modbus

2026-04-30T21:12:35Z

Admin: Created page with "= Modbus Protocol Overview = == Introduction == '''Modbus''' is a widely used open communication protocol developed by Modicon (now Schneider Electric) in 1979 for industrial automation systems. It is one of the most common protocols used on top of serial communication standards such as RS-485, RS-422, and RS-232, as well as TCP/IP networks (Modbus TCP). Modbus defines the '''application layer''' (message structure and data model) and is independent of the underlying p..."

= Modbus Protocol Overview =

== Introduction ==
'''Modbus''' is a widely used open communication protocol developed by Modicon (now Schneider Electric) in 1979 for industrial automation systems. It is one of the most common protocols used on top of serial communication standards such as RS-485, RS-422, and RS-232, as well as TCP/IP networks (Modbus TCP).

Modbus defines the '''application layer''' (message structure and data model) and is independent of the underlying physical layer.

It is widely used in PLC systems, industrial sensors, SCADA systems, energy meters, and embedded devices due to its simplicity and robustness.

== Core Principles ==
* Master–slave (client–server) communication model
* Simple request/response mechanism
* No built-in collision handling (handled by master logic or bus topology)
* Device addressing system
* Register-based data model

== Modbus Variants ==
; Modbus RTU
: Binary protocol used over serial lines (RS-485, RS-422, RS-232)
* Compact frame format
* CRC error checking
* Most common industrial implementation

; Modbus ASCII
: Human-readable ASCII-based version
* Easier to debug manually
* Slower and less efficient than RTU
* Rare in modern systems

; Modbus TCP
: Ethernet-based version
* Runs over TCP/IP (port 502)
* No CRC (handled by TCP)
* Allows higher scalability and integration with IT networks

== Network Architecture ==

; Master–Slave Model (RTU/ASCII)
* One master controls communication
* Multiple slaves respond only when addressed
* Slaves never initiate communication

; Client–Server Model (TCP)
* Master → Client
* Slave → Server
* Multiple clients supported over Ethernet

== Addressing ==

* Device addresses: 1–247
* Address 0: Broadcast (no response)
* Each slave must have a unique address on the bus

Incorrect configuration:
* Duplicate addresses → communication conflicts
* Address mismatch → no response

== Modbus Frame Structure (RTU) ==

<pre>
| Address | Function | Data | CRC |
| 1 byte | 1 byte | N bytes | 2 bytes |
</pre>

; Fields:
* '''Address''': Slave device ID
* '''Function''': Operation code (read/write)
* '''Data''': Registers, addresses, values
* '''CRC''': Error detection (16-bit)

== Common Function Codes ==
{| class="wikitable"
! Code !! Function !! Description
|-
| 01 || Read Coils || Read digital outputs
|-
| 02 || Read Discrete Inputs || Read digital inputs
|-
| 03 || Read Holding Registers || Read analog data / configuration
|-
| 04 || Read Input Registers || Read sensor values
|-
| 05 || Write Single Coil || Control single digital output
|-
| 06 || Write Single Register || Write one register value
|-
| 15 (0x0F) || Write Multiple Coils || Batch digital output control
|-
| 16 (0x10) || Write Multiple Registers || Batch register write
|}

== Data Model ==

Modbus uses a simple memory-like structure:

* Coils (0xxxx): Digital outputs (read/write)
* Discrete Inputs (1xxxx): Digital inputs (read-only)
* Input Registers (3xxxx): Analog inputs (read-only)
* Holding Registers (4xxxx): Configuration / writable registers

Each register is:
* 16-bit wide
* Big-endian format (MSB first)

== Modbus RTU Timing ==

Critical timing requirements:

* Silent interval ≥ 3.5 character times (frame delimiter)
* Inter-character delay ≤ 1.5 character times
* Baud rate typically: 9600–115200 bps

Timing violations cause:
* Frame corruption
* Slave timeout
* Communication errors

== Physical Layer Usage ==

Modbus is commonly implemented on:

* RS-485 (most common)
* RS-422 (point-to-multipoint read-only systems)
* RS-232 (single device links)
* Ethernet (Modbus TCP)

RS-485 is preferred due to:
* Multi-drop capability
* Noise immunity
* Long cable support

== Termination and Biasing (RS-485 context) ==
When used over RS-485:

* 120 Ω termination at both ends of the bus
* Biasing resistors may be required for idle stability
* Proper grounding is essential for long runs

Modbus itself does NOT define electrical termination — it depends on the physical layer.

== Error Handling ==
Modbus RTU uses:

* CRC-16 checksum for error detection
* Timeout-based failure detection

Modbus TCP uses:
* TCP/IP error handling (no CRC in Modbus layer)

No retransmission mechanism is defined in the protocol itself.

== Limitations ==
* No built-in encryption or security
* No authentication mechanism
* Limited data types (16-bit registers)
* No standardized device discovery
* Master bottleneck in RTU systems
* No collision handling at protocol level

== Advantages ==
* Very simple protocol design
* Lightweight and fast implementation
* Wide industry adoption
* Vendor-independent
* Easy to debug and implement
* Works over multiple physical layers

== Applications ==
* Industrial automation (PLC systems)
* SCADA monitoring systems
* Energy meters and smart grids
* HVAC control systems
* Industrial sensors and actuators
* Water treatment systems
* Building automation (BMS)
* Embedded microcontroller systems

== Common Implementation Issues ==
* Incorrect register addressing (offset confusion: 0-based vs 1-based)
* Endianness mismatches
* Wrong baud rate or parity settings
* Missing termination on RS-485 bus
* Duplicate slave IDs
* Improper timing in RTU mode
* Mixing Modbus TCP and RTU assumptions

== Debugging Tips ==
* Use Modbus analyzer or protocol sniffer
* Verify CRC calculations
* Check baud rate and parity alignment
* Confirm slave address mapping
* Monitor RS-485 differential signal (A-B)
* Test with single slave before expanding network
* Validate register offsets carefully

== Security Considerations ==
Modbus has no built-in security mechanisms:

Risks:
* Unauthorized command injection
* Network sniffing (plaintext protocol)
* Device manipulation

Mitigations:
* Network segmentation (industrial VLANs)
* Firewalls and gateways
* Modbus over VPN tunnels
* Protocol wrappers with authentication

== Comparison with Other Protocols ==
{| class="wikitable"
! Feature !! Modbus !! CAN Bus !! Profibus
|-
| Complexity || Low || Medium || High
|-
| Speed || Medium || Medium || High
|-
| Topology || Master-slave || Multi-master || Master-slave
|-
| Security || None || None || Limited
|-
| Use case || Industrial automation || Automotive / embedded || Industrial systems
|}

== Conclusion ==
Modbus remains one of the most widely used industrial communication protocols due to its simplicity, reliability, and ease of implementation. While it lacks modern security and advanced features, its compatibility with multiple physical layers and broad ecosystem support ensure its continued relevance in industrial and embedded systems.

Proper implementation of timing, addressing, and physical layer design is critical for stable operation.

''This page provides a foundational overview of Modbus and should be used alongside RS-485/RS-422 physical layer documentation and device-specific register maps.''

== See Also ==
* [[RS-485]]
* [[RS-422]]
* [[RS-232]]
* [[Serial communication]]
* [[Industrial communication protocols]]

== External References ==
* Modbus Organization Specification (www.modbus.org)
* Schneider Electric Modbus documentation
* Texas Instruments Modbus over RS-485 application notes
* Analog Devices industrial communication guides

RS-485

2026-04-30T21:11:52Z

Admin:

RS-485

2026-04-30T21:11:29Z

Admin: Created page with "= RS-485 Standard Overview = == Introduction == '''RS-485''' (also known as '''TIA-485-A''' or '''EIA-485''') is a balanced differential serial communication standard introduced in 1983 by the Telecommunications Industry Association (TIA). It defines only the physical layer (electrical characteristics), making it protocol-agnostic and highly flexible. RS-485 is widely adopted in industrial automation, embedded systems, building management, and instrumentation networks du..."

= RS-485 Standard Overview = == Introduction == '''RS-485''' (also known as '''TIA-485-A''' or '''EIA-485''') is a balanced differential serial communication standard introduced in 1983 by the Telecommunications Industry Association (TIA). It defines only the physical layer (electrical characteristics), making it protocol-agnostic and highly flexible. RS-485 is widely adopted in industrial automation, embedded systems, building management, and instrumentation networks due to its robustness, long-distance capability, and resilience to electromagnetic interference (EMI). Unlike higher-level communication protocols, RS-485 does not define data framing, addressing, or error handling — these are implemented by protocols such as Modbus, BACnet, or proprietary systems. == Core Principles == * Differential signaling over twisted pair * Multi-drop bus architecture * Half-duplex dominant communication (full-duplex optional) * Shared medium with controlled access (via protocol) == Key Features == ; Balanced Differential Signaling : Uses two lines (A and B). Signal is represented as voltage difference (Vdiff = VA − VB). Rejects common-mode noise. ; Multipoint Capability : Standard supports 32 unit loads. Modern ICs allow 128, 256 or more nodes. Depends on receiver input impedance (1/8 UL, 1/4 UL, etc.) ; Unit Load (UL) and Node Calculation : 1 UL = 12 kΩ input impedance. Formula: <code>Max nodes = 32 / (receiver UL rating)</code> : Examples: :* 1 UL receivers → 32 nodes :* 1/4 UL (48 kΩ) → 128 nodes :* 1/8 UL (96 kΩ) → 256 nodes ; Data Rate vs Distance Tradeoff :* 10 Mbps up to ~10–15 meters :* 1 Mbps up to ~100 meters :* 100 kbps up to ~1200 meters ; Slew Rate Control : Some transceivers offer limited slew rate to reduce reflections and EMI on long cables or low-speed applications. ; Topology : Linear bus (daisy chain) is REQUIRED for stability. Stub length should be minimized (< 30 cm typical). Star topology causes reflections and is strongly discouraged. ; Termination : 120 Ω resistors at BOTH ends of the bus. Matches cable impedance → reduces reflections. == Electrical Characteristics == ; Differential Voltage :* Logic 1 (MARK): Vdiff > +200 mV :* Logic 0 (SPACE): Vdiff < -200 mV :* Typical driver output: ±1.5V to ±5V ; Common-Mode Voltage Range : -7 V to +12 V (receiver must tolerate this range) ; Receiver Sensitivity : Must detect signals as low as ±200 mV ; Driver Output : Must provide at least 1.5 V across 54 Ω load ; Driver Output Current : Up to 250 mA typical (check specific transceiver datasheet) ; Three-State Drivers : High-Z (tri-state) allows bus sharing. Enables multiple transmitters without conflict. === Bus State Table === {| class="wikitable" |+ RS-485 Bus States ! State !! Vdiff (A−B) !! Driver Logic !! Receiver Output |- | Mark (1) || > +200 mV || High || 1 |- | Space (0) || < -200 mV || Low || 0 |- | Idle (Open, with biasing) || approx 0 V (biased to > +200 mV typically) || Not defined || 1 (if failsafe) |} == Bus Biasing (Failsafe) == Biasing ensures a defined logic state when no driver is active. Typical implementation: * Pull-up resistor on line A (to VCC) * Pull-down resistor on line B (to GND) Example resistor values: 680 Ω – 4.7 kΩ depending on system. Without biasing: bus floats → noise → false triggering. Modern transceivers often include '''failsafe receivers''' internally (guarantee logic 1 on open/short/idle bus). == Transmission Line Effects == At higher speeds or longer distances, RS-485 behaves as a transmission line: * Signal reflections occur if impedance mismatch exists * Propagation delay matters (~5 ns/m typical cable) * Ringing and overshoot can corrupt data Best practices: * Always terminate correctly * Avoid stubs * Use controlled impedance cable (~120 Ω) == Grounding and Isolation == RS-485 is differential but NOT fully immune to ground differences. Options: * Shared signal ground (recommended for small systems) * Isolated transceivers for: ** Industrial environments ** Long-distance links ** Different power domains Isolation methods: * Optocouplers * Digital isolators (e.g., ADuM series) == Half-Duplex vs Full-Duplex == ; Half-Duplex (2 wires) : Single pair (A/B). One device transmits at a time. Most common implementation. ; Full-Duplex (4 wires) : Two differential pairs (A/B for TX, Z/Y for RX). Simultaneous TX/RX. Less common due to extra wiring. == Collision Avoidance == RS-485 does NOT include collision detection. Handled by protocol: * Master-slave (e.g., Modbus RTU) * Token passing * Time-slot scheduling Incorrect handling leads to: * Bus contention * Signal corruption * Potential driver damage == Common Transceiver Chips == {| class="wikitable" |+ Popular RS-485 Transceivers ! Model !! Unit Load !! Max Speed !! Special Feature |- | MAX485 || 1 || 2.5 Mbps || Classic, widely available |- | SP485 || 1 || 5 Mbps || Low cost |- | MAX487 || 1/4 || 250 kbps || 128 nodes |- | MAX1487 || 1/4 || 2.5 Mbps || 128 nodes |- | ADM2483 || 1/8 || 500 kbps || Isolated, 256 nodes |} == Cable Selection == Recommended: * Twisted pair (mandatory) * Characteristic impedance: 100–120 Ω * Shielded cable for noisy environments Examples: * CAT5e / CAT6 (works well) * Industrial RS-485 cable (e.g., Belden 9841) == Connectors == Common connector types: * Screw terminals * DB9 (industrial legacy – pinout NOT standardized!) * RJ45 (structured cabling reuse) '''Warning:''' RS-485 does NOT define a connector or pinout. Always verify documentation. == Advantages == * High immunity to EMI/RFI * Long cable lengths * Multi-drop capability * Low cost implementation * Widely supported hardware == Limitations == * No built-in protocol * Requires careful wiring * Sensitive to topology errors (no star) * No automatic arbitration * Ground potential differences can cause issues == Applications == * Industrial automation (Modbus RTU, PROFIBUS DP) * PLC and SCADA systems * Building automation (HVAC, lighting, access control) * Energy meters and smart grids * CNC machines and robotics * Remote sensor networks * Elevator and security systems == Comparison with Other Standards == {| class="wikitable" ! Feature !! RS-232 !! RS-422 !! RS-485 |- | Signaling || Single-ended || Differential || Differential |- | Max Distance || ~15 m || ~1200 m || ~1200 m |- | Nodes || 1 driver, 1 receiver || 1 driver, 10 receivers || 32 drivers, 32 receivers (up to 256) |- | Noise Immunity || Poor || Good || Excellent |- | Duplex || Full (3 wires) || Full (4 wires) || Half (2 wires) or Full (4 wires) |} == Common Mistakes == * Missing termination resistors * Using star topology * Long stubs * No biasing resistors * Mixing A/B polarity * Ignoring grounding * Using wrong cable (non-twisted) == Design Best Practices == * Use termination ONLY at bus ends * Keep stubs as short as possible * Add biasing resistors if needed (one location only) * Use isolated transceivers in harsh environments * Validate signal with oscilloscope * Label A/B clearly (vendors may swap naming!) == Typical Network Layout == <pre> [Master] --- Term --- Device --- Device --- Device --- Term --- 120Ω (last device) 120Ω | (biasing optional, one location only) </pre> == Debugging Tips == * Measure differential voltage (A-B) * Check idle state (should be stable, typically >200 mV with biasing) * Look for reflections on oscilloscope * Verify polarity consistency (A to A, B to B throughout) * Disconnect nodes to isolate faults * Verify termination resistance across A-B (should be ~60 Ω if both ends terminated) == Conclusion == RS-485 remains one of the most reliable and widely used physical layer standards for industrial and embedded communication. Its simplicity, robustness, and flexibility ensure its continued relevance even in modern systems alongside Ethernet and wireless technologies. Proper design — especially topology, termination, and grounding — is critical to achieving stable and high-performance communication. ''This page serves as the central reference for RS-485 and links to detailed subtopics such as termination, biasing, isolation, and protocol implementations.'' == See Also == * [[Modbus]] * [[RS-232]] * [[RS-422]] * [[Differential signaling]] * [[Serial communication]] == External References == * TIA/EIA-485-A Standard (1998) * Application notes: Texas Instruments (SLLA272D), Analog Devices (AN-960), Maxim (AN-723)

RS-232

2026-04-30T21:11:02Z

Admin: Created page with "= RS-232 Standard Overview = == Introduction == '''RS-232''' (also known as '''TIA-232-F''' or '''EIA-232''') is one of the earliest serial communication standards, introduced in the 1960s for connecting data terminal equipment (DTE) and data communication equipment (DCE), such as computers and modems. Unlike RS-422 and RS-485, RS-232 uses '''single-ended signaling''' and is intended for short-distance, point-to-point communication. Despite its age, RS-232 remains wid..."

= RS-232 Standard Overview =

== Introduction ==
'''RS-232''' (also known as '''TIA-232-F''' or '''EIA-232''') is one of the earliest serial communication standards, introduced in the 1960s for connecting data terminal equipment (DTE) and data communication equipment (DCE), such as computers and modems.

Unlike RS-422 and RS-485, RS-232 uses '''single-ended signaling''' and is intended for short-distance, point-to-point communication.

Despite its age, RS-232 remains widely used in embedded systems, industrial equipment, laboratory instruments, and legacy communication interfaces.

== Core Principles ==
* Single-ended voltage signaling (referenced to ground)
* Point-to-point communication (1 transmitter ↔ 1 receiver per line)
* Full-duplex operation (separate TX and RX lines)
* Strict electrical voltage level definitions

== Key Features ==

; Single-Ended Signaling
: RS-232 uses one signal wire referenced to a shared ground. Unlike differential standards, it is more sensitive to noise and ground differences.

; Full-Duplex Communication
: Separate lines are used for transmit (TX) and receive (RX), allowing simultaneous bidirectional communication.

; Simple Wiring
: Minimum configuration typically requires 3 wires:
* TX
* RX
* GND

Optional control lines:
* RTS/CTS (flow control)
* DTR/DSR (modem control)
* DCD, RI (status signals)

; Short Distance Limitation
: Designed for cable lengths up to ~15 meters at standard speeds.

; Low Data Rate (Relative to Modern Standards)
* Typical speeds: 300 bps to 115.2 kbps
* Some implementations reach higher rates over short distances

== Electrical Characteristics ==

; Voltage Levels
RS-232 uses inverted voltage logic:

* Logic 1 (MARK): −3 V to −15 V
* Logic 0 (SPACE): +3 V to +15 V

Undefined range:
* −3 V to +3 V (invalid / noise region)

; Voltage Swing Requirement
* Drivers must produce at least ±5 V
* Typical output: ±12 V (legacy systems)

; Receiver Thresholds
* Detects logic levels above ±3 V
* High noise tolerance within specified limits

; Ground Reference
* All signals are referenced to a common ground (GND)
* Ground differences can cause communication failure

== Connector Standards ==

RS-232 does NOT define a single mandatory connector, but common implementations include:

; DB9 (DE-9)
Most widely used in modern systems:
* Compact
* Standardized de facto pinout in PCs

; DB25
Older standard used in legacy systems and industrial equipment

; Custom Headers
Common in embedded systems (pin headers, JST, etc.)

== Typical DB9 Pinout (DTE - PC Side) ==
{| class="wikitable"
! Pin !! Signal
|-
| 1 || DCD (Data Carrier Detect)
|-
| 2 || RXD (Receive Data)
|-
| 3 || TXD (Transmit Data)
|-
| 4 || DTR (Data Terminal Ready)
|-
| 5 || GND (Signal Ground)
|-
| 6 || DSR (Data Set Ready)
|-
| 7 || RTS (Request to Send)
|-
| 8 || CTS (Clear to Send)
|-
| 9 || RI (Ring Indicator)
|}

== Topology ==
RS-232 is strictly:

* One DTE ↔ One DCE (point-to-point)
* No multi-drop support
* No bus capability

Incorrect usage:
* Connecting multiple devices on same TX/RX lines → not supported

== Flow Control ==

RS-232 supports both hardware and software flow control:

; Hardware Flow Control
* RTS/CTS handshake
* DTR/DSR signaling

; Software Flow Control
* XON / XOFF protocol

Flow control prevents buffer overflow in slower devices.

== Signal Inversion ==
RS-232 logic is inverted compared to TTL:

* Idle (MARK) = negative voltage
* Active (SPACE) = positive voltage

This inversion is critical when interfacing with microcontrollers.

== Level Conversion ==
RS-232 cannot be connected directly to TTL/CMOS logic.

Common converters:
* MAX232 (most popular)
* SP3232
* ADM232

These convert:
* ±12 V RS-232 ↔ 0–3.3 V / 0–5 V TTL logic

== Noise Immunity ==
RS-232 is more susceptible to noise due to:
* Single-ended signaling
* Ground reference dependency
* Large voltage swings but no differential rejection

Recommended improvements:
* Short cable lengths
* Shielded cables
* Proper grounding

== Cable Characteristics ==
Recommended cable:
* Multi-core shielded cable
* Low capacitance per meter
* Straight-through or null-modem depending on application

Typical max distance:
* ~15 meters at 19.2 kbps
* Shorter distances at higher speeds

== Null Modem Concept ==
For direct device-to-device communication:

* TX ↔ RX crossover
* RTS ↔ CTS crossover (if used)
* GND shared

This configuration simulates DTE ↔ DCE connection.

== Advantages ==
* Extremely simple implementation
* Wide legacy support
* No complex termination required
* Low cost hardware
* Good for short-distance debugging and configuration

== Limitations ==
* Very short communication distance
* No multi-drop capability
* Sensitive to ground differences
* Low noise immunity compared to differential standards
* Obsolete in modern high-speed systems

== Applications ==
* Embedded system debugging (serial console)
* BIOS / firmware configuration
* Industrial machine configuration
* Laboratory instruments (oscilloscopes, analyzers)
* Legacy networking equipment
* GPS modules and serial sensors

== Comparison with RS-422 and RS-485 ==
{| class="wikitable"
! Feature !! RS-232 !! RS-422 !! RS-485
|-
| Signaling || Single-ended || Differential || Differential
|-
| Distance || ~15 m || ~1200 m || ~1200 m
|-
| Nodes || 1:1 || 1:10 || Multi-node (32–256)
|-
| Noise immunity || Low || High || Very high
|-
| Wiring complexity || Low || Medium || Medium
|-
| Use case || Local device link || Point-to-multipoint || Industrial networks
|}

== Common Mistakes ==
* Connecting RS-232 directly to TTL pins
* Ignoring voltage inversion
* Using long cables beyond specification
* Mixing ground references improperly
* Assuming multi-device support (not possible)
* Incorrect null-modem wiring

== Design Best Practices ==
* Use MAX232-class level shifters for MCU integration
* Keep cable lengths short (<15 m)
* Always connect ground reference
* Use shielded cables in noisy environments
* Verify pinout before connecting devices
* Use proper null-modem wiring when required

== Debugging Tips ==
* Measure voltage at idle (should be negative)
* Check TX/RX inversion if no communication
* Verify ground continuity
* Use loopback test (TX ↔ RX on same device)
* Check baud rate mismatch
* Validate null-modem wiring if direct connection used

== Conclusion ==
RS-232 remains a simple, reliable, and widely supported serial communication standard, especially in legacy systems and embedded debugging applications. While largely replaced by differential standards such as RS-422 and RS-485 in industrial environments, it continues to play an important role in low-level device communication and maintenance interfaces.

''This page serves as a reference for RS-232 electrical behavior, wiring, and practical implementation details in modern and legacy systems.''

== See Also ==
* [[RS-422]]
* [[RS-485]]
* [[Serial communication]]
* [[UART]]
* [[Differential signaling]]

== External References ==
* TIA/EIA-232-F Standard
* Maxim Integrated RS-232 interface guides
* Texas Instruments application notes on UART and level shifting

RS-422

2026-04-30T21:10:18Z

Admin: Created page with "= RS-422 Standard Overview = == Introduction == '''RS-422''' (also known as '''TIA/EIA-422-B''') is a balanced differential serial communication standard introduced to provide high-speed, long-distance, point-to-point communication. Unlike RS-485, RS-422 is primarily designed for '''single-driver, multi-receiver''' topologies rather than multi-drop networks. RS-422 defines only the physical layer and is protocol-agnostic. It is commonly used in industrial control syste..."

= RS-422 Standard Overview =

== Introduction ==
'''RS-422''' (also known as '''TIA/EIA-422-B''') is a balanced differential serial communication standard introduced to provide high-speed, long-distance, point-to-point communication. Unlike RS-485, RS-422 is primarily designed for '''single-driver, multi-receiver''' topologies rather than multi-drop networks.

RS-422 defines only the physical layer and is protocol-agnostic. It is commonly used in industrial control systems, broadcast equipment, telecommunications, and embedded systems where reliable long-distance unidirectional or bidirectional communication is required.

== Core Principles ==
* Differential signaling over twisted pair
* Point-to-multipoint topology (1 driver, up to 10 receivers)
* Full-duplex communication (separate TX and RX pairs)
* Fixed driver-receiver hierarchy (no bus contention)

== Key Features ==

; Balanced Differential Signaling
: RS-422 uses two wires per signal pair (A/B). Data is transmitted as a voltage difference, improving noise immunity and allowing long cable runs.

; Single Driver Architecture
: Only one active transmitter is allowed on the line at any time. Up to 10 receivers can listen simultaneously.

; Full-Duplex Operation
: Requires two twisted pairs:
* One pair for TX
* One pair for RX

; Long Distance Communication
: Supports cable lengths up to ~1200 meters at lower speeds.

; High Data Rates
: Typical operation:
* Up to 10 Mbps at short distances (~10–50 m)
* ~100 kbps at maximum distance (~1200 m)

; No Bus Arbitration Required
: Since only one driver exists, RS-422 does not require collision handling mechanisms.

== Electrical Characteristics ==

; Differential Voltage Levels
* Logic 1 / MARK: Vdiff > +200 mV
* Logic 0 / SPACE: Vdiff < -200 mV

; Driver Output Voltage
* Typically ±2 V to ±6 V differential

; Receiver Sensitivity
* Detects signals as low as ±200 mV

; Common-Mode Voltage Range
* Approximately -7 V to +7 V

; Load Capability
* One driver supports up to 10 unit loads (receivers)

== Bus Topology ==

RS-422 is NOT a shared multi-driver bus.

Correct topology:
* Point-to-multipoint (star-like or tree-like acceptable only for receivers)
* Single transmitting source

Incorrect usage:
* Multiple active transmitters on same pair → not supported

== Transmission Model ==
RS-422 uses separate differential pairs:

<pre>
TX (Driver Side)
A/B ------------------> Receiver 1
├----> Receiver 2
└----> Receiver 3

RX (Return Path - optional second pair)
A'/B' <---------------- Receiver/Remote device TX
</pre>

== Termination ==
Termination is used to reduce reflections in long or high-speed links.

* Typically 100–120 Ω resistor across differential pair
* Usually placed at receiver end only
* Full-duplex systems may require termination on both TX and RX pairs

Unlike RS-485, termination design is simpler due to single-driver architecture.

== Biasing ==
Biasing is generally NOT required in RS-422 systems because:
* There is always an active driver
* Line state is always defined

However, in idle or disconnected conditions:
* Failsafe receivers may be used
* Some systems still implement weak biasing for stability

== Grounding and Noise Immunity ==
RS-422 is differential but still requires proper grounding practices:

Recommended:
* Common reference ground between devices
* Shielded twisted pair cable in noisy environments
* Isolation for industrial or long-distance systems

Isolation options:
* Digital isolators
* Optocouplers

== Duplex Modes ==

; Full-Duplex (standard mode)
: Uses two differential pairs:
* TX pair (driver → receiver)
* RX pair (receiver → driver)

; Half-Duplex (non-standard usage)
: Can be implemented by sharing lines with external switching, but this is NOT native RS-422 behavior and reduces performance benefits.

== Comparison with RS-485 ==

{| class="wikitable"
! Feature !! RS-422 !! RS-485
|-
| Drivers || 1 || Multiple (multi-drop)
|-
| Receivers || Up to 10 || Up to 32–256
|-
| Topology || Point-to-multipoint || Multi-drop bus
|-
| Duplex || Full-duplex (4 wires) || Half or full-duplex
|-
| Collision handling || Not needed || Required (protocol-based)
|-
| Use case || Point links, broadcast systems || Industrial multi-node networks
|}

== Cable Requirements ==
Recommended cable characteristics:
* Twisted pair (mandatory)
* 100–120 Ω impedance
* Shielded for industrial environments
* Low capacitance for long distance operation

Common cables:
* CAT5e / CAT6 (acceptable)
* Industrial RS-422 rated cables

== Connectors ==
RS-422 does NOT define a connector standard.

Common implementations:
* DB9 (vendor-specific pinouts)
* Screw terminals
* RJ45 (custom assignments in structured systems)

== Advantages ==
* Long-distance communication
* High noise immunity
* High data rates
* Simple point-to-point architecture
* No multi-driver conflicts

== Limitations ==
* Not a true multi-drop bus
* Requires more wiring (4 wires full-duplex)
* Limited number of receivers (max ~10 standard)
* No addressing or arbitration
* Less flexible than RS-485 for networks

== Applications ==
* Industrial machine control links
* CNC systems
* Broadcast video equipment control
* Telecommunications equipment
* Serial data acquisition systems
* Embedded device interconnects
* Point-to-point sensor communication

== Common Mistakes ==
* Using RS-422 as a multi-drop bus (incorrect)
* Connecting multiple drivers together (causes damage)
* Incorrect termination placement
* Mixing RS-422 and RS-485 wiring assumptions
* Ignoring cable impedance

== Design Best Practices ==
* Use dedicated point-to-point links only
* Keep cable pairs consistent (TX/RX separation)
* Use proper termination at receiver end
* Match ground reference between devices
* Use shielding in noisy environments
* Validate signals with differential probing

== Typical Network Layout ==
<pre>
[Controller TX]
|
|---- Device 1 (RX)
|---- Device 2 (RX)
|---- Device 3 (RX)

(Return path optional via second pair)
</pre>

== Debugging Tips ==
* Verify TX/RX pair orientation
* Measure differential voltage (A-B)
* Ensure only one driver is active
* Check termination resistance (~120 Ω expected)
* Inspect for ground potential differences
* Use oscilloscope for signal integrity issues

== Conclusion ==
RS-422 is a robust and high-performance differential communication standard optimized for point-to-multipoint, single-driver systems. While less flexible than RS-485, it provides excellent signal integrity, long-distance capability, and high-speed operation in dedicated links.

Its simplicity makes it ideal for deterministic communication systems where network complexity is not required.

''This page provides a foundational overview of RS-422 and should be used alongside detailed topics such as termination, cable design, and differential signaling principles.''

== See Also ==
* [[RS-485]]
* [[RS-232]]
* [[Differential signaling]]
* [[Serial communication]]
* [[Transmission line theory]]

== External References ==
* TIA/EIA-422-B Standard
* Texas Instruments RS-422 application notes
* Analog Devices differential signaling guides
* Maxim Integrated interface documentation

RS-485:General disclaimer

2026-04-30T20:35:55Z

Admin:

= General Disclaimer =

== Purpose of This Disclaimer ==
This page outlines general limitations of responsibility regarding the content published on RS-485.COM. By using this site, you acknowledge and accept these terms.

== No Guarantee of Accuracy ==
RS-485.COM is a collaborative knowledge platform maintained by volunteers. While efforts are made to ensure technical accuracy and clarity, the content may:

* Contain errors or omissions
* Become outdated over time
* Vary in completeness depending on contributor expertise

No guarantee is made regarding the accuracy, reliability, or completeness of any information presented on the site.

== No Professional Advice ==
All content on RS-485.COM is provided for general informational and educational purposes only.

It does NOT constitute:
* Professional engineering advice
* Legal advice
* Certified technical guidance
* Safety-critical design approval

Users are responsible for verifying information and consulting qualified professionals before applying it in real-world or safety-critical systems.

== Use at Your Own Risk ==
Any reliance on information from RS-485.COM is strictly at your own risk.

RS-485.COM, its administrators, and contributors shall not be held liable for any direct or indirect damages, losses, system failures, or consequences resulting from the use or misuse of content on this site.

== External Links ==
RS-485.COM may include links to external websites for reference or additional information.

We do not:
* Control external content
* Guarantee external accuracy
* Endorse third-party websites

Users should review external sites’ own policies before use.

== Community Contributions ==
Content is created and maintained by a community of volunteers.

As a result:
* Articles may be edited, updated, or restructured by other contributors
* Information may evolve over time without prior notice
* Content may reflect differing interpretations or approaches

By contributing, users agree that their submissions may be freely modified to improve accuracy, consistency, and readability within the project.

== Licensing and Content Policy ==
All contributions must comply with the site's licensing requirements.

Accepted content must be:
* Original work, or
* Properly attributed public domain material, or
* Released under a compatible free license

RS-485.COM does not knowingly accept copyrighted material without authorization.

Specific licensing terms may be defined in the [[Project:Copyrights]] page.

== Limitation of Responsibility ==
To the maximum extent permitted by applicable law:

* RS-485.COM is not responsible for errors, data loss, or system damage resulting from use of its content
* Contributors and administrators are not individually liable for published material
* The platform is provided "as is" without warranties of any kind

== Changes to This Disclaimer ==
This disclaimer may be updated at any time without prior notice. Continued use of the site indicates acceptance of the current version.

----
''This page provides a general disclaimer for RS-485.COM and its content.''

RS-485:About

2026-04-30T20:34:51Z

Admin:

= About RS-485.COM =

== Overview ==
RS-485.COM is an open, collaborative knowledge platform dedicated to the RS-485 (TIA-485) communication standard and its ecosystem. Built on MediaWiki, the site enables engineers, developers, and enthusiasts to document, refine, and share technical knowledge in a transparent and structured way.

The project focuses on clarity, accuracy, and practical usefulness, combining theoretical explanations with real-world engineering experience.

== Purpose ==
The primary purpose of RS-485.COM is to serve as a centralized, vendor-neutral reference for RS-485 and related serial communication technologies. The site aims to reduce fragmentation of information by consolidating documentation, best practices, and implementation knowledge in one place.

== Mission ==
Our mission is to provide a comprehensive, freely accessible, and continuously improving resource that helps users:

* Understand the fundamentals of RS-485 communication
* Design reliable and robust systems
* Troubleshoot real-world issues
* Compare RS-485 with alternative technologies
* Apply the standard effectively across different industries

We strive to bridge the gap between formal specifications and practical implementation.

== Scope ==
RS-485.COM covers a broad range of topics, including but not limited to:

* Electrical characteristics and signal behavior
* Network topology (bus structure, termination, biasing)
* Hardware design considerations
* Protocols using RS-485 (e.g., Modbus RTU, proprietary systems)
* Interoperability and compatibility
* Diagnostics and fault analysis
* Modern adaptations and integrations

Related standards such as RS-232 and RS-422 are included where relevant for comparison and context.

== Content Structure ==
Content on RS-485.COM is organized into several key categories:

* '''Technical Documentation'''
In-depth explanations of signaling, voltage levels, timing, and physical layer behavior.

* '''Design Guidelines'''
Practical recommendations for wiring, grounding, shielding, termination, and EMC considerations.

* '''Applications'''
Real-world use cases in industrial automation, building systems, transportation, and embedded devices.

* '''Comparisons'''
Analytical comparisons with other communication standards and interfaces.

* '''Guides and Tutorials'''
Step-by-step instructions for setup, testing, debugging, and system integration.

* '''Reference Materials'''
Datasheets, schematics, timing diagrams, and curated external resources.

== Editorial Principles ==
RS-485.COM follows a set of core editorial principles:

* '''Accuracy''': Information should be technically correct and verifiable
* '''Neutrality''': Content should remain vendor-neutral and unbiased
* '''Clarity''': Complex topics should be explained in a clear and structured manner
* '''Practicality''': Emphasis on real-world applicability
* '''Transparency''': All changes are tracked and publicly visible

Content may be edited, expanded, or reorganized by other contributors to improve quality.

== Community ==
RS-485.COM is open to contributions from anyone with an interest in serial communication technologies.

Contributors can:
* Create and edit articles
* Improve existing documentation
* Add diagrams and examples
* Participate in discussions

All contributions are subject to community review and may be refined for accuracy, consistency, and readability.

Administrators provide moderation, maintenance, and enforcement of site policies.

== Independence ==
RS-485.COM is an independent, non-commercial project. It is not affiliated with any manufacturer, standards organization, or commercial entity.

The site does not promote specific products or vendors, and aims to remain a neutral technical resource.

== Copyright and Licensing ==
Contributors are responsible for ensuring that their submissions:

* Are original, or
* Are sourced from public domain or appropriately licensed materials

By submitting content, contributors agree that their work may be:

* Edited or reformatted
* Integrated with other content
* Retained as part of the site's revision history

Specific licensing terms may be defined on a dedicated [[Project:Copyrights]] page.

== Limitations ==
While efforts are made to ensure accuracy, RS-485.COM does not guarantee that all information is complete, up-to-date, or error-free.

Content is provided for educational and informational purposes only and should not replace professional engineering judgment or official documentation.

== Contact ==
For questions, suggestions, or collaboration inquiries:

* Use article discussion (talk) pages
* Visit the [[Project:Discussion]] page
* See the [[Contact]] page for additional methods

== Future Development ==
The project is continuously evolving. Planned improvements may include:

* Expanded protocol documentation
* More real-world case studies
* Interactive diagrams and tools
* Multilingual content

Contributions in these areas are especially welcome.

----
''This page defines the purpose, scope, and principles of RS-485.COM.''

RS-485:Privacy policy

2026-04-30T20:33:33Z

Admin:

= Privacy Policy =

== Introduction ==
This Privacy Policy explains how RS-485.COM ("we", "us", or "the site") collects, uses, stores, and protects information provided by contributors, registered users, and visitors. By accessing or using this site, you agree to the practices described below.

RS-485.COM is committed to transparency and data minimization. This wiki is a technical resource, not a commercial service. We do not sell, rent, or trade personal data.

== Definitions ==
* '''Visitor''': Anyone who reads wiki pages without logging in.
* '''Contributor''': Any user (registered or unregistered) who creates or modifies content. Unregistered contributors are identified by IP address.
* '''Registered User''': Anyone with an active account (username + email).
* '''Administrator''': Trusted user with access to certain site tools and logs.

== Information We Collect ==

=== User Contributions (Public) ===
Any text, images, files, or metadata you upload or edit on RS-485.COM. This includes:
* Page edits and summaries
* Uploaded files (diagrams, schematics, datasheets)
* Discussion/talk page comments

'''Note''': All contributions are publicly visible and permanently archived in page history (including your username or IP address).

=== Account Information ===
When you register, we collect:
* Username (publicly visible)
* Email address (private — used only for password reset, notifications, and administrative contact)
* Optional profile fields (e.g., "real name", "affiliation") — if provided, these become public

=== Technical Data (Automatically Collected) ===
For every visit, standard web server logs may record:
* IP address (retained for a limited period for security purposes and may be anonymized after approximately 30 days)
* Browser user agent
* Referring URL
* Timestamp and accessed pages
* Wiki action (view, edit, upload, login)

This data is used exclusively for:
* Security (detecting abuse, spam, brute-force attempts)
* Performance analysis (slow pages, error rates)
* Basic traffic statistics

=== Cookies ===
RS-485.COM uses essential cookies for:
* Login sessions (keeping you logged in)
* Preferences (editor settings, diff view mode)
* CSRF protection (security)

No tracking, advertising, or third-party cookies are used. You can disable cookies in your browser, but login and editing will become difficult or impossible.

== How We Use Information ==
We use collected information for the following legitimate purposes:

{| class="wikitable"
! Purpose !! Data Used
|-
| Maintaining the wiki || Contributions, account info
|-
| Attribution (who wrote what) || Username or IP, timestamp
|-
| Preventing spam and vandalism || IP addresses, user agent, edit patterns
|-
| Sending password reset emails || Email address
|-
| Notifying you of changes (watchlist) || Email address (opt-in)
|-
| Improving site performance || Technical logs
|-
| Complying with legal requests (e.g., court orders) || As required by law
|}

== Sharing of Information ==

=== Publicly Visible Information ===
* All page edits, file uploads, and talk page messages are visible to anyone on the internet.
* Page history stores your username or IP address indefinitely as part of the wiki's attribution system.

=== Third-Party Sharing ===
We do NOT share personal information with third parties except in the following cases:
* '''Legal requirement''': Valid court order, subpoena, or law enforcement request (we may notify affected users unless prohibited).
* '''Emergency''': To prevent serious harm where reasonably necessary.
* '''Spam/abuse prevention''': IP addresses may be shared with anti-spam services for abuse mitigation.

=== Service Providers ===
RS-485.COM may use:
* Web hosting provider (may have access to server logs under confidentiality obligations)
* Email service (for password resets and account-related communication)

Providers are selected with consideration for applicable data protection regulations (such as GDPR and CCPA where relevant).

== Data Retention ==

=== Contributions ===
* Retained permanently in page history (transparency and attribution).
* Removal is limited and performed only in exceptional cases (e.g., legal or privacy concerns).

=== Account Information ===
* Retained as long as your account exists.
* You may request account closure and removal of your email. Username remains for attribution purposes.

=== Technical Logs ===
* Stored for a limited period for security and operational purposes.
* May be anonymized or aggregated after initial retention.

=== Email Addresses ===
* Stored until account closure or removal request.
* Used only for account-related communication.

== Security ==

=== Account Security ===
* Passwords are securely hashed (never stored in plain text).
* Users are responsible for maintaining password confidentiality.
* Two-factor authentication (2FA) may be available depending on system capabilities.

=== Site Security ===
* HTTPS (TLS) encryption for all connections.
* Regular updates to software components.
* Administrative access is restricted and logged.

=== Limitations ===
No system is completely secure. Do NOT post:
* Passwords, API keys, or credentials
* Personal contact information (phone, address)
* Confidential or proprietary information

== Your Rights ==
Depending on your jurisdiction, you may have rights such as:

* '''Access''': Request a copy of your personal data
* '''Correction''': Update inaccurate information
* '''Deletion''': Request removal of account-related personal data (excluding public contributions)
* '''Restriction''': Limit certain processing
* '''Portability''': Receive your data in a structured format
* '''Objection''': Object to certain processing activities (note: attribution is inherent to wiki functionality)

To exercise these rights, contact administrators via the [[Contact]] page.

== Children's Privacy ==
RS-485.COM is not directed at children under 16. We do not knowingly collect personal data from minors. If such data is identified, it will be removed upon request.

== Third-Party Links ==
This site may contain links to external resources. We are not responsible for their privacy practices.

== Changes to This Policy ==
This Privacy Policy may be updated periodically. Significant changes may be announced via:
* Site notice or banner
* Main page announcement
* Email notification (if applicable)

The "Last updated" date reflects the current version.

== Enforcement ==
Violations of this policy (e.g., posting private information of others) may result in:
* Content removal
* Account suspension or ban
* Further action where required by law

== Contact ==
For privacy-related questions or requests:
* [[Project:Discussion]] page
* Direct contact via [[Contact]]

== Acknowledgment ==
By using RS-485.COM, you acknowledge and agree to this Privacy Policy.

----
''Last updated: 2026-04-30''
''Applies to RS-485.COM and its subdomains only.''

RS-485:Privacy policy

2026-04-30T20:31:34Z

Admin:

= Privacy Policy =

== Introduction ==
This Privacy Policy explains how RS-485.COM ("we", "us", or "the site") collects, uses, stores, and protects information provided by contributors, registered users, and visitors. By accessing or using this site, you agree to the practices described below.

RS-485.COM is committed to transparency and data minimization. This wiki is a technical resource, not a commercial service. We do not sell, rent, or trade personal data.

== Definitions ==
* '''Visitor''': Anyone who reads wiki pages without logging in.
* '''Contributor''': Any registered or unregistered user who edits, uploads, or creates content.
* '''Registered User''': Anyone with an active account (username + email).
* '''Administrator''': Trusted user with access to certain site tools and logs.

== Information We Collect ==

=== User Contributions (Public) ===
Any text, images, files, or metadata you upload or edit on RS-485.COM. This includes:
* Page edits and summaries
* Uploaded files (diagrams, schematics, datasheets)
* Discussion/talk page comments

'''Note''': All contributions are publicly visible and permanently archived in page history (including your username or IP address).

=== Account Information ===
When you register, we collect:
* Username (publicly visible)
* Email address (private — used only for password reset, notifications, and administrative contact)
* Optional profile fields (e.g., "real name", "affiliation") — if provided, these become public

=== Technical Data (Automatically Collected) ===
For every visit, standard web server logs record:
* IP address (anonymized after 30 days)
* Browser user agent
* Referring URL
* Timestamp and accessed pages
* Wiki action (view, edit, upload, login)

This data is used exclusively for:
* Security (detecting abuse, spam, brute-force attempts)
* Performance analysis (slow pages, error rates)
* Basic traffic statistics

=== Cookies ===
RS-485.COM uses essential cookies for:
* Login sessions (keeping you logged in)
* Preferences (editor settings, diff view mode)
* CSRF protection (security)

No tracking, advertising, or third-party cookies are used. You can disable cookies in your browser, but login and editing will become difficult or impossible.

== How We Use Information ==
We use collected information for the following legitimate purposes:

| Purpose | Data Used |
|---------|------------|
| Maintaining the wiki | Contributions, account info |
| Attribution (who wrote what) | Username or IP, timestamp |
| Preventing spam and vandalism | IP addresses, user agent, edit patterns |
| Sending password reset emails | Email address |
| Notifying you of changes (watchlist) | Email address (opt-in) |
| Improving site performance | Technical logs |
| Complying with legal requests (DMCA, court orders) | As required by law |

== Sharing of Information ==

=== Publicly Visible Information ===
* All page edits, file uploads, and talk page messages are visible to anyone on the internet.
* Page history stores your username or IP address forever (by design — wiki principle of attribution).

=== Third-Party Sharing ===
We do NOT share personal information with third parties except in the following rare cases:
* **Legal requirement**: Valid court order, subpoena, or law enforcement request (we will notify affected users unless prohibited).
* **Emergency**: To prevent death or serious physical harm.
* **Spam/abuse prevention**: IP addresses may be shared with public anti-spam databases (e.g., StopForumSpam) only for repeat vandalism.

=== Service Providers ===
RS-485.COM may use:
* Web hosting provider (has access to server logs under strict confidentiality)
* Email sending service (for password resets — no marketing)

All providers are GDPR/CCPA-compliant where applicable.

== Data Retention ==

=== Contributions ===
* Retained permanently in page history (transparency and attribution).
* Deletion is limited to revision deletion or suppression (administrator tools, used only for legal or privacy emergencies).

=== Account Information ===
* Retained as long as your account exists.
* You may request account closure and anonymization of your email (contact administrators). Username cannot be fully deleted due to attribution requirements.

=== Technical Logs ===
* Raw IP logs are kept for 30 days, then anonymized (last octet removed).
* Aggregate analytics (no IPs) retained indefinitely.

=== Email Addresses ===
* Stored until account is closed or you request removal.
* Never used for marketing or newsletters.

== Security ==

=== Account Security ===
* Passwords are hashed (never stored in plain text).
* You are responsible for using a strong, unique password.
* Enable two-factor authentication (2FA) if supported by your wiki engine.

=== Site Security ===
* HTTPS (TLS) encryption for all connections.
* Regular security updates to wiki software.
* Administrator access restricted and logged.

=== Limitations ===
No system is 100% secure. Do NOT post:
* Passwords, API keys, or credentials
* Personal contact information (phone, address, real name if you prefer pseudonymity)
* Trade secrets or confidential employer information

== Your Rights (GDPR, CCPA, and similar laws) ==
Depending on your jurisdiction, you may have the right to:

* **Access**: Request a copy of your personal data we hold.
* **Correction**: Fix inaccurate account information.
* **Deletion**: Request removal of your account and associated email (contributions remain under pseudonym).
* **Restriction**: Temporarily prevent processing of your data.
* **Portability**: Receive your data in a machine-readable format.
* **Object**: Object to specific processing (e.g., public attribution — not possible on a wiki).

To exercise these rights, contact administrators via the site's discussion page or email (address provided in [[Contact]]).

== Children's Privacy ==
RS-485.COM is a technical resource for engineers and hobbyists. It is not directed at children under 16. We do not knowingly collect personal information from minors. If you believe a child has provided personal data, contact us for removal.

== Third-Party Links ==
Our wiki pages may contain links to external sites (datasheets, forums, vendors). We are not responsible for their privacy practices. Always check their policies before providing personal information.

== Changes to This Policy ==
This Privacy Policy may be updated periodically. Significant changes (e.g., new data collection, sharing practices) will be announced:
* On the site's main page
* Via a notice on the wiki (banner for 30 days)
* By email to registered users (if the change affects their rights)

The "Last updated" date at the bottom of this page will always reflect the latest version.

== Enforcement ==
Violations of this Privacy Policy (e.g., deliberate doxxing, posting private information of others) may result in:
* Temporary or permanent account ban
* Removal of offending content (revision deletion)
* Reporting to relevant authorities if required by law

== Contact ==
For privacy-related questions, data requests, or concerns:
* Use the site's [[Project:Discussion]] page (public)
* Contact administrators via Special:EmailUser (if enabled)
* Or send a physical letter to the address listed on the [[Contact]] page

For urgent security or legal matters, use the contact methods described on the [[Contact]] page.

== Acknowledgment ==
By using RS-485.COM, you acknowledge that you have read, understood, and agreed to this Privacy Policy. If you do not agree, please do not register or edit — you may still read the wiki as a visitor.

----
''Last updated: 2026-04-30''
''This policy applies to RS-485.COM and its subdomains. It does not apply to third-party services or external links.''

File:RS-485 COM logo.png

2026-04-30T20:25:20Z

Admin:

Main Page

2026-04-30T20:03:28Z

Admin:

Main Page

2026-04-30T20:01:16Z

Admin:

= RS-485 Standard Overview =

== Introduction ==
RS-485 (also known as TIA-485-A or EIA-485) is a balanced differential serial communication standard introduced in 1983 by the Telecommunications Industry Association (TIA). It defines only the physical layer (electrical characteristics), making it protocol-agnostic and highly flexible.

RS-485 is widely adopted in industrial automation, embedded systems, building management, and instrumentation networks due to its robustness, long-distance capability, and resilience to electromagnetic interference (EMI).

Unlike higher-level communication protocols, RS-485 does not define data framing, addressing, or error handling — these are implemented by protocols such as Modbus, BACnet, or proprietary systems.

== Core Principles ==

Differential signaling over twisted pair
Multi-drop bus architecture
Half-duplex dominant communication (full-duplex optional)
Shared medium with controlled access (via protocol)

== Key Features ==

'''Balanced Differential Signaling'''
Uses two lines (A and B)
Signal is represented as voltage difference (Vdiff = VA − VB)
Rejects common-mode noise
'''Multipoint Capability'''
Standard supports 32 unit loads
Modern ICs allow 128, 256 or more nodes
Depends on receiver input impedance (1/8 UL, 1/4 UL, etc.)
'''Data Rate vs Distance Tradeoff'''
10 Mbps up to ~10–15 meters
1 Mbps up to ~100 meters
100 kbps up to ~1200 meters
'''Topology'''
Linear bus (daisy chain) is REQUIRED for stability
Stub length should be minimized (< 30 cm typical)
Star topology causes reflections and is strongly discouraged
'''Termination'''
120 Ω resistors at BOTH ends of the bus
Matches cable impedance → reduces reflections

== Electrical Characteristics ==

'''Differential Voltage'''
Logic 1 (MARK): Vdiff > +200 mV
Logic 0 (SPACE): Vdiff < -200 mV
Typical driver output: ±1.5V to ±5V
'''Common-Mode Voltage Range'''
-7 V to +12 V (receiver must tolerate this range)
'''Receiver Sensitivity'''
Must detect signals as low as ±200 mV
'''Driver Output'''
Must provide at least 1.5 V across 54 Ω load
'''Three-State Drivers'''
High-Z (tri-state) allows bus sharing
Enables multiple transmitters without conflict

== Bus Biasing (Failsafe) ==
Biasing ensures a defined logic state when no driver is active.

Typical implementation:

Pull-up resistor on line A
Pull-down resistor on line B

Example:

680 Ω – 4.7 kΩ resistors depending on system

Without biasing:

Bus floats → noise → false triggering

Modern transceivers often include '''failsafe receivers''' internally.

== Transmission Line Effects ==
At higher speeds or longer distances, RS-485 behaves as a transmission line:

Signal reflections occur if impedance mismatch exists
Propagation delay matters (~5 ns/m typical cable)
Ringing and overshoot can corrupt data

Best practices:

Always terminate correctly
Avoid stubs
Use controlled impedance cable (~120 Ω)

== Grounding and Isolation ==
RS-485 is differential but NOT fully immune to ground differences.

Options:

Shared signal ground (recommended for small systems)
Isolated transceivers for:
Industrial environments
Long-distance links
Different power domains

Isolation methods:

Optocouplers
Digital isolators (e.g., ADuM series)

== Half-Duplex vs Full-Duplex ==

'''Half-Duplex'''
Single pair (A/B)
One device transmits at a time
Most common implementation
'''Full-Duplex'''
Two differential pairs
Simultaneous TX/RX
Less common due to extra wiring

== Collision Avoidance ==
RS-485 does NOT include collision detection.

Handled by protocol:

Master-slave (e.g., Modbus RTU)
Token passing
Time-slot scheduling

Incorrect handling leads to:

Bus contention
Signal corruption
Potential driver damage

== Cable Selection ==
Recommended:

Twisted pair (mandatory)
Characteristic impedance: 100–120 Ω
Shielded cable for noisy environments

Examples:

CAT5e / CAT6 (works well)
Industrial RS-485 cable

== Connectors ==
Common connector types:

Screw terminals
DB9 (industrial legacy)
RJ45 (structured cabling reuse)

Pinout is NOT standardized → always verify documentation.

== Advantages ==

High immunity to EMI/RFI
Long cable lengths
Multi-drop capability
Low cost implementation
Widely supported hardware

== Limitations ==

No built-in protocol
Requires careful wiring
Sensitive to topology errors
No automatic arbitration
Ground potential differences can cause issues

== Applications ==

Industrial automation (Modbus RTU, PROFIBUS DP)
PLC and SCADA systems
Building automation (HVAC, lighting, access control)
Energy meters and smart grids
CNC machines and robotics
Remote sensor networks
Elevator and security systems

== Comparison with Other Standards ==
{| class="wikitable"

! Feature !! RS-232 !! RS-422 !! RS-485
Signaling
-
Max Distance
-
Nodes
-
Noise Immunity
-
Duplex
}

== Common Mistakes ==

Missing termination resistors
Using star topology
Long stubs
No biasing resistors
Mixing A/B polarity
Ignoring grounding
Using wrong cable (non-twisted)

== Design Best Practices ==

Use termination ONLY at bus ends
Keep stubs as short as possible
Add biasing resistors if needed
Use isolated transceivers in harsh environments
Validate signal with oscilloscope
Label A/B clearly (vendors may swap naming!)

== Typical Network Layout ==

Linear bus
Termination at both ends
Devices connected along the line
Optional biasing at one location

== Debugging Tips ==

Measure differential voltage (A-B)
Check idle state (should be stable)
Look for reflections on oscilloscope
Verify polarity consistency
Disconnect nodes to isolate faults

== Conclusion ==
RS-485 remains one of the most reliable and widely used physical layer standards for industrial and embedded communication. Its simplicity, robustness, and flexibility ensure its continued relevance even in modern systems alongside Ethernet and wireless technologies.

Proper design — especially topology, termination, and grounding — is critical to achieving stable and high-performance communication.

''This page serves as the central reference for RS-485 on RS-485.COM and links to detailed subtopics such as termination, biasing, isolation, and protocol implementations.''

Main Page

2026-04-30T19:59:14Z

Admin:

= RS-485 Standard Overview =

== Introduction ==
RS-485, also known as TIA-485-A or EIA-485, is a standard introduced in 1983 that defines the electrical characteristics of drivers and receivers for use in serial communications systems. It is widely used in industrial control systems, building automation, and telecommunications due to its robustness in noisy environments and ability to support long-distance communication.

== Key Features ==
* '''Balanced Differential Signaling''': Uses a pair of wires (A and B) to transmit data, providing noise immunity.
* '''Multipoint Capability''': Supports up to 32 unit loads (expandable with modern transceivers).
* '''Data Rate and Distance''': Up to 10 Mbps at short distances; up to 1200 meters at lower speeds.
* '''Topology''': Recommended bus (daisy-chain) topology; star and ring topologies are discouraged due to signal reflections.
* '''Termination''': Requires termination resistors (typically 120 Ω) at both ends of the bus to prevent signal reflections.

== Electrical Characteristics ==
* '''Voltage Levels''': Logical 1 when differential voltage > +200 mV; logical 0 when < -200 mV.
* '''Common-Mode Range''': Tolerates -7 V to +12 V.
* '''Three-State Drivers''': Allows multiple transmitters on the same bus by enabling/disabling drivers.

== Advantages ==
* High noise immunity due to differential signaling.
* Long-distance communication (up to 1200 meters).
* Cost-effective twisted-pair cabling.
* Supports half-duplex and full-duplex communication.

== Applications ==
* Industrial automation (Modbus RTU, PROFIBUS).
* Building automation (HVAC, lighting control).
* Telecommunications infrastructure and remote sensor networks.

== Comparison with Other Standards ==
* '''RS-232''': Single-ended, shorter distance, less noise immunity.
* '''RS-422''': Similar differential signaling but limited to point-to-point connections.

== Practical Considerations ==
* '''Biasing''': Ensures a known idle state on the bus.
* '''Repeaters''': Used to extend distance or support star topologies.
* '''Cable Selection''': Twisted-pair cables with characteristic impedance around 120 Ω.

== Conclusion ==
RS-485 remains a cornerstone of industrial and automation communication systems due to its robustness, scalability, and cost-effectiveness. Its ability to handle noisy environments and long distances makes it indispensable in modern digital communication networks.

----
''This page provides a comprehensive overview of RS-485 for the RS-485.COM wiki.''

Main Page

2026-04-30T19:57:18Z

Admin:

{{Short description|Multidrop serial communication standard}}

{{Infobox fieldbus protocol
|name = TIA-485-A (Revision of EIA-485)
|standard = ANSI/TIA/EIA-485-A-1998 Approved: March 3, 1998 Reaffirmed: December 7, 2012
|governing_body =
|type_of_network =
|physical_media =[[Balanced line|Balanced interconnecting cable]]
|network_topology =[[Point-to-point_(telecommunications)|Point-to-point]], [[Multidrop bus|multi-dropped]], [[Bus network|multi-point]]
|maximum_devices =At least 32 unit loads
|maximum_distance = Not specified
|maximum_speed =
|device_addressing =
|mode_of_operation =Different receiver levels: binary 1 (OFF) (Voa–Vob < −200 mV) binary 0 (ON) (Voa–Vob > +200 mV)
|maximum_baud_rate =
|maximum_binary_rate =
|voltage =
|mark1 =
|space0 =
|available_signals =A, B, C
|connector_types =Not specified
}}
[[File:Honeywell 4600g - board 1 - Texas Instruments VN08-9677.jpg|thumb|Texas Instruments VN08 (SN75HVD08) - Wide Supply Range RS-485 Transceiver]]
'''RS-485''', also known as '''TIA-485(-A)''' or '''EIA-485''', is a standard, originally introduced in 1983, defining the electrical characteristics of drivers and receivers for use in [[serial communication]]s systems. Electrical signaling is [[balanced]], and [[Telecommunications link#Multipoint|multipoint]] systems are supported. The standard is jointly published by the [[Telecommunications Industry Association]] and [[Electronic Industries Alliance]] (TIA/EIA). Digital communications networks implementing the standard can be used effectively over long distances and in [[Electromagnetic compatibility|electrically noisy environments]]. Multiple receivers may be connected to such a network in a linear, [[multidrop bus]]. These characteristics make RS-485 useful in [[industrial control system]]s and similar applications.

== Overview ==
RS-485 supports inexpensive [[local network]]s and [[multidrop communications]] links, using the same [[differential signaling]] over [[twisted pair]] as [[RS-422]]. It is generally accepted that RS-485 can be used with data rates up to 10 [[bitrate|Mbit/s]]{{efn|Under some conditions it can be used up to [[data transmission]] speeds of 64 Mbit/s.<ref>{{citation |title=RS-485 Reference Guide |url=http://www.ti.com/lit/sg/slyt484a/slyt484a.pdf |archive-url=https://web.archive.org/web/20180517101401/http://www.ti.com/lit/sg/slyt484a/slyt484a.pdf |archive-date=2018-05-17}}</ref>}} or, at lower speeds, distances up to {{convert|1200|m|abbr=on|-3}}.<ref>{{cite web|url=https://www.analog.com/en/resources/technical-articles/full-guide-to-serial-communication-protocol-and-our-rs485.html|title=How Far and How Fast Can You Go with RS-485? - Application Note – Maxim|website=www.maximintegrated.com}}</ref> As a [[rule of thumb]], the speed in bit/s multiplied by the length in meters should not exceed 108. Thus a {{nowrap|50-meter}} cable should not signal faster than {{nowrap|2 Mbit/s}}.<ref name=slla070d>{{cite tech report |url=http://focus.ti.com/lit/an/slla070d/slla070d.pdf |format=pdf |website=[[Texas Instruments]] |first=Manny |last=Soltero |first2=Jing |last2=Zhang |first3=Chris |last3=Cockril |first4=Kevin |last4=Zhang |first5=Clark |last5=Kinnaird |first6=Thomas |last6=Kugelstadt |title=RS-422 and RS-485 Standards Overview and System Configurations, Application Report |id=SLLA070D |date=May 2010 |orig-year=2002}}</ref>

In contrast to RS-422, which has a driver circuit which cannot be switched off, RS-485 drivers use [[three-state logic]] allowing individual transmitters to be deactivated. This allows RS-485 to implement [[linear bus topology|linear bus topologies]] using only two wires. The equipment located along a set of RS-485 wires are interchangeably called nodes, stations or devices.<ref>{{cite book |author=Electronic Industries Association |series=EIA Standard RS-485 |title=Electrical Characteristics of Generators and Receivers for Use in Balanced Multipoint Systems |year=1983 |oclc=10728525}}{{page needed|date=October 2011}}</ref> The recommended arrangement of the wires is as a connected series of point-to-point (multidropped) nodes, i.e. a line or [[Bus network|bus]], not a [[Star network|star]], [[Ring network|ring]], or multiply connected network. Star and ring topologies are not recommended because of signal reflections or excessively low or high termination impedance. If a star configuration is unavoidable, special RS-485 repeaters are available which bidirectionally listen for data on each span and then retransmit the data onto all other spans.

[[File:Rs485-bias-termination.svg|thumb|Typical bias network together with termination. Biasing and termination values are not specified in the RS-485 standard. However, bias resistors are commonly not recommended any more by component suppliers.]]
Ideally, the two ends of the cable will have a [[termination resistor]] connected across the two wires. Without termination resistors, [[signal reflection]]s off the unterminated end of the cable can cause data corruption. Termination resistors also reduce electrical noise sensitivity due to the [[Brownian noise|lower impedance]].{{elucidate|discuss=[[Talk:Electrical termination#Noise sensitivity]]|date=July 2018}} The value of each termination resistor should be equal to the cable [[characteristic impedance]] (typically, 120 ohms for twisted pairs). The termination also includes pull up and pull down resistors to establish bias for each data wire for the case when the lines are not being driven by any device. This way, the lines will be biased to known voltages and nodes will not interpret the noise from undriven lines as actual data; without biasing resistors, the data lines float in such a way that electrical noise sensitivity is greatest when all device stations are silent or unpowered.<ref>{{cite web | title = Application Note 847 FAILSAFE Biasing of Differential Buses | url = http://www.ti.com/lit/an/snla031/snla031.pdf | publisher = [[Texas Instruments]] |year = 2011}}</ref>

== Standard ==
The EIA once labeled all its standards with the prefix RS ([[Recommended Standard]]), but the EIA/TIA officially replaced RS with EIA/TIA to help identify the origin of its standards. The EIA has officially disbanded and the standard is now maintained by the TIA as TIA-485, but engineers and applications guides continue to use the RS-485 designation.<ref>{{cite web | url = https://www.eetimes.com/trim-the-fat-off-rs-485-designs | title = Trim-the-fat-off-RS-485-designs | publisher = [[EE Times]] | year = 2000}}</ref> The initial edition of EIA RS-485 was dated April 1983.<ref>"EIA Standard RS 485 Electrical Characteristics of Generators and Receivers for Use in Balanced Digital Multipoint Systems", reproduced in "Data Communications Standards Library", Telebyte Technology Inc., Greenlawn, New York 1985.</ref>

RS-485 only specifies the electrical characteristics of the generator and the receiver: the [[physical layer]]. It does not specify or recommend any [[communications protocol]]; Other standards define the protocols for communication over an RS-485 link. The foreword to the standard references ''The Telecommunications Systems Bulletin TSB-89'' which contains application guidelines, including data signaling rate vs. cable length, stub length, and configurations.

Section 4 defines the electrical characteristics of the generator (transmitter or driver), receiver, transceiver, and system. These characteristics include: definition of a unit load, voltage ranges, open-circuit voltages, thresholds, and transient tolerance. It also defines three generator interface points (signal lines); A, B and C. The data is transmitted on A and B. C is a ground reference. This section also defines the logic states 1 (off) and 0 (on), by the polarity between A and B terminals. If A is negative with respect to B, the state is binary 1. The reversed polarity (A positive with respect to B) is binary 0. The standard does not assign any logic function to the two states.

== Full duplex operation ==
RS-485, like RS-422, can be made [[duplex (telecommunications)|full-duplex]] by using four wires.<ref>{{citation |title=RS-485 Connections FAQ |url=https://www.advantech.com/en-eu/resources/white-papers/02cb2f4e-4fb2-4a87-be3b-508325bd61d6 |publisher=Advantech B+B SmartWorx |access-date=2023-09-15}}</ref> Since RS-485 is a multi-point specification, however, this is not necessary or desirable in many cases. RS-485 and RS-422 can interoperate with certain restrictions.<ref>{{citation |title=What is the difference between RS422 communication and RS485 communication? |url=https://www.brainboxes.com/faq/what-is-the-difference-between-rs422-communication-and-rs485-com |publisher=Brainboxes LLC |access-date=2024-10-27}}</ref>{{fv|reason=Although the opportunity is apparent to the skilled reader, there is no mention of interoperability in the source.|date=October 2024}}

==Converters and repeaters==
Converters between RS-485 and [[RS-232]] are available to allow a [[personal computer]] to communicate with remote devices. By using [[repeater]]s very large RS-485 networks can be formed.

==Network topology==
TSB-89A, Application Guidelines for TIA/EIA-485-A does not recommend using star topology, as doing so may lead to long stubs (branches of the star), which can cause signal reflections that make data transmission unreliable.<ref>{{citation |url=https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/00-138-00-00-00-33-63-91/TSB_2D00_89_2D00_A.pdf |title=TSB-89A, Application Guidelines for TIA/EIA-485-A |access-date=2019-04-06}}</ref>

==Protocols==
RS-485 does not define a [[communication protocol]]; merely an electrical interface. Although many applications use RS-485 signal levels, the speed, format, and protocol of the data transmission are not specified by RS-485. Interoperability of even similar devices from different manufacturers is not assured by compliance with the signal levels alone.

== Applications ==
RS-485 signals are used in a wide range of computer and automation systems.

In a computer system, [[SCSI]]-2 and SCSI-3 may use RS-485 to implement the [[physical layer]] for data transmission between a controller and a disk drive.

RS-485 is used for low-speed data communications in commercial aircraft cabins' [[vehicle bus]]. It requires minimal wiring and can share the wiring among several seats, reducing weight.

These are used in [[programmable logic controller]]s and on factory floors. RS-485 is used as the physical layer underlying [[List of automation protocols|many standard and proprietary automation protocols]] used to implement [[industrial control systems]], including the most common versions of [[Modbus]] and [[Profibus]]. '''{{visible anchor|DH 485}}''' is a proprietary communications protocol used by [[Allen-Bradley]] in their line of industrial control units. Utilizing a series of dedicated interface devices, it allows PCs and industrial controllers to communicate.<ref>{{cite web
|url=http://www.ab.com/en/epub/catalogs/12762/2181376/214372/1535907/3404063/ |archive-url=https://web.archive.org/web/20120310095800/http://www.ab.com/en/epub/catalogs/12762/2181376/214372/1535907/3404063/ |archive-date=2012-03-10 |title=DH-485 Industrial Local Area Network Overview |publisher=[[Rockwell Automation]] |access-date=10 September 2010}}</ref> Since it is differential, it resists electromagnetic interference from motors and welding equipment.

In theatre and performance venues, RS-485 networks are used to control lighting and other systems using the [[DMX512]] protocol. RS-485 serves as a physical layer for the [[AES3]] digital audio interconnect.

RS-485 is also used in [[building automation]] as the simple bus wiring and long cable length is ideal for joining remote devices. It may be used to control video surveillance systems or to interconnect security control panels and devices such as access control card readers.

It is also used in [[Digital Command Control]] (DCC) for [[model railway]]s. The external interface to the DCC command station is often RS-485 used by hand-held controllers<ref>[http://www.lenzusa.com/techinfo/xpressnetfaq.htm lenzusa.com], XpressNET FAQ, accessed July 26, 2015 {{Webarchive|url=https://web.archive.org/web/20171117050219/http://www.lenzusa.com/techinfo/xpressnetfaq.htm |date=November 17, 2017 }}</ref> or for controlling the layout in a networked PC environment. [[8P8C modular connector]]s are used in this case.<ref>[http://www.bidib.org/bidibus/bidibus_e.html#T2 bidib.org], "BiDiBus, a Highspeed-Bus for model-railways", accessed July 26, 2015.</ref>

== Signals ==
[[File:RS-485 transceiver.svg|thumb|RS-485 interface consisting of a line driver and line receiver. Single-ended signals are shown on the left. The RS-485 bus, shown on the right, has three signals consisting of a differential pair and signal common.]]
{| class="wikitable"
|+RS-485 signal states
!Signal
!Mark (logic 1)
!Space (logic 0)
|-
|A
|Low
|High
|-
|B
|High
|Low
|}

The RS-485 differential line consists of two signals:
* '''A''', which is low for logic 1 and high for logic 0 and,
* '''B''', which is high for logic 1 and low for logic 0.

Because a [[Mark and space|mark]] (logic 1) condition is traditionally represented (e.g. in RS-232) with a negative voltage; and [[Mark and space|space]] (logic 0) represented with a positive one, A may be considered the ''non-inverting'' signal and B as inverting. The RS-485 standard states (paraphrased):<ref>{{cite web | url = http://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf | title = Polarity conventions | publisher = [[Texas Instruments]] | year = 2003}}</ref>
* For an off, mark or logic 1 state, the driver's A terminal is negative relative to the B terminal.
* For an on, space or logic 0 state, the driver's A terminal is positive relative to the B terminal.{{efn|There is an apparent typo in this statement as both states in the standard are designated ''binary 1''. It is clear in the figure that follows that the off state corresponds to binary 1 and on corresponds to binary 0.}}

The truth tables of most popular devices, starting with the SN75176, show the output signals inverted. This is in accordance with the A/B naming used by most differential transceiver manufacturers, including:
* [[Intersil]], as seen in their data sheet for the ISL4489 transceiver<ref>{{cite web | url = http://www.intersil.com/data/fn/fn6074.pdf |url-status=dead |archive-url=https://web.archive.org/web/20041204120233/http://www.intersil.com/data/fn/fn6074.pdf | archive-date=2004-12-04 | title = Data Sheet FN6074.3: ±15kV ESD Protected, 1/8 Unit Load, 5V, Low Power, High Speed and Slew Rate Limited, Full Duplex, RS-485/RS-422 Transceivers | publisher = [[Intersil Corporation]] | date = 28 April 2006}}</ref>
* [[Maxim Integrated|Maxim]], as seen in their data sheet for the MAX483 transceiver<ref>{{cite web | url = http://datasheets.maxim-ic.com/en/ds/MAX1487-MAX491.pdf | title = Data Sheet 19-0122 – MAX481/MAX483/MAX485/MAX487–MAX491/MAX1487: Low-Power, Slew-Rate-Limited RS-485/RS-422 Transceivers | date = September 2009 | publisher = [[Maxim Integrated]] | access-date = 2009-06-17 | archive-date = 2009-09-27 | archive-url = https://web.archive.org/web/20090927022738/http://datasheets.maxim-ic.com/en/ds/MAX1487-MAX491.pdf | url-status = dead }}</ref> and for the new generation 3.3v micro controller the MAX3485
* [[Linear Technology]], as seen in their datasheet for the LTC2850, LTC2851, LTC2852<ref>{{cite web | url = http://cds.linear.com/docs/Datasheet/285012fd.pdf |archive-url=https://web.archive.org/web/20110302044542/http://www.linear.com/docs/Datasheet/285012fd.pdf |archive-date=2011-03-02 | title = LTC2850/LTC2851/LTC2852 3.3V 20Mbps RS485/RS422 Transceivers | publisher = [[Linear Technology Corporation]]| year = 2007}}</ref>
* [[Analog Devices]], as seen in their datasheet for the ADM3483, ADM3485, ADM3488, ADM3490, ADM3491<ref>{{cite web | url = http://www.analog.com/static/imported-files/data_sheets/ADM3483_3485_3488_3490_3491.pdf | title = ADM3483/ADM3485/ADM3488/ADM3490/ADM3491 (Rev. E) | publisher = [[Analog Devices, Inc.]] | date = 22 November 2011}}</ref>
* [[FTDI]], as seen in their datasheet for the USB-RS485-WE-1800-BT<ref>{{cite web | url = http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_USB_RS485_CABLES.pdf | title = USB to RS485 Serial Converter Cable Datasheet | publisher = [[Future Technology Devices International Ltd]] | date = 27 May 2010}}</ref>
These manufacturers all agree on the meaning of the standard, and their practice is in widespread use. The issue also exists in programmable logic controller applications.{{efn|With [[Modbus]], [[BACnet]] and [[Profibus]], A/B labeling refers '''A''' as the ''negative green'' wire and '''B''' as the ''positive red'' wire, in the definition of the D-sub connector and M12 circular connector, as can be seen in Profibus guides.<ref>{{cite web | url = http://www.profibus.com/download | title = Profibus Interconnection Guideline (PDF) |version=1.4 |date=January 2007 |publisher = P International |page=7 |url-access=registration }}</ref><ref>{{cite web | url = https://cache.industry.siemens.com/dl/files/591/35222591/att_105793/v1/mn_pbnets_76.pdf | title = SIMATIC NET Profibus Network Manual (PDF) |date=April 2009 |publisher = Siemens|page=157}}</ref> As long as standard excludes logic function of the generator or receiver,<ref>{{cite web | url = https://en.wikibooks.org/wiki/Serial_Programming/RS-485#RS-485 | title = RS-485 Technical Manual, TIA-485 section | publisher = Wikibooks}}</ref> it would make sense '''A''' (green, negative) is higher than '''B''' (red, positive). However this contradicts the facts that an idle '''mark''' state is a logical '''one''' ''and'' the termination polarization puts '''B''' at a higher voltage in Profibus guidelines.<ref>{{cite web | url = http://www.profibus.com/download | title = Profibus Interconnection Guideline (PDF) |version=1.4 |date=January 2007 |publisher = P International |page=8 |url-access=registration }}</ref> That so-called 'Pesky Polarity' problem <ref>{{cite web | url = https://en.wikibooks.org/wiki/Serial_Programming/RS-485#.5BThat_Pesky.5D_Polarity | title = RS-485 Technical Manual, That Pesky Polarity | publisher = Wikibooks}}</ref> raised confusion which made authors think '''A''' is inverting within the TIA-485-A standard itself <ref>{{cite web | url = http://www.chipkin.com/rs485-polarity-issues | title = RS485 Polarity Issues | publisher = Chipkins Automation Systems}}</ref> and advise to swap what is '''A''' and '''B''' in drivers and line labeling as can be read in a section of an application bulletin: "Design Consideration #3: Sometimes Bus Node '''A''' Isn’t Really Bus Node '''A'''".<ref>{{cite web | url = http://www.nve.com/Downloads/ab19.pdf | title = Application Bulletin AB-19, Profibus Compliance: A Hardware Design Guide | publisher = NVE Corporation | year = 2010}}</ref> It is now a common design decision to make this inversion which involves the following polarity chain: [[UART]]/[[Microcontroller unit|MCU]] idle → TTL/CMOS {{=}} +5 V → Line '''B''' voltage > Line '''A''' voltage, implying '''A''', the green wire, is indeed connected to the driver ''inverting'' signal, as seen in a whitepaper.<ref>{{cite web | url = https://www.advantech.com/th-th/resources/white-papers/2fde048f-f42c-439b-b0a9-485cd548f172 | title = White paper: Polarities for Differential Pair Signals | publisher = Advantech B+B SmartWorx}}</ref>}} Care must be taken when using A/B naming. Alternate nomenclature is often used to avoid confusion surrounding the A/B naming:
* TX+/RX+ or D+ as alternative for B (high for mark i.e. idle)
* TX−/RX− or D− as alternative for A (low for mark i.e. idle)

RS-485 standard conformant drivers provide a differential output of a minimum 1.5 V across a 54-Ω load,
whereas standard conformant receivers detect a differential input down to 200 mV. The two values provide
a sufficient margin for a reliable data transmission even under severe signal degradation across the cable
and connectors. This robustness is the main reason why RS-485 is well suited for long-distance
networking in noisy environment.<ref>{{cite web | url = https://www.ti.com/lit/an/slla272c/slla272c.pdf | title = The RS-485 Design Guide | publisher = Texas Instruments}}</ref>

In addition to the '''A''' and '''B''' connections, an optional, third connection may be present (the TIA standard requires the presence of a common return path between all circuit grounds along the balanced line for proper operation)<ref>ANSI/TIA/EIA-485-A, page 15, A.4.1</ref> called '''SC''', '''G''' or '''reference''', the common signal reference ground used by the receiver to measure the A and B voltages. This connection may be used to limit the [[common-mode signal]] that can be impressed on the receiver inputs. The allowable common-mode voltage is in the range −7 V to +12 V, i.e. ±7 V on top of the 0–5 V signal range. Failure to stay within this range will result in, at best, signal corruption, and, at worst, damage to connected devices.

Care must be taken that an SC connection, especially over long cable runs, does not result in an attempt to connect disparate grounds together – it is wise to add some [[current limiting]] to the SC connection. Grounds between buildings may vary by a small voltage, but with very low impedance and hence the possibility of catastrophic currents – enough to melt signal cables, PCB traces, and transceiver devices.

RS-485 does not specify any connector or pinout. Circuits may be terminated on [[screw terminal]]s, [[D-subminiature]] connectors, or other types of connectors.

The standard does not discuss cable shielding but makes some recommendations on preferred methods of interconnecting the signal reference common and equipment case grounds.

== Waveform example ==
The diagram below shows [[Electric potential|potentials]] of the A (blue) and B (red) pins of an RS-485 line before, during, and after transmission of one byte (0xD3, least significant bit first) of data using an [[asynchronous start-stop]] method.

[[File:RS-485 waveform.svg|thumb|upright=1.35|left|B (U+, inverting) signal shown in red, A (U−, non-inverting) signal shown in blue]]
{{clear}}

== See also ==
* [[List of network buses]]

== Notes ==
{{Notelist}}

== References ==
{{Reflist}}

== External links ==
{{Wikibooks|Serial Programming:RS-485 Technical Manual}}
* [https://store.accuristech.com/standards/tia-tia-485-a?product_id=2591400 "TIA-485-A"] - purchase official standard
* [https://www.analog.com/en/resources/technical-articles/rs485-cable-specification-guide--maxim-integrated.html "Guidelines for Proper Wiring of an RS-485 Network"] - Maxim
* [https://www.analog.com/en/resources/app-notes/an-960.html "RS-485 Circuit Implementation Guide"] - Analog
* [https://www.ti.com/lit/ta/sszt500/sszt500.pdf "RS-485 Frequently Asked Questions"] - TI
* [https://www.renesas.com/en/document/apn/an1986-external-fail-safe-biasing-rs-485-networks "External Fail-Safe Biasing of RS-485 Networks"] - Renesas
* [http://www.ti.com/lit/an/slyt324/slyt324.pdf "RS-485 Passive Failsafe for an Idle Bus"] - TI, and [https://dcs-bios.a10c.de/rs485-resistors.html RS-485 Resistor Calculator]

{{Computer-bus}}

[[Category:Serial buses]]
[[Category:Telecommunications-related introductions in 1998]]
[[Category:EIA standards]]
[[Category:Serial digital interface]]

RS-485:General disclaimer

2026-04-30T19:54:59Z

Admin: Created page with "= General Disclaimer = == No Guarantee of Accuracy == RS-485.COM is a collaborative project. While contributors strive to provide accurate and reliable information, the content may contain errors, omissions, or outdated material. RS-485.COM makes no guarantees regarding the completeness or correctness of any information. == No Professional Advice == The information provided on RS-485.COM is for general educational and informational purposes only. It should not be consi..."

= General Disclaimer =

== No Guarantee of Accuracy ==
RS-485.COM is a collaborative project. While contributors strive to provide accurate and reliable information, the content may contain errors, omissions, or outdated material. RS-485.COM makes no guarantees regarding the completeness or correctness of any information.

== No Professional Advice ==
The information provided on RS-485.COM is for general educational and informational purposes only. It should not be considered professional engineering, legal, or technical advice. Users should consult qualified professionals before relying on any information for critical applications.

== Liability ==
RS-485.COM, its contributors, and administrators are not responsible for any damages, losses, or consequences resulting from the use of information found on this site. Use of the content is entirely at your own risk.

== External Links ==
This site may contain links to external websites. RS-485.COM does not control and is not responsible for the content of external sites.

== Community Contributions ==
All contributions are made by volunteers. Content may be edited, altered, or removed by other contributors. By submitting material, you agree that it may be freely modified to improve accuracy and clarity.

== Licensing ==
Content on RS-485.COM must comply with licensing rules. Contributions should be original, public domain, or freely licensed. RS-485.COM does not accept copyrighted material without permission.

----
''This page provides the general disclaimer for RS-485.COM.''

RS-485:Privacy policy

2026-04-30T19:54:26Z

Admin: Created page with "= Privacy Policy = == Introduction == This Privacy Policy explains how RS-485.COM collects, uses, and protects information provided by contributors and visitors. By using this site, you agree to the practices described below. == Information We Collect == * '''User Contributions''': Any text, images, or files you upload or edit on RS-485.COM. * '''Account Information''': Username, email address, and optional profile details. * '''Technical Data''': Log files, IP address..."

= Privacy Policy =

== Introduction ==
This Privacy Policy explains how RS-485.COM collects, uses, and protects information provided by contributors and visitors. By using this site, you agree to the practices described below.

== Information We Collect ==
* '''User Contributions''': Any text, images, or files you upload or edit on RS-485.COM.
* '''Account Information''': Username, email address, and optional profile details.
* '''Technical Data''': Log files, IP addresses, browser type, and usage statistics.

== How We Use Information ==
* To maintain and improve the RS-485.COM wiki.
* To ensure compliance with community guidelines and licensing requirements.
* To provide attribution for contributions.
* To analyze site usage and improve performance.

== Sharing of Information ==
* Contributions are publicly visible and may be edited by others.
* Account information is not shared with third parties except as required by law.
* Technical data may be used internally for security and analytics.

== Data Retention ==
* Contributions remain part of the wiki history.
* Account information is retained as long as the account is active.
* Technical logs are stored temporarily for maintenance and security purposes.

== Security ==
RS-485.COM takes reasonable measures to protect user information. However, no system is completely secure, and contributors should avoid posting sensitive personal data.

== Licensing ==
All contributions must comply with RS-485.COM licensing rules. Content should be original, public domain, or freely licensed.

== Changes to This Policy ==
This Privacy Policy may be updated periodically. Significant changes will be announced on the site.

== Contact ==
For questions or concerns regarding privacy, please use the discussion pages or contact the site administrators.

----
''This page outlines the privacy practices of RS-485.COM.''

RS-485:About

2026-04-30T19:53:17Z

Admin: Created page with "= About RS-485.COM = == Purpose == RS-485.COM is a collaborative knowledge platform dedicated to documenting, explaining, and expanding understanding of the RS-485 communication standard and related technologies. Powered by MediaWiki, it enables contributors worldwide to share expertise, technical details, and practical applications. == Mission == Our mission is to provide a comprehensive, freely accessible resource on RS-485, covering its history, electrical character..."

= About RS-485.COM =

== Purpose ==
RS-485.COM is a collaborative knowledge platform dedicated to documenting, explaining, and expanding understanding of the RS-485 communication standard and related technologies. Powered by MediaWiki, it enables contributors worldwide to share expertise, technical details, and practical applications.

== Mission ==
Our mission is to provide a comprehensive, freely accessible resource on RS-485, covering its history, electrical characteristics, advantages, and real-world use cases. We aim to support engineers, students, and enthusiasts in learning and applying RS-485 effectively.

== Content ==
* '''Technical Documentation''': Detailed explanations of RS-485 signaling, wiring, and protocols.
* '''Applications''': Examples from industrial automation, building control, and telecommunications.
* '''Comparisons''': Insights into how RS-485 differs from RS-232, RS-422, and modern communication standards.
* '''Guides and Tutorials''': Practical advice for setup, troubleshooting, and integration.

== Community ==
RS-485.COM is open to contributions from anyone interested in serial communication standards. All edits are subject to review and may be refined by other contributors to ensure accuracy and clarity.

== Copyright and Licensing ==
Content contributed to RS-485.COM must be original or sourced from public domain or freely licensed materials. Contributors agree that their work may be edited, altered, or removed to maintain the quality and reliability of the resource.

== Contact ==
For questions, suggestions, or collaboration inquiries, please use the discussion pages or contact the site administrators.

----
''This page explains the purpose and scope of RS-485.COM.''

Main Page

2026-04-30T19:52:17Z

Admin:

Main Page

2026-04-30T19:45:09Z

Admin: Created page with "RS-485 Standard OverviewIntroductionRS-485, also known as TIA-485-A or EIA-485, is a standard introduced in 1983 that defines the electrical characteristics of drivers and receivers for use in serial communications systems. It is widely used in industrial control systems, building automation, and telecommunications due to its robustness in noisy environments and ability to support long-distance communication.Key Features Balanced Differential Signaling: Uses a pair of w..."

RS-485 Standard OverviewIntroductionRS-485, also known as TIA-485-A or EIA-485, is a standard introduced in 1983 that defines the electrical characteristics of drivers and receivers for use in serial communications systems. It is widely used in industrial control systems, building automation, and telecommunications due to its robustness in noisy environments and ability to support long-distance communication.Key Features

Balanced Differential Signaling: Uses a pair of wires (A and B) to transmit data, providing noise immunity.

Multipoint Capability: Supports up to 32 unit loads (expandable with modern transceivers).

Data Rate and Distance: Up to 10 Mbps at short distances; up to 1200 meters at lower speeds.

Topology: Recommended bus (daisy-chain) topology; star and ring topologies are discouraged due to signal reflections.

Termination: Requires termination resistors (typically 120 Ω) at both ends of the bus to prevent signal reflections.

Electrical Characteristics

Voltage Levels: Logical 1 when differential voltage > +200 mV; logical 0 when < -200 mV.

Common-Mode Range: Tolerates -7 V to +12 V.

Three-State Drivers: Allows multiple transmitters on the same bus by enabling/disabling drivers.

Advantages

Noise Immunity: Differential signaling rejects common-mode interference.

Long-Distance Communication: Effective up to 1200 meters.

Cost-Effective: Uses inexpensive twisted-pair cabling.

Flexibility: Supports half-duplex and full-duplex communication.

Applications

Industrial Automation: Modbus RTU, PROFIBUS.

Building Automation: HVAC, lighting control.

Telecommunications: Infrastructure and remote sensor networks.

Comparison with Other Standards

RS-232: Single-ended, shorter distance, less noise immunity.

RS-422: Similar differential signaling but limited to point-to-point connections.

Practical Considerations

Biasing: Ensures a known idle state on the bus.

Repeaters: Used to extend distance or support star topologies.

Cable Selection: Twisted-pair cables with characteristic impedance around 120 Ω.

ConclusionRS-485 remains a cornerstone of industrial and automation communication systems due to its robustness, scalability, and cost-effectiveness. Its ability to handle noisy environments and long distances makes it indispensable in modern digital communication networks.

This page provides a comprehensive overview of RS-485 for the RS-485.COM wiki.