<html><body><div>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. <div><br></div><div>Wesley</div><br><br>-------- Original message --------<br>From: Tyler Lemon <tlemon@jlab.org> <br>Date: 2/1/17 3:59 PM (GMT-05:00) <br>To: dsg-hallb magnets <dsg-hallb_magnets@jlab.org>, Nathan Baltzell <baltzell@jlab.org> <br>Subject: [Dsg-hallb_magnets] Fast-DAQ time gaps- VT1 sent to EPICS first <br><br></div><br><div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hello Wesley, Nathan, and Ruben,<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>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.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>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.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Best regards,<br data-mce-bogus="1"></div><div>Tyler<br data-mce-bogus="1"></div></div></div></body></html>