To integrate an LonWorks adapter using non LNS-based integration software, Itho will supply an interfacefile (XIF-file).

Size: px

Start display at page:

Download "To integrate an LonWorks adapter using non LNS-based integration software, Itho will supply an interfacefile (XIF-file)."

Lauren Richards
5 years ago
Views:

1 Startup Guide LonWorks Adaptor Table of content Preface... 2 Conditions... 2 Installing the Software... 2 Installing AmVent for LNS Software... 2 Using non LNS-Based LON Software... 2 Base Setup with Itho DCW using LonMaker... 2 nvischeduler... 3 nvisetptairflow... 4 nvisetpttemp... 4 nvibypassopm... 5 Disabling Automatic Reset to Default Operating Mode... 6 Setting Max Fan Voltage... 7 Base Setup with Itho DCW in a non LNS tool... 8 nvischeduler... 8 nvisetptairflow... 9 nvisetpttemp... 9 nvibypassopm... 9 Disabling Automatic Reset to Default Operation Mode Setting Max Fan Voltage AmVent User Defined Network Variable- and Configuration Parameter-Types

2 Preface This guide should be regarded a supplement to the document, Itho Lon module for DCW, which is the complete documentation for the LonWorks adapter interface. Conditions By supplying an Itho ventilation unit with a LonWorks adapter instead of the display controller, all control functionalities are transferred from display controller to the LonWorks adapter. Different from a traditional LonWorks Gateway, which typically transfers signals between a dedicated controller and a LonWorks control network, the LonWorks adapter is a LON based control of the ventilation unit. It is recommendable to have the LonWorks integration carried out by a person with the necessary knowledge of LON technology. A LNS -based tool is preferable, but not strictly necessary. Installing the Software As the LonMark interface for the LonWorks adapter contains user defined network variable types (UNVTs), and user defined configuration variable types (UCPTs), using LNS based integration software (e.g. LonMaker ) is recommended where producer specific type files can be used. To integrate an LonWorks adapter, using LNS based integration software (e.g. LonMaker ), Itho will supply type- and interface-files. The files are given as a Windows -setup which must run on the PC from where the integration is made. To integrate an LonWorks adapter using non LNS-based integration software, Itho will supply an interfacefile (XIF-file). Installing AmVent for LNS Software Open AmVent_install.zip and run AmVent_install.exe on the Windows PC where the LNS based integration software has been installed. Interface- and type-files are automatically stored in the correct folders in the LonWorks folder. The LonMark resource file library is automatically updated. Subsequently the LonMaker version 3.2 or higher will show the UNVTs and the UCPTs correctly in the LonMaker browser. For older LonMaker versions it might be necessary to use AmVent Visio shape, when the function block for the LonWorks Adapter is added to the LonMaker drawing. This way the UNVTs and the UCPTs will show correctly in the LonMaker browser. Visio stencil with AmVent Fb is accessible in the folder C:\LonWorks\LonMaker\Visio\Airmaster. Using non LNS-Based LON Software Use AmVent.XIF according to the guide of the LON software in question. To read user defined LonMark types see type definition at the end of this document. Base Setup with Itho DCW using LonMaker Below is shown how to establish a minimum network setup for LON - control of an Itho ventilation unit using the integration tool LonMaker. 2

3 This serves as an example. For alternatives please read LON systeemhandleiding. To control an Itho DCW the following must be established at a sub central or a main central on the following outgoing network variables: To control operating mode establish NVO type SNVT_tod_event To control airflow set point establish NVO type SNVT_lev_percent To control temperature set point establish NVO type SNVT_temp_p To control the bypass damper establish NVO type SNVT_switch Connections are made in LonMaker as shown below: Drawing 1 Handling the variables: nvischeduler If wanted this variable can be changed in type, but for the sake of simplicity we will keep it in its original type SNVT_tod_event. The LonMark type SNVT_tod_event is an array of variables and to be formatted like: typedef struct { occup_t current_state; occup_t next_state; unsigned long time_to_next_state; } SNVT_tod_event where the type occup_t can assume the values: -1 OC_NUL 0 OC_OCCUPIED 1 OC_UNOCCUPIED 2 OC_BYPASS 3 OC_STANDBY When controlling the Itho DCW with the variable time_to_next_state is set to 0, and both current_state as well as next_state for one of the following 4 commands: 0 (OC_OCCUPIED) 1 (OC_UNOCCUPIED) 2 (OC_BYPASS) 3 (OC_STANDBY) 3

The Itho DCW must be told how to react to the above mentioned commands, which

by sending value 0(OC_OCCUPIED), and to OFF by sending the value

