SPBT2532C2AT datasheet(45/48 Pages) STMICROELECTRONICS

45 / 48 page

SPBT2532C2.AT

Other responses

Doc ID 16089 Rev 3

45/48

E.4

Unexpected disconnect

Bluetooth connections may be unexpectedly dropped (e.g., in changing RF conditions).

Although it is generally assumed that a disconnect will be negotiated on the application

level, the remote device may initiate a disconnect. When that happens, the disconnect may

be unexpected. This section applies to both the general case and the unexpected

disconnect.

It is useful for the local host to be notified that a connection has been terminated when it isn’t

controlling the termination. An unexpected disconnect is essentially defined as a disconnect

that occurs while in bypass mode. If this happens, abSerial will respond with:

###NO CARRIER

AT-AB -CommandMode-

It is the responsibility of the host to prevent this string from appearing in the data stream

during normal operation.

If a remote disconnect occurs during command mode, this notification string is also sent. It

will not be sent, however, if an initial setup cannot be established or if the disconnect is

requested by the local device.

Hardware handshaking is not used to indicate a disconnection in this implementation.

Modems can use DCD (data carrier detect) to notify the DTE (data terminal entity, e.g.,

computer) that a connection is either available or unavailable.

SPBT2532C2AT Datasheet(PDF) 45 Page - STMicroelectronics