(c) Schneider Automation GmbH, 1995-1999; All Rights Reserved

Porting Applications into Concept V2.2

This document contains the following sections:

1. Overview
2. Converting Projects to Concept 2.2
3. Updating to the Current Exec's
4. Importing Applications
4.1 Importing Applications from Concept 2.0 - Patch A4
4.2 Importing Applications from Concept 2.1 - Patch B2.1
4.3 Importing Applications from Concept 2.11
4.4 Importing Applications from Concept 2.12
4.5 EFB Substitutions
5. Technical Support

1. Overview

The purpose for this document is to review the process of converting an application from
previous versions of Concept to the latest version of Concept 2.2. Regardless of the version of
Concept you are moving from, the process to Export/Import your application will follow the
same basic steps.

2. Converting Projects to Concept 2.2

Please follow the steps described below when installing Concept 2.2 and porting your projects
from previous Concept versions. Applications written in Beta versions of Concept 2.2 are not
fully compatible with the released Concept version.

Step Action
1 Export your project created in a previous Concept version using the Concept
Converter program (dbconv.exe) supplied with the earlier version of Concept. This will
save your project in a <project>.asc file in the directory of your project.Repeat this
step for all projects.
2 Move all the *.asc files just created, to a directory(s) outside of the Concept directory.
3 Make a backup copy of the project(s) and the *.asc files to maintain backward
compatibility if the upgrade should not succeed.
4 Handle EFB's and custom loadables separately. The loadables have to be copied into
the "Concept/dat" sub directory of the Concept 2.2 version, EFB's must be rebuilt and
installed using the EFB toolkit with the Borland 5.0 C++ Compiler.
5 Install Concept 2.2. Do not install the new version of Concept over an existing
Concept directory. Instead use the uninstall dialog (Control Panel->Software) for V2.2
 Beta, delete all files under the Concept directory and its sub directories (for version
2.11 or earlier), or install it in a separate directory.
6 Install the ExecLoader found on the Service Release CD # 2.
7 Reboot your PC.
8 Flash the appropriate Exec to the controller (see Updating to the Current Exec's
below)
9 Copy the saved *.asc files into the new project directory, e.g the new Concept
directory or a newly created sub directory under Concept directory for each project.
10 Run the Concept Converter 2.2 and import all your projects to be used in Concept 2.2.
11 Run Concept 2.2 and open your converted projects.You will be notified of Concept 2.2
changes that will effect your application. The tables found under Importing
Applications provides information on porting from previous versions of
Concept as well as the EFB blocks effected and a description of the change
made to the block. It may be necessary to replace a block from a previous
version with a new named block. If required, this information is provided
below as well.

3.0 Updating to the Current Exec's

Run the loader utility (ExecLoader.exe, must be installed on your hard disk) and re-flash your
controllers with the appropriate exec. Refer to the file EXECS.DOC for the correct exec to
download.
It is highly recommended to power cycle the PLC after loading a new exec to the PLC.

4.0 Importing Applications

The following tables represent blocks which may have been used in a previous version of
Concept and whose definition has changed in Concept 2.2. There will be a message
associated with each block that has changed which appears when the user tries to open a
project that has been ported from a previous version. Depending on the type of change made
to the block, the user may just be informed that the block has changed internally, and it should
not effect the application at all. There are other blocks whose interface has changed. This may
or may not effect a customer's application. The user has the choice to substitute all instances
of the old blocks with the new blocks, or ignore the new block substitution but the project will
not download. A third choice is the user has the ability to substitute all occurrences of a
changed block, with a new named block. If this is required, the new named block is provided in
the third column of the table below.

Note: Project’s desktop file is not imported. Do not copy it from the previous version of
Concept.

4.1 Importing Applications from Concept 2.0 Patch A4

Previous Block Name Change Made to Block Concept 2.2 Replacement

O_DEBUG new output pin "WARN_CODE"

COMP_PID new output pins
"SP_CAS_N","YMAN_N", "OFF_N",

ACT_DIA code optimized

DYN_DIA code optimized
Previous Block Name Change Made to Block Concept 2.2 Replacement
GRP_DIA code optimized
LOCK_DIA code optimized
PRE_DIA code optimized
REA_DIA internally used memory increased in
size

DEFUZ_INT # of input pins reduced from 31 to 18

DEFUZ_REAL # of input pins reduced from 31 to 18
DEFUZ_STI # of input pins reduced from 30 to 9
DEFUZ_STR # of input pins reduced from 30 to 9
FUZ_STERM_INT # of input pins reduced from 31 to 4
FUZ_STERM_REAL # of input pins reduced from 31 to 4
FUZ_ATERM_STI # of input pins reduced from 31 to 9
FUZ_ATERM_STR # of input pins reduced from 31 to 9
FUZ_ATERM_INT # of input pins reduced from 25 to 9
FUZ_ATERM_REAL # of input pins reduced from 25 to 9

QUANTUM changed internally

