105BCommunication processor
12.4 Universal serial interface (USS) communication
S7-1200 Programmable controller
System Manual, 11/2011, A5E02486680-05
577
STATUS
(W#16#....)
Description
8182
The user supplied a Word for a parameter value and received a DWord or Real from the drive in the
response.
8183
The user supplied a DWord or Real for a parameter value and received a Word from the drive in the
response.
8184
The response telegram from drive had a bad checksum. The drive number where the error occurred is
returned in the "USS_Extended_Error" variable. See the extended error description below this table.
8185
Illegal drive address (valid drive address range: 1 to16)
8186
The speed set point is out of the valid range (valid speed SP range: -200% to 200%).
8187
The wrong drive number responded to the request sent. The drive number where the error occurred is
returned in the "USS_Extended_Error" variable. See the extended error description below this table.
8188
Illegal PZD word length specified (valid range = 2, 4, 6 or 8 words)
8189
Illegal Baud Rate was specified.
818A
The parameter request channel is in use by another request for this drive.
818B
The drive has not responded to requests and retries. The drive number where the error occurred is
returned in the "USS_Extended_Error" variable. See the extended error description below this table.
818C
The drive returned an extended error on a parameter request operation. See the extended error
description below this table.
818D
The drive returned an illegal access error on a parameter request operation. See your drive manual for
information of why parameter access may be limited.
818E
The drive has not been initialized. This error code is returned to USS_RPM or USS_WPM when
USS_DRV, for that drive, has not been called at least once. This keeps the initialization on first scan of
USS_DRV from overwriting a pending parameter read or write request, since it initializes the drive as a
new entry. To fix this error, call USS_DRV for this drive number.
80Ax-80Fx
Specific errors returned from PtP communication FBs called by the USS Library - These error code
values are not modified by the USS library and are defined in the PtP instruction descriptions.
1
In addition to the USS instruction errors listed above, errors can be returned from the
underlying PtP communication instructions (Page 532).
For several STATUS codes, additional information is provided in the "USS_Extended_Error"
variable of the USS_DRV Instance DB. For STATUS codes hexadecimal 8180, 8184, 8187,
and 818B, USS_Extended_Error contains the drive number where the communication error
occurred. For STATUS code hexadecimal 818C, USS_Extended_Error contains a drive error
code returned from the drive when using a USS_RPM or USS_WPM instruction.
Communication errors (STATUS = 16#818B) are only reported on the USS_PORT
instruction and not on the USS_DRV instruction. For example, if the network is not properly
terminated then it is possible for a drive to go to RUN but the USS_DRV instruction will show
all 0's for the output parameters. In this case, you can only detect the communication error
on the USS_PORT instruction. Since this error is only visible for one scan, you will need to
add some capture logic as illustrated in the following example. In this example, when the
error bit of the USS_PORT instruction is TRUE, then the STATUS and the
USS_Extended_Error values are saved into M memory. The drive number is placed in
USS_Extended_Error variable when the STATUS code value is hexadecimal 8180, 8184,
8187, or 818B.