Functional description "BIU-2ILT"

Transcription

1 Cécile PAULME AEG Functional description "BIU-2ILT"

2 TABLE OF CONTENTS 1. INTRODUCTION 3 2. ELECTRONIC PRODUCT FORM Product description Physical installation Technical specifications wiring Logic representation Binding FUNCTIONS Introduction Assignment of motors Motor information Individual manual local control One or more standard Dry contact or open collector switches Setting and control of 3 additional intermediate positions Priority level Controls from the network Wind sensor interface Sun Sensor Interface Group controls interface Network management tools Node object management Motor(s) status Different configurations DOCUMENTATION REFERENCE 22 Table of How to use Table 1: How to use Management motor...12 Table 2: How to use Priority level...14 Table 3: How to use Wind function...15 Table 4: How to use Sun function...16 Table 5: how to use group control function...16 Table 6 : How to use node object management...18 Table 7 : How to use nvostatus...19 Table 8 : How to use Motor Status...20 Table of figure Figure 1 : wiring...7 Figure 2 : Node description...9 Figure 3 : Binding /22

3 1. Introduction This functional description contains : ELECTRONIC PRODUCT FORM : information concerning the physical installation the software installation the BINDING : different connections with the others products FUNCTIONS : contains the functional description, the functioning of each variables, each configuration properties and the interactions. 3/22

4 2. ELECTRONIC PRODUCT FORM 2.1 Product description This product ( BIU-2ILT) is an interface between 2ILT motor and the LonWorks network (free topology, 78 kbs). The sector power supply is 230 VAC. This product needs a router power supply. The BIU-2ILT can be controlled via : - local control : controls from local hardwired switches for each motor. -networks controls :Group Control, Sun Sensor Interface, Wind interface or any device using in an appropriate way the input variables of the BIU-2ILT.( figure 2 : functional object representation ) The interoperability functional depends to the using variables and each function is configured with a level priority which determinate the action type will carry out. 4/22

5 R R 1 3 Test LPT-10 EBBT Made in France Set-up ID R R NDUL Test Made in France Set-up ID Test mode LPT-10 EBBT R AEG 2.2 Physical installation BIU-2ILT BIU-2ILT M1 M1 M2 M2 PC SEGMENT 1 ROUTER POWER SUPPLY BIU-2ILT BIU-2ILT M1 M1 M2 M2 SEGMENT 2 REPEATER POWER SUPPLY GROUP CONTROL WIND SENSOR SUN SENSOR LUND Test mode AutoC LED service PIN Push button service PIN LED service PIN Push button service PIN DOUBLE PUSH BUTTON BUS LONWORKS : 2 twisted pair SEGMENT 3 ROUTER POWER SUPPLY The product BIU-2ILT must be connected to the others products via the Bus LonWorks. They communicate together, and with the PC. 5/22

6 2.3 Technical specifications box Material ABS Color KJB (grey,supplier) Size 135x120x47 mm System of protection IP 20 Power Supply from the network Lon network free topology 78kbit/s T range working +5 C to +45 C storing -20 C to +70 C Rate of relative humidity 90% maxi. at 25 C Connectors network plug-in screw type connector with 2 terminals, 7.62mm spacing, for 2x2.5mm² cables motor 2 female RJ9 sockets manual controls - a female RJ11 socket -in parallel with a 3 terminal screw type connector, 5.08 mm spacing, for 2x1mm² cables 6/22

