Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Reading and writing various types of objects (device codes) is supported. These objects are bit-oriented or word-oriented, and the interpretation of several (16 or 32) consecutive bit objects as a signed/unsigned number or two consecutive word objects as a number (unsigned, signed, a real 32-bit number) is supported. Access to a specific bit of a word object is also supported.

...

  • Communication line category: TCP/IP-UDP (FINS/UDP protocol variant) or  TCP/IP-TCP (FINS/TCP protocolvariant).
  • TCP/IP-UDP parameters:
    • Host: IP address or of the network interface that is used for communication by the KOM process. A symbolic name that can be translated to an IP address can be entered too.
      Note: a symbolic name ALL or can be entered - in which case all available interfaces are used.
    • Port: UDP port number that is used for communication by the KOM process.
    • Note: The parameters of the backup server (Host and Port) are not used in this protocol.
  • TCP/IP-TCP parameters:
    • As the Host, Port, and Line Number parameters are not used (PLC address is configured on the station), arbitrary values can be specified.

...

ParameterMeaningUnitDefault value
General Parameters

Kotva
ct
ct
Code type

Type of message encoding:

  • Binary code - messages are binary encoded, they are smaller and more compact
  • ASCII code - messages are text-encoded, they are larger but more visually readable
-Binary code

Kotva
ft
ft
Frame type

The type of frame (header) used. This type must be the same as the type configured on the Mitsubishi PLC side

  • 1E - the simplest header, without a data length specification
  • 3E - header with a data length specification
  • 4E - header with a specification of data length and a serial identifier of individual messages
-3E
1E/3E/4E Frames Common Parameters

Kotva
sn
sn
Station No. (PC No.)

Hexadecimal number (00-FF) specifying the station network module number (for remote stations). Keep the default value FF for directly connected PLCs.

-FF

Kotva
mt
mt
Monitoring Timer

Specification of the time to wait for a response in 250 ms units, which is sent in the message header (a value of 0 means waiting without restriction). The default value of 16 means waiting for 4 seconds.

250 ms16

Kotva
mp
mp
Max Points

The maximum number of objects read in one message. The range is 1-960. Objects can be of bit or word type. A bit object is transmitted as 1 bit (2 bits in ASCII encoding), a word object is transmitted as 2 bytes (4 bytes in ASCII encoding).
When reading objects periodically, read requests are split into multiple if the number of objects in one request is greater than the specified maximum.

-480

Kotva
md
md
Max Data Bytes

Maximum response size - the size of the pure data. The range is 2-8192 bytes.
When reading objects periodically, the read requests are split into several if the response size is larger than the specified maximum.

byte512
3E/4E Access Route Parameters

Kotva
nn
nn
Network No.

Destination network number (for multidrop systems/stations on remote networks). The value is entered in decimal and is in the range 0-255. When communicating with a directly connected station, the value 0 is entered. Other values (see documentation) are entered when communicating with stations located on other network segments (it can also be serial lines) located behind the directly connected station. See Literature for more information.

-0

Kotva
dm
dm
Request destination module I/O No.

Target I / O module number (for multidrop/multiCPU/redundant systems). The value is entered in hexadecimal and is in the range 0000-FFFF. When communicating with a directly connected station, the value 03FF is entered. Other values (see documentation) are entered when communicating with stations located on other network segments (it can also be serial lines) located behind a directly connected station, in the case of multidrop connections, and in the case of working with redundant PLCs and PLCs with multiple CPUs. See Literature for more information.

-03FF

Kotva
ds
ds
Request destination module station No.

Destination station number (for multidrop/multiCPU/redundant systems). The value is entered in hexadecimal and is in the range 00-FF. When communicating with a directly connected station, the value 00 is entered. Other values (see documentation) are entered in the case of a multidrop connection. See Literature for more information.

-00
Other Parameters


Kotva
rc
rc
Retry Count

Maximum count of request retries. If no response returns after a request had been sent, the station's status will change to a communication error.-2

Kotva
rt
rt
Retry Timeout

Timeout before resending a request if no response has been received.s0.1

Kotva
wt
wt
Wait Timeout

Timeout for receiving a response. The value of the parameter should be greater than the time corresponding to the value of the Monitoring Timer parameter.

s1.0

Kotva
fd
fd
Full Debug

Logging of detailed debug information about communication in the line log.YES/NONO

Kotva
td
td
Text Debug

Text reports of messages. If Code type=ASCII code, message listings will be in text form.

YES/NONO

...

The address of the I/O tag is in the form <device code><device number>{ .Mitsubishi protocol} { ,<value type>} {, Mitsubishi protocol}
Note: the I/O tag whose is ignored if its address starts with % IGNORE is ignored. %IGNORE

Kotva
device_code
device_code
Device code

In Mitsubishi protocol terminology, individual objects whose values are read and written are called devices. The protocol allows access to multiple types of devices. Working with the following types of devices is supported:

Device typeDevice codeData type
Special relaySMbit
Special registerSDword
InputXbit
OutputYbit
Internal relayMbit
Latch relayLbit
AnnunciatorFbit
Edge relayVbit
Link relayBbit
Data registerDword
Link registerWword
Timer ContactTSbit
Timer CoilTCbit
Timer Current valueTNword
Retentive Timer ContactSTSbit
Retentive Timer CoilSTCbit
Retentive Timer Current valueSTNword
Counter ContactCSbit
Counter CoilCCbit
Counter Current valueCNword
Link special relaySBbit
Link special registerSWbit
Direct access inputDXbit
Direct access outputDYbit
Index register

Z

word


Kotva
device_number
device_number
Device number

...

Optional parameter - data interpretation.
For device types (device code) that have word data, the default interpretation is WORD (e.g. SD5 address).
For device types (device code) that have bit data, the BIT interpretation is preset (e.g. X5 address)

Value type
Interpretácia
Interpretation
BITInterpretation of a bit-type device as a bit (e.g. X3, BIT)
Interpretation of one bit of word-type device as a bit (e.g. D5.0)
WORDInterpretation of 16 consecutive bit-type devices as a 16-bit unsigned number (e.g. X10, WORD).
Interpretation of one word-type device as an unsigned 16-bit number (e.g. SD10, WORD).
INTInterpretation of 16 consecutive bit-type devices as a 16-bit signed number  (e.g. X10, INT).
Interpretation of one word-type device as a signed 16-bit number (e.g. SD10, INT).
DWORDInterpretation of 32 consecutive bit-type devices as a 32-bit unsigned number (e.g. X10, DWORD).
Interpretation of 2 consecutive word-type devices as a 32-bit unsigned number (e.g. SD10, DWORD).
DINTInterpretation of consecutive 32 bit-type devices as a 32-bit signed number (e.g. X10, DINT).
Interpretation of 2 consecutive word-type devices as a 32-bit signed number (e.g. SD10, DINT).
REALInterpretation of consecutive 32 bit-type devices as a 32-bit floating-point number (e.g. Y10, REAL).
Interpretation of 2 consecutive word-type devices as a 32-bit floating-point number (e.g. SD10, REAL).

Note: when interpreting 32-bit numbers, the data is interpreted as little-endian (a lower word at lower address, higher at higher address).

...