Resolving SIMIT Crashes During PROFINET OMS Hardware Configuration Import from TIA Portal

In SIMATIC SIMIT (v9.0 and v10.x), software crashes occurring during the import of PROFINET hardware configurations (.oms files exported from TIA Portal V13 SP1) are caused by version discrepancies in the SIMIT TIA Export Tool, XML schema buffer overflows on large distributed topologies, or unsupported third-party GSDML modules. SIMIT's Open Modeling Standard (OMS) parser terminates unexpectedly when encountering unassigned I/O addresses, un-parameterized failsafe submodules, or missing GSDML definitions. Resolving this requires updating SIMIT to the latest service pack, verifying clean compilation in TIA Portal, and regenerating the export with the matching SIMIT plugin.

The SIMIT PROFINET Coupling and Open Modeling Standard (OMS)

SIMATIC SIMIT (6DL8913-0AK00-0AB5) uses virtual couplings to interface simulation models with automation controllers:
* The OMS Workflow:
1. The hardware configuration is completed in TIA Portal or STEP 7.
2. The SIMIT TIA Export Tool add-in generates an Open Modeling Standard (.oms) archive containing the physical PROFINET topology, rack layouts, submodule addresses, and symbolic I/O tables.
3. In SIMIT, the engineer adds a PROFINET Coupling and imports the .oms file, which automatically populates thousands of simulation input and output signal channels.
* The Crash Symptom:
When clicking Import in SIMIT V9.0, the progress bar stalls at parsing module data, followed by an immediate application crash (SIMIT.exe has stopped working).

Root Causes for SIMIT Parser Crashes During OMS Import

SIMIT TIA Export Tool Version Mismatch:
The TIA Portal export plugin version must match the installed SIMIT release. Using an export tool from SIMIT V8.1 or V9.1 with SIMIT V9.0 causes binary XML formatting conflicts.
Unsupported Third-Party GSDML Device Descriptions:
If the PROFINET network contains complex third-party field devices (e.g., specialized multi-axis servo drives, barcode scanners, or custom gateways) whose GSDML files contain non-standard XML schema tags, the SIMIT parser crashes on memory allocation.
Unassigned I/O Addresses in TIA Portal:
Submodules left in HW Config without assigned I/O addresses or with overlapping memory partitions generate null pointer exceptions in SIMIT's address mapping table.
Un-parameterized Failsafe Modules:
PROFIsafe I/O modules (e.g., F-DI, F-DO) with missing F-destination addresses (F_Dest_Add) cause schema validation aborts.

Comparison Table: SIMIT Hardware Coupling Methods

The table below outlines alternative controller coupling methods in SIMIT:

Coupling TypeConfiguration MethodData SourceSensitivity to Complex HWIdeal ApplicationPROFINET OMS ImportAutomated import via .omsTIA Portal / STEP 7 HW ConfigHigh (Parses full hardware topology)Complete virtual commissioningVirtual Controller (VC)Direct project memory couplingS7-400 / CPU 410 user programLowIntegrated PCS 7 testingPLCSIM AdvancedAPI connection via virtual switchS7-1500 / ET 200SP CPU memoryLowTIA Portal logic testingGeneric Signal Table (CSV)Manual / Scripted CSV importTag lists from Excel / ManagerZero (Crash Proof)Rapid simulation prototyping

Diagnostic Checks: Validating TIA Portal Hardware Configurations

Before generating the OMS export:
* Perform Full Hardware Recompile:
In TIA Portal, right-click the PLC device and select Compile -> Hardware (rebuild all). Ensure zero warnings regarding missing GSDML files or duplicate IP/device names.
* Verify Address Allocation:
Open the Device Overview table. Confirm every configured I/O module has valid start and end addresses assigned within the process image partition.

Step-by-Step Procedure to Resolve SIMIT OMS Import Crashes

Update SIMIT Software:
Install the latest update for your SIMIT release (e.g., SIMIT V9.0 Upd1 or Upd2). Updates resolve known parser buffer overflows on large PROFINET networks.
Install Matching SIMIT TIA Export Tool:
* Navigate to the SIMIT installation directory: C:\Program Files (x86)\Siemens\Automation\SIMIT\SIMIT TIA Portal Export Tool.
* Install the exact plugin corresponding to your TIA Portal version (V13 SP1).
Generate a Clean OMS Export in TIA Portal:
* Open TIA Portal V13 SP1.
* Ensure the project compiles with zero hardware errors.
* Right-click the PLC -> Export to SIMIT. Select Export PROFINET IO Data.
Isolate Problematic Modules (If Crash Persists):
* If SIMIT still crashes, open the generated .oms archive using a ZIP utility.
* Inspect the internal DeviceList.xml.
* In TIA Portal, temporarily delete complex third-party non-Siemens drives or unneeded communication gateways, re-export, and test import in SIMIT.
Alternative Workaround: CSV Signal Import:
If an obscure GSDML module prevents OMS import, export the I/O symbol table from TIA Portal as a .csv file and import it directly into SIMIT's Standard Coupling table.

Verification

To verify successful PROFINET hardware import:
1. Open SIMIT and navigate to the configured PROFINET coupling.
2. Click Import Hardware Configuration and select the .oms file.
3. Confirm that the import completes with 100% progress and displays the summary message: 'Hardware configuration successfully imported.'
4. Expand the signal tree in SIMIT. Verify that all digital inputs, analog inputs, and drive control words populate with correct symbolic tag names.

Limitations and Operational Precautions

Simulation Depth of Third-Party Devices: SIMIT simulates the bus communication interface (inputs and outputs) of PROFINET devices; it does not emulate the internal proprietary firmware algorithms of complex third-party instruments.
Failsafe Telemetry Bypass: When simulating PROFIsafe modules in SIMIT without real safety controllers, F-channel passivation must be depassivated using SIMIT safety bypass blocks.
Licensing Disclaimer: SIMIT simulation software (6DL8913-0AK00-0AB5) requires valid engineering and runtime licenses managed via Automation License Manager.