7 R AEG 2.4 wiring SOMFY concept on LonWorks ACTUATOR INTERFACE FOR 2ILT MOTORS EBBT LPT-10 transceiver m Network current : 20 ma DEVICE ID : LED service PIN Push button service PIN B1 B2 Local control ILT motor 2 LPT-10 LonWorks network { B1 B2 n B1 B4 B5 B6 B2 n B1 B4 B5 B6 Specific switch ILT1 ILT2 ILT Motor 1 ILT Motor 2 M M N L N L B2 Local control ILT motor 1 MAIN Line Neutral Earth Figure 1 : wiring 7/22

8 2.5 Logic representation This product (BIU-2ILT) can control different functionality : Individual manual local control, controls from the network (sensors interfaces or group control interfaces), the priority management, and the network management.a standard representation of this product view from the network is a functional profile. That describe the product in 4 functional objects : nvirequest NODE OBJECT ID=0 SNVT_obj_request nvisblndrequest SNVT_char_ascii nvisblndinforeq SNVT_Char_ascii nviinstalldel SNVT_lev_disc nvitestmode SNVT_sy_test_mode nviscncfgpushbttn SNVT_scene_cfg SNVT_config_src SNVT_elapsed_tm SNVT_time_sec SNVT_lev_disc nvostatus SNVT_obj_status nvosblndstatus1 SNVT_SnblndState nvosblndstatus2 SNVT_SnblndState nvosblndinfo SNVT_str_int nciconfigsource ncistsmaxsendt ncisblndmaxsendt;ncisnwdmaxrcvt ncidsloccontr;ncidslocintpstn nviswitch0 SWITCH OBECT ID=1 nviswitch1 nviswitch2 nviswitch3 nviswitch4 SNVT_char_ascii SNVT_time_sec SNVT_char_ascii SNVT_time_sec SNVT_state nciswprio0,nciswprio1,nciswprio2,nciswprio3,nciswprio4 nciswmaxrcvt0...nciswmaxrcvt4 ncicontout0,ncicontout1,ncicontout2,ncicontout3,ncicontout4 nciswapptdly0,nciswapptdly1,nciswapptdly2,nciswapptdly3,nciswapptdly4 nciswrlsatmtc 8/22

9 nviwind SNVT_speed WIND OBJECT ID=2 SNVT_speed SNVT_char_ascii SNVT_time_sec SNVT_time_sec SNVT_lev_disc SNVT_lev_disc nciwdthrsh nciwdprio nciwdapptdly nciwddistdly nciwdappact nciwddisact nciwdapppriodly nciwddispriodly nvisun SNVT_lux SUN OBJECT ID=3 SNVT_lux SNVT_char_ascii SNVT_time_sec SNVT_time_sec SNVT_lev_disc SNVT_lev_disc ncisnthrsh ncisnprio ncisnapptdly ncisndistdly ncisnappact ncisndisact ncisnapppriodly ncisndispriodly Figure 2 : Node description 9/22

10 2.6 Binding The functional relation between Group control, Sensor interfaces,..., is defined by the binding via the network input not used in the product. nvoswitch nviswitch0 BIU-2ILT OR nviswitch1 Group Control Interface OR nviswitch2 OR nviswitch3 PUSH BUTTON OR nviswitch4 nvowind SNVT_speed nviwind SNVT_speed nvowdthrsh SNVT_speed nciwdthrsh SNVT_speed Wind sensor Interface WIND SENSOR nvosun SNVT_lux nvisun SNVT_lux nvosnthrsh SNVT_lux ncisnthrsh SNVT_lux Sun sensor Interface nvisblndrequest SNVT_char_ascii nvosblndstatus1 SNVT_SblndState SUN SENSOR nvisblndinforeq SNVT_char_ascii nvosblndstatus2 SNVT_SblndState nvosblndinfo SNVT_str_int Figure 3 : Binding 10/22

11 3. FUNCTIONS 3.1 Introduction Many different functions are possible with this product. It depends of the Binding and of the parameters of configuration. Parameters can be configured : Parameters of the Switch control to define which motor(s) will be controlled by which switch Priority level to define which action will be carry out Individual manual control to enable or disable the functionality and to configure them controls from the network ( Sensors, Group controls..) to define the value of the different configuration variable The network management tools can be controlled. NOTA :each network variable is defined in the functional profile Version /22

12 3.2 Assignment of motors Which Switch controls input controls which motor(s), this function can be configured with a table assignment. Motor(s) controls are linked with a configuration variable : SNVT_char_ascii nciswcontout0 ; SNVT_char_ascii nciswcontout1 ; SNVT_char_ascii nciswcontout2 ; SNVT_char_ascii nciswcontout3 ; SNVT_char_ascii nciswcontout4 ; How to use The group control 0 controls motor A The group control 3 controls motors A, B The group control 1 controls motor A The group control 4 controls motor A motor B motor A Value nciswcontout0 x 1 nciswcontout3 x x 3 nciswcontout1 x 1 nciswcontout4 x Motor information Table 1: How to use Management motor For each motor, a request information on the motor 1 or 2 can be asked and the information is reported. The information contains : torque, speed, week-year of production. Motor information are linked with the variables : SNVT_char_ascii nvisblndinforeq ; SNVT_str_int nvosblndinfo ; 3.4 Individual manual local control For each motor, the interface offers inputs for 5 buttons. Different functions can be achieved depending on the type of control device connected to the interface : One or more standard Dry contact or open collector switches -This applies for switches with 2 buttons ( see Figure 1) B1 and B2provides : -up on B1 ; -down on B2 ; -by simultaneous action on B1 and B2 (=B3) 12/22

13 -if motor is turning : stop -if motor is not turning and the action released under 4 then motor goes to intermediate position -if motor is not turning and the action released over 4 then current position is memorized as the new intermediate position -There is no initial preset of this intermediate position ; if none has been set, then no movement is achieved when the action is released under 4.The intermediate position can be set through the network, and its adjustment inhibited through the network Setting and control of 3 additional intermediate positions use of B4, B5 and B6. This applies for switches with 6 buttons (specific switches ). B4,B5,B6 enable to control of 3 intermediate positions. The default configuration sets them at 75%, 50%, and 25% between up and down limits. An action on one of these 3 buttons released over 4 sets the current position as the new intermediate position controlled by this button. Then can also be set to other values through the network. Individual manual controls are linked with the variables : SNVT_lev_disc ncidslocintpstn ; 3.5 Priority level Any control, local or from the network, is given by the following priority level : -no priority ; -low priority ; -medium priority ; -high priority When a command with a priority level n disappears, a command with a priority level n-1 is carried out. A local manual control or a group control kills a control with the priority level 0 and the «permanent» status. Group controls are linked with the variables SNVT_char_ascii nciswprio0 SNVT_char_ascii nciswprio1 SNVT_char_ascii nciswprio2 SNVT_char_ascii nciswprio3 SNVT_char_ascii nciswprio4 Sun is linked with the variable SNVT_char_ascii ncisnprio Wind is linked with the variable SNVT_char_ascii nciwdprio 13/22

14 How to use : the Group control 2 is controlled with low priority the Group control 4 is controlled with high priority the wind is controlled with medium priority the sun is controlled with no-priority no low medium high value nciswprio2 X 200 nciswprio4 X 100 nciwnprio X 150 ncisnprio X Controls from the network Table 2: How to use Priority level 3 types of controls from the network can be controlled : -Wind sensor interface -Sun sensor interface -Group control interface Wind sensor interface The product has one wind inputs which receive a speed value (m /s) mesuared by a wind sensor. Each input can be configured,with the PC, by the following functioning parameters : -threshold : the measured value is compared with this value -appearing time delay : time between exceeding the threshold and the action -position to reach after the appearing time delay ; release or upholding the priority after the action ( one-shot or permanent ) -disappearing time delay : time between becoming lower than the threshold and the action -position to reach after the disappearing time delay ; release or upholding the priority after the action ( one-shot or permanent ) These parameters are linked with the configuration variable : SNVT_speed nciwdthrsh SNVT_time_sec nciwdapptdly nciwdappact SNVT_lev_disc nciwdapppriodly SNVT_time_sec nciwddistdly nciwddisact SNVT_lev_disc nciwddispriodly How to use : When the speed value becomes higher than 6.9m/s, the motor will go up immediatly, and this action is released. 14/22

15 When the speed value becomes lower than 6.9m/s, the motor will go down with 720 seconds for delay time before the action, and this action is maintained. nciwdthrsh = 6.9 nciwdapptdly = 0 nciwdappact = 3,FF,7FFF nciwdapppriodly = ST_OFF nciwddistdly = 720 nciwddisact = 2,FF,7FFF nciwddispriodly = ST_ON Table 3: How to use Wind function Sun Sensor Interface The product has one sun inputs which receive a brightness value (lux) mesuared by a sun sensor. Each input can be configured,with the PC, by the following functioning parameters : -threshold : the measured value is compared with this value -appearing time delay : time between exceeding the threshold and the action -position to reach after the appearing time delay ; release or upholding the priority after the action ( one-shot or permanent ) -disappearing time delay : time between becoming lower than the threshold and the action -position to reach after the disappearing time delay ; release or upholding the priority after the action ( one-shot or permanent ) These parameters are linked with the configuration variable : SNVT_lux ncisnthrsh SNVT_time_sec ncisnapptdly ncisnappact SNVT_lev_disc ncisnapppriodly SNVT_time_sec ncisndistdly ncisndisact SNVT_lev_disc ncisndispriodly How to use : When the brightness value becomes higher than 24 klux, the motor will godown immediatly, and this action is maintained. When the brigthness value becomes lower than24 klux, the motor will go up with 180seconds for delay time before the action, and this action is released.. ncisnthrsh = ncisnapptdly = 0 ncisnappact = 2,FF,7FFF ncisnapppriodly = ST_ON 15/22

16 ncisndistdly = 180 ncisndisact = 3,FF,7FFF ncisndispriodly = ST_OFF Table 4: How to use Sun function Group controls interface The product has 5 inputs Network controls which receives a setting information from switches. Each of them, with the PC can be configured by the following functioning parameters : -max receive time : the maximum period of time that expires before the object automatically doesn t take into account the present value of the control setting if a new value is not received. WARNING : a good functioning depends to the value of SblndMaxSendTime. -appearing time delay : time delay between network control reception and control execution -release : when the Network control disappears, any other permanent sensor control with noprio is carried out if release is ticked These parameters are linked with the configuration variables : SNVT_time_sec nciswmaxrcvt ; SNVT_time_sec nciswapptdly0 ; SNVT_time_sec nciswapptdly1 ; SNVT_time_sec nciswapptdly2 ; SNVT_time_sec nciswapptdly3 ; SNVT_time_sec nciswapptdly4 ; SNVT_state nciswrlsatmtc ; How to use The network control is controlled with no period of time for receiving a new value and with 180 seconds before the moving of the motor.and switch 2 is releasing in automatic. ncimaxrcvt=0 nciswapptdly=180 nciswrlsatmc=01 00 Table 5: how to use group control function The network variable is configured by 3 fields : Command, position and angle. 16/22

17 Command Position * Angle ** Interpretation OFF ( = 0 ) XX XX unused ON ( = 1 ) XX XX unused DOWN ( = 2 ) invalid invalid going down UP ( = 3 ) invalid invalid going up STOP ( = 4 ) invalid invalid stopped to unknown position STATE (= 5 ) 100% 0% 0<x%<100 invalid invalid invalid up position down position specified position NULL ( = 255 ) XX XX unused Example 1 : The network control A is configured as following :5 ; 50% ; invalid. When the corresponding button will be pressed, the motor(s) will move and the screen(s) will go to the specified position : 50% Example 2 : The network control B is configured as following :3 ; invalid; invalid. When the corresponding button will be pressed, the motor(s) will move and the screen(s) will go up. If you want to control many motors with an interval between their moving, use the configuration parameter AppTimeDelay. 3.7 Network management tools With a supervision, the status of each object in the node, the status of each sunblind can be asked by inputs variable (nvirequest & nvisblndrequest)and reported by output variables (nvostatus & nvosblndstatus1&2). The node object provides Object Status and Sunblind Status Node object management To request and control the status of each object,the node uses an input variable. This input variable provides the mechanism to request a particular mode for a particular object within a node. For example, each node object (group control, Sun object...) can be enable or disable. This input variable includes one field to allow the Node Object to report status for all objects on a node and one field to request the node. For the first one, 4 values are possible : ID=0 : node object ID=1 : group control 17/22

18 ID=2 : wind object ID=3 : sun object For the second one, 4 values are possible 0 :RQ_NORMAL :enable object and remove override. 1 :RQ_DISABLED : disable object. 2 :RQ_UPDATE_STATUS : just report status. 5 :RQ_REPORT_MASK : report status bit mask. This input variable is linked with : SNVT_obj_request nvirequest How to use : ACTION You want to know the status of the node object and set the nvostatus with current object 0 status. nvirequest object_id 0 2 You want to disable the wind object. 2 1 You want to enable the sun object. 3 0 object_request Table 6 : How to use node object management nota : each node can be requested by any value of each object_request. To report the status of any object of the node, the node use an output variable. 4 fields are used for report the status of any object of the node : one reports the ID number A status is reported whenever a request is received for an object id that is not defined in the node. 2 values are possible 0 :disable 1 :enable Reporting a status is required if an unsupported request code is received on the object request input network variable. 2 values are possible 0 :disable 1 :enable reporting if the status is disable or enable 2 values are possible 0 :disable 18/22

19 1 :enable These parameters are linked with the output variable SNVT_obj_status nvostatus How to use : nvostatus is set only when a request status is asked. ACTION The node object Sun is disable Motor(s) status NvoStatus object_id invalid_id invalid_request disabled Table 7 : How to use nvostatus To request the status of the motor(s), the node uses an input variable. This input variable is set each time a request the motor status is send on the network via the input variable nvisblndstatus. And a configuration variable ncisblndmaxsendt can be used to transmit automatically the current value of the output variable(nvosblndstatus) which contains the status of the motor(s). This input variable is linked with : SNVT_char_ascii nvislndrequest To report the motor(s) status, the node uses an output variable. The motor(s) status are send on the output variable(nvosblndstatus1&2) when the timer expires or a request is received. this variable includes three fields. one gives the information of the current position. one indicates the source of the current control of the motor. one indicates what is the cause between the current position and the position asked.. These output variables are linked with : SNVT_SblndState nvosblndstatus1 SNVT_SblndState nvosblndstatus2 How to use : ACTION nvisblndrequest nvosblndstatus1 You want to known the status of the motora 1 2 ;3 ;0 2 indicates the current position : DOWN 3 indicates the Source 19/22

20 position : sun sensor 0 indicates the Cause : well executed Table 8 : How to use Motor Status 3.8 Different configurations A Sensor Interface (in example : Sun Interface ; Rain Interface ;Wind Interface ; Group control interface ) is a node which transmits events or physical values. An actuator Interface ( in example : BIU-2ILT ; BUI-LT ; BIU-2LT ; BIU-6AC...) is a node which receives data from a sensor, a switch or the LonWorks bus and activates or stop the motors. This product supports 3 different configuration processes on the network : -automatic installation : nothing has to be done at installation ; all the Actuator interfaces belong to the same group have the same behavior regarding the sensors of the installation. This automatic installation is implemented when the product leaves the production line ; as soon as another configuration process is used, the automatic installation cannot be used anymore unless a specific software is done on the device itself. -PC configuration by the means of an appropriate software. -intuitive installation : it is an installation configuration used in the SOMFY LonWorks products to configure an installation of sensors and actuators on the network. This configuration consists in creating groups of actuators. All the actuators of the group have the same behavior regarding the sensor controlling the group. The intuitive configuration requests for all the products one button and one LED ; those are ID button and the ID LED. The process of creating a group, at first installation or for a modification, is as follows : Press the ID button of a sensor during approx. 5 until its ID LED flashes ; wait until it stops flashing and turns on continuously. Press the ID button of an actuator ( ex : BIU-LT interface, BUI-6AC interface, BIU-ILT interface...) whose will be controlled by the sensor. Its ID LED and the ID LED of the sensor will flash during few seconds, then its ID LED will turn on as the ID LED of the sensor will turn on again ; this means that the actuator is controlled by the sensor. If an actuator is controlled by the sensor, its ID LED is turn on.the actuator will be no longer control by the sensor, give a pulse on its ID button. Its ID LED of the sensor will flash during few seconds, then its ID LED will turn off ; this means that the actuator is no longer controlled by the sensor. When the group has been set ( or modified ), a pulse on the ID button of the sensor ends the process. All the ID LED will turn off. Nota : the process is anyhow now ended when no ID LED is activated during 3 minutes after the process has been initiated. 20/22

21 This variable is linked with the output variable SNVT_lev_disc nviinstalldel and with the configuration variable SNVT_config_src nciconfigsource 21/22

22 4. DOCUMENTATION REFERENCE The SNVT Master List and Programmer s Guide The Functional Profile ref version /22