IBM CTI 2572 Network Card User Manual


 
CTI 2572 Installation and Operation Guide
110
HEX DEC DESCRIPTION SOLUTION
247E 9342
INVALID DATA CHARACTER
The 2572 detected an invalid data character
in the message sent from the remote device.
Only characters 0-9 and A-F are allowed.
See error code 247A.
247F 9343
ODD NUMBER OF CHARACTERS
The 2572 detected an odd number of
characters in the message sent from the
remote device. All CAMP messages have an
even number of characters.
See error code 247A.
2480 9344
UNKNOWN ERROR CHARACTER
The response contained an unknown error
character.
This error is caused by an improperly
programmed server node. If the server is a
PLC emulating a 2572 server, review the code
and correct as required. If the server is
another 2572, contact CTI.
248A 9354 INVALID SERVICE TYPE
You specified an invalid value for Type of
Service. Must be 1=TCP or 2=UDP.
Correct the value in the Command Block.
248B 9355 INVALID REMOTE IP ADDRESS
You specified an invalid value for the remote
IP Address.
Correct the value in the Command Block.
2490 9360 INVALID ADDRESS CLASS
The address class is not supported by the
remote device.
If the server is another 2572, check the
firmware version of the module to ensure the
latest revision.
If the server is a PLC emulating a 2572
server, review the code and correct as
required.
2492 9362 CAMP ID MISMATCH
The response did not contain a message ID
which matched the command.
This can be caused by an improperly
programmed remote device. It can also be
caused by response delays which exceed the
command timeout value. Thus it may be a
response to a previous command.
Check the remote device for problems and
correct as required.
Determine whether you have response delays
that exceed the command timeout. You may
be able to increase the timeout value so that
the command waits longer for a response.
You can use network analyzer software to
view network traffic. See the Troubleshooting
Chapter of this manual and the CTI 2572
Installation and Operation Guide.
2497 9367 UNKNOWN COMMAND
The protocol manager received a command
number which is not valid.
Ensure that Offset 1 in the Command block
contains a valid Command Code.
Check to be sure that the Command Slot
points to the correct V memory Address for
the Command Block.
Make sure that you have specified the correct
protocol manager number in the Create
Connection command and that you are using
the right connection number.