RS-485 Polarity: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
Our terminology: | Our terminology: | ||
{| class="wikitable" | {| class="wikitable" style="text-align: center;" | ||
|+ Nominal Terminology | |+ Nominal Terminology | ||
|- | |- | ||
Line 16: | Line 16: | ||
Labeling found in the field | Labeling found in the field | ||
{| class="wikitable" | {| class="wikitable" style="text-align: center;" | ||
|+ Manufacturer's Labeling | |+ Manufacturer's Labeling | ||
|- | |- | ||
Line 25: | Line 25: | ||
| || + || - || Symbol || BACnet Specification | | || + || - || Symbol || BACnet Specification | ||
|- | |- | ||
| || + || - || Symbol || FT-Click, | | || + || - || Symbol || FT-Click, BASRouter LX | ||
|- | |- | ||
| || B+ || A- || || MBS UBR-01 | | || B+ || A- || || MBS UBR-01 Mk II | ||
|- | |- | ||
| || U+ || U- || || [https://en.wikipedia.org/wiki/RS-485 Wikipedia] | | || U+ || U- || || [https://en.wikipedia.org/wiki/RS-485 Wikipedia] | ||
Line 37: | Line 37: | ||
TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! : | TI has a very definitive [https://e2e.ti.com/cfs-file/__key/telligent-evolution-components-attachments/13-143-00-00-00-26-49-60/RS485-_2D00_-Polarity-Conventions.pdf document], but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the [https://en.wikipedia.org/wiki/RS-485 Wikipedia article] on bus states is WRONG ! : | ||
{| class="wikitable" | {| class="wikitable" style="text-align: center;" | ||
|+ RS-485 Bus State Terminology | |+ RS-485 Bus State Terminology | ||
|- | |- |
Revision as of 05:56, 17 September 2023
RS-485 comprises two signals, one that 'tracks' the logic levels (high voltage == 1, low voltage == 0). The other signal does the opposite. The meaning of these two signals has been polluted by chip and box vendors, which leads to a lot of confusion. A lot of further confusion arises when one considers the UART logic levels vs signal levels and labels. This article attempts to resolve the status without adding to the confusion
Our terminology:
Our Terminology | Description | Logic levels | Data (UART) Representation |
---|---|---|---|
A | Tracking UART value | High voltage (typically +5 or +3.3) | 1 |
B | Non-tracking | Low voltage (close to 0v) | 0 |
Labeling found in the field
Comment | Tracking | Non-tracking | Class | Manufacturer examples |
---|---|---|---|---|
Our terminology | A | B | Nominal | BITS |
+ | - | Symbol | BACnet Specification | |
+ | - | Symbol | FT-Click, BASRouter LX | |
B+ | A- | MBS UBR-01 Mk II | ||
U+ | U- | Wikipedia | ||
TI convention | A | B | TI Polarity Conventions |
TI has a very definitive document, but one that has to be read carefully in terms of terminology. Read this document with the following table in mind. Note, according to TI (and our opinion), the Wikipedia article on bus states is WRONG ! :
UART bit | Logic level | A-B (T+ - T-) result | Legacy | RS-485 state | RS-485 A volt | RS-485 B volt |
---|---|---|---|---|---|---|
1 | high | A > B | Mark/Idle | On (0) | high | low |
0 | low | A < B | Space | Off (1) | low | high |