Hmm…maybe I just didn’t see how to do the setup, but I hooked it up to an ossm on the prostate side through intiface and it didn’t move position. (I was using the test slider, so maybe the issue is there?)
I think vibrators they just get set to a static percentage right? The ossm would have to be set to some sort of oscillating pattern between a min and max range
Unless there is a setup difference I need to use on the intiface side? Maybe I need to set that to oscillate? I can do more testing on my side, unless you have suggestions you can already think of.
OSSM & Reciprocating Machine Support: Added dedicated handling for linear sex machines and DIY strokers (such as the OSSM) connecting through Intiface Central. The engine now detects and formats commands for LinearCmd (position and duration vectors) as well as ScalarCmd with ActuatorType: "Oscillate", ensuring reciprocating hardware moves instead of dropping invalid vibration packets.
Per-Axis Role Mapping: Replaced rigid device-level tagging with granular, per-actuator mapping in the Intiface configuration modal. Each detected axis on multi-axis hardware (OSR2, SR6, multi-motor toys, or thrusting rigs) can be independently assigned to Primary (Tease) or Secondary (Milker).
Individual Axis Testing: Every detected actuator now includes a real-time capability badge (Linear, Oscillate, Vibrate, Rotate) and an independent test button to verify physical actuation and directional response before starting a session.
Rotational Toy Support & Edge Inversion: Integrated RotateCmd and scalar rotation for rotary toys (such as the Vorze A10 Cyclone). Rotational velocity scales inversely with heart rate, and the spin direction automatically reverses upon hitting an edge cutoff to disrupt sensory accommodation.
Modes & Interface Refinements
Restored “Head Play” Experience Mode: Re-integrated the glans-targeting profile, which automatically shifts stroke boundaries upward to isolate the top 25% of physical travel as heart rate approaches your climax threshold.
Canonical Vector Favicon: Restored the physical /icon.svg asset link across browser tabs, PWA manifests, and mobile bookmarks.
Experimental Notice & Community Feedback
Important: Protocol support for linear reciprocating sex machines (OSSM), multi-axis strokers, and rotational hardware is currently experimental. Because firmware builds, stepper motor drivers, and Intiface device definitions vary significantly across DIY and commercial setups, active user feedback is needed to refine motion smoothness, step durations, and boundary limits. Please share test results, behavior notes, or bug reports via this thread or directly to support@edgeloop.app.
This is sooo cool, I thought you needed like, an inflatable pressure sensor up your butt to do this sorta stuff. Now I kinda want a heart rate monitor to test it out …
Its been fun to develop for sure! i know you can get basic BLE Bluetooth Heart Rate Monitors on Amazon for like 30-50 bucks, but i use my smartwatch (Pixel Watch 2) If you get a chance to try it out let me know what you think!
Will do! I assume theres a bit of a learning curve, since I got no clue where to put the cutoff point to. no clue how my heartrate looks during it. But I guess I’ll find out soon!
@Jalex i’m working on some defaults, and playing with power levels and such, but it just takes time. i’ve found for me the happy spot to be around 150 and it does a great job of holding me there and not letting me tip over the edge.
but somewhere in these updates it kinda depowered itself so i’m trying to fix that now.
@Redbird When i integrated stuff for rotational devices and linear motors i went ahead and tried to grab all the devices i could think of, i specifically though about the osr2 and osr6, so try it and let me know!
did some testing with the OSSM. the oscillate test seems to be working. the position one is not. Also there doesnt seem to be a way to only enable one of them. maybe i’m misunderstanding the ui.
Lastly, i dont suppose you have instructions for the bluetooth connectivity using a galaxy watch 7 do you? it doesnt have the “Heart rate sharing” that the pixel watch has. i’ve tried a few third party apps but none work.
I tried it with the handy 2 and my galaxy watch it works well! Interface and everything is really well done, but I did encounter some issues on my side (I think its just me)
I’m not sure whether its the heart rate sensor not reading accurately or my heart rate seems to stay the same when close to climax, I had to pause plenty of times due to that, I think its just a me issue or the sensor not detecting accurately.
I think different people would have different reaction to it but im not sure, anyways its really well done and I love the concept!
For galaxy watch users, our watch doesn’t support broadcasting heart rate to BLE like pixel watch so I installed “Heart for Bluetooth” and it does work well!
Hmm…was there anything you did to get the heart for Bluetooth working? That was one of the apps I tried without success. It wouldn’t show up on the list for pairing.
Edit: did some more testing, and it seems to work on my phone but not on my desktop. no idea why.
@marshallmims if bluetooth disconnects during a session, it should stick with the previously obtained value until reconnect rather than going back down to zero.
So my Heartrate Monitor arrived today (I went for a cheapo chinese thingy called Coospo H6M) but I’m having trouble connecting it to the app.
When I click on the Heart Rate Monitor Box and press the “Scan &Pair” Button nothing happens, it doesnt show up, theres no feedback to what could be the issue at all.
And now I’m wondering whether the thingy I bought might not support it. For the record, it connects fine to my pc directly just the button doesnt seem to work
I’m on Linux using the Firedragon Browser, but I tried chrome as well with the same result
@Jalex try chromium and you’ll have to enable an experimental flag to enable Bluetooth in Linux. It’s a Linux thing. I had to do the same thing. It can’t be anything installed via a flatpak either. It has to be natively installed.
Okay finally got to try this. I like how it works. Will be playing with it more.
Had questions on the HRM part. I got it hooked up. It said I was at 67. Started it then it jumped to low 70’s. After some time it worked me closer.but my heart rate barely went into the 80’s. I thought I’d cum way before 140. So I dropped it to 100. Then was actually getting close to an edge around 90. So I dropped it to 90. Then I let it torment me for a while getting close and not edging but then speeding up as soon as the edge went away. ( So far my favorite part) But still my HR never send much above that 90 limit. So it would slow down to fast sometimes I think. Not sure. Then it was getting late so I decided to hit the forced orgasm button. At my current state. I had no choice. No control. It ran me down and drained me empty. I was able to focus enough to watch my HRM and I started cumming at 110 and continue to 115. Then took as much pot as I could take I realized it wasn’t gonna let me rest and had to hit stop.
So my question is on the numbers. Mine are way different from yours. Am I setting them correctly? I might try 95 max next time. Any help adjusting them would be appreciated. Also. I noticed when I sat up my HR went up almost 10 for about 10 seconds then back to normal.
In all. I really enjoyed the ending and the edging. The start up was kinda robotic and not arousing feeling with it just hammering away at my meat. Maybe a slow “warm up” setting would fix this. Not sure. I know for me very fast scripts from the start just make me numb up. Super slow strokes for a few minutes 5 max would probably help in my case. Idk about other guys
I love where this is going and want to see this grow. Thank you