SPBT2532C2AT STMICROELECTRONICS | Alldatasheet

Document overview

  • Manufacturer or author: Provided By ALLDATASHEET.COM(FREE DATASHEET DOWNLOAD SITE)
  • PDF pages: 48

Technical content

Datasheet sections

  • 1 RoHS compliance
  • 2 Application
  • 3 Block diagram
  • 4 Electrical characteristics
  • 4.1 Absolute maximum ratings
  • 4.2 Operating ranges
  • 4.3 Power consumption
  • 4.4 DC I/O specification
  • 5 Bluetooth parameters
  • 5.1 RF performance characteristics
  • 6 Pin settings
  • 6.1 Pin connections
  • 6.2 Pin description
  • 7 Software architecture
  • 7.1 Lower layer stack
  • 7.2 Upper layer stack: amp’ed UP
  • 7.3 AT command set: abSerial
  • 8 Hardware design
  • 8.1 Component drawing
  • 8.2 UART interface
  • 8.3 Typical circuit
  • 9 Soldering

Datasheet sections

Datasheet sections

Features

■ Bluetooth® specification compliant V2.1 ■ Output power class-2 ■ Transmission rate up to 2 Mbps with EDR ■ Point-to-point ■ Packet types supported: – ACL: DM1, DM3, DM5, DH1, DH3, DH5, 2- DH1, 2-DH3, 2-DH5 ■ Adaptive frequency hopping (AFH) ■ Efficient and flexible support for WLAN coexistence in collocated scenario ■ Communication interfaces: (a) – Fast UART up to 3.25 Mbit/s – SPI interface –I 2C interface –I 2S interface ■ General I/O: (a) – 4 general purpose I/O – 4 x 12-bit A/D input ■ User interface: – AT command set ■ Memory: – 256 Kbytes Flash memory – 48 Kbytes RAM memory ■ 3.3 V single supply voltage ■ No external oscillator required ■ Module size: 10 x 13 mm

Description

The SPBT2532C2.AT is a surface-mount PCB module that provides fully embedded, ready-to-use Bluetooth wireless technology. It is designed for maximum performance in a minimal space and includes 4 general purpose (a) and 4 A/D IO lines (a), several serial interface options (a), and up to 2 Mbps data throughput. The re-programmable Flash memory contains embedded firmware for serial cable replacement using the Bluetooth SPP profile. a. All these resources cannot coexist at the same time; they are shared on the 8 pins available for interface. Standard configuration for AT command set is 4 pins for UART and 4 pins for GPIO.

SPBT2532C2.AT Contents Doc ID 16089 Rev 3 3/48

SPBT2532C2.AT Contents Doc ID 16089 Rev 3 5/48

SPBT2532C2.AT RoHS compliance Doc ID 16089 Rev 3 7/48

1 RoHS compliance

ST modules are RoHS compliant and being based on ST devices comply with ECOPACK® norms implemented by ST.

2 Application

  • Serial cable replacement
  • Industrial control
  • Medical
  • POS terminals
  • Data acquisition equipment
  • Internet access points
  • Machine control
  • Sensor monitoring
  • Robotic and bionic control
  • Security control
  • Patient monitoring
  • Wireless printers
  • Cordless terminals
  • Laptops, PCs and accessories
  • Handheld devices and accessories
  • HID devices (keyboard, mouse, joystick, game controller…)

3 Block diagram

Figure 1. Block diagram

4 Electrical characteristics

4.1 Absolute maximum ratings

4.2 Operating ranges

Table 1. Absolute maximum ratings Table 2. Operating ranges

4.3 Power consumption

  • CPU 32 MHz
  • UART supports up to 921 Kbps
  • Data throughput up to 2 Mbps

4.4 DC I/O specification

Table 3. High speed CPU mode Table 4. DC input / output specification

5 Bluetooth parameters

5.1 RF performance characteristics

  • Test condition: nominal
  • Voltage: typical, VIN = 3.0 V
  • Temperature: typical TA = 25 °C Note: For more complete data, please refer to STM STLC2500D datasheet.

Table 5. RF performance characteristics

6 Pin settings

6.1 Pin connections

Figure 2. Pin connection diagram

6.2 Pin description

Table 6. Pin description

