Resolving SFC Compiler Error 'sfc_functiontypesgetv8_2 doesn't deliver a function type'

Resolving SFC Compiler Error 'sfc_functiontypesgetv8_2 doesn't deliver a function type'

The compiler error 'sfc_functiontypesgetv8_2 doesn't deliver a function type' during Sequential Function Chart (SFC) calculation or compilation in SIMATIC PCS 7 V8.2 indicates an internal DLL version mismatch or corrupted SFC function type library (S7JDAUDB.DLL / SFC_FunctionTypesGetV8_2.dll). This occurs when an engineering update or hotfix is applied partially or when shared COM libraries become desynchronized. To resolve this, install the latest cumulative update for SIMATIC SFC V8.2 (such as SFC V8.2 Upd1 or Upd2), execute 'Clean Up Block Types' in SIMATIC Manager, and recompile the SFC charts with memory reset.

Table of Contents

Architecture of SFC Function Types and Type Libraries

In SIMATIC PCS 7, the Sequential Function Chart (SFC) engineering environment evaluates transitions, step actions, and operating state logic. When an engineer defines step assignments or checks transition logic in the SFC Editor, the compiler invokes internal type evaluation routines.

The dynamic library SFC_FunctionTypesGetV8_2.dll (interfacing with S7JDAUDB.DLL) queries the STEP 7 global block catalog to retrieve parameter signatures, mathematical operators, and system function types. If this interface fails to return expected type metadata, compilation halts immediately.

Root Cause of the sfc_functiontypesgetv8_2 DLL Exception

The error sfc_functiontypesgetv8_2 doesn't deliver a function type typically stems from three specific inconsistencies:

  1. Partial Software Update: Installing a PCS 7 update or STEP 7 Hotfix without installing the corresponding SFC update causes a binary signature mismatch between STEP 7 base components and the SFC editor COM interfaces.
  2. Corrupted Type Library Registration: Windows registry keys binding the COM ProgID for SFC_FunctionTypesGet become damaged or point to an obsolete DLL path.
  3. Inconsistent Global Block Types: If custom user function blocks or outdated library blocks in the project share conflicting type definitions, the SFC type analyzer aborts.

Step-by-Step Patching and Library Synchronization Workflow

Follow this procedure to restore SFC compiler stability:

  1. Verify Installed SFC Version:
    - In SIMATIC Manager, select Help > About SIMATIC Manager....
    - Click Display and locate SIMATIC SFC.
    - Note the exact version and update build (e.g. V8.2.0.0).
  2. Download Official SFC Update:
    - Open the Siemens Compatibility Tool (www.siemens.com/kompatool).
    - Download the latest cumulative update for SIMATIC SFC V8.2 (SIOS Entry ID 109756832).
  3. Close Applications and Install Update:
    - Close SIMATIC Manager, CFC, SFC, and WinCC.
    - Run Setup.exe with administrator privileges.
    - Restart the engineering station after setup completes.

Cleaning Up Block Types and Recompiling Charts

After applying the update, synchronize project type libraries:

  1. Open the project in SIMATIC Manager.
  2. Select the AS Chart folder and navigate to Options > Manage Block Types....
  3. Click Clean Up; this purges unreferenced block types and resolves duplicate interface definitions.
  4. Open the SFC Editor and execute Chart > Check Consistency.
  5. In SIMATIC Manager, perform a full CFC/SFC compilation (CFC > Compile > Entire program) with Generate module drivers checked.

Troubleshooting Matrix for SFC Compilation Errors

The table below correlates compiler error messages with diagnostic causes and remedies:

Compiler Error / CodeUnderlying Root CauseVerification MethodCorrective Remedysfc_functiontypesgetv8_2 doesn't deliver...Incompatible SFC DLL / incomplete patchCheck SFC version in About dialogInstall latest SFC V8.2 Cumulative UpdateRefBlockCopy - S7JDAUDB.DLLCorrupted SFC type registrationInspect S7JDAUDB.DLL in Step7\binRe-register DLL via regsvr32 or reinstall SFCBlock type different in source and targetInconsistent Master Data LibraryCompare block timestamps in MDLUpdate block types across multiprojectError -321 opening SFC databankCorrupted SfcRtBase database indexCheck wincproj\OS\SfcRtBaseDelete SfcRtBase files and recompile OSSyntax error in transition calculationUnresolved tag pointer or invalid typeCheck SFC transition conditionRe-select operands via Symbol Table browser

Verification

Confirm that SFC calculation and compilation are restored:

  1. Open the affected SFC chart in the SFC Editor.
  2. Perform a transition calculation check (SFC > Check Consistency); confirm zero errors are reported.
  3. Modify a transition formula and click Apply; verify syntax evaluation completes successfully.
  4. In SIMATIC Manager, execute a full AS program compilation; verify compilation finishes with 0 Errors.
  5. Open an SFC instance online in the AS; confirm live step execution displays without fault.

Limitations and Operational Precautions

Review the following software engineering precautions:

  • Homogeneous Engineering Stations: In multi-engineer environments, ensure all engineering laptops and ES stations have the identical PCS 7 service pack and SFC update build installed.
  • Multiproject Backup Mandatory: Always execute File > Archive... in SIMATIC Manager prior to installing updates or running block type cleanup wizards.
  • Validate Against Compatibility Matrix: Never install standalone STEP 7 hotfixes from internet forums without verifying PCS 7 release compatibility on the official Siemens Compatibility Tool.

Engineer FAQ

What does the sfc_functiontypesgetv8_2 error specifically mean?

It means the SFC compiler's internal function type query service failed to return type definitions from the global catalog, caused by an unpatched or mismatched SFC DLL build.

Can I fix this error by copying the DLL from another computer?

Manually copying DLL files into the Siemens installation folders is strongly discouraged, as COM object registrations, type libraries, and dependent assemblies will remain mismatched. Always install the official Siemens update package.

Does this compiler error corrupt the downloaded program in the CPU?

No. The error aborts the compilation process before any code is generated or transferred, leaving the program in the CPU completely untouched.

Technical References

Related Articles

Related Tags

  • SFC Compiler
  • sfc_functiontypesgetv8_2
  • S7JDAUDB.DLL
  • PCS 7 V8.2
  • SFC Update
  • Consistency Check
6 respuestas