01-31-2018, 06:04 PM
I understand that, but if my BBS software sees a CONNECT non verbose code of 1, it assumes that the modem has made a remote connection at 300 baud (this is the only connect speed not formally specified in the Hayes reference so the assumption is that the connection is 300 baud) and the BBS drops the serial port connection speed to the modem to 300 baud. Since the modem is stuck by AT*B1200 at 9600 baud it will not communicate with the BBS due to a port speed mismatch.
If I use the command ATX1 the message returned by the WiModem232 is still "CONNECT" not "CONNECT 9600" The non-verbose connect code returned is still 1.
What I'm asking is that a firmware option be implemented whereby the WiModem232 returns an explicit connect non verbose code (and verbose code if you'd like) describing the connect speed. This can be dependent on the baud rate set by the AT*B command, since the baud rate between the computer and the WiModem232 can't change anyway.
If I use the command ATX1 the message returned by the WiModem232 is still "CONNECT" not "CONNECT 9600" The non-verbose connect code returned is still 1.
What I'm asking is that a firmware option be implemented whereby the WiModem232 returns an explicit connect non verbose code (and verbose code if you'd like) describing the connect speed. This can be dependent on the baud rate set by the AT*B command, since the baud rate between the computer and the WiModem232 can't change anyway.