Only modulo 5 values are accepted (by 0.5°C)
*
See list of states in table no. 1
**
*** See list of states in table no. 2
**** Write function available only on the single controller or cascade master (screen parameter 6640 must be different
from slave without adjustment)
***** Only values in steps of 10 minutes are accepted
******* : only values in steps of 1°C are accepted
error code*: see Navistem H3100 manual for code / error message correspondence
Reading the time and date (register 717 / 0x2CD):
Important: the 3 registers from 717 must be read on 1 request.
1
register:
st
High byte: hours
Low byte: minutes
2
register 2:
nd
Most significant byte: day
Low weight byte: month
3
register 3:
rd
word: year
Example: January 31, 2022 at 4:07 p.m.
1
register (HHMM) : 4103
st
2
register (JJMM) :
nd
3
register (YYYY) :
rd
Values displayed for the time schedules (Modbus addresses: 300, 400, 500 and 600):
The time is codified on 1 register in the following manner:
hh:mm → (hh x 60) + mm to be transformed into hexadecimal
e.g.: 22:30 → (22 x 60) + 30 = 1350 (decimal) = 0546 (hexadecimal)
If no time is programmed, the registry must have the value FFFF.
Example for Monday with:
Phase 1: switching on at 6.30 a.m. / switching on 10.30 p.m.
Phase 2 & 3: no schedule scheduled
Monday
The 42 registers are distributed as follows:
Engagement
Monday
1
Tuesday
7
Wednesday
13
Thursday
19
Friday
25
Saturday
31
Sunday
37
15.12.2022
in decimal
in hexadecimal
7937
2022
Phase 1
[01] [86]
[05] [46]
Phase 1
Triggering
Engagement
2
8
14
20
26
32
38
INFORMATION:
10 07 either 0x10 = 16, 0x7 = 7
1F 01 either 0x1F = 31, et 0x01 = 1
07 E6
Phase 2
[FF] [FF]
[FF] [FF]
Phase 2
Triggering
3
4
9
10
15
16
21
22
27
28
33
34
39
40
The 42 registers should be read and written
simultaneously (functions 0x03, 0x04 and 0x10:
see § 3.4.1).
NAVIPASS Modbus - Accessory
Phase 3
[FF] [FF]
[FF] [FF]
Phase 3
Engagement
Triggering
5
11
12
17
18
23
24
29
30
35
36
41
42
6
83 / 202