Migrating to Siemens MProt driver version 2.10 from previous versions.

This driver’s current version (2.10) implements its strings in a format standardized by its manufacturer; nonetheless, it can simultaneously remain compatible with the old format via special settings.

Q&A:

Question: What could possibly happen if an older application, whose tags are configured in STRING format, migrates to version 2.10, but the option “Keep support for legacy strings” remains unchecked?

Answer: In this scenario, all STRING tags would return read errors. When the option “Keep support for legacy strings” is checked, the tags will resume reading successfully.

Question: Can an application using STRING-type tags migrate from previous versions to version 2.10 to use the new string format?

Answer: Yes! Nonetheless, all STRING-type tags will return error when read. This will continue until the first write is performed, which in turn will force the string to follow the correct pattern. Successful read will then resume after this first write.

If you wish to adequate the application to the correct string format, a thorough and careful read of version 2.10’s manual is recommended; this will help you set string-type tags properly, and also adequate these tags’ settings in conformity to the string variable statements performed at the Ladder. After this, the writing should occur. These tags’ read will return successfully.

The scenario mentioned above (adequacy to standard format) is highly recommended. However, it will all depend on the user. Their decision must take in consideration the work being accomplished. The number of string tags in the application must the number one factor to be gauged here.

Question: So, legacy strings may someday be outdated?

Answer: Yes! Only applications developed in versions previous to 2.10 and that have not suffered the string tags adequacy process will continue using the previous format (legacy strings); this is why it is very important to keep support to legacy formats.