C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How to Resolve the Parameter is Incomplete Error for IEPAR_STR in SIMATIC BATCH

How to Resolve the Parameter is Incomplete Error for IEPAR_STR in SIMATIC BATCH

To resolve the "Parameter is Incomplete" validation error when adding an IEPAR_STR (Interface Equipment Parameter for Strings) block to a Master Recipe in SIMATIC BATCH Control Center (BatchCC), configure a valid default string value and synchronize the parameter length between CFC and the BATCH Process Cell. Unlike numerical parameter blocks (IEPAR_REAL, IEPAR_DINT) that default to zero, SIMATIC BATCH recipe validation rejects uninitialized string parameters. In addition, the maximum string length defined on the AS block interface must match the data type definition in the BATCH Engineering catalog. The error is resolved by entering an explicit default string in the recipe step, aligning data type lengths, and executing a complete "Generate, Propagate, Merge, and Download" sequence.

Table of Contents

Mechanics of the IEPAR_STR Block in SIMATIC BATCH Architecture

SIMATIC BATCH coordinates recipe execution with controller automation through dedicated Interface Equipment Parameter (IEPAR) blocks:
- Parameter Types: Recipes exchange variables with the AS using typed interface blocks: IEPAR_REAL (floating-point setpoints), IEPAR_DINT (integer counters), IEPAR_BOOL (flags), and IEPAR_STR (alphanumeric text strings).
- Function of IEPAR_STR (FB111): Transfers text strings—such as lot identifiers, operator names, material barcodes, and quality control codes—between the BATCH Server and the controller's equipment phase (IEPH).
- Validation Strictness: When an engineer validates a Master Recipe in BatchCC, the BATCH validation engine inspects every parameter definition against the process cell database schema. If any mandatory attribute is unassigned or malformed, the recipe cannot be released.

Root Causes of the 'Parameter is Incomplete' Validation Error

The "Parameter is Incomplete" error on IEPAR_STR typically stems from one of three configuration oversights:

Configuration AreaFailure MechanismResolution PathUninitialized Default ValueThe recipe author added the string parameter to the recipe header or step but left the value field entirely null. SIMATIC BATCH treats a null string as an incomplete configuration.Enter an explicit default string (or space placeholder) in the recipe parameter properties.String Length DiscrepancyThe CFC block parameter defines a string length of 16 characters (STRING[16]), but the BATCH Data Type catalog defines the parameter as 32 characters (STRING[32]).Align string lengths identically across CFC, the BATCH catalog, and the recipe.Out-of-Sync Process CellThe block was added to CFC, but the BATCH engineering data was not updated via "Generate, Propagate, Merge", leaving BatchCC with an outdated type descriptor.Execute full BATCH data compilation and update the process cell in BatchCC.

Data Type Sizing and String Length Constraints

Handling string data in SIMATIC S7 and BATCH requires strict adherence to memory structures:
* S7 String Format: In STEP 7, a STRING data type contains a two-byte header: Byte 0 stores the maximum declared capacity, and Byte 1 stores the current actual length.
* Default Length: If an unconstrained STRING is declared in S7, it defaults to 254 bytes. SIMATIC BATCH standard equipment parameters typically restrict strings to 16, 32, or 64 characters to optimize communication telegram sizes over Industrial Ethernet.
* Delimiter Syntax: In BatchCC recipe parameter dialogs, strings should be entered as plain text without leading or trailing quotation marks (do not enter "MyText" or 'MyText'). BatchCC treats quotes as literal string characters rather than delimiters.

Method: Step-by-Step Parameter Configuration and Recipe Validation

Follow this procedure to configure IEPAR_STR correctly and clear the recipe validation error:

Step 1: Configure IEPAR_STR in CFC

  1. In SIMATIC Manager, open the CFC chart containing the target equipment phase (IEPH).
  2. Insert an instance of IEPAR_STR (FB111 from the SIMATIC BATCH library).
  3. Connect the output IEPAR_STR.E_STR to the corresponding technological input on the equipment phase block.
  4. In the block properties, assign an unambiguous parameter name (e.g., Lot_Number).
  5. Set the initial string value parameter (U_STR) to a valid default string (e.g., 'DEFAULT' or 'NONE').