13 RXD I Receive data ADC3 (1)

  1. ADC pin functions are not 5V tolerant, when used as ALT pin function. Otherwise the I/O pins are all 5V

14 TXD O Transmit data ADC2

11 CTS I Clear to send (active low) ADC0/I 2C Data/Aux Uart Rx

12 RTS O Request to send (active low) ADC1/I 2C Clock/Aux Uart Tx

6 ANT RF I/O 50 Ω Rx/Tx antenna port

9 Reserved I Boot 0

10 RESETN I Reset input (active low for 5 ms);

1 GPIO [1] I/O General purpose input/output SPI MISO

2 GPIO [2] I/O General purpose input/output SPI MOSI/I 2S_SD

3 GPIO [3] I/O General purpose input/output SPI SCLK/ I 2S_CK

4 GPIO [4] I/O General purpose input/output SPI SS/I 2S_WS

7 Software architecture

Figure 3. Bluetooth firmware implementation

SPBT2532C2.AT Software architecture Doc ID 16089 Rev 3 15/48

7.1 Lower layer stack

  • Full Bluetooth v2.1 data rate (3M bps maximum)
  • Device power modes—active, sleep and deep sleep
  • Wake on Bluetooth feature—optimized power consumption of host CPU
  • Authentication and encryption
  • Encryption key length from 8-bits to 128-bits maximum
  • Persistent Flash memory—for BD Address and radio parameter storage
  • ACL (Asynchronous Connection Less) packet types (DM1, DH1, DM3, DH3, DM5, DH5, 2-DH1, 2-DH3, 2-DH5)
  • Point to point support
  • Park, sniff, and hold modes—fully supported to maximum allowed intervals (see Appendix B: )
  • Master slave switch—supported during connection and post connection
  • Dedicated inquiry access code—for improved inquiry scan performance
  • Dynamic packet selection—channel quality driven data rate to optimize link performance
  • Dynamic power control—interference reduction and link performance
  • Bluetooth test modes—per Bluetooth v2.0 specification
  • 802.11b/g co-existence—AWMA and AFH
  • Vendor specific HCI commands—to support device configuration and certification test modes

7.2 Upper layer stack: amp’ed UP

  • SPP , SDAP , GAP protocols
  • RFComm, SDP , and L2CAP supported

7.3 AT command set: abSerial

  • Please see Appendix B: abSerial reference guide for details

8 Hardware design

  • All unused pins should be left floating; do not ground.
  • All GND pins must be well grounded.
  • Traces should not be routed underneath the module.

8.1 Component drawing

Figure 4. Pin placement Figure 5. Ground plane diagram

8.2 UART interface

Figure 6. Connection to host device

8.3 Typical circuit

Figure 7. Typical RS232 circuit

9 Soldering

phenomenon, particular attention has to be taken on the set up of the peak temperature. IPC/JEDEC J-STD-020C, July 2004 recommendations. Figure 8. Soldering Table 7. Soldering

SPBT2532C2.AT Certifications Doc ID 16089 Rev 3 19/48 Appendix A Certifications A.1 FCC compliance FCC licensing is dependent on final antenna implementation. Many tests do not need to be repeated for final compliance and certification.

service using the Bluetooth serial port profile. command interface, (abSerial) SW developed by Amp’edRF . Figure 9. SW developer Errors responses are also detailed in this document. The following acronyms are used in this document. Table 8. Definitions and acronyms

refer to the abserial user guide. through an AT command interface as shown below. Figure 10. Communications between hosts

  • Point-to-point connection – abSerial only supports a connection with one device at a time.
  • Optional MultiPoint applications are available upon request
  • Serial port profile – SPP is supported wit h abSerial for both Client and Server application.
  • Optional dial up networking – DUN profile support for Client applications (DUN Server is not currently supported).
  • Optional OBEX profiles are available upon request
  • Command and bypass modes – it is possible to switch between command and bypass (data transmit/receive) modes during an active connection
  • Security – Bonding and data encryption provides a secure link between two devices.
  • Multiple device bonding – special security keys can be exchanged with multiple devices to allow different devices to securely connect with abSerial.
  • Power conservation – use of the sniff feature to minimize power consumption.
  • Variable baud rates – the serial port can be configured for the following baud rates: AT Cmds Host Device Bluetooth Device Bluetooth Device

