Release Notes Concept V2.

6 SR7

(c) Schneider Electric, 1995-2011; All Rights Reserved

Release Notes of Concept V2.6 Service Release 7

This document contains the following sections:

• Installation
• New Features and Functionality in Concept V2.6 Service Release 7
• Quality improvement and bug fixing
• Known issues that are not solved with this Service Release
• CC2Cat installation

1 Installation

The installation of Concept V2.6 Service Release 7 requires at least an installed Concept V2.6
basic version. SR7 will update any Concept 2.6 version, the EFB-Toolkit and the Application
Loader.
First download the Service Release SR7 from Schneider WEB page and run “Install.exe”. During
installation select the option "Upgrade Concept V2.6 XL/M/S", "Upgrade Concept V2.6
Application Loader" or "Install EXEC components separately”. The option "Install EXEC
components separately” will only update the Executive Loader.

Concept 2.6 SR7 contains all changes from Concept 2.6 SR1 till Concept 2.6 SR6a. For detailed
information see Release Notes of Concept 2.6 SR1…SR6 and SR7.
To use an EFB-Toolkit, it must be installed prior to the installation of the SR7.

Supported Operating Systems

Service Release 7 supports Windows XP Professional, Windows Vista Business 32-Bit and
Windows 7 Professional 32-Bit.

Windows 98, Windows NT4 and Windows 2000 are no longer validated.

WIN 2000 users have to have Administrator- or Power User rights when installing and running
Concept 2.6 and its service parts.
Due to different security permissions, WIN XP users must have Administrator rights when
installing and running Concept 2.6 and its service parts.

Windows Vista and Windows 7

Concept 2.6 SR7 will also run on Windows Vista Business 32 Bit (first introduced with Concept
2.6 SR5 Patch A) and on Windows 7 Professional 32-Bit. Detailed restrictions for the usage of
Concept on Windows Vista and Windows 7 are described in chapter 6.

Since Concept has been released, the Microsoft Windows versions have changed and different
security mechanisms were created and implemented. Concept, originally developed on WIN 3.1
was at that time not designed to support these security levels and an evolvement in this area
would require a complete redesign.

MDC-files: By updating a Concept Version with a new Service Release, the MDC file
information of the installed version will be lost and the 3rd party modules are no longer included
in the project.

page 1 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

The loss of the MDC file information can only be recognized by a ‘Bad Traffic Cop Stop’ error
4000 at PLC start.
When users perform a Concept update in the form of a new version or service release, any
MDC add-on's will require to be processed via the ModConnect tool again.

Authorization: Due to programming changes in the Concept application, it may be necessary

for you to authorize this service release after installation.
Select Start
Programs
Concept
Authorization
Select Task: “Authorize this PC”
or
Select Task: “Authorize by multi-user license disk”
Select one of the following methods of authorization: Phone, Fax or Email
Fill in your user information (required fields are marked with *)

*** Important: Please use the serial number and part number of your original Concept package***

1.1 Upgrade to Concept V2.6 SR7 from a version prior to V2.5 SR1

You must convert all applications with the Concept Converter before performing this
install. For details please refer to the file "UPGRADE.PDF" in the Concept directory.
Existing DFBs must be deleted from the local and global DFB directory before importing
the project.

1.2 Upgrade to Concept V2.6 SR7 from version V2.5 SR1 or a later version

• With Concept V2.6 SR7, it is not necessary to convert existing projects from Concept V2.5
SR1, V2.5 SR2 or V2.6 SR1…SR6.

• Upgrade the PLC Exec (firmware) only, if necessary due to a bug fix or new feature usage
(e.g. PLC memory defragmentation)

2 New Features and Functionality in Concept Version 2.6 SR7

2.1 New Hardware:

None

2.2 New Firmware/EXEC:

The IEC-PLC EXECs of Concept V2.6 SR7 are not compatible with EXECs from versions of
Concept prior to Concept V2.5 SR1. Therefore an update of the firmware is necessary. See the
table below for a complete list of the modifications.

page 2 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

