All documentation becomes dated, and this manual is no exception. Microchip tools and
documentation are constantly evolving to meet customer needs, so some actual dialogs and/or
tool descriptions may differ from those in this document. Please refer to our website
(www.microchip.com) to obtain the latest documentation available.
Documents are identified with a “DS” number. This number is located on the bottom of each
page, in front of the page number. The numbering convention for the DS number is
“DSXXXXXA”, where “XXXXX” is the document number and “A” is the revision level of the
document.
Introduction
This document describes how to tune GestIC® systems that consist of an MGC3140 gesture controller
based on Microchip's GestIC technology and Gesture sensor.
Recommended Reading
For the latest information on using the device, read the “MGC3140 3D Tracking and Gesture Controller
Data Sheet” (DS40002037) located on the Microchip website. The release notes (Readme) contain
update information and known issues that may not be included in this user’s guide. For the latest
information on using the Aurea GUI, refer to the “Aurea Graphical User Interface User’s Guide”
(DS40001681) located on the Microchip website.
The MGC3140 Gesture IC (GestIC) has two types of parameters:
1.Run-time parameters that control basic functions such as selecting which of the five preset
frequencies (between 1 and 5) to use, enabling and disabling gestures and forcing a recalibration
(baseline). These are controlled by the host over the I2C interface using messages defined in the
MGC3140 run-time library interface specification reference.
2.Design-specific design-time parameters, which are configured once per project at design time and
control design characteristics, such as electrode weighting, gesture timings, and signal thresholds.
These parameters are configured using the Aurea Graphical User Interface application.
This document describes the tuning process for both the run-time and the design-time parameters.
1.1 Aurea
The Aurea Graphical Interface User’s Guide describes the use of the Aurea graphical interface to:
•Monitor the output of the MGC3140
•Control MGC3140 run-time parameters
•Configure MGC3140 design-time parameters
•Load design-time parameter files onto the MGC3140
•Program the MGC3140
•Update the MGC3140 bootloader
•Save the MGC3140 firmware and parameterization data in order to provide a final firmware (FW)
and parameterization combination for manufacture
MGC3140
Introduction
(1)
Note:
1.Combines the FW and parameters that are in Aurea that were loaded onto the device. Aurea does
not read firmware from the device.
1.1.1 Firmware and Parameter Update Using Aurea
Aurea uses a compressed file containing MGC3140 firmware, bootloader and parameterization data as
an image source for programming the MGC3140. It can also save the parameterization file and the
existing firmware from the .enz file
extension .enz.
Note:
1.The firmware cannot be read back from the IC. A newly created .enz file will create FW from the
parameters tuned in Aurea (on the PC) and the FW used by Aurea to download to the MGC3140.
1.1.1.1 Aurea .enz File Format
An .enz file is simply a zip container containing a number of files including a special file called
contents.json which describes the content of the .enz file.
•Library.hex – Contains MGC3140 firmware and bootloader in standard Intel® HEX format.
•Library.settings – A text description of design-time parameter settings.
•Loader.hex – Contains the MGC3140 bootloader in standard Intel HEX format.
•Content.json – Describes the contents of the .enz file.
Note: Aurea will not program the bootloader if the current bootloader in the MGC3140 has the same
version as in this file.
(1)
into a new compressed file. This file is noted by the
It has to be noted that the implemented tuning steps will depend on the customer requirements.
Positional accuracy or reporting, some gestures or GestIC electrode touch, approach and power-saving
may or may not be required.
During the setup process, tuning parameters are adjusted using slide bars that are dragged using the
mouse. For fine tuning, click on the Slider and use the left-right arrow keys to adjust the parameter value.
In order to tune the design-time parameters, select the Setup tab in Aurea and press the 3D
Parameterization button.
Figure 3-1. Aurea Parameterization
MGC3140
Tuning
The Aurea Setup tab has two top-level menu items on the left:
•Basic – Allows basic setup of the Analog Front-End by mapping the receive electrodes to the
MGC3140 receive pins. This feature provides Printed Circuit Board (PCB) layout flexibility.
•Extended – Allows detailed tuning.
Figure 3-2. Setup - Basic Menu
3.1 Electrode Mapping
The Analog Front-End (AFE) settings comprising of Electrode Selection and Electrode Mapping can be
modified on this page. They adjust the connection between the MGC3140 and the external electrodes.
The settings are adjusted using the corresponding radio buttons or sliders.
•Electrode Selection
The optional Center electrode can be enabled or disabled by checking the four electrodes (no
Center) or five electrodes (with Center) check boxes.
Only the four frame electrodes (North, East, South, and West) are used for signal processing.
–Five electrodes
All four frame electrodes and the Center electrode are used for signal processing.
•Electrode Mapping
The electrode mapping allocates the MGC3140 RX pins to the outlying electrodes. The correct
electrode mapping can be verified by touching the electrode and monitoring the signals in the
Signals tab. The corresponding electrode signal in the Rx Signals tab should then increase.
3.2 Extended Parameterization
When selected, the Extended menu item opens up the Firmware Selection window. The use of this
window ensures that the correct firmware is loaded onto the MGC3140 for the design-time
parameterization process.
3.2.1 Firmware
Load the firmware and parameter file which will be used as a basis for the tuning using this window, as
described in the "Aurea Graphical User Interface User's Guide" (DS40001681). Remember to select the
“Keep the current AFE parameters” check box unless the AFE electrode selection and mapping of the
parameters that are about to be downloaded are going to be used instead.
MGC3140
Tuning
Once the firmware has been loaded, the full Extended Parameter window becomes available providing
the following menu options. See figure below.
Note: The extended parameter options are only available after firmware and parameter download. They
disappear after exiting the Setup tab, or disconnecting or resetting the MGC3140, and require another
firmware and parameter download before becoming visible again.
The Tx frequency selection is available from the System Start-up window.
A range of five frequencies may be selected or deselected to avoid noise. The MGC3140 constantly
monitors the noise levels on all selected frequencies and will hop to the lowest noise level frequency
when the current frequency noise gets too high. The automatic frequency hopping can be limited by
unchecking one or more frequencies in the list. The following frequencies are available: 42 kHz, 43 kHz,
44 kHz, 45 kHz, and 100 kHz.
3.2.2.2 Active Features
The Colibri Suite features can be active or inactive on MGC3140 start-up.
•Approach Detection – Selects if the Approach Detection feature is enabled at start-up.
•Touch Detection – Selects if the Touch Detection feature is enabled at start-up.
•Gestures – Selects if a particular gesture is active at start-up.
•Flicks – Flick selection has the behavior shown in the table below.
MGC3140
Tuning
Table 3-1. Flick Selection
Double Flick Edge Flick Normal Flick Description
000
001
010
011
100
101
110
111
Note:
1.0 = Not selected
2.1 = Selected
None Active
Only Normal Flick reported
Only Edge Flick reported
Normal and Edge Flicks reported
Double Flick reported. Disables Normal and Edge Flicks.
Normal and Edge Flicks are never reported.
Double Flick is reported. Disables Normal Flicks and Edge
Flicks. Normal and Edge Flicks are never reported.
Double Flick reported. Disables Normal and Edge Flicks.
Normal and Edge Flicks are never reported. If calibration
after flick is enabled in the Gestures menu by selecting the
'triggers calib' option, then calibrations may still be triggered
when the hand leaves the sensing area after flicks, or in the
middle of a Double Flick.
These settings should not be selected.
•Circles/AirWheel: Discrete Circles and AirWheel are exclusive. The Airwheel has higher priority
than discrete circles. When the AirWheel is enabled, only AirWheel information will be reported. To
use the Discrete Circle gestures, AirWheel must be disabled.
The Sensor Data Output I2C message (ID 0x91) contains all data which are generated in MGC3140. That
includes recognized gestures as well as continuous data like position or raw sensor data.
A detailed description of the I2C message format can be found in the "MGC3140 GestIC® Library
Interface Description User's Guide" (DS40001875).
If selected, data (On or Dynamic) will be added as a payload element to the sensor data output I2C
message.
There are three options for data selection:
•Off – Data will never be sent.
•On – Data are sent with every packet.
•Dynamic – Only changes will be sent to minimize data traffic.
The following table lists the payload elements of the sensor data output message.
Table 3-2. Sensor Data Output Payload Elements
Data/Payload
DSP Status
Gesture Data
Touch Data
AirWheel Data
Position Data
Noise Power
Uncalibrated Signal Data
Signal Deviation Data
(1)
ElementLibrary CommandDescription
DSPStatus
GestureInfo
TouchInfo
AirWheelInfo
xyzPosition
NoisePower
CICData
SDData
This field contains the Calibration
events information and the currently
used Tx frequency.
This field contains the recognized
gestures.
This field contains the Touch events
information.
This field contains the AirWheel
information.
This field contains the X, Y and Z
position data.
This field contains the current
measured signal variance.
This field contains the Uncalibrated
Signal (CIC) data.
This field contains the Signal Deviation
(SD) data.
AirWheel counter decimated by factor 4If set, AirWheel counter is only
reported when a change of at least four
bits has occurred.
Note:
1.Payload Element names are those defined in the "MGC3140GestIC® Library Interface Description