4 The Itho DCW must be told how to react to the above mentioned commands, which is done in the configuration table: SCPTvalueDefinition in the variable nviopmode. When the value 0 (OC_OCCUPIED) is sent, the Itho DCW will react as set in table index (0). When the value 1 (OC_UNOCCUPIED) is sent, the Itho DCW will react as set in table index (1), etc. In the LonMaker Browser the SCPTvalueDefinition table is set as shown in drawing 2. Drawing 2 In the example you can see how to control the Itho DCW to Normal ON by sending value 0(OC_OCCUPIED), and to OFF by sending the value 1(OC_UNOCCUPIED) nvisetptairflow This variable sets the wanted airflow of an Itho DCW in normal (occupied) mode. The variable type is SNVT_lev_percent and is shown in percentage (0-100%). nvisetpttemp This variable sets the desired air inlet temperature of an Itho DCW in normal (occupied) mode. The variable type is SNVT_temp_p and shows in degrees Celsius (8,00-30,00 C). 4

nvibypassopm If the Itho DCW unit supports Bypass (indicated by the value BOOL_TRUE

$typedef struct { unsigned value; signed state; } SNVT_switch; where the type value$ can assume the values: -1 OC_NUL 0 OFF 1 ON To activate bypass send: Value=100,0

can assume the values: -1 OC_NUL 0 OFF 1 ON To activate bypass send: Value=100,0

5 nvibypassopm If the Itho DCW unit supports Bypass (indicated by the value BOOL_TRUE in UCPTsysConfigStatus:bypassInstalled (see drawing 3)), this functionality can be controlled by nvibypassopm. Drawing 3 The variable type of nvibypassopm is SNVT_switch and is formatted like: typedef struct { unsigned value; signed state; } SNVT_switch; where the type value is a percentage of 0,5% (0,0-100,0%), and the type state is a numeric value which can assume the values: -1 OC_NUL 0 OFF 1 ON To activate bypass send: Value=100,0 State=1 Not to activate bypass send: Value=0,0 State=0 - to the network variable nvibypassopm. We recommend that Bypass always be activated. 5

Disabling Automatic Reset to Default Operating Mode All NV inputs in

automatically falls back to default parameters if the NVI is not

So if a network variable is not updated within the given interval,

In order to disable this functionality, SCPTmaxRecvTime must be

6 Disabling Automatic Reset to Default Operating Mode All NV inputs in connection with the Ventilation Unit functionality block automatically falls back to default parameters if the NVI is not updated within a configured maxreceivetime. So if a network variable is not updated within the given interval, the control will act from a default parameter. In order to disable this functionality, SCPTmaxRecvTime must be configured for every NVinput to a 0 value, which disables the functionality. This is done in the LonMaker -browser: Set the configuration value SCPTmaxRcvTime for each of the network variables: nvibypassopm nviopmode nvischeduler nvisetptairflow nvisetpttemp - - to value 0,0. 6

7 Setting Max Fan Voltage The following values are unit specific and must be changed to exactly suit the unit in question: - Max reference signal to the inlet fan UCPTmaxInletFanV (default 50%). - Max reference signal to the outlet fan UCPTmaxOutletFanV (default 65%). It shows as a percentage of 10V, i.e. 73% equals 7,3V. The values to be inserted are given by the dealer. The settings are made in the LonMaker Browser: 7

8 Base Setup with Itho DCW in a non LNS tool The text below shows how to establish a minimum network setup for a LON - control for an Itho DCW ventilation unit. This serves as an example. For alternatives, please read the LON systeemhandleiding. To control an Itho DCW the following must be established at a sub central or a main central on the following outgoing network variables: To control operating mode establish an NVO type SNVT_tod_event To control airflow set point establish an NVO type SNVT_lev_percent To control temperature set point establish an NVO type SNVT_temp_p To control bypass damper establish an NVO type SNVT_switch The network variables are tied to the Itho DCW Airmaster AmVent node, or led (Network variable updates) from the BMS system to the Itho DCW Airmaster AmVent node. Handling the variables: nvischeduler This variabel is from the type SNVT_tod_event. The LonMark type SNVT_tod_event is formatted the following way: typedef struct { occup_t current_state; occup_t next_state; unsigned long time_to_next_state; } SNVT_tod_event where the type occup_t can assume the values: -1 OC_NUL 0 OC_OCCUPIED 1 OC_UNOCCUPIED 2 OC_BYPASS 3 OC_STANDBY When controlling the Itho DCW with the variable, time_to_next_state is set for 0, and both current_state as well as next_state for one of the following 4 commands: 0 (OC_OCCUPIED) 1 (OC_UNOCCUPIED) 2 (OC_BYPASS) 3 (OC_STANDBY) Itho DCW must be told how to react to abovementioned commands, which is done in the table for value of configuration: SCPTvalueDefinition in the variable nviopmode. When the value 0 (OC_OCCUPIED) is sent, the Itho DCW will react as set in table index (0). When the value 1 (OC_UNOCCUPIED) is sent, the Itho DCW will react as set in table (1), etc. The values in the configuration variable SCPTvalueDefinition are set to the following values: {0x00, 0x03, 0x03, 0x03, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF}. In this particular example you can thereby control Itho DCW to Normal ON by sending value 0(OC_OCCUPIED), and to OFF by sending the value 1(OC_UNOCCUPIED). 8

9 nvisetptairflow This variable sets the wanted airflow of an Itho DCW in normal (occupied) mode. The variable type is SNVT_lev_percent and is shown in percentage (0-100%). nvisetpttemp This variable sets the wanted air inlet temperature of an Itho DCW in normal (occupied) mode. The variable type is SNVT_temp_p and shows in degrees Celsius (8,00-30,00 C). nvibypassopm If the Itho DCW unit supports Bypass (indicated by the value 1 in UCPTsysConfigStatus: field2 (x,x,x,x,x,x,x)), this functionality can be controlled by nvibypassopm. The variable type of nvibypassopm is SNVT_switch and is formatted the following way: typedef struct { unsigned value; signed state; } SNVT_switch; where the type value is a percentage value of 0,5% (0,0-100,0%), and the type state is a numeric value which can assume the values: -1 OC_NUL 0 OFF 1 ON To activate bypass send: Value=100,0 State=1 To deactivate bypass send: Value=0,0 State=0 - to the network variable nvibypassopm. It is recommended that the Bypass always is activated. 9

10 Disabling Automatic Reset to Default Operation Mode. All NV inputs in connection with the VentilationUnit functionality block automatically falls back to default parameters if the NVI is not updated within a configured maxreceivetime. So if a network variable is not updated within the given interval, the control will act from a default parameter. In order to disable this functionality, SCPTmaxRecvTime must be configured for every NVinput to a 0 value, which disables the functionality. Set the configuration value SCPTmaxRcvTime for each of the network variables: nvibypassopm nviopmode nvischeduler nvisetptairflow nvisetpttemp - - to value 0,0. Setting Max Fan Voltage The following values are unit specific and must be changed to exactly suit the unit in question: - Max reference signal to the inlet fan UCPTmaxInletFanV (default 50%). - Max reference signal to the outlet fan UCPTmaxOutletFanV (default 65%). It shows as a percentage of 10V, i.e. 73% equals 7,3V. The values to be inserted are given by the dealer. 10

11 AmVent User Defined Network Variable- and Configuration Parameter-Types --- UNVT_op_mode enum vent_opmode_t; typedef enum vent_opmode_t { /* 0 */ OM_NORMAL_OCC = 0, /* 1 */ OM_NORMAL_UNOCC = 1, /* 2 */ OM_NIGHT_COOLING = 2, /* 3 */ OM_OFF = 3, /* 4 */ OM_MAN = 4, /* 5 */ OM_OCC_SENS = 5, /* 6 */ OM_CO2 = 6, /* 7 */ OM_TEMP_OCC = 7, /* 8 */ OM_TEMP_UNOCC = 8, /* 9 */ OM_HUMIDITY = 9, /* 10 */ OM_COMB_OCC_SENS = 10, /* 11 */ OM_COMB_OCC = 11, /* 12 */ OM_COMB_UNOCC = 12, /* 127 */ OM_FALL_BACK = 127, /* -1 */ OM_NUL = -1 } vent_opmode_t; --- UNVT_fan_speed Typedef struct { }UNVT_fan_speed; SNVT_switch fan[2]; --- UCPTairflowRelUNOCC SNVT_lev_percent; --- UCPTnightCoolAirflow SNVT_lev_percent; --- UCPTtempAdjustUNOCC SNVT_temp_diff_p; --- UCPTnightCoolTemp SNVT_temp_p; --- UCPTbypassEnTdiff SNVT_temp_diff_p; --- UCPTtempTrigOCC SNVT_temp_p; --- UCPTtempTrigUNOCC SNVT_temp_p; --- UCPTrhHysteresis SNVT_lev_percent; --- UCPTsysConfigStatus Typedef struct { Boolean_t statusvalid; Boolean_t bypassinstalled; Unsigned short mainctrlmajorver; Unsigned short mainctrlminorver; Unsigned short ficmajorver; Unsigned short ficminorver; Unsigned short fipver; } UCPT sysconfigstatus; --- UCPTmaxInletFanV SNVT_lev_percent; --- UCPTmaxIOutletFanV SNVT_lev_percent; --- UCPTmaxCO2 SNVT_ppm; 11

Itho Lon module for DCW

Itho Lon module for DCW Functional Profile: Ventilation Unit UFPTventilationUnit Ventilation Unit: 20100 Version 1.0 August 2008 Compliant with LonMark Application- Layer Interoperability Guidelines Ver.