Ø
Doesn't that include my 'new' parameters/PVs?? And if that is the case, then surely the new .template file would also be involved in that build process.
No, your new PVs are simply new instances of existing record types that are defined in the dbd file. The template file is what creates an instance of a record, so that is all you need. The dbd file contains the definition of the record
type, it does not create a record instance.
Mark
Thanks Mark,
I haven't yet got this completely clear in my mind... You say that "simDetectorApp.dbd will be created for you automatically by the build system. It contains the definitions of
all records in your application ...". Doesn't that include my 'new' parameters/PVs?? And if that is the case, then surely the new .template file would also be involved in that build process.
Sorry if I'm being obtuse!
Phil
On 06/01/2016 17:07, Mark Rivers wrote:
Hi Phil,
-
To add my 'new' parameters/PVs, do I only need to create a new .template file and then do dbLoadRecords... for that file during the IOC startup sequence? (I.e. am I correct that I do not need to change the equivalent of simDetectorApp.dbd, which is very long
but doesn't seem to contain anything specific to the ADExample camera?).
You are correct that you just need to create a new .template file. The equivalent of simDetectorApp.dbd will be created for you automatically by
the build system. It contains the definitions of all records in your application, the symbols for all device and driver support, etc.
-
Am I also correct that, the database aspects of the 'new' parameters/PVs are not involved in the build process? (Conversely, the simDetectorApp.dbd analog
is involved).
Yes, that is correct. As I said above the simDetectorApp.dbd file is created for you based on simDetectorSupport.dbd and commonDriverMakefile.
-
What is the difference between a .dbd file and a .template file?
As a simplification, the .dbd file contains the definitions of the records, the .template file contains the values for specified record fields.
Mark
I'm developing an areaDetector driver and IOC. The code and folder structure is based on ADExample.
In addition to the 'standard' parameters/PVs associated with an areaDetector IOC, I need some additional parameters/PVs that are specific to my camera etc. I also need to 'override' some of the standard definitions (due to limited data type support, no colour
support etc.).
Questions:
-
To add my 'new' parameters/PVs, do I only need to create a new .template file and then do dbLoadRecords... for that file during the IOC startup sequence? (I.e. am I correct that I do not need to change the equivalent of simDetectorApp.dbd, which is very long
but doesn't seem to contain anything specific to the ADExample camera?).
-
Am I also correct that, the database aspects of the 'new' parameters/PVs are not involved in the build process? (Conversely, the simDetectorApp.dbd analog
is involved).
-
What is the difference between a .dbd file and a .template file?
Thanks,
Phil
--
Pixel Analytics is a limited company registered in England. Company number:
7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP
--
Pixel Analytics is a limited company registered in England. Company number:
7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP