[Dsg-rtpc] [New Comment] MFC104 seems flaky

Brian Eng beng at jlab.org
Tue Mar 17 17:38:07 EDT 2020


That's fine. The login server is down now so I couldn't actually change anything.

I'll make changes if need be tomorrow.

Good luck with the new detector install!

________________________________________
From: Eric Christy <christy at jlab.org>
Sent: Tuesday, March 17, 2020 5:36 PM
To: Brian Eng; Sebastian Kuhn
Cc: dsg-rtpc at jlab.org; Bob Miller; JIWAN POUDEL; Mohammad Hattawy; Patrizia Rossi; Amrit Yegneswaran; Marc Mcmullen
Subject: Re: [New Comment] MFC104 seems flaky

Hi Brian,


I am not sure when Sebastian will be able to respond to your email as he and all other available BONuS personnel on site are in Hall B cabling up the new RTPC.


Regards,

Eric
________________________________
From: Brian Eng <beng at jlab.org>
Sent: Tuesday, March 17, 2020 4:41 PM
To: Sebastian Kuhn <kuhn at jlab.org>
Cc: dsg-rtpc at jlab.org <dsg-rtpc at jlab.org>; Bob Miller <rmiller at jlab.org>; Eric Christy <christy at jlab.org>; JIWAN POUDEL <jpoud001 at odu.edu>; Mohammad Hattawy <mohammad.hattawy at gmail.com>; Patrizia Rossi <rossi at jlab.org>; Amrit Yegneswaran <yeg at jlab.org>; Marc Mcmullen <mcmullen at jlab.org>
Subject: Re: [New Comment] MFC104 seems flaky

Ok, first go at this remotely ...

Someone should test this locally on the computer and report back. I didn't exercise the valve any as I wasn't sure what the state of the system was in.

There should now be a file called 'Target MFC' (not sure if extensions are hidden or not) in the same folder where the GUI is.

If you double click on it to launch it you should get a screen like the following:
[cid:4e3e6013-7f3e-4c24-a412-51a4060b8347]

This means it's running, if somehow it isn't it will look like the screenshot below (notice the extra bar at the top with the run button[arrow]) as well as the icon text, if so click on the run button
[cid:c86f98e7-86ef-4a20-a270-4721e9a0fd43]

Now that we're sure it is running click on the 'Initalize MB' button which should connect to the MFC and start updating the values, i.e. it will look like the screenshot below
[cid:4515a85a-e2bf-4c9c-a8af-f41e5be7ad4a]

Namely the information box at the top is now populated and all the information on the right side is as well. Note that the information box and the indicators next to it is only populated once when first connecting while the plot and indicators next to it should always be updating (some more obvious than others).

The 'Override' selection drop down has three choices: Normal, Open, and Closed. Normal means the valve position is based on what the set point is, the other 2 are self-explanatory.
[cid:6c0c884f-d365-4cb2-bc8e-f45d6270d46e]

If you want to update the information box (i.e. to see what the current gas is or get a current temperature reading) you'll need to click on the 'Close MB' button twice (once to stop plotting and another to close the connection) then 'Initialize MB'

When you're finished with the program click the 'Stop' button and close the program.

P.S. There is also an update time in ms in the bottom left, you can change this to suit your needs (I don't think I'd go below 50ms). It was hard to tell remotely if this value was okay or not, but the higher/slower the better as far not causing performance issues.
________________________________________
From: Sebastian Kuhn <kuhn at jlab.org>
Sent: Tuesday, March 17, 2020 11:41 AM
To: Brian Eng
Cc: dsg-rtpc at jlab.org; Bob Miller; Eric Christy; JIWAN POUDEL; Mohammad Hattawy; Patrizia Rossi; Amrit Yegneswaran; Marc Mcmullen
Subject: Re: [New Comment] MFC104 seems flaky

Please go ahead. Nobody is using the system right now, and you can logout anyone who is still logged in (probably me).

On Mar 17, 2020, at 11:25 AM, Brian Eng <beng at jlab.org<mailto:beng at jlab.org>> wrote:

I will start on setting up something that can from the same computer that has been used to control the target gas from. I'll need to login to test at some point, so if someone is logged in they'll temporarily be disconnected.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: running.PNG
Type: image/png
Size: 22059 bytes
Desc: running.PNG
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rtpc/attachments/20200317/3acea957/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not running.PNG
Type: image/png
Size: 22665 bytes
Desc: not running.PNG
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rtpc/attachments/20200317/3acea957/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: connected.PNG
Type: image/png
Size: 26095 bytes
Desc: connected.PNG
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rtpc/attachments/20200317/3acea957/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: override.PNG
Type: image/png
Size: 26655 bytes
Desc: override.PNG
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rtpc/attachments/20200317/3acea957/attachment-0011.png>


More information about the Dsg-rtpc mailing list