On Thu, Sep 22, 2022 at 5:32 PM B 9 <[email protected]> wrote: > > Of particular note for troubleshooting is that, if some of the data gets > transferred, but it is garbled or you get a ?DS ERROR, then the problem > is that your PC's serial port does not support "ON CHIP SOFTWARE FLOW > CONTROL". One solution is to buy a serial card or USB cable with an FTDI > chip in it. (Other companies make ICs that support on chip software flow > control, I even have a cheap Prolific 2303 device that does, but FTDI is > the only company I know of whose chips are supposed to always work. ) > > I've never heard of this on-chip software flow control.All I knew was that software flow does not work under Linux. My experience is software flow control with a Model T *does* work on Windows.
Is that something you have to enable? Seems awfully strange to have the chip interceding in-band. Automatic hardware flow control I have heard of. This failure on Linux is why I made HTERM to use hardware flow control If there's a consistent way to make it work on Linux, it would be good to know. Even just with FTDI chipset. Windows prolific drivers are trash. I don't know about Prolific on Linux. Is the stty command you put supposed to enable on-chip software flow control? Which part? *s**tty -F /dev/ttyUSB0 ixon ixoff stop ^S start ^Q -onlcr -icrnl eof ^Z 19200* -- John. >
