<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>LPC MicrocontrollersのトピックLPC804 evk touch: drift and sudden unexpected jumps</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2251251#M59027</link>
    <description>&lt;P&gt;I'm using the demo touch shield w/ 5 pads and 5 LEDs.&lt;/P&gt;&lt;P&gt;In order to detect a touch event, I continuously read the touchpad (based on the "capt_basic_continuous" demo from the LPCExpresso SDK). I average over 5 readouts for "current" values, and over 300 for "baseline" values. I then subtract "current" from "baseline" to get relative potential, usually within 0/-1 (idle) to +30 (firm touch).&lt;/P&gt;&lt;P&gt;Once I detect at least one pad going above a predefined threshold (around +10), the one with the highest relative value is registered as being touched. I then stop correcting the baseline until all pads fall below the threshold value, which is my criteria for "back to idle" at - which point I deregister the touch and resume updating baseline values.&lt;/P&gt;&lt;P&gt;For instance, at idle I may see raw values of 644/643, 619/618, 636/636, 651/650, 590/590 - which correspond to -1, -1, 0, -1, 0. On touch, these may rise to e.g. +24, +7, +11, +6, +2 - indicating that pad 0 is being touched. Once finger is removed, these go back to about the same average values (idle).&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This works well for short-time runs.&lt;/EM&gt; It accounts for the slow drift I see in the baseline over time.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;However, over longer runs (hours) something happens to the board that I don't understand&lt;/STRONG&gt; - if I touch a pad after not touching it for a while (hours), suddenly the readouts change &lt;EM&gt;drastically&lt;/EM&gt;&amp;nbsp;and alter the baseline long-term without giving me a chance to adjust, leading to a "stuck" touchpad.&lt;/P&gt;&lt;P&gt;For example, I'm seeing a readout of say 643 current / 643 baseline on pad 0. The normal behaviour when I touch pad 0 is that it falls to about 620 current, which leads to a diff value of +23 on detection on that pad.&lt;/P&gt;&lt;P&gt;But after a few hours and no touch events, this behaviour changes and when I touch e.g. pad 0, suddenly I see values of -6, +37, +29, +30, +24. The software still manages to catch that I touched pad 0... but once I release it, I then have: -39, +29, +19, +20, +15 - 4/5 of which are now above the predefined threshold of +10.&lt;/P&gt;&lt;P&gt;This indicates that the baseline has shifted quite dramatically when I touched the touchpad, and since 4/5 pads now register as "touching" - I no longer have the chance to readjust. Thus, the keypad is stuck in "being touched" mode, as it will no longer register "idle" (since the new idle is a huge distance away).&lt;/P&gt;&lt;P&gt;What am I doing wrong? What hardware behaviour/phenomenon am I not accounting for? Am I reading too fast? Too slow? Too few samples?&lt;/P&gt;&lt;P&gt;I'm currently using a clock divider of 7 (should be about 2.14 MHz), with a poll count of 9.&lt;/P&gt;</description>
    <pubDate>Fri, 28 Nov 2025 13:08:26 GMT</pubDate>
    <dc:creator>Egon_Freeman</dc:creator>
    <dc:date>2025-11-28T13:08:26Z</dc:date>
    <item>
      <title>LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2251251#M59027</link>
      <description>&lt;P&gt;I'm using the demo touch shield w/ 5 pads and 5 LEDs.&lt;/P&gt;&lt;P&gt;In order to detect a touch event, I continuously read the touchpad (based on the "capt_basic_continuous" demo from the LPCExpresso SDK). I average over 5 readouts for "current" values, and over 300 for "baseline" values. I then subtract "current" from "baseline" to get relative potential, usually within 0/-1 (idle) to +30 (firm touch).&lt;/P&gt;&lt;P&gt;Once I detect at least one pad going above a predefined threshold (around +10), the one with the highest relative value is registered as being touched. I then stop correcting the baseline until all pads fall below the threshold value, which is my criteria for "back to idle" at - which point I deregister the touch and resume updating baseline values.&lt;/P&gt;&lt;P&gt;For instance, at idle I may see raw values of 644/643, 619/618, 636/636, 651/650, 590/590 - which correspond to -1, -1, 0, -1, 0. On touch, these may rise to e.g. +24, +7, +11, +6, +2 - indicating that pad 0 is being touched. Once finger is removed, these go back to about the same average values (idle).&lt;/P&gt;&lt;P&gt;&lt;EM&gt;This works well for short-time runs.&lt;/EM&gt; It accounts for the slow drift I see in the baseline over time.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;However, over longer runs (hours) something happens to the board that I don't understand&lt;/STRONG&gt; - if I touch a pad after not touching it for a while (hours), suddenly the readouts change &lt;EM&gt;drastically&lt;/EM&gt;&amp;nbsp;and alter the baseline long-term without giving me a chance to adjust, leading to a "stuck" touchpad.&lt;/P&gt;&lt;P&gt;For example, I'm seeing a readout of say 643 current / 643 baseline on pad 0. The normal behaviour when I touch pad 0 is that it falls to about 620 current, which leads to a diff value of +23 on detection on that pad.&lt;/P&gt;&lt;P&gt;But after a few hours and no touch events, this behaviour changes and when I touch e.g. pad 0, suddenly I see values of -6, +37, +29, +30, +24. The software still manages to catch that I touched pad 0... but once I release it, I then have: -39, +29, +19, +20, +15 - 4/5 of which are now above the predefined threshold of +10.&lt;/P&gt;&lt;P&gt;This indicates that the baseline has shifted quite dramatically when I touched the touchpad, and since 4/5 pads now register as "touching" - I no longer have the chance to readjust. Thus, the keypad is stuck in "being touched" mode, as it will no longer register "idle" (since the new idle is a huge distance away).&lt;/P&gt;&lt;P&gt;What am I doing wrong? What hardware behaviour/phenomenon am I not accounting for? Am I reading too fast? Too slow? Too few samples?&lt;/P&gt;&lt;P&gt;I'm currently using a clock divider of 7 (should be about 2.14 MHz), with a poll count of 9.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 13:08:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2251251#M59027</guid>
      <dc:creator>Egon_Freeman</dc:creator>
      <dc:date>2025-11-28T13:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2251259#M59028</link>
      <description>&lt;P&gt;Im using SDK version 25.06.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 13:18:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2251259#M59028</guid>
      <dc:creator>Egon_Freeman</dc:creator>
      <dc:date>2025-11-28T13:18:48Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2253323#M59036</link>
      <description>&lt;P&gt;Apologies the late reply,&lt;/P&gt;
