Project-Converting

ALPHA-VISION^® content: Project-Converting

Project-Converting

SUMMARY

This document describes how to convert an existing S7-Project for use on a SoftPLC7 und how to perform some basic checks on the result.

Introduction
Converting
SoftPLC7.ini
Consistence check
Analysis of calling
Runtime check

Introduction

Steps to convert a STEP7-Program

Converting
The STEP7-Program is converted to a SoftPLC7-Program.
SoftPLC7.ini
That file is modified according to the imported STEP7-Program.
Consistency
The completeness of the modules is checked.
Analysis of calling
Plausibility of the information displayed is checked by the user.
Runtime check
The SoftPLC7-Program is started.

Converting

After starting the program 'SoftPLC.exe' the item 'Convert' in the pull-down menu 'File' opens the following dialog:

Source folder

You may input or browse for the folder location of the files to be converted. (OFFLINE DIRECTORY of the STEP7 Project)

Button labeled ‘S7-Program..’

Opens a dialog to input or browse for the location of the STEP7 project to be converted.

Destination folder

You may input or browse for the folder the converted files should be written to.

Button labeled ‘Convert’

Starts converting the S7-Project to SoftPLC7-Project.

If source or destination is missing, conversion does not start
Only one project can be converted at a time
The field “Report” informs about progress of the conversion
In case of error, the reason is given in the Report field

Note:

Conversion may also be done via Command line. see: 'Call-up syntax for SoftPLC7' in System_Overview.

SoftPLC7.ini

The 'SoftPLC7.ini' file holds parameters needed for the runtime.

Default name is SoftPLC7.ini.
If the default name is not used, the *.ini file name must be specified on program start
If SoftPLC7s are instanciated, any SoftPLC7 needs its own *.ini file with its distinctive file name.
In no circumstances default *.ini filenames my be used
A standard SoftPLC7.ini file is included in software delivery

Structure of SoftPLC7.ini

The file is structured in sections; a section may have arbitrary entries.
Some of the section entries are written by the system itself according to user input.

I.E. see Converting above
“Source =” and “Destination folder” are written to section [Convert] entry “From” and “To”.
Next time 'Converting' is called up these entries are presented as pre select.

Very little of the entries need adaptation to a specified project, these are marked in the following.

Sections to be taken care of:

(Depending on functionality and used hardware not all of the sections may exist)
For detailed Syntax of any of the following see: 'SoftPLC7.ini'

[HLL-Functions] ! has to be checked !
All Modules modules having a corresponding DLL must be listed here.

[OBx] ! only when deviate from default !
If OBs differ from default, the deviations has to be defined here.
(OBs without deviation needn’t be listed at all)

[OB1] ! only when deviate from default !
Like OBx, but has the additional parameter “Cycle Monitoring”

[Run]
The last active SoftPLC7-Program is listed here.

[Convert] ! information only !
The source / destination of last converted S7-Program is listed here.

[StartUp]
For possible StartUp-Parameters.

[ACI] ! only needed for connection to ALPHA-VISION^®-VISU !
Defines the DataObject file of the visualisation.

[AciConnect]
Needed for connection to ALPHA-VISION^®-VISU.

[PG]
Defines parameter to connect to debug interface.

[Watch]
Defines how often debug informations are checked.

[Retentive]
Defines the number of remanent flag-bytes, timers and counters.

[Exit]
Defines whether on closing down SoftPLC7 persistent data should be saved in the persistent directory.

Consistence check

After starting SoftPLC7.exe a consistence check should be performed.
(Pull-down menu ‘File’ item ‘Consistence’)
The completeness of modules is checked; missing ones are listed.

Note:

In S7 environment, modules of the library needn’t be available in the project folder in addition; on converting to SoftPLC7 only modules out of the Offline-folder will be converted. That means, under SIMATIC-Manager at least those library-modules, that be needed in the project, must be copied to the S7-Program environment.

Analysis of calling

Select 'analysis of calling' in pull-down menu 'File' for that check.

All modules are listed in a tree.

A module in bold font indicates that the module is listed in the INI-file; means - got a corresponding DLL.
A module in normal font indicates, that the module is executed as standard S7-Code.
A module in brackets indicates that the module is not called at all.
+ in front of a module indicates, that via mouse-click (an)other module(s) calling that module can be listed.

Note:

System-Modules must appear in bold font – if necessary enlist them.
Non-System-Modules in bold font should be checked.
Generally anyS7-Module may be substituted by DLLs, but its rather rarely at the moment, exceptions are “FC5, FC6, FC8, FC50, FC60” (send-recv) nevertheless check!
A module in brackets (not called) should be look at with care, as a module called indirectly (i.E. UC FC[MW03] can not be identified by ‘analysis of calling’ and therefore will be marked as 'not called'.

Runtime check

If the program enters STOP-condition unexpected, an S7-Error occurred.

For further investigation the SIMATIC-Manager or “Test mode” via pull-down menu “VIEW” may be used.