...
Within the IOC, a Data Source PV, e.g. an ai record from an IP330, is configured to provide specially time stamped scalar values to the BSA support within the same IOC.
...
- 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.
Data Receptor
When you create the BSA records, e.g.
dbLoadRecords("db/Bsa.db","DEVICE=TRIG:B34:EV05, ATRB=COUNTER")
the The BSA database defines a PV for feeding data from your Data Source to the rest of the BSA system. When configuring the BSA database, be sure the name matches the Data Source PV. The BSA internals depend on the PV names being composed of the same $(DEVICE) and $(ATRB) parts. It would cause confusion if the history buffers had a name that didn't correspond to the data in them.
