Chapter 6. COMMREQ/Data_Init_Comm Programming
GFK-2892F
March 2019
57
The upper word of the status location provides additional status information
VALUE
decimal
(word)
VALUE
Hex
(word)
DESCRIPTION
0
0
Command has not been processed.
1
1
Non-specific command failure.
2
2
Null or invalid command block.
3
3
Unknown Task ID detected. Task ID should be 132 for Gateway COMMREQs, or 131 for generic
PROFINET acyclic requests.
4
4
Command completed successfully.
5
5
Incorrect command block length.
10
0x0A
Unknown command number.
11
0x0B
Invalid PROFINET device number. Number should be in the range 1 through
MAX_PROFINET_IO_DEVICE_CONNECTIONS (model-specific definition).
12
0x0C
PROFINET device is ‘undeclared’. The PROFINET device specified in the command block is not
known to the PNC as currently configured.
13
0x0D
PROFINET API value is out of range. The value should be 0 or 1 (always 0 for Gateway requests).
14
0x0E
PROFINET slot value is out of range. The value should be in the range 0 through 31 (Gateway
requests normally use 31, except when using read index 0x0203).
15
0x0F
PROFINET subslot value is out of range. Gateway requests always use subslot 1. Generic acyclic
requests test for a subslot value in range 1 through 32784.
16
0x10
Invalid transfer length specified. Value is either too large, or zero.
17
0x11
PROFINET stack interface failure; read_req call failed at invocation site.
18
0x12
Error returned from PROFINET stack; a generic acyclic request issued a read_req call that
produced a negative confirmation callback.
19
0x13
PROFINET stack interface failure; write_req call failed at invocation site.
20
0x14
Error returned from PROFINET stack; a generic acyclic request issued a write_req call that
produced a negative confirmation callback.
21
0x15
Invalid Genius device number. Value should be in range 0 through 31.
22
0x16
Invalid circuit number. Value should be in range 1 through 32.
23
0x17
Error returned from PROFINET stack; a Gateway request issued a write_req call that produced a
negative confirmation callback.
24
0x18
Error returned from PROFINET stack; a Gateway request issued a read_req call that produced a
negative confirmation callback.
25
0x19
Last write request to the Gateway timed out or had an error. When Gateway status was
checked (via read index 0x0200), the returned value was 2.
26
0x1A
Last write request to the Gateway caused a
stuck busy
result. Gateway status checks (via read
index 0x0200) have returned a value of 1 for more than 300 msec.
27
0x1B
Gateway status check (via read index 0x0200) returned an invalid value (not 0, 1, or 2).
28
0x1C
Error returned from PROFINET stack; an attempt to retrieve a Genius Reply from the Gateway
(via read index 0x0201) produced a negative confirmation callback.
29
0x1D
The message status byte associated with a Genius Reply is not 0, indicating a problem.
30
0x1E
A Genius Reply does not have the expected length.
31
0x1F
A Write Configuration COMMREQ specified a configuration data length that does not match the
required configuration length for the device.
32
0x20
A Read Block I/O COMMREQ specified an invalid offset value.
33
0x21
An internal error has been detected in the PNC COMMREQ firmware.
34
0x22
The COMMREQ request is not supported by the specified Genius device.
35
0x23
The data type code specified for a Read Data or Write Data COMMREQ does not have a value
recognized by the High-Speed Counter.
