As the previous figure shows, if iFIX security has not been enabled or if the user account has the necessary application feature, the Recipe Builder examines the recipe for errors. The following figure provides a flowchart of the steps the Recipe Builder performs before uploading a recipe.
Examining a Recipe for Errors During an Upload
As you can see, this process is similar to the steps taken when downloading a recipe. For example, just as with downloading, the Recipe Builder examines the database to ensure the specific blocks exist.
Similarly, the Completion Status field is updated when the upload process begins. The Completion Status Values table describes the possible values and their meaning.
Should the Recipe Builder detect an error, it displays an error message box with the following text:
Precheck of recipe recipe
completed with x database errors
You can display these errors by selecting the View button on the message box. When you select this button, the Precheck Error dialog box appears and displays a list of errors.
Common upload precheck errors include an active upload interlock or an attempt to upload from a tagname that does not exist. To correct these, or any other errors, you must cancel the upload first. For additional information about handling precheck errors, refer to the section Understanding Audit Trail and Error File Messages.
NOTE: If the Recipe Builder encounters precheck errors for the upload or download interlock, the Item No. field in the Precheck Error List dialog box is left blank for that block. To correct the error for either interlock, open the database and make the necessary changes or change the interlock with the Advanced Options dialog box.
