RCL-Light/Blind Series RCL-ITR. User Guide

Transcription

1 RCL-Light/Blind Series RCL-ITR User Guide

2 Document Revision History: 1. Version Initial Release - July Version Initial Release - November 2013 RCL-Light/Blind Series & RCL-ITR - User Guide v2.0 05DI-UGRCLLB-20 Distech Controls, 2013 First printing - May Printed in France. While all efforts have been made to verify the accuracy of information in this manual, Distech Controls is not responsible for damages or claims arising from the use of this manual. Persons using this manual are assumed to be trained professionals and are responsible for using the correct wiring procedures, correct override methods for equipment control and maintaining safe working conditions in fail-safe environments. Distech Controls reserves the right to change, delete or add to the information in this manual at any time without notice. Distech Controls, the Distech Controls logo, and Open-to-Wireless are registered trademarks of Distech Controls Inc. LONWORKS, LNS, and LonMark are registered trademarks of Echelon Corporation; BACnet is a registered trademark of ASHRAE; BTL is a registered trademark of BACnet International; Niagara AX Framework is a registered trademark of Tridium Inc.; EnOcean is a registered trademark of EnOcean GmbH; ZigBee is a registered trademark of ZigBee Alliance, DALI is a registered trademark of AG-DALI (ZVEI). All other trademarks are the property of their respective owners

3

4

5 CHAPTER INTRODUCTION... 9 Introduction to the Light/Blind Controllers and Network Interface Product Lines LONMARK Functional Profiles About This User Guide Purpose of the User Guide Intended Audience Conventions Used in this Document Acronyms and Abbreviations Used in this Document CHAPTER GETTING STARTED ON EC-NET AX PRO FOR LONWORKS DEVICES System Requirements Pre-Configuration Installing the Device Configuration Wizards Adding a Device to the Network Database Commissioning the Device Discovering an Existing Network Matching Devices EC-Net AX Device Upload and Download Device Upload Device Download Launching the Device Configuration Wizards CHAPTER GETTING STARTED ON LONWATCHER System Requirements Installing the Device Configuration Plug-in Registering the Device Configuration Plug-in Adding a Device to the Network Database Launching the Device Configuration Plug-In CHAPTER DEVICE CONFIGURATION Windows Units Measurement Units Selecting a Measurement System Overview of the Configuration Tool User Interface Connected and Disconnected Status Main Menu File Edit Options Help Shortcuts Toolbar Room Sensor Management General Temperature Measurement and Setpoint Offset Light Level Measurement Presence Detection RCL-Light/Blind/ITR User Guide 3

6 Display Room Control Management Coupling Control Light Control Loop Installation Configuration Dimming Control Lighting Commands Sunblind commands Occupancy Management Relations between Occupancy Modes Room Management BMS Management Effective Occupancy Room Unoccupancy Delay Occupancy Interaction On Lights Occupancy Interaction On Sunblinds First Occupancy Management Light Management (Light controllers only) Manual Overrides Hardware Sunblind Management (Sunblind controllers only) Manual Overrides Hardware Network Management RJ9 Network Configuration Lon Network Configuration Sensor Data Maintenance Room Module Operations Light Manual Operations Light Act Manual Operations (lighting controllers only) Sunblind Manual Operations Sunblind Act Manual Operations (sunblind controllers only) CHAPTER NODE OBJECT DESCRIPTION Overview Mandatory Network Variables Object Request Object Status Optional Network Variables File Request File Position File Status Manufacturer Network Variables Run Hours Initialization Light Shedding Manufacturer Configuration Properties Neuron Chip Firmware Version Atmega Firmware Version Atmega Firmware UID Fail-Safe Mode Activation RCL-Light/Blind/ITR User Guide

7 CHAPTER OCCUPANCY SENSOR OBJECT DESCRIPTION Overview Mandatory Network Variables Occupancy Output Manufacturer Network Variables ECO-Vue Leaf Pattern Temperature Setpoint Temperature Setpoint Offset Occupancy Fan Speed Command Sensor Communication Fan Speed Command Light Level Measurement Occupancy Output Temperature Offset Temperature Mandatory Configuration Properties Location Label Manufacturer Configuration Properties Presence Detection Configuration Temperature Offset Range Room Sensor Configuration Light Level Measurement Configuration Presence Detection Configuration Room Device Commands Acquisition Temperature Measurement Acquisition nvosensdata Parameter Selection nvosenslightlev Automatic Update nvosenslightlev Minimum Transition Time Light Level Variations Required to update nvosenslightlev Light Level Measurement Calibration nvosenspresence Occupancy Sensitivity nvosenstemp Automatic Update Temperature Variations required to update nvosenstemp nvosenstemp Minimum Transition Time nvosenstemp Offset CHAPTER ROOM CONTROLLER OBJECT DESCRIPTION Overview Manufacturer Network Variables Occupancy Command Input Occupancy Sensor Input Presence Sensor Input Illumination Level Input Value Light Command Reception Input Sunblind Command Reception Input BMS Light Command Override Input BMS Sunblind Command Override Input Sensor Communication Input Effective Light Measurement Occupancy Detection Output Effective Occupancy Status Output Lamp Actuator Commands Sunblind Actuator Commands RCL-Light/Blind/ITR User Guide 5

8 Lighting Control Output Sunblind Control Output Manufacturer Configuration properties Light Level Setpoint Room Controller Object Coupling Dimming Configuration Light Loop Configuration Occupancy Management & Default Room Settings Lighting Command Configuration Lighting Command Value Initial Lighting Command Light Shedding Sunblind Groups Initial Sunblind Commands CHAPTER LAMP ACTUATOR OBJECT DESCRIPTION Overview Mandatory Network Variables Value Input Value Feedback Output Optional Network Variables Running Hours Output Lamp Energy Consumption Manufacturer Network Variables Control-Forwarding Output Manufacturer Configuration Properties Light Configuration Light Power CHAPTER SUNBLIND ACTUATOR OBJECT DESCRIPTION Overview Mandatory Network Variables Setting Input Control-Forwarding Output Optional Network Variables Running Hours Output Sunblind Energy Consumption Manufacturer Network Variables Control-Forwarding Output Manufacturer Configuration Properties Sunblind Configuration Sunblind Power CHAPTER APPENDICES Default Configuration Network Interface Default Configuration Lighting Controllers Default Configuration Sunblind Controllers Default Configuration Smart Grid Integration: Demand Response Introduction Demand response management Light Shedding RCL-Light/Blind/ITR User Guide

9 Compatibility with the CTR Series product line Introduction CTR Lighting controllers configuration for use with RCL-Light/ Blind controllers CTR Sunblind controllers configuration for use with RCL-Light/ Blind controllers Coupling Control - Example Typical installation Requirements Configuration RCL-Light/Blind/ITR User Guide 7

10

11 CHAPTER 1 INTRODUCTION This section introduces the Light/Blind Series controllers as well as the network interface, summarizes their features, and provides an overview of the user guide. In This Chapter Topic Introduction to the Light/Blind Controllers and Network Interface Product Lines Page About This User Guide 15 Acronyms and Abbreviations Used in this Document RCL-Light/Blind/ITR User Guide

12 RCL-ITR RCL-Blind-8LV RCL-Blind-4LV RCL-Blind-8 RCL-Blind-4 RCL-Light-8D RCL-Light-4D RCL-Light-8 RCL-Light-4 Introduction to the Light/Blind Controllers and Network Interface Product Lines The RCL-Light line of controllers is microprocessor-based and is designed to control 4 or 8 ON/OFF or dimming lighting fixtures, depending on models, and to connect 4 additional RJ9 accessories to the LON network. The RCL-Light Series contains four models as follows: RCL-Light-4, RCL-Light-8, RCL-Light- 4D and RCL-Light-8D. The RCL-Blind line of controllers is microprocessor-based and is designed to control 4 or VAC or 24 VAC sunblinds, depending on models, and to connect 4 additional RJ9 accessories to the LON network. The RCL-Blind Series contains four models as follows: RCL-Blind-4, RCL-Blind-8, RCL-Blind- 4LV and RCL-Blind-8LV. The RCL-ITR network interface is designed to connect 4 additional RJ9 accessories to the LON network. Model RJ9 Inputs ON/OFF Light Outputs 4 8 Dimming Light Outputs VAC Sunblind Outputs VAC Sunblind Outputs 4 8 Table 1-1: Models and Features in the RCL-Light/Blind/ITR Product Line 10 RCL-Light/Blind/ITR User Guide

13 RCL-ITR RCL-Blind-8LV RCL-Blind-4LV RCL-Blind-8 RCL-Blind-4 RCL-Light-8D RCL-Light-4D RCL-Light-8 RCL-Light-4 LONMARK Functional Profiles Model Node Objects Occupancy Sensor Objects Room Controller Objects Lamp Actuator Objects Sunblind Actuator Objects RCL-Light/Blind/ITR User Guide 11

14 12 RCL-Light/Blind/ITR User Guide

15 RCL-Light/Blind/ITR User Guide 13

16 14 RCL-Light/Blind/ITR User Guide

17 About This User Guide Purpose of the User Guide This user guide is intended to provide information that will help the user to configure and use the Light/Blind Series controllers as well as the network interface. For the purpose of the examples used in this user guide, some features or applications require a specific device or software in order to work properly. Please refer to the product data sheets or contact a sales representative for more information about the product line. Intended Audience This user guide only explains hardware installation in a general sense. Please refer to the individual device s installation guides for specific hardware installation information. This user guide does not provide and does not intend to provide instructions for safe wiring practices. It is the user s responsibility to adhere to the safety codes, safe wiring guidelines and safe working practices of the local area. This user guide does not intend to provide all the information and knowledge of an experienced technician or engineer. This user guide is intended for system designers, integrators, and field technicians who have experience with control systems. It is recommended that anyone installing and configuring the devices specified in this user guide have prior training in the usage of these devices. Conventions Used in this Document Notes This is an example of Note text. Wherever the note-paper icon appears, it means the associated text is giving a time-saving tip or a reference to associated information of interest. Cautions and Warnings This is an example of Caution and Warning text. Wherever the exclamation icon appears, it means that there may be an important safety concern or that an action taken may have a drastic effect on the device, equipment, and/or network if it is done improperly. RCL-Light/Blind/ITR User Guide 15

18 Acronyms and Abbreviations Used in this Document APB BAS BCP BI BV CP EEPROM I/O IP LON LNS NCI NV NVI NVO NXE PC PID PIR RAM RTC SCPT SNVT UCPT UNVT XIF APplication Binary File Building Automation System Building Controls Protocol Binary Input Binary Value Configuration Property Electronically Erasable Programmable Read-Only Memory Input/Output Internet Protocol Local Operating Network LONWORKS Network Services Network Constant Input Network Variable Network Variable Input Network Variable Output Neuron EXEcutable File Personal Computer Proportional Integral Derivative Control Passive Infra Red Random Access Memory Real Time Clock Standard Configuration Property Type Standard Network Variable Type User Configuration Property Type User Network Variable Type EXternal Device InterFace File Table 1-2: Acronyms and Abbreviations 16 RCL-Light/Blind/ITR User Guide

19 CHAPTER 2 GETTING STARTED ON EC-NET AX PRO FOR LONWORKS DEVICES This chapter provides a detailed explanation of how to install the EC-Net AX device wizards, add a device to a network database and launch the device configuration wizard. In This Chapter Topic System Requirements 18 Pre-Configuration 19 Installing the Device Configuration Wizards 20 Adding a Device to the Network Database 21 Discovering an Existing Network 26 Matching Devices 28 EC-NetAX Device Upload and Download 29 Page Launching the Device Configuration Wizards 31 RCL-Light/Blind/ITR User Guide 17

20 System Requirements Microsoft Windows 2000, Windows XP, Windows Vista, Windows 7 or Windows 8 With a Microsoft Windows 2000 or XP operating system: - Operating System: Windows 2000 or XP. - Processor: 500 MHz or faster. - Memory: 256 MB RAM minimum. - Hard Drive: 500 MB minimum free hard disk space. - Display: Minimum - Super VGA (800x600). Recommended x Accessories: Mouse or other Windows-compatible pointing device. - Network Interface: LONWORKS network interface required. With a Microsoft Windows Vista operating system: - Operating System: Vista Home Premium, Vista Business or Vista Ultimate. - Processor: 1 GHz or faster. - Memory: 1 GB RAM minimum. - Hard Drive: 40 GB minimum free hard disk space. - Display: 128 MB video card minimum. - Accessories: Mouse or other Windows-compatible pointing device. - Network Interface: LONWORKS network interface required With Microsoft Windows 7 or Windows 8 operating system - Operating System: Microsoft Windows 7 or Windows 8. - Processor: 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor. - Memory: 2 GB RAM (32-bit) or 4 GB RAM (64-bit). - Hard Drive: 500 MB minimum free hard disk space. - Display: Minimum - Super VGA (800x600). Recommended x Accessories: Mouse or other Windows-compatible pointing device. - Network Interface: IP network adaptor for network access and internet access. - Other: LONWORKS network interface required 18 RCL-Light/Blind/ITR User Guide

