Requirements for a dildonics protocol
Posted: Tue May 12, 2009 10:08 pm
I'm thinking about the requirements for a protocol between the PC and a dildonics controller, as I would like to design one. We need this protocol (and of course a free reference implementation) at an early stage, so we can easily integrate experimental input- and output-devices with software for controlling outputs and analyzing input data.
So I am calling on you, as your ideas could provide valuable input to this process.
IMHO, these requrements are needed:
- The protocol has to be simple. Looking at past attempts to protocols at IETF, the simple protocols tend to win.
- We have to realize that the external (to the PC) dildonics controller has limited capabilities. Because of this we should limit the work the dildonics controller has to do.
- We need to make it possible for the PC to control various outputs, like vibrators.
- We need to make it possible for the PC to get readings on various inputs, like penile plethysmographs, rectal pressure sensors and other input devices. For these devices we often need a high sample rate, as postprocessing this data on the PC is key to the optimal use of this data.
So I am thinking about (and half way implementing) a simple protocol with these properties:
- It is a simple command-response protocol, except for asynchronous messages from device inputs.
- Inputs can buffer readings on the controller and send these asynchronous to the PC.
My idea is to design the protocol and a reference implementation on a PC and an Arduino, so we have a framework we can use for future development. With this framework, and the right PC-side analysis software, new inputs like seraph0x's penile plethysmograph and my rectal pressure sensor can easily be integrated into any software someone writes for this framework for analysis and/or feedback to outputs for arousal and orgasm control. Any software I write for this will be free software.
But I would really like some input from you, as I know many of you have thoughts about this. Even if you have not thought about this, please spend a few minutes thinking about it, and let us know your thoughts. We can easily filter out bad ideas, but I am certain that some of you have some really good ideas that I have not thought about.
So I am calling on you, as your ideas could provide valuable input to this process.
IMHO, these requrements are needed:
- The protocol has to be simple. Looking at past attempts to protocols at IETF, the simple protocols tend to win.
- We have to realize that the external (to the PC) dildonics controller has limited capabilities. Because of this we should limit the work the dildonics controller has to do.
- We need to make it possible for the PC to control various outputs, like vibrators.
- We need to make it possible for the PC to get readings on various inputs, like penile plethysmographs, rectal pressure sensors and other input devices. For these devices we often need a high sample rate, as postprocessing this data on the PC is key to the optimal use of this data.
So I am thinking about (and half way implementing) a simple protocol with these properties:
- It is a simple command-response protocol, except for asynchronous messages from device inputs.
- Inputs can buffer readings on the controller and send these asynchronous to the PC.
My idea is to design the protocol and a reference implementation on a PC and an Arduino, so we have a framework we can use for future development. With this framework, and the right PC-side analysis software, new inputs like seraph0x's penile plethysmograph and my rectal pressure sensor can easily be integrated into any software someone writes for this framework for analysis and/or feedback to outputs for arousal and orgasm control. Any software I write for this will be free software.
But I would really like some input from you, as I know many of you have thoughts about this. Even if you have not thought about this, please spend a few minutes thinking about it, and let us know your thoughts. We can easily filter out bad ideas, but I am certain that some of you have some really good ideas that I have not thought about.