RXC RXC RXC VISONIK® Integration of DESIGO™ RXC Basic documentation CM2Z8338en_01 12.06.
Contents 1 About this document ..................................................................................... 5 1.1 Overview ....................................................................................................... 5 1.2 Revision history ............................................................................................ 5 1.3 What is this document about?....................................................................... 6 1.4 For whom is this document intended? ...
3.2.23 Disable or limit auxiliary energy supply .......................................................38 3.2.24 Intranet room operation ...............................................................................39 3.2.25 Control of blinds, 2 groups ..........................................................................40 3.2.26 Control of blinds, 4 groups ..........................................................................41 3.2.27 Lighting control, 2 groups ..........................
Introduction 1 About this document 1.1 Overview This opening section describes the content and purpose of this document. It – Introduces the basic topology of the DESIGO RXC system within VISONIK – Defines the target readership of this manual, and the background knowledge required – Shows how the activities described fit into the project handling procedure. Contents of this section 1 About this document ..................................................................................... 5 1.
1.3 This document deals with the integration of the DESIGO RXC room management system into VISONIK. The diagram below shows the basic topology with the associated system levels. 8338Z01en DESIGO RXC in VISONIK What is this document about? DESIGO™INSIGHT VISONIK® DCS BPS-CFE NIDES.RX LON bus Aut o DESIGO™RX A ut o A ut o - Notes on the diagram + - + The system levels and components shown in the diagram are: Name Description DESIGO™ INSIGHT ® VISONIK NIDES.
1.4 Target readership For whom is this document intended? This document is written for staff in the Building Automation division of Siemens Building Technologies, working in the field of building automation and control as: • Sales personnel • System engineers • Commissioning and service engineers This document contains all the information relevant to the above staff in relation to the integration of DESIGO RXC into VISONIK.
1.5 The flow chart below is a simplified illustration of the handling of a project for the integration of DESIGO RXC into a management system – from the specification and tender documentation to engineering and commissioning. 8338Z14D Project handling from start to finish What activities does this document describe? Specifications Room partitioning, control loops, interfaces etc.
1.
Introduction 2 Integration overview 2.1 Overview This section gives an overview of the integration of DESIGO RXC into VISONIK. Key items are: – Integration topology with a brief description of the equipment involved. – RX master functions and NIDES binding templates – Preliminary hardware list for an initial estimate of the number of controllers Contents of this section 2.1 Overview .....................................................................................................10 2.
2.2 Structure Topology for RX integration The diagram below shows the topology for the integration of DESIGO RX into VISONIK. 8338Z03 BLN (SDLC) NIDES.RX Bindings V.24 NVs BPS V16 LON (LonMark) T RX master / CFE application RXC Components involved RXC RXC The main components involved in the integration of RX into VISONIK are: Element Description BLN (SDLC) Building Level Network (SDLC ring) of the VISONIK system BPS V16 VISONIK BPS, type PRV2.
2.3 Mapping as VISONIK data points Mapping the RXC controllers in the RX master As the RX master, the VISONIK BPS maps the DESIGO RXC application to VISONIK data points and parameters as follows: • TEC data points • Link points Functions for HVAC functions (TEC groups and TEC rooms) for third-party blinds, lighting and special functions The mapped data points can be operated like normal VISONIK points.
2.4 The concept of RX master functions RX master functions / NIDES binding templates The actual purpose of integration is to make available the RX master functions .
2.5 Introduction RX master functions with VISONIK templates 1 / 2 VISONIK Templates 1 and 2 are stored in the RXT10 as default templates for integration into the NIDES.RX. The difference between the two templates is as follows: – VISONIK Template 1 contains the main functions for HVAC, blinds and lighting – VISONIK Template 2 incorporates additional HVAC functions These functions are described in detail in the two tables below.
2.6 RS master functions, extended selection Introduction The RX master functions automatically integrated with VISONIK Templates 1 and 2 can be supplemented with a number of other functions if required. These are listed below.
2.7 Room operation via the Intranet Phased out From 2006, the room operation via the intranet is not available any more. Introduction Room operation via the Intranet is designed for office buildings with PC networks installed. In these circumstances, instead of wall-mounted room units, users can operate the room from their office PC via an Internet browser. Room units and functions The diagram below shows the room units in the DESIGO RXC range, and their functions.
2.8 Overview Preliminary hardware list The table below shows a preliminary hardware list. It provides the following information for the various applications, and can therefore be used for a preliminary estimate when preparing a quotation.
3 Integration functions 3.1 Overview Introduction In the first part of this section, all the RX master functions available for the RXC applications are described in detail. Subsections 3.3 to 3.6 deal with the creation of groups for HVAC, lighting and blinds. Contents of this section 3.2 Functions for the DESIGOTM RXC applications...........................................19 3.2.1 Example of a read operation .....................................................................21 3.2.
3.2 Functions for the DESIGOTM RXC applications The RX master functions in the BPS are implemented by mapping VISONIK parameters to controller network variables. As can be seen in subsection 2.2, the VISONIK parameters are first transmitted to the NIDES.RX and only then mapped to the network variables. The following diagram shows the process from the functional viewpoint. VISONIK BPS NIDES.RX RXC TEC parameters RSUS SOPST AOPST nvo nvi RSUZ ERSTA LON TRUNKBUS Link point params.
NV name in NIDES.RX Definition of RS master function 3.2.1 Shows which RXC applications can be used NV name in RXC controller Example of a read operation All RXC applications 3.2.24 Intranet room operation VISONIK BPS DP. Parameters NIDES.RX Function/Range NV name / element Function/Range RXC controller BT User designation NV name @TCRn.AOPST See "Effective room status" ← nviEffectOccup See "Effective room status" ← 1 Effect Occup nvoEffectOccup @TCRy.
3.2.2 Displaying the device status All RXC applications and all third-party devices VISONIK BPS DP.Parameter Function/Range @TCRn.ERSTA Status display for whole room: 0 = All controllers normal, 9 = At least one faulty controller (no communications) @AI x' y.ERSTA @AO x' y.ERSTA Status display, single value: 0 = Controller x normal, 9 = Controller x fault NIDES.
3.2.3 Definition of room operating mode All RXC applications VISONIK BPS DP.Parameter NIDES.RX Function/Range @TCRn.SOPST See table of bindings @TCRn.MOPST 1) RXC controller BT User designation NV name / element Function/Range → nvoUseSchedule See table of bindings → 1 → nvoOccSchedule See table of bindings → 1 NV name NV element Building Use Scheduler nviUseSchedule Current state Occup Scheduler nviOccSchedule Current state @TCRn.
3.2.4 Define controller operating mode All RXC applications VISONIK BPS DP.Parameter NIDES.RX Function/Range NV name / element Function/Range nvoApplicMode Controller application mode (see table of bindings) @TCRn.RLHT @TCRn.RLCO See table of bindings → RXC controller BT User designation → 1 Application Mode NV name NV element nviApplicMode Table of bindings @TCRn.RLHT @TCRn.
3.2.5 Night purge All VAV applications, FPB05 VISONIK BPS DP.Parameter NIDES.RX Function/Range @TCRn.SOPST @TCRn..RRTP See table of bindings @TCRn.
3.2.6 Displaying the actual controller operating mode VISONIK BPS DP.Parameter Function/Range @TCRn.AOPST 2) See table of bindings All RXC applications NIDES.RX NV name / element 2) ← nviEffectOccup RXC controller BT User designation Function/Range ← See table of bindings 1 Effect Occup NV name NV element nvoEffectOccup 2) In the RXC Application Library V2, the NV element EffHvacMode.op_mode is used instead of NV EffectOccup. Table of bindings Effect Occup @TCRn.
3.2.7 Display current room temperature All RXC applications VISONIK BPS DP.Parameter Function/Range Current room temperature Controller x @TCRn.ARTP(x) 3.2.8 NIDES.RX ← NV name / element Function/Range nviSpaceTemp °C BT User designation ← 1 Effect Space Temp Display effective setpoints for heating and cooling VISONIK BPS Function/Range NV name / element Function/Range @TCRn.ASPH Effective heating setpoint nviSetptEffect 2) .occupied_heat °C @TCRn.
3.2.10 Summer / winter compensation All RXC applications VISONIK BPS DP.Parameter NIDES.RX Function/Range @TCGm.DSPC BT User designation NV name / element Function/Range → nvoSetptShift .occupied_cool Occupied cooling setpoint shift → 1 → nvoSetptShift .occupied_heat Occupied heating setpoint shift → 1 See diagram @TCGm.
3.2.11 Basic setpoints All RXC applications VISONIK BPS NIDES.RX RXC controller BT User designation NV name / element Function/Range ↔ ncoSetpoints . occupied_heat Occupied heating setpoint ↔ 2 Reduced heating setpoint ↔ ncoSetpoints . standby_heat Standby heating setpoint ↔ @TCRn.SPEH Economy heating setpoint ↔ ncoSetpoints . unoccupied_heat Unoccupied heating setpoint @TCRn.SPCC Comfort cooling setpoint ↔ ncoSetpoints . occupied_cool @TCRn.
Note Depending on the type of application, it may be that only “Primary Heat” or only “Primary Cool” is incorporated. Caution With changeover applications, the current position of the control valve of the RXC controller is always sent to nvoHeatPrimary. As it is not possible to distinguish between heating and cooling without additional information (integration of the NV “Unit Status”), the current valve position is mapped to @TCRn.OXWA. Changeover aktiv TCRn.COVR.OR Stellung Changeoverventil TCRn.
3.2.13 Display current fan speed All FNC applications VISONIK BPS DP.Parameter @TCRn.OFAN NIDES.RX Function/Range Fan speed ← NV name / element Function/Range nviFanSpeed 0 = Off, 1 = Sp.1, 2 = Sp.2, RXC controller BT User designation ← 2 NV name Fan Speed nvoFanSpeed 3 = Sp.3 3.2.14 Electric heating coil, position of current valve and max. electrical energy VISONIK BPS RAD03, FNC01, VAV03, VAV06, FPB05 NIDES.RX RXC controller BT User designation DP.
Maximale elektr. Energie Stellung Stromventil TCRn.FCHB*) [kW] TCRn.OHHB(x) [kW] 01141en RX master Multpl. TEC.FCHB [kW] TEC.OHHB [%] Absolute Power Cons. [Watt] Primary Heat / Secondary Heat [%] The parameter FCHB must be configured in accordance with the maximum output of the electric reheater. The value must be the same as the one configured in the RT10 tool (see diagram, right).
3.2.16 Display of current air flow rates VAV applications, FPB05 VISONIK BPS NIDES.RX DP.Parameter Function/Range @TCRn.AIRVS2(x) Supply air flow rate (cooling duct) ← nviAirflow @TCRn.AIRVS1(x) Supply air flow rate, heating duct @TCRn.AIRVE(x) Extract air flow volume Note 3.2.
3.2.19 Display current sequence (heating / cooling) VISONIK BPS DP.Parameter NIDES.RX NV name / element Function/Range @TCRn.ASTH Current sequence (see diagram) @TCRn.ASTC Control action: Heating Control action: Cooling TCRn.ASTH TCRn.ASTC All RXC applications ← nviUnitStatus .
3.2.20 Display current heating/cooling energy demand VISONIK BPS DP.Parameter @TCRn.ADMC All RXC applications NIDES.RX NV name / element Function/Range ← See diagram nviTerminalLoad @TCRn.ADMH Actual command for heating energy Actual command for cooling energy TCRn.ADMH TCRn.ADMC RXC controller Function/Range -100..0% = Heating 0..+100% = Cooling ← BT User designation NV name ne Terminal Load nvoTerminalLoad 01143en RX master Absolute value () S1=-100..0 S1=0..
3.2.21 Room temperature averaging All RXC applications VISONIK BPS DP.Parameter Function/Range @TCRn.ARTP(x) Current room temperature, controller x @TCRn.RRTP Room temperature average NIDES.RX RXC controller BT User designation NV name ← ne Local Temp Sensor nvoTempSensor nvoTempSensorPPS °C ← 1 Effect Space Temp nvoSpaceTemp °C → ne Space Temp nviSpaceTemp NV name / element Function/Range ← nviTempSensor °C ← nviSpaceTemp → nvoSpaceTemp @TCRn.
SpaceTemp HvacMS NIDES.RX RXC Master RXC Slave T TempSensor RXC Slave T TempSensor SpaceTemp 3.2.22 Definition of emergency mode (Emergency OFF / Smoke extraction) VISONIK BPS DP.Parameter @AOx’42.EMV @TCRn.SOPST All VAV applications, FPB05 NIDES.RX Function/Range See table of bindings → NV name / element Function/Range nvoEmergOverride See table of bindings RXC controller → BT User designation NV name ne nviEmergOverride Emergency override Table of bindings @AOx’42.EMV @TCRn.
In operating state SOPST=6, Emergency Override is determined by link point @AOx’42. Single-parameter integration of iEmergOvr for the HVAC master in Room n with Controller number x). The value of must always be assigned before setting @TCRn.SOPST to 6. Caution 3.2.23 If the room concerned is subject to a time schedule(@DSTy), this must be deactivated during emergency operation (@DSTy.ACT=0), otherwise parameter @TCRn.SOPST will be overwritten again.
3.2.24 Intranet room operation All RXC applications VISONIK BPS DP.Parameter Function/Range @TCRn.AOPST See "Effective room status" @TCRy.ARTP NIDES.RX RXC controller BT User designation NV name / element Function/Range NV name ← nviEffectOccup See "Effective room status" ← 1 Effect Occup nvoEffectOccup ← nviSpaceTemp Current room temperature ← 1 Effect Space Temp nvoSpaceTemp @AOx’24.
3.2.25 Control of blinds, 2 groups INT01, INT02, INT03, INT04, INT06, INT07, INT15, INT17 VISONIK BPS NIDES.RX RXC controller BT User designation NV name → 1 Blind Override #1 nviSblndOverr_1 0 = Up; 1 = Down1; 2 = Down2 → ne 0=Up; 1=Down1; 2=Down2, 3=Auto → 1 NV name / element Function/Range → nvoSblndOverr_1 0=Up; 1=Down1; 2=Down2, 3=Auto @AOx‘1.PARINT(2) (See diagram) → nvoSblndCmd_1 @AOx’2.EMV → nvoSblndOverr_2 DP.Parameter Function/Range @AOx’1.
3.2.26 Control of blinds, 4 groups INT05 VISONIK BPS DP.Parameter NIDES.RX Function/Range NV name / element RXC controller BT User designation Function/Range NV name NV element @AOx’1.EMV → nvoSblndOverr_1 0=Up; 1=Down1; 2=Down2, 3=Auto → @AOx‘1.PARINT(2) Control of Blinds 1 and 2 (See diagram) @AOx’2.EMV → nvoSblndCmd_1 0 = Up; 1 = Down1; 2 = Down2 → ne Blind Command #1 nviSblndCmd_1 → nvoSblndCmd_2 0 = Up; 1 = Down1; 2 = Down2 → ne Blind Command #2 nviSblndCmd_2 @AOx’3.
3.2.27 Lighting control, 2 groups INT01, INT04, INT05, INT10, INT12, INT15, INT17 VISONIK BPS DP.Parameter NIDES.RX Function/Range RXC controller NV name / element Function/Range BT User designation Control of lighting group 1 @AOx‘5.PARINT(2) (see diagram) → nvoLightOverr_1 0 = OFF; 1 = ON, 255 = Auto → → nvoLightCmd_1 0 = Off, 0.5...100 = On, n% → @AOx’6.EMV → nvoLightOverr_2 0 = OFF; 1 = ON, 255 = Auto → → nvoLightCmd_2 0 = Off, 0.5...100 = On, n% → @AOx’5.
3.2.28 Lighting control, 4 groups INT02, INT03, INT06, INT07, INT11 VISONIK BPS DP.Parameter NIDES.RX NV name / element Function/Range RXC controller BT User designation Function/Range NV name NV element → nvoLightOverr_1 0 = OFF; 1 = ON, 255 = Auto → → nvoLightCmd_1 0 = Off, 0.5...100 = On, n% → ne Light Command #1 nviLightCmd_1 → nvoLightCmd_2 0 = Off, 0.5...
3.2.29 Additional single parameters for HVAC control VISONIK BPS Depends on application NIDES.RX RXC controller BT User designation NV name / element Function/Range → nvoAirflowSetpt l/s → ne Aiflow Setpoint nviAirflowSetpt Occupancy sensor → nvoOccSensor 0 = Occupied, 1 = Unocc. → ne Occup Sensor nviOccSensor @AOx’27.EMV Definition of sequence: heating/cooling → nvoHeatCool 0 = Auto, 1 = Heat, 3 = Cool → ne Heat Cool Mode nviHeatCool @AOx’29.
3.2.30 Other single parameters for lighting control VISONIK BPS DP.Parameter All INT applications NIDES.RX Function/Range NV name / element Value range RXC controller BT User designation NV name @AOx’111.EMV Measured daylight intensity → nvoLightLuxLevel Lux → ne Daylight Lux Level nviLightLuxLevel @AOx112’.EMV Daylight switch-off threshold 1 ↔ ncoLuxThrsldOff_1 Lux ↔ ne Daylight Threshold #1 nciLuxThrsldOff_1 @AOx113’.
VISONIK BPS NIDES.RX RXC controller BT User designation NV name / element Value range ← nviCtrl_D1 . state 0 = OFF; 1 = ON ← ne Controller input D2 ← nviCtrl_D2 . state 0 = OFF; 1 = ON ← @AIx’159.EMV Controller input D3 ← 0 = OFF; 1 = ON ← @AIx’161.EMV Controller input D4 ← nviCtrl_D4 . state 0 = OFF; 1 = ON @AIx’163.EMV Extension module 1, input D1 ← nviExMod_1_D1 . state @AIx’165.EMV Extension module 1, input D2 ← nviExMod_1_D2 . state @AIx’167.
3.3 Introduction Definition of HVAC groups HVAC groups are defined to take account of various HVAC and organizational aspects affecting the building, such as: – The direction in which the building faces (HVAC zones / groups based on HVAC requirements) – The use of a number of rooms at given times (groups based on occupancy pattern) The room as the basic element for RXC integration In the context of the integration of RXC into VISONIK, the basic element for the definition of HVAC groups is the room.
3.4 Defining lighting and blind groups In addition to HVAC functions, the integrated applications of DESIGO RXC include the control of lighting and blinds. This makes it necessary to define groups for these purposes too, whether in response to HVAC conditions or differing patterns of room occupancy. The RXC controller as the basic element Whereas the room is the basic element for defining HVAC groups, in the case of blinds and lighting, the definition of groups is based on the RXC controller.
3.5 Problem Control priority functions for lighting and blind groups Since one RXC controller can be assigned to a number of lighting or blind groups, each with different group values, a method must be found to determine which group is to act on the RXC controller. The diagram below highlights the problem on the basis of the groupings illustrated earlier.
3.6 Introduction Examples for lighting and blind groups This page shows two typical examples of the application of lighting and blind groups.
Introduction 4 Engineering 4.1 Overview This section concerns the engineering required to integrate the DESIGO RXC system into VISONIK BPS. The key areas covered are: – – – – Contents of this section Data flow from the plant to the VISONIK data points Engineering procedure The configuration of groups for HVAC, blinds and lighting Single-parameter integration 4.2 From the application to the TEC data points............................................... 52 4.3 Overall engineering procedure ........
4.2 Purpose of the overview From the application to the TEC data points The diagram below is a simplified illustration of the route taken by data from the I/Os and parameters of the application through to the VISONIK data points in the BPS. Its purpose is – To provide an overall picture of the data flow, from the perspective of the application – To illustrate the interaction between the various elements. This will help clarify the engineering steps described later.
Description of individual elements The individual elements in the diagram on the previous page are as follows (starting at the bottom): Element Description Application The term “application” refers to the software solution for a given HVAC application, e.g. a room fan-coil system. The application maps all inputs, outputs and parameters in the “device”. Device The “device” refers to the type of DESIGO RXC device in the database of the RXT10.1 tool, and is a component of a project.
4.4 Flow chart Overall engineering procedure The flow chart below is a simplified illustration of the complete engineering process for the integration of the DESIGO RXC controllers. Activities and elements related specifically to VISONIK are shown on a shaded background. 01037en Specifications Peripheral devices Type, installation - Location text - NIDES bindings Planning of installation, wiring diagrams Engineering with RXT10.1: Create project, select devices, applications and controllers.
Overview The diagram below shows the workflow for the integration of DESIGO RXC into VISONIK. 90161Aen RXT10 1 RxNibps.col Project data BLN (SDLC) NIDES.RX V.24 BPS LON bus Infolist 2 GroupConfig.
4.6 Purpose of the location text in the RXT10 Entering the location text in the RXT10 When integrating DESIGO RXC into VISONIK, the “Location” input field in the RXT10 is used for additional VISONIK-specific information about the room number, master/slave controller and RXC controller number. This information is referred to as the “location text”.
4.6.1 Contents Content and format of the location text The location text must always include the following information: - Number of the room in which the controller is located - Information as to whether the controller in that room is a master or slave (HVAC) - VISONIK RXC device number (identification of the device in the VISONIK system) Note: The location text does not necessarily correspond to the building-based addresses. These can be entered later with the appropriate text in the TEC data point.
TCR 1 RXC M 37 TCR 2 TCR 3 RXC M RXC M 38 39 TCR 4 RXC S RXC M 41 S 42 40 T South Location text RXC 83 38 Z2 7D The location text for this example is as follows: 8338O03E Note The input format and the value ranges are checked by the RXT10 tool. However, there is no check when the data is entered; checking only takes place when you save the project. Devices which do not have bindings to the NIDES.RX will not be checked, and the associated location text can be defined freely.
4.7 Selecting the NIDES binding template Template selection In the RXT10, select NIDES binding template VISONIK 1 or VISONIK 2. User-defined templates To create user-defined templates, use the Binding Template Editor. The screenshot shown is valid for the direction “Device to NIDES.R”: X”. Clicking the “Switch” button allows you to change direction (network variables from the NIDES.RX to the device).
Overall classification The following engineering steps deal with the mapping of the RXC controllers and their functions to VISONIK data points. This pave gives an overview of the VISONIK data structures used in this process.
4.9 Defining groups The groupings are defined in file GroupConfig.COL by editing TSK112 manually (assuming it exists; if not, it must be created). In this task the “RX coupling” application later creates the VISONIK data structures automatically. The print-out below shows the default TSK112 with details of the format for each of the groups. For editing and saving the GroupCOnfig.COL file, we recommend use of the VISOTool, because in the BPS the comments are removed when the file is saved.
4.9.1 Defining groups in GroupConfig.COL Edit the GroupConfig.COL file as indicated in the table below: Element Entries DATA -9 Enter a line for each group, using the format indicated above the input lines. Each line must start with DATA and end with the terminator “ –9 ”. DATA –9 at the end of the inputs terminates the definition of the groups. HVAC groups HVAC groups: Group numbers 1 .. 200, and max. 20 rooms per group Important: A room must not be assigned to more than one HVAC group.
4.10 System example Example with HVAC, blind and lighting groups The following is an example of a floor plan, incorporating DESIGO RXC controllers for the room management system.
4.10.1 Entries in GroupConfig.COL Edited GroupConfig.COL for the example The print-out below shows the GroupConfig.COL file, after editing for the system example described above. The edited text is shown in bold. Refer to the previous page for notes on the entries. .TSK112 1 -- [1-08-99/V1.
4.10.2 Lighting and blind group priorities The following rules apply to the priorities: – Each group of blinds and each lighting group must be assigned a priority level between 1 and 100, where 1 is the highest. – No priority level may be assigned more than once (this applies to lighting and blinds separately). – The priorities assigned are relevant only if the group concerned is configured in “Remote” mode.
4.11 Integration of single parameters The following diagram applies to both the additional network variables of standard RXC applications and to the network variables of third-party applications. The term “single parameter integration” refers to the mapping of an individual NV element to the Event Main Value (EVM) of a link point (AI or AO) without any special additional function. The diagram below shows the principle of this mapping process. LON Gerät x NIDES.
Restrictions affecting single parameter integration Network variables can be integrated as single parameters, provided that: - the RXT10 tool knows the application concerned the allocation from input (nvi) or output (nvo) on the NIDES.RX side to the link point element address is defined. Caution: This only applies to some of the NVs shown in the NIDES.RX window (target). NVs not documented in Tables 4.10.1 and 4.10.2 are excluded from single parameter integration.
4.11.1 Mapping table for NIDES.RX outputs The NV Name and SNVT_Type columns contain the names of the NIDES.RX outputs in the order in which they appear in the NIDES.RX window of the Binding Template Editor. The switch must be set so that the NIDES.RX window (Target) is to the left of the connecting arrow. Outputs in the NIDES.RX window of the Binding Template Editor cannot be integrated unless they are documented here. In the case of structured NVs, a permanently defined selection of elements is mapped.
NIDES.RX NV Name (Description) SNVT_Type BPS NV Element Link point Integration function nvoAirflowSetpt SNVT_flow ← @AO x ' 19 nvoApplicMode SNVT_hvac_mode ← @AO x ' 26 3.2.4 nvoAuxHeatEnable SNVT_switch ← @AO x ' 30 3.2.
NIDES.
NIDES.RX NV Name (Description) SNVT_Type BPS NV Element Link point Integration function nvoOutdoorTemp SNVT_temp_p ← @AO x ' 44 nvoPpm SNVT_ppm ← @AO x ' 97 nvoPressP_1 SNVT_press_p ← @AO x ' 162 nvoSblndCmd_1 SNVT_setting function ← @AO x ' 114 3.2.25 nvoSblndCmd_2 SNVT_setting function ← @AO x ' 117 3.2.25 nvoSblndCmd_3 SNVT_setting function ← @AO x ' 120 3.2.26 nvoSblndCmd_4 SNVT_setting function ← @AO x ' 123 3.2.
NIDES.
NIDES.
4.11.2 Mapping table for NIDES.RX inputs The NV Name and SNVT_Type columns contain the names of the NIDES.RX inputs in the order in which they appear in the NIDES.RX window of the Binding Template Editor. The switch must be set so that the NIDES.RX window (Target) is to the right of the connecting arrow. Inputs in the NIDES.RX window of the Binding Template Editor cannot be integrated unless they are documented here. In the case of structured NVs, a permanently defined selection of elements is mapped.
NIDES.RX NV Name (Description) SNVT_Type BPS NV Element Link point Integration function nviCoolPrimary SNVT_lev_percent → @AI x '65 3.2.12 nviCoolSecondary SNVT_lev_percent → @AI x '12 3.2.
NIDES.RX BPS SNVT_Type NV Name (Description) NV Element Link point Integration function nviFlowF1 SNVT_flow_f → @AI x '146 AppLibV2 nviFlowP1 SNVT_flow_p → @AI x '147 AppLibV2 nviFlowTemp SNVT_tem_p → @AI x '82 nviFlowSetpoint SNVT_lev_percent → @AI x '72 nviFreqF1 SNVT_freq_f → @AI x '148 AppLibV2 nviHeatAirDmpPos SNVT_lev_percent → @AI x '86 3.2.17 nviHeatCool SNVT_hvac_mode → @AI x '52 nviHeatPrimary SNVT_lev_percent → @AI x '63 3.2.12 3.2.
NIDES.RX NV Name (Description) SNVT_Type BPS NV Element Link point nviLoadAbs SNVT_power → @AI x '61 nviLux SNVT_lux → @AI x '78 nviOADamper SNVT_lev_percent → @AI x '66 nviOccSensor SNVT_occupancy → @AI x '81 nviPowerF1 SNVT_power_f → @AI x '149 nviPpm SNVT_ppm → @AI x '76 nviPumpStatus SNVT_switch Value → @AI x '83 nviSashPosition SNVT_switch State → @AI x '123 Value → @AI x '124 Integration function 3.2.14 3.2.
NIDES.RX NV Name (Description) nviSwitch24 nviSwitch25 SNVT_Type SNVT_switch SNVT_switch BPS NV Element Link point State → @AI x '22 Value → @AI x '21 State → @AI x '24 Value → @AI x '23 Integration function nviTempP10 SNVT_temp_p → @AI x '17 nviTempSensor SNVT_temp_p → @AI x '96 3.2.21 nviTempSensorPPS SNVT_temp_p → @AI x '16 3.2.21 nviTerminalLoad SNVT_lev_percent → @AI x '62 3.2.20 nviUnitStatus SNVT_hvac_status in_alarm → @AI x '49 mode → @AI x '43 3.2.
Introduction 5 Commissioning 5.1 Overview This section describes the commissioning procedure for the integration of DESIGO RXC into VISONIK. The key points are as follows: • Commissioning procedure • Indication and operation • Procedure for updates and modifications Contents of this section 5.2 Commissioning procedure .......................................................................... 80 5.3 Commissioning procedure (workflow)......................................................... 81 5.
5.2 Flow chart Commissioning procedure The flow chart below is a simplified illustration of the commissioning procedure for the integration of the DESIGO RXC controllers. The activities and elements specifically related to VISONIK are shown on a shaded background. Engineering LON commissioning with RXT10.1 NIDES.
5.3 Introduction Commissioning procedure (workflow) This topic deals with commissioning on the VISONIK side. Essentially it consists of the following: • Commissioning the NIDES.RX • Commissioning the RX master • VISONIK-specific engineering Commissioning the NIDES.RX To commission the NIDEX.RX, proceed as follows: Step Activity 1 Commission the NIDES hardware as described in data sheet CA2N3299E. 2 Connect the NIDES.RX to the RS master Notes on connection: – The NIDES.RX and the VISONIK.
5.4 NIDES indicators Status indication in the commissioning phase This illustration shows a section of the NIDES.RX display: POWER STATUS BATTERY 8338Z33 SERVICE The table below gives the meaning of the various states of the POWER (green) and STATUS (red) LEDs when commissioning the RX master: Circumstances LED Description Normal operation POWER LED ON (continuous) Power supply OK Infolist download into NIDES (during normal operation) Sequence: 1. POWER LED flashing 2.
5.5 General options for operation Operating the data points The integrated data points can be operated with the VISOTOOL Editor, for example: RMR report output Room management reports can be obtained with the command RMR, for example: • To read the effective heating setpoint: • To specify a new Comfort heating setpoint: (basic setpoint setting for Comfort/Heating) RMR RMR @ TCG n RMR @ TCR n Example of an RMR @TCR1.ASPH @TCR1.SPCH:=20.
5.6 Structure of the TEC data points Introduction For the purposes of integration into VISONIK, the RXC controllers are mapped to virtual TEC rooms as internal data points. Access to individual controllers takes place indirectly, via the room, as is the usual case for TEC controllers.
5.7 Example Operation of the HVAC groups The diagram below again shows the example of the "Definition of HVAC groups" T RXC RXC Production RXC RXC RXC TCR 5 North 01041E RXC Warehouse TCR 6 TCG 1 Offices TCR 1 RXC TCR 2 RXC TCR 3 RXC TCG 2 Allocating the rooms to groups TCR 4 RXC RXC RXC T South The rooms are allocated to the groups in the GroupConfig.COL file. (Refer to the section on defining groups in the "Engineering" section).
5.8 Operating the blind and lighting groups Introduction The RX master makes the group connections for blinds and lighting zones in accordance with the entries in the GroupConfig.col file (TSK 112). For more information refer to "Group definition" in the "Engineering" section. Example The blinds of controllers 1M55 and 2M56 in Rooms 1 and 2 are to be assigned to a blind group, and the lighting zones of the same controllers to a lighting group (Priority level 3 for both groups).
Parameters R/W @AO g.EMV W (Specification of parameter EMV optional) Description Command when g=1 (blinds): Up (0) / Down(1) / Down(2) / Auto(3) @AO g.PARINT(1) R Command when g=101 (lighting zones): Off(0) Dimming (1…100%) Auto(255) 1) Last command issued 2) @AO g.PARINT(2) R/W Operating mode: Local (0) / Remote(1) @AO g.PARINT(3) R @AO g.FBV - Priority (1..
6 Index Intranet room operation ............................................ 16 A Address ranges, reserved .........................................60 Application, definition ................................................53 C Commissioning NIDES.RX ............................................................81 RX master ............................................................81 States...................................................................82 D Data flow, elements and definitions..........
/90 Building Technologies Building Automation Integration of DESIGO™ RXC Index CM2Z8338en_01 12.06.
Siemens Switzerland Ltd. Building Technologies Group International Headquarters Building Automation Gubelstrasse 22 CH-6301 Zug Tel. +41 41-724 24 24 Fax +41 41-724 35 22 www.sbt.siemens.com © 2006 Siemens Switzerland Ltd. Subject to change 90/90 Building Technologies Building Automation Integration of DESIGO™ RXC CM2Z8338en_01 12.06.
