does this IOC support HDF5 file write?

[LeeYangLBLBCS]

Does this IOC have ability to write out HDF5 files?
The MEDM screen for "File format" only has two options:
TIFF
Invalid
Am I missing HDF5 plugin in the st.cmd file or this IOC does not work with it?

[MarkRivers]

There are 2 different ways that areaDetector can write files:

• Using the vendor's file writing capabilities
• Using areaDetector plugins

The Pilatus vendor file writer is limited to TIFF and CBF. The ADPilatus driver then reads the TIFF or CBF file, puts the data in an NDArray, and calls all registered plugins. The HDF5 plugin can then be used to write the NDArray to an HDF file. It is in the Plugins/File/HDF5 file menu.

[LeeYangLBLBCS]

The TIFF file write works, but the HDF pluggin does not. Does it need extra setup to connect to the Pilatus vendor's data?

this HDF window does not generate output file:

[MarkRivers]

The HDF5 plugin screen shows that it is not getting any NDArray callbacks. Array Counter, Array Size, and Time stamp are all 0.

It should be getting callbacks since you have Array Callbacks=Enable on the Pilatus screen, and the Array Port for the HDF5 plugin is PIL, which is correct.

Are there any error messages on the IOC console?

[LeeYangLBLBCS]

here is the last few lines of the iocshell terminal:
2024/11/07 21:42:30.361 NDPluginFile::doCapture: ERROR, must collect an array to get dimensions first
2024/11/07 21:42:31.576 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 21:42:41.564 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif
2024/11/07 21:42:53.136 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 21:42:54.272 NDPluginFile::doCapture: ERROR, must collect an array to get dimensions first
2024/11/07 21:42:55.126 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif
2024/11/07 21:48:00.957 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif
2024/11/07 21:48:11.532 NDPluginFile::doCapture: ERROR, must collect an array to get dimensions first
2024/11/07 21:48:13.925 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 21:48:24.313 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif
2024/11/07 21:49:39.427 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 21:49:40.065 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 21:49:40.425 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 21:49:40.717 NDPluginFile::writeInt32: ERROR, no valid array to write2024/11/07 22:49:54.571 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif
2024/11/07 22:53:50.202 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif

[MarkRivers]

2024/11/07 21:42:55.126 pilatusDetector::waitForFileToExist timeout waiting for file to be created /mnt/data531/20241107_LY_bluesky_test.tif

That is the problem. camserver has written the file, but the ADPilatus IOC is not able to read it back. Here is the likely cause of this problem:

• There is only a single "path" to the TIFF file. This path is used both by camserver to write the file, and by ADPilatus to read the file.
• If the IOC and camserver are running on the same computer this is not an issue, a single path will always work.
• However, if camserver and the IOC are running on different computers, then you may need to use soft links to make the path seen by camserver and the path seen by ADPilatus be the same.

This is documented in the description of NDFilePath here:
https://areadetector.github.io/areaDetector/ADPilatus/pilatusDoc.html#implementation-of-standard-driver-parameters