21 Pre-Configuration Before installing a device wizard, adding a device to a network database and launching the device configuration wizard, these steps must first be followed to allow EC-Net AX to support the controllers: Install the EC-Net AX support pack (The latest support pack can be installed by using the Distech Controls Smart Installer software. The Smart Installer can be downloaded from the Distech Controls website at Connect to a platform 1. Install the Distech Controls EC-BOS AX distribution files through the platform Distribution File Installer 2. Connect to a station 3. Check that the Wizard Service is installed under Services. If not, install it using drag and drop from the distechcontrols palette. For detailed instructions on how to perform these steps, please refer to the EC- Net AX Wizards User Guide available on our website. RCL-Light/Blind/ITR User Guide 19

22 Installing the Device Configuration Wizards To install the device configuration wizards, follow the steps below: Close any programs that are running on the PC. Double-click on the device configuration wizard setup executable file. 1. The installation welcome screen will open. Click Next > to continue. Figure 2-1: Wizard Installation Welcome Screen 2. Follow the on screen instructions for any subsequent confirmation prompts that may appear (depending on whether this is a new installation of the wizard or an update). 3. Click the Finish button to complete the installation. 20 RCL-Light/Blind/ITR User Guide

23 Adding a Device to the Network Database In order to add, configure and/or monitor LON devices there must be a LON Network already established in the station. Once the LON Network has been configured, devices can start to be added to the LON Network that is running from the EC-BOS AX station. To add devices to the LON Network: 1. Click the Open Palette button in the Palette side bar to open the Open Palette selection window. Figure 2-2: Opening the Open Palette window If the Palette side bar is not open in the Side Bar Pane click Windows Side Bars Palette to add the Palette side bar. 2. Select distechcontrols from the Open Palette selection window and click OK. This will add the distechcontrols palette to your Palette side bar. Figure 2-3: The Open Palette window RCL-Light/Blind/ITR User Guide 21

24 3. Expand the Drivers folder and drag and drop the BcpLonNetwork from the distechcontrols palette onto the Drivers tree. Figure 2-4: Adding a device to the LON Network 4. Right Click on the BcpLonNetwork in the Nav tree. Select view, then Bcp Lon Device Manager. Figure 2-5: Opening the Bcp Lon Device Manager 22 RCL-Light/Blind/ITR User Guide

25 5. Click New, Figure 2-6: Adding a LON device 6. Select Bcp Lon Device in the scrolling menu Figure 2-7: Selecting the Bcp Lon Device 7. Keep default parameters and click OK. Figure 2-8: Validating the Bcp Lon Device 8. Right-click on the newly BcpLonworksDevice and select device model Figure 2-9: Setting the device model 9. You can now select the appropriate device in the scrolling menu. RCL-Light/Blind/ITR User Guide 23

26 Figure 2-10: Selecting the device model 10. Click OK. In the View Pane the device will be highlighted in yellow. This means that the device has yet to be commissioned. Commissioning the Device Once a device has been added to the LON Network it must be commissioned. The device can be commissioned using two methods; via the device s service pin or by manually entering the device s Neuron ID number. Commissioning the Device via the Service Pin 1. Select the device and click Commission. The Commission window will appear. Figure 2-11: Commissioning the device 2. Click Service Pin and then press the service pin on the device. Figure 2-12: Pressing the device s service pin 3. The device is now ready to be configured. Once the device is pinged, the state of the device will change from Unknown to Config Online. 24 RCL-Light/Blind/ITR User Guide

27 Commissioning the Device Manually 1. Right-click the device either in the Nav Side Bar or in the View Pane, select Views and then Property Sheet. This will open the device s property sheet in the View Pane. Figure 2-13: Accessing the device s property sheet 2. Expand the Device Data tree and enter the device s Neuron ID number in the Neuron ID field. Click Save when finished. Figure 2-14: Manually adding the device s Neuron Id number 3. Go back to the LON Network database (by double-clicking on the BcpLonNetwork entry in the Nav Side Bar). Select the device and click Commission and then Apply. Figure 2-15: Commissioning the device 4. The device is now ready to be configured. You will notice that the state of the device changed from Unknown to Config Online. RCL-Light/Blind/ITR User Guide 25

28 Discovering an Existing Network There will be instances where a LON Network will be created in EC-Net AX at a site that already has one created. This requires that the existing network be discovered and then added to the LON Network being created in EC-Net AX. 1. Double-click the BcpLonNetwork driver in the Nav Side Bar. This will display the LON Network database in the View Pane. Click Discover. The View Pane will become divided into two sections; one listing the LON Network database and the other listing all discovered devices. Figure 2-16: Discovering an existing network 26 RCL-Light/Blind/ITR User Guide

29 2. To add the discovered devices, select them and click Add. The Add window will appear. Click OK. Figure 2-17: Adding the discovered devices to the LON Network The discovered devices have been added to the LON Network database. Figure 2-18: The LON Network with the discovered devices RCL-Light/Blind/ITR User Guide 27

30 Matching Devices There are instances when a site has an existing LON Network and there is a LON Network database already established in EC-Net AX for that site. In this instance it would be necessary to match the devices from the site to the devices in the LON Network database. To match devices: 1. Double-click the BcpLonNetwork driver in the Nav Side Bar. This will display the LON Network database in the View Pane. Click Discover. The View Pane will become divided into two sections; one listing the LON Network database and the other listing all discovered devices. 2. Select the device from the Discovered section to the device it is to be matched to from the Database section and click Match. Figure 2-19: Selecting the devices to be matched 3. The Match window will appear. Click OK to match the devices Figure 2-20: Matching the devices 28 RCL-Light/Blind/ITR User Guide

31 EC-Net AX Device Upload and Download Device Upload Upload reads transient (nvs) and persistent (ncis and cps) data from the device and writes to the station s database (Lon device). This is necessary when adding a new device to the EC-Net AX database. Proceed as follows. 1. Right-click the device and select Actions > Upload. Figure 2-21: Accessing the Upload Lon Device Dialog 2. An Upload dialog box allows you to select the type of data. Typically, you leave dialog parameters at their default settings (true) recursive is always recommended. Click OK. Device Download Figure 2-22: Upload Lon Device Dialog An Upload action is also available at the BcpLonNetwork level with the same Upload dialog selections as shown above. This provides a global upload from all Lon devices. Download writes persistent data (ncis and cps) to the device from values in the station s database (Lon device). This is necessary when you add or modify blocks in your code that are available as network variables while the controller is offline. Proceed as follows. 1. Right-click the device and select Actions > Download. Figure 2-23: Accessing the Download Lon Device Dialog 2. A Download dialog box allows you to select recursive writes. Typically, you leave recursive at default (true), to write to all child data items. Use Download to restore nci and cp values to known good values, as previously saved in the station. Click OK. RCL-Light/Blind/ITR User Guide 29

32 Figure 2-24: Download Lon Device Dialog A Download action is also available at the BcpLonNetwork level with the same Download dialog selections above. This provides a global download from all Lon devices. 30 RCL-Light/Blind/ITR User Guide

33 Launching the Device Configuration Wizards An EC-Net AX Wizard allows the user to program and/or configure a device through the EC- Net AX platform. Those familiar with LNS networks would recognize these wizards as plug-ins. The look and functionality of the wizards are just like LNS Plug-ins. The device s wizard must be installed on the PC running EC-Net AX before it can be launched. Every device type has its own programming wizard and configuring wizard. 1. Open the device configuration wizard by right-clicking the device in the Nav Side Bar, selecting Launch Wizard. Figure 2-25: Wizard Launch Application RCL-Light/Blind/ITR User Guide 31

34 2. Click Launch. The device s wizard will appear. Figure 2-26: EC-Net AX Wizard Please note that a device s EC-Net AX wizard can only be used from one location at a time. For example, if one user at one PC has a particular device s wizard open, another user at another PC mustn't access that same device wizard. 32 RCL-Light/Blind/ITR User Guide

35 CHAPTER 3 GETTING STARTED ON LONWATCHER 3 This chapter provides a detailed explanation of how to install and register the device plug-ins, add a device to a network database and launch the device configuration plug-in. In This Chapter Topic System Requirements 34 Installing the Device Configuration Plug-in 35 Registering the Device Configuration Plug-in 36 Adding a Device to the Network Database 37 Page Launching the Device Configuration Plug-In 41

36 System Requirements Microsoft Windows 2000, Windows XP, Windows Vista, Windows 7 or Windows 8 EC-Net AX configuration software v or higher With a Microsoft Windows 2000 or XP operating system: - Operating System: Windows 2000 or XP. - Processor: 500 MHz or faster. - Memory: 256 MB RAM minimum. - Hard Drive: 500 MB minimum free hard disk space. - Display: Minimum - Super VGA (800x600). Recommended x Accessories: Mouse or other Windows-compatible pointing device. - Network Interface: LONWORKS network interface required. With a Microsoft Windows Vista operating system: - Operating System: Vista Home Premium, Vista Business or Vista Ultimate. - Processor: 1 GHz or faster. - Memory: 1 GB RAM minimum. - Hard Drive: 40 GB minimum free hard disk space. - Display: 128 MB video card minimum. - Accessories: Mouse or other Windows-compatible pointing device. - Network Interface: LONWORKS network interface required With Microsoft Windows 7 or Windows 8 operating system - Operating System: Microsoft Windows 7 or Windows 8. - Processor: 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor. - Memory: 2 GB RAM (32-bit) or 4 GB RAM (64-bit). - Hard Drive: 500 MB minimum free hard disk space. - Display: Minimum - Super VGA (800x600). Recommended x Accessories: Mouse or other Windows-compatible pointing device. - Network Interface: IP network adaptor for network access and internet access. - Other: LONWORKS network interface required 34 RCL-Light/Blind/ITR User Guide

37 Installing the Device Configuration Plug-in To install the device configuration plug-ins, follow the steps below: Close any programs that are running on the PC. 1. Double-click on the device configuration plug-in setup executable file. 2. The installation welcome screen will open. Click Next > to continue. Figure 3-1: Plug-In Installation Welcome Screen 3. Follow the on screen instructions for any subsequent confirmation prompts that may appear (depending on whether this is a new installation of the plug-in or an update). 4. Click on the Finish button to complete the installation. When updating a previous version of the plug-in, the user is given the option to reboot the computer now or later. It is highly recommended to reboot the computer immediately and to not run other software/plug-in setups before rebooting. RCL-Light/Blind/ITR User Guide 35

38 Registering the Device Configuration Plug-in Registering the device configuration plug-ins adds the device template to the active network database. The device template is used for device commissioning and the plug-in is used for device configuration. This section describes how to register the device configuration plug-ins using Lonwatcher 3. If an alternate LNS network management tool is being used, refer to its documentation for a description of how to register a plug-in. To register this device configuration plug-ins, do the following: 1. Open a network database in Lonwatcher 3 by double-clicking on the network name in the tree-view pane. The Register Plug-Ins window will automatically open unless the Skip this window on next startup option has previously been checked. If the Register Plug-Ins window does not open automatically, right-click on a subsystem and select Plug-Ins (SubSystem) > Register. 2. Select the newly installed device configuration plug-ins and click on Add. Figure 3-2: Register Plug-Ins 3. The selected plug-ins will appear in the To Register box. Select the devices for which you want to create a template. Figure 3-3: Plug-Ins Registration 4. Click on OK to complete the registration process. The registration process may take several minutes depending on the number of plug-ins being registered and the speed of the computer. 36 RCL-Light/Blind/ITR User Guide

39 Adding a Device to the Network Database 1. In the tree-view pane of Lonwatcher 3, right-click on the desired subsystem to which a device will be added. 2. Select Add > Device. The Add Device window will open. Figure 3-4: Add Device - Commission 3. Type in the desired name for the device in the Device field. 4. Check the Commission Device option if the device is already physically connected to the network. Otherwise leave the option unchecked. 5. (Optional) Enter a description for the device in the Description field. 6. Click on Next >. Figure 3-5: Add Device - Device Channel and Location RCL-Light/Blind/ITR User Guide 37

40 7. Specify the Device Channel on which the device is/will be installed. 8. (Optional) Type in the device location in the Location field. 9. Click on Next >. Figure 3-6: Add Device - External Interface Definition and Application Image 10. Load the External Interface Definition from the device template as follows: Select the Load from template option. Select the appropriate template from the Template Name drop-down menu. 11. Load the Application Image into the device by selecting the Load Image option. Lonwatcher 3 should automatically detect the application binary (APB/NXE) file that is compatible with the device template. Verify that Lonwatcher 3 has detected the correct APB/NXE file by examining the file name, then click on Next > to proceed to the subsequent window. If the device is not being immediately commissioned on the network, the Load Image option will be grayed out. The APB/NXE file can be loaded later on once the device is attached to the network and it is ready to be commissioned. 38 RCL-Light/Blind/ITR User Guide

41 Figure 3-7: Add Device - Ping Interval, Configuration Properties and Initial State 12. Set the Ping Interval to Longest (By default this setting is disabled). 13. Under Configuration Properties select s. 14. Set the Initial State to Online, then click on Next >. Figure 3-8: Add Device - Device Identification Method RCL-Light/Blind/ITR User Guide 39

42 15. Configure the Device Identification Method as follows: If the device is already connected to the network and can be easily accessed, select the Service Pin method. Click on Finish. There will then be a prompt to press the service pin. Once the service pin is pressed, the device will be added to the database and will be commissioned. If the device is not connected to the network, but the Neuron ID (found on a sticker on the device) is available, select Manual Entry. Type in the device s Neuron ID, then click on Finish. Lonwatcher 3 will give a warning if an improper APB file is trying to be loaded into the device. If the Program Id Check option has been disabled in the Lonwatcher 3 Settings menu and the wrong APB file is loaded into the device, the Neuron chip in the controller may be damaged and it may become unusable. If the service pin does not properly detect the device or if an incorrect APB file is loaded, the Memory Erase jumper can be used to erase the Neuron chip s memory and return it to an applicationless state. Please refer to the device s Hardware Installation Guide for more information. 40 RCL-Light/Blind/ITR User Guide

43 Launching the Device Configuration Plug-In Once a device has been added to a network, it has to be configured based on the requirements of its zone of control. To launch the device configuration plug-in: In the tree-view pane, right-click on the device and select Configure. Figure 3-9: Configuration Plug-In If a plug-in does not launch correctly verify that it is registered properly. If not, re-register the plug-in and launch it again. RCL-Light/Blind/ITR User Guide 41

44 CHAPTER 4 DEVICE CONFIGURATION The Device Configuration tool is used to specify the equipments that are being sensed and controlled by the Light/Blind controllers and the network interface, as well as lighting and sunblinds parameters when applicable. In This Chapter Topic Page Windows Units 43 Overview of the Configuration Tool User Interface 46 Main Menu 47 Shortcuts 56 Toolbar 57 Room Sensor 58 Room Control Management 62 Occupancy Management 67 Light Management (Light controllers only) 72 Sunblind Management (Sunblind controllers only) 74 Network 76 Maintenance RCL-Light/Blind/ITR User Guide

45 Windows Units This section describes how the configuration tool is affected by the units of measurement that are configured in the PC operating system. The choices the operating system makes affect how other programs, such as Microsoft Visio, formats and displays information. If the operating system s measurement units use a comma for decimal values, the number format must be changed as described in Selecting a Measurement System. Measurement Units This section will be most useful if you are using the Imperial system of measurement. There are two main measurement systems in use in the world today, the International System (SI) and the Imperial System. Below is a comparison between Imperial units and SI units. Imperial Inch Yard Mile SI Centimeter Meter Kilometer Degrees Farenheit Degrees Celsius Table 4-1: Comparing Imperial and SI units NVs are based upon SI units. This can lead to some unavoidable problems in data translation when using Imperial units. Some automatic translation between SI and Imperial units is provided. However, like in all translations, errors can occur. For example, a whole number in one system can become a decimal fraction in another: 72 F is approximately equal to C. Additionally, the values created by converting Imperial to SI or SI to Imperial are subject to rounding errors. If an Imperial value is entered into an NV by using the configuration tool, the value is converted after it is entered. The value is then rounded and written to the network variable. When the NV is being monitored, the value must be read from the NV, converted and then rounded before being displayed. Due to the two conversions and two rounding operations, the value may differ from what was entered. The same process and resulting rounding error applies to configuration properties. Figure 4-1: Writing and reading Imperial units RCL-Light/Blind/ITR User Guide 43

46 Selecting a Measurement System To select units of measurement: 1. In Control Panel, select Date, Time, Language, and Regional Options. 2. Select Change the format of numbers, dates, and times. Figure 4-2: Date, Time, Language, and Regional Options Window 3. Select the language region from the drop down list provided. The number, time and date formats will be automatically completed. Figure 4-3: Regional and Language Options dialog box 4. In the box labeled Number, ensure that the number format uses a decimal point and not a comma to indicate numerals representing values less than 1. For example, use and not , If the country chosen uses a comma, click Customize. 6. In the Customize Regional Options dialog box, select metric by clicking on the down arrow in the box labeled Measurement system. 7. Ensure that the Decimal symbol box contains a period. If the Decimal symbol box does not contain a period, select the symbol in the box and then press the period key. 44 RCL-Light/Blind/ITR User Guide

47 Figure 4-4: Customize Regional Options dialog box The units to be displayed in the configuration tool have now been set. If Imperial units have been chosen, remember that the NVs are still using SI units. Moreover, if viewing the data in Imperial units, know that a converted, rounded value is being seen. RCL-Light/Blind/ITR User Guide 45

48 Overview of the Configuration Tool User Interface The device configuration tool consists of a Main Menu and Toolbar, Configuration Window Menu and Configuration Window Figure 4-5: Main Menu and Toolbar, Configuration Window Menu and Configuration Window Main Menu and Toolbar Configuration Window Menu Configuration Window Connected and Disconnected Status Connected Status Disconnected Status To commission a device, it should be physically connected to the network. When the device is connected to the network, the green CONNECTED status is displayed in the Configuration Window bottom right corner In the same manner, if the device to be commissioned has not been physically connected to the network, the red DISCONNECTED status will be displayed. 46 RCL-Light/Blind/ITR User Guide

49 Main Menu The Main Menu is located at the top of the device configuration tool. It contains the commands and options that are needed to manage and use the configuration tool. File This menu contains functions essential for saving and managing your configuration files. Figure 4-6 File Menu Save Export To File Import From File Exit Creates a backup of the configuration tool's data related to the device in the software database. The configuration tool s data can also be saved by clicking Save Project on the Toolbar or by pressing Ctrl+S on the keyboard. Exports the configuration tool s data to the PC as an.lpfc file. The configuration tool s data can also be exported by clicking Export To File on the Toolbar. This opens the Save As window. Imports data saved on the PC as an.lpfc file into the configuration tool. The imported data must belong to the same model of the device. The data can also be imported by clicking Import To File on the Toolbar. This opens the Open window. Exits the configuration tool. If there are any unsaved changes to the configuration tool s data, a prompt window will appear asking if the database is to be saved. RCL-Light/Blind/ITR User Guide 47

50 Export to file The Export to file window is used to name and save a configuration tool s data to the PC. Import from file Figure 4-7 Save As Window The Import from file window is used to locate and open an.lpfc file from the PC. Figure 4-8 Open Window 48 RCL-Light/Blind/ITR User Guide

51 Edit This menu contains commands for reading and writing to the device and database, and resetting the configuration to its default values. Figure 4-9 Edit Menu Read From Device Write To Device Device Information Write To Multiple Devices Upgrade Firmware Reads the data from the connected device and displays it in the configuration tool. For LonWorks models, if no device is being physically connected, reads the data from the database. The data can also be read from the device by clicking Read From Device on the Toolbar. Writes the data displayed in the configuration tool to the connected device. For LonWorks models, if no device is being physically connected, the data is written to the database. The data can also be written to the device by clicking Write To Device on the Toolbar. Opens the Device Information window. The Device Information can also be opened by clicking Device Information on the Toolbar. This information is only available if the device is attached and online. Writes the data displayed in the configuration tool to two or more devices at a time. The data can also be downloaded by clicking Write To Multiple Devices on the Toolbar. This opens the Synchronization window. Opens the firmware update Firmware Upgrade Wizard Reset All To Default Resets all data in the configuration tool to their default values. This opens the Device Information The Device Information window displays device information according to the type of controller that is currently connected. Figure 4-10 Device Information Window RCL-Light/Blind/ITR User Guide 49

52 Synchronization The Synchronization window is used to write the configuration to multiple devices. Start by clicking on Select Devices to open the Select Devices window. Select Devices Figure 4-11 Synchronization Window Selection The Select Devices window is used to select the devices to which the configuration will be written. You can select non-commissioned or offline devices for synchronization (LONWORKS only). In this case, the application will only save the configuration to the database for this device. The device can be synchronized once it has been commissioned. The status is also displayed in the Select Devices window. Non-commissioned devices are greyed out and commissioned devices are shown in green. Figure 4-12 Select Devices Window 50 RCL-Light/Blind/ITR User Guide

53 Figure 4-13 Synchronization Window Selection Complete Figure 4-14 Synchronization Warning Message Figure 4-15 Synchronization Results To display the synchronization progress details, click the Back button. To end the synchronization process, click the Next button, then press Finish. RCL-Light/Blind/ITR User Guide 51

54 Firmware Upgrade Wizard The firmware upgrade windows is accessed by clicking on the firmware upgrade icon or via the Edit Menu: Figure 4-16 Firmware Upgrade Select Device Select the device which firmware is to be updated and click Next: Figure 4-17 Firmware Upgrade Select Firmware Click the top right button. The Open File window appears: 52 RCL-Light/Blind/ITR User Guide

55 Figure 4-18 Firmware Upgrade Open Firmware File Select the new firmware file and click Open. Figure 4-19 Firmware Upgrade Firmware File Validation Click Next: the device is updated with the specified firmware file. Figure 4-20 Firmware Upgrade Firmware Update RCL-Light/Blind/ITR User Guide 53

56 Once the specified devices upgraded, click Next: Figure 4-21 Firmware Upgrade Firmware Update Completion Click Finish to close firmware update process. Options This menu allows the user to select the measurements units. Figure 4-22 Options Menu Measurement Units Select either Metric or Imperial measurement units before performing any other tasks. 54 RCL-Light/Blind/ITR User Guide

57 Help This menu is used to access the configuration tool s help file and Message History window, as well as the version and build number in About. Figure 4-23 Help Menu Help Content Opens the section of the configuration tool s help file that applies to the current window being viewed. The help file can also be opened by clicking Help on the Toolbar. Opens the configuration tool s help file table of contents. Message History About Opens the Message History window. Displays the name and installed version of the configuration tool. The About window can also be opened by clicking About on the Toolbar. Message History The Message History window is a sequential list of actions that have been taken after entering the configuration tool. It lists the action number, the date and time of the action, a description of the action, the module or functional block in which the action was performed and the function of the action. The Message History content may also be saved as a.txt file. Figure 4-24: Message History Window RCL-Light/Blind/ITR User Guide 55

58 Shortcuts A few commands have a keyboard shortcut associated with them for more rapid use. The table below contains all the commands that have a keyboard shortcut associated with them. Save Help Content Ctrl+S Ctrl+F1 F1 56 RCL-Light/Blind/ITR User Guide

59 Toolbar The Toolbar provides quick access to most of the same features that are contained in the Main Menu. Figure : Toolbar Save Export To File Import From File Write To Multiple Devices Write To Device Read From Device Device Information Upgrade Firmware Help About RCL-Light/Blind/ITR User Guide 57

60 Room Sensor Management The Room Sensor management page includes four identical tabs, one for each available room sensor. Room sensors commands (light, sunblind, occupancy, fan speed and setpoint offset) can be enabled/disabled and the different measurements possibly realized by the room sensor (temperature, light level, presence) can be enabled/disabled and parameterized. This section also includes infrared remote control zone number setting and room sensor display and menu management. All the configuration parameters in this page are described in the tables below. FIgure 4-26: Room Sensor Configuration page 58 RCL-Light/Blind/ITR User Guide

61 General Parameter Infrared remote control zone number (IR remote control only) Enable/disable room sensor commands The General section allows to set the IR zone number when an IR remote control is used and to enable/disable the available commands that can be realized by the room sensor. Description When the controller is associated to an infrared remote control, enter the zone number assigned to your infrared remote control to enable communication. 0 enables communication with all infrared zones. Enable or disable the room sensor commands by ticking the matching box. The room sensor commands that can be enabled/disabled are: Light commands Sunblind commands Occupancy commands Fan speed commands Setpoint offset commands Temperature Measurement and Setpoint Offset Parameter Enable/disable temperature measurement The Temperature Measurement and Setpoint Offset section allows to enable/disable temperature measurement and to manage the different pertinent parameters. Description Enable or disable the room sensor's temperature measurement. Temperature calibration offset Temperature setpoint offset range Enter here the temperature calibration to be applied to the measurement received by the controller. i.e if the room space temperature is actually 18 C (64 F) and the information received by the controller is 21 C (70 F), the value to be entered to match actual and received temperatures is -3 C (-6 F). The current room temperature measured by the room sensor can be visualized simply by clicking on the icon on the right part of the screen. The maximum temperature range provided to the end user to adjust the setpoint. For example, with a current temperature setpoint at 20 C (68 F), setting 3 allows the end user to adjust the room s temperature from 17 C to 23 C (62.6 F to 73.4 F). Light Level Measurement The Light Level Measurement section allows to enable/disable light level measurement and to manage the different associated parameters. RCL-Light/Blind/ITR User Guide 59

62 Parameter Enable/disable light level measurement Light level reflection factor Description Enable or disable the room sensor's light level measurement. Calibrate the light level measurement using a percentage between 0% and 200%. This parameter is used as shown in the following formula: Luminosity reflection factor / 100 = Measured Luminosity / Transmitted Luminosity From 1 to 99, the value is amplified From 101 to 255, the value is attenuated No effect if 0 or 100. The current light level measured by the room sensor can be visualized simply by clicking on the icon on the right part of the screen. Presence Detection Parameter Enable/disable presence detection function Presence detection sensitivity The Presence Detection section allows to enable/disable presence detection and to manage the different pertinent parameters. Description Enables or disables presence detection from the room sensor. Set the number of detection pulses it takes before presence (or absence) is considered to be trusted (to avoid unwanted occupancy status modification). Display The Display section allows the selection of the value to be displayed, as well as the menus to be retrievable from the room sensor. 60 RCL-Light/Blind/ITR User Guide

63 Parameter Sensor Display Description Select the parameter to be displayed on the room sensor screen: Central setpoint Central setpoint (blink) Central setpoint + offset Central setpoint + offset (blink) Effective room temperature Effective room temperature (blink) Effective setpoint Effective setpoint (blink) Effective setpoint offset Room sensor temperature Enable/disable room sensor menu entry Check the Enable feature box if the room sensor retrievable menus are to be updated on controller configuration update. Checking this box allows setting independently the different menus below. Simply tick the matching box to display the menus on the room sensor. Note: in any case the retrievable menus can be set directly on the room sensor. If the 'Enable/disable room sensor menu entry' box is ticked, the room sensor's retrievable menus are reset to the wizard's parameters every time the configuration is modified.if not, updating the configuration will not update the room sensor's displayed menus. RCL-Light/Blind/ITR User Guide 61

64 Room Control Management The Room Control Management page includes four identical tabs, one for each room controller object. This page allows setting the relationships between each room controller object, to specify the light control loop settings and the installation configuration. Figure 4-177: Room Control Configuration page 62 RCL-Light/Blind/ITR User Guide

65 Coupling Control The Coupling Control section allows setting the Master/Slave configuration between the different room controller objects. This allows to control up to 8 different light/sunblind groups (2 for each room controller) from a single room device. Please note that, when in coupling mode, bindings on slave Room Controller Objects NVIs can cause dysfunctions. Parameter Room controller coupling mode Description The different room controller objects can be managed independently or linked to another room controller. In this case, the settings of the master room controller are dynamically applied to the slaves, allowing you to manage several room controllers from a single tab. When a room controller object X is coupled with a room controller object Y, light control loop parameters, installation configuration parameters, dimming control parameters as well as occupancy settings are no more retrievable. Nervertheless it is still possible to act on lighting commands and sunblind commands independenly so as to be able to control different equipment types. All these settings can be accessed in the master room controller tab. Light Control Loop The light control loop periodically computes the light command to control light intensity. This computation period can be set to your liking. The control loop can drive on/off or dimming lights. The command is expressed in % for dimming lights, on/off lights only using 0% and 100%. The light control loop differentiates "window" and "corridor" lights to adjust light power depending on the distance to the window so as to reach a consistent light level in the room. Lights can be configured either in "window" or "corridor" mode. A specific calculation is performed for each light output. From the desired light level and the installation configuration, the control loop calculates a command in %. The behaviour difference between the «window side» and the «corridor side» depends on low and high thresholds. RCL-Light/Blind/ITR User Guide 63

66 Parameter Setpoint Corridor group scaling Window group scaling Description The light level to be maintained by the light group. Used to differentiate window side and corridor side light power. Set the scaling applied to the minimum and the maximum of the light command in order to redefine orders sent to the corridor light group. Used to differentiate window side and corridor side light power. Set the scaling applied to the minimum and the maximum of the light command in order to redefine orders sent to the window light group Installation Configuration Parameter Light level averaging samples Light power The aim of this section is to acquire the configuration data required for light control loop computation. Dimming Control Parameter Dimming Management +Step Value Time between steps Description Set here the number of samples over which the average light level is calculated. The light level value in lux when all lights are fully on. The aim of this section is to acquire the dimming management data required for light control loop computation. Description Set here if the dimming action is to be applied in the Lamp Actuator object (LampAct: default) or in the Room Controller object (RoomCtrl). Note: managing dimming from the room controller objects allows for using the dimming signal to control other controllers Lighting Actuator Objects. The step between each successive lighting command. The time elapsed between each successive lighting command. Lighting Commands Each of the four room controllers can manage independently two different lighting command (typically window side and corridor side), leading to the management of up to eight independent lighting commands fixtures. 64 RCL-Light/Blind/ITR User Guide

67 Parameter Manual lighting override operations for test purposes Room sensor override group number Light Control group Light state on power up Managed by light control loop Load shedding Control loop minimum dimming value Description Manual lighting overrides applied on Room Controller s object s nvilightcmd On: Turns on the matching light output Off: Turns off the matching light output Test: Enters the test mode the light is alternatively turned on for 10 seconds and the turned off for 10 seconds. Click again to exit the test mode. Note 1: If a room device is connected, light level measurement must be disabled to prevent value from being overridden by the control loop. Note 2: The controller has to be reset after using this function so as to make sure overrides are cancelled. The room sensor number from which overrides are applied. Set here the light groups assigned to the room sensor override group number defined above: window, corridor, or both. Define here the light command value to be sent when the controller is powered up. Enable this feature if you want the lighting fixture to be controlled by the light control loop. If disabled, the lighting fixture receives orders directly from the room sensor or the BMS. Enable this feature if you want load shedding to be applied to the specified lighting command. - For ON/OFF lights: set here the hysteresis low value, below which the lighting fixture will be turned off. - For dimming lights: enter here the light command value above which the dimming fixture is turned on. Sunblind commands Parameter Manual sunblind override operations for test purposes Room sensor override group number Each of the four room controllers can manage independently two different sunblind commands, leading to the management of up to eight independent sunblinds. Description Manual sunblind overrides applied on Room Controller s object s nvisblndcmd Up: Raises the matching sunblind group Down: Lowers the matching sunblind group Test: Enters test mode the sunblind is alternatively raised for 10 seconds and lowered for 10 seconds. Click again to exit test mode. Note: The controller has to be reset after using this function so as to make sure overrides are cancelled. The room sensor number from which commands are applied. RCL-Light/Blind/ITR User Guide 65

68 Parameter Sunblind state on power up Description Define the default sunblind commands to be sent when powering up the controller: - Translation: argument of State - Rotation: argument of State - State: - Nul: not used - Off: not used - On: not used - Down: moves down by translation field value and rotates backwards by rotation field value. - Up: moves up by translation field value and rotates forwards by rotation field value. - Stop: stops sunblind immediately State: sends an absolute positioning command to translation field value position and rotation field value angle. Note: for reliability reasons, STATE function should be preferred. 66 RCL-Light/Blind/ITR User Guide

69 Occupancy Management The Occupancy Management page contains four sections to configure occupancy operation depending on the BMS occupancy status and the room occupancy status. Figure 4-188: Occupancy Management page RCL-Light/Blind/ITR User Guide 67

70 The controller's occupancy mode results from the synthesis of 2 data: The Room occupancy status sent from a room sensor o Occupied o Unoccupied A delay can be set on the unoccupied command received from the room sensor to avoid unnecessary detection by maintaining the room occupancy status 'unoccupied' the time needed to leave the room even if presence information is received during this time. The room occupancy status is calculated from: Presence sensors User action on "Occupied/Unoccupied" buttons When the user presses "Occupied/Unoccupied" buttons, the room enters in the requested occupancy mode. For each occupancy detection, the room occupancy timer is reinitialized. If no occupancy is detected during this time, the room switches to "unoccupied. The BMS occupancy status based on a time schedule o Occupied o Unoccupied o Standby The BMS Occupancy status can drive directly the room occupancy status Relations between Occupancy Modes Combining Room Occupancy Status and BMS Occupancy Status offers 6 different possibilities. For each of these 6 possibilities, Effective Room Occupancy status can be defined, leading to different scenarii: Light command (either "window" or "corridor" or both) to a dimming level. Lightloop process start ("window" and/or "corridor"). UP or DOWN sunblind command. Effective occupancy setting. Presence timer setting. The system includes the management of several multisensors in a single room. The illustration below describes the relationships between occupancy modes. BMS standby mode is not shown as it acts as BMS occupied mode. 68 RCL-Light/Blind/ITR User Guide

71 Room Management Parameter Reset overrides on occupancy changes Occupancy detection inhibit delay after unoccupied override Description Tick the matching box if the fan speed and temperature setpoint overrides have to be reset when the occupancy statuses switch to the one described in the corresponding line. Enter the amount of time during which automatic presence detection is disabled after setting the room to 'unoccupied' through the room sensor. RCL-Light/Blind/ITR User Guide 69

72 BMS Management Set the action to be taken on room occupancy status when the BMS occupancy status is updated. Parameter Room occupancy on BMS occupancy update Description No effect Forced occupied on occ or standby: Force room occupancy to occupied when the BMS enters occupied or standby mode. Forced unoccupied on unocc: Force room occupancy to unoccupied when the BMS enters unoccupied mode. Forced to BMS: Combination of the two alternatives above: forces room occupancy to occupied when the BMS enters occupied or standby mode and forces room occupancy to unoccupied when the BMS enters unoccupied mode. Effective Occupancy Set the logic to be used to set the room s effective occupancy status depending on BMS and room occupancy statuses. Parameter Effective occupancy based on BMS and room occupancy Description Set the effective occupancy status to be used for each combination of BMS occupancy Status and Room Occupancy Status. Tick the matching box if presence detection is to be activated for the matching combination Room Unoccupancy Delay Room unoccupancy delay restarts after every presence detection. If no presence is detected once this delay elapsed, the effective occupancy status switches to 'Unoccupied'. Parameter Room unoccupancy delay after presence detection or occupancy override Description For each combination scenario, set the effective unoccupancy delay to be used after presence detection or occupancy override. Occupancy Interaction On Lights Set here the desired commands sent by the room controller when the effective occupancy status is updated. Each Room Controller object manages two separate light commands (window side/corridor side). Parameter Window group command on effective occupancy update Corridor group command on effective occupancy update Description Set here the light command to be sent by the room controller object to the matching window side command: light control loop value (tick loop enabled ), a specific set value (tick set and specify the value to be applied), or the current value (untick loop enabled and set ). Set here the light command to be sent by the room controller object to the matching corridor side command: light control loop value (tick loop enabled ), a specific set value (tick set and specify the value to be applied), or the current value (untick loop enabled and set ). 70 RCL-Light/Blind/ITR User Guide

73 Occupancy Interaction On Sunblinds Set here the desired commands sent by the room controller object to the sunblind actuator object when the effective occupancy status is updated. Each Room Controller object manages one group. Parameter Action on sunblinds when effective occupancy changes Description Tick Set if you want to define the sunblind translation and rotations commands to be sent by the room controller object. If unticked, the current value is ticked. First Occupancy Management Set here the desired commands sent by the room controller for the first room occupancy after the BMS occupancy status switched to occupied. Parameter Sunblind position Sunblind rotation angle Description Set here the sunblind translation to be applied on first occupancy. Set here the sunblind rotation to be applied on first occupancy. RCL-Light/Blind/ITR User Guide 71

74 Light Management (Light controllers only) The Light Management page allows you to perform manual operations for test purposes and to parameterize the installation. All these configuration parameters are described in the tables below. Figure 4-29: Light Management page Manual Overrides Parameter Manual lighting override operations for test purposes Description Manual lighting overrides applied on Room Controller s object s nvilightcmd On: Turns on the matching light output Off: Turns off the matching light output Test: Enters the test mode the light is alternatively turned on for 10 seconds and the turned off for 10 seconds. Click again to exit the test mode. Note 1: If a room device is connected, light level measurement must be disabled to prevent value from being overridden by the control loop. Note 2: The controller has to be reset after using this function so as to make sure overrides are cancelled. Parameter Light type Hardware Light ON Treshold (ON/OFF Lighting only) Light OFF Treshold (ON/OFF Lighting only) Minimum Light Command (Dimming Lighting only) Configure the light type and the matching lighting thresholds for the selected output. Description Select the type of lights used: Digital (on/off): Lights that are full-on or full-off. Dimming: Lights that have a continuously variable light output. Enter here the value for which the light is turned ON Enter here the value for which the light is turned OFF The light command value below which the light is completely OFF and above which the lamp starts to dim up. 72 RCL-Light/Blind/ITR User Guide

75 Parameter Maximum Light Command (Dimming Lighting only) Dimming Time (Dimming Lighting only) Estimated light output power consumption Description The light command value above which the light is fully ON and below which the lamp starts to dim down. The time the lights need to go from fully ON to fully OFF and vice versa. Enter here the estimated light output power consumption to allow for monitoring energy consumption. RCL-Light/Blind/ITR User Guide 73

76 Sunblind Management (Sunblind controllers only) The Sunblind Management page allows you to perform manual operations for test purposes and to parameterize the installation. All these configuration parameters are described in the tables below. Figure 4-30: Sunblind Configuration page Manual Overrides Parameter Manual operation on the sunblind for test purposes Parameter Polarity Hardware Translation time Rotation time Use this feature to test and identify the different sunblind groups in your room. Description Manual sunblind overrides applied on Room Controller s object s nvisblndcmd Up: Raises the matching sunblind group Down: Lowers the matching sunblind group Test: Enters test mode the sunblind is alternatively raised for 10 seconds and lowered for 10 seconds. Click again to exit test mode. Note: The controller has to be reset after using this function so as to make sure overrides are cancelled. Configure the sunblind translation and rotation times for the selected sunblind group. Description Select the polarity of the sunblinds in use to fit the sunblind motor wiring type: Normal Reverse The time the sunblind takes to translate from fully closed to fully opened The time the sunblind takes to accomplish full rotation 74 RCL-Light/Blind/ITR User Guide

77 Parameter Manual override rotation step Delay between steps Max angle Min angle Boot delay Estimated light output power consumption Description The amount of rotation achieved for each manual rotation order received. This parameter is used to smooth the rotation of sunblinds with the remote control and room sensors. The delay between each rotation step (in seconds) The maximum angle the sunblind can reach. The minimum angle the sunblind can reach. Enter here the time the sunblind needs to boot after being powered up (in tenths of seconds). Enter here the estimated sunblind output power consumption to allow for monitoring energy consumption. RCL-Light/Blind/ITR User Guide 75

78 Network Management The Network Management page contains specific configuration parameters. This page also allows you to enable RJ9 network fail-safe mode. All these parameters are described in the tables below. Figure 4-31: Network Configuration page RJ9 Network Configuration Set if the fail-safe mode is to be engaged when presence detection information from the room sensor is lost. The fail-safe mode starts an alarm mode if a sensor is defective. For every presence detection sent to the Room Controller Object, a timer is started. If the timer expires (no detection signal received), the room enters alarm mode: 100% light command is sent. Alarm mode is escaped when a detection is received from the multi-sensor. Parameter Fail safe time out Description Set here the time between losing presence detection information and entering fail-safe mode. 0 disables fail-safe functionality. 76 RCL-Light/Blind/ITR User Guide

79 Lon Network Configuration The heart beat and throttle for the Network Variable Outputs and Inputs associated with the controller can be set, as well as the sensor data transmitted to the network. Heartbeats Heartbeats can be set on nvosenslightlev and nvosenstemp to allow other controllers to detect if a given controller is alive and online. When the max receive time is exceeded, the matching variable is sent. Parameter Description nvosenslightlev Max send time: The maximum time period between automatic transmissions of the network variable on the network (whether or not the variable's value has changed). Setting the max send time to 0 disables it. This is a LONWORKS communications setting. This is often referred to as the "heartbeat". If the Max receive time is configured for the corresponding network variable input, the recommended setting for this value is twice the Max send time value. Min send time: The minimum time period that must pass between network variable updates on the network. If the value of the network variable changes, an update will only be sent after this time expires. This is a LONWORKS communications setting. Setting Min send time to 0 disables it. This is often referred to as the "throttle". Min delta: The minimum change in value needed to trigger an update, while respecting the time limits set for Min send time and Max send time. nvosenstemp Max send time: The maximum time period between automatic transmissions of the network variable on the network (whether or not the variable's value has changed). Setting the max send time to 0 disables it. This is a LONWORKS communications setting. This is often referred to as the "heartbeat". If the Max receive time is configured for the corresponding network variable input, the recommend setting for this value is twice the Max send time value. Min send time: The minimum time period that must pass between network variable updates on the network. If the value of the network variable changes, an update will only be sent after this time expires. This is a LONWORKS communications setting. Setting Min send time to 0 disables it. This is often referred to as the "throttle". Min delta: The minimum change in value needed to trigger an update, while respecting the time limits set for Min send time and Max send time. For more information about LONWORKS networking principles and network variables, please visit the Echelon website at Sensor Data RJ9 sensor data can optionally be shared with other controllers over the LONWORKS Network. RCL-Light/Blind/ITR User Guide 77

80 Parameter RS Sensor. nvosensdata sent values Description Enable: Shares the corresponding RJ9 sensor data with other controllers on the LONWORKS Network. Disable: Does not share the corresponding RJ9 sensor data with other controllers on the LONWORKS Network. The possible shared data are: - Temperature - Light level - Presence - Setpoint offset overrides - Fan speed overrides - Occupancy overrides - Light overrides - Sunblind translation overrides - Sunblind rotation overrides For more information about LONWORKS networking principles and network variables, please visit the Echelon website at 78 RCL-Light/Blind/ITR User Guide

81 Maintenance The Maintenance page allows you to proceed to several tests for maintenance purposes. All these parameters are described in the tables below. Figure 4-32: Maintenance page RCL-Light/Blind/ITR User Guide 79

82 Room Module Operations Parameter RS Sensor This function helps you to identify infrared or radio receivers onsite. Description Test an infrared or radio receivers as follows: 1. Click Test to monitor the occupancy function of the receiver from the wizard. 2. Send 'occupied/unoccupied' commands to the receiver through the room sensor module or the remote control 3. The wizard occupancy icon changes according to the received occupancy command. Light Manual Operations Parameter Light Cmd X (RoomCTRLY) This allows you to test the different light groups in the different room controller objects. Description The following lighting tests are available as follows: On: Room controller Y s light command X is set to ON. Off: Room controller Y s light command X is set to OFF. Test: Enters the test mode Room controller Y s light command X is alternatively turned ON and OFF every 10 seconds. Click again to exit the test mode. Note: The wizard s test mode is automatically escaped if a contradictory input is received from te room device. Light Act Manual Operations (lighting controllers only) Parameter Light Act Cmd X This allows you to test the light commands sent by the different lamp actuator objects. Description The following lighting tests are available as follows: On: Lamp Actuator X light command X is set to ON. Off: Lamp Actuator X light command X is set to OFF. Test: Enters the test mode the lamp actuator object sends alternatively ON and OFF every 10 seconds. Click again to exit the test mode. Note: The wizard s test mode is automatically escaped if a contradictory input is received from te room device. Sunblind Manual Operations Parameter Sblnd Cmd X (RoomCTRLY) This allows you to test the different sunblind groups. Description The following sunblind tests are available as follows: Up: Room controller Y s sunblind command X is set to UP. Down: Room controller Y s sunblind command X is set to DOWN. Test: Enters the test mode Room controller Y s sunblind command X is alternatively set to UP and DOWN every 10 seconds. Click again to exit the test mode. Note: The wizard s test mode is automatically escaped if a contradictory input is received from te room device. 80 RCL-Light/Blind/ITR User Guide

83 Sunblind Act Manual Operations (sunblind controllers only) Parameter Sblnd Act Cmd X This allows you to test the sunblind commands sent by the different sunblind actuator objects. Description The following sunblind tests are available as follows: Up: Sunblind Actuator X translation command X is set to UP. Down: Sunblind Actuator X translation command X is set to DOWN. Test: Enters the test mode the sunblind actuator object command is alternatively set to UP and DOWN every 10 seconds. Click again to exit the test mode. Note: The wizard s test mode is automatically escaped if a contradictory input is received from te room device. RCL-Light/Blind/ITR User Guide 81

84 CHAPTER 5 NODE OBJECT DESCRIPTION A complete list of the NVs and CPs for the Node object. In This Chapter Topic Overview 83 Mandatory Network Variables 84 Optional Network Variables 86 Manufacturer Network Variables 88 Page Manufacturer Configuration Properties RCL-Light/Blind/ITR User Guide

85 Overview The Node Object allows the function of objects within a node to be monitored. Upon receiving an update to the nvirequest network variable, the nvostatus network variable is updated. The definition of SNVT_obj_request includes an object ID field to allow the Node Object to report status and alarm conditions for all objects on a node. Figure 5-1 Node Object Overview RCL-Light/Blind/ITR User Guide 83

86 Mandatory Network Variables Object Request Network Input SNVT_obj_request nvirequest; This network variable input provides the mechanism to request a particular mode for a particular object within a node. For a listing of all possible request codes and for the meaning of the function codes for SNVT_obj_request see the SNVT Master List. Valid Range The valid range is any value within the defined limits of SNVT_obj_request. The only mandatory request functions are RQ_NORMAL, RQ_UPDATE_STATUS and RQ_REPORT_MASK. Unsupported request functions must return invalid_request in the object status. It is not required to support object disable, self-test, override or alarm reporting. The semantic definitions of the object request codes are as follows: RQ_NORMAL - if the object was in the disabled or overridden state, this request cancels that state, and returns the object to normal operation. If the object was already in the normal state, a request to enter the normal state is not an error. After node reset, the state of objects on the node is application-specific. RQ_REPORT_MASK - the status bits that are supported by the object are sent to the network variable output of type SNVT_obj_status. If object disable is not supported, the disabled bit in the status mask must be zero for that object. See below for a description of the status mask. If self-test is not supported, the fail_self_test and self_test_in_progress bits in the status mask must be zero for that object. If alarm reporting is not supported, the in_alarm bit in the status mask must be zero for that object. RQ_OVERRIDE - the object is placed in the overridden state. See the description of the Override Behavior and Override Value configuration properties in Chapter 3 for details. After node reset, the state of objects on the node is application-specific. An object may be in both the overridden and disabled states at the same time. RQ_CLEAR_ALARM - the alarm state of the object is cleared, SNVT alarm is updated to no alarms. State of the object is unchanged. Persistent alarms are reported as they are re-detected. RQ_PROGRAM the receiver connected to the controller sends to the matching the remote control a pairing request. Node Object Behavior Supporting requests to the node object (type 0) is optional. A request RQ_DISABLED to object type 0 means that all objects in the node should be disabled. If any of the objects in the node support the disable function, then those objects should be disabled, and invalid_request should not be reported. However, if none of the objects in the node supports the disable function, then invalid_request should be reported. Note that a request to disable the node object does not disable file transfer, or any other request to the node object. The SNVT_obj_status output and the SNVT_alarm output are not disabled when the node object is disabled. A request RQ_NORMAL to the node object (type 0) specifies that all objects in the node leave the disabled and overridden states. If requests to the node object are supported, RQ_NORMAL is always a valid request to this object. 84 RCL-Light/Blind/ITR User Guide

87 A request RQ_REPORT_MASK to the node object causes the object to respond with a mask of supported status bits in the SNVT_obj_status network variable output. A one bit in the mask means that the node may set the corresponding bit in the object status when the condition defined for that bit occurs. A zero means that the bit is never set by the node. A request RQ_OVERRIDE to the node object causes all objects in the node that implement the overridden state to enter that state. Object Status Network Output SNVT_obj_status nvostatus; This network variable output reports the status for any object on a node. Valid Range The valid range is any value within the defined limits of SNVT_obj_status. The meaning of the fields of SNVT_obj_status are detailed in the SNVT Master List and Programmer's Guide ( ). The report_mask, invalid_id and invalid_request fields are the only mandatory bits in SNVT_obj_status, all other status bits are optional. Reporting a status of invalid_request is required if an unsupported request code is received on the object request network variable input. A status of invalid_id is reported whenever a request is received for an object ID that is not defined in the node. If the object ID is invalid and invalid_id is reported, then no further checking of the request code need be performed. A self-documenting mask is used to describe the status bits that are supported beyond the two mandatory bits described above. The obj_request code RQ_REPORT_MASK causes the object to respond with a mask of supported status bits in the SNVT_obj_status network variable output. A one bit in the mask means that the object may set the corresponding bit in the object status when the condition defined for that bit occurs. A zero bit means that the bit may never be set by the object. When setting the status in response to a RQ_REPORT_MASK, the report_mask bit must be set to distinguish this from other forms of status. When Transmitted Data are transmitted whenever a value is received on the Object Request input and when the Object Status Max Send Timer expires. When the Object Status Max Send LONMARK Interoperability Guidelines 3-11 Timer expires, the status of each object (including the node object) is returned sequentially in round-robin fashion, one object status per expiration of the timer. Update Rules The application must update the status such that a poll of the status following the request is guaranteed to return a reasonable value. In a Neuron C program, this means setting the status in the same critical section as the request event is processed. Setting the status may mean setting the actual result or, for RQ_SELF_TEST, setting the self_test_in_progress indicator. Update Rate The default update rate for this network variable is 0 times per second. Default Service Type The default service type is acknowledged. RCL-Light/Blind/ITR User Guide 85

88 Optional Network Variables File Request Network Input SNVT_file_req nvifilereq; This input network variable specifies a requested operation code and file index. When a request is received, the device performs the requested operation and returns the status of that operation in the nvofilestat output network. The request operation codes are defined in the SNVT Master List, and described in the Echelon LONWORKS File Transfer Protocol Engineering Bulletin ( ). Files are identified with a unique 16-bit number called the file index. Up to files can be identified on any device. This input network variable must be implemented in the Node Object functional block if the device supports LONWORKS FTP. It must not be implemented if the device supports the direct memory read/write access method for data files. Valid Range The valid range of SNVT_file_req. The typical default value is FR_NUL. Configuration Considerations None specified. File Position Network Input SNVT_file_pos nvifilepos; This input network variable controls the position of the read/write pointer in a file used for random access, and is also used to specify the length of the next file transfer. The rw_ptr field is a 32-bit value compatible with the Neuron C s32_type signed 32-bit type. For more details, see the Echelon LONWORKS File Transfer Protocol Engineering Bulletin ( ). This input network variable must be implemented in the Node Object functional block if the device supports the LONWORKS FTP with random and sequential access method. It must not be implemented if the device supports the LONWORKS FTP with sequential access or the direct memory read/write access methods for data files. Valid Range The valid range of SNVT_file_pos. None specified. Configuration Considerations None specified. File Status Network Output SNVT_file_status nvofilestat; This output network variable transmits the status of the last file-request received via the nvifilereq input network variable. The returned status codes are defined in the 86 RCL-Light/Blind/ITR User Guide

89 SNVT Master List, and described in the Echelon LONWORKS File Transfer Protocol Engineering Bulletin ( ). This output network variable must be implemented in the Node Object functional block if the device supports LONWORKS FTP. It must not be implemented if the device supports the direct memory read/write access method for data files. Valid Range The valid range of SNVT_file_status. The typical default value is FS_NUL. Configuration Considerations The Node Object implements the file-request and file-position network variables as inputs, and the file-status network variable as an output. The device can therefore act as the Sender or the Receiver in a file transfer, but it cannot act as the Initiator of a file transfer using these network variables. When Transmitted The output variable is transmitted when either of the following conditions occurs: During file transfer When polled RCL-Light/Blind/ITR User Guide 87

90 Manufacturer Network Variables Run Hours Initialization Network Input UNVT_elapsed_tm nvirunhours; This input network variable is used to reset nvorunhours network variable output in Lamp Actuator (Light Controllers) or Sunblind Actuator (Blind Controllers) objects. Valid Range Sub Name Valid Range index 01 day hour minute second millisecond {0 ; 0 ; 0 ; 0 ; 0 ; 0} 0 : resets all 1 : resets 1 st actuator object 2 : resets 2 nd actuator object 3 : resets 3 rd actuator object 4 : resets 4 th actuator object 5 : resets 5 th actuator object 6 : resets 6 th actuator object 7 : resets 7 th actuator object 8 : resets 8 th actuator object Light Shedding Network Input SNVT_switch nvilightshedding; This input network variable is used to apply a shedding coefficient to nvolampvalue in the Room Controller object so as to allow system power overloading management. The actual value sent to the lamp actuator object (nvolampvalue) is the light control loop value multiplied by (1-nviLightShedding). Valid Range Sub Name Description 01 state Enable/disable light shedding command acquisition -1: Invalid 0: Disabled 1: Enabled 02 value Light shedding coefficient (%) {-1, 0} 88 RCL-Light/Blind/ITR User Guide

91 Manufacturer Configuration Properties Neuron Chip Firmware Version UCPTapplicationSoftwareVersion cpfwversionnc This configuration property is used to store the Neuron Chip firmware version in operation. Atmega Firmware Version UCPTfirmwareVersion cpfwversionat This configuration property is used to store the Atmega firmware version in operation. Atmega Firmware UID UCPTfirmwareUID cpfirmwareuid This configuration property is used to store the Atmega firmware version in operation. Fail-Safe Mode Activation UCPTsystemCtrl cpsystemctrl This configuration property is used to set the time in minutes after which the system enters fail-safe mode. Valid Range 0 to 255 0: disabled 10 RCL-Light/Blind/ITR User Guide 89

92 CHAPTER 6 OCCUPANCY SENSOR OBJECT DESCRIPTION A complete list of the NVs and CPs for the supported LonMark objects. In This Chapter Topic Overview 91 Mandatory Network Variables 92 Manufacturer Network Variables 92 Mandatory Configuration Properties 96 Page Manufacturer Configuration Properties RCL-Light/Blind/ITR User Guide

93 Overview The Occupancy Sensor Object defines the configuration of connected sensors, i.e to enable or disable received parameters (temperature, light level, occupancy, etc.) Figure 6-1 RS Sensor Object Overview RCL-Light/Blind/ITR User Guide 91

94 Mandatory Network Variables Occupancy Output Network Output SNVT_occupancy nvosensocc This network variable output provides the current occupancy sensor s state. Valid Range The range of SNVT_occupancy. OC_NULL When Transmitted When the occupancy state changes from unoccupied to occupied or when the occupancy state has changed from occupied to unoccupied at the frequency of the heartbeat. Update Rate The maximum update rate is fixed by the heartbeat frequency and the minimum update rate is fixed by the debouncing time. Default Service Type The default service type is acknowledged Manufacturer Network Variables ECO-Vue Leaf Pattern Network Input SNVT_count nvisensecovue This network variable input is used to override the number of leaves to be displayed on the ECO-Vue leaf pattern on an Allure RS-Smart-Sense. Valid Range 0: ECO-Vue is driven by the controller algorithm 1: 1 leave 2: 2 leaves 3: 3 leaves 4: 4 leaves 0 Temperature Setpoint Network Input SNVT_temp_p nvisenssetpt This network variable input is used to override the room device s temperature setpoint displayed on the room sensor. Valid Range The valid range is to RCL-Light/Blind/ITR User Guide

95 0 Temperature Setpoint Offset Network Input SNVT_temp_p nvisenssetptoff This network variable input is used to override the room device s temperature offset displayed on the room sensor. Valid Range The valid range is to Occupancy Network Input SNVT_occupancy nvisensoccup This network variable input is used to override the room device s occupancy status displayed on the room sensor.. Valid Range The range of SNVT_occupancy. OC_NUL Fan Speed Command Network Input SNVT_switch nvisensfanspeed This network variable input is used to override the room device s fan speed command on ambiance device. Valid Range Sub Name Description 01 state State of the Fan Speed Command Override -1: Auto 0: Off 1: On 02 value Fan speed command value (%) {0, -1} Sensor Communication Network Output UNVT_Dalilon nvosensdata This network variable output is available to report the RS Sensor status. The combination of all fields determines the transmitted information type. RCL-Light/Blind/ITR User Guide 93

96 Light level measurement Valid Range Bitset LuxLevel Occ Reserved1 Reserved2 Reserved3 Reserved4 1 Filtered light level measurement Room Occupied/ occupancy Unoccupied Presence 3 - Occupied detection Light Push / /- Key - Group command release Sunblind /- Key or setting - - Group commands Temperature Temperature offset Offset Fan speed Fan speed Filtered Temperature 8 temperature measurement measurement Light level setpoint Unoccupancy inhibit delay Light level setpoint (lux) Unoccupancy delay (x 100 ms) : GTB_OCC 2 : GTB_UNOCC 3 : GTB_STDBY {0; 0; 0; 0; 0; 0; 0; 0; 0} When Transmitted On event Update Rate Set the nvosensdata parameter selection in the configuration property cpenablesensordata. Fan Speed Command Network Input SNVT_switch nvosensfanspeed This network variable output provides the fan speed command sent by the room devices. Valid Range Sub Name Description 01 state State of the Fan Speed Command Override -1: Auto 0: Disabled 1: Enabled 02 value Fan speed command value (%) {-1, 0} 94 RCL-Light/Blind/ITR User Guide

97 Light Level Measurement Network Output SNVT_lux nvosenslightlev This network variable output provides the value of the light level measured with the sensor. Valid Range The valid range is lux with 1 lux resolution, as defined for SNVT_lux When Transmitted Whenever the hardware state changes more than defined by configuration parameter mindeltalight. Update Rate Defined by configuration parameters minsendtime and maxsendtime Default Service Type The default service type is acknowledged. Set the nvosenslightlev Automatic Update in the configuration property cplightmaxsendt. Set the nvosenslightlev Minimum Transition Time in the configuration property cplightminsendt. Set the Light Level Variations Required to update nvosenslightlev in the configuration property cplightmindelta. Set the Light Level Measurement Calibration in the configuration property ncisensorreflect. Occupancy Output Network Output SNVT_occupancy nvosenspresence This network variable output provides the Presence detection status from the room device. Valid Range The range of SNVT_occupancy. OC_NULL When Transmitted When a RJ9 data is received Set the nvosenspresence Ocupancy Sensitivity in the configuration property cpsensorpresfilter. Temperature Offset Network Output SNVT_temp_p nvosenssetptoff This network variable output is used to provide the temperature offset as defined in the room device. Valid Range RCL-Light/Blind/ITR User Guide 95

98 The valid range is to When Transmitted When a RJ9 data is received Set the nvosenssetptoff Network Variable Length in the configuration property cpmaxnvlengthnvosenssetptoff. Set the nvosenssetptoff Network Variable Type in the configuration property cpmaxnvlengthnvosenssetptoff. Temperature Network Output SNVT_temp_p nvosenstemp This output variable reports the temperature detected by the room device. Valid Range The valid range is to When Transmitted When a RJ9 data is received Set the nvosenstemp automatic update in the configuration property cptempmaxsendt. Set the temperature variations required to update nvosenstemp in the configuration property cptempmindelta. Set the nvosenstemp minimum transition time in the configuration property cptempminsendt. Set the hardware temperature measurement calibration in the configuration property ncisensofftemp. Mandatory Configuration Properties Location Label SCPTlocation cplocation This configuration property is used to store ASCII text. It provides more space for descriptive location information. Valid Range Any NUL terminated ASCII string of 31 bytes total length An ASCII string containing all zeros. SCPT Reference SCPT_location (#17) 96 RCL-Light/Blind/ITR User Guide

99 Manufacturer Configuration Properties Presence Detection Configuration SCPTzoneNum cpsensorirzone This configuration property is used to select the Infrared Zone from which orders are received. Value Range 0: accepts orders from any infrared zone 0: accepts orders from infrared zones 0 and cpsensorirzone 0. Temperature Offset Range UCPToffsetRange cpoffsetrange This configuration property indicates the variation range (in K) of the temperature offset. It is symmetric, for example if cpoffsetrange = 3, then the range is -3 C to +3 C. Valid Range to Room Sensor Configuration UCPTroomDisplay cproomdisplay This configuration property defines the room sensor display and activated features. Valid Range Sub Name Description 01 Unsigned short menu_config Configuration of the room sensor functions: Bit7 (MSB): Activation of the configuration (+128) Bit6: Not used (+64) Bit5: Not used (+32) Bit4: Lights activation (+16) Bit3: Sunblinds activation (+8) Bit2: Occupancy activation (+4) Bit1: Fan speed activation (+2) Bit0 (LSB): Setpoint offset activation (+1) The value to write is the sum of the functions to be activated. To enable the configuration, Bit7 must be set to 1 (+128) Ex: Activation of offset + fan speed + occup: = 135 RCL-Light/Blind/ITR User Guide 97

100 02 Unsigned short display_config Type of display of the room device: 0: set point shift 1: room temperature 2: actual calculated set point (blink) (nvisenssetpt) 3: actual calculated set point (fix) (nvisenssetpt) 4: central setpoint (blink) 5: central setpoint (fix) 6: room temperature (blink) 7: room temperature (fix) 8: central setpoint + offset (blink) 9: central setpoint + offset {255; 1} : all menus activated, room temperature displayed. Light Level Measurement Configuration UCPTsensorLightMeas cpsensorlightmeas This configuration property is used to set light level measurement configuration. Valid Range Sub Name Description 01 Unsigned short light_meas_onoff 02 Unsigned short light_filter not used 03 Unsigned short reserved1 Reserved bytes {1; 10} Presence Detection Configuration UCPTsensorPresence cpsensorpresence Enable/disable light level measurement 0: Disabled 1: Enabled This configuration property is used to set presence detection configuration. Valid Range Sub Name Description 01 Unsigned short pres_meas_onoff 02 Reserved1 Not used 1 Enable/disable presence detection 0: Disabled 1: Enabled Room Device Commands Acquisition UCPTsensorSettings cpsensorsettings This configuration property selects the orders to be acquired from the room device. Valid Range 98 RCL-Light/Blind/ITR User Guide

101 Sub Name Description 01 light_ctrl_off 0: light orders acquisition enabled 1: light orders acquisition disabled 02 sblnd_ctrl_off 0: sunblind orders acquisition enabled 1: sunblind orders acquisition disabled 03 occ_off 0: occupancy orders acquisition enabled 1: occupancy orders acquisition disabled 04 fan_off 0: fan speed orders acquisition enabled 1: fan speed orders acquisition disabled 05 temp_offset_off 0: temperature offset orders acquisition enabled 1: temperature offset orders acquisition disabled {0, 0, 0, 0, 0} Temperature Measurement Acquisition UCPTsensorTemp cpsensortemp This configuration property enables or disables temperature measurement acquisition and sets temperature measurement filter parameters. Valid Range Sub Name Description 01 temp_meas_onoff 0: temperature measurement acquisition disabled 1: temperature measurement acquisition enabled 02 temp_filter Set here in C the temperature variation that triggers temperature measurement variable update. If the variation between two consecutive measurement exceeds temp_filter, the value is not updated. {1, 5} nvosensdata Parameter Selection UCPTenableSensorData cpenablesensordata This configuration property selects the information to be sent through nvosensdata. Valid Range Sub Name Description 01 light_meas 0: light level measurement enabled 1: light level measurement disabled 02 occ 0: occupancy command enabled 1: occupancy command disabled 03 presence 0: presence detection enabled 1: presence detection disabled 04 light_cmd 0: lighting command enabled 1: lighting command disabled 05 sblnd_trans 0: sunblind translation command enabled 1: sunblind translation command disabled RCL-Light/Blind/ITR User Guide 99

102 06 sblnd_rot 0: sunblind rotation enabled 1: sunblind rotation disabled 07 temp_offset 0: temperature offset command enabled 1: temperature offset command disabled 08 fanspeed 0: fan speed command enabled 1: fan speed command disabled 09 temperature 0: temperature measurement enabled 1: temperature measurement disabled 10 fail_safe Not used 11 save_light_setpt Not used {1; 1; 1; 1; 1; 1; 1; 1; 1; 1; 1} nvosenslightlev Automatic Update SCPTmaxSendTime cplightmaxsendt This configuration property indicates the maximum period of time (in seconds) that expires before the sensor object automatically updates nvosenslightlev. Valid Range 0 to SCPT Reference: SCPTmaxSendTime(49) nvosenslightlev Minimum Transition Time SCPTminSendTime cplightminsendt This configuration property indicates the minimum period of time (in seconds) between nvosenslightlev transitions. Valid Range 0 to SCPT Reference: SCPTminSendTime (52) Light Level Variations Required to update nvosenslightlev UCPTminDeltaLight cplightmindelta This configuration property indicates the minimum light level change (in lux) required to update the output network variable nvosenslightlev. Valid Range 0 to RCL-Light/Blind/ITR User Guide

103 Light Level Measurement Calibration UCPTsensorReflect cpsensorreflect This configuration property is used to calibrate the external hardware by specifying the reflection coefficient (in %) to be applied to the hardware sensor input value to match the actual light level. Valid Range 0 to Measure the actual light level using a luxmeter. 2- Read the light level acquired from the sensor input with cpsensorreflect = 100% 3- Enter the reflection coefficient = (sensor light level/actual light level)* nvosenspresence Occupancy Sensitivity UCPTsensorPresFilter cpsensorpresfilter Number of detections needed before considering nvosenspresence as actual. Valid Range 1 to nvosenstemp Automatic Update SCPTmaxSendTime cptempmaxsendt This configuration property indicates the maximum period of time (in seconds) that expires before the sensor object automatically updates nvosenstemp. Valid Range 0 to SCPT Reference: SCPTmaxSendTime (49) Temperature Variations required to update nvosenstemp SCPTminDeltaTemp cptempmindelta This configuration property indicates the minimum temperature change (in C) required to update the output network variable nvosenstemp. Valid Range RCL-Light/Blind/ITR User Guide 101

104 to SCPT Reference: SCPTminDeltaTemp (64) nvosenstemp Minimum Transition Time SCPTminSendTime cptempminsendt This configuration property indicates the minimum period of time (in seconds) between nvosenstemp transitions. Valid Range 0 to SCPT Reference SCPTminSendTime (52) nvosenstemp Offset SCPTtempOffset cptempoffset This configuration property is used to calibrate the external hardware by specifying the offset (in C) applied to nvosenstemp temperature measurement. Valid Range -10 C to +10 C (-18 F to +18 F) 0. SCPT Reference SNVT_temp_diff_p (225). 102 RCL-Light/Blind/ITR User Guide

105 CHAPTER 7 ROOM CONTROLLER OBJECT DESCRIPTION A complete list of the NVs and CPs for the Room Controller LonMark object. In This Chapter Topic Page Overview 104 Manufacturer Network Variables 105 Manufacturer Configuration properties 113 RCL-Light/Blind/ITR User Guide 103

106 Overview The Room Controller object receives the information from the Occupancy Sensor objects and calculates the data to be sent to the Lamp Actuator and Sunblind Actuator objects. Figure 7-1: Room Controller Object 104 RCL-Light/Blind/ITR User Guide

107 Manufacturer Network Variables Occupancy Command Input Network Input SNVT_occupancy nviocccmd nviocccmd defines the operating mode sent by the BMS. Valid Range OC_OCCUPIED: OC_UNOCCUPIED: OC_STANDBY: OC_NUL: The Room Controller object should operate in the occupied mode The Room Controller object should operate in the unoccupied mode The Room Controller object should operate in the standby mode Network variable input invalid or unused. OC_NUL is equivalent to OC_OCCUPIED The default value is OC_NUL. This value will be adopted at power-up. This network variable input does not use the Receive Heartbeat function. Occupancy Sensor Input Network Input SNVT_occupancy nvioccsensor; This network variable input is used to indicate the presence of occupants in the controlled space. It is typically sent by an occupancy sensor. In cases where an occupancy sensor is hardwired to the Room Controller object, a valid value for nvioccsensor will take precedence over the hardwired input. This input is used in conjunction with nviocccmd to determine the effective occupancy mode. Refer to Effective Occupancy Output (nvoeffectoccup) for more information. Valid Range OC_OCCUPIED: OC_UNOCCUPIED: OC_NUL: The Room Controller object should operate in the occupied mode The Room Controller object should operate in the unoccupied mode Network variable input invalid or unused. OC_NUL is equivalent to OC_OCCUPIED The default value is OC_NUL. This value will be adopted at power-up and in case of not receiving an update within the specified receive heartbeat time. This variable is transmitted immediately when its value has changed significantly. Presence Sensor Input Network Input SNVT_occupancy nvipressensor This network variable input is used to acquire presence information from a sensor. RCL-Light/Blind/ITR User Guide 105

108 Valid Range OC_OCCUPIED: OC_UNOCCUPIED: OC_NUL: OC_NUL The Room Controller object should operate in the occupied mode The Room Controller object should operate in the unoccupied mode Network variable input invalid or unused. OC_NUL is equivalent to OC_OCCUPIED Illumination Level Input Value Network Input SNVT_lux nvilightlevel This network variable input provides the ambient light level of the space. Valid Range The valid range is lux with 1 lux resolution, as defined by SNVT_lux Light Command Reception Input Network Input SNVT_switch nvilightcmd This network variable input is used to acquire a light command from a Standard LonMark object Switch. An update to nvilightcmd_x updates nvolampvalue_x unless a valid value is present in nvilightovr_#. Valid Range {0,0 }= Light Off {1,(0 to 100)} = Light On at x % {-1, 0}: invalid Sunblind Command Reception Input Network Input SNVT_setting nvisblndcmd This network variable input is used to receive a sunblind command in standard LonMark format. An update to nvisblndcmd_# updates nvosblndset_# (where # = 1 to 4) unless a valid value is present in nvisblndovr_#. Valid Range Function Translation Rotation Description value x angle α SET_DOWN INV INV Sunblind moves down to closed position or until STOP command is received. INV or 0<x<100% INV or 0 <= α <=360 Sunblind moves down by x% and slats rotate by α (relative commands). 106 RCL-Light/Blind/ITR User Guide

109 Function Translation Rotation Description value x angle α SET_UP INV INV Sunblind moves up to open position or until STOP command is received. 0<x<100% 0 <= α <=360 Sunblind moves up by x% and slats rotate by + α (relative commands). SET_STOP Don t care Don t care Stops sunblind immediately. Interrupts any other command. SET_STATE 0<x<100% -360 <= α <=360 Set the absolute sunblind position to x% and slat angle to α. SET_NUL Don t care Don t care Not used SET_OFF Don t care Don t care Not used SET_ON Don t care Don t care Not used {SET_OFF, 0, 0} BMS Light Command Override Input Network Input SNVT_switch nvilightovr This network variable input is used to acquire a light command from the Building Management System. An update to nvilightovr_x updates nvolampvalue_x and overrides it until a value of -1,0 is received to release the override. Valid Range {0,0 }= Light Off {1,(0 to 100)} = Light On at x % {-1, 0}: disabled BMS Sunblind Command Override Input Network Input SNVT_setting nvisblndovr This network variable input can be used by the Building Management System to override a sunblind. An update to nvisblndovr_# updates nvosblndset_# (where # = 1 to 4) and overrides until a release value is received. Valid Range Function Translation Rotation Description value x angle α SET_DOWN INV INV Sunblind moves down to closed position or until STOP command is received. INV or 0<x<100% INV or 0 <= α <=360 Sunblind moves down by x% and slats rotate by α (relative commands). RCL-Light/Blind/ITR User Guide 107

110 Function Translation Rotation Description value x angle α SET_UP INV INV Sunblind moves up to open position or until STOP command is received. 0<x<100% 0 <= α <=360 Sunblind moves up by x% and slats rotate by + α (relative commands). SET_STOP Don t care Don t care Stops sunblind immediately. Interrupts any other command. SET_STATE 0<x<100% -360 <= α <=360 Set the absolute sunblind position to x% and slat angle to α. SET_NUL Don t care Don t care Deactivates sunblind blocking from BMS SET_OFF Don t care Don t care Not used SET_ON Don t care Don t care Not used {SET_OFF ; 0 ; 0} Sensor Communication Input Network Input UNVT_Dalilon nvisensdata This network variable input is used to acquire data from the occupancy sensor object (Temperature, light level, presence detection, user commands). Valid Range 108 RCL-Light/Blind/ITR User Guide

111 Light level measurement Bitset LuxLevel Occ Reserved1 Reserved2 Reserved3 Reserved4 1 Filtered light level measurement Room Occupied/ occupancy Unoccupied Presence 3 - Occupied detection Light Push / /- Key - Group command release Sunblind /- Key or setting - - Group commands Temperature Temperature offset Offset Fan speed Fan speed Filtered Temperature 8 temperature measurement measurement Light level setpoint Unoccupancy inhibit delay Light level setpoint (lux) Unoccupancy delay (x 100 ms) Fail-safe mode 90 Error type - Configuration remote control {0, 0, OC_OCCUPIED, 0, 0, 0, 0} : GTB_OCC 2 : GTB_UNOCC 3 : GTB_STDBY Erreur : 1 Fin erreur : Effective Light Measurement Network Output SNVT_lux nvolightlevel This network variable output is used to transmit the room effective light measurement to the BMS (in lux). This value can output the multi-sensor light level or the corrected light level. This value is calculated from nvilightlevel according the following formula: nvolightlevel = Filtered nvilightlevel + nvolampvalue1 + nvolampvalue2 cplightctrlset. light_power x Typical Range When Transmitted This variable is transmitted whenever the value has changed. Occupancy Detection Output Network Output SNVT_occupancy nvopresence This network variable output is used to transmit the occupancy detection. Occupancy detection can be read from the RJ9 input, from nvipresence or from a digital input. Valid Range RCL-Light/Blind/ITR User Guide 109

112 OC_OCCUPIED: OC_UNOCCUPIED: OC_NUL: 1 = OC_NUL The Room Controller object should operate in the occupied mode The Room Controller object should operate in the unoccupied mode Network variable input invalid or unused. OC_NUL is equivalent to OC_OCCUPIED Effective Occupancy Status Output Network Output SNVT_occupancy nvoeffectoccup This network variable output is used to indicate the actual occupancy mode of the unit. This information is typically reported to a supervisory controller, or provided to another Room Controller object to coordinate the operation of multiple units. The effective occupancy is set depending on nviocccmd and room occupancy according to UCPToccCtrl scenario. Valid Range OC_OCCUPIED: OC_UNOCCUPIED: OC_STANDBY: OC_NUL: OC_NUL. When Transmitted The Room Controller object should operate in the occupied mode The Room Controller object should operate in the unoccupied mode The Room Controller object should operate in the standby mode Network variable input invalid or unused. OC_NUL is equivalent to OC_OCCUPIED The variable is transmitted immediately when its value has changed. Additionally, this network variable is also transmitted as a heartbeat output on a regular basis as dictated by the Maximum Send Time (cpmaxsendtime) configuration value. Default Service Type The default service type is unacknowledged. Lamp Actuator Commands Network Output SNVT_switch nvolampvalue# (#=1 or 2) These network variable outputs provide the state of command for the matching lamp actuator (ON or OFF) and the percentage level of intensity. Valid Range The valid range of the state is as defined for SNVT_switch where 0 means OFF and 1 means ON. The 8-bit intensity value contains a value 0 to 200, representing minimum to maximum (0%-100%) intensity. 110 RCL-Light/Blind/ITR User Guide

113 {-1;0} When Transmitted Whenever the state or intensity of the lamp actuator is required to change. Sunblind Actuator Commands Network Output SNVT_setting nvosblndset# (#=1 or 2) These network variable outputs provide the state of command for the sunblind actuator object. Valid Range Function Translation Rotation Description value x angle α SET_DOWN INV INV Sunblind moves down to closed position or until STOP command is received. INV or 0<x<100% INV or 0 <= α <=360 Sunblind moves down by x% and slats rotate by α (relative commands). SET_UP INV INV Sunblind moves up to open position or until STOP command is received. INV or 0<x<100% INV or 0 <= α <=360 Sunblind moves up by x% and slats rotate by + α (relative commands). SET_STOP Don t care Don t care Stops sunblind immediately. SET_STATE 0<x<100% -360 <= α <=360 SET_NUL Don t care Don t care Not used SET_OFF Don t care Don t care Not used SET_ON Don t care Don t care Not used Interrupts any other command. Set the absolute sunblind position to x% and slat angle to α. Invalid values (INV) are respectively 0xFF (127.5) for translation value and 0xFFFF (355.34) for rotation angle. is {SET_OFF; 0; 0} When Transmitted Whenever the state or intensity of the sunblind actuator is required to change. Lighting Control Output Network Output SNVT_setting nvolightcontrol This network variable output is used to control the lighting in compatibility mode. This variable can be used to control lighting of legacy controllers using the device as a master node. Typical Range RCL-Light/Blind/ITR User Guide 111

114 nvolampvalue1/2 nvolightcontrol Description Light Behavior State Value Function Setting Rotation 1(On) 100% Dim Lights Up 0(Off) 0% Dim Lights Down 1(On) 0<x<100% -1(Nul) 0% {SET_OFF, 0, 0} Control Lights at x level Stop Lights dimming When Transmitted Lights Dim Up or Until a Stop Command is received Lights Dim Down or until a Stop Command is received Lights are dimmed until they reach x % Lights are stopped at their current level SET_STATE 100% -11 & -12 SET_STATE 0% -11 & -12 SET_ON 0<x<100% -21 & -22 SET_STOP 0% -11 & -12 Whenever the state or intensity of the lamp actuator is required to change effective light measurement output. Sunblind Control Output Network Output SNVT_setting nvosblndcontrol This network variable output is used to to control the sunblinds. This is used for compatibility mode with the IRC-SRC Series and CR Series controllers. nvosblndcmd1/2 nvosblndcontrol Description Sunblind Behavior Function Setting Rotation Function Setting Rotation SET_DOWN SET_UP INVALID INVALID INVALID 0< α <360 0<x<100% 0< α <360 0<x<100% INVALID INVALID INVALID INVALID 0< α <360 0<x<100% 0< α <360 0<x<100% INVALID Sunblind moves down Relative slats angle downwards Sunblind move down relatively and slats rotates downwards relatively Sunblind moves down relatively Sunblind moves up Relative slats angle upwards Sunblind move up relatively and slats rotates upwards relatively Sunblind moves up relatively SET_STOP Don t care Don t care Sunblinds stop SET_STATE 0<x<100% INVALID 0<x<100% INVALID -360<α< <α<360 Sunblind translation setting only Sunblind rotation setting only Sunblind translation to x position and slat rotation to α angle Sunblind moves down to the position specified in the actuator device or until STOP command is received Sunblind rotates the slats downwards by a relative angle of α Sunblind moves down relatively and rotates relatively. If α=0, the slat angle remains the same. Moves the sunblind down by x%. The slat angle remains the same Sunblind moves up to the position specified in the actuator device or until STOP command is received Sunblind rotates the slats upwards by a relative angle of α Sunblinds move up relatively and rotates relatively. If α=0, the slat angle remains the same Moves the sunblinds up by x%. The slats angle remains the same Immediately stops the sunblinds Sets the absolute position as specified in the setting field Sets the absolute rotation angle as specified in the roataion field Sets the absolute sunblind position to x and the slat rotation angle to α. SET_DOWN 0-31 & -32 NOT SUPPORTED NOT SUPPORTED NOT SUPPORTED SET_UP 0-31 & -32 NOT SUPPORTED NOT SUPPORTED NOT SUPPORTED SET_STOP 0-31 & -32 NOT SUPPORTED NOT SUPPORTED SET_STATE See tables 1 & 2-31 & RCL-Light/Blind/ITR User Guide

115 When Transmitted The variable is transmitted immediately when its value has changed Lighting Command State Output Manufacturer Configuration properties Light Level Setpoint SCPTluxSetpoint nciluxsetpoint This configuration property is used to change the illumination level setpoint for the controller. Valid Range The valid range is lux with 1 lux resolution, as defined for SNVT_lux. The default value is 300. SCPT Reference SCPTluxSetpoint #82 Room Controller Object Coupling UCPTcoupling cpcoupling This configuration property is used to slave the room controller object to another one. In this case, the settings of the master room controller are dynamically applied to the slaves. When a room controller object X is coupled with a room controller object Y, light control loop parameters, installation configuration parameters, dimming control parameters as well as occupancy settings are no more retrievable. Nervertheless it is still possible to act on lighting commands and sunblind commands independenly so as to be able to control different equipment types. Valid Range 0: master 1: slaved to room controller 1 2: slaved to room controller 2 3: slaved to room controller 3 4: slaved to room controller 4 The default value is 0. Dimming Configuration UCPTdimCtrl cpdimctrl This configuration property is used to slave the room controller object to another one. Valid Range RCL-Light/Blind/ITR User Guide 113

116 Sub Name Description 01 Mode Dimming command source: 0: Lamp Actuator Object 1: Room Controller Object 02 step Increment step (in %) Range: 0 to Period Time between each increment step (in tenths of second). Range: 0 to 255 The default value is {0 ; 5 ; 1}. Light Loop Configuration UCPTlightCtrlSet cplightctrlset This configuration property defines the light loop configuration Valid Range Sub Name Description 01 prop_band Not used 02 int_time Not used 03 fast_zone Not used 04 deadband Not used 05 win_side_scaling[0] Low threshold (in %) for window side lighting Minimum value: 0 Maximum value: win_side_scaling[1] High threshold (in %) for window side lighting Minimum value: 0 Maximum value: corr_side_scaling[0] Low threshold (in %) for corridor side lighting Minimum value: 0 Maximum value: corr_side_scaling[1] High threshold (in %) for corridor side lighting Minimum value: 0 Maximum value: loop_ctrl_prd Not used 10 light_power Total power supplied by the lighting devices installed inside the room (in lux). Minimum value: 0 Maximum value: light_power_ratio Not used 12 light_effect_mode Not used 13 light_mean_n Number of light level measurements to average light level value in order to smooth nvolightlevel (Low pass 1 st order filter). 14 reserved1 Not used {0; 0; 0; 0; 25; 100; 0; 75; 0; 500; 0; 0; 1; 0} Occupancy Management & Default Room Settings UCPToccCtrl cpoccctrl This configuration property defines the room occupancy management. 114 RCL-Light/Blind/ITR User Guide

117 Valid Range Sub Main Variables Description 01 user_occ_cfg Not used 02 BMS_occ_cfg Defines BMS occupancy status according to room occupancy status Default: 0 03 unocc_inhibit_delay Timer for blocking of the presence detection, in seconds. (0: unlimited) Default: Reserved Not used 05 first_occupancy First occupancy lighting and sunblind settings 06 BMS_occupancy [3] Configuration of the light and sunblind behaviour during the various occupancy states. Includes room_occ & room_unocc 02: BMS_occ_cfg Defines room occupancy status when BMS occupancy changes 0 Room occupancy is independent from BMS occupancy 1 If BMS occupancy switches to 'occupied', room occupancy switches to 'occupied' 2 If BMS occupancy switches to 'unoccupied', room occupancy switches to 'unoccupied' 3 Room occupancy follows BMS occupancy (combination of 1 & 2) Default 2 03: Timer for blocking of the presence detection, in seconds unocc_inhibit_delay Default 10 seconds 0 Unlimited 05: first_occupancy Defines the sunblind positioning when the room is actually detected as occupied for the first time after the BMS occupancy switched to occupied sblnd_trans Sunblinds translation (step =10%) Valid Range: 0 to 10 : 0 to 100% 11 : not commanded Default: 0 sblnd_rot Sunblind slats angle (only available if sblnd_trans 11): - 0: 0-1: 45-2: 90-3: 135-4: 180-5: : : -90-8: to 15: 0 Default: 0 RCL-Light/Blind/ITR User Guide 115

118 06: BMS_occupancy[X) BMS_occupancy[0] BMS_occupancy[1] BMS_occupancy[2] Defines the BMS Occupancy Status used when the BMS occupancy is 'occupied' (or any other value) used when the BMS occupancy is 'unoccupied' used when the BMS occupancy is standby Default parameters below are described as follows: {BMS_occupancy[0].room_occ value ; BMS_occupancy[1].room_occ value ; BMS_occupancy[2].room_occ value ; BMS_occupancy[0].room_unocc value ; BMS_occupancy[1].room_unocc value ; BMS_occupancy[2].room_unocc value} room_occ / room_unocc light_ovr_en1 light_ovr_en2 light_ctrl_en1 light_ctrl_en2 sblnd_ovr_en1 sblnd_ovr_en2 pres_enable fan_rst Offset_rst dim_light1 dim_light2 Defines the different commands according to occupancy statuses 0: 'Window side' light groups are not controlled 1: 'Window side' light groups are controlled (switched on at N% or switched off) Default: {0 ; 0 ; 0 ; 1 ; 1 ; 1} 0: 'Corridor side' light groups are not controlled 1: 'Corridor side' light groups are controlled (switched on at N% or switched off) Default: {0 ; 0 ; 0 ; 1 ; 1 ; 1} 0: 'Window side' light groups are not controlled 1: 'Window side' light groups are controlled as a function of the Light level- default Default: {1 ; 1 ; 1 ; 0 ; 0 ; 0} 0: 'Corridor side' light groups are not controlled 1: 'Corridor side' light groups are controlled as a function of the light level Default: {1 ; 1 ; 1 ; 0 ; 0 ; 0}} 0: Sunblinds are not controlled 1: Sunblinds are controlled Default: {0 ; 0 ; 0 ; 0 ; 1 ; 0} Not used 0 : Presence detection is deactivated 1: Presence detection is activated Default: {1 ; 1 ; 1 ; 1 ; 1 ; 1} 0: fan command is reset on occupancy change 1: fan command is not reset on occupancy Default: {0 ; 1 ; 1 ; 0 ; 1 ; 1} 0: Temperature setpoint offset is reset on occupancy 1: Temperature setpoint offset is not reset on occupancy change Default: {0 ; 1 ; 1 ; 0 ; 1 ; 1} Dimming value for 'Window side' light groups (light_ovr_en1 =1), step = 10%. Valid Range: 0 to 10 : 0 to 100% Default: {100 ; 100 ; 100 ; 0 ; 0 ; 0} Dimming value for Corridor side' light groups (light_ovr_en2 =1), step = 10%. Valid Range: 0 to 10 : 0 to 100%Default: {100 ; 100 ; 100 ; 0 ; 0 ; 0} sblnd_trans Sunblinds translation (step =10%) Valid Range: 0 to 10 : 0 to 100% Default: {0 ; 0 ; 0 ; 0 ; 100 ; 0} 116 RCL-Light/Blind/ITR User Guide

119 sblnd _rot:4 reserved4 reserved5 room_unocc_delay effect_occ_cfg analog_fan_inhibit:1 analog_offset_inhibit:1 reserved6 Sunblind slats angle: - 0: 0-1: 45-2: 90-3: 135-4: 180-5: : : -90-8: to 15: 0 Default: {0 ; 0 ; 0 ; 0 ; 0 ; 0} Time in seconds during which the room is considered as occupied after a presence detection (only for room_occ) Default: {900 ; 300 ; 900 ; N/A ; N/A ; N/A} Value of the variable nvoocceffect during this occupancy state Default: {OC_OCCUPIED ; OC_OCCUPIED; OC_STANDBY; OC_UNOCCUPIED ; OC_UNOCCUPIED; OC_STANDBY } Not used Not used Lighting Command Configuration Network input config UCPTgrpSet cplightgrpset This configuration property defines the origin of lighting commands (control group and remote control group) sent by the controller through nvolampvalue. Valid Range Sub Name Description 01 ctrl_grp Defines the control group of the lighting command 1 : Window side 2 : Corridor side 02 user_grp Defines the remote control group of the lighting command 1: group 1 2: group 2 3: group 3 4: group 4 5: group 5 6: group 6 7: group 7 8: group 8 03 reserved1 Not used {X ; X} RCL-Light/Blind/ITR User Guide 117

120 Lighting Command Value UCPTlightCtrlAdj cplightctrladj This configuration property defines lighting commands sent by the controller through nvolampvalue. Valid Range Sub Name Description 01 ctrl_onoff 0: Not driven by loop control 1: Driven by loop control 02 min_ctrl minimum intensity (0%-100%) 03 reserved1 Reserved {1; 0} Initial Lighting Command UCPTlightInit cplightinit This configuration property defines lighting commands to be sent by the controller on reset or power-up through nvolampvalue. Valid Range Sub Name Description 01 value Value of initial lighting command (%) 02 state 0: Lamp OFF 1: Lamp ON {100; 1} Light Shedding UCPTlightShedding cplightshedding This configuration property activates/deactivates light shedding applied to nvolampvalue. Valid Range 0: Light Shedding disabled 1: Light Shedding enabled 1 Sunblind Groups UCPTgrpSet cpsblndgrpset This configuration property defines the user and control groups to which nvosblndsetx belongs to. 118 RCL-Light/Blind/ITR User Guide

121 Valid Range Sub Name Description 01 ctrl_grp Not used 02 user_grp Indicates to which user group nvosblndsetx is assigned. 0: All groups 1: group 1 2: group 2 3: group 3 4: group 4 5: group 5 6: group 6 7: group 7 8: group 8 With X = 1, 2 {X,X} Initial Sunblind Commands UCPTsblndInit cpsblndinit This configuration property defines sunblind commands to be sent by the controller on reset or power-up through nvosblndset. Valid Range Sub Name Description 01 unsigned short Function function 02 unsigned short setting Sunblind initial positioning: translation Valid Range: 0 to 100% 03 Unsigned short rotation {SET_STATE; 50; -90} Sunblind initial positioning: rotation ( ) Valid Range: to 360 RCL-Light/Blind/ITR User Guide 119

122 CHAPTER 8 LAMP ACTUATOR OBJECT DESCRIPTION A complete list of the NVs and CPs for the supported LonMark objects. In This Chapter Topic Page Overview 121 Mandatory Network Variables 122 Optional Network Variables 122 Manufacturer Network Variables 123 Manufacturer Configuration Properties RCL-Light/Blind/ITR User Guide

123 Overview The LONMARK Lamp Actuator profile. The profile is used for devices that can control the illumination level of a lamp. Typical lamp actuators are dimmers, relays and controllable electronic ballasts. The Lamp Actuator object embeds energy counting variables and value forwarding variables. Figure 8-1 Lamp Actuator Object Overview RCL-Light/Blind/ITR User Guide 121

124 Mandatory Network Variables Value Input Network Input SNVT_switch nvilampvalue This network variable input provides a means for another device to pass data to the lamp actuator. Valid Range The valid range of the state is as defined for SNVT_switch where 0 means off and 1 means on (255 - undefined - is rejected). The 8-bit intensity value goes from 0 to 200, representing minimum to maximum (0%-100%) intensity. {0,-1} Value Feedback Output Network Output SNVT_switch nvolampvaluefb This output network variable provides the state of the lamp actuator (ON or OFF) and the percentage level of intensity. Valid Range The valid range of the state is as defined for SNVT_switch where 0 means off and 1 means on (255 - undefined - is not used). The 8-bit intensity value goes from 0 to 200, representing minimum to maximum (0%-100%) intensity. {0, 0} When Transmitted: Whenever the state or intensity of the lamp actuator is requested to change. Default Service Type The default service type is unacknowledged. Optional Network Variables Running Hours Output Network Output SNVT_elapsed_tm nvorunhours This network variable output provides the lamp actuator s running hours. The timer is enabled (counting time) whenever the lamp actuator is turned ON. Valid Range The valid range is 0 to days, 23 hours, 59 minutes, 59 seconds and 999 ms RCL-Light/Blind/ITR User Guide

125 When Transmitted: On request. The application updates the output variable when the hour is changed. Default Service Type: The default service type is unacknowledged. Lamp Energy Consumption Network Output SNVT_elec_kwh nvoenergycnt This network variable output provides the total consumption of the lamp since nvorunhours initialization (nvorunhours_x*ucptlightw). Valid Range Manufacturer Network Variables Control-Forwarding Output Network Output config SNVT_switch nvolampvaluefwd This network variable output is used to forward the input NV of nvilampvalue to another device or functional block. Valid Range The valid range of the state is as defined for SNVT_switch where 0 means off and 1 means on (255 - undefined - is rejected). The 8-bit intensity value goes from 0 to 200, representing minimum to maximum (0%-100%) intensity. {-1,0} Manufacturer Configuration Properties Light Configuration Network input config UCPTlightCfg cplightcfg This configuration property is used to configure the lamp type. Valid Range Sub Main Variables Description 01 type Used to indicate the type of lighting 0: Digital (ON/OFF) 1: Dimming 02 min_dimming For digital lights: value (in %) below which the lamp is turned OFF. RCL-Light/Blind/ITR User Guide 123

126 For dimmable lights: value (in %) below which the lamp is OFF. 03 max_dimming For digital lights: value (in %) above which the lamp is turned ON. For dimmable lights: value (in %) above which the lamp is set to max_dimming. 04 dimming_time Time in seconds to dim from 0% to 100%. Min: 1. Max: 25.5 s. 05 Reserved1 Not used {1; 0; 100; 5; 0} Light Power Network input config UCPTlightW cplightw This configuration property is used to configure the lamp power in Watts Valid Range RCL-Light/Blind/ITR User Guide

127 CHAPTER 9 SUNBLIND ACTUATOR OBJECT DESCRIPTION A complete list of the NVs and CPs for the supported LonMark objects. In This Chapter Topic Page Overview 126 Mandatory Network Variables 127 Optional Network Variables 128 Manufacturer Network Variables 129 Manufacturer Configuration Properties 129 RCL-Light/Blind/ITR User Guide 125

128 Overview The network interface definition is based on the LONMARK Sunblind Actuator profile. The Sunblind Actuator functional block is used to drive a motorized sunblind to a specific position (length) and/or angle. Figure 9-1 Sunblind Actuator Object Overview 126 RCL-Light/Blind/ITR User Guide

129 Mandatory Network Variables Setting Input Network Input SNVT_setting nvisblndset When using SNVT_setting for sunblinds, note that there are different types of sunblinds available on the market, which may differ in their mechanical possibilities. These differences may be exposed through the resulting UP and DOWN movement and slat movement. For example, with standard shutters: Only the sunblind position is adjustable. A slat angle is usually not available. However, using Venetian blinds: The sunblind position is adjustable as well as the slat angle. The following table is related to the use of Venetian blinds, which are a complex sunblind type. All other sunblind types may be controlled easily with the same consideration, but noting that some sunblinds do not have the Slat angle feature. Valid Range Function SET_DOWN SET_UP Translation value x INV INV or 0<x<100% INV Rotation angle α INV INV or 0 <= α <=360 INV 0<x<100% 0 <= α <=360 SET_STOP Don t care Don t care SET_STATE 0<x<100% -360 <= α <=360 Description SET_NUL Don t care Don t care Not used SET_OFF Don t care Don t care Not used SET_ON Don t care Don t care Not used Sunblind moves down to closed position or until STOP command is received. Sunblind moves down by x% and slats rotate by α (relative commands). Sunblind moves up to open position or until STOP command is received. Sunblind moves up by x% and slats rotate by + α (relative commands). Stops sunblind immediately. Interrupts any other command. Set the absolute sunblind position to x% and slat angle to α. Invalid values (INV) are respectively 0xFF (127.5) for translation value and 0x7FFF (355.34) for rotation angle. Relative positioning relate always on the fully mechanical/physical movement range of a sunblind. {SET_OFF, 0,0} RCL-Light/Blind/ITR User Guide 127

130 Control-Forwarding Output Network Output SNVT_setting nvosblndsetfb This network variable output is used to provide feedback of the actual sunblind state, received from an RCx add-on module, to another device or functional block. Valid Range Function Translation Rotation position x slat angle α SET_STATE Absolute position Absolute angle {SET_OFF, 0,0} Optional Network Variables Running Hours Output Network Output SNVT_elapsed_tm nvorunhours This network variable output provides the sunblind actuator s running hours. The timer is enabled (counting time) whenever the sunblind actuator is turned ON. Valid Range The valid range is 0 to days, 23 hours, 59 minutes, 59 seconds and 999 ms. 0 When Transmitted: On request. The application updates the output variable when the hour is changed. Default Service Type: The default service type is unacknowledged. Sunblind Energy Consumption Network Output SNVT_elec_kwh nvoenergycnt This network variable output provides the total consumption of the sunblind since nvorunhours initialization (nvorunhours_x*ucptsblndw). Valid Range RCL-Light/Blind/ITR User Guide

131 Manufacturer Network Variables Control-Forwarding Output Network Output SNVT_setting nvosblndsetfwd This network variable output is used to provide feedback or to forward the input NV command of nvisblndset to another device or functional block. Valid Range The valid range of nvisblndset. {SET_OFF, 0,0} Configuration Considerations The transmission of this NV is regulated by the nvisblndset NV. When Transmitted: The output variable is transmitted: when the state of nvisblndset has changed. when polled. Default Service Type: The default service type is unacknowledged and repeated. Manufacturer Configuration Properties Sunblind Configuration Network input config UCPTsblndCfg cpsblndcfg This configuration property is used to configure the sunblind type. Valid Range Sub Variables Description 01 polarity Sunblind polarity. Can be used to correct wiring error. 0: Direct 1 to 255: Reverse 02 translation_time Full translation time (in seconds) for the sunblind. Range: 0 to rotation_time Full rotation time for the sunblind. Range: 0 to rotation_step Slat rotation step (%) Range: rotation_step_delay Time between rotation steps (in seconds). Range: 0 to max_angle Maximum angle (in ) of sunblind rotation. Range: to min_angle Minimum angle (in ) of sunblind rotation. Range: to 360 RCL-Light/Blind/ITR User Guide 129

132 08 boot_delay Sunblind starting time (in tenths of seconds) Range: 0 to 2550 {0 ; 30 ; 0 ; 10 ; 0.2 ; 0 ; -90 ; 0} Sunblind Power Network input config UCPTsblndW cpsblndcfg This configuration property is used to configure the sunblind power in Watts 60. SNVT_temp_diff_p (225). 130 RCL-Light/Blind/ITR User Guide

133 CHAPTER 10 APPENDICES This section exposes the devices default configuration, demand response management and compatibility wih legacy controllers. In This Chapter Topic Page Default Configuration 132 Smart Grid Integration: Demand Response 135 Compatibility with the CTR Series product line 137 Coupling Control - Example 142 RCL-Light/Blind/ITR User Guide 131

134 Default Configuration When first powering the device, default bindings are set to allow for direct installation. All default bindings are canceled if: - Room controller object s cpcoupling is different from 0. - Another variable is binded on a NVI used in the default configuration. Default bindings are reset when - Room controller object s cpcoupling is set to 0, and the eventually modified NVIs are set back to their default binding. Network Interface Default Configuration X = 1 to RCL-Light/Blind/ITR User Guide

135 Lighting Controllers Default Configuration X = 1 to 4 Lamp Actuator object n (X+4) is not used for 4-channel controllers.

136 Sunblind Controllers Default Configuration X = 1 to 4 Sunblind Actuator object n (X+4) is not used for 4-channel controllers. 134 RCL-Light/Blind/ITR User Guide

137 Smart Grid Integration: Demand Response Introduction Smart Grid A smart grid is a modernized electrical grid that uses information and communications technology to gather and act on information, such as information about the behaviors of suppliers and consumers, in an automated fashion to improve the efficiency, reliability, economics, and sustainability of the production and distribution of electricity. The total load connected to the power grid can vary significantly over time. Although the total load is the sum of many individual choices of the clients, the overall load is not a stable, slow varying, average power consumption. Traditionally, to respond to a rapid increase in power consumption, faster than the start-up time of a large generator, some spare generators are put on a dissipative standby mode. A smart grid may warn all specified individual loads, or another larger customer, to reduce the load temporarily (to allow time to start up a larger generator) or continuously (in the case of limited resources). In the traditional grid, the failure rate can only be reduced at the cost of more standby generators. In a smart grid, the load reduction by even a small portion of the clients may eliminate the problem. To reduce demand during the high cost peak usage periods, communications and metering technologies inform smart devices in the home and business when energy demand is high and track how much electricity is used and when it is used. It also gives utility companies the ability to reduce consumption by communicating to devices directly in order to prevent system overloads. One advantage of a smart grid application is time-based pricing. Customers who traditionally pay a fixed rate for kwh and kw/month can set their threshold and adjust their usage to take advantage of fluctuating prices. This may require the use of an energy management system to control appliances and equipment and can involve economies of scale. Another advantage, mainly for large customers with generation, is being able to closely monitor, shift, and balance load in a way that allows the customer to save peak load and not only save on kwh and kw/month but be able to trade what they have saved in an energy market. Again this involves sophisticated energy management systems, incentives, and a viable trading market. Demand response Demand response support allows generators and loads to interact in an automated fashion in real time, coordinating demand to flatten spikes. Eliminating the fraction of demand that occurs in these spikes eliminates the cost of adding reserve generators, cuts wear and tear and extends the life of equipment, and allows users to cut their energy bills by telling low priority devices to use energy only when it is cheapest. According to Federal Energy Regulatory Commission, Demand Response (DR) is defined as Changes in electric usage by end-use customers from their normal consumption patterns in response to changes in the price of electricity over time, or to incentive payments designed to induce lower electricity use at times of high wholesale market prices or when system reliability is jeopardized. DR includes all intentional modifications to consumption patterns of electricity of enduse customers that are intended to alter the timing, level of instantaneous demand, or the total electricity consumption. Basically, demand response allows to manage customer consumption of electricity in response to supply conditions. Electrical generation and transmission systems may not always meet peak demand requirements the greatest amount of electricity required by all utility customers within a given region. In these situations, overall demand must be lowered, either by turning off service to some devices or cutting back the supply voltage (brownouts), in order to prevent uncontrolled RCL-Light/Blind/ITR User Guide 135

138 service disruptions such as power outages (widespread blackouts) or equipment damage. Utilities may impose load shedding on service areas via rolling blackouts or by agreements with specific high-use industrial consumers to turn off equipment at times of system-wide peak demand. Demand response management Light Shedding Lighting controllers, sunblind controllers, and network interfaces controllers embed demand response management to comply with smart grid systems. The load shedding demand is acquired from Occupancy Sensor Object s nvilightshedding and is treated in the Room Controller Object so as to modulate Room Controllers nvolampvalue lighting commands directly with the load shedding demand according to the following formula: nvolampvalue = light control loop value x (1 nvilightshedding) For example, if a 25% load shedding is applied through nvilightshedding, nvolampvalue is decreased by 25%: - The maximum command reachable by nvolampvalue is 75%. - If nvolampvalue command was 50% before the load shedding was applied (whereas set by the end user through the room device or calculated by the light control loop), the new value is : 50% x (1-25%) = 37.5% The end user can still manage the lighting command from 0 to 100%. Nevertheless, as the 25% decrease is applied to nvolampvalue, a 100% user command will result in a 75% nvolampvalue command. Occupancy statuses modifications do not interrupt load shedding application. A load sheeding command applied to an Occupancy Sensor Object X is applied to all nvolampvalue lighting outputs of the Room Controller Object X, as well as on nvolampvalue lighting outputs of all Room Controller Objects slaved to Room Controller X. Proper use of demand response functionality requires its activation in cplightshedding and appropriate binding of nvilightshedding. 136 RCL-Light/Blind/ITR User Guide

139 Compatibility with the CTR Series product line Introduction The RCL-Light/Blind controllers are implementing the Lamp Actuator and Sunblind Actuator object profiles from the LonMark association thus making them different from the CTR controllers when controlling lights and sunblinds. When using existing CTR Series controllers with RCL-Light/Blind Series of controllers, specific configurations must be made to make them compatible. The RoomCtrl object of the RCL controller needs to be responsible for the light and blind control based on lux level, occupancy, remote control and bms commands/overrides The RoomCtrl objects of the RCL-Light/Blind controllers are using variables nvolampvalue1/2 and nvosblndset1/2 to control the Lamp Actuator and Sunblind Actuator objects. To be able to control CTR Series Light and Blind objects from the RCL-Light/Blind, one must use the following variables: nvolightcontrol and nvosblndcontrol from these RoomCtrl objects. The nvolightcontrol and nvosblndcontrol variables are often referred as the compatibility variables; they implement parts of the CTR Series control scheme for lighting and sunblinds. The following sections detail how to configure your CTR series of controllers to make them compatible with the RCL-Light & Blind series of controllers. CTR Lighting controllers configuration for use with RCL- Light/ Blind controllers a. Each RCL-Light/Blind RoomCtrl objects can control up to 2 control groups (Window / Corridor). Each of these 2 control groups can have a specific room sensor override group #. The easiest way to configure this is by using the Configuration Plug-In/Wizard. b. In the example above, the variable RoomCtrl01/nvoLampValue1 (LightCmd1) will be linked with the following; Room sensor overrides from Group #1 Control loop signal for Window side Commands from RoomCtrl01/nviLightCmd1 Overrides from RoomCtrl01/nviLightOvr1 RCL-Light/Blind/ITR User Guide 137

140 c. Once this is done, the CTR Lighting controller must be configured to make it compatible with the RCL-Light/Blind controller. For compatibility mode, the system is controlling the light objects of the CTR controller using remote control groups. To link a light object from a CTR controller to the nvolightcontrol of an RCL-Light/Blind controller, the user must configure the following parameters: CTR/Light[x]/UCPT_Lum_Cfg/LightMode 0 On/Off Lights (CTR-4L/8L) 1 Dimmable Lights (CTR-4LD/8LD) 2 DALI Control (CTR-DALI-LR8/16 and CTR-8L-DALI) CTR/Light[x]/UCPT_Lum_Cfg/Group 1 the light is linked to nvolampvalue1 2 the light is linked to nvolampvalue2 Caution, setting this value to any value other than 1 or 2 will make this Light incompatible with RCL-Light & Blind controllers. CTR/Light[x]/UCPT_Lum_Cfg/MinGrada For Dimmable Lights, the minimum value of the lights. For On/Off Lights, the threshold value to set the light on or off. CTR/Light[x]/UCPT_Lum_Regul/RegulGroup This value must be set to the same value as the UCPT_Lum_Cfg/Group Note that no other parameters in UCPT_Lum_Regul is used in this configuration. d. Once the CTR controller configured, bindings need to be made between the RCL controller and the CTR controller. To link a light object from the CTR controller to the Light control loop of the RCL controller, these 2 variables need to be bound together. RCL/RoomCtrl0x/nvoLightControl_x CTR/Light[x]/nviCmdLum e. The following commands will be sent over the network on the nvolightcontrol_x compatibility variable based on the value sent by nvolampvalue1/2 nvolampvalue1/2 nvolightcontrol Description Light Behavior State Value Function Setting Rotation 1(On) 100% Dim Lights Up 0(Off) 0% Dim Lights Down 1(On) 0<x<100% -1(Nul) 0% Control Lights at x level Stop Lights dimming Lights Dim Up or Until a Stop Command is received Lights Dim Down or until a Stop Command is received Lights are dimmed until they reach x % Lights are stopped at their current level SET_STATE 100% -11 & -12 SET_STATE 0% -11 & -12 SET_ON 0<x<100% -21 & -22 SET_STOP 0% -11 & RCL-Light/Blind/ITR User Guide

141 CTR Sunblind controllers configuration for use with RCL- Light/ Blind controllers a. Each RCL-Light/Blind RoomCtrl objects can operate sunblind depending on occupancy information and room sensor override group #. The easiest way to configure this is by using the Configuration Plug-In/Wizard. b. In the example above, the variable RoomCtrl01/nvoSblndSet1 (Sunblind Cmd 1) will be linked with the following; Room sensor overrides from group #3 Occupancy options Commands from RoomCtrl01/nviSblndCmd1 Overrides from RoomCtrl01/nviSblndOvr1 c. Once this is done, the CTR Sunblind controller must be configured to make it compatible with the RCL-Light/Blind controller. In compatibility mode, the system controls the sunblind objects of the CTRL controller through control groups. To link a sunblind object from a CTR controller to the nvosblndcontrol of an RCL-Light/Blind controller, the following parameters are to be configured: CTR/Store[x]/UCPT_Store_Cfg/StoreMode 0 Up/Down commands only 1 Up/Down and absolute position (Must be set to 1) CTR/Store[x]/UCPT_Store_Cfg/Group 1 the sunblind is linked to nvosblndset1 2 the sunblind is linked to nvosblndset 2 Caution, setting this value to any value other than 1 or 2 will make this Sunblind incompatible with RCL- Light & Blind controllers. CTR/Store[x]/UCPT_Store_Regul/Regul_Group This value must be set to the same value as UCPT_Store_Cfg/Group Note that all the other parameters in UCPT_Store_Regul aren t used in this configuration. RCL-Light/Blind/ITR User Guide 139

142 d. After having configured the CTR controller, bindings need to be made between the RCL- Light & Blind controller and the CTR. To link a sunblind object from the CTR controller to the Sunblind control logic of the RCL controller, these 2 variables need to be bound together: RCL/RoomCtrl0x/nvoSblndControl_x CTR/Store[x]/nviCmdStore e. The following commands will be sent over the network on the nvosblndcontrol_x compatibility variable based on the value sent by nvosblndset1/2: nvosblndcmd1/2 nvosblndcontrol Description Sunblind Behavior Function Setting Rotation Function Setting Rotation SET_ DOWN SET_UP INVALID INVALID 0<x<100% 0<x<100% INVALID 0<α<360 0<α<360 INVALID Sunblind moves down Relative slat angle downwards Sunblind and slats move down relatively Sunblind moves down relatively INVALID INVALID Sunblind moves up INVALID 0<x<100% 0<α<360 0<α<360 Relative slat angle downwards Sunblind and slats move up relatively Sunblind moves down to the minimum position or until STOP command is received. Sunblind rotates the slats downwards by a relative angle of α Sunblind move down relatively and rotates the slats relatively Moves the sunblind down by x%. At the new sunblind position, the slat angle is the same as before. Sunblind moves up to the maximum position or until STOP command is received. Sunblind rotates the slats upwards by a relative angle of α Sunblind move up relatively and rotates the slats relatively SET_ DOWN 0-31 & -32 NOT SUPPORTED NOT SUPPORTED NOT SUPPORTED SET_UP 0-31 & -32 NOT SUPPORTED NOT SUPPORTED 0<x<100% INVALID Sunblind moves up relatively Moves the sunblind up by x%. At the new sunblind position, the slat angle is the same as before. NOT SUPPORTED SET_ STOP Don t care Don t care Sunblind stops Stops sunblind immediately SET_STOP 0-31 & -32 SET_ STATE 0<x<100% INVALID Sunblind translation INVALID -360<α<360 Sunblind rotation 0<x<100% -360<α<360 Sunblind translation and rotation Sets the sunblind absolute position as specified in the setting field Sets the slats absolute angle as specified in the setting field Sets the sunblind position to x and the slat angle to α SET_ STATE NOT SUPPORTED NOT SUPPORTED See tables 1 and 2-31 & RCL-Light/Blind/ITR User Guide

143 TABLE 1 : TRANSLATION nvosblndcmd1.setting Field nvosblndcontrol Translation Calculation From 0% to 4.5% 100% From 5% to 14.5% 90% From 15% to 24.5% 80% From 25% to 34.5% 70% From 35% to 44.5% 60% From 45% to 54.5% 50% From 55% to 64.5% 40% From 65% to 74.5% 30% From 75% to 84.5% 20% From 85% to 94.5% 10% Greater or equal to 95% 0% TABLE 2 : ROTATION nvosblndcmd1.rotation Field nvosblndcontrol Rotation Calculation From -360 to (horizontal) From -315 to (45 ) From -270 to (vertical) From -225 to (45 ) From -180 to (horizontal) From -135 to (135 ) From -90 to (vertical) From -45 to (135 ) From 0 to (horizontal) From 45 to (45 ) From 90 to (vertical) From 135 to (45 ) From 180 to (horizontal) From 225 to (135 ) From 270 to (vertical) From 315 to (135 ) From 360 to (horizontal) Sunblinds are considered open at 0% for RCL-Light/Blind series while sunblinds are considered open at 100% for CTR series. Leading to translation value inversion in table 1. nvosblndcontrol.setting field in SET_STATE mode is equal to Translation + Rotation values from TABLE 1 and TABLE 2 Ex: If nvosblndcmd1 is equal to SET_STATE, 36%, 150 then nvosblndcontrol will be equal to SET_STATE, 61%, -31 (See highlighted values in TABLE1 and 2) RCL-Light/Blind/ITR User Guide 141

144 Coupling Control - Example Typical installation 8 lighting fixtures are installed in the room: Requirements L1, L3, L5 and L7 are set on windows side and L2, L4, L6 and L8 on corridor side when managed by the light control loop. Each channel of the room device must control the matching lighting fixture (L1 controlled by user group 1, L2 by user group 2.) when managed by the room device. Configuration o Connect the room device to the Room Controller object 1 o Slave Room Controller objects 2, 3 and 4 to Room Controller 1: Using network variable cpcoupling Using the wizard: Room Controller Coupling mode RoomCtrl1 RoomCtrl2 RoomCtrl3 RoomCtrl Stand-alone With RoomCtrl 1 With RoomCtrl 1 With RoomCtrl RCL-Light/Blind/ITR User Guide

145 o Set the different light command in the different room controllers as shown below: RoomCtrl1 RoomCtrl2 RoomCtrl3 RoomCtrl4 LightCmd1 LightCmd2 LightCmd1 LightCmd2 LightCmd1 LightCmd2 LightCmd1 LightCmd2 Using network variable cplightgrpset Ctrl_grp User_grp Using the wizard: Room Sensor Override group Number Light Control Group Window Side Corridor Side Window Side Corridor Side Window Side Corridor Side Window Side Corridor Side o The controller is now configured as required according to the diagram shown below: Using coupling control requires to ban bindings on slaved Room Controller objects. RCL-Light/Blind/ITR User Guide 143