Document: GestIC® Design Guide
Latest update time：2021-09-01 12:03
Reads：
Introduction
The MGC3XXX gesture controller is based on Microchip's GestIC® technology and provides a fully integrated 3D gesture solution for a wide range of commercial, industrial, medical, and automotive applications.
This design guide introduces the GestIC electrode design rules, provides examples of excellent sensor designs, and addresses potential pitfalls. The design process for a GestIC system involves five steps, which are outlined in Figure 1-1.
Step 1:
Before embarking on the design, review the entire 3D application. The following points should be known:
-
Input Device Use Case - Sensor Range Expectations
-
Required 3D sensor functions
-
Available space for the sensor
-
Battery power status
-
Knowing the above information about how it works with Microchip 2D (touch controller) or 1D (button) solutions, a preliminary electrode design can be drawn.
Step 2:
Electrode design is performed within a given application boundary. The following information is required:
-
Mechanical structure of the equipment (dimensions, component placement, and metal/conductive parts)
-
Electronic circuits (block diagrams, power supplies, host controllers, peripherals, and interconnections)
-
Ground (GND) - a potential source of noise within the system.
Steps 3 and 4:
Integrate the sensor into the application's hardware and software architecture based on the information provided in step 2. Detailed information such as the overall system schematics and software architecture may be required.
After completing these steps, it is recommended to build a sensor prototype and parameterize it for the target application.
Step 5:
Adjust the GestIC firmware parameters.
This electrode design guide covers the fundamentals of GestIC electrode design (Steps 1 and 2) and hardware integration (Steps 3 and 4).
To view the full document, please click "Read the original text" below.
↓↓↓
Featured Posts
- How can I modify the registry to change the USB loading method in wince5.0?
- Iamanovice.IcameacrossaGPSall-in-onedeviceusingthewince5.0operatingsystem,withabuilt-in4GResidentFlash.IcanseethedrivelettersofResidentFlashandResidentFlash2intheresourcemanager,butthedriveletterdoesnotappear
-
foxdoghunter
Embedded System
Embedded System- After the microcontroller is powered on, the relay keeps ringing.
- IboughttheTieniuMCUonTaobao.Itworkedfinebefore,butIdon'tknowwhatprogramwasburnedintoit.Asaresult,therelaywouldmakeasoundeverytimethepowerwasturnedon,andthegreenlightundertherelaywouldflashforamoment.Du
-
cdlyz90
51mcu
- C8051 MCU cannot enter serial port interrupt
- IamusingtheC8051microcontroller.Nowserialport0cansendandreceivenormally,butserialport1cansenddatabutcannotenterthereceiveinterrupt.Thefollowingisthesoftwarecode.Pleasehelpmetakealook.voidUARTInit(void){PCON
-
fancyland
51mcu
- 【Low Power Consumption】Power Consumption Analysis at 40nm and 45nm Process Nodes
- Atthe40nmand45nmprocessnodes,powerconsumptionhasbecomethenumberonefactorinFPGAselection.ThiswhitepaperrevealshowXilinxdesignedthelatestSpartan-6(45nm)andVirtex-6(40nm)FPGAfamiliestoreducedynamicpowerconsumptio
-
hangsky
FPGA/CPLD
- (MSP430 sharing) Experience of using MSP430 microcontroller to write programs for products
- IhavebeenusingTI'sMSP430chipforseveralyears.Recently,IusedanMSP430G2231inmyproducts.Iamwillingtoshareitwithyou. LetmetalkabouttheMSP430G2231first.Facedwiththetemptationofthehugemid-to-low-endMCUmarket,TIfi
-
reayfei
Microcontroller MCU
- Why can't my KEIL software generate a Hex file even though there are no problems with compilation and linking? ?
- StartFragment I'musingSTM32F103C8.Doesanyoneknow?Intheproject,thereisanoutputoptioninthegenerate.hexfile,justcheckit.ThepictureItickedaboveisnotshowingup
-
爱好汽车电子
TI Technology Forum
京公网安备 11010802033920号