Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Sat, 27 Feb 2021 05:28:12 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 11RDIHch026466; Sat, 27 Feb 2021 08:18:52 -0500 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 11RDIGGN026463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 27 Feb 2021 08:18:16 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 11RDIDQX025567 for ; Sat, 27 Feb 2021 08:18:16 -0500 Received: from oc11expo31.exchange.mit.edu (18.9.4.104) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sat, 27 Feb 2021 08:17:44 -0500 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo31.exchange.mit.edu (18.9.4.104) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sat, 27 Feb 2021 08:18:15 -0500 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.100) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sat, 27 Feb 2021 08:18:15 -0500 Received: from MWHPR13CA0010.namprd13.prod.outlook.com (2603:10b6:300:16::20) by BL0PR0102MB3377.prod.exchangelabs.com (2603:10b6:207:1e::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.33; Sat, 27 Feb 2021 13:18:13 +0000 Received: from CO1NAM11FT016.eop-nam11.prod.protection.outlook.com (2603:10b6:300:16:cafe::8a) by MWHPR13CA0010.outlook.office365.com (2603:10b6:300:16::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.9 via Frontend Transport; Sat, 27 Feb 2021 13:18:11 +0000 Received: from mail-ej1-f52.google.com (209.85.218.52) by CO1NAM11FT016.mail.protection.outlook.com (10.13.175.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3890.19 via Frontend Transport; Sat, 27 Feb 2021 13:18:11 +0000 Received: by mail-ej1-f52.google.com with SMTP id g5so19509512ejt.2 for ; Sat, 27 Feb 2021 05:18:11 -0800 (PST) Received: by 2002:ab4:9c4d:0:0:0:0:0 with HTTP; Sat, 27 Feb 2021 05:18:08 -0800 (PST) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sat, 27 Feb 2021 05:18:08 -0800 Subject: [EE] Monitoring/Logging a PID controller, SLB4848 Thread-Topic: [EE] Monitoring/Logging a PID controller, SLB4848 Thread-Index: AdcNDGXBN9Fe2ysrSOmB/mMs7xXQEw== Message-ID: List-Help: List-Subscribe: , List-Unsubscribe: , Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.218.52 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.52; helo=mail-ej1-f52.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=o7HrIcahvl4liuHPFVffBi35z8z56TqjhPF+BhLZwo4=; b=QGG0yY1aBUvmVYvVPXcBKubiUTPVjDmNtc+U4LI86Al8mmnXGDioY45HLyJuxnbICb e8vY2Vp9Z/DzJwXrTtsYH6nTdN3Gx2bwVWEifGH3dngNdtPtsZFJRF1QmHuGVLdHzRBv ATOnoXkTx6lNb5ZF4CpGEcrxrJVYRez3c+sNu5jLI5AuTThB/L9flLtFOO3MX5QRcf6S UYsYLrKPzZ0meDhjZHjfWQgmV9HZ+rHmXpgQeOdaEpmJSxDfEkstPWchOzj++JksP+Bv pBJwuK40vUE/T6Y8X4nM6dfpDq1ZFhBXttbeJi2CBs7wjIKjVjcGCn9y9+mc3CX+gGt5 CZ3g== authentication-results: spf=pass (sender IP is 209.85.218.52) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a17:907:2d8e:: with SMTP id gt14mr8143047ejc.325.1614431889461; Sat, 27 Feb 2021 05:18:09 -0800 (PST) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi everyone, For fun, I am controlling the temperature of a unused room with a SOLO Basic SLB4848 PID temperature controller from AutomationDirect. Tuning the controller has proven to be harder than it looks due to the long time constant of the room. For instance, a change in setpoint or tuning parameter can take several days to fully play out. The room in question is a (possibly drafty and poorly insulated) unused bedroom. In my case, to artificially increase the difficulty of this exercise, I am using an RTD to monitor air temperature 1 foot above the floor. The PID controller is driving an electric radiator that heats the room by convection. While I am sure that I could make things significantly easier on myself if I changed the system configuration (adding a fan, elevating the sensor) - I'd prefer to leave the system as is. I would like to monitor or log the input and/or output of this PID controller. The input is temperature (RTD resistance), the output is duty cycle (12V to soild state relay)/average power supplied the electric heater. While I could rig up an arduino, I was wondering if there were any off the shelf solutions. In particular, some multimeters do logging functions. I was also wondering if anyone on the list had any experience with said multimeters or other tools. And if they had any advice on monitoring/logging said system. Regards, Jason White --=20 Jason White --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .