This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cap sense using single pin per sensor

Hi,

  I'm using the nRF52840 dev kit for a BLE-based application.  I need to implement a capacitive touch button for detecting button presses and releases (no sliding).  I only have 1 analog input pin connected to my sensor.  I've looked at the nrf52-capsense-example project here, but it is based on SDK-12. 

  Is this still the recommended method to follow when only a single pin is connected to the touch sensor?

  Are there any issues using this method along with BLE (SoftDevice S140)?

  Is there any way to use the csense library in this configuration?

  Thanks...

Brian

Parents
  • Hi Einar,

      Thanks for the quick response!  

      I have looked at the capacitive sensor library in SDK16.  From what I could tell, my sensor needs to be hooked up to 2 pins to implement a capacitive sensor button.  My sensor is only connected to one pin (AIN3).  Is it possible to use the newer Capacitive Sensor library with a sensor only connected to one pin?

      Also, does the erratum 84 only apply to the nRF52832?  I'm using the nRF52840. 

    Thanks...

    Brian

  • Hi Brian,

    Brian said:
    Is it possible to use the newer Capacitive Sensor library with a sensor only connected to one pin?

    Yes, the capsense driver supports both methods. Please see this page for details.

    Brian said:
    Also, does the erratum 84 only apply to the nRF52832?  I'm using the nRF52840. 

    In practice, erratum 84 applies to all nrF52 devices. Formally, it does not, since the nRF52840 does not have this support at all if you refer to the product specification. And that is because it uses the same implementation as nRF52832, which is non-functional (as you can see from erratum 84).

    Einar

Reply
  • Hi Brian,

    Brian said:
    Is it possible to use the newer Capacitive Sensor library with a sensor only connected to one pin?

    Yes, the capsense driver supports both methods. Please see this page for details.

    Brian said:
    Also, does the erratum 84 only apply to the nRF52832?  I'm using the nRF52840. 

    In practice, erratum 84 applies to all nrF52 devices. Formally, it does not, since the nRF52840 does not have this support at all if you refer to the product specification. And that is because it uses the same implementation as nRF52832, which is non-functional (as you can see from erratum 84).

    Einar

Children
No Data
Related