Re: areadetector, extra IOC only for plugins

[Pete Jemian via Tech-talk <tech-talk at aps.anl.gov>]

Perhaps a screen view might help (using caQtDM screens).
https://anl.box.com/s/ws3w1rihw1xj3rup3xxyodsl0hwmn3lf

On 9/19/2023 10:19 AM, Heinz Junkes via Tech-talk wrote:
> I would be happy if someone here could enlighten me 😉
 Two IOCs are used in this example:

* `bdpad:` ADSimDetector with image and PVA plugins enabled
* `bdppva:` pvaDriver with image plugin enabled

The image data is created by the ADSimDetector IOC cam and published by both CA
(image plugin) and PVA (PVA plugin).  Publishing involves enabling the respective
plugins on the IOC.  Within each IOC, plugins receive image data (NTNDArray) via
an asyn port.  Between IOCs, image data is received as PVs (either ca or PVA).
The pvaDriver IOC subscribes to the PVA PV from the ADSimDetector IOC. The PVA
is where the pvaDriver IOC cam gets its image data.

Other area detector plugins are optional for this example.

Bottom left screen shows simulated sawtooth image generated by the ADSimDetector.

Next screen to the right shows the image as received by the pvaDriver IOC.

On the far right, the pvaDriver IOC "cam1" configuration shows, in the "pvaDriver"
section of the screen, where to enter the (PVA) PV name to be received as input.
This is the PV name published by the ADSimDetector IOC.

--
----------------------------------------------------------
Pete R. Jemian, Ph.D.                 <jemian at anl.gov>
Beam line Controls and Data Acquisition (BC, aka BCDA)
Advanced Photon Source,    Argonne National Laboratory
Argonne, IL  60439                    630 - 252 - 3189
-----------------------------------------------------------
      Education is the one thing for which people
         are willing to pay yet not receive.
-----------------------------------------------------------