DOCUMENTATION MECrf TECHNICAL AND APPLICATION DESCRIPTION. Last modification: 24 November 2017

Size: px

Start display at page:

Download "DOCUMENTATION MECrf TECHNICAL AND APPLICATION DESCRIPTION. Last modification: 24 November 2017"

David Garrett
5 years ago
Views:

DOCUMENTATION MECrf TECHNICAL AND APPLICATION DESCRIPTION Author: Peter Hauner Last modification: 24 November 2017 2001-2017 Apricum d.o.o. Mažuranićeva 4, 21312 Podstrana, Hrvatska Details, modifications and corrections may be subject to change without notice.

1 DOCUMENTATION MECrf TECHNICAL AND APPLICATION DESCRIPTION Author: Peter Hauner Last modification: 24 November Apricum d.o.o. Mažuranićeva 4, Podstrana, Hrvatska Details, modifications and corrections may be subject to change without notice. Apricum gives no warranty for the accuracy of the document. The reproduction, transmission and use of this document or its contents is not permitted without written authority. All rights reserved.

2 1 CONTENTS 1 Contents MECrf Product Description Apricum MECrf Highlights Operational Description Normal Mode Program Button The Function Button Manual Function Factory Reset Application Description ETS Parameters Physical Address Assignment General Main Line (KNX TP) Subline (KNX RF) State of Delivery Technical Data RF Technical Data Dimension Drawing /

3 2 MECrf PRODUCT DESCRIPTION The basic functionality of the media coupling device MECrf is connecting KNX TP (main line) and KNX RF (subline). Main task of the MECrf is filtering the telegram traffic according to the installation place in the hierarchy (individually addressed telegrams, in this document named Physical telegrams) or according to the built in filter tables for group oriented communication (Group telegrams). Filtering of messages can be enabled or disabled. With the MECrf it is possible to address every bus device in the bus system. For RF devices the MECrf can be used as the programming interface via TP. Programming on the TP side from RF side can be suppressed. Number of retransmissions can be reduced. Device oriented messages can be suppressed. The MECrf has no KNX communication objects for itself, supports long messages (up to 201 byte APDU length) and features a configurable Manual function (e.g. transmit all group telegrams) that can be activated by a single button press. In addition, the device switches on filter tables after time out automatically. Another feature to increase the data trough put is the ability to send an immediate acknowledged (IACK on TP side) on an own frame. The device conforms to KNX-AN161 with all options (Filtering, Raw mode) and offers a detailed internal diagnosis by displaying all operational states with six LEDs. The LEDs show the device states like bus state, traffic on bus, errors/faulty messages, busy on the bus, state of the filter table, etc. LED Picture 1: Frontside panel and backside panel description 1 Bus State KNX RF (Subline) 7 Programming 2 Bus State KNX TP (Main line) Part 3 4 Telegram Traffic KNX RF (Subline) Telegram Traffic KNX TP (Main line) / 13 A B RF antenna Function button 5 Physical Address Routing C Program button 6 Group Address Routing D KNX TP connector

3 APRICUM MECrf HIGHLIGHTS In combination with the Apricum USB interface UIMtp long messages are made possible (e.g. for energy metering applications).

4 3 APRICUM MECrf HIGHLIGHTS In combination with the Apricum USB interface UIMtp long messages are made possible (e.g. for energy metering applications). The MECrf favourably replaces a line coupler in a wireless sub network. The Apricum MECrf works without external power supply. Retransmitter function is supported. Picture 2: Connection scheme IACK on own sent out messages (ETS configurable) on TP side. After no IACK response on TP side the MECrf is able to repeat it up to three times. For physically addressed and for group addressed telegrams this can be configured via ETS independently. In case of an IACK response there will be no repetition. The failure mechanism of a negative IACK or BUSY is still maintained hereby. Programmable automatic switch on of the filter table after timeout. For a predefined amount of time (ETS configurable) it is possible to switch off the filter table with pressing a button on the device. So, without reconfiguring the device with the ETS the filter table can be switched off by a button press which is necessary for running fast diagnostics on site. Filtering of messages can temporarily be disabled by pressing the Function button. This eases commissioning and debugging of the system. Without an ETS download a temporary access to other lines is possible. After the timeout an automatic switching the filter table on is implemented (the timeout is configurable in the ETS). This avoids forgetting to reactivate the filter. For networks with a high bus load a high internal amount of communication buffers is suitable. The MECrf is featuring a high internal amount of communication buffers being capable of smoothing peeks in the communication load course. The MECrf s ETS database entries are available for the ETS5. 4 /

