Prev: design issue - embedded webserver application
Next: spartan 3E ethernet PHY help..
From: KyBoiler on 23 Mar 2010 18:08
So for my capstone project I've decided on a myoelectric controlled (think
robotic prosthetics) wireless computer mouse. From my little reading so
far, I can avoid the pc side of the bluetooth stack entirely by conforming
to the Human Interface Device profile on the device side. The way I read
it, it should be basically connect and play, no drivers needed.

I have some decent info on the analog side of picking up muscle
contractions, but other than the Bluetooth HID spec, not much info on the
communication.

I'm looking for advice on a uC to bluetooth connection (or uC with
bluetooth on board?) and it would be great to see some kind of pseudocode
layout of what the Bluetooth HID is looking for from the hardware side.

I'm familiar with AVRs but willing to learn PIC, ARM, etc. if they are
significantly better suited to the task.

I just discovered BlueGiga Modules... looks very promising for ~$26. Self
contained HID stack, uart to uC, and radio in one surface mount part (not
ball grid). Anyone have any experience with these?

In the BlueGiga datasheet it states to line the outside of the pcb with
vias every 0.3" I've never done an RF board... is that typical?

Thanks!

tl:dr
Any comments on BlueGiga modules and the HID profile? Different
suggestion?



---------------------------------------
Posted through http://www.EmbeddedRelated.com
 | 
Pages: 1
Prev: design issue - embedded webserver application
Next: spartan 3E ethernet PHY help..