Porovnávané verzie

Stará verzia 1

changes.mady.by.user D2000 Dev Team

Uložené

porovnané s

Nová verzia 2

changes.mady.by.user D2000 Dev Team

Uložené

Kľúč

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

Supported device types and versions
Communication line configuration
Communication station configuration
I/O tag configuration
Literature
Changes and modifications
Document revisions

Kotva
typy_verzie
typy_verzie
Supported device types and versions

...

The Hivus communication protocol supports the communication with control units (RJ) and dataloggers (HDL) produced by Hivus. The communication was implemented and tested with control unit the RJ-05e control unit. The control unit is used to time control of performance and regulation of DEZOSTER devices desoster devices (air ozonizers).

Kotva
komunikacna_linka
komunikacna_linka
Communication line configuration

...

  • Category of communication line: Serial, MOXA IP Serial Library
  • Parameters of the serial line:
    • Baud rate: 19200 Baud
    • Parity: optional
      Note: Parity MARK (sending the device address) and SPACE (all others) are set during a transmission, so the parity setting is not important.
    • Handshaking: none

Note: communication on Serial line was tested on computer serial port, virtual serial port corresponding to MOXA NPort device and virtual serial port corresponding to Serial/USB converter USB-COM GemBird.
Communication on MOXA IP Serial Library line was tested through the use of MOXA NPort 5450I.

...

  • Communication protocol: Hivus Controller
  • Station address: 1 Byte.
    Address 0 is "broadcast" (each device responses to it, but only on reading by 02h function). I/O tag - type 105 (logger number) is used to detect the real address of device.
    Addresses 1-255 represents the common addresses of devices (04h function is used to read data).
  • Time parameters - recommended polling period is 1 min (to avoid loading overloading the processor of the control unit by very frequent communication).

...

Configuration dialog window - Communication station - field "Protocol parameters".
These parameters influence some optional parameters of the protocol. These The following parameters can be used:

Tab. č. 1

Key word
KeywordFull nameDescriptionUnitDefault value
Kotva
dbgi
dbgi
DBGI
Debug InputValue 1 activates the listing of information
on loaded
about received values of I/O tags in trace file of the line in the format:
In I/Otag_name = value		-2
Kotva
dbgo
dbgo
DBGO
Debug OutputValue 1 activates the listing of
information on loaded
information about written values of I/O tags in trace file of the line in the format:
Out I/Otag_name = value		-2
Kotva
raw
raw
RAW
Read After WriteIf the parameter is True, the writing of value (by 05h function) is followed by reading.
Note: Reading does not relate to date and time settings that are done by 01h protocol function (see I/O tag 121).		-False

Kotva
merany_bod
merany_bod
I/O tag configuration

...

Possible value types of I/O tag: Ai, Ao, Ci, Di, TxtO, TxtI.

I/O tag address is written in the format:

  • T=type - I/O tags without index
  • T=type;I=index - I/O tags with index (channels and signalization of failures on DEZOSTERdesoster)
  • T=type;I=index;J=index; - I/O tag contains raw data of protocol with address 100

The header, which is read from the control unit by the KOM process, contains the information that is mapped into I/O tags without index (e.g. moto hours worked, number of engaged channels, type of control unit), information about channels and signalization of failures on DEZOSTERdesosters.
There can be configured 0 up to 8 channels. Each channel is defined by characteristics (1-15, see table below), value, upper/lower limit (something like upper/lower limit in D2000). The channels can be addressed in two ways:

  1. consecutive number 1-8:
    • instantaneous value is addressed by T=16, I=1..8 in I/O tag,
    • type is addressed by T=17, I=1..8 in I/O tag
    • upper limit is addressed by T=18, I=1..8 in I/O tag
    • lower limit is addressed by T=19, I=1..8 in I/O tag
  2. order within channels with particular characteristiccharacteristics. Instantaneous value of i-th measurements with characteristic t is addressed by T=t, I=i.
    For example, instantaneous value of third measurement of type 1 [temperature] is defined by T=1, I=3 no matter on which channel this temperature occurs.