5 4 OPERATIONAL DESCRIPTION According either to the factory default settings or the latest parameter settings downloaded from ETS (also other tools) the MECrf operates as it is supposed to. Like a polite device the MECrf s internal functioning contains channel sensing before transmission to determine if the transmission channel is free. Concerning any end user application the duty cycle must be kept below 1%. Please note for commissioning: Do not mount the MECrf on a metal rail or on a metal fastener. Make sure that during operation a minimum distance of 20cm to the human body, conducting surfaces and metal objects is kept. All telegrams are blocked because the filter table is not defined The switch-off time for the Manual Function is 60 min The physical address is NORMAL MODE Number LED Colour Explanation / Range Bus State KNX RF (Subline) Bus State KNX TP (Main line) Telegram Traffic KNX RF (Subline) Telegram Traffic KNX TP (Main line) Physical Address Routing Group Address Routing 7 Programming green Subline OK < off > Subline not connected green green+red Main line OK Manual Function active < off > Main line not connected blinking green Telegram traffic extent indicated by blinking blinking red Transmission error < off > No telegram traffic blinking Telegram traffic extent of routed telegrams, green indicated by blinking blinking red Transmission error < off > No telegram traffic routed green orange Filtering active Block all green+orange Route all < off > Routing of Physical telegrams not the same between main line and subline green Filter table active red green+red < off > red blinking red Block all Route all Routing of Group telegrams not the same between main line and subline Program mode active No RF connection / 13

6 4.2 PROGRAM BUTTON To download the desired physical address or to download a full ETS setting the Program button needs to be pressed. Successive pressing on the Program button will lead to turn on and off the ETS Program Mode. The Programming LED (LED 7) lights up in colour red. 4.3 THE FUNCTION BUTTON The Function button is used for two purposes; either to activate/deactivate the Manual Function or to do a factory reset. It depends on the duration of time this button is pressed MANUAL FUNCTION Picture 3: Side view and Function button Long press ( 3 sec) Pressing the Function button for about 3 seconds turns on and off the Manual Function. When turned to On the LEDs 2,5,6 light with mixed colour and LED 1 lights green. The default function is set by the RF line and the (KNX) line parameters. To configure the Manual Function and set the Fallback time use the ETS parameter tab General. The last downloaded parameter setting and filter table are still available after switching back from Manual Function to Normal Mode. During a physical address download (also full download) the Manual Function is switched off automatically FACTORY RESET Very long press ( 15s) A factory reset is carried out by pressing the Function button for about 15 seconds (LEDs 2,5,6 and LED 1 light with mixed colour). After release, pressing it again for some seconds resets all the parameters to factory default (incl. physical address and since version 1.3 domain address). Subsequently, the LEDs change their status. 6 /

7 5 APPLICATION DESCRIPTION When the coupler receives telegrams (for example during commissioning) that use physical addresses as destination addresses, it compares the physical addresses of the receiver with its own physical address and then decides whether it has to route the telegrams or not. Due to telegrams with group addresses the coupler reacts in accordance with its parameter settings. During normal operation (default setting), the coupler only routes those telegrams whose group addresses have been entered in its filter table. If the coupler routes a telegram and does not receive an acknowledgement, or if a bus device discovers a transmission error, the coupler repeats the telegram on TP side up to three times (depending on the corresponding parameter that is set to the device through the last ETS download). With the parameters Repetitions if errors..., this behaviour can be set separately for both Physical telegrams and Group Telegrams. These parameters should stay with the default setting. 6 ETS PARAMETERS All screen shots in this chapter represent the MECrf database entry in ETS PHYSICAL ADDRESS ASSIGNMENT With the ETS the physical address can be assigned to the device by setting the desired address in the properties window of the ETS. To download the desired physical address and a full ETS setting into the device the Program button C has to be pressed. The Program button puts the device into Program Mode. After starting the download and pressing the Program button the device restarts itself. To commission the device an interface connection (IP, USB) to the KNX bus system is required. The device is supplied with the individual physical address The KNX product database entry (available for ETS5 and higher) can be downloaded from the Apricum website and the KNX Online Catalog. Note: In this document only the term physical address is used. The term physical address means the physical address as well as the individual address. Both terms are used by the KNX organisation interchangeably. Picture 4: Properties window / 13

