Thread View: comp.os.linux.misc
3 messages
3 total messages
Started by Craig Sanders
Thu, 17 Feb 1994 06:05
flow control on ttyS0
Author: Craig Sanders
Date: Thu, 17 Feb 1994 06:05
Date: Thu, 17 Feb 1994 06:05
75 lines
2729 bytes
2729 bytes
I'm having what I suspect is a flow control problem with my modem. Firstly, what have I got: 16550 serial port. ttyS0 aka com1 Netcomm Trailblazer (Australian version of early model Telebit 1000) modem. Can do 1200, 2400, PEP (19200) speeds. It doesn't do MNP or 'uucp spoofing' as later model Telebit's can do. Software is Taylor UUCP 1.04, as distributed with the SLS 1.03 package. Symptoms: If I lock the modem to 19200 interface speed (S51=5), but get a 2400 bps connection then uucp connections bomb out with lots of errors. If I lock the interface speed at 19200 and get a PEP connection, there is no problem. If I lock at 2400 bps and get a 2400bps connection, there is no problem. I should be able to lock the modem at 19200 and get a 2400 connection without a problem. I used to do it months ago when I was in fidonet. So, is this a hardware problem? How can I set the flow control ? properly Do I need to use setserial or something ? Or is it software? Should I get a copy of the source for uucp and recompile it myself? FYI, my ATN? modem register display: ATN? E1 F1 M1 Q0 T V1 X1 Version R2.3AUS-024 S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=055 S08=002 S09=006 S10=007 S11=080 S12=050 S45=000 S48=000 S49=000 S50=000 S51=002 S52=002 S53=001 S54=003 S55=003 S56=017 S57=019 S58=000 S59=000 S60=000 S61=020 S62=003 S63=001 S64=000 S65=000 S66=001 S67=000 S68=255 S90=000 S91=000 S92=000 S100=000 S101=000 S120=000 S121=000 S122=001 N0: N1: N2: N3: N4: N5: N6: N7: N8: N9: OK When I want a PEP connection, I have to run minicom and manually set ATS50=255 and S51=5. I'd like to be able to leave the modem locked at 19200, regardless of the actual connection speed. any suggestions? -- Craig Sanders cas@muffin.apana.org.au Be compassionate: Don't say "straight", say "psychedelically challenged"!
Re: flow control on ttyS0
Author: michael butler
Date: Thu, 17 Feb 1994 14:40
Date: Thu, 17 Feb 1994 14:40
29 lines
1943 bytes
1943 bytes
Craig Sanders (cas@muffin.apana.org.au) writes: : I'm having what I suspect is a flow control problem with my modem. [ .. ] : So, is this a hardware problem? How can I set the flow control ? : properly Do I need to use setserial or something ? I'm not sure about Linux but you MUST use some sort of flow control even when the line speed (DCE rate) approximates the computer <-> modem rate (DTE). Errors just become more obvious where there is a greater disparity between the two. For an '8-bit transparent' transport as compressed UUCP news bundles require, your only real choice is to use RTS/CTS handshaking. Set S58=2 and leave S68=255 as you have it .. then explore how to get Linux to work with it. : When I want a PEP connection, I have to run minicom and manually set : ATS50=255 and S51=5. I'd like to be able to leave the modem locked at : 19200, regardless of the actual connection speed. S51=5 will achieve that by itself, even with a 2400 baud caller. It's the missing RTS/CTS flow control that's causing the problem, michael -- imb@scgt.oz.au, imb@asstdc.com.au, 3:712/515@fidonet
Re: flow control on ttyS0
Author: Craig Sanders
Date: Sat, 19 Feb 1994 01:27
Date: Sat, 19 Feb 1994 01:27
34 lines
2171 bytes
2171 bytes
imb@asstdc.scgt.oz.au (michael butler) writes: >Craig Sanders (cas@muffin.apana.org.au) writes: >: I'm having what I suspect is a flow control problem with my modem. > [ .. ] >: So, is this a hardware problem? How can I set the flow control ? >: properly Do I need to use setserial or something ? >I'm not sure about Linux but you MUST use some sort of flow control even >when the line speed (DCE rate) approximates the computer <-> modem rate >(DTE). Errors just become more obvious where there is a greater disparity >between the two. >For an '8-bit transparent' transport as compressed UUCP news bundles >require, your only real choice is to use RTS/CTS handshaking. Set S58=2 and >leave S68=255 as you have it .. then explore how to get Linux to work with >it. Thanks, this seems to have fixed it. I must have missed this when I spent hours poring over the manual a couple of months ago when I first encountered this problem. Since then I've had a PEP connection so it hasn't bothered me, but my feed recently dropped back to 2400bps causing the problem to appear again. -- Craig Sanders cas@muffin.apana.org.au Be compassionate: Don't say "straight", say "psychedelically challenged"!
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads