User Manual

Exchanging a V3.0 CPU for a V4.0 CPU
B.1 Exchanging a V3.0 CPU for a V4.0 CPU
Easy Book
346 Manual, 03/2014, A5E02486774-AF
Web server
If you exchange a V3.0 CPU for a V4.0 CPU, your Web server project settings for activating
the Web server and whether or not to require HTTPS access will be the same as they were
in V3.0. You can then configure users, privileges, passwords (Page 193), and languages as
needed to use the Web server. If you do not configure users with additional privileges, then
you are limited as to what you can view from the standard Web pages (Page 194). The S7-
1200 V4.0 CPU does not support the former pre-configured "admin" user and password.
Formerly, the Data log Web server page provided a "Download and Clear" operation. The
V4.0 Web server File browser page (Page 194), from which you access data logs, no longer
provides this feature. Instead, the Web server provides the ability to download, rename, and
delete data log files.
Transfer card incompatibility
You cannot use a V3.0 transfer card (Page 58) to transfer a V3.0 program to a V4.0 CPU.
You must open the V3.0 project in STEP 7, change the device to a V4.0 CPU (Page 74), and
download the STEP 7 project to your V4.0 CPU. After you have changed your project to a
V4.0 project, you can then make a V4.0 transfer card for subsequent program transfers.
GET/PUT communication
By default, GET/PUT communication was enabled in V3.0. When you replace your V3.0
CPU with a V4.0 CPU (Page 74), you see a message in the compatibility information section
stating that GET/PUT is enabled.
Motion control support
S7-1200 V4.0 CPUs do not support the V1.0 and V2.0 motion libraries. If you perform a
device exchange for a STEP 7 project with V1.0 or V2.0 motion libraries, the device
exchange substitutes compatible V3.0 motion control instructions (Page 217) for the V1.0 or
V2.0 motion library instructions at compile.
If you perform a device exchange for a STEP 7 project that contains two different motion
control instruction versions (V3.0 and V4.0), the device exchange substitutes compatible
V4.0 motion control instructions (Page 217) at compile.
During a device exchange from V3.0 to V4.0, the motion control Technological Object (TO)
version automatically changes to V4.0. The TO structure is different between V3.0 and V4.0.
All associated blocks change as well. Block interfaces, watch tables, and traces update to
the new V4.0 structure. You can find the differences between the V3.0 and V4.0 motion
control axis parameters in the following two tables:
V3.0
V4.0
Config.General.LengthUnit
Units.LengthUnit
Config.Mechanics.PulsesPerDriveRevolution
Actor.DriveParameter.PulsesPerDriveRevolution
Config.Mechanics.LeadScrew
Mechanics.LeadScrew
Config.Mechanics.InverseDirection
Actor.InverseDirection
Config.DynamicLimits.MinVelocity
DynamicLimits.MinVelocity