atcomsystems.ca/forum Forums Computers & Programming Computers, Software, Accessories Modem commands

the &F would turn that off by initializing the modem to facotry default, which should have dialback set to off. He might try AT&E to turn off software flow control.

PMCook, you're right about the AT&F command, though many modems have to be issued the command twice - AT&F0 and AT&F1 so both the chipset (the data pump etc) AND the entire board clears.
Also not all modems have all registers, so ATS86? may not work. Issue a series of info commands to find out - ATI0, ATI1, ATI2 etc etc untill it returns an error. Everyone of these commands gives different info.

I need to check my initialization strings again. I may have a colon instead of a semicolon inserted somewhere, although I have not changed a thing on this computer in three years.

I'll also try the &E idea. What do I have to lose? Thanks to all so far for your input. I need to get this problem fixed, hook or crook, so anything is worth the effort.

Did you try strapping DTR high (AT&D or AT&D0)?

My initialization string includes &D2, but that hasn't changed. I guess I can try that and see what happens. Thanks, Tim.

Could you post the init string?
Also, were the modem drivers updated? (Maybe automatically)
Was the comm software updated?

Sure. It is now ATE1Q0X1&C1&D2S8=13S11=200

Nothing has changed, no upgrades, no drivers. It's just for basic remote programming at 19.2K baud max.

&D2 will hang up the modem when DTR drops. &D0 causes modem to stay online regardless of DTR.
Also, the X commands only affect what is reported back from the modem, not what the modem does.
The &D2 command could be the problem here. I assume you use a similar string for the other (working ) modem?

Yes. I have the internal modem that is giving me problems, but I also have my Motorola Startac cell phone connected as an external modem using COM2. Note: There aren't any IRQ conflicts either.

The same initialization string using the same programs works fine on the external (cell) modem. It's the internal modem that seems like it doesn't want to play. I still can't understand why "AT&F" shouldn't solve my problem from a blank terminal screen.

I let the program initialize the modem using the aforementioned string, then I manually enter "AT&F". For all intensive purposes, that should have defaulted any of the changes my initialization string created, correct?

I use X1 to force the modem to NOT monitor for dial tone or busy when dialing out. Otherwise, I can't transfer a call INTO it or call into a system via auto attendant. It thinks that it has encountered a busy signal when it hears voice. I've been using that setting for years on all of my modems, both with this one and a half-dozen of them at the office.

I frequently have to dial into a system manually and navigate my way to a point where I can get to the system's modem. Once I reach the distant modem, I type in "ATD" from my terminal screen, transfer the call to my modem's extension, then hit enter. That has worked fine for me. Obviously, I can't use the "ATA" command, so I just let my modem "think" that it initiated the call and everyone is happy.

I've just tried &D, &D1 and &D2 (each time saving the entry using &W) and the same exact thing happens: It dials the number, pauses 13 seconds based upon my S8 setting, dials the remaining digits, then drops the call with a profound click.

Oh and yes, I do have the line cord connected to the proper jack on the modem card. Just in case, I tried it both ways!

Maybe I just have a bad modem card. I hate to part with it since it will work down to 300 baud for older systems; something that is hard to do with newer modems. I guess I can snag one from work and bring it home if necessary, but I just find it odd that the problem is so predictable every time.

Before you chuck the modem, issue an AT&V1 command after the link drop. The results should include "Termination Reason" or similarly worded thing. I'd love to know what's reported.

Yes, AT&F superceeds every command previously issued. But if there's any question about what setting is or isn't in effect, it's handy to know some of the ATI commands. ATI4=Return current modem settings and ATI5=Return NVRAM settings. It might be worth comparing these two option sets to see if they match.