Introducing OSR new firmware

fenderwq

RealcumberScripts Old question but I had some time with the FunSR1 now and I can say it's a very good device. The main advantage for me is that I like my favourite fleshlights a lot better then the handy sleeves. I also have a Keon but the script playback of that device is really crap compared to the handy (and even more so then the FunSR1) and I also hate the battery concept so I never use it.

Playback on the FunSR1 is really good though. Bluetooth can cause some issues depending on how far away your computer is (mine is in another room). Would have liked a stable wifi connection better. It is what it is though.

I love that multi fun player now has the ability to map the edging buttons (it's a bit clunky still (it's not really a toggle and you have to press buttons multiple times) but a huge improvement for these kind of OSR/SSR toys and imo an essential feature to have). Once you have this set up you can basically just forget about it and use it similar to a handy. I do miss the range sliders the handy has in DeoVR though.

Noise is okay, similar to handy I'd say. It can handle quite a bit of weight and has no problems with something like a fleshlight.

The device is more noticable in passthorugh then a handy though. I find the orange accent color especially distracting. Also fleshlights are just much bigger than a handy sleeve but that's not a fault of the device (it even supports handy sleeves too (both adapters are included).

Mounting was easy too, could just use the handy handsfree adapter I had lying around.

All in all pretty great device and a definite upgrade over the handy if you don't mind a little initial set up. It was delivered quickly too. It's not a traditional consumer device though (even though it's pretty plug and play) but I don't know if it really matters much for a SLR script streaming or Heresphere XBVR kind of use case.

paulsy101

The firmware itself worked well for what it is designed, to use with the Haptics Connect app. It did take a little figuring out though. I would recommend updating the uploader page to inform users that they must push a configuration from the Configurator tab after successfully applying the firmware. Also, with the Configurator, I would recommend defaulting to BLE as the Active Input, as that is what the Haptics Connect app uses to connect to the device.

Once I had the firmware flashed and I pushed the BLE configuration, I was able to get Haptics Connect to control my OSR2+ for the stroke axis and adjust the speed and range from the Manual section of the app. Unfortunately I don't have a sex toy scripts subscription (more on that later), and SLR doesn't have a demo to test scripts on their site (see this post) I was not able to test it out from SLR with an actual scripted scene.

I pushed a configuration to this firmware with Serial as the Active Input and was able to control my OSR2+ using the serial connection method on Ayva Stoker Lite . There it was able to control the stroke, roll, pitch, and twist axes successfully.

The site to update the firmware is nice, but doesn't seem to match the proper audience. It is my opinion that the vast majority of users of the OSR2, SR6, or SSR1 are going to be fairly tech savvy and not really need to have a site update the firmware for them.

Overall, the firmware is serviceable and is a good step in the right direction, and will hopefully pave the way for the future. But ultimately, I have gone back to the TCode_ESP32_Release_v0.3b firmware I was using previously for a few reasons:

Multiple "Active Inputs" from one configuration - With the v0.3b firmware, I can use serial or websocket to control my OSR2+ without having to push a new configuration depending on the connection type I want to use.
Direct web interface of the OSR2+ - With the v0.3b firmware, I can go to the IP address it is assigned and make changes directly without having to connect serially, go to the hapticsconnect.com site, and push a new config. Additionally, the Haptics Connect firmware is missing vibe and iLube configs I am considering adding, and doesn't seem to have surge and sway configs should I decide to upgrade to an SR6.
Lack of Multi-Axis scripts on SLR - A big reason I decided to build an OSR2+ is for the multi-axis capabilities. If I just wanted the stroke axis, I could have saved some money and just gotten a Handy. I'm still new to the OSR2+ and learning, but so far I've found that using MultiFunPlayer I can add patterns or randomness to the other axes if a script doesn't include them. From looking at the Haptics Connect interface, it doesn't appear that is available. So with only 1 multi-axis scene available on SLR, I cannot justify the added cost for a sex toy script subscription.

dahandy

SR6 support would be greatly appreciated! Right now I guess that SR6 must be tethered via PC via USB via MFP via ... to get it working with Quest 3. Such a hassle.

[deleted]

Could you please share your Serial adapter version? We need to know in order to reproduce what you are experiencing

dahandy

Seems like the GPIO pins are wrong for SR6. Could you provide correct values? Some of the servos are not being controlled at all. Thanks.

Correct PINs:

#define LowerLeftServo_PIN 15 // Lower Left Servo (OSR2 Left Servo)
#define UpperLeftServo_PIN 2 // Upper Left Servo
#define LowerRightServo_PIN 13 // Lower Right Servo (OSR2 Right Servo)
#define UpperRightServo_PIN 12 // Upper Right Servo
#define LeftPitchServo_PIN 4 // Left Pitch Servo (OSR2 Pitch Servo)
#define RightPitchServo_PIN 14 // Right Pitch Servo
#define TwistServo_PIN 27 // Twist Servo
#define ValveServo_PIN 25 // Valve Servo
#define TwistFeedback_PIN 26 // Twist Servo Feedback
#define Vibe0_PIN 18 // Vibration motor 1
#define Vibe1_PIN 19 // Vibration motor 2

Also, how do I enter bonding / pairing mode on the ESP32 SR6 BLE?

dahandy

Bump! No changes have been made. Could you please update the support for SR6? Thank you.

« Previous Page