PLCSTAT internally used memory increased in
size
SFCCNTRL new output pin TERRACT

ATI030 Changed internally reason bug fix:

Raw values ("Type: Undefined")
must not be divided by 10 on
Resolution: 0.1 Deg.

4.2 Importing Applications from Concept 2.1 Patch B2.1

Previous Block Name Change Made to Block Concept 2.2 Replacement

ACT_DIA (CC2.1, with no longer supported XACT_DIA

STATION-pin)
ACTDIAB (CC2.1, no no longer supported ACT_DIA
STATION-pin)
ACT_DIA (CC2.1B2, equivalent to ACT_DIA ACT_DIA
no STATION-pin) Changed Internally

DYN_DIA (CC2.1, with no longer supported XDYN_DIA

STATION-pin)
DYNDIAB (CC2.1, no no longer supported DYN_DIA
STATION-pin)
DYN_DIA (CC2.1B2, equivalent to DYN_DIA DYN_DIA
no STATION-pin) Changed Internally

GRP_DIA (CC2.1, with no longer supported XGRP_DIA

STATION-pin,
with 2 input pins)
GRPDIAB (CC2.1, no no longer supported GRP_DIA
STATION-pin, with
extensible pins)
GRP_DIA (CC2.1B2, equivalent to GRP_DIA GRP_DIA
Previous Block Name Change Made to Block Concept 2.2 Replacement
no STATION-pin, with Changed Internally
extensible pins)

LOCK_DIA (CC2.1, no longer supported XLOCK_DIA

with STATION-pin)
LOCKDIAB (CC2.1, no no longer supported LOCK_DIA
STATION-pin)
LOCK_DIA (CC2.1B2, equivalent to LOCK_DIA LOCK_DIA
no STATION-pin) Changed Internally

PRE_DIA (CC2.1, with no longer supported XPRE_DIA

STATION-pin)
PREDIAB (CC2.1, no no longer supported PRE_DIA
STATION-pin)
PRE_DIA (CC2.1B2, equivalent to PRE_DIA PRE_DIA
no STATION-pin) Changed Internally

REA_DIA (CC2.1, with no longer supported XREA_DIA

STATION-pin)
READIAB (CC2.1, no longer supported REA_DIA
without STATION-pin)
no longer supported

REA_DIA (CC2.1B2, internally used memory increased in

no STATION-pin) size Interface was Changed

XACT (CC2.1) internally used memory

increased in size
XACT (CC2.1B2) equivalent to XACT
Changed Internally

I_SCA20_WARN no longer supported I_SCALE_WARN

(CC2.1)
I_SCA20 (CC2.1) no longer supported I_SCALE
ERR2HMI Output pin WAF no longer supported

DEFUZ_INT # of input pins reduced from 31 to 18

DEFUZ_REAL # of input pins reduced from 31 to 18
DEFUZ_STI # of input pins reduced from 30 to 9
DEFUZ_STR # of input pins reduced from 30 to 9
FUZ_STERM_INT # of input pins reduced from 31 to 4
FUZ_STERM_REAL # of input pins reduced from 31 to 4
FUZ_ATERM_STI # of input pins reduced from 31 to 9
FUZ_ATERM_STR # of input pins reduced from 31 to 9
FUZ_ATERM_INT # of input pins reduced from 25 to 9
FUZ_ATERM_REAL # of input pins reduced from 25 to 9

HTB5 internally used memory increased in

size
PLCSTAT internally used memory increased in
size
SFCCNTRL New output pin TERRACT
Previous Block Name Change Made to Block Concept 2.2 Replacement

ATI030 Changed internally reason bug

fix:Raw values (”Type: Undefined”)
must not be divided by 10 on
Resolution: 0.1 Deg.

4.3 Importing Applications from Concept 2.11

Previous Block Name Change Made to Block Concept 2.2 Replacement

REA_DIA (without internally used memory

STATION-pin) increased in size

ERR2HMI output pin WAF no longer supported

DEFUZ_INT # of input pins reduced from 31 to 18

DEFUZ_REAL # of input pins reduced from 31 to 18
DEFUZ_STI # of input pins reduced from 30 to 9
DEFUZ_STR # of input pins reduced from 30 to 9
FUZ_STERM_INT # of input pins reduced from 31 to 4
FUZ_STERM_REAL # of input pins reduced from 31 to 4
FUZ_ATERM_STI # of input pins reduced from 31 to 9
FUZ_ATERM_STR # of input pins reduced from 31 to 9
FUZ_ATERM_INT # of input pins reduced from 25 to 9
FUZ_ATERM_REAL # of input pins reduced from 25 to 9

PLCSTAT internally used memory

increased in size
XSFCCNTRL new input pin RESSTEPT

GET_BIT input pin "IN" of data type ANY

changed to data type WORD.
input pin "REVERS" no longer
supported
SET_BIT output pin "RES" of data type ANY
changed to data type WORD
input pin "REVERS" no longer
supported