SPBT2532C2.AT 22/48 Doc ID 16089 Rev 3 B.5 Factory defaults

  • The follow factory defaults are typically shipped with our standard products. Customized defaults may be ordered upon request.
  • UART: 115200 baud, no parity, 1 stop bit, 8 data bits
  • Local name: “Amp’ed UP!”
  • Class of device: misc device
  • Profile: SPP (serial port profile)
  • Service name: “AMP-SPP”
  • Deep sleep: disabled
  • Page and inquiry scan: 1.28 s interval, 11 ms duration
  • Security: disabled
  • Bonding PIN: “1234”
  • Bonding allowed: always enabled

behavior, syntax of the command, context of the command, and types of responses. Table 9. abSerial command summary

include an approximate delay before response. Error responses are described in Appendix D error responses. identification number (PIN) is also required with this command. is the PIN code to use (up to 16 characters). Table 9. abSerial command summary (continued)

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 25/48 C.2 Build The version command is used to return the current version of the abSerial interface. C.2.1 Syntax AT+AB Build C.2.2 Responses If the operation is successful, the response is: AT-AB abSerial Build [date] where [date] is the date code of the application firmware. C.3 Bypass The Bypass command is used to return the abSerial interface to the bypass mode, if a connection is still available. The possible use for this is to change a setting after a connection has been made (such as the UART baud rate). If the abSerial interface does not have a connection, it will respond as if the connection is down. C.3.1 Syntax AT+AB Bypass C.3.2 Responses If a connection is still available, the response is: AT-AB -BypassMode- If there is currently no connection, the response is: AT-AB ConnectionDown C.4 ChangeBaud The host sends the ChangeBaud command in order to change the local UART speed to a new speed identified by the host. This setting will only remain in effect during the current session - until reset. C.4.1 Syntax AT+AB ChangeBaud [rate]

Commands SPBT2532C2.AT 26/48 Doc ID 16089 Rev 3 where [rate] is the new baud rate:

  • 1200
  • 2400
  • 4800
  • 9600
  • 19,200
  • 38,400
  • 57,600
  • 115,200
  • 230,400
  • 460,800
  • 921,600 C.4.2 Responses If the change is accepted, the response is: AT-AB Baudrate Changed The actual change will not occur until the response has been completely transmitted. C.5 ChangeDefaultBaud The host sends the ChangeDefaultBaud command in order to change the default UART speed to a new speed identified by the host. This command is used to override the default baud rate from the Dynamic Configuration script so that the device does not require reprogramming to update this setting. The new baud rate is updated permanently until the device is either re-programmed or another ChangeDefaultBaud command is issued. The baud rate specified in the command will not take effect until the device is reset. To change the baud rate of the current session, use the ChangeBaud command. C.5.1 Syntax AT+AB ChangeDefaultBaud [rate] where [rate] is the new baud rate:
  • 1200
  • 2400
  • 4800
  • 9,600
  • 19,200
  • 38,400
  • 57,600
  • 115,200
  • 230,400
  • 460,800
  • 921,600

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 27/48 C.5.2 Responses If the change is accepted, the response is: AT-AB Baudrate Changed C.6 DefaultLocalName The DefaultLocalName command is used to set the name of the device to the name that is reported during device discoveries. By default, the abSerial interface uses “Amp’edBTDevice”. Changing the name using this command will permanently change the local name, unlike the LocalName command. C.6.1 Syntax AT+AB DefaultLocalName [name] Where [name] is a string for the new local name (up to 50 characters). The space character is allowed; the name is assumed to be all text up to the end of the command. C.6.2 Responses If the operation is successful, the response is: AT-AB LocalNameOk C.7 DeleteSmartCable The DeleteSmartCable command removes the current Smart Cable settings that were entered using the SmartCableSetup command, but not the setting from the dynamic configuration. The Smart Cable will then be deactivated for the remainder of this session. Upon reset, if a dynamic configuration for a Smart Cable exists, it will be activated. If there is no dynamic configuration Smart Cable setup, then this feature will remain deactivated. C.7.1 Syntax AT+AB DeleteSmartCable C.7.2 Responses If the operation is successful, the response is: AT-AB DeleteSmartCableDone

