SLLA628 September   2023 THVD1424

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Use Case Domain of RS-485
    1. 1.1 RS-485 Compliant Transmitter
    2. 1.2 RS-485 Compliant Receiver
    3. 1.3 RS-485 Transceiver Use Case Variability
  5. 2Traditional RS-485 Design Process
    1. 2.1 Design Process Overview
    2. 2.2 Requirement Definition
      1. 2.2.1 Bus Voltage and Logic Voltage (VCC and VIO):
      2. 2.2.2 Number of Communication Nodes Supported plus Static vs. Dynamic Systems
      3. 2.2.3 Max Bus Length, Network Topology, Emission Concerns, and Data Rate Required
      4. 2.2.4 Duplex
      5. 2.2.5 Protection Needs
      6. 2.2.6 Additional Features of RS-485 Bus
    3. 2.3 IC Selection, Application Design, and Validation/Qualification
  6. 3One Multi-System Design: Flexible RS-485 with the THVD1424
    1. 3.1 Flexible Multi-System Design
    2. 3.2 Simplification of RS-485 Design Process Using THVD1424
      1. 3.2.1 Bus Voltage and Logic Voltage Supplies (VCC and VIO)
      2. 3.2.2 Number of Communication Nodes Supported plus Dynamic or Static Systems
      3. 3.2.3 Max Bus Length, Network Topology, Data Rate, and Emissions Concerns
      4. 3.2.4 Duplex
      5. 3.2.5 Protection Needs
      6. 3.2.6 Additional Features
  7. 4Summary
  8. 5References

IC Selection, Application Design, and Validation/Qualification

With the requirements of the system defined the next three steps in the process are straight-forward and are largely guided by the first step in the process. The IC selection process will allow for quick disqualifications of parts that don’t meet the absolute needs of the use case. With each additional requirement added to the RS-485 system the pool of potential parts will decrease limiting the ability of many parts to be used across varied use cases. With general bus architecture informed by the standard and with system definition finalized the actual application design has largely been tackled throughout the definition and IC selection process. Finally, there is the question of validation and qualification – depending on the end user they may do IC and system level qualification to see if the IC and system are functioning as they should. These two events are typically separate where designers don’t usually have to re-qualify the same device over multiple projects so parts that fit multiple niches can be beneficial to the entire process.

With proper requirements defined the last three generalized steps are straight-forward. However, with the large amount of variability of RS-485 implementations even similar use cases could require different IC selections – adding a level of complexity to the design and qualification processes which could lead to multiple designs and additional qualification procedures.