SIMATIC

S7-1200 System Manual

Update to edition 05/2009
Product Information

In spite of efforts to ensure the accuracy and clarity in the product documentation, some of the pages in the S7-1200
Programmable Controller System Manual contain information that has been identified as being incomplete, incorrect or
misleading.

An interrupt event with no attached OB

When you configure the PLC, you can configure interrupt events to occur (for example, for the HSC or for edge-detection of
digital inputs). You have the option to associate the event with an interrupt OB during configuration, or you can also use an
Attach instruction in your program to associate an event with an interrupt OB.
If the interrupt event occurs but cannot find an attached OB, the following message might be written to the diagnostics
buffer: "Accepted number of pending OB 0 - events exceeded - Processing continued (no OB processing)"
When troubleshooting, check the following possible causes for this message:
● An interrupt event was enabled but not associated with an interrupt OB in the device configuration, and the user program
did not include an Attach instruction to associate the event with an interrupt OB.
● A Detach instruction in the user program removed the association with the interrupt OB.
If you receive this message, ensure that all events are correctly attached to an interrupt OB.

Booleans and Boolean arrays are not allowed for TRCV/TRCV_C and PtP instructions
The use of Boolean data or Boolean arrays is not allowed for the TRCVand TRCV_C instructions and for the point-to-point
(PtP) instructions.

GET_ERROR instruction always returns a 0 for the FLAGS byte

In the description of the of the data structure for the ERROR parameter of the GET_ERROR instruction (Section 6.2.3.3), the
description of the FLAGS byte states that a value of "1" determines that an error occurred during a call to another block.
However, the GET_ERROR instruction always returns a value of "0" for the FLAGS byte.

"Diagnostics changed" bit is not available during startup or the first scan cycle
Because the CPU does not set the "diagnostics changed" bit until the end of the first execution of the of the program cycle
OBs, your program cannot detect if there has been a diagnostic change either during the execution of the startup OBs or the
first execution of the program cycle OBs.

Attempting to force I/O on a write-protected memory card causes an error

If the user program on a write-protected memory card is being executed by the CPU, you cannot initiate or change the
forcing of I/O from a watch table because you cannot override the values in the write-protected user program. Any attempt to
force the write-protected values generates an error.

Procedure for accessing the properties of a card reader

In section 3.4.2 that describes how to create a "Program" card, the procedure is incorrect. After you expand the "SIMATIC
card reader", you must also expand the card reader device. Select the drive where you inserted the memory card. Right-click
the drive to display the context menu and select "Properties". From the drop-down menu for "Card type" of the "Properties"
dialog, select "Program".

Password-protection of specific blocks or instructions

Section 3.1.4 of the S7-1200 System Manual incorrectly implies that access to the CPU can be password-protected for an
individual instruction, such as the "Set time of day/date" instruction. However, you can only password-protect access for the
complete CPU.

