current community

your communities

more stack exchange communities

company blog
Stack Exchange Inbox Reputation and Badges
tour help
Electrical Engineering Stack Exchange is a question and answer site for electronics and electrical engineering professionals, students, and enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
up vote 34 down vote favorite
2

"RS" in communication standards RS232 and RS485 stands for "Recommended Standard". But what information does "232" or "422" or "485" convey in the name? What naming convention is used for numbers succeeding the letters "RS" when naming the RS standards?

share

locked by Dave Tweed♦ 13 hours ago

This post has been locked due to the high amount of off-topic comments generated. For extended discussions, please use chat.
up vote 23 down vote accepted

It's the document serial number of the standard. Same reason why the HTTP protocol is also known as RFC2616 and the Javascript programming language is also known as ECMA262.

The numbers themselves have no meaning. For example while EIA232 specifies the electrical characteristics of a digital serial communications system, EIA222 specifies standards for antenna masts and RS225 is a standard for RF connectors.

Wikipedia has an incomplete list of popular RS/EIA standards: https://en.wikipedia.org/wiki/EIA_standards

share
2  
RFC numbers do occasionally have a little structure, but as far as I know it's limited to things like reusing the last two or three digits of the number for an update to an important standard (e.g. RFC 822, the original core email specification, was superseded by RFC 2822 and then RFC 5322). – zwol yesterday
3  
I don't know anyone who refers to the HTTP protocol as RFC2616 -- the document itself gives the protocol a name, so that is its name. (It's not even specified by RFC 2616 any more -- it was replaced by RFCs 7230 through 7237 in 2014). – Henning Makholm yesterday
2  
@HenningMakholm -- it's probably exactly because the IETF doesn't maintain document numbers for a specific topic that we don't use the document number in the name of protocols. Other standards bodies typically use a versioning scheme (e.g. appending a date after the document number as in Crowley's example of ISO9001:2016 referring to a specific version of ISO9001) that allows the base number to remain the same when new versions of a standard are released. That makes it much more convenient to use the document number to refer to the standard. – Periata Breatta 23 hours ago
    
@Periata Breatta Thank You.Reasonable explanation. – Sonam Khullar 21 hours ago
up vote 38 down vote

It signifies nothing; it's part of a sequential list of EIA standards: -

enter image description here

share
    
Well, it refers to one very specific item in that list. Isn't that significant? – Octopus yesterday
    
@Octopus maybe you can be a little clearer about what you mean? – Andy aka yesterday
up vote 3 down vote

RS = recommended standard

RFC = request for comment,

numbers don't have any real meaning

share
1  
The OP knows about RS already, and doesn’t mention RFC. – JDługosz yesterday

Not the answer you're looking for? Browse other questions tagged or ask your own question.