Platform PLC Name Concept 2.6 SR7 Comment

Quantum 140 CPU x13 0x Q186V245.bin
140 CPU x13 0xS Q1SV248E.bin IEC Only – Stripped Executive
(old HW-revision)
140 CPU x13 0xS Q1rv301E.bin IEC Only – Stripped Executive
(latest HW-revision, PV-No >=6)
140 CPU 424 0x Q486V224.bin
140 CPU X34 0x Q58V129E.bin Older Hardware Revision
140 CPU X34 0xA Q5RV143E.bin Latest Hardware Revision
140 CPU 534 14B Q5BV115E.bin Latest Hardware Revision
Compact All CTSX225E.bin
Momentum 171 CCS 7x0 x0-984 M1LLV207.bin LL984 Only; XMIT Support
171 CCC 7x0 10-984 M1LLV207.bin LL984 Only; XMIT Support
171 CCS 7x0 x0-IEC M1IV212E.bin IEC Only; XXMIT Support only
171 CCC 7x0 10-IEC M1IV212E.bin IEC Only; XXMIT Support only
171 CCC 9x0 x0-984 M1EV128.bin LL984 Only; Ethernet Support
171 CCC 9x0 30 M1EV131E.bin IEC Only; Ethernet, with WEB pages
Atrium 180 CCO 121 01 AI3V046E.bin No XXMIT Support
180 CCO 241 01 AI5V417E.bin No XXMIT Support
180 CCO 241 01-S908 ------ No Concept 2.6 Support

2.3 Firmware/EXEC History Tables

The following tables show firmware/exec versions delivered with previous versions of Concept.
Concept Quantum
Version 140 CPU x13 140 CPU x13 140 CPU 424 140 CPU x34 140 CPU x34 140 CPU 534
0x 0xS 02 1x 1xA 14B
(IEC only)
2.5 SR1 Q186v222.bin QIECv250.bin Q486V219.bin Q58v108D.bin Q5rv102D.bin
2.5 SR2 Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v110D.bin Q5rv104D.bin
2.5 SR2a Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v110D.bin Q5rv104D.bin
2.5 SR2b Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v110D.bin Q5rv104D.bin
2.5 SR2c Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v110D.bin Q5rv104D.bin
2.5 SR2d Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v110D.bin Q5rv104D.bin
2.5 SR2e Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v114D.bin Q5rv109D.bin
2.5 SR2f Q186V230.bin Q1sv230D.bin Q486V219.bin Q58v114D.bin Q5rv109D.bin
2.5 SR2g Q186V240.bin Q1sv241E.bin Q486V219.bin Q58v118E.bin Q5rx127E.bin
2.6 SR1 Q186V240.bin Q1sv231E.bin Q486V219.bin Q58v115E.bin Q5rv120E.bin
2.6 SR1a Q186V240.bin Q1sv240E.bin Q486V219.bin Q58v117E.bin Q5rv123E.bin
2.6 SR1b Q186V240.bin Q1sv240E.bin Q486V219.bin Q58v117E.bin Q5rv123E.bin
2.6 SR1c Q186V240.bin Q1sv240E.bin Q486V219.bin Q58v117E.bin Q5rv123E.bin
2.6 SR1d Q186V240.bin Q1sv240E.bin Q486V219.bin Q58v117E.bin Q5rv123E.bin
2.6 SR2 Q186V240.bin Q1sv241E.bin Q486V219.bin Q58v118E.bin Q5rv126E.bin
2.6 SR2a Q186V240.bin Q1sv241E.bin Q486V219.bin Q58v118E.bin Q5rv126E.bin
2.6 SR2b Q186V242.bin Q1sv242E.bin Q486V220.bin Q58v120E.bin Q5rv129E.bin
2.6 SR2c Q186V242.bin Q1sv242E.bin Q486V220.bin Q58v120E.bin Q5rv129E.bin
2.6 SR3 Q186V242.bin Q1sv242E.bin Q486V220.bin Q58v121E.bin Q5rv130E.bin
2.6 SR3a Q186V242.bin Q1sv242E.bin Q486V220.bin Q58v122E.bin Q5rv131E.bin
2.6 SR3b Q186V242.bin Q1sv242E.bin Q486V220.bin Q58v122E.bin Q5rv131E.bin Q5bv103E.bin
2.6 SR4 Q186V243.bin Q1sv243E.bin Q486V222.bin Q58v123E.bin Q5rv132E.bin Q5bv104E.bin
2.6 SR4_1 Q186V245.bin Q1sv245E.bin Q486V222.bin Q58v123E.bin Q5rv132E.bin Q5bv104E.bin
2.6 SR4A Q186V243.bin Q1sv243E.bin Q486V222.bin Q58v123E.bin Q5rv132E.bin Q5bv104E.bin
2.6 SR4B Q186V244.bin Q1sv244E.bin Q486V223.bin Q58v124E.bin Q5rv133E.bin Q5bv105E.bin
2.6 SR4C Q186V245.bin Q1sv245E.bin Q486V223.bin Q58v125E.bin Q5rv135E.bin Q5bv107E.bin
2.6 SR5 Q186V245.bin Q1sv245E.bin Q486V223.bin Q58v125E.bin Q5rv136E.bin Q5bv108E.bin
2.6 SR5A Q186V245.bin Q1sv246E.bin Q486V224.bin Q58v128E.bin Q5rv139E.bin Q5bv111E.bin
2.6 SR6 Q186V245.bin Q1sv247E.bin Q486V224.bin Q58v129E.bin Q5rv140E.bin Q5bv112E.bin
2.6 SR6A Q186V245.bin Q1sv248E.bin Q486V224.bin Q58v129E.bin Q5rv141E.bin Q5bv113E.bin
2.6 SR7 Q186V245.bin Q1sv248E.bin Q486V224.bin Q58V129E.bin Q5rv143E.bin Q5bv115E.bin
Q1rv301E.bin

page 3 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

Concept Momentum
Version 171 CCS 7x0 171 CCS 7x0 171 CCC 9x0 171 CCC 9x0 171 CBB 970 171 CBB 970
x0 x0 x0 30 30 30
171 CCC 7x0 171 CCC 7x0
10 10
(LL984 only) (IEC only) (LL984 only) (IEC only) (LL984 only) (IEC only)

2.5 SR1 M1v203.bin M1IEC250.bin M1EV104.bin M1EWI250.bin

2.5 SR2 M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2a M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2b M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2c M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2d M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2e M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2f M1v203.bin M1IV204D.bin M1EV106.bin M1EV106D.bin
2.5 SR2g M1LLV207.bin M1IV210E.bin M1EV120.bin M1EV122E.bin
2.6 SR1 M1LLV207.bin M1IV208E.bin M1EV107.bin M1EV111E.bin
2.6 SR1a M1LLV207.bin M1IV209E.bin M1EV107.bin M1EV112E.bin
2.6 SR1b M1LLV207.bin M1IV209E.bin M1EV107.bin M1EV112E.bin
2.6 SR1c M1LLV207.bin M1IV209E.bin M1EV107.bin M1EV112E.bin
2.6 SR1d M1LLV207.bin M1IV209E.bin M1EV107.bin M1EV112E.bin
2.6 SR2 M1LLV207.bin M1IV210E.bin M1EV120.bin M1EV122E.bin
2.6 SR2a M1LLV207.bin M1IV210E.bin M1EV120.bin M1EV122E.bin
2.6 SR2b M1LLV207.bin M1IV210E.bin M1EV120.bin M1EV123E.bin
2.6 SR2c M1LLV207.bin M1IV210E.bin M1EV120.bin M1EV123E.bin
2.6 SR3 M1LLV207.bin M1IV210E.bin M1EV123.bin M1EV123E.bin
2.6 SR3a M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV126E.bin
2.6 SR3b M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV126E.bin
2.6 SR4 M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV126E.bin
2.6 SR4_1 M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV126E.bin
2.6 SR4A M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV126E.bin MPSV101.bin MPSV102E.bin
2.6 SR4B M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV127E.bin MPSV101.bin MPSV103E.bin
2.6 SR4C M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV127E.bin MPSV101.bin MPSV103E.bin
2.6 SR5 M1LLV207.bin M1IV210E.bin M1EV126.bin M1EV127E.bin MPSV101.bin MPSV103E.bin
2.6 SR5A M1LLV207.bin M1IV211E.bin M1EV128.bin M1EV130E.bin MPSV103.bin MPSV106E.bin
2.6 SR6 M1LLV207.bin M1IV212E.bin M1EV128.bin M1EV131E.bin MPSV103.bin MPSV107E.bin
2.6 SR6A M1LLV207.bin M1IV212E.bin M1EV128.bin M1EV131E.bin MPSV103.bin MPSV107E.bin
2.6 SR7 M1LLV207.bin M1IV212E.bin M1EV128.bin M1EV131E.bin MPSV103.bin MPSV107E.bin

Concept Compact
Version
2.5 SR1 CTSX202D.bin
2.5 SR2 CTSX205D.bin
2.5 SR2a CTSX205D.bin
2.5 SR2b CTSX205D.bin
2.5 SR2c CTSX205D.bin
2.5 SR2d CTSX205D.bin
2.5 SR2e CTSX205D.bin
2.5 SR2f CTSX205D.bin
2.5 SR2g CTSX215E.bin
2.6 SR1 CTSX210E.bin
2.6 SR1a CTSX212E.bin
2.6 SR1b CTSX212E.bin
2.6 SR1c CTSX212E.bin
2.6 SR1d CTSX212E.bin
2.6 SR2 CTSX214E.bin
2.6 SR2a CTSX214E.bin
2.6 SR2b CTSX217E.bin
2.6 SR2c CTSX217E.bin
2.6 SR3 CTSX218E.bin
2.6 SR3a CTSX219E.bin

page 4 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

2.6 SR3b CTSX219E.bin

2.6 SR4 CTSX221E.bin
2.6 SR4_1 CTSX221E.bin
2.6 SR4A CTSX221E.bin
2.6 SR4B CTSX221E.bin
2.6 SR4C CTSX222E.bin
2.6 SR5 CTSX222E.bin
2.6 SR5A CTSX223E.bin
2.6 SR6 CTSX224E.bin
2.6 SR6A CTSX225E.bin
2.6 SR7 CTSX225E.bin

Concept Atrium
Version 180 CCO 121 01 180 CCO 241 01 180 CCO 241 01 –s908
2.5 SR1 AI3v042D.bin AI5v035D.bin -------
2.5 SR2 AI3v043D.bin AI5v037D.bin -------
2.5 SR2a AI3v043D.bin AI5v037D.bin -------
2.5 SR2b AI3v043D.bin AI5v037D.bin -------
2.5 SR2c AI3v043D.bin AI5v037D.bin -------
2.5 SR2d AI3v043D.bin AI5v037D.bin -------
2.5 SR2e AI3v043D.bin AI5v037D.bin -------
2.5 SR2f AI3v043D.bin AI5v037D.bin -------
2.5 SR2g AI3v043D.bin AI5v037D.bin -------
2.6 SR1 AI3v044E.bin ------- -------
2.6 SR1a AI3v046E.bin AI5v416E.bin
2.6 SR1b AI3v046E.bin AI5v416E.bin
2.6 SR1c AI3v046E.bin AI5v416E.bin
2.6 SR1d AI3v046E.bin AI5v416E.bin -------
2.6 SR2 AI3v046E.bin AI5v416E.bin -------
2.6 SR2a AI3v046E.bin AI5v416E.bin -------
2.6 SR2b AI3v046E.bin AI5v416E.bin -------
2.6 SR2c AI3v046E.bin AI5v416E.bin -------
2.6 SR3 AI3v046E.bin AI5v417E.bin -------
2.6 SR3a AI3v046E.bin AI5v417E.bin -------
2.6 SR3b AI3v046E.bin AI5v417E.bin -------
2.6 SR4 AI3v046E.bin AI5v417E.bin -------
2.6SR4_1 AI3v046E.bin AI5v417E.bin -------
2.6 SR4A AI3v046E.bin AI5v417E.bin -------
2.6 SR4B AI3v046E.bin AI5v417E.bin -------
2.6 SR4C AI3v046E.bin AI5v417E.bin -------
2.6 SR5 AI3v046E.bin AI5v417E.bin -------
2.6 SR5A AI3v046E.bin AI5v417E.bin -------
2.6 SR6 AI3v046E.bin AI5v417E.bin -------
2.6 SR6A AI3v046E.bin AI5v417E.bin -------
2.6 SR7 AI3v046E.bin AI5v417E.bin -------

