KNX IP Interface PoE N000401

N000401 DE 31640810 WEEE

Our best price
10,950.63₹ excl. VAT

5-6 days* (IND)

Safety and hazard information
Please note that electrotechnical work may only be carried out by qualified electricians or under their guidance and supervision. Observe any deviating country-specific electrical installation standards and regulations and seek advice from a local electrician.In addition, observe more current safety instructions and regulations for the products on the manufacturer's side or the product descriptions and installation instructions on the manufacturer's side.

Devices with a connected load of > 380V/400V require a heavy current connection and may only be connected by an approved electrical company. Devices with a power rating > 12kW require the approval of your grid operator (Germany, other countries may differ).
read more
show less
Note: The Power over Ethernet supply is standardized acc. to Standard PoE (IEEE 802.3af) and... more
KNX IP Interface PoE N000401 – EIBMARKT: Note: The Power over Ethernet supply is standardized acc. to Standard PoE (IEEE 802.3af) and integrated via RJ45. We can recommend a PoE Ethernet Switch from Netgear, e.g. FS108P. The device disposes of 8 ports, four of which are equipped with Power over Ethernet (IEEE802.3af, 48 VDC). The IP interface, for example, can be connected to one of these four ports. As an alternative, power supply can be provided by means of screw connecting terminals at the upper side using a separate power supply unit (12-24V DC) or transformer (12-24V AC). Parallel power must be avoided! Caution when using managed Switches (Cisco or similar): With some Switches there can problems with the standard settings and the IP devices are not recognized. In this case make the following adjustment at the Switch: Full-Duplex-Mode Digit rate: 10 Megabit/s A blinking Ethernet LED at the IP Router or IP Interface indicates an existing link i.e. the digit rate and the mode have been set correctly. KNX/EIB IP Interface IP Interface between LAN and EIB/KNX bus Application area The KNXnet/IP-Interface is used to connect a PC to the KNX/EIB network for programming via ETS or visualizations. The connection is made through LAN (IP). The IP address can be obtained by a DHCP server or by manual configuration (ETS) respectively. This device works according to the KNXnet/IP specification using the core, the device management und the tunnelling part. A typical application: the device is mounted in the sub-distribution and connected to the KNX EIB. The sub-distribution also disposes of a network connection to a remote PC. Using the remote PC the EIB KNX devices can be programmed, now, by means of LAN via ETS or the facility can be visualized with the respective software tools. The IP interface can also be used directly with a PC using a cross link cable. The PC must dispose of a valid IP configuration, i.e. at least the IP address and the sub-network must have been adjusted. The IP interface must have the same sub-network and get an IP address from this area. An example: PC: IP address: 192.168.1.10 Sub-network: 255.255.255.0 IP Interface: IP address: 192.168.1.11 Sub-network: 255.255.255.0 In this particular case, the IP interface must be provided with voltage from a power unit using a cross link cable since no switch that is capable of Power over Ethernet (PoE) is available here. Up to 5 tunneling connections possible, one tunneling connection already configured by the manufacturer with the physical address 15.15.250. Allocating or configuring further tunneling connections can be realized by pressing the Learn Key (>1sec). All other tunneling connections are then configured depending on the first tunneling connection such as: Tunneling connection 1 (15.15.250) Press key >1sec (flashing of Learn LED indicates that the additional connections have been activated). Tunneling connection 2 (15.15.251) Tunneling connection 3 (15.15.252) Tunneling connection 4 (15.15.253) Tunneling connection 5 (15.15.254) If you press the key for < 1sec, the normal only Learn mode of the device (physical address KNX) is activated and this is indicated by the permanent LED light. To configurate the additional tunneling connections proceed as follows: Initial situation: Device is connected with KNX Bus and supplied with electricity, Learn LED is not on. Press and hold the Learn key. > Press Learn key until Learn LED starts to flash quickly. > Release Learn key only after flashing has stopped and LED is off again. The remaining 4 tunneling connection received their physical addresses as described in this procedure. To change the address area of the tunneling connection, the physical address of the first tunneling connection must be adapted. This adjustment is made by means of the ETS in the communication settings. Using the input field Physical address in the window Local adjustments the physical address of the first tunneling connection can be changed. Press the Learn Key again for more than 1 sec to configure the other tunneling connections. It must be considered that there might be address conflicts here since the addresses of the tunneling connections are not displayed directly in the ETS project! The physical addresses for the tunneling connections are always allocated starting from the physical address of the first tunneling connection upwards. e.g.: Tunneling 1: 1.1.1 à Tunneling 2: 1.1.2, Tunneling 3: 1.1.3, Tunneling 4: 1.1.4, Tunneling 5: 1.1.5 Technical data   Electrical safety   - Protection (EN 60529): IP 20   - Safety extra low voltage SELV DC 24 V   EMC requirements   - Complies with EN 61000-6-2, EN 61000-6-3 and EN 50090-2-2   Environmental requirements   - Ambient temp. operating: - 5 ... + 45 °C   - Ambient temp. Non-op.: - 25 ... + 70 °C   - Rel. humidity (non-condensing): 5 % ... 93 %   Certification   - EIB/KNX   CE norm   - Complies with the EMC regulations (residential and functional buildings) and     low voltage directive   Physical specifications   - Housing: Plastic   - Rail mounted device   - Width: 36 mm   - Weight: approx. 100 g   - Fire load: approx. 1000 kJ   Operating controls   - Learning key for EIB/KNX   Indicators   - Learning-LED (red)   - Signal-LED (green) for EIB/KNX   - Signal-LED (green) for LAN   Ethernet   - 10BaseT (10Mbit/s)   - Supported internet protocols ARP, ICMP, IGMP, UDP/IP and DHCP   Power supply   - External supply 12-24V   - Alternative: Power-over-Ethernet   - Power consumption: < 800 mW   Connectors   - EIB/KNX connection terminal   - LAN RJ-45 socket   - Screw connector for power supply Manufacturer: EIBMARKT GmbH Item number: N000401 Some more hints about the technique of monitoring: The group-/and bus monitor works in the ETS3 but not the old bus monitor from IT GmbH (separate external tool). Programming is done starting from ETS3. You are searching for active IP components in the network (KNXnet/IP > Scan) via ETS3, the ETS3 will then find and suggest the respective device. Now, you can load the application using LAN. Normally, a change of the physical address can only be made using an additional interface not locally (only Com Port is local for ETS3). TIP to change the physical address: Using ETS3 you can ''simply'' program the physical address or use the Replace function. Then, there will be an error message of the ETS3, but the device has, however, really been changed on the bus with a new address, just test it ... Programming of the IP-Interfaces should be done via the bus (EIB KNX), i.e. using another IP-Interface or a USB-interface. The IP-Interface has two physical addresses: First, the usual physical address as any other KNX device. In addition to that, there is another physical address for the connection which can be selected using Extras->Options->Communication->Adjustments. These two addresses should be different. Otherwise it might be impossible to program the IP-Interface. If there is no other interface available for programming, the IP-Interface itself can be used. To do so, a connection via the IP-Interface must be made. Then, the IP-Interface has to be programmed (select ''via Bus''). After changing the IP-address the IP-connection collapses, i.e. the IP-connection must be configured again using Extras->Options->Communication->etc. Programming by selecting ''local'' is possible as far as the device goes but the current ETS version does not yet support this.p>The IP Interface supports bus monitor mode, the IP Router does not. When downloading you might have selected ''local'' ? That does not work in the ETS. Even for local connection the selection must be made ''via Bus''. However, first, the two individual physical addresses of the device must be set correctly, see our handbook (PDF) from the product detail view in the Shop. Another problem can be the Firewall! For the Firewall rules Port 3671 should be entered. This is the port to which the IP interface responds; it is always the same. Communication is ensured by UDP, only. photographed by EIB3D.COM
... more

Rate item

(0 reviews)
Read, write and discuss reviews... more
Customer review for "KNX IP Interface PoE N000401"
Write a review
Evaluations will be activated after verification.
Please enter these characters in the following text field.

The fields marked with * are required.