Some hang-up issues
#11
This works perfectly on my Amiga. AT&Qx has nothing do with hanging up. AT&D2 is what controls the DTR for hanging up.
Reply
#12
Sorry, that was a typo. Setting &D2 does not hang up the modem when DTR is lowered.
In fact, with the following setup it hangs up immediately upon connect (the following is a direct cut and paste from ZTerm):
AT&V
C0 E1 L0 M0 N0 Q0 V1 X1 S0:0 S1:0 S2:43 S3:13 S4:10 S5:8 S6:2 S7:60 S8:2 S9:6 S10
:15 S11:90 S12:50 S25:0 S30:30 S37:6 *B9600 *BL512 *C0 *D0 *L6400 *LED2 *P1541 *R
0 *T0 &C1 &D2 &K0 &Q2 &S0

For instance:
AT&D2
OK
ATDT A80SAPPLEIIBBS.DDNS.NET:6502
CONNECT 9600

NO CARRIER

I'm starting to think this WiModem232 has some sort of defect.
Or am I initializing it improperly?
Reply
#13
Well, if it hangs up immediately then the hang up is working, but seems like it is inverted.  I will look into it.  I think the Amiga is actually inverted.

I got my Apple //e and Apple //gs systems setup today.  So, I will be going through ProTERM and setting them up correctly, and then I will go on to setting up GBBS.
Reply
#14
(02-17-2018, 07:18 PM)admin Wrote: Well, if it hangs up immediately then the hang up is working, but seems like it is inverted.  I will look into it.  I think the Amiga is actually inverted.

I got my Apple //e and Apple //gs systems setup today.  So, I will be going through ProTERM and setting them up correctly, and then I will go on to setting up GBBS.

Thanks.
PM me an I'll email you a working 800K image of GBBS and the setup manual for you to play with.
Reply
#15
OK, thanks!
Reply
#16
Looking forward to seeing what you figure out with this!
- Jarrod Kailef, Wearer of Many Hats

[Image: SignatureRow.png?raw=1]
Reply
#17
I've got this same exact issue while working with an S-100 system under CP/M, although I'm working it from the inbound direction.
AT&V reports:
B0 C0 E1 L0 M0 N0 Q0 V1 X1 S0:0 S1:0 S2:255 S3:13 S4:10 S5:130 S6:2 S7:45 S8:2 S
9:6 S10:25 S11:90 S12:50 S25:25 S30:30 S37:6 *B9600 *BL512 *C0 *D0 *L6400 *LED5
*P1541 *R0 *T1 &C1 &D2 &G0 &K0 &Q0 &S2

On connect, the S-100 system sees the ring indication and sends the ATA command to answer the phone.  It then instantly disconnects and reports it as a "voice" call.  I've noticed that despite &S2, the DSR does not match the connection state.  The serial board in my system uses an 8251A USART, so it's common to track the DSR to detect the connection state as the chip doesn't support the DCD line.

I'm using a WiModem232 v2 on firmware v3.02.  

Suggestions? 

Tnx!

g.
Reply
#18
Are you trying to call from the WiModem232 to your S-100? DSR never has the connection state no matter what you have it set to, per the Hayes standard. It is typically used to tell the terminal if it is in command mode or not.

The receiving side can only know about a connection by either monitoring the communications and watching for a "CONNECT" message or by monitoring the DCD line. After a connection occurs, only the state of the DCD line can tell the modem that the connection is active or has been lost.
Reply
#19
Telnet client to WiModem232 on the S-100 system. The DCD line doesn't tell the modem anything, it tells the /host/ whether or not the modem has a carrier. (DCD is an input, not an output.)

Is there an AT command in the WiModem232 firmware that will force DSR to follow DCD?

tnx.

g.
Reply
#20
No, because that is not the Hayes standard. The WiModem232 follows the Hayes standards. That standard uses DCD to determine the connection status (active or inactive).
Reply




Users browsing this thread: 4 Guest(s)