Experimental Physics and
Industrial Control System

Hi,

 

If I was doing this today I’d do it the way Mark described below (separate IOC, pvaDriver, dynamically setting the input PV name to the NDPluginPva of each camera), as you get the benefits of using the NTNDArray data type which greatly simplifies client configuration. Also, I would add any processing plugins in the separate IOC, linked to the output of the pvaDriver.

 

However, if you’re only using channel access then this is a solution I’ve used for years:

 

Setup a high level camera IOC with a subArray record, such like:

 

# ///

# /// subArray for high level user display.

# /// This has to be as big as the biggest detector

# ///

record(subArray, "$(S):Det:Array") {

  field(INP, "$(S):Det:Q1:Array1:ArrayData CP MS")      ß areaDetector stdArray plugin array PV name

  field(FTVL, "LONG")

  field(MALM, "$(MAX_SIZE)")

  field(NELM, "$(MAX_SIZE)")

  field(INDX, "0")

}

 

And setup several other records to hold the array size values (if the camera images are different sizes), to use in the client display widget:

 

# ///

# /// Several records to provide the sizes and scale of the array

# ///

record(longin, "$(S):Det:ArraySizeX") {

  field(INP, "$(S):Det:Q1:Array1:ArraySize0_RBV CP MS")

}

record(longin, "$(S):Det:ArraySizeY") {

  field(INP, "$(S):Det:Q1:Array1:ArraySize1_RBV CP MS")

}

 

(and more records if you need them)

 

Then use an mbbo to select which camera you want, and that triggers sseq records that write the INP link field names in each of the records above (including the CP MS link attributes).

 

The client screen just sees these high level records.

 

Cheers,

Matt