Signalization of failures on DEZOSTER desoster enables to read the statuses of DEZOSTER of desoster 1..10 that are connected to concentrator 1 (T=101) or concentrator 2 (T=102).

These I/O tags can be configured:

Kotva
tabletypegr1
tabletypegr1
Table 1 - I/O tags for channels

AddressValue typeMeaning

Kotva
1_15
1_15
T=

typ

type;I=index

Ai, Ci, Di
Reading of instantaneous value of measurement of typ type, which is index-th in order.
Index can be from range 1..8.
Type can be from range 1..15 according to table below:

TypeDescription
Kotva
1
1
1
Temperature (°C)
Kotva
2
2
2
Relative humidity (%)
Kotva
3
3
3
Ozone concentration (ppm - parts per million)
Kotva
4
4
4
Pressure (kPa)
Kotva
5
5
5
Flow (m3/hour)
Kotva
6
6
6
Air quality (ppm)
Kotva
7
7
7
VOC - Volatile organic compounds (ppm - parts per million)
Kotva
8
8
8
Flow velocity (m/s)
Kotva
9
9
9
Toxicity (%)
Kotva
10
10
10
Intensity (%)
Kotva
11
11
11
NH3 concentration (ppm - parts per million)
Kotva
12
12
12
CO concentration (ppm - parts per million)
Kotva
13
13
13
State of blocking sensor (0/1)
Kotva
14
14
14
Dew point (%)
Kotva
15
15
15
State of the fan (0/1)

Example of address: T=8;I=1 - I/O tag will contain the instantaneous value of flow velocity that is first in order. If type 8 (flow velocity) is not configured on any of channels 1..8, I/O tag value will be invalid.

Note: Instantaneous value of the channel can have a flag indicating the unconnected sensor. This flag is mapped to an attribute of "WEAK" value in D2000. If the instantaneous value from the example mentioned above should have a flag indicating the unconnected sensor, it should be probably 0 with an attribute "WEAK".
Kotva
16
16
T=16;I=index
Ai, Ci, DiReading of instantaneous value of channel with index.
Index can
The index can be from range 1..8.
Example of address: T=16;I=2 - I/O tag will contain the instantaneous value of channel 2.

Note: Instantaneous value of the channel can have a flag indicating the unconnected sensor. This flag is mapped to an attribute of "WEAK" value in D2000. If the instantaneous value from the example mentioned above should have a flag indicating the unconnected sensor, it should be probably 0 with an attribute "WEAK".
Kotva
17
17
T=17;I=index
Ai, CiReading of channel characteristics with index.
Index
The index can be from range 1..8.
Example of address: T=17;I=2 - I/O tag will contain the characteristics of channel 2.

Note: The characteristics can be from range 1..15 with the meaning stated in the table or invalid
,
if no sensor is connected to the channel.
Kotva
18
18
T=18;I=index
Ai, CiReading of upper limit of the channel with index.
Index
The index can be from interval 1..8.
Example of address: T=18;I=2 - I/O tag will contain the upper limit of channel 2.

Note: The value is invalid
,
if no sensor is connected to the channel.
Kotva
19
19
T=19;I=index
Ai, CiReading of lower limit of the channel with index.
Index can
The index can be from interval 1..8.
Example of address: T=19;I=2 - I/O tag will contain the lower limit of channel 2.

Note: The value is invalid
,
if no sensor is connected to the channel.

Table 2 - I/O tags - raw data from the protocol

AddressValue typeMeaning
Kotva
100
100
T=100;I=index;J=index
TxtIReading the raw data from the protocol header into the text I/O tag. "I" and "J"
indicate
indicates the beginning and end byte (1-128), and this condition must be valid: I<=J.
For example I/O tag with address T=100;I=113;J=128 (bytes 113-128 from header) contains a comment from printer (it is the same as I/O tag T=110).
For example I/O tag with address T=100;I=27;J=29 (bytes 27-29 from the header) contains the type of device (it is the same as I/O tag T=106).