2.4 Additional Execs

Please see our web page www.schneider-electric.com for any updates to these executives.

page 5 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

3 Quality improvement and bug fixing

The following issues have been fixed in Service Release 7.

3.1 Configuration

3.1.1 Cannot configure ADM-850-10 / ADO-830-30 within Momentum I/O bus drop

Problem Description:
Momentum modules 170-ADM-850-10 and 170-ADO-830-30 can be configured within local drop
but not within I/O bus drop.

Affected module:
Sysnfdb.s*

3.1.2 OK button in DCP drop dialog doesn’t work

Problem Description:
In PLC Configuration open the I/O Map Configuration and create a DCP drop. The OK button to
accept the settings in the DCP drop dialog box doesn't work, when any registers are configured.

Affected module:
Config.dll

3.2 Export / Import

3.2.1 Project export with Concept Converter fails

Problem Description:
Under special circumstances the export of a Concept-project with the Concept-Converter is
aborted with the error-message "Section xxx (Typ xxx) export not implemented". The Export file
is incomplete and can’t be used.

Affected module:
Ai.dll

3.3 Execs

3.3.1 Checksum calculation for IEC Execs

Description:
A new IEC checksum calculation during Runtime has been introduced in the Quantum PLC
Exec.

Behaviour with new PLC Exec

• If there is an inconsistency in the IEC application storage structure, the PLC stops with stop-
code 0004.
• The runtime heap check increases the PLC cycle time (not more than 1 millisecond)

page 6 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

• The size of the downloadable EXEC firmware file is now 400KB (392KB before).

NOTE:
• The available application memory is not affected by the bigger EXEC size.
• Since the runtime check is time-sliced, a corruption of the heap is not immediately detected.
The worst time needed to detect a defect depends on the size of the application i.e. mainly on
the number and size of the program sections.

User action:
Update the PLC firmware to enable the IEC checksum calculation.

Affected module:
Platform PLC Name Firmware
PLCSim32 Plcsim32.exe
Quantum 140 CPU x34 1xA Q5RV143E.bin
140 CPU 534 14B Q5BV115E.bin

3.4 Documentation improvements

3.4.1 Compact I/O’s from Modsoft are not converted

Problem Description:
When importing a Modsoft project for a Compact PLC with the Modsoft Converter, the I/O
modules of the Compact are not imported in the Concept project. When starting conversion, you
are asked for a CPU. If the Modsoft CPU type is not known in Concept, you have to select a
compatible Concept CPU, but in this case the I/O modules are not converted. This behavior is
not described.

Affected module:
Concman.hlp, Modcvt.hlp

3.4.2 Ethernet I/O scanner dialog

Problem Description:
In the “Ethernet I/O scanner” dialog the documentation about the following topics has been
improved.
• Diagnostic block / Device Control block
• Repetition rate
• Setting Ethernet Address parameter

Affected module:
Concman.hlp, Conccont.hlp

3.4.3 PLC selection dialog

Problem Description:
In the Context help of the “PLC selection dialog” the section “Number of I/O maps allowed with
stripped Quantum CPUs” contains a table, which is incomplete.

Affected module:
Concman.hlp

page 7 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

3.4.4 Compact I/O module documentation

