| General > General Technical Chat |
| Awesome DIY Haptic Knob |
| << < (2/2) |
| Bud:
No google account required to use this ? :-// ::) |
| SiliconWizard:
--- Quote from: Bud on April 15, 2022, 06:53:00 pm ---No google account required to use this ? :-// ::) --- End quote --- Wow, good idea. Some smart IoT knob, sending user action to a remote server, then getting back the info to be displayed on it, and the actions to be taken (and of course, all of that being logged on the server for the company's delight). You could configure the whole thing on a web page connecting to your account. Brilliant! As I often say: don't give them ideas. :-DD |
| Brumby:
--- Quote from: SiliconWizard on April 15, 2022, 07:13:00 pm --- --- Quote from: Bud on April 15, 2022, 06:53:00 pm ---No google account required to use this ? :-// ::) --- End quote --- Wow, good idea. Some smart IoT knob, sending user action to a remote server, then getting back the info to be displayed on it, and the actions to be taken (and of course, all of that being logged on the server for the company's delight). You could configure the whole thing on a web page connecting to your account. Brilliant! --- End quote --- :scared: --- Quote ---As I often say: don't give them ideas. :-DD --- End quote --- ... let alone any details!! But it is a cool idea. Edit: The button, that is - NOT the IOT thing!!! |
| SiliconWizard:
Of course we were exaggerating the trait here, but the amount of features kind of suggested going a bit further. And yes, the project is cool, but I still think it's a little too much for its intended purpose (a knob!), with many more potential failure modes than a single knob/rotary encoder, which is not good. Besides, when designing projects with knobs, one is a lot more likely to implement an ad-hoc GUI rather than rely on a specific GUI on the knob itself that may not match the GUI for the rest of the product. So, I think it's like a bad good idea (or a good bad idea, if you prefer), but that's just my opinion. |
| T3sl4co1l:
Agreed, would be best with a more traditional GUI, as an input device to it. The embedded screen isn't really even needed, but helps show amount or position or range, and perhaps what the quantity is if you're not keeping an eye on the main screen. I don't think that it really fails? If you make sure that the motor doesn't get stuck on, then it's still just an encoder sans detents. As long as the GUI (on itself or elsewhere) is responsive, that's not too bad, certainly no worse than other things I've used. Tim |
| Navigation |
| Message Index |
| Previous page |