[Dsg-hallb_magnets] Fast-DAQ time gaps- VT1 sent to EPICS first

[Nathan Baltzell]

I believe you have a limit on array length on the cRio's EPICS (and that's why went to 5 Hz instead of 1 Hz)?  

And I'd think longer arrays / faster updates would just exacerbate the gap problem.

-Nathan

----- Original Message -----
From: "Wesley Moore" <wmoore at jlab.org>
To: "Tyler Lemon" <tlemon at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org>, "Nathan Baltzell" <baltzell at jlab.org>
Sent: Wednesday, February 1, 2017 4:06:02 PM
Subject: RE: [Dsg-hallb_magnets] Fast-DAQ time gaps- VT1 sent to EPICS first

I believe having them separated is what it needed for creating the root data and post-processing. Same with the timestamp, it's of no use to be separate.  Nathan may have any opinion though. 
Wesley

-------- Original message --------
From: Tyler Lemon <tlemon at jlab.org> 
Date: 2/1/17  3:59 PM  (GMT-05:00) 
To: dsg-hallb magnets <dsg-hallb_magnets at jlab.org>, Nathan Baltzell <baltzell at jlab.org> 
Subject: [Dsg-hallb_magnets] Fast-DAQ time gaps- VT1 sent to EPICS first 

Hello Wesley, Nathan, and Ruben, 

As discussed in this morning's meeting, timestamps of the cRIO shared variables used to send data to EPICS confirms that VT1 is sent to EPICS first. 

After the KPP, it might be a good idea to look into changing how data is sent to EPICS from the Fast-DAQ cRIO. This could be sending all data in one array (as done with the PLC) or providing an additional time stamp from the cRIO. 

Best regards, 
Tyler