...
The Touch Sensor Module is now ready to communicate. After the procedure, the sensor module is enabled by default and will start sending ASN.1 serialized touch notifications. To disable the touch notifications, a Disable request must be sent. Refer to zForce Message Specification for examples of requests, responses and notifications.
...
Use the following procedure to prepare the Touch Sensor MOdule Module over I2C.
- Power on the Touch Sensor Module.
- Wait for sensor module to assert Data Ready pin (DR).
- Initiate 2 byte I2C read operation. Payload of this read should be EE XX where XX is the amount of bytes to read in a second I2C read operation.
Read XX amount of bytes (number of bytes to read is indicated by second byte of first I2C Read Operation). Now read a message called BootComplete. The message should be
Code Block theme Confluence F0 11 40 02 00 00 63 0B 80 01 YY 81 02 03 YY 82 02 00 YY
where YY is usually "00" but can have another value. This signals that the sensor module is now booted.
To enable the Touch Sensor Module to start sending touch notifications, do the following:
Send an Enable command:
Code Block theme Confluence EE 09 40 02 02 00 65 03 81 01 00
Read the response. The response should be:
Code Block theme Confluence EF 09 40 02 02 00 65 03 81 01 00
The Touch Sensor Module is now ready to communicate. When DR is asserted the sensor module will send a touch notification or a new BootComplete. A BootComplete indicates that the sensor module has restarted for some reason; Enable must then be set again. For more details, refer to I2C Transport.
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Read More on Software Integration
Read More
|