ATI030 Changed internally reason bug fix:

Raw values (”Type: Undefined”)
must not be divided by 10 on
Resolution: 0.1 Deg.
4.5 EFB Substitutions

If some of the EFBs used in your application have been changed within Concept 2.2 (interface
changed/internally changed) this issue is brought to your attention via a message box the first time
you open your application. There are instances where you are faced with an option to substitute the
old function blocks. If you choose not to substitute an EFB then you cannot download to the PLC,
and the analyzer will prompt you with an appropriate error.

The number of extensible pins for EFBs of the FUZZY library have been adjusted to its documented
and functional supported amount. Links and variables attached to pins higher than the new limit
(which didn't have any effect and thus should never be used) will be deleted. All other logic will be
ported correctly.

The CONF_20 library containing diagnostic and I_SCALE EFBs was introduced in V2.1 B1.1
accidentally and does not exist in Concept 2.2. If you have used these EFBs in your application, a
dialog will open giving you the opportunity to substitute the EFBs in Concept 2.2. Please refer to the
table below to determinate the EFBs with the same interface and functionality for substitution.

Previous Concept Version Concept 2.2 Equivalent Block

______________________________________________________________
Library CONF_20/Diag_Base Diagno/Diagnostics
ACTDIAB ACT_DIA
DYNDIAB DYN_DIA
GRPDIAG GRP_DIA
LOCKDIAB LOCK_DIA
PREDIAB PRE_DIA
READIAB REA_DIA

Library CONF_20/Analog_IO_Scaling ANA_IO/ANALOG_IO_SCALING

I_SCA20 I_SCALE
I_SCA20_WARN I_SCALE_WARN

5.0 Technical Support

Stripped Quantum (140 CPU 13 xxS)

The new loadable EMUQ used for Floating point emulation must be manually installed in the loadable
list if your application is using REAL arithmetic with the stripped Quantum 140 113 xxS (no Co-
Processor)

Hybrid applications (LL984 and IEC Program)

With Concept 2.2 the changes to solve the "remove disable coil" problem (subject: RDE and IEC-
located coil) introduced the changes that coils can't be written from both an IEC section and a LL984
section. The analyzer generates an error message.

LD Editor, DFBs written in LD from previous Concept versions

The representation for the LD editor has changed to cell orientation (switched to grid mode).
The graphical conversion is done when opening the section and may alter the graphical appearance.
If you have ported an application from a previous version that contained one or more LD sections,
you will be prompted to review all LD sections when you open your Concept 2.2 project. For each
LD section you will be prompted with the following message: ‘The section '<section>' was created
with Concept 2.12 or older. Do you want to update this section. Attention: The section will be
rearranged and you cannot undo this operation’. If you select YES, then your logic will be
reformatted in a grid fashion. If you select NO, your blocks are not substituted, but you will not be
allowed to download.

After converting an existing project which contains LD DFBs you must open up each LD section for
the conversion to take place. (Nested DFBs must be opened in the correct bottom-up sequence).

If you choose to upgrade into the grid representation, you may find there are LD sections which
require manual modifications be made.

RDE Templates
RDE Templates are not upward compatible. If a RDE Template created in an older version of
Concept is opened in a newer version of Concept, the format of the RDE spreadsheet will be
incorrect. The column format of the RDE spreadsheet was modified after the Concept 2.1x release.
You will receive an Internal System Error -20002.

Ethernet Configuration Screen

The Quantum Ethernet module configuration is no longer accessed through the module parameters
button on the IO Map. It has been moved to the Ethernet I/O Scanner screen found on the
Configure menu.

Memory requirements
The memory required to access discrete references has increased. An internal IEC (mirror)
buffer is no longer used.
The size of the application is slightly different between Concept 2.1 and 2.2 because of a changed
accessing 0x and 1x references. The direct access (read or write) of these references may increase
your code.

Process diagnostics error buffer (4 Kbytes) is not longer allocated by default with Concept 2.2.
This reduces the overhead of DFB instance data compared to versions 2.1/2.11.

E.g.

Application type Used total memory in Kbytes Delta

Concept Version 2.0 2.1/2.11 2.2 2.0/2.2 2.1/2.2

steal 247,2 289,3 256,2 + 3,6% -11.4%
chemical 287,8 311,7 296,8 + 3,1% - 4,7%
flow control 102,7 121,4 105,3 + 2.5% - 13,2%
automotive* - 125,5 160,9 - +28,2%
mining - 167.6 170.1 - + 1.4%
mining - 307.0 314.1 - + 2.3%

* With diagnostic buffer enabled in V2.2 and very extensive use of 0x or 1x registers.

Force
The behavior of disable has been changed. 0x/1x references will be set to the given value in the scan
regardless of the logic evaluation. 0x/1x references, which are used in IEC sections, behave now as
it does in LL984 sections.
User EFBs have to be recompiled with the EFB Toolkit for Concept 2.2