Commands SPBT2532C2.AT 28/48 Doc ID 16089 Rev 3 C.8 DisableBond The DisableBond command is used to disallow new bonding with a device. This command cannot be used while a connection is active. C.8.1 Syntax AT+AB DisableBond C.8.2 Responses If the operation is successful, the response is: AT-AB BondDisabled C.9 Discovery The Discovery command is used to initiate a device discovery. The command will return the number of responses of nearby devices and then the individual responses with BD address, name of device. The number of devices returned is limited to 10. Inquiry is performed with an interval of 10.24 seconds. The devices are reported in the same order as the original inquiry results. C.9.1 Syntax AT+AB Discovery AT+AB Discovery [CoD] AT+AB Discovery [CoD] [profile] [include service enable/disable] C.9.2 Responses When the discovery command has been accepted, the response is: AT-AB InqPending Once the initial inquiry is complete and discovery has been started, the response is: AT-AB DiscoveryPending [num] where [num] is the number of devices found, in decimal (up to 10 will be reported). For each name or service name request that is successful, the response uses the returned names in the following format. AT-AB Device [BD addr] [name] AT-AB Device [BD addr] Unknown C.10 DUNConnect The DUNConnect command is used to initiate a connection with the specified device. The remote BD address must be specified. The remote Service is optional. If not specified, the first registered DUN service will be used by default.

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 29/48 C.10.1 Syntax AT+AB DUNConnect [BD Addr] [Service] Where [BD Addr] is the remote devices BD Address to page. [Service] is the specific service on the remote device; optional. C.10.2 Responses If the connection is successful, the response is: AT-AB ConnectionUp AT-AB -BypassMode- If the connection cannot be completed, the response is: AT-AB DUNConnectionClosed C.11 DUNDisconnect The DUNDisconnect command is used to terminate a connection with the remote device. C.11.1 Syntax AT+AB DUNDisconnect C.11.2 Responses If the connection is successful, the response is: AT-AB DUNConnectionClosed C.12 EnableBond The EnableBond command is used to enable bonding with another device. The BD Address, PIN and timeout parameters are optional. When no BD Address is specified, requests from all BD Addresses are allowed. If a BD Address is specified, bonding requests from devices with BD Addresses other than the one specified will fail and the existing link key will be deleted for that device. Optionally, a PIN code may be entered with this command. If no PIN code is specified, the default PIN code will be used. The default PIN code is either the last 4 digits of the device’s BD address or the dynamically configured PIN code, depending on the default PIN selection in the dynamic configuration file. Also, a timeout value, in seconds, may be entered after the PIN code. Bonding will be disabled automatically after the requested timeout. If no timeout is specified, bonding is enabled until reset or until the DisableBond command is used. If this command is issued multiple times, only the last PIN and BD address are saved. Also, if this command is issued before the first timeout occurs, the subsequent command will extend the timeout. The timeout is always set to the specified time beyond the last received EnableBond.

Commands SPBT2532C2.AT 30/48 Doc ID 16089 Rev 3 C.12.1 Syntax AT+AB EnableBond AT+AB EnableBond [BD addr] AT+AB EnableBond [BD addr] [PIN] AT+AB EnableBond [BD addr] [PIN] [timeout] Where [BD addr] is the BD Address of the remote device with which to bond, [PIN] is the PIN code to use (up to 16 characters), and [timeout] is the duration of the timeout in seconds (1 to 14,400, in decimal). C.12.2 Responses If the operation is successful, the response is: AT-AB BondEnabled If bonding has been initiated by a remote device, the notification is: AT-AB BondPending [BD addr] where [BD addr] is the BD address of the remote device that initiated the bonding. If bonding has occurred, the notification is: AT-AB BondOk [BD addr] where [BD addr] is the BD address of the remote device with successful bonding. If bonding was initiated by a remote device but failed, the notification is AT-AB BondFail When the time limit for bonding has expired, the notification is AT-AB BondDisabled C.13 EraseBondTable The EraseBondTable command is used to erase all of the bonded device entries. Single devices cannot be erased with this command C.13.1 Syntax AT+AB EraseBondTable C.13.2 Responses If the operation is successful, the response is: AT-AB BondTableErased C.14 ExitPark The ExitPark command is used to switch a device from park mode to active mode.

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 31/48 C.14.1 Syntax AT+AB ExitPark [BD address] Where [BD address] is the BD address of the device to be switched to active mode. C.14.2 Responses If the operation is successful, the response is: AT-AB ActiveMode C.15 ExitSniff The ExitSniff command is used to switch a device from sniff mode to active mode. C.15.1 Syntax AT+AB ExitSniff [BD address] Where [BD address] is the BD address of the device to be switched to active mode. C.15.2 Responses If the operation is successful, the response is: AT-AB ActiveMode C.16 GPIOConfig The GPIOConfig command is used to configure a GPIO pin to input or output. C.16.1 Syntax AT+AB GPIOConfig [GPIO Pin] [Configuration] Where [GPIO Pin] is the Pin number, 1 – 4, of the desired GPIO to configure. [Configuration] is i or I for input and o or O for output. C.16.2 Responses If the operation is successful, the response is: AT-AB GPIOConfigDone C.17 GPIORead The GPIORead command is used to read a GPIO pin. A GPIO may be read while configured as either an input or output. C.17.1 Syntax AT+AB GPIORead [GPIO Pin]

Commands SPBT2532C2.AT 32/48 Doc ID 16089 Rev 3 Where [GPIO Pin] is the Pin number, 1 – 4, of the desired GPIO to read. C.17.2 Responses If the operation is successful, the response is: AT-AB GPIOReadDone [result] Where [result] is either a 1 to indicate high, or 0 to indicate low. C.18 GPIOWrite The GPIOWrite command is used to set a GPIO pin to high or low. A GPIO may only be set when configured as an output. C.18.1 Syntax AT+AB GPIOWrite [GPIO Pin] [Setting] Where [GPIO Pin] is the Pin number, 1 – 4, of the desired GPIO to read. [Setting] is a 1 to set a pin to high and a 0 to set a pin to low. C.18.2 Responses If the operation is successful, the response is: AT-AB GPIOWriteDone C.19 Hold The Hold command is used to switch a device from active mode to hold mode. C.19.1 Syntax AT+AB Hold [BD address] [Hold Duration] Where [BD address] is the BD address of the device to be switched to active mode. [Hold Duration] is given in slots from 4-10,000. C.19.2 Responses If the operation is successful, the response is: AT-AB HoldMode C.20 HostEvent The HostEvent command is used to enable/disable the host notification strings. This will override the default setting in the dynamic configuration only for the current session; until reset. C.20.1 Syntax AT+AB HostEvent [Enable/Disable]

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 33/48 Where [Enable/Disable] is an e or E character to enable this parameter and a d or D character to disable it. C.20.2 Responses If the feature is successfully enabled, the response is: AT-AB HostEvent Enabled If the feature is successfully disabled there is no response because the events have been disabled. C.21 LocalName The LocalName command is used to set the name of the device to the name that is reported during device discoveries. By default, the abSerial interface uses Amp’edBTDevice. Changing the name using this command does not permanently change the local name. C.21.1 Syntax AT+AB LocalName [name] Where [name] is a string for the new local name (up to 50 characters). The space character is allowed; the name is assumed to be all text up to the end of the command. C.21.2 Responses If the operation is successful, the response is: AT-AB LocalNameOk C.22 Park The Park command is used to switch a device from active mode to park mode. C.22.1 Syntax AT+AB Park [BD address] [Beacon Period] Where [BD address] is the BD address of the device to be switched to active mode. [Beacon Period] is given in slots from 200-10,000. C.22.2 Responses If the operation is successful, the response is: AT-AB ParkMode C.23 RemoteCommand The RemoteCommand command is used to enable/disable the remote command mode. This setting is stored in persistent memory, and will be retained after each reset. Additionally, the new setting will take effect upon the next device reset.

