www.ezurio.com
7.3.1.5Bluetooth
•Set the module to be a master or slave
•Make a Bluetooth connection to a specified device
•Perform a full inquiry for other Bluetooth devices
•Query a remote device to check if a service is offered
•Fetch the friendly name of a remote device
•Increase or decrease the delay before the master abandons a connection attempt
•Change the device class code
•Set the device’s friendly name
•Change the Inquiry scan time
•Change number of returned devices from an inquiry scan
•Obtain the RSSI value for a connection
7.3.1.6Power Management
•Decrease or increase the output power to suit your connection range
•Configure the modules to work in Sniff and other low power modes.
7.4Multipoint Firmware
For multipoint operation, the same hardware can be loaded with multipoint software. Whereas the firmware for single point ‘AT’ communication only allows one connection to be active at any one time, using multipoint firmware allows a number of simultaneous connections to be made and maintained. It also allows connections to multiple profiles to one or more devices. Multipoint firmware should be seen as a concept of channels instead of slave connections.
When operating in Bluetooth multipoint mode, the resources and bandwidth of a Bluetooth master device are shared amongst the different connected devices. This has an impact on the maximum throughput to any one device. If multiple device connections are maintained it also impacts on the memory resources and device database within the Bluetooth stack. Designers should be aware of these restrictions when using multipoint configurations. In most cases better latency and power consumption can be achieved by polling or fast data transfer rather than by maintaining concurrent connections.
In general, multipoint connections are viable for up to three connections, but other connection schemes become appropriate if a greater number of devices are being deployed.
7.5OTA (Over the Air) Configuration
When the BISM2 has its remote AT parser enabled, its settings can be remotely controlled by a master unit (see register S536). This places the slave unit’s AT parser in remote mode providing over the air configuration. This mode is of use for remote sensor applications, where no host processor is required to control the slave Bluetooth unit.
7.6Boot modes
The module has the capability of booting into 1 of 7 modes. Currently only Boot Mode 1 is supported.
Boot Mode 1 is default and gives functionality equivalent to the BISM1 module.
These modes will specify different PSKEY settings to allow for different basic operation. Please contact Ezurio for further information.
