hilscher DTM Bedienungsanleitung Seite 128

Fehlercodes
CIP Connection-Manager-Object-Instance Codes zum Erweiterten Status
Allgemeiner Erweiterter
Status (hexa Status
dezimal)
0x010A
0x01
through
0x010F
0x01 0x0110
0x01 0x0111
0x01 0x0112
DTM für EtherNet/IP-Scanner-Geräte | Konfiguration von EtherNet/IP-Scanner-Geräten
DOC061201OI07DE | Revision 7 | Deutsch | 2013-09 | Freigegeben | Öffentlich
Beschreibung
Reserved by CIP
TARGET FOR CONNECTION NOT CONFIGURED
This extended status code shall be returned when a connection is requested to a
target application that has not been configured and the connection request does
not contain a data segment for configuration. Only a target node shall return this
extended status code. Reference section C-1.4.5 — DATA SEGMENT
[Ref.] THE CIP NETWORKS LIBRARY, Volume 1
RPI NOT SUPPORTED.
This extended status code shall be returned if the device can not support the
requested O->T or T->O RPI. This extended status code shall also be used if the
connection time-out multiplier produces a time-out value that is not supported by
the device or the production inhibit time is not valid.
Note: it is highly recommended to use Extended Status 0x112 when the RPI
values(s) are not acceptable.
RPI VALUE(S) NOT ACCEPTABLE
This error is to be returned when the RPI value(s) in the forward open request are
outside the range required by the application in the target device or the target is
producing at different interval, The target shall include information with acceptable
RPI(s). for this error, the extended status size is 6 16-bit words and is formatted
as follows:
Data Type Value
UINT 0x0112
USINT variable
UDSINT variable
Explanation of field
Extended status code
Acceptable Originator to Target RPI (see below) type,
values:
0 — the RPI specified in the forward open was
acceptable (the Originator to Target RPI value is
1
ignored).
1 — unspecified (used to suggest an alternate RPI,
e. g. default)
2— minimum acceptable RPI (used when RPI was
too fast for range)
3 — maximum acceptable RPI (used when RPI was
too slow for range)
4— required RPI to correct mismatch (used when
data already being consumed at a different interval)
5-255 — reserved
Acceptable Target to Originator RPI (see below) type,
values:
0— the RPI specified in the forward open was
acceptable (the Target to Originator RPl value is
1
ignored).
1 — unspecified (used to suggest an alternate RPI,
e.g. default)
2— minimum acceptable RPI (used when RPI was
too fast for range)
3 — maximum acceptable RPI (used when RPI was
too slow for range)
4— required RPI to current mismatch (used when
data already being produced at a different interval,
typically multicast)
5-255— reserved
128/154
© Hilscher, 2006-2013