Capsense problems on CY8PROTO-063-BLE using PSoC Creator 4.2

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

cross mob
StNu_1610991
Level 4
Level 4
First comment on KBA 50 sign-ins 25 replies posted

I am migrating a project which uses capsense to the PSoC6.   Previously the 4100S was used to do touch sensing on three buttons; it worked well.  Now, nothing related to capsense works.  I have isolated the problem by using CE222827 - PSoC 6 MCU: Capsense Tuner with the capsense device using a single CSD button.

PDL 3.1.0 is being used.  I am aware of the

Beware of automatic updating your project PDL components to the latest.

posting but have not been able to resolve the problem using the suggestions.

The project compiles and the capsense tuner is connected to 063-BLE via a UART.  The data coming into the tuner is a constant 4095.  Not even any noise shows.

The single touch sensor is connected to P7.1 and there is an external 0.47pF capacitor connected to it and ground.

Any suggestions as to what I could be missing?

0 Likes
1 Solution
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

Thanks for the project.

Although I don't have the hardware, I just tried to take a look at.

[Short Report]

(1) I could not build your project

(2) By doing "Update Components" to the project, I could build the project.

[Long Report]

So to see what's going on, I duplicated your projec to "UART02_Copy_01"

And I tried to "Clean and Rebuild" the project

020-Clean-rebuild.JPG

Then I received the following dialogs

(Info) answered "OK"

021-info.JPG

Update Configuration Files

Checked all and selected "Replace"

022-udpate-confi-files.JPG

Compile failed with an Error "cy_stc_system_callback_param_t ..."

023-Error.JPG

Then I tried "Update Components..."

024-update-components.JPG

A dialog informing about unsaved documents, answered "Yes".

025-unsaved-documents.JPG

The "Component Update Tool" Dialog showed up.

There "CapSense" was included!

Selecting "Next > "

026-component-update-tool.JPG

