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

How to Fix Missing Signal Assignments in SIMIT Chart Template Imports

How to Fix Missing Signal Assignments in SIMIT Chart Template Imports

In SIMIT Simulation (V8.0, V8.1, and higher), an import table preview that displays signal replacements correctly but generates chart instances with empty, unassigned signals is caused by duplicate template chart definitions residing across both Global Templates and Project Templates libraries, or by active communication couplings locking the tag table during instantiation. When duplicate templates exist, SIMIT's preview parser evaluates the global template while the generation engine binds to the local project template lacking the placeholder mappings. Consolidating templates into the Project Templates library, removing global duplicates, and disconnecting couplings during import resolves the issue.

Table of Contents

SIMIT Template Instantiation and Placeholder Architecture

SIMIT Simulation provides automated engineering tools to generate thousands of simulation components (such as valves, motors, transmitters, and piping networks) from spreadsheet data tables.

The instantiation workflow relies on:
1. Chart Templates: Standardized SIMIT charts created in the template library containing graphical blocks and dynamic signal placeholders enclosed in curly brackets (e.g., {TAG}, {SIGNAL_IN}, {FEEDBACK_OPEN}).
2. Import Tables: Excel or tab-delimited text files mapping individual instance names to concrete PLC I/O signals, memory bits, and plant area parameters.
3. Instantiation Engine: SIMIT reads the spreadsheet, presents a preview table showing string replacements, and generates concrete chart instances across the simulation workspace.

Root Cause Analysis for Blank Signal Bindings After Import

Engineers frequently encounter a confusing anomaly in SIMIT:
* In the Import Preview dialog, every placeholder replacement appears flawless, showing green matching indicators and correct tag assignments.
* After clicking Finish / Import, the newly generated simulation charts appear in the project tree, but all signal connections are blank and empty, requiring tedious manual reconnection.

Primary Root Causes

  • Template Namespace Collisions: SIMIT maintains two distinct template repositories: Global Templates (available to all projects on the workstation) and Project Templates (local to the specific .simit project). If a template chart (e.g., VlvL) exists in both repositories with slight differences in internal placeholder GUIDs or parameter tags, SIMIT parses the Global template during preview calculation but resolves the Project template during physical instantiation, discarding unmapped signals.
  • Trailing Whitespace in Spreadsheet Tokens: Hidden spaces or carriage returns in Excel column headers or cells (e.g., "{TAG }" instead of "{TAG}") cause string matching to fail silently during the generation phase.
  • Active Simulation Couplings: If SIMIT has an active online coupling (such as PLCSIM, Virtual Controller, or OPC) open in the background, the global tag dictionary is locked against dynamic structure insertion, resulting in unlinked signal blocks.

Step-by-Step Remediation and Import Procedure

To resolve missing signal assignments and execute a clean template import:

Step 1: Consolidate Template Repositories

  1. In SIMIT, open the Task Card on the right side and select Templates.
  2. Expand both Project Templates and Global Templates.
  3. Check for duplicate template chart names (e.g., VlvL, MotL, AnaInput).
  4. If a template exists in Global Templates, copy it to Project Templates, then delete or rename the duplicate from Global Templates to eliminate namespace ambiguity.
  5. Ensure the active project references exclusively the local Project Templates.

Step 2: Validate Placeholder Syntax and Clean Delimiters

  1. Open the template chart in Project Templates.
  2. Double-click each signal block (e.g., Input, Output, Global Connector) and verify placeholder strings:
    * Use clean syntax without leading or trailing spaces: {Signal_Name}.
    * Verify case sensitivity matches the Excel spreadsheet column headers exactly.
  3. In SIMIT Import Settings, enable the option:
    * 'Remove placeholders with empty replacement'. This ensures unassigned tokens are flagged immediately rather than silently discarded.

Step 3: Disconnect Simulation Couplings Prior to Import

  1. In SIMIT Project Navigation, select Couplings (e.g., PLCSIM Advanced, Virtual Controller, or PRODAVE).
  2. If the simulation is running or coupled, click Disconnect / Deactivate.
  3. Close any external PLC simulator connections.

Step 4: Re-execute Table Import

  1. Right-click the target chart folder in SIMIT and select Import -> Instantiation of templates....
  2. Select your validated Excel table.
  3. Review the preview pane to ensure all signals map to green valid replacements.
  4. Click Import.
  5. Once generation completes, reconnect the simulation coupling and initialize runtime.

SIMIT Template and Coupling Diagnostic Reference

The following table outlines diagnostic indicators and troubleshooting actions for SIMIT template imports:

Symptom / BehaviorUnderlying CauseDiagnostic CheckCorrective ActionPreview correct, generated charts blankDuplicate template in Global and Project librariesCompare Template Task Card foldersDelete global duplicate; use Project TemplatesPartial signal assignmentCase sensitivity mismatch in Excel column headersInspect Excel header vs {Placeholder}Align spelling and capitalization exactlyImport fails with 'Tag locked'Active coupling running in backgroundCheck Couplings status iconDisconnect coupling before running importPlaceholders remain as literal {TAG}Placeholder not defined in Excel tableSearch chart for unmapped tokensEnable 'Remove placeholders with empty replacement'Import takes excessive time (>10 min)Excessive cross-sheet Excel formattingInspect file size and formulasSave Excel as clean .csv or tab-delimited .txt

Eliminating library ambiguity ensures 100% automated signal binding across thousands of simulation tags.

Verification

To verify that SIMIT template instantiation succeeded:
1. Open any of the newly created simulation charts in the Project Navigation tree.
2. Inspect the signal input and output connector blocks on the chart canvas.
3. Verify that the signal fields contain concrete, populated PLC tags (e.g., DB100.DBX0.0 or symbolic tag names) rather than empty fields or literal {...} placeholders.
4. Activate the simulation coupling and start SIMIT runtime.
5. In the PLC engineering tool (SIMATIC Manager or PLCSIM), force a test signal and verify bidirectional response in the instantiated SIMIT chart.

Limitations and Operational Precautions

  • Always back up the SIMIT project (File -> Save As) before executing bulk template instantiations involving hundreds of charts.
  • Special characters (such as /, \, *, ?, or :) in Excel instance names are invalid in SIMIT chart titles and will cause instantiation aborts.
  • Avoid using complex formulas or macro scripts inside the Excel import sheet; export the workbook to pure text values before importing.
  • When updating an existing simulation, deleting old charts before re-importing is safer than attempting in-place overwriting.

Engineer FAQ

Why did the preview show correct replacements if the templates were duplicated?

The SIMIT import wizard preview parser evaluates the first template found in its search path (often the global library), whereas the physical chart instantiation compiler bound to the local project library which had different placeholder definitions.

Can I use CSV files instead of Excel spreadsheets for SIMIT instantiation?

Yes. Tab-delimited .txt or semicolon-delimited .csv files are fully supported and often import faster than .xlsx files with complex cell formatting.

Does SIMIT require an active PLC connection to import templates?

No. Importing templates is an offline engineering task. In fact, having an active online coupling during import can lock tag registries and cause signal binding failures.

Technical References

Related Articles

Related Tags

  • SIMIT_Simulation
  • Virtual_Commissioning
  • Template_Import
  • Signal_Placeholders
  • SIMIT_V8_0
6 respuestas