7-3-2 Prohibit/permit centralized control
[Purpose of this function]
1) It cannot be added any devices which might cause influences to D3-NET communication. In case of a lot of
units connected to the same D3-NET line and communication is very busy, but it is necessary to capture data
without affection to D3-NET.
2) Under circumstance of no centralized controller is allowed to connect, but it is necessary to capture data.
Or existing supervisor controller such as BMS controls VRV units by KRP2A or KRP4A. (see Q-101)
[Limitations]
If the centralized control function is prohibited, limitations listed below will apply.
1) No centralized control can be done from [Centralized control] screen.
2) No new data acquisition can be done because D3-NET initialization to obtain unit information. (in case of
connecting checker to systems for the first time, at first temporarily permit centralize operation and create a
new network map. Then prohibit centralized control again.)
It is possible to stop sending centralized control command from checker by this setting.
Checker has a centralized operation function, it regularly transmits data as a centralized controller to the
connected D3-NET line.
To prohibit centralized control by this function, data transmission as centralized controller can be
stopped by checker.
This setting can be changed from the menu
shown left.
Default set value is “Permission”
Besides, this setting is reverted every time
software starts up back to default value
(Permission). Changed value would not retain.
*After restarting software, set value would
change to “Permission”, if you need to continue
“Prohibition” it is necessary to change this setting
every time.
AS0112-P-DENV
47
https://daikin-p.ru
