BEGIN:VCALENDAR VERSION:2.0 PRODID:IEEE vTools.Events//EN CALSCALE:GREGORIAN BEGIN:VTIMEZONE TZID:America/Los_Angeles BEGIN:DAYLIGHT DTSTART:20240310T030000 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:PDT END:DAYLIGHT BEGIN:STANDARD DTSTART:20241103T010000 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:PST END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20240421T020552Z UID:789ECFB9-5888-4802-9C87-50B454B02067 DTSTART;TZID=America/Los_Angeles:20240417T174500 DTEND;TZID=America/Los_Angeles:20240417T194500 DESCRIPTION:Being fresh out of grad school (FOOGS) in 1988\, I reacted to P ID controllers in the usual way for young Ph.D. recipients: with a certain “hands-off” smugness. Yet\, as the years in industry wore on\, I kept encountering these ubiquitous devices in practice and had to learn to dea l with them\, understand them\, and roll my own. What I found led me to co nsider PIDs\, not as a separate art from advanced methods\, but as a funda mental building block which can be used as part of most controllers\, simp le or advanced. It seemed that – at least in the mechatronics world – PIDs were considered too simple for much interest in academia while practi cing engineers didn’t seem to care why they were working. In the process world\, where PIDs studied far more\, the issues and methods of mechatron ic PIDs seemed like obscure corner cases. Depending upon the teaching text \, issues of sampling and digital representation may have been completely omitted. There were other surprises. While PIDs were almost universal and standard\, they were almost never unified or standardized. Furthermore\, w hat seemed to limit performance was not the structure of the controller it self\, but the lack of accurate system/process models based on repeated ph ysical system measurements. Finally\, the mechatronic and process PID goal s and foibles were not that different once one considered the different sy stem\, time constant\, and measurement constraints. We will discuss these issues with the goal of getting a more unified view of PIDs across our app lication domains. We will provide a handful of common PID forms and show h ow they are related\, so that we can approach any PID structure with the s ame analytical approach. We will finally look forward to how PIDs can be u sed\, not only as a fundamental teaching tool for explaining control outsi de of our research circles\, but as a critical component for advanced cont rol methods. As the great Paul Simon might say\, “Mama don’t take my P ID away.”\n\nSpeaker(s): Dr. Danny Abramovitch \, \n\nAgenda: \n5:45 - 6 :15 : Networking and light dinner\n\n6:15 - 7:15 : Talk and Q&A\n\n7:15 - 7:45 : Networking\n\nRoom: SCDI - 2116\, Bldg: Sobrato Campus for Discover y and Innovation - SCDI\, 500 El Camino Real \, Santa Clara \, Californi a\, United States\, 95053 LOCATION:Room: SCDI - 2116\, Bldg: Sobrato Campus for Discovery and Innovat ion - SCDI\, 500 El Camino Real \, Santa Clara \, California\, United St ates\, 95053 ORGANIZER:mkhanbaghi@scu.edu SEQUENCE:18 SUMMARY:Unintentional Expertise: How the Necessity of Working with PID Cont rollers Across Multiple Domains Fundamentally Improved My Understanding of Control Theory and Practice URL;VALUE=URI:https://events.vtools.ieee.org/m/415806 X-ALT-DESC:Description: <br /><p class="MsoNormal" style="text-align: justi fy\; tab-stops: 0in\;"><span style="font-size: 12pt\; font-family: arial\, helvetica\, sans-serif\;">Being fresh out of grad school (FOOGS) in 1988\ , I reacted to PID controllers in the usual way for young Ph.D. recipients : with a certain &ldquo\;hands-off&rdquo\; smugness.<span style="mso-space run: yes\;">&nbsp\; </span>Yet\, as the years in industry wore on\, I kept encountering these ubiquitous devices in practice and had to learn to dea l with them\, understand them\, and roll my own.<span style="mso-spacerun: yes\;">&nbsp\; </span>What I found led me to consider PIDs\, not as a sep arate art from advanced methods\, but as a fundamental building block whic h can be used as part of most controllers\, simple or advanced.<span style ="mso-spacerun: yes\;">&nbsp\; </span>It seemed that &ndash\; at least in the mechatronics world &ndash\; PIDs were considered too simple for much i nterest in academia while practicing engineers didn&rsquo\;t seem to care why they were working.<span style="mso-spacerun: yes\;">&nbsp\; </span>In the process world\, where PIDs studied far more\, the issues and methods o f mechatronic PIDs seemed like obscure corner cases.<span style="mso-space run: yes\;">&nbsp\; </span>Depending upon the teaching text\, issues of sa mpling and digital representation may have been completely omitted.<span s tyle="mso-spacerun: yes\;">&nbsp\; </span>There were other surprises.<span style="mso-spacerun: yes\;">&nbsp\; </span>While PIDs were almost univers al and standard\, they were almost never unified or standardized.<span sty le="mso-spacerun: yes\;">&nbsp\;</span>Furthermore\, what seemed to limit performance was not the structure of the controller itself\, but the lack of accurate system/process models based on repeated physical system measur ements. Finally\, the mechatronic and process PID goals and foibles were n ot that different once one considered the different system\, time constant \, and measurement constraints.<span style="mso-spacerun: yes\;">&nbsp\; < /span>We will discuss these issues with the goal of getting a more unified view of PIDs across our application domains. We will provide a handful of common PID forms and show how they are related\, so that we can approach any PID structure with the same analytical approach. We will finally look forward to how PIDs can be used\, not only as a fundamental teaching tool for explaining control outside of our research circles\, but as a critical component for advanced control methods.<span style="mso-spacerun: yes\;"> &nbsp\; </span>As the great Paul Simon might say\, &ldquo\;Mama don&rsquo\ ;t take my PID away.&rdquo\;</span></p>\n<p class="MsoNormal" style="text- align: justify\; tab-stops: 0in\;"><span style="font-size: 10.0pt\;">&nbsp \;</span></p>\n<p class="MsoNormal" style="text-align: justify\; tab-stops : 0in\;"><span style="font-size: 10.0pt\;">&nbsp\;</span></p><br /><br />A genda: <br /><p>5:45 - 6:15 : Networking and light dinner</p>\n<p>6:15 - 7 :15 : Talk and Q&amp\;A</p>\n<p>7:15 - 7:45 : Networking</p> END:VEVENT END:VCALENDAR