System, method, and computer program product embodiments are provided for a projected capacitive (PCAP) touch system that includes a touchscreen and two or more touch controller application-specific integrated circuits (asics) communicatively coupled to the touchscreen, where connections between receiver (and/or driver) circuits of the two or more touch controller asics and touchscreen electrodes are interleaved. The two or more touch controller asics do not exchange raw mutual capacitance or self capacitance data during a measurement frame. Further, a processor may be coupled to the two or more touch controller asics, and may determine final touch coordinates based on all subsets of coarse touch coordinate data from each of the two or more touch controller asics. Embodiments also include determining each subset of coarse touch coordinate data based on a shape of a touch rather than a two-dimensional square or rectangular region of the touchscreen.
|
1. A projected capacitive (PCAP) touch system comprising:
a touchscreen; and
a first and a second touch controller application-specific integrated circuit (asic) communicatively coupled to the touchscreen to detect self-capacitive touch data from touchscreen electrodes over an entire touch area of the touchscreen, wherein a first driver circuit of the first touch controller asic comprises first connections to a first subset of the touchscreen electrodes, wherein a second driver circuit of the second touch controller asic comprises second connections to a second subset of the touchscreen electrodes, wherein the first subset of the touchscreen electrodes is interleaved with the second subset of the touchscreen electrodes.
12. A method, for a first touch controller application-specific integrated circuit (asic), comprising:
determining a first subset of coarse touch coordinate data received from first driver circuits coupled to a first subset of touchscreen electrodes of a projected capacitive (PCAP) touchscreen, wherein the first subset of touchscreen electrodes is interleaved with a second subset of touchscreen electrodes, wherein the second subset of touchscreen electrodes is coupled to second driver circuits of a second touch controller asic, and wherein the first subset of touchscreen electrodes and the second subset of touchscreen electrodes together cover an entire touch area of the PCAP touchscreen; and
transmitting the first subset of coarse touch coordinate data to a processor, wherein the processor receives a second subset of coarse touch coordinate data from the second touch controller asic, and wherein the processor determines final touch coordinates based on the first subset of coarse touch coordinate data and the second subset of coarse touch coordinate data.
20. A non-transitory computer readable medium having stored therein one or more instructions that, when executed by one or more processors, cause the one or more processors of a first touch controller application-specific integrated circuit (asic) to perform operations, the operations comprising:
determining a first subset of coarse touch coordinate data received from first driver circuits coupled to a first subset of touchscreen electrodes of a projected capacitive (PCAP) touchscreen, wherein the first subset of touchscreen electrodes is interleaved with a second subset of touchscreen electrodes, wherein the second subset of touchscreen electrodes is coupled to second driver circuits of a second touch controller asic, wherein the first subset of touchscreen electrodes and the second subset of touchscreen electrodes together cover an entire touch area of the PCAP touchscreen; and
transmitting the first subset of coarse touch coordinate data to a processor, wherein the processor receives a second subset of coarse touch coordinate data from the second touch controller asic, and wherein the processor determines final touch coordinates based on the first subset of coarse touch coordinate data and the second subset of coarse touch coordinate data.
2. The PCAP touch system of
3. The PCAP touch system of
4. The PCAP touch system of
5. The PCAP touch system of
6. The PCAP touch system of
7. The PCAP touch system of
8. The PCAP touch system of
9. The PCAP touch system of
10. The PCAP touch system of
11. The PCAP touch system of
13. The method of
14. The method of
15. The method of
16. The method of
17. The method of
a partial sum of mutual capacitance measurements satisfying a significant touch threshold across a third subset of touchscreen electrodes of the PCAP touchscreen; an X touch coordinate associated with the third subset of touchscreen electrodes; and a Y touch coordinate associated with the third subset of touchscreen electrodes, and
wherein the determining a first subset of coarse touch coordinate data is performed without communicating with the second touch controller asic.
18. The method of
19. The method of
|
This application is a continuation of U.S. patent application Ser. No. 15/874,510, filed on Jan. 18, 2018, entitled Large PCAP Screen with Multiple Touch Controller ASICs with Interleaved Receiver Connections, the contents of which are hereby incorporated by reference in its entirety.
The present disclosure relates generally to touch sensitive systems, and more specifically to large scale display systems.
The ability to interact with computer applications via touch with displays is ubiquitous for today's consumers. While several touch technologies are possible to support touch interactions, each has advantages and disadvantages that tailor each for particular environments, sizes, and applications. Projected capacitive (PCAP) technology is utilized to support characteristics expected from touch interactions in small screen devices such as handheld devices, e.g., smartphones, tablets, etc. Translating those characteristics for use with larger screens and applications faces challenges.
Large PCAP touchscreen systems that include multiple touch controller application-specific integrated circuits (ASICs) to support a large number of sensor electrodes result in increased cost and complexity to achieve acceptable response times and touch detection accuracy compared to smaller PCAP touchscreen systems with a single touch controller ASIC. Further, implementing a single touch controller ASIC that would provide enough sensor input/output (I/O) pins to cover the large number of sensor electrodes required for a large PCAP touchscreen in the same manner as a smaller PCAP touchscreen would be cost prohibitive.
Large projected capacitive (PCAP) touchscreens that include multiple PCAP touch controller application-specific integrated circuits (ASICs) are computationally intensive. For example embodiments discussed herein, references of “ASIC” means a “PCAP touch controller ASIC,” and “electrode” means “touchscreen electrode.” When an ASIC of the multiple ASICs that cover a large PCAP touchscreen system, obtains raw touch signal data from a portion of the large PCAP touchscreen, a data processor needs to merge this ASIC's raw touch signal data with raw touch signal data from the remaining multiple ASICs before the final touch contact locations (e.g., (x,y) coordinates) are processed and derived for the large PCAP touchscreen. The exchanging and merging of the raw touch signal data among the multiple ASIC's can be computationally intensive.
Some embodiments include a PCAP touch system with a large PCAP touchscreen having a large number of electrodes and multiple ASICs that avoid the complexity of exchanging and/or merging the raw touch signal data among the multiple ASICs.
System, method, and computer program product embodiments are provided for a PCAP touch system that includes a touchscreen and two or more touch controller application-specific integrated circuits (ASICs) communicatively coupled to the touchscreen, to detect capacitive touch data from touchscreen electrodes, wherein each receiver circuit of the two or more touch controller ASICs connects to a selected portion of the touchscreen electrodes in an interleaved manner. In some embodiments, the two or more touch controller ASICs do not exchange raw mutual capacitance data during a measurement frame.
In some embodiments, the one or more processors are configured to: determine a final touch coordinate based on a first subset of coarse touch coordinate data from a first touch controller ASIC and a second subset of coarse touch coordinate data from a second touch controller ASIC. Each subset of coarse touch coordinate data from the first or second touch controller ASIC may be based at least on a number of horizontal and vertical electrode intersections whose mutual capacitance measurements satisfy a significant touch threshold. In addition, a first subset of touchscreen electrodes may be odd numbered and a second subset of touchscreen electrodes may be even numbered, wherein each subset of coarse touch coordinate data includes: a partial sum of mutual capacitance measurements satisfying a significant touch threshold across each subset of touchscreen electrodes; an X touch coordinate associated with each subset of touchscreen electrodes; and a Y touch coordinate associated with each subset of touchscreen electrodes, wherein the partial sum, X touch coordinate, and Y touch coordinate are calculated by each touch controller ASIC individually for one of the first subset or the second subset of touchscreen electrodes without communicating with the other touch controller ASIC.
In the PCAP touch system, a coarse pitch size of each subset of coarse touch coordinate data from one of the two or more touch controller ASICs may be based on a pitch size of the touchscreen and a number of the two or more touch controller ASICs. Some embodiments include third connections between driver circuits of the first touch controller ASIC and a third subset of touchscreen electrodes of the touchscreen, that are interleaved with fourth connections, wherein the fourth connections are between driver circuits of the second touch controller ASIC and a fourth subset of touchscreen electrodes of the touchscreen. The two or more touch controller ASICs may be configured to determine self-capacitance measurements.
Further embodiments, features, and advantages of the present disclosure, as well as the structure and operation of the various embodiments of the present disclosure, are described in detail below with reference to the accompanying drawings.
The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the disclosure and to enable a person skilled in the relevant art(s) to make and use the disclosure.
The present disclosure will now be described with reference to the accompanying drawings. In the drawings, generally, like reference numbers indicate identical or functionally similar elements. Additionally, generally, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears.
The following Detailed Description of the present disclosure refers to the accompanying drawings that illustrate exemplary embodiments consistent with this disclosure. The exemplary embodiments will fully reveal the general nature of the disclosure that others can, by applying knowledge of those skilled in relevant art(s), readily modify and/or adapt for various applications such exemplary embodiments, without undue experimentation, without departing from the spirit and scope of the disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and plurality of equivalents of the exemplary embodiments based upon the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by those skilled in relevant art(s) in light of the teachings herein. Therefore, the detailed description is not meant to limit the present disclosure.
The embodiment(s) described, and references in the specification to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment(s) described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
U.S. patent application Ser. No. 15/214,196, entitled Projected-Capacitive(PCAP) Touchscreen filed on Jul. 19, 2016, and U.S. patent application Ser. No. 14/871,496, entitled Supporting Multiple Users on a Large Scale Projected Capacitive Touchscreen ('496 Application) filed on Sep. 30, 2015, are herein incorporated by reference in their entirety. Both of these applications describe PCAP touchscreen systems.
U.S. patent application Ser. No. 62/508,549, entitled PCAP with Enhanced Immunity to Water Contaminants filed on May 19, 2017, (“Immunity Application”) which is incorporated herein by reference in its entirety, includes description of a mixed-mode measurement frame that includes self-mode measurement and a mutual-mode measurement.
Touchscreen 110 may be communicatively coupled to circuit board 140 via interface 160, and circuit board 140 may be communicatively coupled to computing device 130 via interface 170. Interfaces 160 and 170 may be wired or wireless and comprise various technologies including but not limited to universal serial bus (USB), Bluetooth™ Low Energy (BLE), Wi-Fi™, and/or logic traces on a circuit board that may be coupled to a connector.
Circuit board 140 may include two or more touchscreen controller application-specific integrated circuits (ASICs) although only 120a and 120b are depicted. Each touchscreen controller ASIC 120 includes their respective firmware 125. Computing device 130 may be a host computer running software application 135 (e.g., application-level software), such as a gaming application. Software application 135 may support multiple users that interact with software application 135. Touchscreen controllers ASIC 120a and 120b include corresponding firmware 125 that may communicate with software application 135 in computing device 130 via a communication protocol to support the performance characteristics of software application 135. The communication between firmware 125 and software application 135 may be indirect via processor 150.
Circuit board 140 may also include processor 150 that may include a USB interface, for example. Processor 150 may receive coarse touch coordinate data from each of the touchscreen controller ASICs 120, and use the received coarse touch coordinate data to calculate final touch coordinates, for example by linear interpolation or weighted summation. Processor 150 may generate reports that include the final touch coordinates (e.g., (x,y) coordinates) and transmit the reports to computing device 130 via interface 170. Note that there is no exchange of raw touch signal data (e.g., raw mutual capacitance measurements) between touchscreen controller ASIC 120a and touchscreen controller ASIC 120b. Coarse touch coordinate data is different than raw touch signal data. For example, coarse touch coordinate data may include compressed and processed high-level information regarding portioned estimates of touch coordinates and portioned touch signal sums around touch center locations from each of the touchscreen controller ASICs 120 as described later.
A case may arise ASIC 120a may provide clock synchronization information to touchscreen controller ASIC 120b, such as when touchscreen controller ASIC 120a is a master device and touchscreen controller ASIC 120b is a slave device. Providing clock synchronization information is not the same as exchanging raw touch signal data. Accordingly, processor 150 may be included in the master device, touchscreen controller ASIC 120a. Thus, touchscreen controller ASIC 120b may transmit coarse touch coordinate data to processor 150 for combining the coarse touch coordinate data from touchscreen controller ASIC 120b with coarse touch coordinate data received from touchscreen controller ASIC 120a to produce final touch coordinates.
The vertical electrodes 202.1 through 202.M are oriented in a vertical direction, such as parallel to the y-axis of the Cartesian coordinate system and perpendicular to the x-axis of the Cartesian coordinate system. In this configuration and arrangement, the vertical electrodes 202.1 through 202.M may be referred to as “X” electrodes due to their role in determining the x coordinates of the touch of the operator when present. However, those skilled in the relevant art(s) will recognize that the other configurations and arrangements for the vertical electrodes 202.1 through 202.M are possible without departing from the spirit and scope of the present disclosure.
As illustrated in
As additionally illustrated in
As shown in
As the term ‘floating’ implies, the plurality of floating transparent conductive islands represent shapes of transparent conductive material, which are not electrically connected within the electrodes 202.1 through 202.M. In an embodiment, the plurality of floating transparent conductive islands eliminate, or substantially reduce, one or more optical discontinuities that would be otherwise present in touchscreen 110 that includes electrodes 202.1 through 202.M.
In the exemplary embodiment illustrated in
As illustrated in
As additionally illustrated in
As shown in
As illustrated in
As further illustrated in
The touchscreen 400 can operate in a row scanning mode of operation or in a column scanning mode of operation. In the row scanning mode of operation, one or more horizontal electrodes from among the horizontal electrodes 302.1 through 302.N are sequentially excited by a drive signal. The drive signal capacitively couples to one or more vertical electrodes from among the vertical electrodes 202.1 through 202.M. Transferred electrical charges or currents due to mutual capacitance(s) between the driven horizontal electrode and the one or more vertical electrodes are measured to detect a presence and/or a location of a touch from an operator, such as a finger of the operator, a hand of the operator, and/or other objects available to the operator, such as a stylus to provide an example. Similarly, in the column scanning mode of operation, one or more vertical electrodes from among the vertical electrodes 202.1 through 202.M are sequentially excited by a drive signal. The drive signal capacitively couples to one or more horizontal electrodes from among the horizontal electrodes 302.1 through 302.N. Transferred electrical charges or currents due to mutual capacitance(s) between the driven vertical electrode and the one or more horizontal electrodes are measured to detect a presence and/or a location of a touch from an operator. The description to follow further describes the operation of the touchscreen 400 in the row scanning mode of operation. Those skilled in the relevant art(s) will recognize that the column scanning mode of operation operates in a similar manner without departing from the spirit and scope of the present disclosure.
During the row scanning mode of operation and as further illustrated in
Generally, a mutual capacitance “CM” is associated with each of the horizontal electrodes 302.1 through 302.N and a corresponding one of the vertical electrodes 202.1 through 202.M. For example, if “i” represents an index for a vertical electrode 202.i from among the vertical electrodes 202.1 through 202.M, and if “j” represents an index of a horizontal electrode 302.j from among the horizontal electrodes 302.1 through 302.N, then M·N mutual capacitances are present between the vertical electrodes 202.1 through 202.M and the horizontal electrodes 302.1 through 302.N, which can be denoted as the set of mutual capacitances CM(i,j) for i=1 to M and j=1 to N.
Below are formulas that may be used to process the low-level raw touch signal data ΔCM(i,j) to produce the high-level touch coordinates (x,y). Note that the resulting high-level information, namely the two numbers x and y, are highly compressed relative to the corresponding low-level data ΔCM(i,j), which corresponds to 28 numbers as drawn in
Readout of projected-capacitive touchscreens is done with appropriate controller electronics. Typically, controller electronics is in the form of a printed circuit board containing a number of electronic components including a sophisticated ASIC. The ASIC coordinates drive signals and measures the mutual capacitance signals ΔCM(i,j). Particularly for small projected-capacitive touchscreens used in mobile devices, a single ASIC contains sufficient circuitry and pins to support all of the touchscreens M+N electrodes. However, for larger commercial touchscreens, it is often the case that the controller electronics includes multiple ASICs to provide a sufficient number of electronic channels (e.g., driver and receiver circuits) to support all touchscreen electrodes.
The horizontal electrodes are driven sequentially, one at the time. For example, the horizontal electrode Y1 may be excited by driver circuits in ASIC 1, then Y2, then Y3, etc. while ASIC 2 driver circuits are off. After horizontal electrode with j index equal to N/2 has been excited, then the ASIC 1 driver circuits are turned off. After that ASIC 2 excites the horizontal electrode with j index equal to (N/2+1), and then (N/2+2), (N/2+3), etc. through to the last horizontal electrode YN. Note that even when one ASIC has its driver circuits off, its receiver circuits may be actively measuring values of CM(i,j) with the aid of excitation signals from the other ASIC. To enable one ASIC to make measurements with the aid of the other ASIC's excitation drive signals, the timing of the two ASICs are carefully synchronized. This is illustrated in
The time between successive pluses in logic trace (a) is the report rate of the touchscreen system. For example, if the time between successive pulses is 10 millisecond, then the report rate is 100 Hz or one-hundred touch coordinate reports per second. Typically, applications require that the time difference between successive frame trigger pulses be short compared to human perception times, for example, 10 milliseconds between frame trigger pulses. In the example given in the figure, the time between pulses in logic trace (a) is also an upper limit to the touch system latency, that is the time between physical contact of a finger touch and reported touch coordinates; however as will be discussed later, latency limits may differ if touches are reported in the next frame after the frame in which the touch measurements are made.
As illustrated in logic trace (b), drive signals from ASIC 1 for horizontal electrodes are initiated by the frame trigger pulse at time T0 and continues until time T2. At time T2, excitation of the upper horizontal electrodes is complete, and ASIC 2 begins driving horizontal electrodes in the lower half of the touchscreen. ASIC 2 generates such drive signals between time T2 and T3; see logic trace (c).
As illustrated in logic traces (d) and (e), both ASIC 1 and ASIC 2 are receiving signals from vertical electrodes and measuring mutual capacitance signals ΔCM(i,j) the entire time that either ASIC 1 or ASIC 2 are generating drive signals for horizontal electrodes.
The ASICs do not need to wait until all data is collected in order to initiate processing of raw mutual capacitance measurements into touch coordinates. For example, ASIC 1 has all the information needed to compute the (x,y) coordinates of touch A illustrated in
At the completion of data acquisition at time T3, neither ASIC 1 nor ASIC 2 have sufficient information to compute the (x,y) coordinates of touch C. Before raw signal data ΔCM(i,j) can be processed to produce the (x,y) coordinates of touch C, low-level raw touch data are exchanged between the two ASICs (or transferred to a third processor for coordinate calculation). Logic trace (f) illustrates such transfer of low-level raw touch data between times T3 and T4. After this transfer is complete, ASIC1 and ASIC 2 have sufficient information to compute touch coordinates of all touches on the touchscreen, including those at the boundary between left and right halves of the touchscreen. This is illustrated in logic traces (g) and (h) where touch data processing recommences and completes between time T4 and time T5.
Finally, between time T5, and the next frame trigger at T6, high-level touch information (e.g., final (x,y) touch coordinate information) is reported from one of the touchscreen controller ASIC's (e.g., a master touchscreen controller ASIC) or a separate micro-processor unit which coordinates the reporting of the final high-level touch information to the host computer, perhaps after the “touch coordinate tracking algorithms” further process high-level (x,y) touch coordinate information by making use of correlations of touch coordinates between frames.
Dealing with touches in the overlap region, such as touch C, reduces system response time, or adds complexity and cost, increases digital noise in touch signal measurements, or a combination of two or all of these. Added cost may be in the form of increased product development time and expenses, as well as increased manufacturing costs of the resulting products.
There are several ways in which the response time associated with the above timing diagram can be improved. If touch reporting (e.g., logic trace (i)) can overlap with mutual capacitance signal measurements ΔCM(i,j) (e.g., logic traces (d) and (e)), then the subsequent frame trigger pulse that initiates of the next cycle of data acquisition may be moved up from time T6 to time T5 or even T4; while this may improve the report rate, moving up the subsequent frame trigger pulse does not necessarily improve the latency of the touchscreen system. If inter-ASIC data transfer (e.g., logic trace (f)) can occur during measurement of mutual capacitance signals ΔCM(i,j), the timing of the subsequent frame trigger pulse (e.g., logic trace (a)) may be moved earlier to time T3. However enabling such parallel activity adds to circuit complexity and cost and also increases risk that digital noise will compromise the quality of measurements of mutual capacitance signals ΔCM(i,j).
As described above, multi-ASIC solutions for PCAP systems with large numbers of electrodes involve engineering trade-offs between response time, cost via complexity, and quality of signal measurements. There is demand for multi-ASIC solutions that minimize the engineering compromises made in such trade-offs.
By itself, in some cases, the hardware change in touchscreen electrode to electronic circuit connections of
Note that the hardware change involves interleaving of connections between vertical electrodes and receiver circuits but not between horizontal electrodes and drive circuits. Hence, there is an asymmetry between the treatment of receiver circuits and driver circuits. This asymmetry results from the fact that receiver circuits capture mutual capacitance data in parallel, while driver circuit excitations are performed serially.
In some embodiments, the use of formulas below may eliminate the need to transfer any raw mutual capacitance data ΔCM(i,j) between ASICs. First, the total sum of mutual capacitance signals ΔCM(i,j) (e.g., S) may be split into odd and even partial sums as shown below. One partial sum of index i is over all odd values of i within the range iMIN≤i≤iMAX. The even partial sum is similarly defined. Note that while the calculation of the total sum, S, requires data measured by both ASICs, the odd partial sum, SODD, may be calculated by ASIC 1 without any communication with ASIC 2. Similarly, the even partial sum, SEVEN, may be computed by ASIC 2 without any information from ASIC 1:
With following definitions, the above equation can be written more concisely.
Equation (1) below states that the total sum, S, equals the partial touch signal measured on odd numbered vertical electrodes, SODD, plus the partial touch signal measured on even numbered vertical electrodes, SEVEN:
S=SODD+SEVEN (Eq. 1)
The math becomes more complex for the touch coordinates x and y as follows:
With the following definitions, the above equation can be written more concisely. For example, the XODD coordinate estimated from signals on the odd vertical electrodes and the XEVEN coordinate estimated from signals on the even numbered vertical electrodes may be defined as follows (where the triple bar “≡” means equality by definition):
The concise version of the equation states that a precise value of the touch coordinate x may be computed as a weighted sum of XODD and XEVEN, the X coordinate estimated from signals on the odd and even numbered vertical electrodes respectively:
While XODD and XEVEN may be poor estimates of the touch coordinate, they may be used with the above Equation 2 to provide a precise estimate of the x touch coordinate.
Odd and even estimates of Y touch coordinates may be similarly defined as follows.
Similar as for the x coordinate, Equation 3 below states that a precise value of the touch coordinate y may be computed as a weighted sum of YODD and YEVEN, the y coordinate estimated from signals on the odd and even numbered vertical electrodes respectively.
The definitions of XODD and YODD are carefully chosen so that they may be computed entirely with information contained within ASIC 1 prior to any communication with ASIC 2. Similarly, XEVEN and YEVEN may be computed by ASIC 2 with no information from ASIC 1.
To compute (x,y) touch coordinates using Equations 1-3 above, coarse touch coordinate data (e.g., SODD, XODD, YODD, SEVEN, XEVEN, and YEVEN) may be communicated from respective ASIC 1 (e.g., touchscreen controller ASIC 120a) and ASIC 2 (touchscreen controller ASIC 120b) to synchronizing circuitry or processor (e.g., processor 150). For example, final (x,y) touchscreen coordinates may be computed and communicated by processor 150 to computing device 130 when processor 150 receives from ASIC 1 (e.g., touchscreen controller ASIC 120a) the three numerical values of SODD, XODD and YODD, and the values of SEVEN, XEVEN and YEVEN from ASIC2 (e.g., touchscreen controller ASIC 120b). Note that no raw mutual capacitance data ΔCM(i,j) need be exchanged between ASICs. Rather, the exchange of coarse touch coordinate data includes much compressed high-level touch information regarding odd or even estimates of touch coordinates and odd or even signal sums from respective ASICs to a processor (e.g., processor 150) that can result in the processor determining final touchscreen coordinates to be reported to computing device 130. And, the determining process may be a linear interpolation or a weighted summation function.
In the above equations, it was implicitly assumed that the two ASICs agree to common ranges of indices iMIN≤i≤iMAX and jMIN≤j≤jMAX in the neighborhood of each touch before computing odd and even estimates of touch coordinates and odd and even estimates of signal sums. Recall that the vertical electrodes are represented by “i” and the horizontal electrodes are represented by “j.” The implicit assumption of the common range of indices requires communication between the ASICs before odd and even touch coordinates can be computed, and is thus undesirable.
Alternative to summing over a square or rectangular region of touchscreen 110 containing a touch, some embodiments include a summation determined over whatever shape the touch has, which may be irregular, for example.
In
Some embodiments replace the two-dimensional sum over electrode indices i and j with a single sum over k. That is, instead of summing over a square or rectangular region containing the touch, the sum is over whatever irregular shape the touch may have. For any intersection index k, that horizontal and vertical indices i and j are determined by the intersection location. In this sense, i and j are functions of index k and may be notated as i(k) and j(k). With this notation, it is possible to calculate the touch signal sum and (x,y) coordinates using the following equations involving a single sum over k, rather than two dimensional sums (e.g., double sums) over i and j.
Similarly, the odd and even versions of coordinate estimates and partial signal sums may be redefined as follows, where the modified index k′ for the alternate expressions for XEVEN and YEVEN is defined by the equation k′=k−KODD.
It can be mathematically proven (but not shown here) that the above equations lead to the equations below.
These equations look exactly the same as equations derived above. However, there is a big difference. In some embodiments, SODD, XODD and YODD may be computed by ASIC 1 (using the index k) over a smaller area of touchscreen 110 and still with no information from ASIC 2. Likewise, SEVEN, XEVEN and YEVEN may be computed (using the alternative index k′) by ASIC 2 over a smaller area of touchscreen 110 and still with no information from ASIC 1.
Similar methods may be applied to touchscreen systems with three or more ASICs.
In the above equations, the total signal sum and ASIC partial signal sums are as follows where KFIRST, KSECOND, KTHIRD and KFOURTH are the number of mutual capacitance signals ΔCM(i,j) that satisfy a significant touch threshold measured by each corresponding ASIC for a touch. For the second, third and fourth ASIC signal partial sums, k′=k−KFIRST, k″=k′−KSECOND, and k′″=k″−KTHIRD are the corresponding indices.
Below are formulas for touch coordinate estimates of each ASIC:
With the above examples for two and four ASICs, corresponding formulas for other numbers of ASICs, such a three ASICs, may be determined.
Pitch size is the distance between two neighboring electrodes on the large PCAP touchscreen, and a common pitch size is 5 mm-7 mm. In the example of a PCAP touch system using two touch controller ASICs with interleaved connections of the receiver circuits, the coarse touch coordinate data (e.g., SODD, XODD and YODD) may be determined from an effective pitch size that is twice as large as the original pitch size of the touch screen. Accordingly, when the number of multiple ASICs used is N, each ASIC of the N ASICs processes raw touch data from a subgroup of electrodes that span the large PCAP touchscreen in the receiver dimension with a coarser pitch size than the original pitch size to produce a subset of the coarse touch coordinates data. The coarser pitch size may be equal to N*(Original_Pitch) size. Original pitch sizes less than 7.5 mm are desired in the receiver dimension for N=2, as the coarser pitch size seen by each of the N=2 ASIC's may be up to 15 mm in the receiver dimension.
The above embodiments may be applied to mixed mutual-mode and self-mode for increased water immunity as described in the Immunity Application. For the purpose of improving touch performance in the presence of water contaminants, it is useful to measure both self-capacitances and mutual capacitances. In brief, self-capacitance measurements are less susceptible to the effects of water contamination on the touch surface, while mutual-capacitance measurements provide better multiple touch performance, and mixed mode systems combine the strengths of both.
The nature of mutual capacitance measurements has been described above. Self capacitances CVS(i) are associated with vertical electrodes of index i where i=1, 2, 3, . . . M and self capacitances CHS(j) are associated with horizontal electrodes of index j where j=1, 2, 3, . . . N.
In the determination of the location of a touch using self-capacitance measurements, the X coordinate of the touch is determined from self-capacitances CVS(i) of vertical electrodes and the Y coordinate is determined from the self-capacitances CHS(j) of horizontal electrodes. Hence self-capacitances CVS(i) and CHS(j) of both vertical and horizontal electrodes are needed to determine the two-dimensional (x,y) coordinates of a touch.
The next three figures analyze what self-capacitance data is available to each of two ASICs for three different interconnect options. Interleaved connections are not only advantageous for mutual-mode as described above, but also advantageous for self-mode as explained below.
Various embodiments can be implemented, for example, using one or more well-known computer systems, such as computer system 2100 shown in
Computer system 2100 includes one or more processors (also called central processing units, or CPUs), such as a processor 2104. Processor 2104 is connected to a communication infrastructure or bus 2106. One or more processors 2104 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor that is a specialized electronic circuit designed to process mathematically intensive applications. The GPU may have a parallel structure that is efficient for parallel processing of large blocks of data, such as mathematically intensive data common to computer graphics applications, images, videos, etc. Computer system 2100 also includes user input/output device(s) 2102, such as monitors, keyboards, pointing devices, etc., that communicate with communication infrastructure 2106 through user input/output interface(s) 2102.
Computer system 2100 also includes a main or primary memory 2108, such as random access memory (RAM). Main memory 2108 may include one or more levels of cache. Main memory 2108 has stored therein control logic (i.e., computer software) and/or data. Computer system 2100 may also include one or more secondary storage devices or memory 2110. Secondary memory 2110 may include, for example, a hard disk drive 2112 and/or a removable storage device or drive 2114. Removable storage drive 2114 may be a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, tape backup device, and/or any other storage device/drive.
Removable storage drive 2114 may interact with a removable storage unit 2118. Removable storage unit 2118 includes a computer usable or readable storage device having stored thereon computer software (control logic) and/or data. Removable storage unit 2118 may be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and/any other computer data storage device. Removable storage drive 414 reads from and/or writes to removable storage unit 2118 in a well-known manner.
According to an exemplary embodiment, secondary memory 2110 may include other means, instrumentalities or other approaches for allowing computer programs and/or other instructions and/or data to be accessed by computer system 2100. Such means, instrumentalities or other approaches may include, for example, a removable storage unit 2122 and an interface 2120. Examples of the removable storage unit 2122 and the interface 2120 may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and/or any other removable storage unit and associated interface.
Computer system 2100 may further include a communication or network interface 2124. Communication interface 2124 enables computer system 2100 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference number 2128). For example, communication interface 2124 may allow computer system 2100 to communicate with remote devices 2128 over communications path 2126, which may be wired and/or wireless, and which may include any combination of LANs, WANs, the Internet, etc. Control logic and/or data may be transmitted to and from computer system 2100 via communication path 2126.
In an embodiment, a tangible apparatus or article of manufacture comprising a tangible computer useable or readable medium having control logic (software) stored thereon is also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 2100, main memory 2108, secondary memory 2110, and removable storage units 2118 and 2122, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 2100), causes such data processing devices to operate as described herein.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the disclosure. However, it will be apparent to one skilled in the art that specific details are not required in order to practice the disclosure. Thus, the foregoing descriptions of specific embodiments of the disclosure are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed; obviously, many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the disclosure and its practical applications, they thereby enable others skilled in the art to best utilize the disclosure and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following claims and their equivalents define the scope of the disclosure.
Based on the teachings contained in this disclosure, it will be apparent to persons skilled in the relevant art(s) how to make and use embodiments of the disclosure using data processing devices, computer systems and/or computer architectures other than that shown in
It is to be appreciated that the Detailed Description section, and not the Abstract section, is intended to be used to interpret the claims. The Abstract section may set forth one or more, but not all exemplary embodiments, of the disclosure, and thus, are not intended to limit the disclosure and the appended claims in any way.
The disclosure has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries may be defined so long as the specified functions and relationships thereof are appropriately performed.
It will be apparent to those skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus the disclosure should not be limited by any of the above-described exemplary embodiments. Further, the claims should be defined only in accordance with their recitations and their equivalents.
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
10503312, | Jan 18 2018 | ELO TOUCH SOLUTIONS, INC | Large PCAP screen with multiple touch controller ASICS with interleaved receiver connections |
9377905, | May 31 2011 | PARADE TECHNOLOGIES, LTD | Multiplexer for a TX/RX capacitance sensing panel |
9660646, | Mar 10 2013 | Apple Inc. | Multiple controllers for a capacitive sensing device |
9740352, | Sep 30 2015 | ELO TOUCH SOLUTIONS, INC | Supporting multiple users on a large scale projected capacitive touchscreen |
20100110040, | |||
20100156811, | |||
20120056662, | |||
20130015906, | |||
20130016051, | |||
20160098111, | |||
20160154531, | |||
20160202797, | |||
20160266679, | |||
20170010706, | |||
20170046007, | |||
20170090616, | |||
20170090644, | |||
20170168629, | |||
20180024665, | |||
20180188863, | |||
20190220131, | |||
EP2667287, | |||
EP2869168, | |||
WO2017201338, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jan 15 2018 | XU, YANSUN | ELO TOUCH SOLUTIONS, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 051204 | /0896 | |
Jun 13 2019 | ELO TOUCH SOLUTIONS, INC | ELO TOUCH SOLUTIONS, INC | ADDRESS CHANGE | 064571 | /0711 | |
Dec 06 2019 | Elo Touch Solutions, Inc. | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Dec 06 2019 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
Aug 21 2024 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Date | Maintenance Schedule |
Mar 02 2024 | 4 years fee payment window open |
Sep 02 2024 | 6 months grace period start (w surcharge) |
Mar 02 2025 | patent expiry (for year 4) |
Mar 02 2027 | 2 years to revive unintentionally abandoned end. (for year 4) |
Mar 02 2028 | 8 years fee payment window open |
Sep 02 2028 | 6 months grace period start (w surcharge) |
Mar 02 2029 | patent expiry (for year 8) |
Mar 02 2031 | 2 years to revive unintentionally abandoned end. (for year 8) |
Mar 02 2032 | 12 years fee payment window open |
Sep 02 2032 | 6 months grace period start (w surcharge) |
Mar 02 2033 | patent expiry (for year 12) |
Mar 02 2035 | 2 years to revive unintentionally abandoned end. (for year 12) |