--===============0582029744==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by pch.mit.edu id o4H0ltCN008233

Josh,
Twisted pairing is important for RS-422 and patch or crossover cable woul=
d matter.
But in this case, not as important.
Grouping is nice.
RS-232 is short distance.

So you are right.
Ray


On Sun, 16 May 2010 20:26:56 -0400, Josh Koffman wrote:
>=A0Hi all. I'm working on a board that has a specific use at the
>=A0moment, but I'd like to leave things a bit open for other future
>=A0uses as well. At the moment, there will need to be a connector that
>=A0talks to a device via RS232. It's low speed (9600bps) and short
>=A0distance (under 10 feet, likely under 3 feet). To keep my options
>=A0open for the future (and to aid my design), I'd like to use RJ45
>=A0connectors to carry the RS232 signal. There is a standard for this
>=A0(EIA-561, mentioned here about 25% of the way down the page, but
>=A0I've seen it elsewhere as well) so I feel ok setting it up. I
>=A0believe that the original intent was to use telephone style cable
>=A0with these RJ45 connectors. What would happen if I used straight
>=A0through CAT5 ethernet cable? Electrically I think it'd be ok, and
>=A0since RS232 isn't a differential signal the pairs shouldn't have to
>=A0be matched.
>
>=A0How wrong am I?
>
>=A0:)
>
>=A0Josh
>=A0--
>=A0A common mistake that people make when trying to design something
>=A0completely foolproof is to underestimate the ingenuity of complete
>=A0fools. -Douglas Adams




--===============0582029744==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--===============0582029744==--