|
|
Products:
Compaq iPAQ H3970 ($750), Belkin
USB Bluetooth adapter ($79), and Ericsson T39m. Note: in this
review I will be using the Belkin replica BT adapter manufactured by
an Asian company called Tecom (part number: BT3030); the adapter is
identical to the Belkin product (less the color of the hardware) and
the configuration steps are similar. You
can find it here. I was also sent the link for another replica.
Find it here. All three adapters look and share similar features
(software, hardware).
Bluetooth (also called 802.15) as well as Wi-fi (or 802.11b) share similar
features such as the ability to wirelessly connect different computing
platforms together but mainly differ on their conceptions and use.
802.11b allows users to connect to a distance in general around 300m
while Bluetooth is much more restrictive and generally designed for
Personal Area Networks (PAN) ranging around 30-100m. 802.11b works in
a similar way that Ethernet does and uses TCP/IP as its main protocol.
Bluetooth uses the Bluetooth stack; a variety of different protocols
that allow communication; Bluetooth is also limited at around 723kbps
as opposed to 802.11b which can go as high as 11Mbps (some newer hardware
as well as the soon to be introduced 802.11g will allow up to 22Mbps
connections with similar range).
The main difference between BT and 802.11b is how the packets are sent
from and to the client machines; BT has to wait until the packet is
received and checked for error by the client (or server) to be able
to send another one. This creates higher overheads in the wireless network
and reduces the transmission speeds but also allows for more accurate
transmission of the data. The other great advantage of BT is its low
power consumption.
Now both BT and 802.11b work on a 2.4Ghz frequency creating some interference
problems if trying to make them cohabit. BT is closer to a serial than
to a true networking oriented connection where 802.11b isn't much harder
to set than a simple router. Now don't get me wrong both have advantages
and disadvantages but they're mainly designed for two different purposes
so don't try to go too far while comparing them.
First,
802.11b consumes a lot more power than BT does. It does provide higher
bandwidth and greater connection distances but also costs more to implement
than BT does. 802.11b can be as easy as picking up an 802.11b router
and a CF card, plug-and-play and you're online just as with any other
wired Ethernet setup (not much more to configure, besides maybe the
WEP for security reasons).
After upgrading to an H3970, T39 phone, I figured that a BT network
would be the best and cheapest way to create a "wireless"
network in my tiny NYC apartment. Belkin just introduced a new Bluetooth
USB adapter a couple of months ago that is supposed to have a 100m range,
plenty of distance to cover most homes and of course my place. For about
$60 I bought the Belkin replica (the Belkin adapter was back-ordered
everywhere I tried at that time). This is a cheapest alternative to
getting an 802.11b CF card and router (probably upwards to $200). Another
reason was security; you'll probably wonder why security was a concern,
well I figured that BT isn't used by many people and can become "hidden"
once the devices are bonded (read below from bonding and security).
This can be a tremendous advantage over 802.11b if you can achieve similar
or adequate connection distances.
Not to mention that I really didn't want to have to deal with creating
a sub-network at home nor did I want to get rid of my router with a
built-in print server.
Setting up the iPAQ to work with the T39:
My first step was
to setup my 3970 to work with my T39 and Voicestream (T-mobile) GPRS
service. Before starting you'll need to subscribe to the GPRS service
(starts at $5/month for 1MB and goes up). Once this is done, Voicestream
offers a tutorial online on how to set up both the iPAQ and the T39
to work together. You can find the tutorial here.
Since the instructions are pretty straight forward I won't go into it
in more details. The connection works great when you aren't using AS
at home to get online. The iPAQ will automatically initiate the connection
and boom, your on.
Bonding the devices and setting up security:
This step can be
applied to both the T39-iPAQ and the iPAQ-Desktop combo. What you'll
need to do once you establish a connection between the two devices is
to create a Bond. Bonding the devices will allow them to recognize each
other without having to search the PAN over and over again. This also
allows for increased security as the devices cannot be discovered (technically)
by other devices once you unselect the option, making the devices hidden
from outside users. This can be something very interesting if you're
like me and concerned about security (802.11b on the other hand can't
be hidden; the SSID or the wireless router will almost always show even
if your network uses encryption). Bluetooth as well as 802.11b allows
for 128bit encryption but it is already well known that 802.11b encryption
isn't hack-proof; sure your average neighbor probably won't ever know
how to hack into your WEP enabled network but I didn't want to take
the risk, especially with so many people living nearby. I'm unsure whether
or not the BT encryption is foolproof but most people don't pay much
attention to it (and again, if they don't know you have a BT wireless
network, how will the hack into it).
BT will ask you to create a passcode (similar to an encryption key).
Since I was going to connect to my T39 as well I only picked a numerical
key (very long). Make sure you write down the key as it will be used
several times during bonding (both with the T39 and the desktop). Enter
the key on the iPAQ fist. The rest of the bonding process is straight
forward: you'll be prompt to enter this key several times on the other
devices. Just play around with it, it isn't very difficult. One tip
to remember is to enable the T39 to be discovered. The option is available
under the Bluetooth menu; the phone will only remain discoverable for
3 minutes so make sure you keep it handy.
Setting
up the BT USB adapter:
This was probably the most painful part. First make sure you install
the software before plugging in the BT adapter to the hardware. The
software will install a new icon on the desktop (that you can't remove,
I didn't like that too much) for your Bluetooth Places ("My Bluetooth
Places") as well as a system tray icon (can't remove it either).
It will also create different types of connections (a new LAN, Dial-up,
FAX and so on) for all the different permitted services.
Once this is done, it's time to jump into the configuration menu. Right
click on the BT desktop icon and select "setup".
Fortunately there is only one setup page (or window) that you'll have
to deal with but the number of options can be overwhelming. Before starting
make sure that BT is turned on for all the devices! Also read the full
instructions first as there are some that need to be done before others
so I don't want you to have to go back and re-create bonding especially.
1) Setup the security to medium (this way you won't need to enter passwords
while trying to establish a connection, but still maintain encryption
and a high level of security).
2) Select the local services tab and go through all the different services. You can select which one you want to start when the computer starts as well as the security level. I decided to start all services but the Dial-up as I won't be using the T39 to go online from my desktop. All my services were setup for encryption and authentification (no authorization as this option will open some annoying pop-ups on the iPAQ especially). Also make sure that the serial port is enabled for COM5.
3)Click the accessibility tab. You might have to go back to this setting more than once but once the devices are bonded (I'll explain that in just a sec) you want this option to be Allow only paired devices and uncheck the Let other devices discover this computer.
4) Now client applications: this part is very similar to the local services option. Enable all services for authentification and encryption and make sure the serial port is setup for COM13 this time.
5) Onto to the discovery tab; here you'll want to have all devices that you want to be allowed to connect listed. You might have to go back to this option menu later as well to add a device. Also you can disable the Look for other BT devices every... (you don't really need it) once all the devices are listed below.
6) The final step is to setup the information exchange folder. In this option you're free to put the files wherever you want. It doesn't really matter.
7) Creating the Bonds: open up the My Bluetooth Place window and select the View Devices in Range option on the left panel. From there you'll be able to view all devices listed and bond them with the PC. This step isn't very complicated and I'm sure you'll figure out how to do it (just make sure you have the passcode nearby as you'll need to enter it both on the desktop and T39 several times if you already entered it on the iPAQ). Note: if the bonding doesn't seem to work, try initiating it from the other device you'd like to bond.
8) Go get some coffee and ask yourself why you ever wanted this at the first place (please don't cry yet cause if you are that far you're almost done... well not really).
9) Once the bonds are created make sure you go back to the options I previously mentioned in the setup and check or uncheck whatever you need.
10) Adding BT
Places. If you select this option you'll be able to add services
and specify which device you want the service to be on;
For instance, the two BT places I did enable where the T39 Information
Synchronization and my iPAQ File Transfer (these are really
the only two I'll ever use from the desktop). For example, once the
Info Sync is created on the desktop it will show in My
BT Places. You can right click on it to see the properties and
add options such as synchronizing Calendar, Tasks
items and so on. I only have the Contacts items enabled since
I'm not planning on using the other PIM functions on my T39. Also make
sure that encryption is checked (it should be). Same goes to create
the File Synchronization option for the iPAQ. Once this is
done, you can restart the desktop.
11) On the iPAQ
now: Turn the iPAQ BT radio back on and click on the BT Manager. Then
click on your computer icon (whatever the name is) and you should see
some options available in the action menu (most services available on
the desktop and on the iPAQ should be listed). Check the Enable Active
Sync partner in there as well.
IMPORTANT:
Now, I hope that you read this first and didn't go ahead with the setup
cause you'll need to go back to the iPAQ for some tweaking. In the BT
Manager, I setup the desktop connection as Home Device and the T39 as
Work Device. This doesn't seem to be that important besides the fact
that you can setup different security features but also signal strength.
This was an important option I wanted.
For the Home devices, I enabled for signal strength for faster transfer
but also range. This option is likely to consume more power but since
I'm at home it doesn't really matter. For the Work devices, I enabled
minimal signal for power saving and since the T39 will most likely be
in my pocket while connecting to the Internet, I don't need a very powerful
signal. Once the BT Manager is open, you can click on Tools
and then Setting for "..." (your connection "...").
You will need to enter the default passkey for all types of connections
(Home, Work, All Devices) as well as other options such as the signal
strength and the encryption.
Now here is how all of my Settings are:
Home, Work and All Device:
a) General: name of my iPAQ, and passkey
b) PIM Objects: Let
other other devices use this service enabled, Authorization
unchecked, Encryption and Passkey required checked, and everything
else checked.
c) Connections: Let other devices see me unchecked and Let
other devices connect to me checked (use the Choose Devices
option to enable only the devices you wish). Transmission power will
depend on the location (Home, Work or All Devices).
d) Serial Port same as PIM Objects with Authorization disabled.
e) File Sharing same as PIM Objects with Authorization disabled.
Also make sure you enable a folder for sharing (usually \My Documents).
Note: I did enable Authorization on File Sharing and PIM for the
Work setting as I probably won't need this while using the T39.
f) Dial-up, Encryption and Passkey enabled.
g) Exit the BT Manager, turn BT radio off and soft reset the iPAQ.
12) Almost done there. Turn the Desktop and iPAQ (with Radio BT) on.
Go in your BT Places and try to open the File Sharing on the
iPAQ (this should work now and you should see the folder that you selected
to share). If it doesn't work, try checking your settings (good luck
there).
From this point on you should be able to establish a connection of some sort with the server. If not check your steps and make sure everything is correct. As a note, you should be able to enable ICS (Internet Connection Sharing) on 2K and XP systems and access the Internet and local network. Enabling ICS can be as easy as checking the box in the network adapter (under properties) you'd like to share but if you are running a firewall or other service that may affect your IP configuration, ICS might not work for you. Even after a few hours trying to get it to work, my WinXP Pro system wouldn't let me share the Internet connection. I'm under the assumption that the two firewalls in conjunction to a router prevent the ICS to properly work on my system. If you have ICS enabled, simply go in your BT Manager and under the Action menu try to connect to the Network service of the server. If this doesn't work for you, proceed to the next step.
13) Now the fun
part: setting up Active Sync. First for some reason BT only allows you
to connect to the Internet or your mail through Active Sync so you'll
need to enable this before behind on the network. (Make sure that the
Internet Pass-through option is enabled in ActiveSync).
Note: If you click on your computer in the
BT Manager, you'll be able to access all the different services running
on the desktop. For instance, you'll be able to connect to the Network
but this won't allow (well at least I couldn't get it to work) to sync
with the desktop or go online (though it should). I didn't try to connect
to network shares with this option but it should work as well.
In any case if you want to use Active Sync you'll need to do this: first
option the Active Sync connection manager on the desktop. Disable USB
sync (for now) and enable AS through the serial COM5. Now go back to
the PPC BT manager and click on your computer (just to make sure that
a connection is established; this process isn't necessary but I found
it to help). Once this is done go back to the Today screen and click
on the BT icon in the lower right of the screen. Select the Start ActiveSync
option.The iPAQ should initiate the connection with AS. Once this is
done and the device is synchronized, you may go back and re-enable the
USB Sync in AS.
Congratulations,
you're done. Now the last and final thing is to get it to work at all
times. The connection speed won't be anywhere near 802.11b and even
though the wireless serial connection should be limited to 115kbps I
thought it was slightly faster (it might actually be somewhere in the
500kbps range for some reason but i'm no sure). Synching the device
won't take much longer than through USB (it seems actually slightly
faster... not sure why either) but if you decide to connect to your
computer, you'll need to wait at least a few minutes to make sure that
AS finished synchronizing before turning the iPAQ off or you might end
up with conflicts everywhere when synching the next time.
Also to initiate transfer you'll need to click on the iPAQ BT icon and
select Start ActiveSync. Once this is done you should be ready to go
online.
As far as connection distances it depends on the conditions. First if
you are already connected to the desktop you will be able to reach much
greater distances. I would say that the 100m rating is about accurate
in open space. In a building environment I was able to connect up to
about 25-30m which is still plenty (you can always add redundant BT
adapter, or even an access point). Now connecting back to the desktop
from the iPAQ was a little more delicate. I'd say that unless you're
within 15m (in a building) from the BT adapter the iPAQ won't be able
to initiate a connection.
Well I hope this little tutorial will help you and not discourage you
to try BT. Sure the process of setting up the devices is a pain but
once everything works fine it's a pleasure to use. As a note, I'm the
one that ended up spending about 10 hours trying to figure out how to
connect the devices (and try to find anything about that online, there
is nothing). One thing you should start up with is to read the user's
manual (one of the PDF file on the install CD); I omitted this step
and it did cost me several hours trying to get it to work. I noticed
that the manufacturer recommends to delete the Partnership before synchronizing
with the desktop but I found that this step can be avoided if you uncheck
the USB option. Once in awhile you'll also need to reboot the desktop
to restart the services (for some reasons) especially if you change
any of the settings (or sometimes just open the setup window) but you
should first try to turn the Radio off and then back on on the iPAQ.
Finally, I wish that MSFT did provide native support for BT devices.
The process was so long simply because WinXP doesn't offer full support
for the USB BT adapter.
Now it's up to you to see whether or not you are willing to spend the
extra $$ and security risk and get 802.11b or use a BT WAN/PAN. I should
say that BT isn't WAN oriented but so far has done a fairly decent job,
especially with minimal hardware.
Discuss
this article here.
More resources here:
Bluetooth specification page: http://www.palowireless.com/infotooth/knowbase/general/9.asp
Bluetooth SIG: http://www.bluetooth.org/
ZDNet UK Bluetooth News: http://news.zdnet.co.uk/0,,t294,00.html
Info
Want
to know more about us?
Or get in touch with us?
Click here!
