TSC2013-Q1: Single Touch Configuration

Hi,

The TSC2013-Q1 can be configured to support both single-touch and multi-touch scenarios. Please reference section 8.2 of the datasheet for instructions on typical application. For a traditional single-touch resistive touchscreen setup:

1.

• By default, the device is capable of detecting more than one touch point and tracking multi-touch gestures. To simplify usage to single-touch, you typically disable extra coordinate channels dedicated to multi-touch in the configuration registers (explained in Section 8 of the datasheet).
• In single-touch mode, the controller measures one (X, Y) coordinate pair per valid touch. Pressure (Z) can also be measured if desired, but it’s not strictly necessary for basic single-touch coordinate acquisition.

2. Configure Auto-Mode or Manual Mode depending on whether you want continuous scanning or on-demand measurements.

3. Adjust PENIRQ and PINTDAV settings in config 2 register

4. Read X, Y Coordinates via interrupt (auto-mode) 

• The TSC2013-Q1 detects a screen press based on the pen-down threshold. If interrupts are enabled, the INT pin goes active when a touch is registered.
• When data is ready, it’s placed in the internal registers or FIFO.
• If using interrupts, the host (RZ/A1H) sees INT asserted and performs an I²C read of the data registers/FIFO.
• Once the user lifts a finger, the TSC2013-Q1 detects that pen-down is no longer valid.
• You can monitor a specific status register or rely on INT going inactive, depending on how you set up the interrupts.

5. Use RZ/A1H as I²C Master with correct bus speed, interrupt configuration, and recommended power settings.

Dear Daveon,

Thank you for the detailed configuration settings. I previously implemented the changes to CFR0 and CFR1. As per your suggestion, I have now implemented the CFR2 settings. The system is working much better,

However, I am encountering some issues with repeated values and ghosting. Specifically, the screen cursor occasionally moves erratically, displaying ghosting values, and some touch events are repeated intermittently. Here are a few examples

TOUCHEVENT - X, Y
TOUCHEVENT - 610, 310
TOUCHEVENT - 223, 279
TOUCHEVENT - 608, 313
TOUCHEVENT - 226, 284
TOUCHEVENT - 611, 313
TOUCHEVENT - 219, 281
TOUCHEVENT - 217, 283 - Repeated
TOUCHEVENT - 613, 309
TOUCHEVENT - 620, 318 - Repeated
TOUCHEVENT - 215, 284

Could you please advise on how to address these issues? Any additional configuration adjustments or troubleshooting steps would be greatly appreciated.

Thank you for your assistance.

Best regards,
Veer

Hi Veer,

You can try the following to prevent false touch events:

- Enable MAV filtering in CFR2 register to smooth out noisy touch data.
• Set 3-point or 5-point averaging for both X and Y coordinates.
• Add 100kΩ pull-downs on X+, X−, Y+, and Y− to prevent floating inputs.
• Use 100–470 pF caps to GND on touch lines to reduce high-frequency noise.
• Only read coordinates when PENIRQ is low and INT is asserted.
• Test with a known-good touchscreen panel to rule out hardware issues.