Hi-tech setups - what are you rocking?

[beldritch]

I first bought a cardboard, then a plastic one and then a Quest. Buy cheap, you buy thrice

For fitness, I think the Quest has got the edge on any other tech. Games like Pistol Whip can easily have you feeling like you've ran a marathon. Even slower paced games can have me aching the next day. I would highly recommend them and my wife loves it.

So what I'm saying is: it's easy to justify their purchase just so you can put them to more twisted use.

[Kinbaku]

I first bought a cardboard, then a plastic one and then a Quest. Buy cheap, you buy thrice

For fitness, I think the Quest has got the edge on any other tech. Games like Pistol Whip can easily have you feeling like you've ran a marathon. Even slower paced games can have me aching the next day. I would highly recommend them and my wife loves it.

So what I'm saying is: it's easy to justify their purchase just so you can put them to more twisted use.

I bought a cardboard first and then the plastic one with the magnet.
So the Quest is in the store waiting for me to buy it.

[Gregovic]

Very interesting and very very similar to something i've been dreaming up for a long time but never had the time or skill (so far) to build. I'm currently on vacation but after that I'll definitely be having another close look at this thread and share some of my thoughts and ideas.

[OrgasmAlley]

"Originally intended as a cock-stroker, the servos aren't strong enough, so I use it with feathers etc. to tease/caress"

RC servos are available with plenty of power for this application. Large scale helicopters and combat robotics are the arenas with the strongest models. For example (note that by all reports this servo is overrated for torque by at least 20%):

https://hobbyking.com/en_us/robostar-ab ... aZNTYtLrAc

[GeneralError]

........
My setup is split in to "modules", with each module performing a specific task. The modules are based on the Wemos/Lolin D1 Mini ESP8266 board, or (for those that need extra "grunt"/functionality) an ESP32 board.
All the modules communicate back to a central controller via MQTT, and I've written some python to control the various modules along with a node-red dashboard to visualise the current device status (this is very much a part of my kink!).
.........

Hi esranon, this is very interesting for me. The setup is very similar to the one I'm using in my Homebound system (see viewtopic.php?f=28&t=12525) with MQTT/node-red/ESP based sensors and actors. While your modules are more stimulation oriented, my modules are enforcing submission (which is my kink ). Besides the blow job and deep throat trainer and the butt plug enforcer I added a liquid feeder lately and I'm working on the integration of a dog shock collar.
Would you share some pictures of your devices and some screenshots of your NodeRed dashboard?

[esranonff]

Hey, so I took a break from all this stuff and deleted my account but have since realised that it's actually a really good way for me to relax (both the designing/building and the usage!) so I'm back!

Since I started the original thread I've moved things on quite a bit.

I've done a lot of playing around with the XToys ecosystem, but I wanted more control over what I was doing and less dependencies on a 3rd party.

One of the best and worst things about xtoys is that with a custom MQTT toy it just sends a string of messages with the speed and channel in it like this:

Code: Select all

{"speed": <INT>, "channel": <INT> }

It's then up to you to decide what to do with that information, but if you need to process it and there are many messages coming in every second as the speed rises and falls, then unless you're very careful with your code you can miss packets and the vibrators behave erratically (and not in a good way - often they just freeze at a set speed IME!)

As a result, I've gone back to putting the logic onto the micro-controller itself, however I've also switch from driving the motors via a motor driver board to using a custom PCB with a PCA9685 I²C PWM driver which gives me control of up to 16 motors from a single device.

I've not reached a need for 16 motors yet (the most I've needed so far is 6!), but the PCA9685 is designed really for driving servos, so it may allow me to pull all the various devices into one and use a state machine in the code to keep track of which motor should be doing what.

The patterns on the controller are still switched via MQTT, but now I send a message such as

Code: Select all

{"motors": [ {"speed": <INT>, "pattern_id": <INT>, "duration": <INT>}, {"speed": <INT>, "pattern_id": <INT>, "duration": <INT>}]}

and the microcontroller knows to set the motor on the appropriate pin to the speed, pattern, and duration in the JSON.

This makes it a lot easier to control without worrying about the MQTT server falling over or only half the commands being processed, removing the likelihood of the motor suddenly jumping from 10% to 90% when it should have ramped up instead!

I'm not comfortable with sharing photos at the moment, but I'd be happy to answer any questions!