Problem Description:
The compact module VRC/ CTR2xx requires three registers for input / output data. The Online
documentations states, that 9 input and 1 output register is necessary. This is not correct and
needs to be corrected.

Affected module:
Comp_EA.hlp

4 Known issues that are not solved with this Service Release

Variable Editor and DTY-File

The project contains user defined global data types. The Variables have init values.
If the user copies the global DTY file to the local DFB folder, then the init values in the Variable
Editor are lost.
Introducing a new DTY file into a project leads to NOT EQUAL. There is no problem if DDT/INC
files are used instead of DTY.

Section Export
The Section Export of FBD sections to ST/IL doesn’t export the logic which is linked to EN/ENO
pins. The user gets the message that EN/ENO pins are ignored; the related logic will not be
exported.

Health Bit of Ethernet I/O

The Health bit of Ethernet I/O modules doesn’t work, if the Timeout value in the Ethernet I/O
scanner configuration is Zero.

Re-Enabling of Disabled Variables in RDE of mixed LL/ IEC applications

In mixed applications the re-enabling of Disabled Variables (deleting checkmark in disable
column) behaves different to IEC only.
It is recommended to download in two steps: First Download the Configuration and the LL984
logic, than download the IEC logic. This will lead to a correct Release of Disabled Variables.

WIN-NT, no virtual ModbusPlus driver installed

In order to pass program execution to the ModbusPlus device driver, Concept (and Modsoft)
triggers an MSDOS software interrupt. The default interrupt number for this job is 5C(hex).
If no virtual ModbusPlus driver is installed, the virtual MSDOS environment under Windows NT
will have problems with this interrupt. If an exception occurs under described circumstances
change the interrupt number to 5D(hex) in the MODICON.INI:
[PORTS]
mbp0=5d
If interrupt 5D is caught by the NTVDM.exe the exception fault should no longer occur.

ESI 062 and NOA 611 in the local rack

If ESI-062-00 has a lower slot position in the local rack than NOA-611-xx the IBS communication
will stop after some minutes (2-20min.).
The behavior is not observed if NOA-611-xx has a lower slot position than ESI-062-00.

page 8 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

NOA 622
The Generic Bus Table (GBT) is limited to 64 KB!

HLI 340
In case the 140-HLI-340-00 is used it is necessary to power cycle the PLC after loading a new
executive to the PLC.
Otherwise it might happen that the CPU doesn't recognize the HLI signal changes.

Hot Stand By
SET_TOD is not running properly in the first section of a Quantum Standby PLC.
If the SET_TOD is programmed in the first executed section and the PLC clock registers are
configured to the Non Transfer Area, then the Standby PLC clock will be synchronized.
PLC clock registers are configured to the Non Transfer Area.
The SET_TOD is programmed in the first section and will be activated each 3s.
However the Standby PLC clock will be synchronized sporadically (a few minutes).

Download Changes must be done with the Primary Controller, not with the Standby controller.
To get identical applications in Primary and Standby controller the user has to perform the XFER
mechanism.

Start behavior of digital outputs mapped to 4x registers

In principle all digital outputs mapped to 0x registers are cleared when the controller starts. 4x
registers are normalized with the download of the configuration! However if digital outputs are
mapped to 4x registers the output value depends on the current value of the assigned register.

Uploading a project with DFBs having ST sections from Concept 2.5 might not possible
Until Concept 2.5 SR2, DFBs could be precompiled in ‘large mode’ and in ‘small mode’.
Since Concept 2.6 SR1 DFBs are always precompiled in the 'large mode'.

Projects with DFBs having ST sections will have problems during Upload, if a PLC contains a
DFB from Concept 2.5 precompiled in ‘small mode’, because for Uploading a project to Concept
2.6 all DFBs are expected to be precompiled in ‘large mode’

Because Uploading to Concept 2.6 with such projects is not possible, customers have to force
that the project will be precompiled in ‘large mode’. This can be done with:

• export and import again the whole project by the Concept-Converter

or
• select 'Concept---Project--Update data types in nested DFBs' in Concept2.6

