A quick query:
How much load does the CapacitiveSensor.h library generate?
I have a sketch that is is a little time critical and too many cycles taken away from the loop{} might have an effect on output.
The project is dimming lights: Mega2560 dimming 12 spots, as well as monitoring buttons and driving a 20x4 LCD display.
Regards,
LargerMon
Dimming lights, monitoring buttons, and handling a display? I don't think cap sense is going to hog up too much you can't do those things. I think maybe you way underestimate how many cycles you get. Blink your eyes. In that amount of time Arduino can execute a couple million instructions. More than enough to do what you want plus cap sense plus many many more things.
Thanks Delta_G,
I have not used capacitivesensor.h before and reading up on how it monitored and tested the capacitance of the line seemed very cycle intensive.
I will proceed with my plan to replace the buttons (5) with capacitive regions.
Cheers,
Lager
I will proceed with my plan to replace the buttons (5) with capacitive regions.
Mechanical devices will always be faster to read than capacitive sensors. Why do you want to replace mechanical devices with "touch me anywhere; I'll guess what you mean" devices?
I know mechanical switches are faster . . . . .
My question is how much overhead does the library take.
Has anyone done this before? Were there issues, slow responces .etc etc