The update targets were CapSense (and LIN_Dynamic, which I don't care now)

Selecting "Finish"

027-component-update-tool-review.JPG

To protect current project,  Workspace/Project Archiver showed up.

Selected "Archive"

028-archiver.JPG

One more dialog, answered "Yes"

029-archive-source.JPG

Summary for the archive

030-archive-summary.JPG

Then the folder containing the archive opened, but I just closed this.

031-folder.JPG

Now the components (must be) up to date.

So I selected "Clean and Rebuild"

032-clean-rebuild-again.JPG

The project was build OK, this time.

033-Rebuild-succeeded.JPG

Please try with this result, and let us know if you see any improvement.

moto

View solution in original post

0 Likes
9 Replies
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

In the CY8CPROTO-063-BLE PSoC 6 BLE Prototyping Board Guide,

There are following descriptions.

I think that P7[1] is used for LED4, so can't you try with other GPIO pins?

Such as P7[2], P10[6] .. P10[0], P5[6]..P5[2], etc.

001-CapSense.JPG

000-Pins.JPG

moto

0 Likes

Sorry, for the test, the pin number used IS P7.2 and the capacitance is 0.47 nF.  In the project we are using P7.1 also, but the red LED was removed from the board.  The third sensor is on P9.5.  The same results appear in the tuner for these other two pins so I reduced the test to just one pin.  It would be great if just that would work.

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

Since you are using CSD, 0.47nF at P7.2 is not required.

So how about trying either

(1) Try using P7.1 (without LED) or other pins stated only as GPIO?

(2) Remove 0.47nF and use P7.2.

As I don't have the same board to test, I can not test it.

but if you can attach your project (cleaned and archived) with your response

it will help others to test it with their hardware(s).

moto

0 Likes

I found that there may be an issue with the PDL version used.  For my main application project, PDL 3.1.0 is used and everything is working fine except for the capsense.

When I tried to compile the capsense example, PDL 3.1.0 produced a compile error.  When the PDL was switched back to 3.0.4 it compiled OK and started running.  But the tuner has no data except constant 4095 values.  The attached project bundle is using 3.0.4.

The project is using P7.2 and now the capacitor is removed.

I am not sure how to attache the project bundle so am using the "insert image".

Sorry, that did not work.  The file was a little over 10MB so it was not accepted.

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

> I am not sure how to attache the project bundle so am using the "insert image".

> Sorry, that did not work.  The file was a little over 10MB so it was not accepted.

Usually, I do

(1) set the target project as active project

000-Workbench.JPG

(2) right-click the active project and from the pop-up menu select "Clean <project>"

001-Clean-Project.JPG

(3) Again right-click the project and select "Archive Workspace/Project..."

002-Archive-Workspace-project.JPG

(4) A couple of dialog windows will appear

The first one to specify the destination and the size

Please select "Minimal" to make the package small.

003-dialog-1.JPG

Then archive result summary will be shown, select [OK]

004-dialog-2.JPG

(5) The folder containing the archive will be opened, you need to attach the ".zip" file.

005-Archived.JPG

(6) Now to attach, at your response window, at first we do not have "attache" button.

So please select "use advanced editor" in the right - top corner.

006-reply-1.JPG

(7) Then "attach" appears at the right-bottom corner.

Please use this to attach your ".zip" file.

007-attach.JPG

moto

0 Likes
lock attach
Attachments are accessible only for community members.

Thanks for the detail.  The only part I was missing was the use of the advanced editor.  Attached is the file.

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

Thanks for the project.

Although I don't have the hardware, I just tried to take a look at.

[Short Report]

(1) I could not build your project

(2) By doing "Update Components" to the project, I could build the project.

[Long Report]

So to see what's going on, I duplicated your projec to "UART02_Copy_01"

And I tried to "Clean and Rebuild" the project

020-Clean-rebuild.JPG

Then I received the following dialogs

(Info) answered "OK"

021-info.JPG

Update Configuration Files

Checked all and selected "Replace"

022-udpate-confi-files.JPG

Compile failed with an Error "cy_stc_system_callback_param_t ..."

023-Error.JPG

Then I tried "Update Components..."

024-update-components.JPG

A dialog informing about unsaved documents, answered "Yes".

025-unsaved-documents.JPG

The "Component Update Tool" Dialog showed up.

There "CapSense" was included!

Selecting "Next > "

026-component-update-tool.JPG

The update targets were CapSense (and LIN_Dynamic, which I don't care now)

Selecting "Finish"

027-component-update-tool-review.JPG

To protect current project,  Workspace/Project Archiver showed up.

Selected "Archive"

028-archiver.JPG

One more dialog, answered "Yes"

029-archive-source.JPG

Summary for the archive

030-archive-summary.JPG

Then the folder containing the archive opened, but I just closed this.

031-folder.JPG

Now the components (must be) up to date.

So I selected "Clean and Rebuild"

032-clean-rebuild-again.JPG

The project was build OK, this time.

033-Rebuild-succeeded.JPG

Please try with this result, and let us know if you see any improvement.

moto

0 Likes
Hari
Moderator
Moderator
Moderator
750 replies posted 500 replies posted 250 solutions authored

Hi StNu_1610991

As MoTa_728816​ suggested, please update the component to the latest version (V3.0) to ensure compatibility with latest PDL. Apart from that a few suggestions regarding CapSense:

1. Please set the modulator clock frequency to the max possible (48MHz) (CapSense configurator > Advanced > CSD Settings > Modulator clock frequency). This will ensure faster scan time and will allow you to set higher sense clock speed.

2. Set the sense clock frequency to a higher value (CapSense configurator > Advanced > widget details > Sense clock frequency). The idea is to set the sense clock frequency to the maximum possible that charges and discharges the sensors completely. Setting a low value would mean the IDAC is also set to a low value and the error in IDAC might cause this issue. You can set the highest frequency and check if the sensors are charged and discharged in an oscilloscope (you will see square waves). If the sensors are being charged and discharged, you can keep it, else you can reduce the frequency.

Additionally, please make sure that a 2.2 NF capacitor is placed in pin 7.7 for Cmod. This is essential for CapSense operation.

You can also check the sensor lines with an oscilloscope to make sure that CapSense scan is happening (you will see square waves in those lines).

Thanks,

Hari

Thank you for the reply.  The problem was that the capsense component had not bee updated to the right version.  After upgrading it sensor data did come in properly.  I added the two other buttons on P7.1 and P9.5 as needed for the project; they were also being sensed properly.

Thanks for your help.