Commands SPBT2532C2.AT 34/48 Doc ID 16089 Rev 3 C.23.1 Syntax AT+AB RemoteCommand [Enable/Disable] Where [Enable/Disable] is an e or E character to enable this parameter and a d or D character to disable it. C.23.2 Responses If the feature is successfully applied, the response is: AT-AB RemoteCommand [Enabled/Disabled] C.24 RemoteCmdDisconnect The RemoteCmdDisconnect command is used to disconnect a remote command connection. This command only applies to the server side of the link; the remote device. The client or local device, if using the abSerial interface, should use a SPPDisconnect command since it is not in Remote Command mode. C.24.1 Syntax AT+AB RemoteCmdDisconnect C.24.2 Responses If the operation is successful, the response is: AT-AB RemoteCmdModeClosed C.25 Reset The Reset command is used to reset the abSerial interface. This is provided in the event that a host application wants to perform a software reset for error recovery. There is a response prior to reset to verify the command was received by the abSerial interface. C.25.1 Syntax AT+AB Reset C.25.2 Responses If the operation is successful, the response is: AT-AB ResetPending

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 35/48 C.26 Security The Security command is used to set the security level of the device in use. By default, security level none is used.

  • Variable pin type (the pincode request event will always be received by the application from the stack), and
  • 128-bit unit key. Service level security, level 2, is not currently supported. The security setting is not preserved in non-volatile memory. C.26.1 Syntax AT+AB Security [level] where [level] is the type of security to use:
  • None
  • Link (default) C.26.2 Responses If the operation is successful, the response is: AT-AB SecurityOk C.27 SmartCableSetup The SmartCableSetup command is used enable and configure a Smart Cable device. A device’s BD Address is specified with which to automatically establish a connection; replacing the need for AT connection commands. This command will override the dynamic configuration of a Smart Cable device until the DeleteSmartCable command is issued; it is saved in non-volatile memory. C.27.1 Syntax AT+AB SmartCableSetup [BD address] [Attempts] [Interval] Where [BD address] is the BD address of the remote device to page and attempt to connect. [Attempts] 0 – 999 is the number of pages the will be attempted to the specified device until a connection is successful. A value of 0 will not automatically page the remote device, however, GPIO 7 may be asserted to manually send a page. A value of 1000 will perform unlimited pages until connected. be switched to active mode. [Sniff Interval] is given in slots from 66-10,000. [Interval] 1-1000 is the number of 100ms intervals (0.1sec to 100 sec) between page attempts. This interval is in addition to the amount of time required by the page attempt itself. C.27.2 Responses If the operation is successful, the response is: AT-AB SmartCableConfigDone

Commands SPBT2532C2.AT 36/48 Doc ID 16089 Rev 3 C.28 Sniff The Sniff command is used to switch a device from active mode to sniff mode. C.28.1 Syntax AT+AB Sniff [BD address] [Sniff Interval] Where [BD address] is the BD address of the device to be switched to active mode. [Sniff Interval] is given in slots from 66-10,000. C.28.2 Responses If the operation is successful, the response is: AT-AB SniffMode C.29 SPPConnect The SPPConnect command is used to initiate a connection with the specified device. The remote BD address must be specified. The remote Service is optional. If not specified, the first registered SPP service will be used by default. C.29.1 Syntax AT+AB SPPConnect [BD Addr] [Service] Where [BD Addr] is the remote devices BD Address to page. [Service] is the specific service on the remote device; optional. C.29.2 Responses If the connection is successful, the response is: AT-AB ConnectionUp AT-AB -BypassMode- If the connection cannot be completed, the response is: AT-AB SPPConnectionClosed C.30 SPPDisconnect The SPPDisconnect command is used to terminate a connection with the remote device. C.30.1 Syntax AT+AB SPPDisconnect C.30.2 Responses If the connection is successful, the response is AT-AB SPPConnectionClosed

SPBT2532C2.AT Commands Doc ID 16089 Rev 3 37/48 C.31 StreamingSerial C.31.1 Syntax AT+AB StreamingSerial [Enable/Disable] Where [Enable/Disable] is an e or E character to enable this parameter and a d or D character to disable it. C.31.2 Query An alternative syntax may be used to query the current StreamingSerial feature status. This syntax is not supported by other commands. AT+AB StreamingSerial C.31.3 Responses If the feature is successfully applied or queried, the response is: AT-AB StreamingSerial [Enabled/Disabled] C.32 UpdateInquiryScan The UpdateInquiryScan command is used to modify the Inquiry scan parameters: mode, duration, and interval. C.32.1 Syntax AT+AB UpdateInquiryScan [mode] [duration] [interval] where[mode] is the discoverable mode:

  • 0: non-discoverable
  • 1: limited discoverability – not supported
  • 2: discoverable [duration] is the scan length in slots; 18 to 4096. The default duration is 18 slots. [interval] is the period between scans in slots; 18 to 4096. The default interval is 2048 slots C.32.2 Responses If the command is successful, the response is: AT-AB InquiryScanUpdateDone

