[Hallb-engineering] [New Logentry] Torus Alarm: METAL4K_DT_MAX

[Probir Ghoshal]

Ruben, Dave


This we have already addressed in the past and if I am not mistaking Brian E had his algorithm that sets the excitation current. The hardware (chassis) seemed to be working.

Rama, Bring and Nick can comment to get the last updated software and the result.


Regards


Probir



________________________________
From: Ruben Fair
Sent: Monday, January 7, 2019 8:04 AM
To: David Kashy; hallb-engineering at jlab.org; Nicholas Sandoval; Tyler Lemon; Probir Ghoshal
Subject: Re: [New Logentry] Torus Alarm: METAL4K_DT_MAX


Tyler, Nick, Probir,


Let me know what you think about this. I have also asked Rama to comment.


Ruben



________________________________
From: kashy at jlab.org <kashy at jlab.org>
Sent: Sunday, January 6, 2019 7:35:02 AM
To: hallb-engineering at jlab.org; Nicholas Sandoval; Tyler Lemon; Probir Ghoshal; Ruben Fair
Subject: [New Logentry] Torus Alarm: METAL4K_DT_MAX

Torus Alarm: METAL4K_DT_MAX <https://logbooks.jlab.org/entry/3641551>

  *   Edit<https://logbooks.jlab.org/entry/3641551/edit?destination=email/send>
  *   Delete<https://logbooks.jlab.org/entry/3641551/delete?destination=email/send>

Lognumber 3641551<https://logbooks.jlab.org/entry/3641551>. Submitted by kashy<https://logbooks.jlab.org/user/kashy> on Sun, 01/06/2019 - 07:31<https://logbooks.jlab.org/entries?start_date=1546774317&end_date=1546781517&book=HBLOG&book=HBTORUS>.

Logbooks:       HBLOG<https://logbooks.jlab.org/book/hblog> HBTORUS<https://logbooks.jlab.org/book/hbtorus>
Entry Makers:   kashy

Last night at 1/5/2019 at 22:39 there was a 5 second period where the signal went from 4.5K to 255K.

All signals that go into this this signal jumped at this time.
CCM_DT_MAX
CCM_USHR_DT
CCM_DSHR_DT

But only the first one above went to 255K.

A similar alarm went off this morning at1/6/2019 at 6:16
This time it was triggered by a quick step change from 4.5 to 43K on the USHR signal.

(Neither of these can be real temperature changes so it must be something in the instrumentation)
These were false alarms. Can we find a reason and stop it from happening?

Thanks
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/hallb-engineering/attachments/20190107/77ecaf10/attachment-0002.html>