資料介紹
Table of Contents
AD714X Input CapTouch? Programmable Controller Linux Driver
Supported Devices
Evaluation Boards
Description
Capacitance Touch Sensors
Capacitance sensors detect a change in capacitance when something or someone approaches or touches the sensor. The technique has been used in industrial applications for many years to measure liquid levels, humidity, and material composition. A newer application, coming into widespread use, is in human-to-machine interfaces. Mechanical buttons, switches, and jog wheels have long been used as the interface between the user and the machine. Because of their many drawbacks, however, interface designers have been increasingly looking for more reliable solutions. Capacitive sensors can be used in the same manner as buttons, but they also can function with greater versatility, for example, when implementing a 128-position scroll bar.
For more info on how these types of sensors work, take a peek at the ADI web site.
Overview
Implementing a capacitive touch sensor solution using the AD714x requires three components:
- the AD714x capacitive-to-digital converter IC,
- sensors on a PCB or Flex Circuit,
- software to communicate with the AD714x.
The sensor traces can be any number of different shapes and sizes. Buttons, wheels, scroll-bar, joypad, and touchpad shapes can be laid out as traces on the sensor PCB.
Many options for implementing the user interface are available to the designer, ranging from simply replacing mechanical buttons with capacitive button sensors to eliminating buttons by using a joypad with eight output positions, or a scroll wheel that gives 128 output positions.
The number of sensors that can be implemented using a single device depends on the type of sensors required. The AD7142 has 14 capacitance input pins and 12 conversion channels, the AD7143 and AD7148 have 8 capacitance input pins and 8 conversion channels, and the AD7147 and AD7147A have 13 capacitance input pins and 12 conversion channels.
Configuration
Software configurable features
Source Code
Status
Files
Function | File |
---|---|
driver | drivers/input/misc/ad714x.c |
i2c bus support | drivers/input/misc/ad714x-i2c.c |
spi bus support | drivers/input/misc/ad714x-spi.c |
include | include/linux/input/ad714x.h |
In Linux, there are three driver modules for the AD714x: linux-2.6.x/drivers/input/misc/ad714x.c linux-2.6.x/drivers/input/misc/ad714x-spi.c linux-2.6.x/drivers/input/misc/ad714x-i2c.c.
ad714x.c fulfills the common arithmetic and state machines for sliders, keypads, touchpads and so on. ad714x-spi.c and ad714x-i2c.c, which call common probe/remove entries in ad714x.c, merge the bottom ad714x driver into Linux SPI/I2C device driver framework. The code included works with the AD7142 and AD7147 demo board. Note that this code is covered under the GPL - if you want non-GPL source, have a look at ADI's Web site.
Example platform device initialization
For compile time configuration, it’s common Linux practice to keep board- and application-specific configuration out of the main driver file, instead putting it into the board support file.
For devices on custom boards, as typical of embedded and SoC-(system-on-chip) based hardware, Linux uses platform_data to point to board-specific structures describing devices and how they are connected to the SoC. This can include available ports, chip variants, preferred modes, default initialization, additional pin roles, and so on. This shrinks the board-support packages (BSPs) and minimizes board and application specific #ifdefs in drivers.
platform data, defines how the PCB info is implemented.
Declaring I2C devices
Unlike PCI or USB devices, I2C devices are not enumerated at the hardware level. Instead, the software must know which devices are connected on each I2C bus segment, and what address these devices are using. For this reason, the kernel code must instantiate I2C devices explicitly. There are different ways to achieve this, depending on the context and requirements. However the most common method is to declare the I2C devices by bus number.
This method is appropriate when the I2C bus is a system bus, as in many embedded systems, wherein each I2C bus has a number which is known in advance. It is thus possible to pre-declare the I2C devices that inhabit this bus. This is done with an array of struct i2c_board_info, which is registered by calling i2c_register_board_info().
So, to enable such a driver one need only edit the board support file by adding an appropriate entry to i2c_board_info.
For more information see: Documentation/i2c/instantiating-devices
For AD7142 demo board, the platform information is:
Declaring SPI slave devices
Unlike PCI or USB devices, SPI devices are not enumerated at the hardware level. Instead, the software must know which devices are connected on each SPI bus segment, and what slave selects these devices are using. For this reason, the kernel code must instantiate SPI devices explicitly. The most common method is to declare the SPI devices by bus number.
This method is appropriate when the SPI bus is a system bus, as in many embedded systems, wherein each SPI bus has a number which is known in advance. It is thus possible to pre-declare the SPI devices that inhabit this bus. This is done with an array of struct spi_board_info, which is registered by calling spi_register_board_info().
For more information see: Documentation/spi/spi-summary
For AD7147 demo board, the platform information is:
Adding Linux driver support
To select it from menuconfig:
Device Drivers ---> Input device support ---> [*] Miscellaneous devices ---> <*> Analog Devices AD714x Capacitance Touch Sensor <*> support I2C bus connection <*> support SPI bus connection
Hardware configuration
We connected the AD7142 demo board to the TWI/I2C connector and AD7147 demo board to the SPI connector on the BF537 STAMP board.
For BF537 STAMP board, please set SW5-3 off as the interrupt input.
And For AD7147 eval-board, please set S4-2 on and other positions off.
Driver testing
Some testing output from the event_test application:
root:~> modprobe ad7142.ko input: ad7142 joystick as /class/input/input0 ad7142_js_attach: at 0x58 root:~> event_test /dev/input/event0 Input driver version is 1.0.0 Input device ID: bus 0x18 vendor 0x1 product 0x1 version 0x100 Input device name: "ad7142 joystick" Supported events: Event type 0 (Reset) Event code 0 (Reset) Event code 1 (Key) Event type 1 (Key) Event code 103 (Up) Event code 105 (Left) Event code 106 (Right) Event code 108 (Down) Event code 294 (BaseBtn) Event code 295 (BaseBtn2) Event code 296 (BaseBtn3) Event code 297 (BaseBtn4) Testing ... (interrupt to exit) Event: time 398.520833, type 0 (Reset), code 0 (Reset), value 0 Event: time 400.734865, type 1 (Key), code 108 (Down), value 1 Event: time 400.734874, type 0 (Reset), code 0 (Reset), value 0 Event: time 400.853353, type 1 (Key), code 108 (Down), value 0 Event: time 400.853360, type 0 (Reset), code 0 (Reset), value 0 Event: time 400.930182, type 1 (Key), code 103 (Up), value 1 Event: time 400.931390, type 0 (Reset), code 0 (Reset), value 0 Event: time 401.046258, type 1 (Key), code 103 (Up), value 0 Event: time 401.047461, type 0 (Reset), code 0 (Reset), value 0 Event: time 402.361193, type 1 (Key), code 294 (BaseBtn), value 1 Event: time 402.362403, type 0 (Reset), code 0 (Reset), value 0 Event: time 402.555558, type 1 (Key), code 294 (BaseBtn), value 0 Event: time 402.556760, type 0 (Reset), code 0 (Reset), value 0 Event: time 402.942508, type 1 (Key), code 295 (BaseBtn2), value 1 Event: time 402.942516, type 0 (Reset), code 0 (Reset), value 0
More Information
- 可編程控制器PLC概述
- 《圖解繼電器與可編程控制器》岡本裕生著 0次下載
- 可編程控制器AC500用戶手冊 1次下載
- 可編程控制器原理及應(yīng)用 21次下載
- XD和XL系列可編程控制器的規(guī)格參數(shù)和輸入輸出接線及運行維護的說明 4次下載
- 可編程控制器基礎(chǔ)及編程技巧 15次下載
- 可編程控制器原理及應(yīng)用系統(tǒng)設(shè)計技術(shù) 15次下載
- 可編程控制器控制系統(tǒng)設(shè)計 0次下載
- 可編程控制器基本指令 0次下載
- 可編程控制器系統(tǒng)構(gòu)成與工作原理 0次下載
- 可編程控制器原理及應(yīng)用 PPT
- 可編程控制器概況
- 可編程控制器(PLC) 0次下載
- 可編程控制器應(yīng)用101例 (三菱電機可編程控制器)
- 可編程控制器概述 ppt 0次下載
- plc可編程控制器是以什么方式進行工作的 896次閱讀
- 國產(chǎn)可編程系統(tǒng)AnyControl的具體功能和特點 3793次閱讀
- 可編程控制器與變頻器的連接和連接時應(yīng)注意的問題 761次閱讀
- 可編程控制器的基本應(yīng)用詳細講解 6805次閱讀
- 可編程控制器的特點有哪些 8439次閱讀
- 使用AT89C51實現(xiàn)的微型可編程控制器的講解 2605次閱讀
- 使用可編程控制器需要注意什么事項 4503次閱讀
- 如何使用可編程控制器替代繼電器 4837次閱讀
- 采用VxWorks嵌入式操作系統(tǒng)實現(xiàn)MB系列智能可編程控制器的軟硬件設(shè)計 3630次閱讀
- 可編程控制器的基本指令_可編程控制器的組成 4721次閱讀
- 可編程控制器與單片機的區(qū)別 1.2w次閱讀
- 超小型可編程控制器它指的是什么 1433次閱讀
- 可編程邏輯控制器是什么_可編程邏輯控制器原理 1w次閱讀
- 可編程控制器基本知識_可編程控制器原理及應(yīng)用 5.8w次閱讀
- 可編程定時控制器電路 3196次閱讀
下載排行
本周
- 1電子電路原理第七版PDF電子教材免費下載
- 0.00 MB | 1491次下載 | 免費
- 2單片機典型實例介紹
- 18.19 MB | 95次下載 | 1 積分
- 3S7-200PLC編程實例詳細資料
- 1.17 MB | 27次下載 | 1 積分
- 4筆記本電腦主板的元件識別和講解說明
- 4.28 MB | 18次下載 | 4 積分
- 5開關(guān)電源原理及各功能電路詳解
- 0.38 MB | 11次下載 | 免費
- 6100W短波放大電路圖
- 0.05 MB | 4次下載 | 3 積分
- 7基于單片機和 SG3525的程控開關(guān)電源設(shè)計
- 0.23 MB | 4次下載 | 免費
- 8基于AT89C2051/4051單片機編程器的實驗
- 0.11 MB | 4次下載 | 免費
本月
- 1OrCAD10.5下載OrCAD10.5中文版軟件
- 0.00 MB | 234313次下載 | 免費
- 2PADS 9.0 2009最新版 -下載
- 0.00 MB | 66304次下載 | 免費
- 3protel99下載protel99軟件下載(中文版)
- 0.00 MB | 51209次下載 | 免費
- 4LabView 8.0 專業(yè)版下載 (3CD完整版)
- 0.00 MB | 51043次下載 | 免費
- 5555集成電路應(yīng)用800例(新編版)
- 0.00 MB | 33562次下載 | 免費
- 6接口電路圖大全
- 未知 | 30320次下載 | 免費
- 7Multisim 10下載Multisim 10 中文版
- 0.00 MB | 28588次下載 | 免費
- 8開關(guān)電源設(shè)計實例指南
- 未知 | 21539次下載 | 免費
總榜
- 1matlab軟件下載入口
- 未知 | 935053次下載 | 免費
- 2protel99se軟件下載(可英文版轉(zhuǎn)中文版)
- 78.1 MB | 537793次下載 | 免費
- 3MATLAB 7.1 下載 (含軟件介紹)
- 未知 | 420026次下載 | 免費
- 4OrCAD10.5下載OrCAD10.5中文版軟件
- 0.00 MB | 234313次下載 | 免費
- 5Altium DXP2002下載入口
- 未知 | 233046次下載 | 免費
- 6電路仿真軟件multisim 10.0免費下載
- 340992 | 191183次下載 | 免費
- 7十天學(xué)會AVR單片機與C語言視頻教程 下載
- 158M | 183277次下載 | 免費
- 8proe5.0野火版下載(中文版免費下載)
- 未知 | 138039次下載 | 免費
評論
查看更多