Bluetooth & Propeller!
ProcessingData...
Posts: 208
This is a statement, not a question! 
And for relatively cheap!
On DX.com, I found two Bluetooth to Serial Modules. Cheap ($11-$8), nice looking, and with breadboard headers already on them!
One was Client only, the other Claimed to be a Client that is able to be configured as a Server!
Client: http://dx.com/p/jy-mcu-arduino-bluetooth-wireless-serial-port-module-104299
Server: http://dx.com/p/serial-bluetooth-rf-transmission-module-for-arduino-white-green-156955
The only issue? Documentation. There was none to be found in the description, and very little in the comments. After going on a web-hunt during the several week wait for shipping from Singapore, I discovered a manual for the Client module, written in broken english, but readable.
After getting the modules, I wired up the client on my breadboard. (Very simple. Actually, if you wanted to, you could plug it straight into the Demoboard header!)
I wrote a simple program to configure the module (Name, PIN, and Baud are settable on the client using AT commands), and then wrote a simple echo program to test it with.
My Android tablet had no problem sending and receiving ASCII from my propeller!
Not bad, for $8.
Next up was the Client/Server module.
It worked in generally the same way, and I quickly found documentation for it (of the same quality). But I realized that I don't really need the level of customization that it gives. Although, if you're really into setting "inquiry access mode" for your bluetooth project, you can do that.
Anyways, I thought I'd share the code with the forums, since I haven't been on here for a while.
Client Code: JY-MCU.zip
Server Code & PDFs: HC-05.zip
And for relatively cheap!
On DX.com, I found two Bluetooth to Serial Modules. Cheap ($11-$8), nice looking, and with breadboard headers already on them!
One was Client only, the other Claimed to be a Client that is able to be configured as a Server!
Client: http://dx.com/p/jy-mcu-arduino-bluetooth-wireless-serial-port-module-104299
Server: http://dx.com/p/serial-bluetooth-rf-transmission-module-for-arduino-white-green-156955
The only issue? Documentation. There was none to be found in the description, and very little in the comments. After going on a web-hunt during the several week wait for shipping from Singapore, I discovered a manual for the Client module, written in broken english, but readable.
After getting the modules, I wired up the client on my breadboard. (Very simple. Actually, if you wanted to, you could plug it straight into the Demoboard header!)
I wrote a simple program to configure the module (Name, PIN, and Baud are settable on the client using AT commands), and then wrote a simple echo program to test it with.
My Android tablet had no problem sending and receiving ASCII from my propeller!
Not bad, for $8.
Next up was the Client/Server module.
It worked in generally the same way, and I quickly found documentation for it (of the same quality). But I realized that I don't really need the level of customization that it gives. Although, if you're really into setting "inquiry access mode" for your bluetooth project, you can do that.
Anyways, I thought I'd share the code with the forums, since I haven't been on here for a while.
Client Code: JY-MCU.zip
Server Code & PDFs: HC-05.zip
Comments
See: http://wireless.fcc.gov/index.htm?job=rules_and_regulations
And for Bluetooth modules and RF exposure here: http://www.rheintech.com/docs/MultiPointOctober2005.pdf
Rick
Ultimately you're going to get what you pay for, so I'd like to recommend one of these http://www.parallax.com/Portals/0/Downloads/docs/prod/rf/30086-RN-42-Bluetooth-Module-Guide-v1.0.pdf from Parallax and Roving Networks (if it meets your requirements for the client/server mode you mentioned).
This device is FCC approved and CE certified, and guaranteed to work when you connect it to your microcontroller [especially one of ours]. Time is a relevant cost for all of us, too - spend your time on the project and not making something poorly documented do what you want it to do.
And if you have a problem with our hardware, we'll replace it anytime. We advertise some kind of 90-day warranty but the reality is that we'll take care of any problems our customers might experience if there's a remote possibility our hardware is at fault. I'm pushing for a Lifetime Warranty on all of our USA-made products (like this module) and soon I hope it to be a standard offering, not just something for the PropBOE.
I've been to factories where these low-cost Chinese products are made, too. There's a cloning problem that makes it difficult to get the same thing over and over again. Once it's Made in China, count on it being Copied in China. China may be the original Open Source Community, grabbing ahold of this new western tradition long before the last decade when it became popular to the rest of the world. Two weeks ago I was in the Shenzhen component market where I saw $9 Arduino clones - and it would've taken an experienced set of eyes with fabrication background to see the difference between the real Italian product. I think the same happens with these Bluetooth modules, ultrasonic sensors, and anything else. They're perfectly content with a 10% margin. As a result, once that product leaves the factory it's not a welcome guest for a return visit.
Once you've accepted these considerations, I admit it could still be worthwhile.
Caveat emptor!
I carry the "slave" version of that module at Propellerpowered, so I've invested a little time and energy in that end.
This page may prove to be useful with documentation and a little helper app I wrote for those.
http://propellerpowered.com/shop/?page_id=1748
Jeff