Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use library without touch sensitive motor faders #13

Open
FabiB98 opened this issue Nov 21, 2022 · 2 comments
Open

Use library without touch sensitive motor faders #13

FabiB98 opened this issue Nov 21, 2022 · 2 comments

Comments

@FabiB98
Copy link

FabiB98 commented Nov 21, 2022

Hi,
first of all: It is a fantastic library and I am very happy that I found it.
One question regarding the library: Is it possible to use this library without touch sensitive motor faders?
My existing ALPS faders do not have such an "Touch" pin.

Do you have any tipps for me how to proceed? Or would you suggest that I should buy new faders.
(However, I have already 16 faders, therefor I do not really like to throw them away....)

Thanks in advance!
Best regards
Fabian

@tttapa
Copy link
Owner

tttapa commented Nov 21, 2022

If you use the latest version, you can set the touch_masks configuration option to all zeros:

static constexpr uint8_t touch_masks[] = {1 << PB0, 1 << PB1, 1 << PB2,

However, that's not enough: if the Arduino doesn't know that you're touching it, how does it know when to turn of the motor? In its current form, the software will just work against you when you try to move it, which kind of defeats the purpose.

You could add some logic to enable the controllers only when the reference changes, with some kind of lock-out system, and then detect when the user stops moving the fader by looking at the analog input.

@FabiB98
Copy link
Author

FabiB98 commented Nov 22, 2022

You could add some logic to enable the controllers only when the reference changes, with some kind of lock-out system, and then detect when the user stops moving the fader by looking at the analog input.

Hi, thanks a lot for your reply!
I see the problem. I thought that there is an easy way to set the program to the above explained behavior.
I had a look to the code and I think that the re-programming expense is quite high.

Maybe I will shift around by introducing an additional push button for every fader. Using a D-FLIPFLOP I will produce a switch behaviour. If I set the Touch pin to VCC I can change the fader position by hand. After that I press the button again and then the PIN will set to LOW --> Motor fader is controlled by command.

Does this make sense for you?
Thanks a lot for your efforts!
Best regards
Fabian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants