EAE LC200 KNX Line Coupler User Manual

: June 16, 2024
: EAE

Table of Contents

General
KNX Programming Mode
Manual Operation and Status display
Factory Default Settings
Reset to factory device Settings
Coupler function
Repeater function
ETS Database
Filter Table
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

Product Manual LC200
EAE KNX Line Coupler
LC200 PM R1.0
EAE KNX LINE Coupler
Product Manual LC200 EAE LC200 KNX Line Coupler Order Code: 50564

General

The KNX LineCoupler 200 is a KNX line coupler in a compact design. It connects two KNX bus segments (for example, a KNX line with a KNX area).
The device has a filter table (8k bytes) and ensures a galvanic separation between the lines. The coupler supports KNX long frames and is compatible with the ETS® software (ETS4 or higher).
The buttons on the front side allow to deactivate the telegram filters for test purposes. The LEDs indicate operating conditions as well as communication errors on the KNX bus.
The power is supplied via the KNX bus (main line).
1.1. Technical Data

Power supply	Bus	DC 21…30V SELV
Current consumption from KNX main line	5 mA
Current consumption from KNX sub line	3 mA
Connections	KNX Main Line
KNX Sub Line	Bus connection terminal

NOTE: Device default physical address is 15.15.0. In order to configure KNX Presence detector, ETS application file “.knxprod” is needed. It’s possible to download the file on EAE website. ETS is required for programming the device. Parameter settings and related group addresses can be changed by ETS. Learn more by reading ETS help file.

1.2. Installation and Connection
The KNX LineCoupler 200 is designed for installation on a DIN rail with a width of 1 unit (18mm). It features the following controls and displays:

EAE LC200 KNX Line Coupler - Connection

❶ KNX Bus Connector (main line)
❷ LED for Programming Mode (red)
❸ Button for Programming Mode
❹ LED KNX (mainline, multicolor)
❺ LED Mode (multicolor)| ❻ LED KNX (sub line, multicolor)
❼ Button ,,Pass Gas”
❽ Button ,,Pass IAs”
❾ KNX bus connector (sub line)
---|---

An external power supply is not necessary as the device is powered by the KNX bus.
The device is not working without bus power (main line).

KNX Programming Mode

The KNX programming mode is activated/deactivated either by pressing the flushed KNX programming button ❸ or by simultaneously pressing the buttons ❼ and ❽.

Manual Operation and Status display

The KNX main line LED ❹ lights up green if the device is successfully powered by the KNX bus. This LED indicates telegram traffic on the KNX bus by flickering.
Communication failures (e.g. repetitions of telegrams or telegram fragments) are indicated by a short change of the LED color to red.
Overview of the different indications of KNX main line LED ❹:

LED Status	Meaning
LED lights green	KNX Bus power (main line) active
LED flashes green	Telegram traffic on the KNX bus (main line)
LED turns red (short)	Communication error on the KNX bus (main line)

The KNX sub line LED ❻ lights up green when the device is ready for operation (supplied by the main line) and the KNX bus voltage is present on the sub line. If the LED is flickering, telegram traffic takes place on the sub line.
Errors in the communication (such as telegram repeats or telegram fragments) are indicated by a short time color change to red.
Overview of the different indications of KNX sub line LED ❻:

LED Status	Meaning
LED lights green	KNX Bus power (sub line) active
LED flashes green	Telegram traffic on the KNX bus (sub line)
LED turns red (short)	Communication error on the KNX Bus (sub line)

For testing purposes (for example, during commissioning) the configured routing settings (filter or block) can be bypassed via manual operation.
With the button “Pass GAs” ❼ the forwarding of group addressed telegrams can be activated.
With the button “Pass IAs” ❽ the forwarding of individually addressed telegrams can be activated.
This is visualized with a single flash of the Mode LED ❺ (orange). If both modes are activated the Mode LED ❺ flashes two times.
Pressing button “Pass GAs” ❼ or button “Pass IAs” ❽ again these settings can be selected and deselected on demand. Via the Escape function (Esc) the manual operation can be stopped by simultaneously pressing the buttons “Pass GAs” ❼ and “Pass IAs” ❽.
If neither programming mode nor manual mode are active the LED ❺ can visualize configuration errors (for details see table below).
Overview of the different indications of the Mode LED ❺:

LED Status	Meaning
LED lights green	Device is working in standard operation mode.
LED lights red	Programming mode is active
LED flashes 1x orange	Programming mode is not active.

Manual operation is active.
Forwarding IA or GA
LED flashes 2x orange| Programming mode is not active.
Manual operation is active.
Forwarding IA and GA
LED flashes red| Programming mode is not active.
Manual operation is not active.
The device is not properly loaded e.g.
after an interrupted download.

Factory Default Settings

Factory default configuration

Reset to factory device Settings

It is possible to reset the device to its factory settings:

Disconnect the KNX Bus connector (main line) ❶ from device
Press the KNX programming button ❸ and keep it pressed down
Reconnect the KNX Bus connector (main line) ❶ of device
Keep the KNX programming button ❸ pressed for at least another 6 seconds
A short flashing of the programming LEDs (❷) visualizes the successful reset of the device to factory default settings.

Coupler function

The KNX LineCoupler 200 operates as a line or backbone coupler. In both cases, KNX TP is used as a backbone.
The following table shows the application possibilities of the KNX LineCoupler 200 compared to the IP based topology:

| Classical Topology (without IP)| IP coupling of areas (IP area coupler)| IP coupling of lines (IP line coupler)
---|---|---|---
Area (Backbone)| TP| IP| IP
Coupling| KNX Line Coupler (max. 15 Pcs.)| KNX IP Router (max. 15 Pcs.)| Directly via LAN Switch
Main line| TP| TP| IP
Coupling| KNX Line Coupler (max. 15×15 Pcs.)| KNX Line Coupler (max. 15×15 Pcs.)| KNX IP Router (max. 225 Pcs..)
Line| TP| TP| TP

EAE LC200 KNX Line Coupler - KNX LineCoupler 200 as line
coupler The individual address assigned to the KNX LineCoupler 200 determines whether the device operates as a line or area coupler. If the individual address is in the form of x.y.0 (x, y: 1..15), the device operates as a line coupler. If it is in the form of x.0.0 (x: 1..15), the router acts as a backbone coupler. EAE LC200 KNX Line
Coupler - Area Coupler

The KNX LineCoupler 200 has a filter table and thus contributes to reducing the bus load. The filter table (8kB) supports the extended group address range and is automatically generated by the ETS.

Repeater function

The KNX LineCoupler 200 can also be used as a repeater. In this case, the individual address has the form x.y.z, where z must not be equal to 0. The filter settings in the parameter dialog of the ETS are ineffective in repeater mode. EAE LC200 KNX Line Coupler - Repeater

ETS Database

The ETS database (for ETS 4.2 or higher) can be downloaded from the product website of the KNX Line Coupler 200 (www.eaetechnology.com).
8.1. ETS Parameter Dialogue
The following parameters can be set using the ETS.
8.2. General Settings

EAE LC200 KNX Line Coupler - General Settings

8.3. Programming mode on device front

EAE LC200 KNX Line Coupler - device front In addition to the normal programming button ❸ the device allows activating the programming mode on the device front without opening the switchboard cover. The programming mode can be activated and deactivated via pressing simultaneously both buttons ❼ and ❽.
This feature can be enabled and disabled via the parameter “Prog. mode on device front”. The recessed programming button ❸ (next to the Programming LED ❷) is always enabled and not influenced by this parameter.

8.4. Manual operation on device
This parameter sets the duration of the manual mode. Upon completion the normal display mode is restored.
8.5. Routing (Sub line → Main line) EAE LC200 KNX Line Coupler -
Routing

Group telegrams (main group 0 to 13)

