-
Notifications
You must be signed in to change notification settings - Fork 0
external heater_profile program does not stop when requested #490
Comments
Since we use |
If user requests exit, then heater should be stopped. |
T96 needs to get a signal for |
Incoming Linkam code from apstools has temperature that includes a configurable It would be a good idea to add unit tests of that stop method to apstools test suite. See BCDA-APS/apstools#618 |
Linkam 1500 is connected., can be run and controlled. Try not to run too long at higher temperatures, at most 300C for 10-30 minutes is fine. |
Test T96 ( |
WHen user sets a new setpoint, they expect the heating power to be set to ON as a consequence. |
This is the |
In commit a727500 , the program https://github.com/APS-USAXS/ipython-usaxs/blob/a727500496e28db95c782e80c36579af9c7fb591/user/heater_profile.py#L224-L244 Complete heater plan, uninterruptedFull execution of the heater plan as shown in the log file:
Interrupted runWhen the stop bit is set early, the profile holds at temperature and exits with heater power on. Here's the first part of the log file:
Externally, user requests stop by setting the bit (in a separate console): bash-4.2$ caput 9idcLAX:bit14 0
Old : 9idcLAX:bit14 ON
New : 9idcLAX:bit14 OFF The log file continues ...
|
The background program does not seem to stop when bit is raised. I tried manually in GUI display and from bps.mv(terms.HeaterProcess.linkam_trigger, 1) and the pulse is still going. I assume the process must stop so next time we start it, with potentially different parameters to run, it will reread its configuration and follow proper temperature trajectory.
Originally posted by @jilavsky in #482 (comment)
The text was updated successfully, but these errors were encountered: