Re: Call for participation -- first draft
Posted: Fri Sep 30, 2011 11:02 pm
Yes, I agree that there is a fine balance to be achieved with complexity, having realistic goals, and cost. Here is where I think we agree:
* Arduino based
* Vibrator control
* SOME level of flexibility
So, there are a few things I can think of to help address this. If we are going to produce a Arduino shield or provide instructions on how to modify / build your own it should have a modular way to attach toys. I think 3.5mm audio jacks are a good choice for this. Hook up any thing you want to it. I also think it would be good to have a relay control for toys that hook up to main power. Plug in anything.
For a mains relay it would be on/off only. For the 3.5mm jacks we should offer a variety of functions controlled at the microcontroller level. For example, if we can use PWM to drive the vibrator at low, medium, high, wave, slow pulse, fast pulse, and response to analog input we can do a LOT with that. We could also try to work out some sort of switch that could be inserted in a batter pack of a traditional toy.... haven't thought that one out too much but it could be attached to the same 3.5mm plug.
On the software side here is what I am thinking. We get some community feedback to pick one tease. We convert this tease to interface with hardware. The tease will only need img tags to http://127.0.0.1:8888/?vibe=low or something similar. I will write a web server that our users will run that will serve back an image (needs to be an image to get around the cross domain issues) and send the commands over serial to the arduino.
In terms of cost, it should be the cost of an arduino ($25 or so), a toy (bullets can be had for $5), and a few basic electronics to drive the DC motor (<$20). So, I think trying to keep our price point around $50 is a good goal.
What do you think?
* Arduino based
* Vibrator control
* SOME level of flexibility
So, there are a few things I can think of to help address this. If we are going to produce a Arduino shield or provide instructions on how to modify / build your own it should have a modular way to attach toys. I think 3.5mm audio jacks are a good choice for this. Hook up any thing you want to it. I also think it would be good to have a relay control for toys that hook up to main power. Plug in anything.
For a mains relay it would be on/off only. For the 3.5mm jacks we should offer a variety of functions controlled at the microcontroller level. For example, if we can use PWM to drive the vibrator at low, medium, high, wave, slow pulse, fast pulse, and response to analog input we can do a LOT with that. We could also try to work out some sort of switch that could be inserted in a batter pack of a traditional toy.... haven't thought that one out too much but it could be attached to the same 3.5mm plug.
On the software side here is what I am thinking. We get some community feedback to pick one tease. We convert this tease to interface with hardware. The tease will only need img tags to http://127.0.0.1:8888/?vibe=low or something similar. I will write a web server that our users will run that will serve back an image (needs to be an image to get around the cross domain issues) and send the commands over serial to the arduino.
In terms of cost, it should be the cost of an arduino ($25 or so), a toy (bullets can be had for $5), and a few basic electronics to drive the DC motor (<$20). So, I think trying to keep our price point around $50 is a good goal.
What do you think?