[Dsg-rich] [EXTERNAL] Re: [New Logentry] RICH compressor ON after maintenance

Tue Oct 8 17:03:55 EDT 2019

Hi Tyler,
We need to test the second compressor (N2) any way independently of the compressor N1 performance.
So, I suggest to connect the compressor N2 to the RICH detector.
Thanks,
Valery

From: Tyler Lemon <tlemon at jlab.org>
Date: Tuesday, October 8, 2019 at 16:51
To: Valery Kubarovsky <vpk at jlab.org>, Marco Mirazita <Marco.Mirazita at lnf.infn.it>
Cc: "dsg-rich at jlab.org" <dsg-rich at jlab.org>, Marco Contalbrigo <mcontalb at fe.infn.it>, Patrizia Rossi <rossi at jlab.org>
Subject: Re: [Dsg-rich] [EXTERNAL] Re: [New Logentry] RICH compressor ON after maintenance

Hi Valery,

To establish a naming convention for the RICH compressors since there are two of them:

  *   Compressor 1 is the compressor that has run in Hall B for previous experimental runs, was serviced recently by Hall B Engineering, and was turned on yesterday.

  *   Compressor 2 is the other compressor currently sitting unused and without power also on the top deck of the Forward Carriage.
If you want to see how the Compressor 2 behaves, we can plan to switch to and test Compressor 2.

If after the switch to Compressor 2, we see the same behavior as in April 2018, it may mean that Compressor 1 needs to be serviced beyond what anyone other than Atlas Copco can do.

Considering this, it may be a good idea to plan to optimize the settings for Compressor 2 and also the air-cooling panel. Anything that can be done to limit the time the compressor is running or the number of times it has to switch on or off will only serve to extend the life of the compressor.

Best regards,
Tyler

________________________________
From: Valery Kubarovsky <vpk at jlab.org>
Sent: Tuesday, October 8, 2019 4:23 PM
To: Tyler Lemon <tlemon at jlab.org>; Marco Mirazita <Marco.Mirazita at lnf.infn.it>
Cc: dsg-rich at jlab.org <dsg-rich at jlab.org>; Valery Kubarovsky <vpk at jlab.org>; Marco Contalbrigo <mcontalb at fe.infn.it>; Patrizia Rossi <rossi at jlab.org>
Subject: Re: [Dsg-rich] [EXTERNAL] Re: [New Logentry] RICH compressor ON after maintenance

Hi Tyler,

Please take a look to the attached report dated on April 11, 2019.

Page 2 presented the compressor performance from April 4, 2018 to April 10, 2019.

As you see, we noticed the significant degradation of it.

I hoped that the service that was done this year will improve the situation.

However, it looks like it did not. We may get a serious problem in the coming fall run.

We can try another compressor to compare with the old one.

Regards,

Valery

From: Dsg-rich <dsg-rich-bounces at jlab.org> on behalf of Tyler Lemon <tlemon at jlab.org>
Date: Tuesday, October 8, 2019 at 13:36
To: Marco Mirazita <Marco.Mirazita at lnf.infn.it>
Cc: "dsg-rich at jlab.org" <dsg-rich at jlab.org>
Subject: Re: [Dsg-rich] [EXTERNAL] Re: [New Logentry] RICH compressor ON after maintenance

Hi Marco,

Is there a set schedule for the tests where the compressor is needed? We can plan to have the compressor turned back on in time for that if there is.

Looking at the archived compressor data since it has been turned on and running steadily, we can see that the compressor is not doing its typical "saw-tooth" pattern that we saw this past April. All other cooling parameters are similar to previous experimental runs.

Attached are plots of archived data: one from the past ~24 hours, and one from about one year ago in September 2018. The one from September 2018 shows the typical "saw-tooth" pattern we expect, but the one from the past 24 hours does not.

The only difference between the two plots is the ambient pressure is higher (411 inches-H2O vs 408 inches-H2O) in the one from September 2018, but I am unsure if this is a big enough difference to cause the saw-tooth pattern to not occur.

Best regards,

Tyler

________________________________

From: Marco Mirazita <Marco.Mirazita at lnf.infn.it>
Sent: Tuesday, October 8, 2019 12:04 PM
To: Tyler Lemon <tlemon at jlab.org>
Cc: dsg-rich at jlab.org <dsg-rich at jlab.org>
Subject: [EXTERNAL] Re: [Dsg-rich] [New Logentry] RICH compressor ON after maintenance

Hi Tyler,
I completed this first test on the RICH (elog
https://logbooks.jlab.org/entry/3733786) and the detector is now off.
I would ask you to turn the compressor also off, unless you need to make
some further test.
The compressor on and electronics off is a condition we want to avoid,
because it generates an increase of the humidity inside the RICH.
Thank you,
Marco

Il 2019-10-07 20:20 tlemon at jlab.org ha scritto:
> RICH COMPRESSOR ON AFTER MAINTENANCE [1]
>
>        * Edit [2]
>        * Delete [3]
>
>  Lognumber 3733741 [1]. Submitted by tlemon [4] on Mon, 10/07/2019 -
> 14:16 [5].
>
>                LOGBOOKS:
>                RICH [6]
>
>                ENTRY MAKERS:
>                ambrown, campero, mealer
>
> The compressor in the RICH air-cooling system has been turned on after
> maintenance on and replacement of the buffer tank PT.
>
> All compressor settings are the same as during the spring physics run:
>  Compressor internal on-off settings: on at 104 psi; off at 113 psi
> (highest output range allowable on compressor)
>  Airflow 1: 500 slm
>  Airflow 2: 400 slm
>
> The new PT installed on the buffer tank appears to match the pressure
> indicated by the buffer tank's local pressure gauge. Because of this,
> the PT reading may be a little different than before.
>
> Since the cooling system is back online, RICH electronics can now be
> powered.
>
>
> Links:
> ------
> [1] https://logbooks.jlab.org/entry/3733741
> [2] https://logbooks.jlab.org/entry/3733741/edit?destination=email/send
> [3]
> https://logbooks.jlab.org/entry/3733741/delete?destination=email/send
> [4] https://logbooks.jlab.org/user/tlemon
> [5]
> https://logbooks.jlab.org/entries?start_date=1570468581&end_date=1570475781&book=RICH
> [6] https://logbooks.jlab.org/book/rich
>
> _______________________________________________
> Dsg-rich mailing list
> Dsg-rich at jlab.org
> https://mailman.jlab.org/mailman/listinfo/dsg-rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rich/attachments/20191008/eb4239f8/attachment-0002.html>