Forums

RS232 cable followup

Started by Unknown December 24, 2012
Thanks again to those who responded to my RS232 cable question. This
morning I soldered on the DB connectors and did a test of the cable.
There were no problems. I fact, though this is really subjective, the
program seemed to download faster than it did with the older, shorter,
spliced cable.
Eric
On Mon, 24 Dec 2012 11:10:20 -0800, etpm@whidbey.com wrote:

>Thanks again to those who responded to my RS232 cable question. This >morning I soldered on the DB connectors and did a test of the cable. >There were no problems. I fact, though this is really subjective, the >program seemed to download faster than it did with the older, shorter, >spliced cable.
Seemed like you'd have been fine and wouldn't need to go to any extreme measures. Good to hear it's working good! Jon
etpm@whidbey.com Inscribed thus:

> Thanks again to those who responded to my RS232 cable question. This > morning I soldered on the DB connectors and did a test of the cable. > There were no problems. I fact, though this is really subjective, the > program seemed to download faster than it did with the older, shorter, > spliced cable. > Eric
The splices will cause impedence discontinuities in the cable which can cause data retries. In turn that will slow things down. -- Best Regards: Baron.
On Mon, 24 Dec 2012 11:41:35 -0800, Jon Kirwan
<jonk@infinitefactors.org> wrote:

>On Mon, 24 Dec 2012 11:10:20 -0800, etpm@whidbey.com wrote: > >>Thanks again to those who responded to my RS232 cable question. This >>morning I soldered on the DB connectors and did a test of the cable. >>There were no problems. I fact, though this is really subjective, the >>program seemed to download faster than it did with the older, shorter, >>spliced cable. > >Seemed like you'd have been fine and wouldn't need to go to >any extreme measures. Good to hear it's working good! > >Jon
The best thing is that I recieved answers here that made me optimistic about success. This is the major reason I like Usenet. Folks offering information while expecting nothing in return and only wanting to know if their advice helped. Cheers, Eric
On Mon, 24 Dec 2012 20:09:25 +0000, Baron <baron@linuxmanic.net>
wrote:

>etpm@whidbey.com Inscribed thus: > >> Thanks again to those who responded to my RS232 cable question. This >> morning I soldered on the DB connectors and did a test of the cable. >> There were no problems. I fact, though this is really subjective, the >> program seemed to download faster than it did with the older, shorter, >> spliced cable. >> Eric > >The splices will cause impedence discontinuities in the cable which can >cause data retries. In turn that will slow things down.
In RS232? With risetimes in the microseconds? No, by a factor of 1000 or so. Besides, most RS232 links don't have provision for data chacking and retry.
On Mon, 24 Dec 2012 20:24:32 -0800, John Larkin
<jjlarkin@highNOTlandTHIStechnologyPART.com> wrote:

>On Mon, 24 Dec 2012 20:09:25 +0000, Baron <baron@linuxmanic.net> >wrote: > >>etpm@whidbey.com Inscribed thus: >> >>> Thanks again to those who responded to my RS232 cable question. This >>> morning I soldered on the DB connectors and did a test of the cable. >>> There were no problems. I fact, though this is really subjective, the >>> program seemed to download faster than it did with the older, shorter, >>> spliced cable. >>> Eric >> >>The splices will cause impedence discontinuities in the cable which can >>cause data retries. In turn that will slow things down. > >In RS232? With risetimes in the microseconds? No, by a factor of 1000 >or so. > >Besides, most RS232 links don't have provision for data chacking and >retry. >
Yeah, I knew it was subjective. Probably I'm just so pleased that the new cable worked after routing it around the inside perimeter of the shop that it seems to work better than the old cable. Since the new cable is much longer than the older cable the signals probably actually take longer. Not that I could actually detect any speed difference. Eric