8 6.2 GENERAL Picture 5: General ETS Text Switch-off time for Manual Function Manual Function Selection [Factory default] 10 min, 1 hour, 4 hours, 8 hours [1 hour] disabled pass all telegrams pass all Physical telegrams pass all Group telegrams [pass all telegrams] Comment After expiry of this time period the Manual Function is switched off automatically. Configuration setting for telegram routing when the Manual Function is activated. 6.3 MAIN LINE (KNX TP) For Group telegrams and Physical telegrams the selection transmit all is intended only for testing purposes. Please do not use for normal operation. If the parameter Send confirmation on own telegrams is set to yes, the MECrf systematically sends an ACK on any own routed telegram. Picture 6: Main line (KNX TP) 8 /

9 ETS Text Telegram routing Group telegrams: Main group 0 13 Group telegrams: Main group Physical telegrams Physical: Repetition if errors on main line Group: Repetition if errors on main line Telegram confirmation on main line Send confirmation on own telegrams Selection [Factory default] Group: filter, Physical: block Group and Physical: filter Group: route, Physical: filter Group and Physical: route configure [Group and Physical: filter] 1. transmit all (not recommended) 2. block 3. filter [filter] 1. transmit all (not recommended) 2. block 3. filter [filter] 1. transmit all (not recommended) 2. block 3. filter [filter] 1. no 2. up to 3 repetitions 3. one repetition [up to 3 repetitions] 1. no 2. up to 3 repetitions 3. one repetition [up to 3 repetitions] 1. if routed 2. always [if routed] 1. yes 2. no [no] Comment - block: no telegrams are routed. - filter: only telegrams entered in the filter table are routed. - route: all telegrams are routed. - configure: the following parameters can be set manually. 1. Group telegrams (with main group 0 13) are routed. 2. Group telegrams (with main group 0 13) are not routed. 3. Group telegrams (with main group 0 13) are routed if they are entered in the filter table. 1. Group telegrams (with main group 14 31) are routed. 2. Group telegrams (with main group 14 31) are not routed. 3. Group telegrams (with main group 14 31) are routed if they are entered in the filter table. 1. All Physical telegrams are routed. 2. Physical telegrams are not routed. 3. Depending on the physical address Physical telegrams are routed. Transmission error (e.g. missing receiver) after sending a Physical telegram on the main line: 1. Physical telegrams are not repeated. 2. Physical telegrams are repeated up to 3 times. 3. Physical telegrams are repeated only once. Transmission error (e.g. missing receiver) after sending a Physical telegram on the main line: 1. Group telegrams are not repeated. 2. Group telegrams are repeated up to 3 times. 3. Group telegrams are repeated only once. 1. Only routed telegrams are confirmed on the main line (own ACK). 2. Each telegram on the subline is confirmed (own ACK). 1. Every telegram on the main line is confirmed with its own ACK (from the media coupler). 2. No confirmation with own ACK / 13

