Showing posts with label bluetooth. Show all posts
Showing posts with label bluetooth. Show all posts

Saturday, February 26, 2011

Bluetooth - Introduction

Thanks to Bluetooth Application Developer’s Guide

Continuation...

Wireless connectivity offers us immense freedom and convenience. It allows us to perform tedious tasks with a minimum of intervention, allows some of our devices to have dual functionality, and makes the vast array of cables we inevitably always leave in the office redundant. Bluetooth technology "will" change the assumptions we all have about our electronic devices.With the cables gone, the idea of having a particular gadget for a specific job will no longer be relevant. With many of the devices already available to consumers, this scenario grows closer to reality every day.

Safety-critical

Although the Bluetooth specification with a frequency-hopping scheme which does provide robustness, it is still a serious consideration for some applications. Bluetooth technology should not be used for safety-critical applications where data absolutely must get through, because there is always a possibility of a burst of interference stopping the link. Interference can come from a variety of sources: microwave ovens, thunderstorms, other communications systems. There are other safety-critical applications where an unreliable link may be acceptable.

Connection Times

There are two delays in setting up a Bluetooth link. First, it takes time to discover devices in the neighborhood. In device discovery, a device sends out inquiry packets, and receives responses from devices in the area, then reports these to the user. It can take ten seconds to find all the devices in an area, and even then you will only find those devices which are willing to report their presence. Some devices may not be set to scan for inquiries, in which case you will never find them!

A second delay occurs when you set up the connection itself. Again, this can take up to ten seconds.This lengthy connection time means that Bluetooth devices are unsuitable for systems where a fast response is needed, such as automatic toll collection on busy roads.

Power and Range
Power is a critical consideration for wireless devices. With the cable gone, the subject of batteries is brought into focus, and the inevitable questions arise concerning battery life, standby time, and physical dimensions. Keeping the power consumption low is an important consideration.

The range of battery life depends upon the product functionality. Power consumption is much higher when either transmitting or receiving, so the longer you expect your product to be in these states the shorter the battery life. Clever power management design, battery monitoring and use of the Bluetooth power saving modes will all contribute to reducing power consumption.

The Bluetooth specification defines three power classes for radio transmitters with an output power of 1 mW, 2.5 mW and 100 mW.The output power defines the range that the device is able to cover and thus the functionality of your product must be considered when deciding which power class to use.

Thursday, February 17, 2011

Bluetooth - Introduction

Thanks to Bluetooth Application Developer’s Guide 

Communication between electronic devices can only be achieved when they also abide by a set of predetermined rules and standards—the Open Systems Interconnect (OSI) model for communications systems protocol stacks being the primary example, and the basis from which many others have evolved.

New technologies are now emerging that allows wireless communication. The IEEE 802.11b or Wi-Fi standard is becoming accepted as the choice for the networking community. IEEE 802.11b has a data throughput of up to 11 Mbps, which gives it viability against wired networks. This technology is expensive and therefore not compatible with price-conscious consumer products, but we have now been provided with the means to create wireless, low-power, cost-effective, unconscious and ad-hoc connectivity between our devices. Its name: Bluetooth.

Wired and Wireless

In the wired solution scenario that we are all accustomed to, all of the mobile devices are used in the singular—the interaction between them is always user initiated.

The alternative – In Bluetooth - The simple act of utilizing Bluetooth technology as cable replacement removes the problem of the actual physical connections and the unconscious and ad-hoc connection capability of the technology can allow communication between the devices with no user intervention at all (OK, after some software configuration and initial device setup!)


This fully wireless scenario can be achieved because of the master/slave nature of the Bluetooth technology. All devices are peers, identified by their own unique 48-bit address, and can be assigned as a master either by function or user intervention. A master can connect to up to seven slaves at the same time, forming a piconet—this “point-to-multipoint” feature is what sets Bluetooth apart from other wireless technologies.

To be continue...