| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [EXTERNAL] Lakeshore 336/360: how do I read the temperature |
| From: | "Pearson, Matthew R. via Tech-talk" <[email protected]> |
| To: | "Specht, Eliot" <[email protected]> |
| Cc: | "[email protected]" <[email protected]> |
| Date: | Tue, 14 Jan 2020 23:12:10 +0000 |
Also, forgot to mention: > > should work, but this returns zero for all four indices. I think that the IOC has provisions (which I haven’t been able to follow) for assigning different sensors to different channels; do I need to do some assignments before I can read temperatures? > > The database logic does link the output channels with input sensors, but it does this based on what’s configured on the controller so we don’t need to worry about it. The only reason this is done in the database logic is to change which temperature input link is used for the put_callback logic for each output (so that we’re waiting for the correct temperature to reach the setpoint when blocked via a put_callback). Cheers, Matt