sarge@thirdi.UUCP (08/31/87)
Awhile back, I wrote a request for information on a problem I had with my Courier 2400 modem: > I've had two courier 2400 modems and both display the same oddity -- > unpredictably, after someone calls in on the modem, after they hang up, > the modem displays two flashing lights, the transmit and receive data > lights, flashing on and off at about one second intervals. From: thirdi!ames!rutgers!princeton!pgt1!brent (Brent Chivers) Sounds very familiar. Do the modem have "Command Echo" set? (I.e., if you give the modem commands from your end (like "ATH0") do they echo back so you can see them?) If so, the modem is echoing back the "Login: " and "Password: " prompts that your system starts sending after someone logs out. On our system this kept a getty so busy that it severely degraded system performance. As a result, we run a little program that turns off command echo, and that solved the problem for us. (We also turn off result codes, which speeds up logins for user and uucp calls, since there is no "RING" or "CONNECT 2400" spit out, which would also be read as login id's or passwords.) We use the same modem for calls in and out, so our uucp sequences first reset the modem so uucp can see command echo and status messages, and after the call is completed our polling script forces the modem into this quiet mode. If you want, I can mail you the code for my little tricks. From: thirdi!isieng!nbisos!nbifet!harlan (Harlan Olson) I did a lot of experimenting with the modem. I found this to work for me. Set all switches off except 3 and 8, which should be on. From: thirdi!hplabs!hpda!hpihoah!dbuckler (Dan Buckler) I have seen this problem. It turned out that the modem was exchanging spaces with the machine. It was never ending as both the modem and the machine were full duplex. My solution was to disable the echo on the modem. There is a dip switch on the bottom of the modem to accomplish this. You will have to toggle the power on the modem in order to have the new switch setting read. My solution has the disadvantage that you won't get an echo of what you have sent the modem. So, for example, if you are dialing out using the modem when you type ATDT..... you won't see anything, but the modem will execute the command. From: Karl Denninger UUCP : ...ihnp4!ddsw1!karl The next time you have this occur, take a phone and plug it into the second jack on the back of the modem -- and see if you're offhook or not. If so -- Connect to the modem directly, and say 'ATI'. If it comes back with '241' then you need a prom upgrade, call USR and tell them you need rev '242' of the prom for the Courier..... We have one like this out here, it's a problem in the ROMS having to do with disconnect/connect detection (it also makes 'x6' mode screw up) (Note: the '242' upgrade fixed several other carrier-related problems, so it might pay to check it anyways with ATI and get 242 if you don't already have it.) (NOTE from Sarge Gerbode -- I have Version 243, so I suppose this doesn't apply to me.) From: thirdi!isieng!kevin@fred.ISI.COM (Kevin Brooks) Your problem sounds like switch settings on the modem. I've set several of these modems up in the past and found that the exact problem you described would occur if the switch settings were inccorrect. USR Settngs 3 and 8 on 1,2,4,5,6,7,9,10 off Your modem may be labled on and off or up and down up = off down = on Switch 5 could go either way up or on - auto-answer down or off - no auto-answer Hope this helps From: thirdi!hamilton@uxc.cso.uiuc.edu (Wayne Hamilton) aha! i also have a courier on an IS qbus, running an older rev of 4.2 (i don't know the exact subversion). we only use it for dialin, so the only way we clear it is via power cycling. i've never seen it happen when i was on-site (it's in DC, i'm in IL), so i don't know about Rd and Td flashing. the last time i was there, i fiddled with the switch settings, and all the testing i did showed it behaving perfectly. soon as i return home, tho, it's back again. the problem i would have is after dialing in once, the next time i tried, the courier would answer and hangup before carrier synch. one day i got disconnected before logout, and i expected to be unable to reconnect, but i succeeded! ever since then, i've been logging out by typing "sleep 15;logout\n<pause>+++<pause>ATH\n". i have a lot less problems now. i'll probably try to hack something up to simulate the out-call that works for you; i hate to drop carrier so "rudely". let me know what you learn; i'll recip. From: thirdi!seismo!sun!rich (Richard Koch) I had the same problem with my Courier 2400. The problem was that the software was not interpreting the hangup signal from the modem and kept sending login: messages to the modem. The fix was to rewire the cable. I spent a LOT of hours with a breakout box getting it to work exactly right. BTW, I use the modem with a Zilog System 8000 running Unix Version III. * * * * * * * * * * * In fact, what worked for me (so far) was simply to turn off the echo. I haven't had to resort to more expreme measures, because all has been fine since I did that. I very much appreciate all the help. I hope others will benefit as well. Sarge Gerbode Institute for Research in Metapsycholopgy 950 Guinda St. Palo Alto, CA 94301 UUCP: pyramid!thirdi!sarge!sarge -- "Absolute knowledge means never having to change your mind." Sarge Gerbode Institute for Research in Metapsychology 950 Guinda St. Palo Alto, CA 94301 UUCP: pyramid!thirdi!sarge