KNX

iRidium for KNX

Description on the web site

Specification

Updated: 25.01.2014

iRidium for KNX is a package of tools for creating unique interfaces and controlling automation systems on the basis of KNX equipment.

iRidium for KNX enables connection of control panels (iOS/Windows/Android/OS X) to the KNX TP1 network via any gateway or KNX router with IP Unicast support: Jung IPS 100/200 REG, Jung IPR 100/200 REG, Evika Logic Machine 2, 3, Reactor, Weinzierl KNX IP BAOS 770/771/772, ABB, Siemens, Gira, etc.

iRidium for KNX uses the IP Unicast connection to the KNX IP gateway to transfer data to the KNX TP1 network via the KNXnet/IP Tunneling protocol.

See information about working with the KNX bus through KNX IP BAOS 771/772 and Object Server (Datapoints) in the KNX IP BAOS section.

This manual introduces only the standard way of using iRidium for controlling equipment of the KNX bus (without using scripts).

Licensing of iRidium for KNX (more):

• Device License Pro (KNX) – a license for a control panel. It enables control of any equipment in the KNX bus via any KNX IP gateway or router with the KNXnet/IP support.
• Site License Pro (Logic Machine 2,3,Reactor) – a license assigned to a Logic Machine controller with the KNX IP gateway function. It can be uploaded on several control panels. The license works when there is connection with the licensed Logic Machine controller.

It is important to know that Logic Machine supports not more than 10 control panels connected simultaneously. If there are more than 10 control panels, then it is required to install an additional KNX IP gateway for which you also need to get a Site license.

This license can be used also when working with other KNX IP gateways and routers (not only Logic Machine), but the number of simultaneous connections will be lower. For example, you can use KNX IP BAOS without Object Server. It will provide up to 5 simultaneous connections.

Instructions

 Training (webinars and video-lessons) >> 

Start Your Work with iRidium

Setting up Connection to KNX

   1 How It Works: Ways of Connection to KNX
   2 Characteristic Features of Connection to KNX via the KNXNet/IP Tunneling Protocol
   3 Preparation of Data in ETS for Their Import in iRidium
       3.1 Preparation of Projects in ETS
       3.2 Import of Group Addresses from ETS to iRidium
       3.3 Creation of KNX IP Routers and Lists of Group Addresses in the Manual Mode
   4 Properties of Connection to KNX IP Routers
       4.1 Connection to KNX IP Routers in the Local Network
       4.2 Connection to KNX IP Routers via the Internet
       4.3 Switching Between the Local and Internet Connection
       4.4 Setting up Multiclient Connection to KNXnet/IP with the Help of iRidium Gate
       4.5 Setting up Multiclient Connection via KNXnet/IP through KNX IP BAOS
   5 Controlling KNX Group Addresses in iRidium Projects
       5.1 Driver Tokens
       5.2 Commands
       5.3 Feedbacks
   6 Emulation of Project Work
   7 Launching Projects on Control Panels

Examples of Controlling Equipment of the KNX Bus

   1 (1 bit) Relays, Shutters, Dry Contact, etc.
       1.1 (1 bit) On/Off by Separate Buttons
       1.2 (1 bit) Trigger Switch with One Button
       1.3 (1 bit) Displaying the Address State
       1.4 (1 bit) Controlling Several Addresses (for Shutters, Roller Blinds, etc.)
   2 (4 bit) Increment/Decrement for Lighting and Shutters (Control Dimming/Control Blinds)
   3 (8, 16, 32 bit) Dimmer, Climate Control and Other Information Variables
       3.1 (8, 16, 32 bit) Sending Values with Button
       3.2 (8, 16, 32 bit) Trigger Switch by One Button
       3.3 (8, 16, 32 bit) Controlling the Level Slider
       3.4 (8, 16, 32 bit) Increment/Decrement of the Current Address Value
       3.5 (8, 16, 32 bit) Color Picker - RGB Pallete for Light Control
       3.6 (Float 16, 32 bit) Displaying Values with Floating Point
    4 Scenes (Macros) in iRidium Projects for KNX
    5 Emulation of Project Work
    6 Launching Projects on Control Panels
    

Downloads

Control of equipment in the KNX bus (KNXnet/IP Tunneling), 1024x768, 3.1 Mb

Control of equipment in the KNX bus (KNXnet/IP Tunneling), 2048x1536, 3.2 Mb