Where can I locate stored values for S+ Function Block Specs? Are spec values held in EBP project database tables?
I'm interested in locating function block configuration, including all the potential stored spec values, in an automated way reading raw configuration backups such as EBP project files.
I see Function Block configuration in the tables of the EBP project file except for the Spec 1, Spec 2, Spec 3, etc. values. Perhaps I'm just overlooking them here or they are located elsewhere?
My main purpose is for change tracking indications from periodically reading snapshots of the configuration values, but I do not want to require the processing of configuration by applications or reports.
I have faith users here have this data mining knowledge and any assistance would be greatly appreciated.
Voted best answer
Just to clarify, the function block spec values are ultimately sourced from the CLDs, where the function codes are configured and connected. The CLDs are then compiled to create the .CFG file which is then downloaded into the controller. The .CFG file is simply a compiled snapshot of the CLD configuration. Once the .CFG file is downloaded to the controller, the controller .CFG file block spec values can also theoretically be changed by tune and online configuration operations carried out on the controller, either from Composer or the HMI, and also without updating the CLDs. Whether or not the CLDs are updated to reflect these changes is largely down to site engineering workflows.
A couple of suggestions that do require Composer Harmony include...
The Composer CLD export of function code entities will export controller configuration(s) to an .mdb/.xls(x)/.csv file. Some of the older versions of the tool were a bit twitchy if there were more than 2 controllers per PCU so in this case the PCUs / modules may have to be exported one at a time. This will give you a snapshot of the configuration contained in the CLDs. From memory exporting to .mdb or .xls(x) does require the respective Office application to be installed but the .csv export work without any Office software installed.
Another option might be the GSLV (Global Save Load Verify) engine, which can automatically verify controller CFGs, CLDs or CFG files against each other and provide a traditional verify report. GSLV can be run from within Composer / Control Engineering or from command line / shortcut / scheduled task. With a bit of planning a reference CFG file can be verified against the current CFG, CLDs or controller CFG to provide incremental and differential verifies over time. The resulting verifies can then be processed as required.
Refer to the Primary Interface manual for your particular version of Composer for details on both items mentioned.
- In text, generated with each DBDOC build, so that you can study both changes in time and uncompiled CLD sheets that do not match the .CFG files
- In an SQLite database, on which you can run queries and reports
- Displayed on the graphical presentation of the CLD logic, in blocks that can be moved out of the way so you can see them
- Able to be validated against the contents of the running module
Of course, we could also mention that we check the projects for numerous undetected errors and warnings. Some of them will bite.
There are quite a few people on this site that use DBDOC at their plants. You can consult with me as geoff at gmcl.com and get much more detail, too.
Is there any plan for upgrade of Engineering? since version details are not mentioned here and based on the hint (EBP), it is old version of composer harmony. If you are upgrading to S+ Engineering 2.x, then you can easily extract the spec values using a query under DATA EDITOR. Also, in S+ Engineering 2.3 and S+ Operations 3.3 version onwards, we can compare the property differences between SPE and SPO values and sync with SPE.