GPF might occur under Windows NT, if calling other programs out of Concept
Calling programs like Congrat, PlcSim32, Sycon or Ccverinf out of Concept 2.6 might lead to a
GPF under Windows NT. If this happens, call these programs separately before invoking
Concept.

IEC Upload doesn't update unlocated init values, which have been changed via
Advanced Monitor window.
The advanced monitor accesses the online database on the PLC and can update the intitial
values in the Concept database. However it does not update the PLCs upload information. This
means, that in case of an IEC upload from the PLC, the intial values changed via the Advanced
Monitor Editor will be overwritten by the initial values from PLC Upload of the Concept Database.

page 9 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

The only possibility to change the initial values in the IEC Upload information of the PLC is via
the complete download (during stopped PLC) using the "ALL" button in the download controller
menu.

SFC initial step and SFCCNTRL function block

The SFCCNTRL function block doesn't reset the Initial step, if the input RESETSFC is already
TRUE in the first scan after download and PLC start.

Workaround:
The RESETSFC input must be linked with the inverted output COLD (Cold-start flag) of the
SYSSTATE function block (see picture).
(If there are actions linked to the Initial Step, they also need to be linked with the COLD start
flag, so that they are not activated in the first PLC scan)

PID function blocks PID, PID1, PIDP1

If the function block PIDP1, PID1 or PID is used as PI controller and the value at the input SP is
already set in the first PLC scan, then the proportional component isn’t working.

Workaround:
The input value SP or KP of the PIDP1 must be zero in the first PLC scan. Please do not assign
init values >0 to the variable connected to these inputs.

5 CC2CAT Installation

Mandatory adjustment in Concept

CC2CAT requires that Concept generates/updates the “.VAR” file during a manual or automatic
save operation. The export of variables to the “.VAR” file needs to be enabled by an entry in
section ‘Common’ in CONCEPT.INI:
[Common]
ExportVariables=1

Installation hints for CC2CAT

CC2CAT provides COM interfaces for other applications and allows access to Concept's project
and variable information.

page 10 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

The functionality of CC2CAT has been extended and adapted to Concept V2.5/V2.6 so that the
upgrade from a previous version of Concept also requires an upgrade of CC2CAT.

Applications using a previous version of CC2CAT (for Concept V2.1x/2.2) need to be modified
due to Concept V2.5/V2.6 new features and the modified addressing mode for variables and
structures.

CC2CAT for Concept V2.5/V2.6 is installed optionally in a subdirectory (\CC2CAT) of the

Concept install path. The install program makes all the necessary entries in the Windows
registry.
Applications using CC2CAT must take into account all the changes compared to previous
versions of Concept and of CC2CAT mentioned above!

The entries in the Windows registry need to be changed, if CC2CAT is to be used with an
earlier version of Concept or vice versa!
All applications using CC2CAT (e.g. OPC-Factory-Server, OFS) as well as CC2CAT itself must
be closed before changing the registry entries!

You have installed CC2CAT (new) for Concept V2.5/V2.6. Now you want to activate an older
version of CC2CAT (old) for an older version of Concept.
The following example demonstrates the steps and the commands needed to be carried out in
order to manually modify the registration of CC2CAT:
1. Remove the "new" CC2CAT Windows registry information:
C:\CONCEPT2.5\CC2CAT\CC2CAT32.EXE -Unregserver
2. Go to the "old" Concept directory (version prior to Concept V2.5 SR1)
and register the "old" CC2CAT version:
C:\CONCEPT_ALT\ CC2CAT.EXE -Regserver

If you wish to undo the registration of the "old" CC2CAT and work again with the "new" Concept
V2.5/V2.6, simply reverse the order of de-registration and registration of the different versions or
CC2CAT:
1. Remove the "old" CC2CAT Windows registry information:
C:\CONCEPT_ALT\ CC2CAT.EXE -Unregserver
2. Change to the "new" Concept directory and re-register:
C:\CONCEPT2.5\CC2CAT\CC2CAT32.EXE -Regserver

