An automated orgasm denial and enhancement device for the DIY community
What will surprise you most is how accurate it is that you only have a few moments left. In this day and age algorithms are a respected part of our lives...this one knows you better than yourself.
Have you ever cut-off a sneeze before it happened and found it a conflicting blend of sensations? Have you ever stopped going before your orgasm so you could last a bit longer? If you're not afraid to use a buttplug and you're ready for an amazing experience this is for you.
It is not a sex-toy in the traditional sense because it doesn't provide pleasure unless you add in a vibrator or connect it wirelessly to other toys. They provide the pleasure, EOM tells them when to stop and when they can start again.
Using an inflatable butt plug to detect pressure changes indicative of pelvic floor contractions, this software, and associated hardware, is used to detect when the user is approaching orgasm and control stimulation accordingly. The net result: automated edging and orgasm denial or enhancement.
Having to wait for it while being right at the edge makes it more intense! Trying to resist getting close is a turn-on for some. When you're ready to end the edging you can use "Control: Orgasm" to allow you to finish after a chosen number of minutes or near-orgasms... if you've had enough simply set it to "Control: Manual" and take care of things manually. It can also be used after orgasms to determine exactly when the refractory period has subsided enough to begin the next round of pleasuring.
The UI is posted at https://rubberyfun.github.io/endless-orgasm-machine/eomui/public and can be installed on your Android or PC as a PWA app for offline use.
This is what the app view looks like:
(the purple icon switches between chart mode and realtime mode)
For legacy purposes the UI is also on the ESP32 itself and can be found by visiting the /ui endpoint at the IP address of your device. You can watch the serial output to determine the IP. Due to space limitations the embedded version can't connect to other toys. It's basically for monitoring the websocket output.
Example: If you join the EOM WiFi access point the IP will be: 192.168.4.1 you should visit http://192.168.4.1/ui It will automatically open a connection to the websocket endpoint at http://192.168.4.1/.
Well, I'll get a store together eventually but for now you'll have to build it yourself. These instructions are meant to make the simplest build possible so you can get playing.
STLs for the wrapped tubing version are in the /hardware directory.
Also included are the source files for customizing your own plug. They are designed in OpenSCAD, which may not be the easiest cad program to work with but its completely open-source and easily sharable for customization.
If you go with an inflatable plug you're on your own...There are not yet any files for enclosing the electronics and securing them...there are a million different products you could buy anyways so nothing could be made to fit. If there is demand I'll post a simple box.
- Install VSCode with the PlatformIO extension
- Open this repo and let all the PlatformIO dependencies download
- If you want to use websockets alongside or instead of bluetooth set "wifi_on" to true and configure your wifi ssid and password at the top of data/config.json or skip this step to let it broadcast its own access point:
EOM. You can have it both ways: Set it up to connect to your home wifi but if you're away EOM will go into access point mode after it fails to find it. - figure out the board you're using. For a Xiao Seeed Esp32-S3 choose '''esp32-s3-devkitm-1'''. For Waveshare Esp32-S3 choose
waveshare_esp32_s3_zero. For a generic ESP32 like Wroom chooseesp32dev - Under
PlatformIO -> Project Tasks -> <your board> -> PlatformchooseBuild Filesystem ImagethenUpload Filesystem Image - Under
PlatformIO -> Project Tasks -> <your board> -> GeneralchooseBuildthen eventuallyUpload and Monitor - Watch for your device's IP address to be displayed in the monitor window (In access point mode it is 192.168.4.1)
WiFi is NOT necessary anymore! The UI can work through bluetooth now! No ip address, wifi setup, or anything else needed. Just connect to your EOM directly by clicking the bluetooth icon. Android or PC Chrome only! Sorry Apple and Firefox enthusiasts but those two have deemed web bluetooth an unacceptable risk and it will never be available.
So how do you get that running? It is now configured as a PWA! This means you can pull it up once from https://rubberyfun.github.io/endless-orgasm-machine/eomui/public and install it as an app. It does not require an internet connection to work after installation...its just there in app mode ready to go. I'll probably end up splitting the UI into an embedded version and an app version.
Using Xtoys you can connect to the EOM and let it control your other Xtoys devices. For Xtoys it emulates a device called MonsterPub Mr. Devil Kegel. Connect to the device called "Libotoy". The "pressure" reading corresponds to the "pleasure" output of the EOM. The sliders for vibrator strength will work in manual mode.
Why Mr Devil? Because it's one of the few bluetooth devices in Xtoys that has 2 way communication and high resolution (16 bit). If you wish to connect Xtoys to the EOM over wifi you can choose the Edge-o-matic 3000 and it is backwards compatible. This is less useful because Xtoys only chose to implement "arousal" and "pressure" inputs, so all the logic that goes into calculating the amount of pleasure is ignored.
| ID | Name | Description |
|---|---|---|
| 1 | Ramp-Stop | Pleasure ramps up, stopping abruptly on arousal threshold crossing. It's very frustrating. |
| 2 | Depletion (default) | Pleasure ramps up, but is reduced for even small arousal spikes. This makes for a constant interaction with your arousal rather than just a sudden cutoff when it's over the limit |
| 3 | Enhancement | This is the opposite of edging, it will make you orgasm faster. Pleasure ramps up as arousal increases, holding a peak for ramp_time. Not compatible with Orgasm mode. |
Websockets are supported for backwards compatibility with nogasm and edge-o-matic devices, but not necessary for the current bluetooth implementation. Documentation for the WebSocket API can be found in doc/WebSocket.md.
You can test this out on almost any ESP32 device without any extra hardware by touching the pin assigned to the pressure sensor. Run your finger over all the pins if you're not sure which one it is. This will be like a pressure sensor being squeezed. To actually play with this device you will need to attach an actual pressure sensor and butt-plug (or 3d-printed tubing version). The MPX5100DP is the sensor it was designed around but anything capable of 15psi or greater should work whether analog or SPI. Plug the port of the pressure sensor into the air hose for the butt plug.
To get it to resemble the original Nogasm device you can then add a 12v power supply and charger, a simple transistor or more protected motor controller, a flyback diode, and vibrator motor. You could share that power supply to the esp32 through a buck converter to make the whole thing wireless. That's it. You can set this all up to attach to the buttplug rather than having a wires and tubes leading to a control box, but its a matter of opinion which way is better.
Tested boards: ESP32DEV, ESP32-WROOM32, ESP32-C6 (WaveShare), ESP32-S3 (Seeed and Waveshare)
- You can use Xtoys.app as a control panel to ramp up any number of vibrators, strokers, or e-stim units in sync with the EOM over bluetooth. See this Xtoys layout for an example
- If you want to connect Xtoys via wifi you will need to enable SSL in
data/config.jsonand use the edge-o-matic Xtoys device. The bluetooth connection is more useful since it sends pleasure level rather than arousal but there are some existing xtoys scripts that work with the edge-o-matic arousal level. - You can use an inexpensive Vibrating inflatable buttplug and remove its control box to wire it directly to the EOM with a power circuit. A non-vibrating plug is even less expensive if you'll be controlling your pleasure wirelessly.
- If an MPXV5100GP pressure sensor is too inconvenient or expensive to source you could use an easy to find generic car exhaust pressure sensor since they are almost all analog 15psi 5v sensors. The pin with the notch is Vin, middle is ground, third is Vout. Everything tested was 3V compatible.
- If you use an ESP32 board with an integrated screen (Example 1, Example 2) you can enable the screen in include/config.h to see the IP of the device.
- As an alternative to a vibrating buttplug you can use a plug made for enema play and pass a wire through the middle to an e-stim electrode or to a vibrator on top.
- Someone posted a build that used tubing wrapped around a 3d printed shaft that also housed the electronics. It was a neat new twist to the inflatable plug since the tubing reacted to pressure just like an inflatable. The link is lost to time but it was on github somewhere.
- You could put in a higher range pressure sensor if you prefer to inflate the plug to more intense levels. The measurement is of change in pressure, not overall pressure.
- You could order a prebuilt PCB like is used for the Nogasm-esp32
- There really are a ridiculous number of implementations of the nogasm concept from the last decade...you should do some nogasm googling.
This is a fork of that project with a different set of goals. The main goal is to make the project accessible to the maker community by keeping the hardware and software simple and DIY friendly - like the original Nogasm that started it all was. The Edge-o-Matic code is designed around selling well-made but proprietary hardware and is locked into it through closed-source code, crippling attempts to use it with DIY hardware. It also included a lot of code to connect to related products and services.
This project was first vastly simplified then expanded with compatibility in mind. You can try it using almost any modern ESP32 device with no additional customization. You will need to connect a pressure sensor and inflatable buttplug to make it functional, but that's it. It's meant to be operated wirelessly rather than through the additional hardware of a screen, knob, LEDs, network jack, etc.
Some notable differences are:
- Runs on nearly any ESP32 board! DIY friendly
- Connects through bluetooth low energy
- Orgasm mode available over UI! (denies orgasms until timer runs out)
- Maximum denial count, so you get to finish after X number of edges
- UI hosted as PWA or on device... and is phone friendly
- defaults to endless orgasm denial in ramp-stop mode
- smaller build size, fits in your butt
- SD card requirement removed
- menu system removed
- console system removed
- action manager system removed
- hardwire networked device support removed
- edge times are in seconds
This is a product of the open source community. This will always be open source. Sharing knowledge this way goes back to patent offices, or perhaps cave-man fire. Sometimes the term can be abused by making things appear open when key information is obfuscated or by taking formerly open repositories offline...that practice of monetizing is also as old as time. No shame. Open-source doesn't mean no profiting and I'll try to make some money too. However this particular project intends to focus on information sharing and DIY accessibility as much as functionality. You should be always be able to build this yourself if you have the free time. That may not be the most profitable route but I hope the open-source community can elevate this project and make it even more useful than I am capable of.
- Rhobot with the original nogasm project that started it all
- TheElims Gave feedback and works on a similar device with much more slick hardware -
- Skier23 who curates a repository and discord with all information regarding the topic.
- Buttplug.io by Qdot - Powers the connections from the EOM app to other bluetooth toys. Him and his discord team are very helpful if irritable.
- Rudolf, who came up with the coiled silicone tube as sensor element and even has written a scientific paper on that topic.
- Maus-Tec who manufactures and sells the Edge-O-Matic
- Onwrikbaar with his bullfrog, who refined the simple nogasm algorithm with a peak summation and decay function.
- night-howler who contributed a breadboard friendly version of the nogasm called protogasm.
- connect to OSSM and DG Labs Coyote
- add build walkthrough to docs and more examples, pinouts and schematics
- audio buzzer for cooldown!
- add a config save button so setting changes aren't immediately permanent (save toy settings separately?)
- do canvas drawing to offscreen element for efficiency
- integrate smoothing filters into pressure readings
- ui and websockets using same endpoint if possible
- bug: arousal overflows on hardware side
- logging from the app
- add X axis on chart (seconds)
- chart glitch on left side at startup
- make motor pin selection more intuitive
- Put some effort into UI styling
- display toy battery level
- bluetooth OTA
- device disconnection
- disable internal motor control option?
- integrated screen support / ip display
- Implement patterns? That's a biggie
- Running average math seems off