TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Paul Edwards
from: David Drummond
date: 1996-02-04 16:06:40
subject: USR Courier

Paul, at 15:50 on Feb 03 1996, you wrote to Bill Grimsley ...

. . .[chomp]. . .

PE> I even read that bit before you quoted it, in an attempt to 
PE> find the bit about the auto-baud rate detect that DD told me 
PE> to read (nevermind it wasn't even there).

BG>> You could've fooled me then.  You may have glanced at them, 
BG>> but you sure didn't grasp what they had to say.  The bottom 
BG>> line is that you should 

PE> YOU are the one who can't grasp it.

BG>> simply set Binkley to a serial port speed of 57600 bps, 
BG>> fire up the modem, and enter the required init$ (say 
BG>> AT&F1&K3S54=64&W, which disables MNP5 but not V.42bis, and 
BG>> also disables the V.25 call-indicate tones).  The &W will 
BG>> also write the port speed to the Courier's NVRAM, and like 
BG>> all error-correcting modems, you should NEVER need change 
BG>> it again, regardless of the link rate of an incoming call.

PE> And like all other modems, expect that if I do change the 
PE> baud rate, to test something out, I expect it to AUTO BAUD 
PE> RATE DETECT.  What a shame that USR's are stuffed in that 
PE> regard.

USRs are not like all other modems.  Lots of the S registers and other
variables are quite different to other modems.  This is why we have modem
setup strings so we can configure our software to match the particular
modem we are (ab)using.

PE> BTW, you can't even grasp that you keep on quoting something
PE> about the baud rate that happens AFTER a connect.  I am 
PE> talking about something that happens BEFORE a connect.

BG>> Bloody hell Paul, is that such a difficult concept for you 
BG>> to grasp ?

PE> Basically because you are wrong.  Be interesting to see if 
PE> you end up apologizing for all your ranting.

PE>> Maybe I should have said that a little more graciously:

PE>> You just misinterpreted the manual.

BG>> Nope, there's nothing at all wrong with MY comprehension.

PE> Apologize when ready.

PE>> In fact, if you type ATZ at 38400, it WILL auto baud rate
PE>> detect, and send the answer, "OK" back to the computer.

BG>> Yep.  It just doesn't permanently write that value to 
BG>> NVRAM, that's all.  

PE> Aha, the man suddenly understands what auto baud rate detect 
PE> is in this context.

PE>> It decides to send "RING" to the computer at a rate other 
PE>> than 38400 though.  Fucked, either by design or by a bug.

BG>> Operator error perhaps?  

PE> Nope, any modem designed to send characters to the modem at 
PE> two different speeds is fucked by design or by a bug.

BG>> Seriously though, if different, mine auto-bauds to 
BG>> the terminal's port rate as expected, with either incoming 
BG>> or outgoing 

PE> Yay, the man is starting to understand.

BG>> calls, and regardless of what had previously been written 
BG>> to NVRAM.  I just 

PE> Yay, the understanding continues.

BG>> ran a few tests with 57600 saved to the modem, but varied 
BG>> my locked port rate between 38400 and 115200 bps.  No 
BG>> problems at all, even on incoming 

PE> Yay, still going.

BG>> calls.  If your Courier isn't doing the same thing, it may 
BG>> indeed be faulty, 

PE> ROFL!  Well what do you know?  I was right all along.  I'll 
PE> still have to see the results of the proper test though.  Ok, 
PE> the proper test to do, is have the NVRAM set to 57600 as 
PE> usual, fire up your comms program at 38400, ATZ, should 
PE> respond "OK".  Now get someone else to call you, and see if 
PE> the word "RING" appears on your screen.  If it does, the bug 
PE> is not affecting you.

The Courier is NOT faulty in this repect. That is how ALL Couriers behave.  

Locked baudrate means LOCKED baudrate.  In a locked baudrate situation the
rate isn't supposed to change.  There is no mention (that I can find) in
the manual to support your theory.

The only reason it accepts your 38400 AT command is in case you wish to
LOCK the baud to some other rate with AT..&W

BG>> or (more likely) the last SDL didn't "take" properly.  That 
BG>> has been known to happen before.

PE> I've just done a reload, just rerun the test, same thing.

Because that is how it is designed to behave.

BG>> It's specific behaviour is controlled by the &Bn command.

PE>> Yeah, and I've got &B1, locked com port.  With "OK" coming 
PE>> in at a different speed to "RING".

The ring is coming in, as designed, at the speed stored in the NVRAM.

BG>> The &B1 setting is "correct", but I don't understand what 
BG>> you mean when you say that the incoming RING is at a 
BG>> different rate.  If both your modem and your serial port 
BG>> are locked to say 57600 bps, that's the speed at which the 
BG>> PC is communicating with the Courier, and is totally 
BG>> unrelated to the caller's speed, which is completely 
BG>> irrelevant from your POV.

PE> My modem has &B1, which means locked com port.  I can send 
PE> AT commands at 38400, and get the response at 38400, long 
PE> before a connect.  Now the USR detects someone is trying to 
PE> ring me, so it tells me "RING".  Only trouble is, it sends 
PE> that at the speed of the last NVRAM save.  Tell me the bit 
PE> that you don't understand.  Try to understand, Bill, I know 
PE> what I'm talking
PE> about.

BG>> I say again...

BG>> ===========================================================
BG>> ===========   &B1   Fixed rate.  Default.  The modem always

. . .[chomp]. . .

PE> See, the rate of my terminal is 38400, not 57600, in the 
PE> tests that I was doing.

PE>> What we CERTAINLY know is that the Spirit was far more 
PE>> robust with this REAL-WORLD modem.

BG>> Oh crap.  If you had a genuine grievance with the Courier, 
BG>> I'd go out of my way to help you solve any legitimate 
BG>> problems, but I'm almost 100% convinced that your 
BG>> "fault-finding" is little more than a childish exercise in 
BG>> oneupmanship, and I for one am no longer interested in 
BG>> playing your silly games.

PE> They are all legitimate problems. 

BG>> My last piece of advice to you is to give the Courier back 
BG>> to Paul, then 

PE> It looks like Paul Markham has saved me $175.  Thanks Paul!

BG>> look around in Aust_Trading for a second-hand Spirit, 
BG>> seeing as how you like them so much.  As far as I'm 
BG>> concerned, you'll deserve each other.

PE> And you know that's a blatant lie too.  I was screaming 
PE> about the Spirit whilst you were still in nappies (or a dress 
PE> at any rate). 

Please have the modem sent here where I can test it under the conditions of
a "perfect" phone line and an experienced operator.


David
ps.  Why is this portrate thing a problem? If you are running in locked
port mode, you are running in locked port mode.  Why would you wish to be
changing the port rate to something other than the one you have locked it
at?
@EOT:

--- Msgedsq/2 3.10
* Origin: JabberWOCky CBCS +61 7 3868 1597 (3:640/305)
SEEN-BY: 640/305 450 711/934
@PATH: 640/305 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.