currently we are developing a proximity button with the CY8CMBR3102-SX1I chip. But we have EMC problems with wired RF test (0,15-80mhz) and wireless RF test (10V/m 80-3000 mhz). All of the software filters in EZ-Click are activated and the pcb is designed as in the design guide recommended. The circular antenna has a diameter of 30mm and a ground ring around it.
Has anyone experience with emc issues and the CAPSENSE technology?
In a design with PSOC4 chip with 4 different sensors that are routed in a similar way (trying to respect as much as possible the recommendation rules), we are experiencing differences between sensors sensitivity. Trying to solve this issue, we did not reach good enough results using the tuning process that appears in the guidelines.
However, we have noticed that the default sensitivity value (normally too high by default in our case) can be reduced adding a pull up resistor closed to the sensor (between the sensor and the recommended serial resistor).
We are wondering if anybody in the community has experienced such sensititvity problems than cannot be adjusted by tuning process ? and if somebody has an electrical reason why this pull-up resistor is lowering the default sensitivity level of a sensor?
Any help on this will be appreciated.
Dear Sirs and Madams,
Please tell us about the data programmed in MBR3.
Currently, MBR3 and a host device are connected via I2C.
Is it possible to read the data in the flash area programmed in MBR3 from the host?
We would like to verify and compare the programmed data of MBR3 by the host device.
I confiemed for datasheet and TRM, but I don't think it can read the data in the flash area. Is this recognition correct?
I have a capsense sensor to sense liquid level in a tank. I have thresholds that move according to temperature which seems to work fine. I am having a problem where the capsense output gets stuck at ~49151 on some sensors.
Has anyone ever seen this before or know how to rectify it ? I am performing resets of the capsense board every 30 seconds, but I have also tried without the resets, same problem.
In the attached file, I use manual turning. But I meet two kinds of clock parameters make me feel confused.
1. "modulator clock frequency": how this parameter effect cap-sense performance ?! If I select higher clock or lower clock, what's the corresponding result ?!
2. "sense clock frequency": how this parameter effect cap-sense performance ?! If I select higher clock or lower clock, what's the corresponding result ?!
Besides, how to select the sense clock source ?! auto, direct, PRS8 and PRS12. how to select them in a proper way ?!
In fact, I know these parameters are explained in the manual but I still feel so confused. So I asked my question in here.
Hope I can get your kindly feedback.
Thank you so much.Show Less
Hi everyone! I'm using CapSense block V7.0 with PSoC Creator 4.2. Communicating via MiniProg4 (I2C-USB bridge). Problem is the connection to Tuner. I have managed to connect to Tuner, several times, but always with exactly the same .hex. Now, I have changed .hex, and now connect process fails, indicating checksum mismatch. I have downloaded the .hex via Debug->Program, and also with PSoc Programmer. Both processes have been success. But, when opening Tools->Component Tuners->connect, it fails. "Mismatch checksum for the data stored in the device and the data loaded into the Tuner (expected: 0xBD36, obtained: 0x8034)" which by the way neither is the checksum read from programmer! Any ideas?Show Less
I have a board that has 13 CAPSENSE sensor pads similar to the CY8CKIT-022 but instead of a flex PCB it is 1.6mm FR4. It is used to measure water level in a plastic tank.
I am having problems trying to detect water as the temperature of the water changes from 20C - 70C. As the water changes temperature, the raw sensor outputs fluctuate with temperature. Hotter temperatures increase the raw output, colder temperatures decrease them.
Is this normal behaviour ? In the test project, a lower limit is calibrated with no water so that any sensor that is significantly above the limit has water beside it. My question is how does this work when the temperature increases, meaning the raw count does, which puts it above the calibration point.
If the tank is full of hot water and loses it all. All of the raw sensor outputs are still significantly above the calibrated low point, even though there is no water, as the board is still hot. So it would still flag as full.
Do I have to implement a temperature curve into the lower limit. Is something wrong? should temperature affect the outputs so drastically ?
I understand how to implement a solution to get around this. I am just wondering should I have to? Or have I calibrated something wrong?
Often while using the tuner it stops working unexpectedly before acquiring all the samples, needing a reset to be able to acquire data again, besides that, it only works if it's on it's own dedicated code, not working properly if it is used alongside some other code other then a minimal one. I'm using a PSoC63. Any tips on what may be going wrong?Show Less
I'm developing a function to capsense one button in CSD, CSX method at regular intervals.
However, It is unreliable because the value measured in this way is different from the value measured by CSD and CSX respectively with two buttons.
Any examples related to this?
If so, I'd appreciate it if you could let me know.
(I'm using PSOC4 and CY8CKIT-145)
I'm sorry. please understand my lacking in English.
Thank you.Show Less