© Siemens Ⓟ2009
A5E02573237-01, 05/2009 1
Condition codes for the T-blocks
The following condition codes for the PROFINET instructions ("T-blocks") were omitted from section 6.2.4 topic
"Communications instructions" in the S7-1200 system manual:
STATUS (W#16#...) Explanation
8070 All internal instance memory is in use
8080 The identifier entered for the communications port is invalid
8081 Timeout, module error, internal error
8090 Message length invalid, module invalid, message invalid
8091 Incorrect version in parameterization message
8092 Invalid record length in parameterization message

Error in the description of the BCD data type

The description of the ranges of the BCD data type in Section 3.3 "Data Types" contains typographical errors. Please correct
the table as follows:
Format Size (bits) Numeric Range Constant Entry Examples
BCD16 16 -999 to 999 123, -123
BCD32 32 -9999999 to 9999999 1234567, -1234567

Updating the clock memory and the system memory

Section 3.1 of the S7-1200 System Manual incorrectly states that the bytes used for system memory and clock memory are
initialized at the beginning of the scan cycle. However, the CPU initializes these bytes on the transition from STOP mode to
STARTUP mode, and the bits of the clock memory change synchronously to the CPU clock throughout STARTUP and RUN
modes.

Description of the parameters for the Set and Rest Bit Field instructions
The description of the output parameter for the Set and Reset Bit Field instructions (SET_BF and RESET_BF) in Section
6.1.1.1 is incorrect. Please use the following table to update the data type and the description for these instructions.
Parameter Data type Description
OUT Boolean array element Starting element of bit field to be set or reset.
Example: #MyArray[3]

Exceeding the maximum pulse frequency with the basic motion control instructions

NOTICE
As described in the S7-1200 System Manual, the maximum pulse frequency of the pulse output generators is 100 KHz for
the digital outputs of the CPU and 20 KHz for the digital outputs of the signal board. However, STEP 7 Basic does not alert
you when you configure an axis that with a maximum speed or frequency that exceeds this hardware limitation. This could
cause problems with your application, so always ensure that you do not exceed the maximum pulse frequency of the
hardware.

Pulse-train outputs cannot be used by other instructions in the user program

When you configure the outputs of the CPU or signal board as pulse generators (for use with the PWM or basic motion
control instructions), the corresponding outputs addresses (Q0.0, Q0.1, Q4.0, and Q4.1) are removed from the Q memory
and cannot be used for other purposes in your user program. If your user program writes a value to an output used as a
pulse generator, the CPU does not write that value to the physical output.

Update to edition 05/2009

2 A5E02573237-01, 05/2009
Complex structures with the Send_PtP instruction
When transmitting a complex structure with the Send_PtP instruction, always use a length of 0.

Correction to the descriptions of the parameters for the USS_DRV instruction

Section 6.3.1.2 (USS_DRV instruction) incorrectly describes the parameters OFF2 (electrical stop bit) and OFF3 (fast stop
bit). Please correct the manual as follows:
● OFF2 (electrical stop bit): When false, this bit causes the drive to coast to a stop and uses no braking.
● OFF3 (fast stop bit): When false, this bit causes a fast stop by causing braking the drive rather than just allowing the
drive to coast to a stop.
For the STATUS parameter, the description should read: "The status value of the request. It indicates the result of the scan."
Please disregard the reference to "drive status word 2".

Extended error codes for the USS drive instructions

Section 6.3.1.6 (USS status codes) omits hexadecimal extended error codes 8180, 8184, 8187, and 818B that are relevant
to storing the drive error code into the USS_Extended_Error variable. In the paragraph that describes the extended error
codes, the manual currently states that the "drive error code is put into the USS_Extended_Error variable when the STATUS
code value is hexadecimal 808C". The hexadecimal error codes 8180, 8184, 8187, and 818B also update the
USS_Extended_Error variable.

Communication connection via ISO-on-TCP

When configuring a connection with an S7-1200 controller via ISO-on-TCP, use only ASCII characters in the TSAP
extension for the passive communication partners.

Forcing the physical inputs and the process image inputs

Section 3.2 ("Data storage, memory areas and addressing") incorrectly describes forcing for the inputs (the I memory area).
You can force an immediate read of the physical input points ("I_:P"), and you cannot force the process image for the inputs.
Refer to the following table.
Memory area Description Force Retentive
I Copied from physical inputs at the beginning of the No No
Process image input scan cycle
I_:P Immediate read of the physical input points on the Yes No
(Physical input) CPU, SB, and SM

Behavior of the CPU when time error interrupt OB 80 is not present

The description under "Monitoring the cycle time" in Section 3.1.2 ("Event execution priorities and queuing") incorrectly
describes the behaviour of the CPU for the time error interrupt (OB 80). Whenever a scan exceeds the maximum cycle time,
an error is generated. If the user program does not include OB 80, however, the CPU does not automatically go to STOP
mode, but instead ignores the error.

Ad hoc mode for TCP and ISO-on-TCP is not supported

The "ad hoc" mode is not supported by the S7-1200. This affects the descriptions of the TSEND_C, TSEND, TRCV_C and
TRCV instructions in Section 6.2.4.2 "Open Ethernet communication".

Usage of the TCON, TSEND, TRCV, TSEND_C and TRCV_C instructions

Use the TCON, TSEND, TRCV, TSEND_C and TRCV_C instructions only in the program cycle OB (OB 1).

Update to edition 05/2009

A5E02573237-01, 05/2009 3
Siemens AG
Industry Sector
Postfach 48 48
90026 NÜRNBERG

Update to edition 05/2009 Update to edition 05/2009

4
A5E02573237-01, 05/2009 A5E02573237-01, 05/2009