...
- TSE = -1 for a fast and simple PV, e.g. an IP330 analog input using I/O Intr and an external EVR trigger. The most recent beam code is used, so processing must complete in 8.33 ms
- TSE = -2 if device support will handle the time stamp. For example, device support code may call evrTimeGet at the beginning of processing, so it has the time stamp corresponding to when data was read even if processing that data takes longer than 8.33 ms
- TSE = an event code #. The time stamp for the most recent trigger for that event code will be used, even if processing takes longer than 8.33 ms. This can be used if data is not synchronized with the beam, but you want the time stamp to correlate with other data. If SCAN is also using an event code, make sure EVNT and TSE match.
- TSEL field set to the .TIME field of another BSA PV. This causes the PV to use the PV named in its TSEL field as the source of the timestamp.
- TSEL field set to the $(DEV)LSUB_EVSEL associated with the EVR trigger output going to your device. The LSUB_EVSEL PV contains the active event code for a trigger. When TSEL is set to the LSUB_EVSEL PV (NOTE: NOT the .TIME field) its value is written to the TSE field of your PV. The time stamp used is then the one associated with the time stamp, just like setting "TSE = event code #" directly, but it automatically changes if a different event code is selected.
Data Receptor
When you create the BSA records, e.g.
...
