Porovnávané verzie

Kľúč

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

...

ParameterMeaningUnitDefault value
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
wft
wft
Wait First Timeout
The delay after sending the request and before reading the response.s0.1
Kotva
wt
wt
Wait Timeout
The delay between the response readings.s0.1
Kotva
mwr
mwr
Max. Wait Retry
The maximum number of retries of the response reading.-20
Kotva
stasi
stasi
Start Silent Interval
"Start silent interval" before the beginning of the transmission in RTU mode.ms50
Kotva
stosi
stosi
Stop Silent Interval
"Stop silent interval" after ending of the transmission in RTU mode.ms50

Kotva
lem
lem
Little Endian Mode

Byte order in Little-endian mode for 4-byte variables. The individual options indicate in which bytes (1-lowest, 4-highest) the individual bytes from the communication will go:

  • 2143 - first the lower word is received, then the higher word (higher byte within the word is always first)
  • 3412 - first the higher word is received, then the lower word (lower byte within the word is always first)
  • 1234 - bytes are received from lowest to highest (direct opposite of big-endian)
-2143

Kotva
bm
bm
Byte mode

Special byte mode of transmission in which the values of registers have a length of 1 byte and not 2 bytes as it is defined in Modbus protocol specification.YES/NONO
Kotva
vm
vm
Variable mode
Special variable mode of transmission in which the values of registers have variable lengths.

The setting of Variable mode:
Little endian = the lowest bytes are sent first
Big endian = the highest bytes are sent first
OFF = variable mode is switched off

Note 1: Variable and byte modes are incompatible and only one of them can be enabled.
Note 2: Emerson FloBoss 103 device: text strings and time stamps of 6-byte are sent always from the lowest byte.
Note 3: Variable mode is implemented only for Protocol Mode=RTU.
Note 4: A data encoding big-endian is used automatically, according to the default parameter values Byte mod=NO and Variable mode=OFF (i.e. according to MODBUS protocol specification).

OFF
Little endian
Big endian
OFF
Kotva
fd
fd
Full debug
Logging of detailed debug information about communication in the line log.YES/NONO
Kotva
pm
pm
Protocol mode
Protocol mode: RTU or ASCII.

Note: In the case of "MODBUS over TCP/IP", the parameter value is ignored and Protocol Mode=RTU is used.

RTU
ASCII
RTU
Kotva
am
am
Addressing model
Sets an address model of MODBUS protocol:
MODBUS PDU
data are addressed from 0 up to 65535.
MODBUS data Model
data are addressed from 1 up to 65536.

Note:
MODBUS PDU is a default value. If the MODBUS data Model is set, the object with the address X is addressed as X-1 in MODBUS PDU.
After you change this parameter, a restart of the respective communication process was required in the past (KOM binaries older than May 27, 2021).
MODBUS PDU
MODBUS data Model
MODBUS PDU
Kotva
mtcpv
mtcpv
TCP/IP protocol variant
Select a variant of the protocol in case of TCP/IP communication:
"MODBUS TCP" is a variant of communication without control checksum. Safeguarding is done by the underlying TCP protocol.
"MODBUS over TCP"
is a variant where a payload is MODBUS RTU data containing a checksum.
"MODBUS TCP"
"MODBUS over TCP"
"MODBUS TCP"
Kotva
mxr
mxr
Max. Registers
Maximum count of registers that are read by one request.-100

Kotva
mxb
mxb
Max. Bytes

Maximum count of bytes that are required by one request (only in "Byte mode").-100

Kotva
blm
blm
Bool Mask

If a value of the integer type (Holding Registers, Input Registers) is assigned to an I/O tag of the Di or Dout type, this is done by comparing the read value with zero. If the value is zero, the value of the I/O tag is False, otherwise True. The Bool Mask parameter allows specific bits to be filtered out before the comparison is made, based on a bitmask specified as a hexadecimal number (the leftmost byte is the highest). The bitmask FF FF FF FF means that all bits are considered (for 1- and 2-register integer addresses).
Bitmask 01 means that only the lowest bit is considered. If the address of the I/O tag specifies the use of only the lower/upper byte of the register, the lowest/second lowest byte of the mask is applied.

-FF FF FF FF
Kotva
sku
sku
Skip Unconfigured
This parameter is used to avoid reading the values from addresses that are not configured.

Description and example:
The requests for data, which are limited by protocol parameter "Max. Registers" or "Max. Bytes", are sent as standard. If I/O tags with addresses "Holding Registers" 1, 2, and 5 have been configured, one request reading 5 registers starting with address 1 is sent although the I/O tags with addresses 3 and 4 are not configured. It is more efficient to obtain the required data by one request than by two ones even if the unnecessary data are also read.
If the parameter "Skip Unconfigured" is set on YES, two requests are sent, the first one reads two registers from address 1 and the second one reads one register from address 5.
Some Modbus servers respond by exception to reading of a range of registers that contains "unknown" registers (which e.g. they don't have mapped to internal memory).

YES/NONO

Kotva
crl
crl
Check Receive Length

If this parameter is set to YES, then an extra check is performed when receiving a response to a read request: the length of received data is checked whether it matches the number of registers in a read request:
  • if Byte mode is on (Byte mode=YES), the length of received data must be equal to the number of registers
  • if both Byte mode and variable mode are off, the length of received data must be equal to double the number of registers
  • if the variable mode is on (Variable mode=little-endian or big-endian), check has not been implemented yet
This extra check is reasonable on high-latency and variable-latency lines - e.g. GPRS networks - to detect and avoid the situation when read request (#1) is repeated due to timeouts and then two responses are received, the second of which could be considered to be an answer to another read request (#2), thus causing wrong values being assigned to I/O tags addressed by this read request #2.
YES/NONO

Kotva
drm
drm
Dummy Request Mode

If the parameter is set to YES, then a single request (which contains the total number of registers) is used. It is necessary that the I/O tags are defined for all addresses 0..N.
This mode can be used for special devices that send all data (with variable size registers - 2, 4, 8 bytes - in a single response).

YES/NONO

Kotva
merany_bod
merany_bod
I/O tag configuration

...

Kotva
extend
extend
Extended format of I/O tag address:

Address format is [xN].[I|U|F|B|C|T][b]RdFn[-WrFn].Address[.BitNr] in which:

  • xN indicates the number of bytes that read or write. Valid values for N are 1, 2, 4, 8 (in combination with I, U, F), 6 for T type, and an arbitrary number for C type.
  • A letter defines the type of I/O tag. Besides standard I, U, F, B, two extra types have been added:
    • C - text string of fixed length (e.g. x10.C3.1001 is a 10-character string on address 1001)
    • T - time stamp with length of 6 bytes (ss:mi:hh dd:mm:yy)
  • The meaning of other parameters is in compliance with the standard mode.

...

  • Ver. 1.0 - November 27th, 2006 - document creating.
  • Ver. 1.1 - November 21st, 2007 - document update.
  • Ver. 1.2 - April 24th, 2009 - document update.
  • Ver. 1.3 - November 3rd, 2010 - document update.
  • Ver. 1.4 - December 6th, 2010 - document update.
  • Ver. 1.5 - September 5th, 2022 - document update (support for 8-byte values in the extended format).
  • Ver. 1.6 - September 7th, 2022 - document update (added parameter "Dummy Request Mode").
Info
titleRelated pages:

Communication protocols

...