Communication protocols
PROGRAMMING MANUAL
210
R
e
vi
si
o
n
1
.0
When writing VR or TABLE:
•
xx = memory address (Most significant byte)
•
yy = memory address (Middle byte)
•
zz = memory address (Least Significant byte)
The TJ2-MC64 responds with these codes:
/i
4.2.3
FINS client protocol
Trajexia can initiate the FINS communication using the
FINS_COMMS
BASIC command. Refer to the command description for details.
Both the Read Memory (0101) and the Write Memory (0102) commands are
supported.
This functionality is useful to communicate with an OMRON PLC, another
Trajexia system or a PC running FINS server application software.
With the Read Memory command, memory can be read from other devices
with FINS server capability. The Write Memory command can be used to
write data to devices with FINS server capability.
The command returns one of the following values, depending on the
outcome of the execution:
/i
4.2.4
ModbusTCP protocol
Modbus is a serial communication protocol published by Modicon. Versions
of this protocol exist for serial port and for Ethernet connection over TCP/IP.
Trajexia supports ModbusTCP as a slave, which means Trajexia can
respond to communication requests, but it cannot initiate the communication
itself.
A subset of the Modbus communication functions is implemented in
Trajexia. The functions supported are shown in the table below.
/i
When the Modbus Discrete Input functions are used, Trajexia accesses the
digital inputs. When the Modbus Coil functions are used, Trajexia accesses
the digital outputs. When the Modbus Holding Registers functions are used,
Trajexia accesses the VR or TABLE memory area. Which memory area
accessed is defined by a parameter of the
ETHERNET
command. Refer to
section 3.2.110 for more information on this command.
Condition
Response code
(hex)
Description
All elements valid
0000
OK
Var_type invalid
1101
No area type
Start_address invalid
1103
Address range designation error
Number of elements invalid
(totals)
1104
Address out of range
-1
The command executed successfully.
0
The command failed.
1
Request was not sent because the client or the FINS protocol is busy.
2
One or more of the request parameters is invalid.
3
Invalid source memory area.
4
Request was sent, but no response from the remote server was received within the
timeout period.
5
An error response code was received from the remote server.
Function number
Function name
Decimal
Hexadecimal
1
1
Read Coils
2
2
Read Discrete Inputs
3
3
Read Holding Registers
5
5
Write Single Coil
6
6
Write Single Register
16
10
Write Multiple Registers
23
17
Read/Write Multiple Registers