OMFINS Specific Errors
- Last UpdatedDec 13, 2021
- 5 minute read
When a hardware error occurs, Plant SCADA generates an alarm, and displays the alarm on the hardware alarm page (in the alarm description of the hardware alarm). To see the error number, you need to have Alarm Category 255 defined with a display format that includes {ErrDesc,15} {ErrPage,10} .
There are a number of generic errors that are common to many protocols. In some cases, only the generic error is available, though often both the generic error and a specific error are given.
The following errors, listed in (hexadecimal) sequence, are specific to this protocol. Plant SCADA displays the error number and description for common protocol-specific errors. Uncommon errors are not contained in the Plant SCADA error database, in which case Plant SCADA will only display the error number.
You may require additional information to enable you to rectify an error. This information should be detailed in the documentation that accompanied the I/O Device (or network). If, after reviewing the documentation, you cannot rectify an error, contact Technical Support for this product.
Messages return a FINS response code. This is two bytes, the main response code and the sub-response code. Response codes are shown in the second table presented. If bit 6 or 7 of the sub-response code is on, the error has occurred in the PC returning the response. If the main response code has bit 7 set, a network relay error has occurred - in this case a further two words will be returned to the driver indicating the location of the error. In the following table response codes are listed in hexadecimal, with xx indicating any value here will return the same generic errors. The two-byte response code will be returned as the Plant SCADA driver error (except for 0001, which will be returned as -1).
Response codes (hex) |
Plant SCADA generic error |
|
0000 |
NOERROR |
|
0001 (returned as -1) |
INVALID_RESPONSE |
|
0101, 0102, 0105, 0106, 0201, 0202, 0203, 0304, 0402, 05xx, 20xx |
GENERAL_ERROR |
|
0103, 0104, 0204, 0205, 25xx |
UNIT_TIMEOUT |
|
0301, 0303, 0302, 22xx, 2301, 2303, 24xx |
HARDWARE_ERROR |
|
0401, 10xx, 11xx, 2302 |
INVALID_COMMAND |
|
21xx |
WRITE_PROTECT |
Main Code |
Sub-Code |
Probable Cause |
Remedy |
|
00: Normal Completion |
00 |
--- |
--- |
|
01:Local node error |
03 |
Send error in local node was caused by lack of available space in internal buffers |
Reduce the load (traffic) on the Ethernet Unit. Check your user applications. |
|
02: Remote node error |
01 |
IP address of remote node not set correctly in IP address table or IP router table |
Set IP address of remote node into IP address table and, if inter network transmission is required, into the IP router table. |
|
02 |
No node with the specified unit address |
Check the remote node's unit address and make sure the correct one is being used in the control data. |
|
|
05 |
Message packet was corrupted by transmission error. |
heck the protocol and controller status by reading them with FINS commands. Increase the number of transmit retry attempts. |
|
|
Response time-out, response watchdog timer interval too short. |
Increase the value for the response monitor time in the control data. |
||
|
The transmission frame may be corrupted or the internal reception buffer full. |
Read out the error log and correct as required. |
||
|
03: Communications controller error |
01 |
Error occurred in the communications controller, ERC indicator is lit. |
Take corrective action, referring to troubleshooting procedures in this section |
|
02 |
CPU error occurred in the PC at the remote node. |
Check CPU indicators at the remote node and clear the error in the CPU (refer to the PC's operation manuals) |
|
|
04 |
Unit number setting error |
Check that the unit number is specified within range and that the same unit number is not used twice in the same network. |
|
|
04: Not executable (service not supported) |
01 |
An undefined command has been used. |
Check the command code is supported by the Unit to which you are sending it |
|
A short frame (4 bytes) is being used for the FINS header frame. |
Check the FINS header frame length. The Ethernet Unit does not support short headers. |
||
|
05: Routing error |
01 |
Remote node is not set in the routing tables |
Set the remote node in the routing tables |
|
02 |
Routing tables aren't registered completely |
Set routing tables at the local node, remote node, and any relay nodes. |
|
|
03 |
Routing table error |
Set the routing tables correctly |
|
|
04 |
The maximum number of relay nodes (2) was exceeded in the command. |
Redesign the network or reconsider the routing table to reduce the number of relay nodes in the command. Communications are possible on three network levels, including the local network. |
|
|
10: Command format error |
01 |
The command is longer than the max. permissible length. |
Check the command format of the command and set it correctly. Verify that broadcast transmissions don't exceed 1,473 bytes. |
|
02 |
The command is shorter than minimum permissible length |
Check the command format of the command and set it correctly |
|
|
03 |
The designated number of data items differs from the actual number in the command data. |
Check the number of items and the data agree |
|
|
05 |
Data for another node on the same network was received from the network |
Check the header parameters in the command data, and that the correct command format is being used. |
|
|
An attempt was made to send response data for a broadcast address. |
|||
|
11: Parameter error |
00 |
The parameters in the command data were incorrect or the UDP/TCP socket number was not within the proper range. |
Check the parameters, and that the socket number is between 1 and 8. |
|
01 |
A correct memory area code has not been used or Expansion Data Memory is not available |
Check the command's memory area code and set the appropriate code. |
|
|
03 |
The first word is in an inaccessible area or the bit number is no 00. |
Set a first word that is in an accessible area. The bit number needs to be 00 for Ethernet Units. |
|
|
22: Status error |
0F |
The same socket service is already in progress at the specified socket number. |
Use the socket status flag in PC memory to check that socket service has finished before starting services again. |
|
10 |
The specified socket is not open |
Open the socket. For TCP sockets, wait until connection is made. |
|
|
23: Environment error |
05 |
IP address conversion incomplete |
Check the IP address and subnet mask in the System Setup are correct. |
|
07 |
IP address conversion is set for automatic conversion only. |
Check the mode settings in the System Setup. This error will be generated for the READ IP ADDRESS command only. |
|
|
25: Unit error |
03 |
I/O setting error (The I/O table differs from the actual Unit configuration.) |
Either change the actual configuration to match the registered one, or generate the I/O table again. |
|
05 |
CPU bus error (An error occurred during data transfer between the CPU and a CPU Bus Unit.) |
Check the Units and cable connections and send the ERROR CLEAR command. |
|
|
0A |
An error occurred during CPI Bus Unit data transfer. |
Check the Units and cable connections and send the ERROR CLEAR command. |
See 9-3 Troubleshooting via response codes of SYSMAC CV-series Ethernet System Manual pages 109-114 of FINS commands reference (section 8-3)
Example:
Plant SCADA Error 18501 response code = 0501, (main response = 5, sub response = 1)
Driver Err: 18501 for an incorrect routing table, with relay error flag set
Refers to the error bit preceding the main response code which should be masked, as per the two bits preceding the sub response code.
Thus if main = 5, sub = 1 then error 10501
Returned code: [0001][1000][0101][0000][0001] -> 18501
Mask red bits: [1111][0111][1111][0011][1111]
Presented code: [0001][0000][0101][0000][0001] -> 10501