What is the best current way for accurate position control Fredorch F21S with buttplug.io?
Isn’t there way to use “Free mode” or “Program mode” directly? (Instead of usage: LinearCmd or ScalarCmd)
How LinearCmd now is implemented, does it use “Program mode” or “Free mode” now?
I’m currently using buttplugCpp project and already wrote C++ program for control Hismith, but now going to switch to Fredorch F21S which allow also control depth. I see there is some discussion closed topic in github.
But it is not clear what is the best way to perform position (as result depth also), speed and etc by API.
The main idea is to make very close complex movements which can change 2-5 times during single move in or out but for Fredorch F21S (in case of Hismith this is already working, especially on low speed movements ~1/4-2 times per second)
Unfortunately now it use “Program mode” only, looks “Free mode” is not supported, also for get required speed it use previous value of position which can be not achieved yet, also it looks if even i will send next command it will not start to do it before finish previous command and so on.
The main issue which i currently get that no one know is it possible to change device speed (range(depth)/pattern) remotely by Bluetooth protocol to concrete speed values like with wired controller (not like in programming mode where only 0-15 speed variants are possible as we know).
Also I need an ability to change speed in real time (without waiting for the previous record(s)/move(s) end like in programming mode).
I found post that xtoys.app does better control, possibly they use another Bluetooth protocol than buttplug do, can some one help with getting such info?
I think possibly there exist some other Bluetooth protocol commands which can change speed and range to concrete values in pattern mode instead of ±1, like it is possible on wired controller.
U made any progress? Its a shame that buttplug docs say they support this device fully but in the end they dont care. Feel like i wasted money because of them.
Please don’t assume I don’t care. I’m both the maintainer of IoSTIndex and the person responsible for reversing the protocol in the first place. I’m also stupidly busy with my day job and life.
I have yet to look at what xtoys has done, but right now, Buttplug only supports the F21S as a linear positional device (go to position X in time Y). The speed is a little off, and is something that’s been on my to-do list for a while. I had actually planned to improve that with the next major release, which will also allow us to support oscillation as an alternative control mode, but probably not with a customisable range to begin with.
I’m not going to be adding direct position control for any fucking machines - full length, full speed movements are going to cause accidents driven by bad maths in some client.