Using the Release 10 of the PAC Control IDE , what are considered best practices for sharing charts across multiple strategies?
We have 5 nearly identical pieces of equipment to control. The differences are minor enough that nearly all of the charts work on any equipment. There are some differences:
- Analog I/O scaling, and
- a few of option settings may be different. The option settings include things like time-out settings, flow and temperature setpoints, and flags indicating the presence of a specific equipment option.
Currently, we are doing this
- each equipment has its own strategy in its own directory.
- the charts are identical in each folder
- each equipment has its one option file that is specified in the control engine download options
- where a specific equipment item requires different code paths within a chart, an option setting (usually specified in the download options) is used in a decision block to specify the specific code path to be used for that option.
- during development, when we change a chart, we manually import the modified chart(s) into the corresponding charts in the other strategies.
Is this about as good as it gets?