[Dsg-hallc_nps] [EXTERNAL] NPS LED/VLD controller specs/information/summary

Mon Feb 13 10:07:14 EST 2023

Hi Aaron.

There have been updates since this last email.  I have added 
descriptions for PVs to control the VLD and channels.

The IOC is running on nps-vme4 with
   PORT=vme4
and Slots indicated with e.g. (slot 17)
   R=VLD17

e.g. ModuleID:
   vme4VLD17:ModuleID

I'm admittedly inexperienced with EPICS drivers.  I will need more input 
on what the Controls GUI requires to function to proceed much further 
with development.

There are examples scripts to operate a single module with calibration 
pulse mode, and to modify the square waveform parameters.

On 19-Jan-23 1:52 PM, Bryan Moffit wrote:
> Hi Aaron.
> 
> I am out until Feb 1st.
> 
> I will try to add an explanation of the PVs.
> 
> 
> On 19-Jan-23 12:16 PM, Aaron Brown wrote:
>> Hi Bryan et al,
>>
>> Just wanted to follow up with regards to the LED controls programming.
>> We have finished the layout of the control GUI.
>> Brian and I have gone over the information in the Github.
>> Is there any additional documentation detailing exactly what the PVs 
>> control.
>> What is not obvious is if the pulse frequency is hard coded in the PV 
>> and exactly what channels are controlled by a PV.
>> Is there a newer version beyond this beta version?
>>
>> -- Aaron
>> ------------------------------------------------------------------------
>> *From:* Bryan Moffit <moffit at jlab.org>
>> *Sent:* Monday, December 5, 2022 7:57 AM
>> *To:* Aaron Brown <ambrown at jlab.org>; Brad Sawatzky <brads at jlab.org>; 
>> dsg-hallc_nps at jlab.org <dsg-hallc_nps at jlab.org>
>> *Cc:* Brian Eng <beng at jlab.org>; William Gu <jgu at jlab.org>; Chris 
>> Cuevas <cuevas at jlab.org>; Robert Michaels <rom at jlab.org>
>> *Subject:* Re: [EXTERNAL] NPS LED/VLD controller 
>> specs/information/summary
>> I've pushed a 'beta' version of the vld-epics driver to github:
>>
>> https://github.com/JeffersonLab/vld-epics 
>> <https://github.com/JeffersonLab/vld-epics>
>>
>> It has read/write support to the VLD parameters, but does not yet
>> include 'automated' specific procedure support (bleaching, calibration
>> pulse).
>>
>> I'm starting to code up that procedure support into the vld library
>> (which has also been updated).  We ought to talk about specifics for the
>> bleaching / calibration pulse functionality and driver hooks to your UI.
>>
>> On 22-Nov-22 5:36 PM, Aaron Brown wrote:
>>> Hi Brad,
>>>
>>> Brian will be on vacation from 11/24/2022 until 01/03/2023.
>>> He will begin working on the control scripts that utilize the 
>>> existing Linux drivers and is confident that this can be completed by 
>>> early January 2023.
>>> With regards to the "Beta quality GUI", the EPICS drivers would need 
>>> to be completed before we could finish this.
>>> The layout of the GUI is done, we just need the PVs before we can 
>>> move to the testing/debugging phase.
>>> for the EPICS drivers, it would be a good idea to see if someone from 
>>> the FE/DAQ group could complete the task.
>>>
>>> Happy Thanksgiving!
>>>
>>> -- Aaron
>>> ------------------------------------------------------------------------
>>> *From:* Brad Sawatzky <brads at jlab.org>
>>> *Sent:* Monday, November 21, 2022 6:42 PM
>>> *To:* Bryan Moffit <moffit at jlab.org>; dsg-hallc_nps at jlab.org 
>>> <dsg-hallc_nps at jlab.org>
>>> *Cc:* Brian Eng <beng at jlab.org>; Aaron Brown <ambrown at jlab.org>; 
>>> William Gu <jgu at jlab.org>; Chris Cuevas <cuevas at jlab.org>; Robert 
>>> Michaels <rom at jlab.org>
>>> *Subject:* [EXTERNAL] NPS LED/VLD controller specs/information/summary
>>> After recent discussions with Bryan and William, I volunteered to send
>>> out a status/summary on the NPS LED/VLD needs for the near (Dec/Jan)
>>> and medium term (Feb/Mar).
>>>
>>>
>>> - Operational specs for the LED pulser are in William's directories.
>>>     - His software libraries and test code can be found here:
>>>          /group/da/distribution/coda/Hardwaremanual/VLD/
>>>       or from the CODA web page.  The test software can be accessed from
>>>          /daqfs/home/jgu/Triggersoftware/trigger.c, VLDtestN functions.
>>>     There are docx files in the /group directory with specs and 
>>> technical
>>>     details.  Ideally we would be running the software under linux 
>>> (intel
>>>     vme computer), so any vxworks specific code should be updated to
>>>     compile in that environment.
>>>     - I am attaching what I think is the most recent spec document for
>>>       easy access:  'VLD.docx'
>>>
>>> - A Control/GUI requirements summary is attached as a text file.
>>>     - See: 'LED-GUI-summary-21Nov2022.txt'
>>>
>>> - Here is a link to some (intel controller) development code from Bryan
>>>     Moffit: 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_vld&d=DwIDAw&c=CJqEzB1piLOyyvZjb8YUQw&r=TkJUDpm1-rWCci4nhe47n5XMOLWvRg1TNSqSgPyxyhs&m=1N3fMPIfm78FoxmXp_mXreXU8E0U2i30VAPa6A-PqDvhIBy5Wm1U9gzMBHv6iWyH&s=B6Fs97LKHZhH97IC2bajCCDXfhExhHaLYIvGerKATkM&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_vld&d=DwIDAw&c=CJqEzB1piLOyyvZjb8YUQw&r=TkJUDpm1-rWCci4nhe47n5XMOLWvRg1TNSqSgPyxyhs&m=1N3fMPIfm78FoxmXp_mXreXU8E0U2i30VAPa6A-PqDvhIBy5Wm1U9gzMBHv6iWyH&s=B6Fs97LKHZhH97IC2bajCCDXfhExhHaLYIvGerKATkM&e=> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_vld&d=DwIDAw&c=CJqEzB1piLOyyvZjb8YUQw&r=TkJUDpm1-rWCci4nhe47n5XMOLWvRg1TNSqSgPyxyhs&m=1N3fMPIfm78FoxmXp_mXreXU8E0U2i30VAPa6A-PqDvhIBy5Wm1U9gzMBHv6iWyH&s=B6Fs97LKHZhH97IC2bajCCDXfhExhHaLYIvGerKATkM&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_vld&d=DwIDAw&c=CJqEzB1piLOyyvZjb8YUQw&r=TkJUDpm1-rWCci4nhe47n5XMOLWvRg1TNSqSgPyxyhs&m=1N3fMPIfm78FoxmXp_mXreXU8E0U2i30VAPa6A-PqDvhIBy5Wm1U9gzMBHv6iWyH&s=B6Fs97LKHZhH97IC2bajCCDXfhExhHaLYIvGerKATkM&e=>>
>>>
>>>
>>> ---------------------------------------------
>>> Near Term Requirements (ie. late-Dec/early-January)
>>> ---------------------------------------------
>>> - We don't need a full working GUI, but we do need a clear, student-
>>>     accessible way to run specific tests.
>>>     * I am imagining a set of pre-compiled, special-case binaries or
>>>       script(s) that are run from a command-line running on the VME
>>>       contoller(s)
>>>
>>> - The scripts should be able to do the following:
>>>     A.  Turn all LED on in bleach mode
>>>       * This should also set the Trg_out NIM ouput logic HI *first*
>>>         and that needs to be tied into the HV interlock circuit.
>>>
>>>     B.  Pulse one or more specified LEDs when a pulse is seen on the VLD
>>>         Trg/Clk input.
>>>         - The list of LEDs to be activated, pulse characteristics, 
>>> etc can
>>>           either be hardcoded, or read-in via a config file.  Doesn't 
>>> have
>>>           to be perfect, just needs to work.  We can fine-tune later.
>>>
>>>
>>> ---------------------------------------------
>>> 'Beta' quality GUI (Feb, early-March)
>>> ---------------------------------------------
>>> - NPS installation begins this spring -- that will come very soon!
>>>
>>> * We will need at least a 'beta' quality (ie. feature complete, but may
>>>     be buggy) GUI by Feb/early-March so we can test and fix bugs before
>>>     the systems is disassembled and moved to the Hall.  It will be a 
>>> while
>>>     before it is working again in the Hall and we definitely do not want
>>>     to leave testing this critical system to the summer.
>>>
>>> -- Brad
>>>
>>> -- 
>>> Brad Sawatzky (he/him), PhD <brads at jlab.org> -<>- Jefferson 
>>> Lab/SciComp/F272
>>> Ph: 757-269-5947  -<>-  Fax: 757-269-5235  -<>- Pager: 
>>> brads-page at jlab.org
>>> The most exciting phrase to hear in science, the one that heralds new
>>>     discoveries, is not "Eureka!" but "That's funny..."   -- Isaac 
>>> Asimov