10 6.4 SUBLINE (KNX RF) For Group telegrams and Physical telegrams the selection transmit all is intended only for testing purposes. Please do not use for normal operation. Picture 7: Subline (KNX RF) ETS Text Telegram routing Group telegrams: Main group 0 13 Group telegrams: Main group Physical telegrams Configuration from subline (KNX RF) Selection [Factory default] Group: filter, Physical: block Group and Physical: filter Group: route, Physical: filter Group and Physical: route configure [Group and Physical: filter] 1. transmit all (not recommended) 2. block 3. filter [filter] 1. transmit all (not recommended) 2. block 3. filter [transmit all] 1. transmit all (not recommended) 2. block 3. filter [filter] allow block [allow] Comment - block: no telegrams are routed. - filter: only telegrams entered in the filter table are routed. - route: all telegrams are routed. - configure: the following parameters can be set manually. 1. Group telegrams (with main group 0 13) are routed. 2. Group telegrams (with main group 0 13) are not routed. 3. Group telegrams (with main group 0 13) are routed if they are entered in the filter table. 1. Group telegrams (with main group 14 31) are routed. 2. Group telegrams (with main group 14 31) are not routed. 3. Group telegrams (with main group 14 31) are routed if they are entered in the filter table. 1. All Physical telegrams are routed. 2. Physical telegrams are not routed. 3. Depending on the physical address Physical telegrams are routed. If blocked, then the ETS download to the MECrf can only occur via KNX TP (main line). 10 /

11 7 STATE OF DELIVERY The MECrf is delivered with the following default factory settings: General Product Order Number Application(s) ETS Name TP RF Media Coupler MECrf RF Coupler TP RF Coupler MECrf Physical address KNX TP (KNX TP Main line to RF Subline) Group telegrams (main group 0 13) Group telegrams (main group 14 31) Physical telegrams Physical: Repetition if errors on KNX TP Group: Repetition if errors on KNX TP Telegram confirmations on KNX TP Send confirmation on own telegrams filter filter filter up to 3 repetitions up to 3 repetitions if routed no KNX RF (KNX RF Subline to KNX TP Main line) Group telegrams (main group 0 13) Group telegrams (main group 14 31) Physical telegrams Configuration from KNX TP filter filter filter enabled / 13

8 TECHNICAL DATA Warning: Do not connect to 230V Marking/Design Current consumption Connection Display elements Control elements Protection type Pollution degree Protection class Overvoltage category

12 8 TECHNICAL DATA Warning: Do not connect to 230V Marking/Design Current consumption Connection Display elements Control elements Protection type Pollution degree Protection class Overvoltage category Approbation CE Marking Power supply Housing colour Dimensions Weight Device temperature Ambient humidity RF performance MECrf < 10 ma KNX TP line: KNX TP connector (red/black), screwless for single-core cable Ø mm LED Bus State LED Telegram Traffic LED PA/GA LED Programming Function button, Program button IP20 according to IEC according to IEC III according to IEC61140 II according to IEC KNX-certified according to ISO/IEC According to low voltage and EMC guidelines Compliance with EN50428, EN50581, EN and EN62479 Safety extra low voltage, 21 30V DC (SELV) Transparent plastic PA66 housing H = 40 mm, W = 40 mm, D = 9 mm 14 g Working temperature: C Storage temperature: C 5 93 %, non-condensing RF antenna RF range: up to 100 m 12 /

9 RF TECHNICAL DATA Frequency range KNX RF KNX Ready (RF+) Modulation Rx radiated sensitivity Tx radiated power KNX Ready RF1.R KNX Multi Bibat max. APDU length 868.

13 9 RF TECHNICAL DATA Frequency range KNX RF KNX Ready (RF+) Modulation Rx radiated sensitivity Tx radiated power KNX Ready RF1.R KNX Multi Bibat max. APDU length MHz + / Khz FSK -100 dbm KNX specification (-95 dbm) +10 dbm KNX specification (0 dbm) Yes (with Listen Before Talk medium access) Hardware is ready for KNX Multi Not supported 201 bytes Mask Version DIMENSION DRAWING All dimensions shown here are specified in mm. Picture 8: Dimension drawing / 13

KNX USB INTERFACE UIMtp

KNX USB INTERFACE UIMtp TECHNICAL AND APPLICATION DESCRIPTION Author: Peter Hauner Last modification: 13 November 2017 2001-2017 Apricum d.o.o. Mažuranićeva 4, 21312 Podstrana, Hrvatska Details, modifications