Step 2: Update BATCH Engineering Data

  1. Select the multiproject root in SIMATIC Manager and open the SIMATIC BATCH engineering dialog.
  2. Execute the compilation pipeline in order:
    - Click Generate: Extracts the new parameter descriptor.
    - Click Propagate: Distributes the parameter schema across AS projects.
    - Click Merge: Merges the parameter into the unified process cell model.
    - Click Compile / Download: Download the updated BATCH engineering data to the BATCH Server.
  3. Perform a CFC Change Download to the AS controller in RUN mode.

Step 3: Update Process Cell in BatchCC

  1. Launch BatchCC on the engineering station or client.
  2. Select Process Cell -> Update Process Cell.
  3. Confirm that the process cell updates with 0 errors.
  4. Navigate to System -> Data Types -> Strings and verify that the parameter data type definition matches the declared length.

Step 4: Configure the Parameter in Master Recipe

  1. Open the target Master Recipe in the BatchCC Recipe Editor.
  2. Open the recipe step or recipe header properties where the string parameter is assigned.
  3. Select the parameter Lot_Number.
  4. In the Value field, enter a valid default string:
    - Enter EMPTY or PENDING (do NOT use quotes).
    - If the parameter is intended to be entered by the operator at runtime, ensure the option Operator editable at start is checked.
  5. Select Recipe -> Validate.
  6. Result: The validation window reports: Validation successful - 0 Errors, 0 Warnings.
  7. Select Recipe -> Release for Production.

Verification

To verify that the string parameter operates properly in runtime:
- In BatchCC, create a new batch order from the released master recipe.
- During batch order creation, observe the parameter dialog: verify that the operator prompt appears, pre-filled with the default string.
- Enter a test string (e.g., LOT-2026-A1) and release the batch.
- Start the batch: open the CFC chart in online Test Mode and monitor IEPAR_STR.ACT_STR.
- Confirm that the string LOT-2026-A1 is received by the AS controller and latched into the equipment phase DB.

Limitations and Operational Precautions

  • Special Character Restrictions: Avoid using non-ASCII characters, semicolons, or control characters in BATCH string parameters, as these can disrupt SQL database queries and CSV report generation.
  • Maximum Character Truncation: If an operator enters a string exceeding the maximum configured length in BatchCC, the input is truncated, potentially cutting off vital batch identification data.
  • Running Batch Protection: Do not modify IEPAR_STR block parameters or re-synchronize the process cell while an active batch is executing within that specific equipment phase.

Engineer FAQ

Can I leave the string value blank if it will be entered by an operator later?

SIMATIC BATCH validation requires an initial default value in the master recipe. If the value must be supplied by the operator, enter a placeholder default like ENTER_LOT and check "Editable by Operator".

Why did entering quotes around the text not solve the error?

BatchCC does not use programming language string delimiters. Entering "Text" causes BatchCC to literally store the quotation mark characters, which does not satisfy unassigned parameter constraints.

How many characters can IEPAR_STR support?

By default, standard IEPAR_STR supports strings up to 32 characters. Extended versions or custom structures can be configured up to 254 characters if supported by the S7 string buffer.

What is the difference between IEPAR_STR and IEPAR_DINT?

IEPAR_STR transfers alphanumeric text characters, whereas IEPAR_DINT transfers 32-bit signed integers. Use IEPAR_DINT whenever data consists purely of numerical values to minimize communication telegram overhead.

Technical References

  • Siemens Industry Online Support: SIMATIC BATCH Operating Manual (A5E38012658).
  • SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: SIMATIC BATCH).
  • SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Advanced Process Library Manual.
  • Siemens Support Guide: Configuring Equipment Parameters and Phases in SIMATIC BATCH.

Related Articles

Related Tags

  • SIMATIC BATCH
  • IEPAR_STR
  • Recipe Validation
  • BatchCC
  • Equipment Phases
  • Process Cell
  • Industrial Automation
20 respuestas