OK, so the description above is 100% repeatable with xDot and AT firmware 3.2.1, as far as I can tell.
I did the following:
Boot up (USB to PC). Type the following commands manually @19200 baud:
+++\r\n
at\r\n
Of course, since the xDot is configured @115200 baud, I get garbage back. Switch to 115200 baud on the PC and send the following:
+++\r\n
at\r\n
The modem responds with the echo characters, excluding the \r\n:
+++at
The normal response would be (communicating @115200 baud from the start):
+++
Command not found!
ERROR
at
OK
This behavior is the same with 3.1.1 and 3.2.1 with both mDot and xDot.
Now, this is an issue for our design, as the “next generation” hardware will not be able to switch off the power of the modem.
Is there any way to get the Dots to “exit” the mode that they’re in? Like an Abort sequence?