|
|
|
I have a Pinril Data Comm. Cadet 2400 modem I got cheap. I seems to be in working order, however I don't have a manual for it and it does not seem to respond to the "AT" commmand set. Anyone know what the command set is for this modem? The DIP switch for Command Recognition is enabled.
19 responses total.
Ummm, maybe try setting the Command Recognitoin switch in the other position ??? It might not agree with your interpretation of "is enabled?" Also, do the TD / RD lights blink at you when you try to issue commands? They should...
The switch is definatly set to enable Command Recognition. The logo is very clear on setting the switches (a rarity). Both TD and RD lights flash when I try to talk to it and the modem will go off-hook and send a carrier/bit stream when playing with a Data/Talk switch on the front bezel. I wonder if Penril Data Comm. is still around?
A wild idea: do you have access (does anyone) to a comm pgm with built-in support for this modem? You might hook it up, either with a loop or to another machine, & see what comes out when the program tries to tell the modem what to do. I suspect you wouldn't be asking if your comm pgm met this requirement. Sigh.
Have you tried any other protocols? Such as the Tandy commands?
No on both the above. I am using Telix and I have no idea what the Tandy commands are. All the modems I've ever used are Hayse compatable or dumb acoustic coupled units. I called a phone No. printed on the bottom of the unit but that was no loner in service. There is an EPROM inside with the date of 1984 stamped on it. Maybe I'll have to pull it out and read the contents with an EPROM programer. There might be some clues inside??? Give me some of the Tandy commands rcurl and I'll give them a whrill. I'll also try to post this question on a Fido Net conferance. Maybe I'll have better luck there due to the larger audience.
First, on the Tandy DCM 212, for Command Recognition, DIP switch 7 is OFF (up). The Wake Up command is [*][.] (without the parentheses). It echos [*]. The dialer command is [D]. Mode parameters may have to be entered. After [*][.], type [L] to list current parameters (echo is *L). Key MANUAL MODE: to N and ORIG MODE: to Y (with M and/or O). When in command mode, one dials with (for example) DT 761 3000 X (If any of this works - I have the manual for Tandy Protocol, and you are welcome to borrow it.)
Well rcurl, I tried the Tandy commands, but n o WOW mongo line noise.
It doesn't show but I was getting a lot of line noise in the responce above. I was using the Penril modem...it seems to have a problem with less than perfect lines too. No go rcurl. Tandy commands don't work either. I was using the modem in dumb mode, having dialed grex from an extension, so it does work to some degree.
You could make it *connect* that way? Wow.
Yea, it has a Talk/Data switch. With the switch in the Talk pos., I make the call and when the host modem answers I switch to Data. That's it, it takes care of the rest (Including all the line noise! ;-)
Again I say "wow". My modem has been getting flaky about hanging up & dialing. (It will stay off-hook even when I power everything down, for example.) I wish it worked like that.
Sounds like the reed relay inside is sticking. This relay is used to dial pulse and connect/disconnect from the line. If you can figure out what voltage it takes to drive the coil around the reed, you can replace it. Radio shack sells 5 and 12 volt reed relays for under $2.00 that could be "hacked" in.
Only by someone more adept than I am at recognizing components, soldering, unsoldering, etc. If I tried something like that I would have no modem at all in very short order. But what you say indeed describes very much what it *sounds* like, especially when it mis-dials. (And, yes, we are talking pulse dialing here.) Thank you *very* much for the hint.
Well all, I found my problem. Silly me. It does respond to the AT command set. It does not respond to the at command set though. This thing is case sensitive! Thanks all for your help!
<red face> Klaus, I'm sorry - I almost mentioned it, but since you kept typing uppercase when you said AT command set I thought you *must* have tried that. I believe the first Hayes modem (real Hayes) I ever used was case-sensitive. Oops. Glad you got it anyway!
Ha, yea, I did type upper case didn't. Live and learn ;-)
I replaced the MOV (spike killer) and several capacitors inside the
Penril modem and so for, no noise? (Wouuldn't you know, right in
the middle of the word noise I got two "{"!) My good friend
Mur
phy!
Side question: Is case-insensitivity part of some official standard, or is it just something that most modems now do? My first semi-Hayes- compatible (a U.S. Robitics Password 1200 baud) was case sensitive, requiring all commands to be in upper case. My new modem, acquired a couple of weeks ago, seems to be completely case-insensitive, accepting "AT", "at", "At", and "aT" for the command prefix. This is very easy to implement of course, as it just involves masking one bit of the ascii code. But I've seen at least one modem that would accept either upper or lower case commands, but required the command prefix to typed in a single case. It liked "AT" and "at", but didn't recognize "At" or "aT" as starting a command. So I'm curious if there are any official standards in this area that a completely Hayes-compatible modem is supposed to adhere to.
Not really, since "Hayes-compatible" is more or less nonexistant now with all of the extended command sets. The problem is that Hayes wasn't the first to come out with, say, an MNP or V.42 modem, so they didn't get to set the standard. Microcom chose an abysmal standard (the backslash as a prefix character), so lots of companies have gone with % or just more S-registers. ZyXEL and Digicom use * as well. The only things that are really standard are the first ten or so S-registers and the basic AT and AT& commands.
Response not possible - You must register and login before posting.
|
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss