Siemens FEC920 User Manual page 106

0 Success. Service was successful
1 Connection Failed. A connection in the path failed
2 Invalid Parameter. A parameter associated with the request was invalid
3 Memory Unavailable. No available resources in the server to service the request
4 Path Segment Error. The syntax of all or some of the path was not understood
5 Path Dest. Error. The path references an unknown object, class or instance
6 Partial Transfer. Only part of the expected data was transferred
7 Connection Lost. The messaging connection was lost
8 Service Unsupported. Undefined service for requested object
9 Invalid Attribute. Invalid attribute data detected
10 Attribute Error. An attribute in the response has a non zero status
11 Already Requested. The object is already in the mode/state being requested
12 Object Conflict. The object cannot perform the requested service
13 Already Exists. The requested instance or object already exists
14 Attribute Error. Request to modify a non modifiable attribute received
15 No Privileges. Permission/Privilege check failed
16 State Conflict. The current state or mode prohibits the execution of the requested service
17 Reply To Large. Response buffer too small for response data
18 Fragmented Value. For example this service request will return only half a REAL data type
19 Not Enough Data. The service does not provide enough data to complete the request
20 Invalid Attribute. Requested attribute is not supported
21 Too Much Data. The service supplied more than was expected
22 Object Non-Exist. The object specified does not exist in the device
23 Seq. Fragmentation. The fragmentation sequence for this service is not active
24 No Attribute Data. The attribute data for this object was not saved at the server prior to this request service
25 Data Store Failure. The attribute data for this object was not saved due to a failure during the attempt
26 Routing Failed. The service request packet was too large for transmission on a network in the path to the
destination. The routing device was forced to abort the service
27 Routing Failed. The service request packet was too large for transmission on a network in the path to the
destination. The routing device was forced to abort the service
28 Missing Attribute. The service did not supply an attribute in a list of attributes that was needed by the service to
perform the requested behavior
29 Invalid Attribute. The service is returning the list of attributes supplied with status information for those attributes
that were invalid
30 Embedded Tag Error. An embedded service resulted in an error. This is most commonly an incorrectly formatted
tag name
31 Vendor Error. A vendor specific error has encountered
32 Invalid Parameter. A parameter associated with the request was invalid
33 Write Once Error. An attempt to write to a write once only parameter occurred
34 Invalid Reply. An invalid reply was received
35 Buffer Overflow. The message received is larger than the receiving buffer
36 Format Error. The format of the received message is not supported
37 Key Path Failure. The key segment in the path does not match destination key
38 Path Size Error. The size of the path in the request is too large
39 Unexpected Attribute. Unable to set the attribute at this time
40 Invalid Member Id. The requested member id does not match class object
41 Member Is R/O. A request to modify a R/O member was received
42 Group 2 Server. Group 2 DeviceNet server response
43 Translation Error. A CIP Modbus translator request failed
44 Attribute Is R/O. A request to read a non readable attribute was received
64 No Tags Found. There were no tags configured in the input or output tables
65 Invalid Config. The total length in characters of all the tags in this table will cause the PLC to exceed its internal
buffer of 500 bytes. To eliminate this problem, reduce the length of some or all tag names
Page 98
FEC920: USER GUIDE
Figure 87 Tag Status code definition
A5E45696052A Rev-AA
September 18