The following files must be installed after CC2CAT is successfully installed:

\CC2CAT\CC2CAT32.EXE
\CC2CAT\TXTCOMP32.DLL
\CC2CAT\TXTBASE32.DLL
\CC2CAT\CCINTERN.DTY

Remark:
In some cases the registration of CC2CAT fails due to the fact that some system-DLLs are
active and could not be replaced. If this happens, please reboot your PC and try to install
Concept again. These DLLs will be replaced automatically after rebooting the PC.

6 Restrictions for Concept usage on Windows Vista and Windows 7

6.1 General conditions for installation and authorization of Concept

Problem Description:
To install Concept you need to be logged in as an Admin user, otherwise you do not have the
right user privileges and the install will not proceed.
To authorize Concept you have to Run the authorization process as Administrator (Right-click
the program file (for example: Concept or Saautor.exe), and then click Run as administrator.

You will find more information about that topic on following Web sites:

page 11 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

http://support.microsoft.com/kb/922708/en-us
http://en.wikipedia.org/wiki/User_Account_Control

6.2 Unable to open Help files that require the Windows Help program

Problem Description:
Since Windows 3.1, Microsoft included the Windows Help program (WinHlp32.exe) with new
releases. WinHlp32.exe is used to view 32-bit Help files that have the “.hlp” file name extension.
Starting with the release of Windows Vista and Windows Server 2008, Microsoft has decided to
no longer include in WinHlp32.exe as a component of the Windows operating system. Microsoft
made this decision because WinHlp32.exe has not had a major update for many years, and it
does not meet Microsoft’s standards for all new Microsoft programs. Microsoft realizes that this
may cause some difficulties for customers who want to upgrade to Windows Vista or to
Windows Server 2008 but still rely on 32-bit “.hlp” files. Therefore, Microsoft offers
WinHlp32.exe as a download from the Microsoft Download Center.
Starting with the release of Windows Vista, third-party software developers are no longer
authorized to redistribute WinHlp32.exe with their programs.

User action:
Download “WinHlp32.exe” for Windows Vista and Windows 7
To download the WinHlp32.exe visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkID=82148

Affected module:
Winhlp32.exe

6.3 Adobe Reader 9 needed for reading PDF files under Windows Vista and
Windows 7

Problem Description:
Third-party software developers are no longer authorized to redistribute Adobe Reader 9 with
their programs.
To get a free version of Adobe Reader 9 users have to download it from Adobe.com.

User action:
Download Adobe Reader 9 for Windows Vista or Windows 7 from the following Web site
http://www.adobe.com

6.4 Unable to show ‘Readme’ during installation of V2.6 basic version

Problem Description:
The install of Service Release 7 requires at least an installed Concept V2.6 basic version. During
the installation of the basic version it’s not possible to see the Readme-file, because the
program used to show the Readme isn’t compatible with Windows Vista / Windows 7.

User action:
Deselect option for showing “ReadMe” at the end of the installation of the Concept V2.6 basic
version. The “ReadMe” file for the basic version can be found on the SR7 documentation CD.

page 12 of 13 10.02.2011
 Release Notes Concept V2.6 SR7

6.5 Error message after SR7 installation

Problem Description:
Even if the installation of the Service Release 7 was successfully, you may see the error-
message “This program might not have been installed correctly” under Windows 7.

User action:
Please select the option “This program installed correctly” to finish the installation.

6.6 MBX Driver Suite for Windows 7

Problem Description:
For the Modbus Plus communication under Windows 7 the new MBX driver suite V7.1 need to
be installed. The new driver supports 32 Bit and 64 Bits Windows 7 versions.

User action:
Install MBX driver Suite V7.1 for Windows 7 from http://www.schneider-electric.com

6.7 Connection to Simulator might be lost

Problem Description:
In some cases the connection to the Simulator might be lost. An error message “Time-out
waiting for response from controller (Get Value Response) Error ID OLI-21744” occurs.

User action:
Reconnect to Simulator

page 13 of 13 10.02.2011