Commands SPBT2532C2.AT 38/48 Doc ID 16089 Rev 3 C.33 UpdatePageScan The UpdateInquiryScan command is used to modify the Page scan parameters: mode, duration, and interval. C.33.1 Syntax AT+AB UpdatePageScan [mode] [duration] [interval] Where [mode] is the connectable mode:

  • 0: non-connectable
  • 1: connectable [duration] is the scan length in slots; 18 to 4096. The default duration is 18 slots. [interval] is the period between scans in slots; 18 to 4096. The default interval is 2048 slots C.33.2 Responses If the command is successful, the response is: AT-AB PageScanUpdateDone C.34 Version The Version command is used to return the current version of the abSerial interface. C.34.1 Syntax AT+AB Version C.34.2 Responses If the operation is successful, the response is: AT-AB abSerialVer [x.y] where [x.y] is the current version of the abSerial Interface.

This chapter details the error responses that occur under specific circumstances.

  • ErrConnect
  • ErrExecution
  • ErrFormat
  • ErrInProgress
  • ErrInvalidParam
  • ErrNumParam
  • ErrUnknownCmd The following subsections detail the different error responses. These error responses replace the original error response AT-AB ErrorCommand D.1 ErrConnect The ErrConnect error response will be sent if abSerial has a valid connection established and the command cannot be executed while connected (even in the command mode). Examples of commands that produce this error response are given in the following table.

Table 10. Example commands that generate <ErrConnect> AT+AB security none Changing security level while a connection is up. AT+AB discovery Performing a device discovery while a connection is up.

Examples of commands that produce this error response are given in the following table. Examples of commands that produce this error response are given in the following table. Table 11. Example commands that generate <ErrExecution> Table 12. Example commands that generate <ErrFormat>

the parameter that was rejected. Examples of commands that produce this error response are given in the following table. error; instead, the extra parameters are ignored. Examples of commands that produce this error response are given in the following table. Table 13. Example commands that generate <ErrInvalidParam>

8136 AT -AB ErrInvalidParam 8136

1600 AT -AB ErrInvalidParam 1600Numeric parameter is out of range (specified

baud rate is not supported by command). Table 14. Example commands that generate <ErrNumParam> AT+AB Security No parameters were specified. AT+AB Sniff The minimum number of parameters was not specified.

Table 15. Example commands that generate <ErrInProgress> AT+AB Discovery Trying to do discovery when the previous one has not completed.

command can produce an error response, the column will be marked with an X. Table 16. Possible ErrConnect error responses

Other responses SPBT2532C2.AT 44/48 Doc ID 16089 Rev 3 Appendix E Other responses The following subsections describe the 4 types of responses that occur under specific circumstances, not necessarily as a result of a specific command. They are:

  • Reset
  • Escape sequence
  • Controlled disconnect
  • Unexpected disconnect E.1 Reset Upon either hardware reset or software reset (such as the Reset command), abSerial will respond as follows after the reset is complete: AT-AB -CommandMode- AT-AB BDAddress [BD addr] Because the BD address of the local device is reported during this response, the response is different than a response to the Escape Sequence. E.2 Escape sequence If the Escape sequence, ^#^$^%, is received and no connection is active, abSerial will immediately respond with: AT-AB -CommandMode- When the Escape Sequence is received while a connection is still active and there is no data for 2 seconds, abSerial will respond (after those 2 seconds of no data) with the same string. abSerial will now be in command mode. E.3 Controlled disconnect If the local host initiates a disconnect, it must first put the abSerial interface into command mode (see the section on Escape Sequence directly above). After a successful disconnect command, the following response is made: AT-AB ConnectionDown

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.

Table 17. Ordering information scheme

SPBT2532C2.AT Revision history Doc ID 16089 Rev 3 47/48

Revision history

Table 18. Document revision history