The serial port profile (SPP). Bluetooth Serial Adapter Hardware Interfaces. You configure the adapter by putting it into command mode and sending ASCII commands over a serial port or the Bluetooth link.Bluetooth Serial Port Adapter - Getting Started - Bluetooth Serial Port Adapter. Document Revision. Document number: 6. Release: Feb 2. 2, 2. Document version: 9. Abstract. This document describes the basic concepts and functionality of the connect. Blue Serial Port Adapter products. It is intended as a getting started guide and there are plenty of references to other relevant documentation for details. It requires some basic understanding of the Bluetooth technology. This is needed to transmit data to a specific Bluetooth channel and to know from what Bluetooth channel data is received. This requires the use of the Extended Data Mode and it requires a TCP/IP stack in the host since the Ethernet frames must carry TCP/IP data. This document describes how to configure the Serial Port Adapter to work also with those kind of smartphones. Please note that the i. Phone requires special hardware and licensing.
This document describes the relevant AT commands for optimization. The supported AT commands are described in . It is important considering the use of different type of modules (e. Bluetooth , Wireless LAN or Zig. Bee) and also when going from one generation to the next. It supports the most commonly used AT commands. See getting started guide . It is possible to configure a module to automatically setup a connection and/or accept an incoming connection. Configuration is done using AT commands. For a host it means that an existing serial cable can be replaced by a Bluetooth solution in many cases without the need to modify the host. Modes of Operation. The Serial Port Adapter can operate in three different modes; AT Mode, Data Mode and Extended Data Mode. By default the Serial Port Adapter will enter Data Mode and it has to be configured to enter Extended Data Mode instead of Data Mode. It enters AT mode by transmitting the escape sequence to the module. The USB Bluetooth dongle also works with any other Bluetooth device that uses the Bluetooth serial port profile. The USB Bluetooth radio dongle for Linux, and Windows provides seamless connectivity for the LaserChamp. Adopted Specifications. Bluetooth Core Specification 4.2 is an important update to the Bluetooth Core Specification delivering exciting new features and benefits for Bluetooth. Alert Notification Profile. By default the escape sequence is: Silence 1 second///Silence 1 second. Please note that the /// must be sent within 2. The module leaves AT Mode and enters Data Mode or Extended Data Mode using the AT*ADDM command. In AT Mode the module is configured using AT commands. For details on available AT commands see . Please note that the module does not accept incoming connections in AT mode. It is, however, possible to set up an outgoing connection using the AT*ADCP command. In Data Mode the module transmits data transparently between the serial port and the Bluetooth connection(s). There is no additional protocol for the serial port. Data transmitted on the serial port to the module will be transmitted, over air, to all Bluetooth connections. Data received from the Bluetooth connections may be interleaved upon reception and it may be difficult or impossible to figure out from what remote device data is received. It is suitable mainly for master/slave polled protocols such as e. Modbus and of course point- to- point communication. To enable control of each individual Bluetooth connection the Extended Data Mode was introduced (see . It is a simple protocol, for the serial port, which makes it possible to transmit data to one specific remote device and to know from what remote device data is received. It is also possible to execute AT commands as part of the Extended Data Mode protocol. Hence, it is not really necessary to enter AT Mode when in the Extended Data Mode. However, since it is possible to enter AT Mode from the Extended Data Mode, tools such as the Serial Port Adapter Toolbox will still work using standard AT commands in AT Mode. Note that, over air, there is no Extended Data Mode protocol data. Hence, it is possible for one side to be configured for Extended Data Mode and the other side standard Data Mode. Carrier boards. There are carrier boards for either USB or RS2. The RS2. 32 carrier board requires a crossed null modem cable. LED Indications and Buttons. There are two operational buttons and one LED. The LED indicates what mode is currently active and what activity that is currently in progress. The following color indications are used. Green: The current mode is Data Mode or Extended Data Mode and no connection attempt is in progress. Orange: The current mode is AT mode. Purple: A connection attempt is in progress. Blue: A connection is currently active. Blue Blinking: A connection is active and data is transmitted or received over air. Red Blinking: Error detected. Typically this means buffer overflow, parity or framing error detected on the UART. Please note that the LED on the USB adapter board is a 3- colour LED which means that, on the module, it corresponds to three IO pins. On another board it may be three one- colour LEDs instead. Restore Default Serial Settings. If the default serial settings button is pressed during power on, the module resets the serial settings and the escape sequence to the default values. Default serial settings is 5. N1 and HW flow control. Default escape sequence is ///Default escape sequence timing is 1s silence before and after escape sequence. Restore Factory Settings. If both the default serial settings and the external connect button is pressed during power on, the factory settings are restored. This can also be achieved by the AT& F command followed by power off/on. Configuration. Using AT commands (see . The easiest way to get started is to use the Toolbox (see . The Toolbox allows for easy configuration with the most common AT commands. Basic Settings. There are some basic commands for controlling the general Bluetooth behavior of the module. Connectable (AT*AGCM): Shall other devices be able to connect to the module? This does not affect outgoing connections. Discoverable (AT*AGDM): Shall the module be visible to remote devices making inquires? Pairable (AT*AGPM): Shall another device be able to pair (authenticate) with the module? Bluetooth name (AT*AGLN): The name found by remote devices making inquires. Class of device (AT*AGLC): Classification of what kind of device the module is. There are standard settings according to the Bluetooth specification. If a module has been configured to connect or accept an incoming connection to/from a remote device and if pairing is done (needed only once), it may be a good idea to disable both discoverable and pairable for security reasons. Client and Server. A client will initiate a Bluetooth connection and the server will accept an incoming connection. The client and server role is often mistaken for master and slave role. The master/slave role is defined at a lower level (master polls slave at radio level) and has nothing to do with client and server. By default the client will become master and the server will become slave. However, a master/slave switch during or after connection set- up will change this. The master/slave role needs only be considered for the multipoint case (see Multipoint section). To configure a client to automatically set- up a connection to a server, the correct Bluetooth profile must be configured and the remote peer must be configured. The Bluetooth profile controls what type of connection that is requested (See Bluetooth Profiles section) and the remote peer defines what server the client shall connect to. Client Profile (AT*ADDCP): The client profile must match the server profile. Number of remote peers (AT*ADNRP): Number of remote peers can be selected from 1 (point- to- point) to 7. Remote Peer (AT*ADRDRP/AT*ADWDRP): Configures what server to connect to and when to initiate the connection. The first remote peer has the peer id 0. The second remote peer has the peer id 1 and so on. To configure the server, only the Bluetooth profile needs to be considered and a module is by default configured as a Serial Port Profile (SPP) server. Server Profile (AT*ADDSP): Will only accept incoming connection attempts for the configured server profile. Some profiles can be configured in parallel. For more than one connection see also the Multipoint section. Bluetooth Profiles. The Bluetooth profiles used by the client and server defines what type of connection that is accepted. Serial Port Profile (SPP): Serial cable emulation profile to replace existing serial cables. Dial- Up Network (DUN): Modem emulation typically used by a Bluetooth device to access the Internet via a mobile phone. It requires the host to have its own TCP/IP stack. Personal Area Network (PAN): Ethernet frames over Bluetooth. Since the Ethernet frames must contain TCP/IP data, the host must have its own TCP/IP stack. In some new mobile phones PAN replaces the DUN profile to access the Internet via the mobile phone. Use PAN- PANU if the device is considered to be an end- point and PAN- NAP if the device is connected to another network (e. Typically, a mobile phone implements the PAN- NAP profile and the remote device connecting to the phone implements the PAN- PANU. For a module to support the PAN profile, the Extended Data Mode must also be configured. The client profile must match the server profile for a connection to be accepted. Please note that there are some special requirements to make the SPP profile work for i. Phone and Android smartphones (see . Best is to enable multipoint for the exact number of channels supported. For example, if a module shall be configured to support two parallel channels use the command AT*ADWM=2,0,1 instead of just enabling the maximum number of connections. In Data Mode, data is transmitted, over air, to all connected devices and data received from the remote devices is interleaved. In Extended Data Mode it is possible to transmit data to a specific remote device and to know from which remote device data is received. For the multipoint case it is important to consider the master/slave role (which is not the same as client/server). If a device has multiple Bluetooth connections active and if the device is master for all the connections, this is a piconet. If the device is master for all of the connections expect one where it is the slave this is called a scatternet. Performance for a piconet is better and more robust than for a scatternet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |