Troubleshoot CEMAT @PG_C_MEASUR_STANDARD Script Errors in PCS 7 V9.0 SP3
For the reported WinCC Runtime message SCRIPT Execute Error in action ... @PG_C_MEASUR_STANDARD ... (null) (null) in PCS 7 V9.0 SP3 with CEMAT V9.0 SP2, first verify that the OS project contains the matching CEMAT WinCC files and inspect the affected faceplate/action using the project's supported engineering tools. Siemens' CEMAT V9.0 SP2 Engineering Manual documents updating the OS project with CematProjectUpdate.exe; it does not establish the cause or operational impact of this exact script message.
Table of Contents
- What the message establishes
- Check CEMAT files in the OS project
- Method: update the CEMAT WinCC project files
- If the error remains
- Expected result
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
What the message establishes
The source reports a WinCC System Log entry naming SCRIPT, Execute Error in action, @PG_C_MEASUR, the view @PG_C_MEASUR_STANDARD, and trailing (null) (null), with a corresponding server summary SCRIPT SRV02 ACTION ERROR. The source author reports PCS 7 V9.0 SP3 and CEMAT V9.0 SP2 for one installation. These fields identify a runtime script error associated with the named view, but the available Siemens documentation does not define those tokens or prove that the problem has no effect on all WinCC functionality.
Check CEMAT files in the OS project
The CEMAT V9.0 SP2 Engineering Manual says to update the WinCC OS project with the installed CEMAT files using CematProjectUpdate.exe. Its procedure copies CEMAT project files from the CEMAT installation into the corresponding OS project directories: GraCS, Library, PRT, and WScripts. The manual also identifies screen-resolution-dependent standard pictures that may be exchanged during the update.
This is a documented CEMAT project update procedure, not a confirmed repair for the particular action error. Use it when project review shows that the relevant OS project is missing or has stale CEMAT files; preserve project backup/change control and choose the destination OS project carefully.
Method: update the CEMAT WinCC project files
- Confirm that the engineering station and OS project use CEMAT V9.0 SP2 and the intended PCS 7/WinCC project version. Retain a recoverable OS-project backup before replacing library or picture files.
- On the engineering system, use the
CematProjectUpdate.exeprocedure documented for the installed CEMAT V9.0 SP2 package. Siemens' manual locates the tool under the CEMAT source directory (shown asD:\CEMAT_CSin that edition). - Set the source to the installed CEMAT source directory and the destination to the intended OS project directory. Review the listed subdirectories that the tool will copy:
GraCS,Library,PRT, andWScripts. - Select the project's configured screen resolution where applicable, then run the OS project update. The manual says each directory is copied to its corresponding OS project directory and the actions are recorded in a log.
- Review the tool log and verify the destination project received the intended files. Follow the PCS 7/WinCC engineering procedure for compiling and delivering the OS project to its runtime station; copying files to the engineering project does not by itself prove that the runtime station has received them.
- Reopen the process screen and the
C_MEASURfaceplate that previously generated the message. Review the WinCC system log for recurrence and verify the specific operator functions that matter to the plant.
If the error remains
If the CEMAT project files are current and the runtime error persists, collect the full System Log entry, exact screen/view and trigger sequence, WinCC/CEMAT version levels on engineering and OS stations, and whether the error reproduces on other OS stations. Compare the affected standard view and project contents with a known-good project/library copy under the site's controlled engineering process. Do not edit protected Siemens script logic or infer what the two (null) arguments mean without the action's documented interface. Escalate the exact error to Siemens when the matching project files do not resolve it.
Expected result
The documented CEMAT project update should place the selected release's CEMAT WinCC files into the specified OS project directories and create an update log. The available source does not confirm that this step clears the exact script error. Treat the original report that the message is sporadic and has no drastic effect as an observation, not as proof that alarms, faceplate behavior, or process visibility are unaffected.
Verification
Check the update log and confirm the intended OS project was the destination. Compile and deploy the OS project according to the site's installed PCS 7 release process. Then open the previously affected process picture, open the C_MEASUR faceplate's standard view, and confirm the relevant display and operator interactions. Check the WinCC System Log for the same SCRIPT Execute Error after the test. Record whether the message recurs and the exact configuration tested; absence during one test does not prove a permanent correction.
Limitations and Operational Precautions
The ticket does not provide the attached images, full action definition, OS project update history, or evidence showing what behavior fails when the message occurs. The CEMAT manual confirms the update tool and copied directories, but not that @PG_C_MEASUR_STANDARD or this script error is repaired by it. The statement that the error has no drastic effect is forum-reported and unverified. Avoid replacing standard project files or changing script actions without a backup and approval. If the error persists after restoring version-matched CEMAT project files, involve Siemens with the complete diagnostic and project version details.
Engineer FAQ
Does (null) (null) prove a specific missing tag or pointer? No. The supplied evidence does not establish what the two fields represent; inspect the action with version-appropriate tools or ask Siemens.
What is the CEMAT V9.0 SP2 documented OS-project update method? The Engineering Manual describes running CematProjectUpdate.exe from the CEMAT installation, selecting the source and OS-project destination, and copying the CEMAT WinCC directories into the project.
Does updating those files prove the script error is fixed? No. The manual documents project file synchronization, but not this exact WinCC runtime error. Verify the affected view and System Log after an approved update.
Technical References
- Siemens, Engineering Manual CEMAT V9.0 SP2, “Installation of a PCS 7 Project,” §3, “Update the WinCC Project with Cemat Functions,” printed p. 3-71. The official PDF was downloaded and read; it describes
CematProjectUpdate.exe, source/destination selection, copyingGraCS,Library,PRT, andWScripts, resolution-dependent picture exchange, and logging: https://cache.industry.siemens.com/dl/files/056/109768056/att_988285/v1/Cem_V90_Engineering_000_en.pdf
Related Articles
- Search IndustrialAutomation.net for CEMAT WinCC project updates
- Search IndustrialAutomation.net for PCS 7 WinCC script errors