Building floor plans can additionally be recorded and retrieved via the floor plan navigation, and the lighting status, blind position, & window status information can be viewed via a floor plan display.
The drawing system has also been modernised and extended. The Quad Client now allows users to select a white interface.
#Knx ets 4 download update
Sapienx Automation provides engineering, training and consultancy for smart buidings, smart metering and smart cities.Besides new functions in the Quad Client, the HomeServer update 4.11 also includes an update for the Gira Expert start-up software. Julio Díaz is an Electrical Engineer at Sapienx Automation, a KNX++ tutor and winner of the KNX International Award. However, if we fail to use the correct local configuration, we might experience error messages from the ETS when loading/unloading devices or when doing diagnoses. The KNX USB device, or local interface, can use any physical address which is not used by another device in the line (typically the local interface is set to the value X.X.100 or X.X.255, as shown in the example above). installations where KNX TP line couplers come into play, the address of the local interface must always correspond to the range in which it is connected. However, in installations with multiple KNX TP lines, i.e. In principle, any default physical address of the local interface does not matter when programing devices within the line where the interface is located. In principle, we can program correctly any device from anywhere in the installation, when the address of the local interface and the addresses of the line couplers are properly configured. The USB interface is located in line 1.2. Programming devices locally and remotely. In the dashboard we have to select Settings –> Communication.
#Knx ets 4 download how to
The following image, shows how to check the address of any local interface in ETS4.
When we first use a local interface such as a USB interface, the physical address of this device has the default address 15.15.255. Main lines are also typical for local interfaces because they are also used as a common point for linking the installation with others, such as visualisation systems, IP interfaces, gateways to other technologies, etc. So, while it is not obligatory to set the local interface in the main or backbone line of the system, main lines such as 1.0 or 0.0 are the logical points to do so, because we use ETS not only for downloading devices but also for testing, telegram monitoring, etc. In order to be successful, you need to configure correctly, and in the right order, the local interface and the TP couplers. Obviously, such messages cause frustration and lost time when downloading or unloading devices, or when carrying out other test operations.įirst of all, I must clarify that, in a KNX installation with multiple KNX TP lines, it is possible to connect the ETS, via the KNX USB interface, in any of the lines for downloading the whole installation. As a consequence, the installer will get the following error message: When this happens, the integrator will be unable to communicate with the device to be configured. Sometimes we do not adequately understand the importance of a correct configuration of the KNX USB interface (local) address. A common task for many integrators is programming the KNX devices in a project with multiple lines connected via KNX TP couplers.