10-15-2024, 12:48 PM
That picture shows some random character being sent as part of the command string.
&S0 does nothing at all Using it is allowed, but it doesn't actually do anything so you can leave that out.
Setting AT&C0 forces the DCD to show as always connected (call present). This is wrong for how a BBS should operate. Typically, a BBS will wait on DCD to go low to know that a connection is made. The only way around that is by actually looking for "RING" to appear and then the "CONNECT" message. Speaking of connect message, the X1 command turns on extended messages. So, on a connection the BBS would see CONNECT followed by the baud rate. For a 2400 baud connection it would get CONNECT 2400 when a connection occurs.
It would be helpful if there was some description of how the BBS operates. Have you verified that the SSC is 100% working? I had a similar situation a few years ago where the SSC was swapped and the problem went away.
&S0 does nothing at all Using it is allowed, but it doesn't actually do anything so you can leave that out.
Setting AT&C0 forces the DCD to show as always connected (call present). This is wrong for how a BBS should operate. Typically, a BBS will wait on DCD to go low to know that a connection is made. The only way around that is by actually looking for "RING" to appear and then the "CONNECT" message. Speaking of connect message, the X1 command turns on extended messages. So, on a connection the BBS would see CONNECT followed by the baud rate. For a 2400 baud connection it would get CONNECT 2400 when a connection occurs.
It would be helpful if there was some description of how the BBS operates. Have you verified that the SSC is 100% working? I had a similar situation a few years ago where the SSC was swapped and the problem went away.