07-18-2019, 09:49 AM
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.
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.