Filter
Top Products
178
FINS/TCP Method Section 7-4
When automatically allocated FINS node addresses are set, the client node
address automatically allocated at the server is stored in the client node
address field.
After a connection has been established as a FINS/TCP client or server, do
not send this command again. Otherwise, the error code (00000003 hexadec-
imal: The command is not supported) will be received in the FINS FRAME
SEND ERROR NOTIFICATION command and the connection will be termi-
nated.
The details of the above frame are shown in the following table.
The following table shows the list of error codes.
FINS FRAME SEND
Command
When FINS frames are sent using TCP/IP, always add the FINS FRAME
SEND command to the beginning of the FINS frame. The FINS frame is sepa-
rated out from the TCP data line following the data length in the FINS FRAME
SEND command.
Item Contents (hexadecimal) Remarks
Header 46494E53 ASCII code: ‘FINS’
Length 00000010 16 bytes: Length of data from
command onwards.
Command 00000001
Error code --- Refer to the following table of
error codes.
Client node address
(FINS node address
of FINS/TCP client)
00000001 to 000000FE 1 to 254
Server node address
(Fins node address
of FINS/TCP server)
00000001 to 000000FE 1 to 254
Error code
(hexadecimal)
Details
00000000 Normal
00000001 The header is not ‘FINS’ (ASCII code).
00000002 The data length is too long.
00000003 The command is not supported.
00000020 All connections are in use.
00000021 The specified node is already connected.
00000022 Attempt to access a protected node from an unspecified IP
address.
00000023 The client FINS node address is out of range.
00000024 The same FINS node address is being used by the client and
server.
00000025 All the node addresses available for allocation have been
used.
Header
Lengt
h
Command
Error code
Server node address
Size
(bytes)
FINS/TCP header
4
4
4
4
4
4
Client node address