From beng at jlab.org  Mon May  1 17:28:08 2023
From: beng at jlab.org (Brian Eng)
Date: Mon, 1 May 2023 21:28:08 +0000
Subject: [dsg-hallb_ltcc] LTCC rack in the hall
In-Reply-To: <C0FE0287-E4BE-4A77-AD06-FEB907A68605@jlab.org>
References: <PH8PR09MB9278A47E472415FAE87E7F24CB6E9@PH8PR09MB9278.namprd09.prod.outlook.com>
 <C0FE0287-E4BE-4A77-AD06-FEB907A68605@jlab.org>
Message-ID: <MN2PR09MB55156EE2C84C89C36F262734A56E9@MN2PR09MB5515.namprd09.prod.outlook.com>

So it was actually the UPS beeping. The GFCI on the outlet in the picture had tripped which meant the UPS wasn't getting any AC power. Since the UPS died the whole rack lost power. I reset the outlet and everything came back on.

Is that what we actually want though?

Since the cRIO already went down I'm in the process of upgrading it to a newer software version as well as adding S2 and S6 DP to EPICS.
________________________________
From: Brian Eng <beng at jlab.org>
Sent: Monday, May 1, 2023 3:12 PM
To: Denny Insley <dinsley at jlab.org>
Subject: Re: LTCC rack in the hall

That should be the only thing that could beep, but I go down and take a look here shortly.

On May 1, 2023, at 2:30 PM, Denny Insley <dinsley at jlab.org> wrote:

Hi Brian,

    Just a heads up because I don't know who else would be interested but, the UPS in the Hall LTCC rack is beeping. I believe, unless you have a beeper on something else in there.

Thanks,
Denny

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_ltcc/attachments/20230501/13e95424/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ltcc_outlet.jpg
Type: image/jpeg
Size: 762127 bytes
Desc: ltcc_outlet.jpg
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_ltcc/attachments/20230501/13e95424/attachment-0001.jpg>

From dinsley at jlab.org  Mon May  1 18:58:35 2023
From: dinsley at jlab.org (Denny Insley)
Date: Mon, 1 May 2023 22:58:35 +0000
Subject: [dsg-hallb_ltcc] LTCC rack in the hall
In-Reply-To: <MN2PR09MB55156EE2C84C89C36F262734A56E9@MN2PR09MB5515.namprd09.prod.outlook.com>
References: <PH8PR09MB9278A47E472415FAE87E7F24CB6E9@PH8PR09MB9278.namprd09.prod.outlook.com>
 <C0FE0287-E4BE-4A77-AD06-FEB907A68605@jlab.org>
 <MN2PR09MB55156EE2C84C89C36F262734A56E9@MN2PR09MB5515.namprd09.prod.outlook.com>
Message-ID: <PH8PR09MB9278D5F239D57DE12EB78924CB6E9@PH8PR09MB9278.namprd09.prod.outlook.com>

Yeah I would think that to be a no. GFCI's in a system circuit sounds like a problem.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: dsg-hallb_ltcc <dsg-hallb_ltcc-bounces at jlab.org> on behalf of Brian Eng via dsg-hallb_ltcc <dsg-hallb_ltcc at jlab.org>
Sent: Monday, May 1, 2023 5:28:08 PM
To: dsg-hallb_ltcc at jlab.org <dsg-hallb_ltcc at jlab.org>
Subject: Re: [dsg-hallb_ltcc] LTCC rack in the hall

So it was actually the UPS beeping. The GFCI on the outlet in the picture had tripped which meant the UPS wasn't getting any AC power. Since the UPS died the whole rack lost power. I reset the outlet and everything came back on.

Is that what we actually want though?

Since the cRIO already went down I'm in the process of upgrading it to a newer software version as well as adding S2 and S6 DP to EPICS.
________________________________
From: Brian Eng <beng at jlab.org>
Sent: Monday, May 1, 2023 3:12 PM
To: Denny Insley <dinsley at jlab.org>
Subject: Re: LTCC rack in the hall

That should be the only thing that could beep, but I go down and take a look here shortly.

On May 1, 2023, at 2:30 PM, Denny Insley <dinsley at jlab.org> wrote:

Hi Brian,

    Just a heads up because I don't know who else would be interested but, the UPS in the Hall LTCC rack is beeping. I believe, unless you have a beeper on something else in there.

Thanks,
Denny

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_ltcc/attachments/20230501/747ef450/attachment.html>