This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652R: Sensor Controller button count

Part Number: CC2652R

HI,

I need to know how many capacitive buttons I can have in my application when using the Sensor controller? Would 4 buttons be ok ? The documentation points out that 2 is maximum, please correct/confirm.

Ho well will buttons based on sensor controller architecture fit in a harsh industrial environment? Is it worth proceeding with Sensor controller based design or should I move to Captivate based design ? 

The circumstances where the buttons (plastic surface) has to work are the following:

- Risk for water drops on the button

- Noisy environment (electric field from motors, inverters)

- Operation with glowes would be nice

Please comment

  • Kenka,

    I suppose you have are using the Capacitive Touch example in Sensor Controller Studio as reference. This example can have as many capacitive buttons as there are analog pins available. There are 8 analog pins available on the CC2652R, and if none of these pins are allocated by the main application then you could have up to 8 capacitive buttons with the Capacitive Touch example.

    If you need more than 8 capbuttons then it is possible to do create a capacitive button matrix out of the analog pins to get more buttons. We don't, however, provide any examples of this though, but it is possible.

    Regarding Capacitive Touch w/Sensor Controller vs Captivate based design, it depends on your requirements. I will loop in an another expert to comment based on the circumstances you listed.

  • Note that the number of possible buttons is 7 if external reference is used, 8 with internal.

    The cap touch solution we have suggested using Sensor Controller is primary for the consumer market where cost is very important and where few buttons are needed. We have seen when we have tested in the office that high noise could cause issues. It could be that it's still possible but the customer has to use time to alter and test the cap sense code that we use in the example.

    What they can do is to get a BOOSTXL-ULPSENSE and just do some tests with this in the environment they want to use it. If they see that they have issues then I would suggest go for Captivate. 

  • Thanks

    Great stuff