qt511 Quantum Research Group, qt511 Datasheet - Page 7

• Manufacturer Part Number: qt511
• Description: Qwheel? Touch Slider Ic
• Manufacturer: Quantum Research Group

Note: Pin /SS clamps to Vss for 250ns after coming out of
sleep state as a diagnostic pulse. To prevent a possible pin
drive conflict, /SS should either be driven by the host as an
open-drain pull-high drive (e.g. with a 100K pullup resistor), or
there should be a ~1K resistor placed in series with the /SS
pin.
3.2.2 DRDY Line
The DRDY line acts primarily as a way to inhibit the host from
clocking to the QT511 when the QT511 is busy. It also acts to
signal to the host when fresh data is available after a burst.
The host should not attempt to clock data to the QT511 when
DRDY is low, or the data will be ignored or cause a framing
error.
On power-up, DRDY will first float for about 20ms, then pull
low for ~525ms until the initial calibration cycle has
completed, then drive high to indicate completion of
calibration. The device will be ready to communicate in
typically under 600ms (with Cs1 = Cs2 = Cs3 =100nF).
While DRDY is a push-pull output ; however, this pin floats
after power-up and after wake from Sleep mode, for ~400µs
(typical at Vdd = 3.3V). It is desirable to use a pulldown
resistor on DRDY to prevent false signalling back to the host
controller; see Figure 1-1 and Section 1.3.
3.2.3 MISO / MOSI Data Lines
MISO and MOSI shift on the falling edge of each CLK pulse.
The data should be clocked in on the rising edge of CLK. This
applies to both the host and the QT511. The data path follows
a circular buffer, with data being mutually transferred from
host to QT, and QT to host, at the same time. However the
return data from the QT is always the standard response byte
regardless of the command.
The setup and hold times should be observed per Figure 3-1.
3.2.4 Sleep Mode
Please refer to Figure 3-1, page 6.
The device always enters low-power sleep mode after an SPI
transmission (Figure 3-1), at or before about 35µs after the
last rising edge of CLK. Before entering sleep mode, the
device will lower DRDY. If another immediate acquisition
burst is desired, /SS should be pulsed at least 35µs after the
last rising edge of CLK. To prolong the sleep state, it is only
necessary to pulse /SS after an even longer duration. During
this time, the QT511 will wake up approximately every 3
seconds and burst before going back to sleep. This allows
the QT511 to compensate for thermal changes.
Changes on CLK will also cause the device to wake, however
the device will not cause an acquire burst to occur if /SS has
also gone low and high again.
In sleep mode, the device consumes only a few microamps of
current. The average current can be controlled by the host, by
adjusting the percentage of time that the device spends in
sleep.
The delay between the wake signal and the following burst is
1ms max to allow power to stabilize. The DETECT and DRDY
lines will float for ~400µs (typical at Vdd = 3.3V) during wake
from Sleep mode; see Section 1.3 for details.
After each acquisition burst, DRDY will rise again to indicate
that the host can do another SPI transmission.
lQ
7
3.3 Commands
Commands are summarized in Table 3-1. Commands can be
overlapped, i.e. a new command can be used to shift out the
results from a prior command.
All commands cause a new acquisition burst to occur when
/SS is raised again after the command byte is fully clocked.
Standard Response: All SPI shifts return a ‘standard
response’ byte which depends on the touch detection state:
No touch detection:
Is touch detection:
Note that touch detection calculated position is based on the
results of the prior burst, which is triggered by the prior /SS
rising edge (usually, from the prior command, or, from a
dummy /SS trigger).
Bit 6 indicates the type of device: ‘1’ means that the device is
a wheel (e.g. QT511), and ‘0’ means the device is a linear
type (e.g. QT401 or QT411).
There are 5 commands as follows.
3.3.1 0x00 - Null Command
The Null command will trigger a new acquisition (if /SS rises),
otherwise, it does nothing. The response to this command is
the Standard Response byte, returned on the next SPI shift.
This command is predominant once the device has been
calibrated and is running normally.
3.3.2 0x01 - Calibrate
This command takes ~325ms @ 3.3V to complete.
0x01 causes the device to do a basic recalibration. After the
command is given the device will execute 10 acquisition
bursts in a row in order to perform the recalibration, without
the need for /SS to trigger each of the bursts. The host should
wait for DRDY to rise again after the calibration has
completed before shifting commands again.
This command should be given if there is an error
reported via the 0x04 command.
On power-up the device calibrates itself automatically and so
a 0x01 command is not required on startup.
The response to this command is the Standard Response
byte, returned on the next SPI shift. During calibration,
device communications are suspended.
3.3.3 0x03 - Drift Compensate
0x03 causes the sensor to perform incremental drift
compensation. This command must be given periodically in
order to allow the sensor to compensate for drift. The more
7
0
7
0
7
0
6
0
6
0
6
0
5
0
5
0
5
0
Bit 7 = 0 (0= not touched)
Bit 6 = 1 to indicate QWheel type
Bits 5, 4, 3, 2: unused (report 0)
Bits 1, 0 reserved (report 0 or 1)
Bit 7 = 1 (1= is touched)
Bits 0..6: Contains calculated position
= 0 to indicate Linear slider type
4
0
4
0
4
0
QT511-ISSG R6.01/1005
3
0
3
0
3
0
2
0
2
0
2
0
1
0
1
0
1
1
0
0
0
1
0
1