This page is a
translated version of the page
KNX IP BAOS and the translation is 100% complete.
iRidium for Weinzierl KNX IP BAOS
a set of tools for creating interfaces for controlling KNX equipment when connecting to the bus via Weinzierl KNX IP BAOS interfaces.
The documentation was updated on 21.10.2021
Description
Weinzierl KNX IP BAOS 770/771/772/773/777 (Bus Access and Object Server) is a KNX IP interface which can work with the KNX bus on the level of datapoints - KNX Application Layer besides telegrams (KNXnet/IP).
Se up as Object Server, Weinzierl KNX IP BAOS with intermediate addresses (Datapoints) enable connection to the KNX bus via TCP/IP, at that BAOS serves as a server - communicates with the bus, receives and sends commands. And control panels connect to the server to send and receive data. Such mode of work makes load on the bus minimal and connection stable.
- BAOS 771 supports up to 250 datapoints (intermediate addresses for accessing the bus), BAOS 772 – up to 1000 datapoints, BAOS 773 – up to 250 datapoints, BAOS 777 - up to 2000 datapoints
- Object Server and datapoints are set up with the help of ETS
Advantages of work via KNX IP BAOS in the Object Server mode:
- Concurrent and stable connection of up to 5 control panels via TCP/IP
- The load on the bus decreases dramatically as KNX IP BAOS returns saved variable states without any additional requests to the bus
- No delay of reconnection which is typical for the majority of KNX IP interfaces when switching Wi-Fi access points or at connection losses.
Connection
Equipment configuration and settings required for iRidium to control KNX equipment via Weinzierl KNX IP BAOS interfaces.
Ways of connection to KNX
Different ways of connection to the bus provide different number of concurrently connected control panels: from one to the unlimited number. The number of concurrent connections is affected by your choice of the way of connection.
2. iRidium Server + KNX IP BAOS
1. KNX IP BAOS provides up to 5 concurrent connections to the KNX bus. It means control is posible from 5 tablets, smart phones or PCs at a time.
2. iRidium server together with KNX IP BAOS provides unlimited number of connections as control panels connect to the server via the iRidium, protocol and do not load the bus.
If you selected work using the BAOS protocol consider its features:
- When selecting the BAOS model make sure it supports the required number of datapoints (variables with the help of which you can control group addresses in the bus). Datapoints have to be activated only for those group addresses with which control panels will work:
- KNX IP BAOS 771 - up to 250 datapoints and up to 2000 group addresses
- KNX IP BAOS 772 - up to 1000 datapoints and up to 2000 group addresses
- KNX IP BAOS 773 - up to 250 datapoints and 10 clients
- KNX IP BAOS 777 - up to 2000 datapoints and up to 2000 group addresses
- To see the status of group addresses at project launch, tick "Read" in the properties of each address in ETS
- Set up Datapoints in advance as BAOS with Datapoints is a separate device in iRidium projects. If you set up group addresses and relate them to GUI first, then when you switch to work with Datapoints, you will have to repeate the process of relating
- Provide connection of not more than 5 control panels to one BAOS, if you use more than 100 Datapoints
- Remove all addresses you do not need to control from your iRidium project. If the address is available for writing only, remove Feedback of this address to decrease the load on the bus
- BAOS 771/772 have limitations for packet processing: TTL is not more than 16 hops between routers. BAOS 777 has a limitation of 64 hops. It is important when controlling BAOS via the Internet. If you need to connect to BAOS located in another city or country try to use BAOS 777, which will receive packets transferred through more than 16 routers (this number is very little if you connect to the remote system).
Contact iRidium technical support team to get more detailed recommendations.
Import of Group Addressed from ETS
iRidium can connect to the bus via KNX IP BAOS and interact with the bus devices via datapoints. A list of dataponits can be imported from ETS5 (*.knxpro) and added to your iRidium project all at once or partially. Reimport and update of datapoints settings are supported.
To import group addresses from ETS5 project (*.knxproj):
1 Start iRidium studio, create a project and open two side panels: IMPORTED DATA and DRIVERS TREE:
2 Find in the IMPORTED DATA panel the Import button and click it, select a file with *.knxproj resolution.
3 When the file is processed, enter synchronization settings of ETS file with the Drivers panel (can be left by default):
see Synchronization settingsof ETS file and KNX driver in iRidium. You can come back to synchronization settigns by clicking the "Settings" button in the import panel.
How flag analysis works: Flags of datapoints are analized and in the basis of their presence a decision is made to add a command and a feedback channel. Flags:
- Communication – neither a command nor a fedback channel is created without this flag;
- Read – it is not analyzed;
- Write – a feedback channel will be added;
- Transmit – a command will be added;
- Update – it is not analyzed.
4 When import is complete and synchronization parameters are entered add addresses to project (a driver of a corresponding type will be created for it):
All addresses or only a part of them can be added and placed in folders:
- To add all addresses from ETS file, drag'n'drop the file to the Drivers panel
- To add part of addresses from ETS file, move a folder with addresses or a group of addresses from the list using drag'n'drop
- Addresses can be added to folders at once. Create a folder in the driver, select the driver, click (+) on the Drivers panel, select "Add command/feedback folder". Drag'n;drop the selected addressed to the folder - commands and feedback channels of the selected addressed will be added to this folder.
Use the Synchronize button, to update addressed in the driver according to the synchronization settings (see settings in the Import panel) or grag'n'drop addresses to the drivers panel for partial synchronization.
5 To update a list of addresses after making changes in the ETS project, export a file from ETS and import it again - data will be united.
New addresses added from ETS file will be marked with the [new] label. Addressed deleted from the ETS file will be marked with the bucket label, they must be deletd from the driver by means of synchronization.
6 A file of ETS project does not store the address of KNX IP interface. Check that you entered the right IP-address of KNX IP interface:
Tools of IMPORTED DATA Panel
- Import – to add new ETS file to the import base or update the contents of the added file. ETS5 (*.knxproj) files are supported.
- Synchronize – to synchronize the file of ETS project with the corresponding driver in the panel. See synchronization settings by clicking a button (4). Synchronization can be done byt drag'n'dropping a file from the import panel on the driver
- Delete data of ETS project – to delete import data completely. It's impossible to delete data from a file partially
- Synchronization settings – parameters to synchronize data about group addresses between the import panel and the driver (see description of parameters in point 3 of the manual import)
- Update properties – to update settings of group addressed during synchronization
- Group address names – to update names
- Group address properties – to update types of data
- Add and delete – to add and delete group addresses during synchronization
- Add new group addresses from ETS file – to add new addresses to the driver
- Delete group addresses removed from file – to delete from the driver addresses that do not exist in ETS file (after confirmation)
- Object flags – analysis of flags of groups objects connected with a group address; analysis of BAOS group objects
- Analyze object flags to create command, feedback and read requests of Group addresses – on the basis of flag analysis only an available method to work with a group address will be added to the driver (comand to write in address, feedback channel to read the state of address, capability to request the state at project)
- Switching the basis of group addresses / BAOS datapoints. ETS file stores information about addresses and datapoints that are used in different drivers and support different methods of sorting
- Method to sort group addresses. Sorting like in ETS is supported: "Group addresses ", "Devices", "Building"
- Name field displays a list of group addresses gathered in folders accordning to selected method of sorting(6). Names are formed from three components: group address, name (like in ETS), all flags of connected group objects. Only address name is used name a command and a feedback channel in the driver
- Type field displays the subtype of a group address according to ETS. If the address is not connected with group objects it won't be added to a project and the type field remains unidentified (Unknown)
- Status field displays [new] sign next to addresses added after reimport of ETS file. It display the bucket sign next to addresses deleted from the ETS file but not yet deleted from the driver
- "Use" filed displays a sign showing if a command and a feedback channel of the corresponding address were created in the driver
Commands & Feedbacks
As a result we have two levels of KNX settings:
- KNX Router (Interface) - the driver, it contains the list of group addresses in the bus
- Commands и Feedbacks - the commands and feedbac channels which help to control the group addresses. Commands - group addresses available for writing, feedback channels - group addresses available for reading.
Commands and feedback channels have to be assigned to project graphic items to control equipment:
- Commands are assigned to graphic items indicating the value to be sent to the bus when clicking on the items
- Feedback channels are assigned to graphic items to display the state of the group address
To assign commands or channels to graphic items use the drag&drop
method.
Below you can see examples of commands to control different types of addresses.
Setting Connection to the bus
Select the connection settings by default. They can be changed while working with the project.
Local connection:
- Host - the KNX IP BAOS IP-address (IPv4)
- Port - the TCP port of connection to the BAOS interface: 12004
- Update time (ms) - the frequency of sending the Ping command for checking the connection with the router. By default: 0, the application determines the request frequency automatically. At manual setting it is recommended to indicate not less than 5000 ms.
Internet and Network Interconnection:
- Host - the public IP-address of the Internet router
- Port - the TCP port of connection to the KNX interface. It has to be available from the Internet, so set up port forarding with the help of the Port Forwarding service of the Internet router
- Update time (ms) - the frequency of sending the Ping command for checking the connection with the router. By default: 0, the application determines the request frequency automatically. At manual setting it is recommended to indicate not less than 5000 ms.
Change of connection settings
Possibility to change connection parameters is required if you leave the Wi-Fi network of the object and start using 3G or another Wi-Fi network. To continue controlling a project, a switch is required from a local to a public IP-address of the internet router.
The switch does not happen automatically, you have to press a button to select a connection mode. For remote control of the system, ports to control the automation system must be made public. To do it Port Forwarding is set on the internet router, Protected connection can be provided by VPN.
1 Download the template (*.js) (right-click button: "Save object as ..."), add the template in the script editor with the button (+) Add Script from file
2 Set script properties as it is shown in the example:
function Internal_1() {
IR.GetDevice("KNX IP BAOS 771/772").SetParameters({Host: "192.168.0.100", Port: 12004, Login: "", Password: "",
UpdateTime: 30000});
}
function External_1() {
IR.GetDevice("KNX IP BAOS 771/772").SetParameters({Host: "215.110.10.10", Port: 12004, Login: "", Password: "",
UpdateTime: 30000});
}
Copy the driver name from the Projeсt Device Panel - a list of properties must be copied from the example.
3 Choose a button that will switch between Internal и External parameters. Open Macros Editor
for the Release event (Programming > Release), chose the Script Call
command and add it with a double click. Choose the name of the function that the button will call:
Now a corresponding set of connection settings will be applied each time when the button is pressed.
Sending commands
Without iRidium Server commands will be sent directly to the KNX bus when clicking on graphic items of the visualization interface. Each control panel connects to the bus individually.
To send commands to the KNX bus, you need to create a graphic interface for your control panel. The interface consists of pages, popups and graphic items, see basic concepts for creation of graphic interfaces.
To simplify your work use interface templates.
To control equipment, set commands (Commands) and feedback channels (Feedbacks). To send a command, drag'n'drop it on a graphic item and enter a value (Value) to be sent. To display feedback, drag'n'drop a feedback channel and enter where the value (Value) must be output.
Below you can see types of group addresses supported by iRidium and settings of graphic items to control these types of addresses:
KNX Type: 1.1-bit
Command:
Type |
1.1-bit |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0 / 1
|
1.001 Switch |
0 = Off, 1 = On
|
0 / 1
|
1.002 Bool |
0 = False, 1 = True
|
0 / 1
|
1.003 Enable |
0 = Disable, 1 = Enable
|
0 / 1
|
1.004 Ramp |
0 = No ramp, 1 = Ramp
|
0 / 1
|
1.005 Alarm |
0 = No alarm, 1 = Alarm
|
0 / 1
|
1.006 Binary Value |
0 = Low, 1 = High
|
0 / 1
|
1.007 Step |
0 = Decrease, 1 = Increase
|
0 / 1
|
1.008 Up/Down |
0 = Up, 1 = Down
|
0 / 1
|
1.009 Open/Close |
0 = Open, 1 = Close
|
0 / 1
|
1.010 Start/Stop |
0 = Stop, 1 = Start
|
0 / 1
|
1.011 State |
0 = Inactive, 1 = Active
|
0 / 1
|
1.012 Invert |
0 = Not inverted, 1 = Inverted
|
0 / 1
|
1.013 DIM Send Stype |
0 = Start/Stop, 1 = Cyclically
|
0 / 1
|
1.014 Input Source |
0 = Fixed, 1 = Calculated
|
0 / 1
|
1.015 Rest |
0 = No action (dummy), 1 = Reset command (trigger)
|
0 / 1
|
1.016 Ack |
0 = No action (dummy), 1 = Acknowledge command (trigger) e.g. for alarming
|
0 / 1
|
1.017 Trigger |
0, 1 = Trigger
|
0 / 1
|
1.018 Occupancy |
0 = Not occupied, 1 = Occupied
|
0 / 1
|
1.019 Window/Door |
0 = Closed, 1 = Open
|
0 / 1
|
1.021 Logical Function |
0 = OR, 1 = AND
|
0 / 1
|
1.022 Scene A/B |
0 = Scene A, 1 = Scene B
|
0 / 1
|
1.023 Shutter Blinds Mode |
0 = only move Up/Down mode (shutter), 1 = Move Up/Down + Step/Stop mode (blind)
|
0 / 1
|
1.100 Coolinig/Heating |
0 = Coolinig, 1 = Heating
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to a command. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 2.1-bit controlled
Command:
Type |
KNX Type: 2.1-bit controlled |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0, 1
|
all
|
No Control
|
2
|
all
|
Control. Function Value 0
|
3
|
all
|
Control. Function Value 1
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items.
KNX Type: 3.3-bit controlled
Command:
Type |
3.3-bit controlled |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0
|
all
|
Stop
|
1
|
all
|
100% Decrease (Down)
|
2
|
all
|
50% Decrease (Down)
|
3
|
all
|
25% Decrease (Down)
|
4
|
all
|
12,5% Decrease (Down)
|
5
|
all
|
6,25% Decrease (Down)
|
6
|
all
|
3,125% Decrease (Down)
|
7
|
all
|
1,56% Decrease (Down)
|
8
|
all
|
Stop
|
9
|
all
|
100% Increase (Up)
|
10
|
all
|
50% Increase (Up)
|
11
|
all
|
25% Increase (Up)
|
12
|
all
|
12,5% Increase (Up)
|
13
|
all
|
6,25% Increase (Up)
|
14
|
all
|
3,125% Increase (Up)
|
15
|
all
|
1,56% Increase (Up)
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items.
KNX Type: 4.Character
Command:
Type |
4.Character |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0...255
|
ISO_8859_1
|
send ASCII symbol, see the table.
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
HEX values received from the table have to be brought to the decimal fromat and sent with the help of the button.
KNX Type: 5.8-bit unsigned value
Command:
Type |
5.8-bit unsigned value |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0...255
|
VALUE, PERSENT, DECEMINAL FACTOR
|
a value from the range
|
0...100
|
5.001 Percentage (0..100%)
|
(%) a re-calculated value
|
0...360
|
5.003 Angle
|
angle
|
0...255
|
5.004 Percentage (0..255%)
|
a value from the range
|
0...255
|
5.005 Ratio
|
a value from the range
|
0...255
|
5.006 Tariff
|
a value from the range
|
0...255
|
5.010 Counter Pulses
|
a value from the range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
Subtype ASCII and ISO-8859_1 see in description of KNX Type: Character
KNX Type: 6.8-bit signed value
Command:
Type |
6.8-bit signed value |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
-128...127
|
all
|
controlling the range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 7.2-byte unsigned value
Command:
Type |
7.2-byte unsigned value |
a type of KNX group address
|
Subtype |
several values |
asubtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0...65535
|
all
|
controlling the range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 8.2-byte signed value
Command:
Type |
8.2-byte signed value |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
-32768...32768
|
all
|
controlling the range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 9.2-byte float value
Command:
Type |
9.2-byte float value |
a type of KNX group addresses
|
Subtype |
several values |
a subtype of KNX group addresses
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
-273... 670433
|
9.001 Temperature C
|
control of temperature
|
-671088... 670433
|
9.002 Temperature Diff, 9.003 Kelvin/Hour
|
(K, K/h) control of temperature
|
0... 670433
|
9.004 Lux, 9.005 Speed, 9.006 Pressure, 9.007 Humidity, 9.008 Air Quality
|
control of a range
|
-671088... 670433
|
9.010 Time 1, 9.011 Time 2, 9.020 Voltage, 9.021 Current, 9.022 Power Depensity, 9.023 Kelvin/Percent, 9.024 Power, 9.025 Volume Flow, 9.026 Rain Amount
|
control of a range
|
-459... 670433
|
9.027 Temperature F
|
control of temperature
|
0... 670433
|
9.028 Wind Speed
|
contro of fan speed
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 10.Time, 11.Date
Command:
Type |
10.Time, 11.Date |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
DD Month YYYY 00:00:00
|
Date
|
date control in the KNX bus (day month year hours: minutes: seconds)
|
00:00:00
|
Time
|
time control in the KNX bus (hours: minutes: seconds)
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
Sending date and time values is done only with the help a special script (see the attached example). The argument for sending time or date is a copy with Date object, If the driver is used in a server project, data and time can not be sent via the web-interface.
KNX Type: 12.4-byte unsigned value
Command:
Type |
12.4-byte unsigned value |
a type of KNX group address
|
Subtype |
12.001 Value |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0...4294967295
|
12.001 Value
|
controlling the range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 13.4-byte signed value
Command:
Type |
13.4-byte signed value |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
-2147383648 ... 2147483647
|
all
|
controlling the range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 14.4-byte float value
Command:
Type |
14.4-byte float value |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
3,4E–38 ... 3,4E+38
|
all
|
control of a range
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 16.Character string
Command:
Type |
16.Character string |
a type of KNX group address
|
Subtype |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
KNX is OK
|
16.000 ASCII, 16.001 ISO 8859-1
|
send a string up to 14 symbols (ENG), up to 7 symbols (RUS)
|
* - enter it when drag'n'dropping a command on a graphic item.
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 17.Scene Number
Command:
Type |
17.Scene Number |
a type of KNX group address
|
Subtype |
17.001 Scene Number |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0...63
|
17.001 Scene number
|
activate the scene
|
* - indicate when drag'n'dropping the command on a graphic item
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 18.Scene Control
Command:
Type |
18.Scene Control |
type of KNX group address
|
Subtype |
18.001 Scene Control |
subtype of KNX group address
|
Command |
Activate the scene (1-64)
Learn the scene (1-64)
Action + scene number (0-63/128-191)
|
parameter for new projects, it activates the scene
parameter for new projects, it learns the scene
deprecated parameter for old projects, it activates / learns the scene
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Command |
Assigning
|
0...63
|
Action + scene number (0-63/128-191)
|
to activate the scene from 1 to 64 (scene numbering starts from 0, scene 1 = 0, scene 64 = 63)
|
128...191
|
Action + scene number (0-63/128-191)
|
to learn the scene from 1 to 64 (scene numbering starts from 128, scene 1 = 128, scene 64 = 191)
|
1...64 |
Activate the scene (1-64) |
to activate the scene from 1 to 64 (scene 1 = 1, scene 64 = 64)
|
1...64 |
Learn the scene (1-64) |
to learn the scene from 1 to 64 (scene 1 = 1, scene 64 = 64)
|
* - indicate when drag'n'dropping the command on a graphic item
To activate a scene when using the "Action + scene number (0-63/128-191)" command, the scene number is indicated with shift of -1, i.e. to activate scene 1 you need to send 0, to activate scene 8 you need to send to 7, to activate scene 64 you need to send to 63.
To learn a scene when using the "Action + scene number (0-63/128-191)" command, the scene number is indicated starting from 128, i.e. to learn scene 1 you need to send 128, to learn scene 7 you need to send 134, to learn scene 64 send 191.
To activate a scene when using the "Activate the scene (1-64)" command, the scene number is indicated without shifting, i.e. to activate scene 1 you need to send 1, to activate scene 8 you need to send 8, to activate scene 64 you need to send 64.
To learn a scene when using the "Learn the scene (1-64)" command, the scene number is indicated without shifting, i.e. to learn scene 1 you need to send 1, to learn scene 8 you need to send 8, tk learn scene 64 you need to send 64.
Feedback:
The settings are similar to commands. Values come to Feedback and they can be used to display the status of registers on items
KNX Type: 20.1-byte
Command:
Type |
20.1-byte |
a type of KNX group address
|
Sub Type |
several values |
a subtype of KNX group address
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints)
|
Value * |
Subtype |
Assigning
|
0...2
|
20.002 SCLO Mode/Building Mode/Occupied |
0 - the building is used, 1 - the building is not used, 2 - the building is secured.
|
0...3
|
20.004 Priority |
0 - high priority, 1 - middle priority, 2 - low priority, 3 - "empty".
|
1...3
|
20.007 Alarm Class |
1 - a simple alarm signal, 2 - the main alarm signal, 3 - a widened alarm signal.
|
0...18
|
20.011 System Error Class |
0 - no error, 1 - general device malfunction, 2 - communication error, 3 - a connection error, 4 - a hardware error, 5 - a software error, 6 - non-volatile memory is not enough, 7 - volatile memory is not enough, 8 - a command to provide 0-size memrory is received, 9 - CRC-error, 10 - reset of watchdog is detected, 11 - an unacceptable operation code is detected, 12 - general security malfunction, 13 - the max length of the table is exceeded, 14 - an indefinite download command is received, 15 - a table of group addresses is not sorted, 16 - an unacceptable connection number (TSAP), 17 - an unacceptable number of the object of the group (ASAP), 18 - a type of the object of the group exceeds (PID_MAX_APDU_LENGT H - 2).
|
0...4
|
20.012 HVAC Error Class |
0 - no malfunction, 1 - a sensor malfunction, 2 - a hardware malfunction / controller malfunction, 3 - an actuator malfunction, 4 - another malfunction.
|
0...12
|
20.014 Beaufort Wind Force Scale |
a scale of wind speed
|
0...4
|
20.102 HVAC Mode |
0 - Auto, 1 - Comfort, 2 - Standby, 3 - Economy, 4 - Building Protection.
|
0...4
|
20.103 DHW Mode |
0 - Auto, 1 - LegioProtect, 2 - Normal, 3 - Reduced, 4 - Off/FromProtect.
|
0...2
|
20.104 Load Priority |
0 - нет, 1 - change download priority, 2 - an absolute download priority.
|
0...17, 20
|
20.105 HVAC Control Mode |
0 - Auto, 1 - Heat, 2 - Morning Warmup, 3 - Cool, 4 - Night Purge, 5 - Precool, 6 - Off, 7 - Test, 8 - Emergency Heat, 9 - Fan only, 10 - Free Cool, 11 - Ice, 12 - Maximum Heating Mode, 13 - Economuc Heat / Cool Mode, 14 - Dehumidification, 15 - Calibration Mode, 16 - Emergency Cool Mode, 17 - Emergency Steam Mode, 20 - NoDem.
|
0...5
|
20.106 HVAC Emergency Mode |
0 - Normal, 1 - EmergPressure, 2 - EmergDepressure, 3 - EmergPurge, 4 - EmergShutdown, 5 - EmergFire.
|
0...2
|
20.107 Changeover Mode |
0 - Auto, 1 - CoolingOnly, 2 - HeatingOnly.
|
1...5
|
20.108 Valve Mode |
1 - A heating step, 2 - B heating step for 2-step heating (A+B), 3 - A cooling step, 4 - B cooling step for 2-step cooling (A+B), 5 - heating / cooling for apps.
|
1...4
|
20.109 Damper Mode |
1 - Fresh air, 2 - Supply air, 3 - Discharge air, 4 - Extract air.
|
1...3
|
20.110 Heater Mode |
1 - Heat Stage A On/Off, 2 - Heat Stage A Proportional, 3 - Heat Stage B Proportional.
|
0...2
|
20.111 Fan Mode |
0 - the fan does not work, 1 -the fan works all the time, 2 - the fan works in intervals.
|
0...2
|
20.112 Master/Slave Mode |
0 - autonomous, 1 - master, 2 - slave.
|
0...2
|
20.113 Status Room Setpoint |
0 - a normal setpoint, 1 - an alternative setpoint, 2 - building security setpoint.
|
1...2
|
20.120 ADA Type |
1 - Air Damper, 2 - VAV.
|
0...1
|
20.121 Backup Mode |
0 - a backup value, 1 - save the last state.
|
0...2
|
20.122 Start Synchronization |
0 - the position has not changed, 1 - closing, 2 - opening.
|
* - enter it when drag'n'dropping a command on a graphic item
Feedback:
The settings are similar to a command. Values come to Feedback and they can be used for displaying the status of registers on items
KNX Type: 229.*4-1-1 byte combined information
Command:
Type |
229.*4-1-1 byte combined information |
a type of KNX group address.
|
Subtype |
229.001 metering value(value, encoding, cmd) |
a subtype of KNX group address.
|
Units |
energy, 0.001 Wh |
a measure unit.
|
Alarm un ack |
false/true |
the alarm status of the object is not confirmed.
|
In alarm |
false/true |
the object is in the alarm status.
|
Overriden |
false/true |
the main value is declined.
|
Fault |
false/true |
the main value is damaged due to a failure.
|
Out of service |
false/true |
the value is not serviced.
|
Address |
1/1/1 |
KNX group address (Address: 1 -for BAOS Datapoints).
|
Value * |
Subtype |
Assignment
|
-2147483648 ... 2147483647 |
001 metering value(value, encoding, cmd) |
control of a range.
|
* - enter it when drag'n'dropping a command on a graphic item.
Feedback:
Type |
229.*4-1-1 byte combined information |
a type of KNX group address.
|
Subtype |
229.001 metering value(value, encoding, cmd) |
a subtype of KNX group address.
|
Address |
1/1/1 |
KNX group address (Address: 1 - for BAOS Datapoints).
|
Value |
Result view |
Assignment
|
-2147483648 - 2147483647 |
Count value |
received value.
|
Value |
Units |
a measure unit.
|
0-1 |
Out of service |
the value is not serviced.
|
0-1 |
Fault |
the main value is damaged due to a failure.
|
0-1 |
Overriden |
the main value is declined.
|
0-1 |
In alarm |
the object is in the alarm status.
|
0-1 |
Alarm un ack |
the alarm status of the object is not confirmed.
|
KNX Type: 232.3-byte colour RGB
Command:
Type |
232.3-byte colour RGB |
a type of KNX group address.
|
Subtype |
several values |
a subtype of KNX group address.
|
Address |
1/1/1 |
KNX group address (Address: 1 - для BAOS Datapoints).
|
Value * |
Result view |
Assignment
|
0...16777215 |
Full |
change the color.
|
0...255 |
Red, Green, Blue |
change the color partially.
|
* - enter it when drag'n'dropping a command on a graphic item.
Feedback:
The settings are similar to the command. Values come to Feedback and they can be used to display the status of registers on items
KNX Type: 251.* Colour RGBW
Command:
Type |
251.* Colour RGBW |
a type of KNX group address.
|
Subtype |
251.600 RGBW value 4x(0..100%) |
a subtype of KNX group address.
|
Value param |
Ceil, Partial |
change the color value (completely / partially).
|
Red information |
Valid / Invalid |
use / do not use the value when forming a color.
|
Green information |
Valid / Invalid |
use / do not use the value when forming a color.
|
Blue information |
Valid / Invalid |
use / do not use the value when forming a color.
|
White information |
Valid / Invalid |
зuse / do not use the value when forming a color.
|
Color part |
Red, Green, Blue, White |
choice of values to change the color partially.
|
Address |
1/1/1 |
group address KNX (Address: 1 - for BAOS Datapoints).
|
Value * |
Value param |
Assignment
|
0...16777215 |
Ceil |
change the color.
|
0...255 |
Partial |
change the color partially.
|
* - enter it when drag'n'dropping a command on a graphic item.
Feedback:
The settings are similar to the command. Values come to Feedback and they can be used to display the status of registers on items
Emulator: Project Testing
Emulator is an application launched in iRidium Studio to test project work.
The Emulator works only after authorization with a login and password from iRidium Mobile website.
The modes of Emulator work is set in Tools > Options > Emulator:
- Show log at Emuator Start opens the log window automatically (otherwise the log can be opened by pressing F4).
Hot keys:
- F4 - open the debug log
- F5 - launch Emulator
- F7 - open a Menu to manage the account and projects
- F8 - open system settings (password: 2007)
Synchronization with Control Panels
Upload and launch of the iRdidium project on the control panel is performed with the help of the iRidium Transfer application, installed on your PC. You can also upload the project on the panel from the editor via Transfer.
Use i3 pro for iOS, Android, Windows, Mac in Test Mode by downloading projects via iRidium Transfer (the possibility is available for integrators):
Emulator
iRidium for Windows
iRidium for iOS
iRidium for Android
iRidium for Mac
iRidium Transfer settings
Commercial use of iRidium is possible only at download of visualization projects with the help of the iRidium Cloud service on the iRidium Mobile web site (see the instructions).
iRidium Cloud can be set up only by a registered integrator. After the setting up he can invite end-users to control the automation object.