Note: These I/O tags are intended for specialists and for future extension of the protocol.

Table 3 - I/O tags relating to fault conditions of dezosterof desoster

AddressValue typeMeaning
Kotva
101
101
T=101;I=index
Kotva
102
102
T=102;I=index
Ai, Ci, DiReading of signalization of device failure with an index that is connected to concentrator No. 1 (if T=101) or concentrator No. 2 (if T=102).
If the index is from the range 1..10, the I/O tag value will contain the information about the failure on a particular
dezoster
desoster (according to the value 0/1, False/True).
If index=0, the I/O tag will contain the information about all 10
dezosters
desosters as integer (status of
dezoster
desoster 1 in 1.
bite
bit up to
dezoster
desoster 10 in 10.
bite
bit)
Example of address: T=101;I=2 - the I/O tag will read the failure signal of
dezoster
desoster 2 that connected with concentrator 1.
Note: If the information in the protocol contains bit, which signalizes "concentrator is not connected", the value of the I/O tag
is
will be Invalid.

Table 4 - I/O tags without indexes

AddressValue typeMeaning
Kotva
103
103
T=103
Ai, CiWorked moto hours - value
form
from range 0-999 999.
Kotva
104
104
T=104
Ai, Ci
Number
The number of connected sensors - value
form
from range 0-8. The channels with connected scanners have valid values (I/O tags of types 1 to 19 - see table 1), other channels has invalid values.
Kotva
105
105
T=105
Ai, Ci
Number of
The control unit number (equal to the station address). It is used to detect the real address of the station if the station address will be 0 (broadcast).
Kotva
106
106
T=106
TxtI3-sign string that defines the type of device:
  • HDL - Hivus Data Logger
  • RJB - control unit without a fan
  • RJV - control unit with fan
Kotva
107
107
T=107
Ai, AoSetpoint for controlling ozone (O3) in ppm. Also, the writing of value
writing
is supported (the protocol function
of protocol
05h).
Kotva
108
108
T=108
Ai, Ao
Threshold
The threshold for an indication of the O3 level in ppm. Also
the
, the writing of value
writing
is supported (the protocol function
of protocol
05h).
Kotva
109
109
T=109
TxtI, TxtO16-sign string - upper and lower limits for the printer. Also, the writing of value
writing
is supported (the protocol function
of protocol
05h).
Note: Presently, this string contains only a protocol-encoded setpoint for controlling ozone and threshold of ozone indication, therefore it is recommended to read and write values by I/O tags T=107 and T=108.
Kotva
110
110
T=110
TxtI, TxtO16-sign string - comment of print. Also the value writing is supported (function of protocol 05h).
Note: This I/O tag is also used to set a control band, blocking sensor, signalization, language, to switch manual/
automat
automatic mode, to set parameters of modes, etc. For more information, see the documentation for communication protocol.
Kotva
121
121
T=121
TxtOWrites values to control unit (by protocol function 01h). Supported values:
  • time - format of value: Thhmmss (hh-hour, mm-minute, ss-second), e.g. T142030 means a time 14:20:30
  • date - format of value Dddmmyyw (dd-day, mm-month, yy-year, w-week day: Monday=1 .. Sunday=7), e.g. D2304153 means date 23.4.2015, Wednesday
T=122TxtI, TxtOWrites 32-bytes of limit values into control unit (by the protocol function 05h).
Note: The first 16 bytes is equal to the I/O tag with address 109, the other 16 bytes
is
are equal to I/O tag with address 110. It is recommended to read and write values by I/O tags T=107, T=108 and T=110.

Kotva
literatura
literatura
Literature

...

  • Ver. 1.0 - April 23, 2015 - creating the document
Info
titleRelated pages:

Communication protocols

...