&lt;P&gt;Could you please confirm that the temperature of the device those not increase between your first reading and the last?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Dec 2025 15:37:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2253323#M59036</guid>
      <dc:creator>carlos_o</dc:creator>
      <dc:date>2025-12-02T15:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2253350#M59037</link>
      <description>This can happen over several hours, but also within an hour even. As far as I can tell, the chip is not warming up at all. The ambient temperature remains the same, give or take normal daily variations. I have it on my table, I'm prototyping. Any increase/decrease would be impossible to spot without measuring equipment.&lt;BR /&gt;&lt;BR /&gt;Also, when I touch the touchpads - they seem to return to their original readings, so it looks like it's drifting until I touch it, at which point it stabilises back to normal. If I were to guess, it kinda looks like it's accumulating charge.</description>
      <pubDate>Tue, 02 Dec 2025 15:57:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2253350#M59037</guid>
      <dc:creator>Egon_Freeman</dc:creator>
      <dc:date>2025-12-02T15:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2253356#M59038</link>
      <description>&lt;P&gt;This is what I'm currently doing:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LPC804_1.jpg" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/368262iB9E148E262148325/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LPC804_1.jpg" alt="LPC804_1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The device will need to work under a sticker, so that's what I'm simulating. I also have I2C attached.&lt;/P&gt;&lt;P&gt;I also replaced the pins with longer ones. Would that make a significant difference?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LPC804_2.jpg" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/368263iE98413F67F58F3C4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LPC804_2.jpg" alt="LPC804_2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;You will also notice that I switched one of the lines (YH/ACMP_14). I reassigned them in the mux, of course. I needed P0_7 for a different purpose here (the extra red cable) and it was the most immediately available to me. The capacitor was replaced with an identical value on the ACMP_14 line (where the DNP resistor would have gone).&lt;/P&gt;</description>
      <pubDate>Tue, 02 Dec 2025 16:04:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2253356#M59038</guid>
      <dc:creator>Egon_Freeman</dc:creator>
      <dc:date>2025-12-02T16:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2254522#M59040</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/251436"&gt;@Egon_Freeman&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The performance of the touch pad is mainly determined by the PCB design and the power supply source.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;So, could you confirm that the power supply is always working at the same value? Any variations on it could affect.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Dec 2025 21:33:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2254522#M59040</guid>
      <dc:creator>carlos_o</dc:creator>
      <dc:date>2025-12-03T21:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2254591#M59041</link>
      <description>&lt;P&gt;I'm currently working off of my PC's USB supply, so the supply is as stable as the USB line.&lt;/P&gt;&lt;P&gt;But would that explain why the floor value &lt;EM&gt;drops after I touch it&lt;/EM&gt; (within &lt;EM&gt;a second&lt;/EM&gt;), and begins slowly climbing again?&lt;/P&gt;&lt;P&gt;I also &lt;EM&gt;don't&lt;/EM&gt; see spontaneous drops. It's &lt;EM&gt;always&lt;/EM&gt; climbing. Shouldn't I expect variable floor (ups and downs) that would follow the voltage changes instead?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Dec 2025 22:43:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2254591#M59041</guid>
      <dc:creator>Egon_Freeman</dc:creator>
      <dc:date>2025-12-03T22:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: LPC804 evk touch: drift and sudden unexpected jumps</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2257449#M59053</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/251436"&gt;@Egon_Freeman&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you confirm that it is possible replicate the behavior you are experiencing with the example without modification?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 22:04:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC804-evk-touch-drift-and-sudden-unexpected-jumps/m-p/2257449#M59053</guid>
      <dc:creator>carlos_o</dc:creator>
      <dc:date>2025-12-08T22:04:04Z</dc:date>
    </item>
  </channel>
</rss>

