Looking for a hardware guru for wireless haptic feedback project (Max/MSP)

Reposting this from the cycling74.com(Max) forum as I got no bites there.

I’m looking for someone who can help me source (and potentially program if it’s an embedded solution) a simple/compact wireless haptic feedback system for use with Max (via OSC).

I want to use the haptic feedback with my dfscore system (http://www.rodrigoconstanzo.com/dfscore), so it needs they would need to be in sync, and with as little latency as possible.

The idea is to have/use between 2-6 of them at a time, so the hardware needs to be on the cheap side of things, and should also be compact and wearable (like embedded in a sweatband around an ankle or wrist).

Each unit only needs 1 (or maybe 2, if there’s an LED involved) digital outs. No analog/digital input needed at all. This is purely for haptic feedback (though having an LED light up with the haptic feedback might also be useful).

Wifi/mesh is ideal as it wouldn’t require a ‘dongle’, but having a receiver dongle is ok too.

I’m thinking a motor like this: https://www.sparkfun.com/products/8449

Which is what’s used in Imogen’s glove project: http://mimugloves.com

I’ve looked at a couple of the cloud/wifi arduino-ish boards out there, like Spark (https://www.particle.io/?redirected=true) and a few others and other than being kind of expensive (though not unmanageable), they seem complicated to setup (for this purpose) and probably laggy, since it goes through a dedicated API.

I have several XBees and found some cool guides on using the built in digital out pins to drive an LED (http://examples.digi.com/lights-motors-more/802-15-4-digital-output-with-an-led/5/) as well as cool guides like this (https://www.faludi.com/classes/sociableobjects/). They are also cheap, light, and small. So something like this is an ideal solution. When I was looking it into it, it looked more complicated to have individually addressable ones.

So if this kind of thing is up your alley, drop me an email (rodrigo dot constanzo at gmail dot com) and we can figure something out.

When I was looking it into it, it looked more complicated to have individually addressable ones.

The configuration of the XBees is a one time thing. Once each XBee has a unique, known address, communicating with any one XBee is simple.

Using the XBees, it doesn't seem like you need any Arduino(s) at all.

I'm not clear on what the motor buzzing is supposed to do with regard to haptic feedback. What I think of when I think of haptic feedback is making the controls emulate the real thing in a virtual reality simulation. Push on the control to close the hood of a virtual car, and the control should provide resistance, just like the real hood would. Simple buzzing doesn't match that definition.