Fun OSR2, 6month review - my first TCode experience

Review Device Reviews
1

Hello, just making a quick report on my good experiences from 6 months with Funosr OSR2, with caveats and shitty mods :slight_smile:
Some of these issues are likely the same in any OSR2, especially if you printed one yourself.

  • It has been very good. At first the cost seemed quite expensive. But after seeing the price vs capability of other options, the Funosr OSR2 now seems like amazing value in hindsight

  • I have had a tonne of fun making my own funscripts, messing with TCode and trying different firmwares.

  • If it breaks, I will definitely fix / replace it.

  • 1st challenge: Mounting the device. I don’t have 3d printer or access to a cheap pay-print service. For the price it would have cost me to get a plastic VESA desk clamp and ship it, I could buy several steel vesa mounts/adapters instead.

  • No matter which mounting option you choose, its gonna be a bit awkward interacting with the PC keyboard while using the OSR. The best solution for myself was to mount the OSR on a separate pole, eg tripod/shelf/stool, underneat the desk.

  • I cannot actually find international supplies for all the VESA mounts I tried, so I can’t easily recommend one. But can definitely recommend getting a VESA quick-release adapter to make setup & packup a lot easier.

  • 2nd challenge: The motor sound. I got cheapest motor option off aliexpress, and they were loud enough to make me feel uncomfortable in using the device. Sometimes I could hear the motors even with noise cancelling headphones on.

  • I invested in new motors. This nearly doubled the overall cost of my device, but… actually it was worth it. Good quality motors can be quieter / faster / stronger and likely last longer before burning out. (I have had no motor failures yet)

  • 3rd challenge: The default range of motion of the OSR2 was too big. As in, it twist too much, thrust too much, and pitch too much. Not only for my own anatomy, but also for the device itself - the fleshlight/sleeve would often hit the OSR2 chassis, my desk etc. This made me worried about causing damage to the motors, or injury XD

  • I learned how to tweak the range limits in Funosr firmware and compile it to the OSR2’s esp32. This kinda worked, but it was pretty time consuming and fiddly.

  • Later, I tried different firmwares entirely, and had great success with one by Khrull from the TempestMax discord. This firmware provided a web-gui portal that you access through your browser and can configure literally any OSR/SR6 setting you could imagine, try the settings out in realtime, and save them to .json file presets. The firmware had bugs occasionally when applying changes, but was worth it.

  • Surprisingly my favourite feature of Khrull’s firmware was the toggle for inverting the L0 / Thrust axis, which brings the OSR2 in line with The Handy and mainstream funscript use. By default, funscript ‘push’ instruction translated to ‘pull’ on OSR2.

  • I think you can get the firmware from https://www.patreon.com/Khrull , it will be called TCode ESP32 . Make sure your device actually has uses the ESP32 before you try it :slight_smile:

  • 4th challenge: It melted… i think? One day, the plastic housing of the OSR2 bent and warped, permanently physically altering the position of one motor. The motors were quite warm to the touch when this happened, but certainly felt like less than 80c. At this time, I had been writing funscripts for several hours with the OSR2 just setting next to me on the desk.

  • Luckily the electronics + motors are fine, and the overall alignment of the rods are still okay.

  • To improve cooling, I have done a very amateur ‘duct tape’ mod of my OSR2.

  • I created about a finger width distance gap between the ‘lid’ of the chassis and the chassis. Spacers from VESA mount kits hold it off the chassis, and some separate small screws do an okay job of pinning it in postion

  • A small laptop-style fan sits inside the gap. It is connected to some spare ESP32 pins. To make it fit the pins, I had to shave off some plastic from the connector. I was worried this would fry the ESP32 or interfere with singals, but it… works somehow? Maybe i got lucky! It is somewhat in place with double sided tape.

  • Lastly the chassis is also wrapped in Velcro to keep it together properly, since my screws were insufficent

  • The unit is now much more vulnerable to stray fluids, dust, etc. To help protect the internals without compromising airflow, a toilet roll was sliced open and taped across the front gap.

  • A side effect of this is that I now have less clearance/range of motion from the OSR2, especially during R2 / Pitch.

  • The motors have never felt warm since.

Overall, it has certainly been a heap of fun!
It was more work/maintenance than i expected, but it was worth it.

2 Likes