Announcements

Equip yourself to optimize PSoc4 MCUs for Evs at the EV Webinar. Click here to register.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

PSoC™ 4 Forum Discussions

user_284076
Level 3
Level 3
10 replies posted 10 likes given 5 replies posted

At random time very rare false proximity as well  as  button start detecting. Is there any suggestion regarding software point of view.

Kindly find attached code.

We can not do hardware changes as the production of board is done but suggestions are welcome for future. 

0 Likes
1 Solution
BragadeeshV
Moderator
Moderator
Moderator
First question asked 1000 replies posted 750 replies posted

Hi user_284076​,

Please upgrade your CapSense component to the latest version CapSense v6.0. There is a lot of issues we have seen with the component you are using. We recommend using the latest version of CapSense for all the new designs.

There are could be many reasons why you might face this issue:

1. External noise

-> Check if you have 560 ohms series resistors in place.

-> Make sure you have a stable supply voltage. Also make sure you have used all the decoupling capacitors placed as recommended.

2. Layout guidelines not followed such as improper grounding:

Please check your layout and schematic files against the Cypress recommendations mentioned in the PSoC 4 CapSense design guide. Don't forget to see the CapSense schematic and layout checklist provided in that document.

3. Sometimes you might have issues when you are using sleep modes. If you are able to identify that this issue happens whenever you device comes out of sleep, you can try rejecting the first few scans that might contain wrong data.

4. When this issue happens check if your raw counts are getting stuck at any value. The best way to avoid this situation is to use the sensor auto reset feature that will make the baseline track the raw counts after a pre-determined time.

5. Check if you see raw counts saturating due to environmental changes, you may have to re-calibrate the widgets to a lesser value.

6. I see that you are using SmartSense algorithm in your project. Can you try switching to manual tuning and check the performance again.

7. The issue can also be due to over sensitivity. Try reducing the sensitivity and check the performance again.

Regards,

Bragadeesh

Regards,
Bragadeesh

View solution in original post

3 Replies
BragadeeshV
Moderator
Moderator
Moderator
First question asked 1000 replies posted 750 replies posted

Hi user_284076​,

Please upgrade your CapSense component to the latest version CapSense v6.0. There is a lot of issues we have seen with the component you are using. We recommend using the latest version of CapSense for all the new designs.

There are could be many reasons why you might face this issue:

1. External noise

-> Check if you have 560 ohms series resistors in place.

-> Make sure you have a stable supply voltage. Also make sure you have used all the decoupling capacitors placed as recommended.

2. Layout guidelines not followed such as improper grounding:

Please check your layout and schematic files against the Cypress recommendations mentioned in the PSoC 4 CapSense design guide. Don't forget to see the CapSense schematic and layout checklist provided in that document.

3. Sometimes you might have issues when you are using sleep modes. If you are able to identify that this issue happens whenever you device comes out of sleep, you can try rejecting the first few scans that might contain wrong data.

4. When this issue happens check if your raw counts are getting stuck at any value. The best way to avoid this situation is to use the sensor auto reset feature that will make the baseline track the raw counts after a pre-determined time.

5. Check if you see raw counts saturating due to environmental changes, you may have to re-calibrate the widgets to a lesser value.

6. I see that you are using SmartSense algorithm in your project. Can you try switching to manual tuning and check the performance again.

7. The issue can also be due to over sensitivity. Try reducing the sensitivity and check the performance again.

Regards,

Bragadeesh

Regards,
Bragadeesh

Thanks for input.

you mean CapSense v5.0 not CapSense v6.0?

0 Likes

CapSense v6.0 is the latest CapSense component version

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes