Cp343-1 And - Siemens SIMATIC S7 Manual

Error messages FB MODBUSCP
STATUS Event text
(Hex)
A006 The given range of data defined with DATA_TYPE,
START_ADDRESS and LENGTH does not exist in
data_type_1 to data_type_8.
CP is server:
The CP sends an exception telegram.
A007 CP is client:
An invalid monitoring time MONITOR is parameterized.
A value > 20ms is required.
A008 Monitoring time MONITOR elapsed when AG_RECV
waits for receipt. E.g. Partner is not ready.
MODBUSCP V2.x:
All connections via Port 502 are terminated and
reestablished.
MODBUSCP V1.x:
As an after effect the loss of synchronization can occur,
which leads to a loss of telegrams.
A009 CP is client: The received transaction identifier TI is not
equal to the sent one.
MODBUSCP V2.x:
All connections via Port 502 are terminated and
reestablished.
A00A CP is client: The received UNIT is not equal to the sent
one.
MODBUSCP V2.x:
All connections via Port 502 are terminated and
reestablished.
A00B CP is client:
Received function code is not equal to the sent one.
CP is server:
An invalid function code was received. The CP sends
an exception telegram.
MODBUSCP V2.x:
All connections via Port 502 are terminated and
reestablished.
MODBUSCP V1.x:
As an after effect the loss of synchronization can occur,
which leads to a loss of telegrams.
A00C The received byte count does not match the number of
registers/bits.
CP is server: The CP sends an exception telegram.
MODBUSCP V2.x:
All connections via Port 502 are terminated and
reestablished.
A00D Only when CP is client: The register/bit address or the
number of registers/bits in the response telegram is not
equal to the one in the request telegram.
OPEN MODBUS / TCP communication via CP343-1 and 443-1
2XV9450-1MB00; Manual edition 4.3
Diagnostics
Remedy
CP is Client:
Correct the parameter's
combination DATA_TYPE,
START_ADDRESS and
LENGTH.
CP is Server:
Modify the request of the client
or correct the parameterization
of data_type_x.
Correct the parameterization.
Verify error messages at the
communication partner.
Check if the communication
partner needs a special unit
identifier.
Verify the data of the
communication partner with the
help of a telegram trace.
CP is client:
Verify the data of the
communication partner with the
help of a telegram trace.
CP is server:
The FB MODBUSCP supports
the function codes 1, 2, 3, 4, 5,
6, 15 and 16.
Verify the data of the
communication partner with the
help of a telegram trace.
6-3