Anderer@UDEL.EDU.UUCP (03/25/87)
We've got a number of ports defined as /AUTOBAUD/PERM connected to our dataswitch here. Normally 1 or 2 CRs is sufficient for the AUTOBAUD to determine the baud rate and bring up the login prompt. ...except at 2400 baud. At that speed, people generally need to type a lot (10 or more) CRs. Sometimes even 50 isnt sufficient. A known problem? Any workarounds? Configuration: 11/780, DZ-11 ports, VMS 4.2.
art@MITRE.ARPA.UUCP (03/25/87)
I have normally noticed that those who have problems autobauding from VMS do not
realize that they must type the carriage returns s l o w l y ! !
I have told users to wait 2 seconds between carriage returns. It takes awhile
for VMS to respond and change the baud rate on the DZ. If the machine is
heavily loaded, one may need to wait longer. 1800 is the worst case
with 2400 being the second worse case. I think that if properly
handled by a user, VMS will autobaud 2400 in 2 or 3 carriage returns.
Typing them too fast however will result in VMS thinking that the
response came after the DZ was switched to a new speed when in fact it
came either before or during the switch.
This is not fido, type the carriage returns slowly.
*
*---Art
*
*Arthur T. McClinton Jr. ARPA: ART@MITRE.ARPA
*Mitre Corporation MS-Z305 Phone: 703-883-6356
*1820 Dolley Madison Blvd Internal Mitre: ART@MWVMS or M10319@MWVM
*McLean, Va. 22102 DECUS DCS: MCCLINTON
*
=-=- This note is in response to yours which follows -=-=
We've got a number of ports defined as /AUTOBAUD/PERM connected to our
dataswitch here. Normally 1 or 2 CRs is sufficient for the AUTOBAUD to
determine the baud rate and bring up the login prompt.
...except at 2400 baud. At that speed, people generally need to type
a lot (10 or more) CRs. Sometimes even 50 isnt sufficient.
A known problem? Any workarounds?
Configuration: 11/780, DZ-11 ports, VMS 4.2.art@MITRE.ARPA.UUCP (03/26/87)
I have normally noticed that those who have problems autobauding from VMS do not
realize that they must type the carriage returns s l o w l y ! !
I have told users to wait 2 seconds between carriage returns. It takes awhile
for VMS to respond and change the baud rate on the DZ. If the machine is
heavily loaded, one may need to wait longer. 1800 is the worst case
with 2400 being the second worse case. I think that if properly
handled by a user, VMS will autobaud 2400 in 2 or 3 carriage returns.
Typing them too fast however will result in VMS thinking that the
response came after the DZ was switched to a new speed when in fact it
came either before or during the switch.
This is not fido, type the carriage returns slowly.
*
*---Art
*
*Arthur T. McClinton Jr. ARPA: ART@MITRE.ARPA
*Mitre Corporation MS-Z305 Phone: 703-883-6356
*1820 Dolley Madison Blvd Internal Mitre: ART@MWVMS or M10319@MWVM
*McLean, Va. 22102 DECUS DCS: MCCLINTON
*
=-=- This note is in response to yours which follows -=-=
We've got a number of ports defined as /AUTOBAUD/PERM connected to our
dataswitch here. Normally 1 or 2 CRs is sufficient for the AUTOBAUD to
determine the baud rate and bring up the login prompt.
...except at 2400 baud. At that speed, people generally need to type
a lot (10 or more) CRs. Sometimes even 50 isnt sufficient.
A known problem? Any workarounds?
Configuration: 11/780, DZ-11 ports, VMS 4.2.iglesias@unxa.uci.EDU.UUCP (03/26/87)
I've seen this on both our 780 and 785 running VMS 4.2 thru 4.5. From what I have been able to figure out, autobauding works like this: * If the line speed is not 9600 or 600 (the autobauding speeds), set it to 9600. * Read a character * If it's recognized in the 9600 baud table, use that speed (9600-1200 baud) * If not, switch to the 600 table and read another character (600-50 baud) * If it's recognized, use that speed Once VMS gets into the second baud rate table, it never gets out. And the table doesn't get reset when the line drops, so it's stuck there until someone hits it at the right baud rate, the system gets rebooted, or someone hits the BREAK key when they get connected to that line. I can reproduce the problem by connecting to a line at 300 baud, hit CR twice and disconnect. Trying a connect at 9600 baud will get you nothing, no matter how many CRs you type. SHOW TERMINAL of that line will show that the speed is set to 600 baud. The fix is for VMS to set the line to a known state when a connection is made. We have a Develcon Dataswitch, so any terminal here can connect to any port. I finally ended up writing a FORTRAN program that checks the lines to see if anybody is on, and if they're not, it sets the speed to 9600 (which corrects the autobauding problem). I tried to educate our users to hit BREAK if they got no response, but that didn't work. Someday when I get some time I'll write an SPR on this. Mike Iglesias University of California, Irvine Disclaimer: Like I said above, it's been a while since I looked at the code that does the autobauding, so there's bound to be something wrong with some of the above statements.
BMW6957@TAMCHEM.BITNET.UUCP (03/26/87)
I seem to remember reading about autobaud a long time ago. I don't know if I remember it properly, but I seem to recall that 2400 baud was a special case. If my memory serves me, at slower baud rates (below 1200) two carriage returns were necessary, separated by about 1 second. At baud rates of 1200 and above (except 2400), a single carriage return would work. And at 2400 baud, I believe it was a control-Y that was used, rather than a carriage return. Now, this may have been way back on VMS 2.5 so things have probably changed, but I just tried a control-Y at 2400 baud and it works (of course, on my system a single carriage return at 2400 also seems to work). It's something to check out, though. Brad Wilson Chemistry Department Texas A&M University BMW6957@TAMCHEM.BITNET
V125KJG8@UBVMS.BITNET.UUCP (03/27/87)
>We've got a number of ports defined as /AUTOBAUD/PERM connected to our >dataswitch here. Normally 1 or 2 CRs is sufficient for the AUTOBAUD to >determine the baud rate and bring up the login prompt. > >...except at 2400 baud. At that speed, people generally need to type >a lot (10 or more) CRs. Sometimes even 50 isnt sufficient. I have also seen this problem on Fido and Opus BBS's. Is there any way that the AUTOBAUD configured to sense space bar depressions instead? I have read that at 2400 bps, the <CR> is a nasty guy to detect out of the malestrom and the space bar may be better. Also, it provides a larger target for those dial- up users who insist on having a cup of coffee in one hand when working their terminal, anyway. Have fun and see yuh... --Curtis R. Anderson State University of New York at Buffalo
BRIAN@UOFT02.BITNET.UUCP (03/28/87)
I have not seen this 2400 autobaud problem on my 785, however, this system has four DHU11's and 2 DMF32's (no DZ's, PLEASE) . The DHU's are all set with modem control and autobaud, whereas the DMF's are used for (1) local terminals (2) Jnet bisynch links and (3) dialout ports for modems on the 2 modem controlled ports. The only problem I have seen is that the Gandalf Pacx 1000 switch has problems sometimes in autobauding a v.22bis call. Brian Nelson