<?xml-stylesheet type="text/xsl" href="https://emersonexchange365.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Setpoint Lead-Lag Question and&amp;#160;Answer</title><link>/services/b/weblog/posts/setpoint-lead-lag-question-and-160-answer</link><description>I wanted to share this question and answer on setpoint lead-lag, from the Mentoring Engineers discussion group in the Emerson Exchange 365 community. The question: …one of the options you recommend for eliminating overshoot at setpoint changes is using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator></channel></rss>