The simatic SD import of the new ladder s7dcl from version V20 does not import correct. If you export working (compiled) software (a function block with in it a couple of networks calling function blocks with the instance data stored in statics of the calling function block) and import the same file(s) it corrupts the software. It assumes you are referencing an instance datablock, instead of the static.

(All by using a small openness api c# program, since it is not yet available in the version control interface).

I tried the latest V20 update 1, but unfortunately this did not resolve the issue. 

The simatic SD makes generating ladder software a lot easier, but at the moment it is useless for this situation.

Anybody any suggestions how to resolve this?

___________

split from Openness V20 Bug?

The problem is related to statics with special characters like a - or a space. These are surrounded by
"Static Instance Name" or "Static-Instance-Name". 

When you use the #"Static Instance Name" when calling a block, TIA Portal assumes a instance datablock. The workaround for now is to not use the special characters. Then the import works fine.

Did you get the export (and import to work)? Where can I get the tool to do this, pls? External Program to interface with TIA Openness.