| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier V34 problems |
Paul, at 08:46 on Feb 01 1996, you wrote to Russell Brooks...
RB> With all the troubles you discribe, It must be setup or BAD lines.
RB> It can't all be blamed on the modem.
PE> I think it can.
Time to take off those blinkers and open your eyes, Paul.
PE> I might be happy to disable the detection phase though, since I don't know
PE> what that is, so I'll try ATS27=48.
A novel approach you have there Paul. Seeing as how you don't know what
trellis coding is either, you might as well disable that too. :)
RB> Give us a dump of ATi6 ATI11 & ATY11.
PE> Ok, will post later. Need to stuff around to get +++ to work.
Oh, rubbish! "+++, ATY11, ATO1". Where's the difficulty with that ?
RB> How can you expect the gods to smile on you when they have seen you Bag
RB> USR grossly in the past.
PE> I haven't actually (before I got this loaner). I used to think
PE> it really was the best.
Excuse me ? Pull the other one Paul.
PE> To who? I'll post the last connect to Dave Hatch's USR...
PE> # 01 Feb 06:53:41.85 Recv/Xmit Level (-dB) 25/15
Quite acceptable. These are mine to DD from this a.m.
# 03 Feb 06:22:35.53 Recv/Xmit Level (-dB) 23/12
PE> 1. After receiving an "AT" command at a particular baud rate,
PE> the modem does not adjust to that baud rate, and instead stays
PE> at the rate at the time of last "AT&W".
RB> This is how you set the Baud rate on setting up the modem originally.
RB> Start your comms prog up and set the comms prog to the baud rate you desire
RB> then do AT&W and it will then stay at the rate you want.
PE> Yes, that is a workaround. It is still a bug though. I have to
PE> rewrite the NVRAM instead of just letting the modem auto-detect
PE> on the "AT" command.
More garbage. Have a quote from the Courier manual...
===================================================================
Word length* 8
Parity* 0 None
DTE rate* (Kbps) 19.2
* Detected by the modem from the AT prefix of the &W command that
writes your defaults to NVRAM. Set your software to the desired
word length, parity and serial port rate defaults before sending
the modem the AT . . . &W string.
====================================================================
&Bn = Serial port rate variable or fixed.
&B0 Variable rates. When the modem switches its connection rate
to connect with a modem operating at a different rate, it also
switches its serial port rate. The software or terminal also
switches serial port rates to match the connection rate.
&B1 Fixed rate. Default. The modem always communicates with the
terminal or computer at the rate at which you have set the
terminal or software, regardless of the connection rate.
For the greatest throughput, set the serial port to 115.2K,
57.6K, 38.4K bps for high speed calls and to at least 9600
bps for 2400-bps calls.
This setting is not affected by the &N setting. However, the
serial port rate must be equal to or higher than the &Nn rate.
&B2 Fixed for ARQ calls/Variable for non-ARQ calls. Answer mode
only. When the modem goes off hook and connects in ARQ mode,
it shifts its serial port rate up to a user-specified rate, for
example, 38.4K bps. If the connection is not under error
control, the modem behaves as if it were set to &B0 and switches
its serial port rate to match the connection rate of each call.
To implement this feature, first set your software to the desired
rate. Then send the modem the AT &B2 [other settings] &W command.
The modem stores the rate of the command in NVRAM along with the
settings. Each time it makes an ARQ connection, the modem checks
NVRAM for the specified serial port rate.
When sending subsequent configurations to NVRAM, be sure your
software is set to your selected serial port rate, so that the
correct rate is maintained.
==========================================================================
PE> No, the previous person (the owner) thought that it was not
PE> possible to load anything other than the Australian code, and
PE> never attempted to do so. I thought it was possible, but
PE> checked with Bill Grimsley first, and he told me it was not
PE> possible, so I never tried either.
It used to be that if application of the wrong SDL was attempted, the modem
did a checksum of the country code and rejected it. However, I can't speak
for the latest SDL at all.
RB> Do you have the On Disk version of the Manual. Get Bill to send it to you.
PE> No, not yet.
Would you bother reading it if I crashed it to you ?
PE> The courier will be online for the next 2.5 weeks, and then I
PE> have to make a decision.
So why the 14400 V.32bis connect this morning then ?
Regards, Bill
--- Msgedsq/2 3.20
* Origin: Logan City, SEQ (3:640/305.9)SEEN-BY: 50/99 620/243 623/630 624/300 640/101 201 206 217 301 305 306 311 SEEN-BY: 640/702 820 821 822 823 829 690/660 711/401 409 410 413 430 510 808 SEEN-BY: 711/809 899 932 934 712/515 713/888 714/906 800/1 7877/2809 @PATH: 640/305 820 711/409 808 809 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™.