SLIP Modem dial-up sequence

embedded

At

send

case.

Well, the "modem" should at least return "CONNECT" when windows sends "ADTxxxx". All other AT commands from windows can be responded to by "OK" Try to dig up a Hayes command set description.

Meindert

sends

The OP should bring up the CD line as well to indicate a connect..

I think tying the DTR,DSR and CD together on the computers' side will do the job. Does windows really need the CD?

Meindert

In Windows Dial-up networking select "Direct connection between two computers (COM1)". Then select baudrate, protocols, etc. When you dial out using that connection Windows will send out the string CLIENT, the embedded system would then reply with the string CLIENTSERVER. The CLIENT / CLIENTSERVER exchange takes the place of the usual modem stuff.

"Meindert Sprang" wrote

do the

I don't think windows needs it per se, but his application (hyperterm?) may. IIRC, I couldn't get hyperterm to send data without it (even with hardware flow control disabled), but I may well be mistaken on that. I tend not to use hyperterm. ;-)

Hyperterm definately does not need the CD and if you disable hardware flow control (affects only DTR/DSR and CTS/RTS) it works fine over 3 wires.

Meindert

Hi Roger,

This is a comment from my 8051 slip code that appears right about where the problems begin. It might be helpful.

/* The COM port driver now believes that it has established a DTE to DTE link via 2 DCE (modem) devices. If DCD is not asserted by the device emulating the local DCE, then the port driver decides that the remote modem has hung up. It then shuts down the link and tries to hang-up the local DCE.

The local DTE will assert DTR whenever its ready to send data on a newly established link. We can link this to DCD to trick the COM port driver into thinking that the local DCE is receiving a carrier from the remote DCE, thereby signalling that the remote DCE has not hung-up and that all is well. This prevents the early SLIP link shut-down.

On a DB25 connector link pin 20 (DTR) to pin 8 (DCD), or for a DB9 connector link pin 4 (DTR) to pin 1 (DCD). */

Regards, Murray R. Van luyn.

embedded

At

send

case.

in

This is a comment from my 8051 slip code that appears right about where the problems begin.

/* The COM port driver now believes that it has established a DTE to DTE link via 2 DCE (modem) devices. If DCD is not asserted by the device emulating the local DCE, then the port driver decides that the remote modem has hung up. It then shuts down the link and tries to hang-up the local DCE.

The local DTE will assert DTR whenever its ready to send data on a newly established link. We can link this to DCD to trick the COM port driver into thinking that the local DCE is receiving a carrier from the remote DCE, thereby signalling that the remote DCE has not hung-up and that all is well. This prevents the early SLIP link shut-down.

On a DB25 connector link pin 20 (DTR) to pin 8 (DCD), or for a DB9 connector link pin 4 (DTR) to pin 1 (DCD). */