Strange ERROR message on connection
#1
Hi,


I'm a new user of the WiModem232, and I love it - it lets my Tandy 102 computer access the Internet, and it's great.
The only issue that I've seen is when using the ATDT command to connect to various hosts on my local network.
When I execute these commands, I get an ERROR message before the connection occurs.  Everything is okay from that point on - it's just the initial ERROR that is a mystery to me.  In this example, 192.168.135.1 is the IP address of the host 'winter.brooknet', which is on my subnet.


Code:
ATDT192.168.135.1:80

ATDT 192.168.135.1

ATDT winter.brooknet:80

ATDT winter.brooknet

I wondered whether the WiModem is expecting a CRLF end-of-line, or some other character?  The Tandy 102 sends a CR (0x0D) when I press the Enter key.

Thanks!

Lex.
Reply
#2
Where exactly do you see the error message? Do you see this only once, or every time you attempt to connect using the ATDT command? The WiModem232 accepts either CR of LF as the "enter" for a command. If you send random characters (visible or not) followed by CR of LF, you will definitely get an ERROR message returned. For example, if you typed some control characters (which are not visible on the screen in a terminal program) followed by CR, you would get an ERROR message. What terminal program are you using? How do you have your setup configured (it should be 8N1).
Reply
#3
(03-09-2019, 07:23 PM)admin Wrote: Where exactly do you see the error message?  Do you see this only once, or every time you attempt to connect using the ATDT command? The WiModem232 accepts either CR of LF as the "enter" for a command.  If you send random characters (visible or not) followed by CR of LF, you will definitely get an ERROR message returned.  For example, if you typed some control characters (which are not visible on the screen in a terminal program) followed by CR, you would get an ERROR message.  What terminal program are you using?  How do you have your setup configured (it should be 8N1).

The ERROR message appears on every ATDT or ATDP command.  I am typing my commands manually, using the Tandy Model 102 TELCOM application, which is about as basic a telcom app as you can get: every typed character is sent to the remote system verbatim and the only intercepted characters are XON/XOFF, for flow control.  I have the comm settings at 38N1D, which means "300 baud, 8N1 format, no XON/XOFF flow control".  I don't think the Tandy 102 looks at the DCD line.  It might examine DSR - not sure.


I've also waited until I had solved the error message thing.  It occurs when I have extended response control (ATX) set to ATX1.  With ATX0 (default), the message does not appear and I get CONNECT instead of ERROR.  You can mark this one as solved now!

Lex.
Reply
#4
Ok, I will look into the extended codes. You shouldn't be getting error unless there is one!
Reply
#5
Thanks!   Cool
Reply




Users browsing this thread: 1 Guest(s)