CompuServe Thread

Terminal programming

3 messages in this thread
#24936From: Joe BuckleyJun 25, 1992 8:29 AM
OK, I'm having a small problem. I am tinkering withg writing a small terminal program to autodial my modem, grab some data, then logout and process the data. The problem is that the modem doesn't seem to respond. I am using unit number 0 to get the system default baud rate and have the serial flags set for SHARED and 7WIRE configuration (without 7Wire, things were worse). I can tell that the modem is recieving data by watching the status LEDs and I can retrieve the echoed characters and dispplay them. The problem is that the modem doesn't respond. No dial tone, no dialing, nothing. As a matter of fact, if I send just an AT, I don't even get the OK return. I'm sure it's something obvious. I just don't know what! Joe
#25384From: Gary DunlapJul 6, 1992 10:52 PM
I know this sounds trivial, but is the baud rate within the range of the modem? Try simply opening SER: and doing I/O to it as a file. Otherwise I am not sure but that whatever data hapens to be in the configuration when you open the channel overwrights the defaults. This seems to happen on even unit 0. Gary Dunlap : Wyrd Software : It just works like magic!
#25535From: Joe BuckleyJul 9, 1992 8:39 AM
Gary, Thanks for the suggestion, the obvious should always be the first to be questioned. Yes, the modem (at the time, 2400bps) worked fine at the default preferences setting. Now I have a 14400 V.32bis/V.42bis modem to play with. It turned out that it was a silly error on my part. The text strings I would send to the modem were terminated with a '\n' newline, instead of a '\r' carriage return only. Silly me! JoeBuckley