<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Hi Marc,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thanks. Many of my requests were long term wants not short term needs. What I need in the short term to continue testing is a solution to the crashing. It's not a safety issue since the independent process controller is always active but it does make it difficult
to demonstrate stable performance. I have requested that the device be moved to the hall next week and I was hoping to have a few days of successful data stable at the desired set temperatures before then. We have already shown the system can get there but
haven't demonstrated long term performance. Do you have any ideas? Is there a remote way to reset the program?</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
-Don</div>
<div class="elementToProof">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Donald Jones</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hall A/C Staff Scientist</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jefferson Lab</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Newport News, VA</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dsg-halla_ecal <dsg-halla_ecal-bounces@jlab.org> on behalf of Marc Mcmullen via Dsg-halla_ecal <dsg-halla_ecal@jlab.org><br>
<b>Sent:</b> Monday, August 21, 2023 12:02 PM<br>
<b>To:</b> dsg-halla_ecal@jlab.org <dsg-halla_ecal@jlab.org><br>
<b>Subject:</b> Re: [Dsg-halla_ecal] heater controls</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hi Don,</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
We have reviewed your findings and are optimizing to the controls software. I'll send an update later this week with the software changes.</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Regards,</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Marc<br>
</div>
<div id="x_appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Donald Jones <jonesdc@jlab.org><br>
<b>Sent:</b> Monday, August 21, 2023 12:24 AM<br>
<b>To:</b> Marc Mcmullen <mcmullen@jlab.org>; Brian Eng <beng@jlab.org><br>
<b>Cc:</b> Jimmy Caylor <jcaylor@jlab.org><br>
<b>Subject:</b> heater controls</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div style="font-family:inherit; font-size:inherit; color:rgb(0,0,0); background-color:transparent">
Hi Marc, Brian,</div>
<div style="font-family:inherit; font-size:inherit; color:rgb(0,0,0); background-color:transparent">
I have been running the heater system since Thursday afternoon when we were given the go ahead again. I'd like to discuss a few things with you but since I have to report for jury duty tomorrow, that may have to wait. Instead I will start the conversation here. </div>
<div style="font-family:inherit; font-size:inherit; color:rgb(0,0,0); background-color:transparent">
A few things I have noticed:</div>
<div style="font-family:inherit; font-size:inherit; color:rgb(0,0,0); background-color:transparent">
<ul data-editing-info="{"orderedStyleType":1,"unorderedStyleType":1}">
<li style="list-style-type:disc">There is some weird behavior in the controls where if I change the setpoint on one zone it immediately affects the output of other zones on the same PID. I would not describe this as happening every time, but quite often. For
example, if I start by setting all three SM zones to the same temperature and then suddenly change one zone to a much higher temperature value than the others, often within a second or two, the other two zones will relax to very low output. This is well before
any real temperature increase could be felt by the other zones. It feels like there is cross-talk somehow between channels. I have also seen when I reset the value of one zone and leave the other two unchanged, that the other two just stop putting out any
power. I am imagining a loop with a shift register to cycle back the set values from the end of the previous loop to the start of the next and with one being changed, sometimes the other two are resetting to 0 or something like this. </li><li style="list-style-type:disc">The system has crashed 3 times since Thursday, The first time happened Friday when I was sitting at the terminal. The second time happened while I was absent on Saturday and the crystals had cooled down by 80 degrees before
I came back to check and found the issue. The last time it happened was tonight Sunday and when I came to check I found the system unresponsive and ~30 degrees hotter than the setpoints. So it's good to know it can freeze and go either way (hotter or colder).
Also, the only way I can restart it is by physically pushing the reset switch, which isn't going to work in the hall. I have been conservatively running the Omega setpoint much lower (250 degC) in case of a malfunction and it was at 246 tonight, so not all
that hot, but more than the usual 220-230.</li></ul>
<div>I shut it down since the crashes are too frequent. W<span style="background-color:transparent">e have to find a solution to the frequent crashes. Perhaps you already have ideas.</span></div>
<div>In addition to these issues, I have a few suggestions that I think would improve the program.</div>
</div>
<div style="font-family:inherit; font-size:inherit; color:rgb(0,0,0); background-color:transparent">
<ul data-editing-info="{"orderedStyleType":1,"unorderedStyleType":1}">
<li style="list-style-type:disc">Separate PID for each zone. We need more flexibility.</li><li style="list-style-type:disc">Make output of PID go from 0 to 100 and then set the output voltage to the square root of the PID output so that the output voltage scales with heater power not heater voltage. </li><li style="list-style-type:disc">We should average the PID output over many seconds before updating. Right now it updates every second and sometimes there are large swings from one second to the next. I suspect that these power supplies aren't built to manage
continuous adjustment thousands of times per hour with potentially large swings in current. I would think something like a 30 second update would be sufficient but we could make the number of seconds a control for more flexibility. I think the graphs and readbacks
should still update every second, but the voltage output should not. </li><li style="list-style-type:disc">The same applies to the software controlled relay. I have seen it turn on and off several times very quickly when it is close to the set threshold. Averaging the deltaT for 30 seconds before turning it back on or off makes sense.</li><li style="list-style-type:disc; color:rgb(0,0,0)"><span style="color:rgb(0,0,0); background-color:transparent">It would be nice to have the PID voltage output on separate graph from the temps</span><br>
</li></ul>
<div><span style="color:rgb(0,0,0); background-color:transparent">Let me know what you think. There will likely be more suggestions and we can discuss the ones I bring up here at a convenient time.</span></div>
<div><span style="color:rgb(0,0,0); background-color:transparent">-Don</span></div>
</div>
<div><br>
</div>
<div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Donald Jones</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hall A/C Staff Scientist</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Jefferson Lab</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Newport News, VA</div>
</div>
</div>
</div>
</body>
</html>