Skip to Content

MPLAB® Code Configurator (MCC) for Touch

Last modified by Microchip on 2026/02/23 09:11

MPLAB® Code Configurator (MCC) offers support for Classic, Harmony, and Melody platforms. Using this intuitive interface, C code can be added for the Peripheral Touch Controller (PTC) and Charge Voltage Discharge (CVD) devices. It supports 8-, 16-, and 32-bit devices, including PIC®, AVR®, and SAM microcontrollers (MCUs) as well as dsPIC® Digital Signal Controllers (DSCs). 

The MPLAB® Code Configurator (MCC) Touch Support by Device Family spreadsheet contains a list of the supported devices for MCC, MCC Melody, MPLAB Harmony, and START configurators. To find specific information for a configurator, check the device name and its corresponding feature set.

This section provides essential information related to MCC.

Step-by-Step Guides for Touch Projects From MCC

The various step-by-step guides for projects generated through MPLAB Harmony and MPLAB Melody, along with how to use the available features for touch, have been detailed in the following pages. 

MCC for Touch Host Driver

MCC has been used for configuring and generating host driver code to support MTCH2120 turnkey devices with Inter-Integrated Circuit (I2C) capability. See the MPLAB® Code Configurator for Touch Host Driver page for the procedure for getting started with the touch host driver. 

Back to Top

MPLAB Data Visualizer for Touch

Two options have been provided for visualizing touch data using MPLAB Data Visualizer. 

Unidirectional Tuning

Unidirectional tuning in MPLAB Data Visualizer refers to the process of adjusting parameters or settings in one direction—either increasing or decreasing—without oscillating back and forth. This approach is particularly useful when optimizing microcontroller performance, calibrating analog peripherals, or fine-tuning communication protocols. In MPLAB Data Visualizer, unidirectional tuning helps engineers systematically improve system behavior by making incremental changes and observing their effects. This approach ensures stability and predictability in the tuning process. By focusing on one direction, users can avoid overshooting optimal values and reduce the risk of introducing instability or errors into their embedded applications.

Unidirectional tuning requires a one-way communication with the device under test.  See the Guide to View Touch Data page for an example.

Bidirectional Tuning

See the following pages for detailed procedures on how to configure and use the bidirectional tuning capability in an application:

Back to Top