Wire lengths for communication testing

Translate This Thread From English to

Threaded View
btmull's Avatar (by Gravatar)btmull posted on
January 3, 2008, 3:41 pm
rate this thread


When testing device communications, is it prudent to specify tests for
the medium's boundaries?  For example:  using a 100 meter length of
CAT5 cable to test TCP communication, or 4000 feet of shielded twisted
pair cable to test RS-485 at 9600 bps.

Does OEM equipment generally get tested in this way?

Other Related Threads
Jerry Avins's Avatar (by Gravatar)Jerry Avins posted on
January 3, 2008, 10:40 pm
Permalink

Re: Wire lengths for communication testing



btmull@yahoo.com wrote:

Is there another way to be sure that the equipment meets its
specifications? After all, those distances are minimums.

Jerry
--
Engineering is the art of making what you want from things you can get.
ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ

Other Related Threads
Gene S. Berkowitz's Avatar (by Gravatar)Gene S. Berkowitz posted on
January 4, 2008, 1:31 am
Permalink

Re: Wire lengths for communication testing



says...

Due to practical limitations, like actually running out 4,000 feet of
cable (rather than leaving it on the spool, which is NOT the same
thing), it's common to simulate long cable by adding resistance and
capacitance to a short cable.  Though if you're building a TDR, you
really do need all that cable, and you have to MEASURE it too...

--Gene

Site Timeline