Hi Peter,
I looked at your simDetector log file, and you are loading the FFT plugin OK.
It looks like from your log file that the FFT error message is actually part of a comment in your startup script. I don’t see how this can be a real error message, since no asyn ports have been created yet at that point in the startup
script.
Ø
# Do not set EPICS_CA_MAX_ARRAY_BYTES to a value much larger than that required, because EPICS Chan2018/11/16 17:08:38.996 NDPluginDriver::connectToArrayPort Error calling pasynManager->connectDevice to array port FFT1 address
0, status=3, error=asynManager:connectDevice port FFT1 not found
Ø
nel Access actually
Mark
From: Mark Rivers
Sent: Monday, November 19, 2018 9:15 AM
To: 'Heesterman, Peter J' <[email protected]>
Subject: RE: ADSimDetector and ADURL - runtime issues with FFT and HDF5
Hi Peter,
Ø
st.cmd in ADSimDetector hasn’t been updated to reflect module paths – in particular lines like
Ø
dbLoadRecords("$(ADCORE)/db/simDetector.template","P=$(PREFIX),R=cam1:,PORT=$(PORT),ADDR=0,TIMEOUT=1")
Ø
where the file is no longer in ADCore.
You did not say what version of ADSimDetector you are using. I think it must be quite old, because you say that st.cmd contains that dbLoadRecords command. However, st.cmd in iocSimDetector actually just contains these 2 lines:
corvette:simDetectorIOC/iocBoot/iocSimDetector>more st.cmd
< envPaths
< st_base.cmd
That change was done a year and a half ago in this commit:
************************
commit d71513f61d27528a9cb06b6962e090d2579299be
Author: Mark Rivers <[email protected]>
Date: Thu Jun 29 11:28:06 2017 -0500
Change to allow normal st.cmd or st.cmd.linux or st.cmd.windows
************************
Ø
When I run the sim detector and try to visualise with ImageJ, I get green on both 13SIM1:image1 and 13SIM1:image2.
Ø
But, I don’t get any image displayed for either.
Have you looked for error messages in the ImageJ log window? This problem is often due to the fact that one has not set EPICS_CA_MAX_ARRAY_BYTES environment variable correctly on both the IOC process and the ImageJ process.
Ø
I note an error:
Ø
NDPluginDriver::connectToArrayPort Error calling pasynManager->connectDevice to array port FFT1 address 0, status=3, error=asynManager:connectDevice port FFT1 not found.
Ø
Could my (b) have anything to do with this error?
Ø
I understand that image2 would be the FFT of the simulated data generated for image1?
Have you updated your commonPlugins.cmd from EXAMPLE_commonPlugins.cmd recently? The FFT plugin was added to EXAMPLE_commonPlugins.cmd in May 2017. Does your simDetector IOC create an FFT plugin?
This error is not causing your problem with seeing the images unless you are telling NDStdArrays to get its data from FFT1.
For your HDF5 problems please run “h5dump –H filename”, which prints a dump of the HDF5 file header information. I just created an HDF5 file using simDetector, containing 10 images saved in Stream mode. I then ran h5dump on the file and
saved to the attached text file.
Mark
I’m seeking to use these modules with HDF5 data archiving.
Accordingly, I’ve been looking at the iocHDF5Test within ADSimDetector, and focused on test5.sh.
I’m working with an Ubuntu 18.04 VM.
areaDetector and ADCore R3-3-2
There are some issues that I need to raise:
a. st.cmd in ADSimDetector hasn’t been updated to reflect module paths – in particular lines like
dbLoadRecords("$(ADCORE)/db/simDetector.template","P=$(PREFIX),R=cam1:,PORT=$(PORT),ADDR=0,TIMEOUT=1"), where the file is no longer in ADCore.
This is easily corrected. Actually, I believe st_base.cmd from iocSimDetector can just be used.
b. When I run the sim detector and try to visualise with ImageJ, I get green on both 13SIM1:image1 and 13SIM1:image2.
But, I don’t get any image displayed for either.
NDPluginDriver::connectToArrayPort Error calling pasynManager->connectDevice to array port FFT1 address 0, status=3, error=asynManager:connectDevice port FFT1 not found.
Could my (b) have anything to do with this error?
I understand that image2 would be the FFT of the simulated data generated for image1?
d. I am able to create a HDF5 file (for either ADSimDetector or ADURL) as requested by the test5.sh script (I cloned the logic of this for the ADURL module).
These files are large (>~100MB), and clearly contain the simulated and URL data, respectively.
I’m able to open the file(s) with the hdfview application (after closing the IOC, to avoid any file write/read share issues).
But, I’m unable to view any of the data because there are no attribute nodes under the ‘test5_001.h5’ root, in the viewer.
Viewing the ‘properties’ on the ‘test5_001.h5’ node in hdfview, shows no attributes and no datasets.
I am able to visualise data from the ADURL module, quite normally.
What is it that I’m missing?