Block:| No group telegrams of this main group are routed to the main line.
Route:| All group telegrams of this main group are routed to the main line
independent of the filter table. This setting is for test purposes only.
Filter:| The filter table is used to check whether or not the received group
telegram should be routed to the main line.
Group telegrams (main group 14 to 31)
Block:| No group telegrams of main groups 14 to 31 are routed to the main line.
Route:| All group telegrams of main groups 14 to 31 are routed to the main line.
This setting is for test purposes only.
Filter:| The filter table is used to check whether or not the received group telegram should be routed to the main line.
Individually addressed telegrams
Block:| No individually addressed telegrams are routed to the main line.
Route:| All individually addressed telegrams are routed to the main line. This setting is for test purposes only.
Filter:| The individual address is used to check whether the received individually addressed telegram should be routed to the main line.
Broadcast telegrams
Block:| No received broadcast telegrams are routed to the main line.
Route:| All received broadcast telegrams are routed to the main line.
Repetition of group telegrams
Disabled:| The received group telegram is not resent to the main line in case of a fault.
Enabled:| The received group telegram is resent up to three times in case of a fault.
Repetition of individually addressed telegrams
Disabled:| The received individually addressed telegram is not resent to the main line in case of a fault.
Enabled:| The received individually addressed telegram is resent up to three times in case of a fault.
Repetition of broadcast telegrams
Disabled:| The received broadcast telegram is not resent to the main line in case of a fault.
Enabled:| The received broadcast telegram is resent up to three times in case of a fault.
Acknowledge (ACK) of group telegrams
Always:| A acknowledge is generated for every received group telegram (from the sub line).
Only if routed:| A acknowledge is only generated for received group telegrams (from the sub line) if they are routed to the main line.
Acknowledge (ACK) of individually addressed telegrams
Always:| A acknowledge is generated for every received individual addressed telegram (from the sub line).
Only if routed:| A acknowledge is only generated for received individually addressed group telegrams (from the sub line) if they are routed to the main line.
Answer with NACK:| Every received individually addressed telegram (from the sub line) is responded to with NACK (Not acknowledge). This means that communication with individually addressed telegrams on the corresponding KNX line is not possible. Group communication (group telegrams) is not affected. This setting can be used to block attempts at manipulation.

When using “Answer with NACK” an access to the device via the KNX sub line is no longer possible. The configuration must be performed via the main line.

8.6. Routing (Main line → Sub line)

EAE LC200 KNX Line Coupler - Main line

Group telegrams (main group 0 to 13)

Block:| No group telegrams of this main group are routed to the sub line.
Route:| All group telegrams of this main group are routed to the sub line
independent of the filter table. This setting is for test purposes only.
Filter:| The filter table is used to check whether or not the received group telegram should be routed to the sub line.
Group telegrams (main group 14 to 31)
Block:| No group telegrams of main groups 14 to 31 are routed to the sub line.
Route:| All group telegrams of main groups 14 to 31 are routed to the sub line.
This setting is for test purposes only.
Filter:| The filter table is used to check whether or not the received group telegram should be routed to the sub line.
Individually addressed telegrams
Block:| No individually addressed telegrams are routed to the sub line.
Route:| All individually addressed telegrams are routed to the sub line. This setting is for test purposes only.
Filter:| The individual address is used to check whether the received individually addressed telegram should be routed to the sub line.
Broadcast telegrams
Block:| No received broadcast telegrams are routed to the sub line.
Route:| All received broadcast telegrams are routed to the sub line.
Repetition of group telegrams
Disabled:| The received group telegram is not resent to the sub line in case of a fault.
Enabled:| The received group telegram is resent up to three times in case of a fault.
Repetition of individually addressed telegrams
Disabled:| The received individually addressed telegram is not resent to the sub line
in case of a fault.
Enabled:| The received individually addressed telegram is resent up to three times in
case of a fault.
Repetition of broadcast telegrams
Disabled:| The received broadcast telegram is not resent to the sub line in case of a fault.
Enabled:| The received broadcast telegram is resent up to three times in case of a fault.
Acknowledge (ACK) of group telegrams
Always:| A acknowledge is generated for every received group telegram (from the main line).
Only if routed:| A acknowledge is only generated for received group telegrams (from the sub line) if they are routed to the sub line.
Acknowledge (ACK) of individually addressed telegrams
Always:| A acknowledge is generated for every received individual addressed telegram (from the main line).
Only if routed:| A acknowledge is only generated for received individually addressed group telegrams (from the main line) if they are routed to the sub line.
Answer with NACK:| Every received individually addressed telegram (from the main line) is responded to with NACK (Not acknowledge). This means that communication with individually addressed telegrams on the
corresponding KNX line is not possible. Group communication (group telegrams) is not affected. This setting can be used to block attempts at manipulation.

When using “Answer with NACK” an access to the device via the KNX main line is no longer possible. The configuration must be performed via the sub line.

Filter Table

The filter table is automatically created by the ETS. The group addresses of the telegrams which shall be forwarded via the coupler are added to the filter table. The contents of the filter table can be displayed via the preview: EAE
LC200 KNX Line Coupler - filter The filter table can be extended by manually adding group addresses. This requires activating “Pass through Line Coupler)” in the property window of the corresponding group address. Due to the significantly shorter transmission times it is recommended to perform downloads via IP.
WARNING

The device must be mounted and commissioned by an authorized electrician.
The prevailing safety rules must be heeded.
The device must not be opened.
For planning and construction of electric installations, the relevant guidelines, regulations and standards of the respective country are to be considered.

©EAE Technology
www.eaetechnology.com