I've actually repaired a couple that've gone bad, including a bluetooth serial adapter. A lot of times there will be a voltage level converter chip like a max232 that'll get killed even though the uart is fine. On May 28, 2015 8:22 PM, "John R. Hogerhuis" <[email protected]> wrote:
> On Thu, May 28, 2015 at 2:44 PM, Mark Wickens <[email protected]> > wrote: > > Just a quick update - and a thank you for all the suggestions. > > In the end I moved to my IBM X60 laptop which, with an ultrabase > connected, > > has a real serial port. I was then able to transfer data at 19200 via > > minicom using the same cable without issue. So the problem appears to lie > > with the USB -> Serial Converted. I'm sure this is probably old news for > > some. I do have other USB -> Serial converters, so may see if any of the > > others work better under Linux. > > > > I've had good results under Linux with FTDI and Prolific chipset based > adapters. Under Windows I can only recommend the FTDI based adapters > because the Windows Prolific driver is a disaster. > > Now, I've had serial inputs and outputs go bad on USB->Serial devices > just like I've seen happen on standard serial ports. > > So I'd say don't blame the "USB" part of it. Serial ports go bad. > > -- John. >
