0% found this document useful (0 votes)
549 views17 pages

KNX Manager

The document provides instructions for configuring and programming Savant's KNX Building Management System integration tool. It discusses adding a KNX profile to a configuration, importing KNX datapoints from an ETS file, adding and programming KNX devices, and syncing the data table. The appendix includes an index of the KNX Manager windows and their functions.

Uploaded by

Shine Vasanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
549 views17 pages

KNX Manager

The document provides instructions for configuring and programming Savant's KNX Building Management System integration tool. It discusses adding a KNX profile to a configuration, importing KNX datapoints from an ETS file, adding and programming KNX devices, and syncing the data table. The appendix includes an index of the KNX Manager windows and their functions.

Uploaded by

Shine Vasanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Savant® KNX Manager

Programming Guide
Document Number: 009-1863-00
Document Date: July 2019
Document Supports: da Vinci 9.1 and higher

Copyright © 2019 Savant Systems, LLC 45 Perseverance Way, Hyannis, MA 02601


-1- Savant.com | 508.683.2500
Contents
To access links to the topics within this document, click the corresponding entry in the table below.

1. Introduction ......................................................................................................................3

2. Important Information ..................................................................................................3

3. Blueprint Configuration ...............................................................................................4


3.1. Add KNX Profile to a Configuration ...............................................................4
3.2. Import KNX Datapoints ......................................................................................5
3.3. Add Devices ............................................................................................................6
3.4. Programing an Entity ...........................................................................................7
Adding a sub-Action (Optional).......................................................................9
3.5. Sync Data Table ................................................................................................... 10

Appendix: KNX Manager Index............................................................................................ 11

Device Window ................................................................................................................... 11

Import Window ................................................................................................................. 12

Details Window ................................................................................................................. 13

Imported Data Window .................................................................................................. 16

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 2 of 17
1. Introduction
This guide details the use of Savant's KNX Building Management System (BMS) Integration tool. The KNX Manager allows direct mapping of KNX
datapoints to Savant States. This mapping allows many-to-one relationships. Multiple datapoints can be mapped to a single Savant State, and a single
Savant Action can report to multiple datapoints. The KNX Manager allows the user to import information from a .knxproj file or .xml exported file from
Engineering Tool Software (ETS).

2. Important Information

Control vs Feedback
Control (actions) and feedback (states) are generally sent and received at different KNX datapoints. This means that during programming, the Group
Addresses for the State and Action should be different for the same piece of information. All data must be provided by the KNX programmer for the site
prior to Savant integration.

Variable Shades
Some types of KNX controlled variable shades report states using a scale inverted from the Savant standard. Within Savant programming, a variable shade
state value of "0" indicates that the shade is all the way down/closed, with a value of "100" indicating all the way up/open. If the shades in the imported
KNX system are set to use "0" for up/open and "100" for closed/down, an "Inverted Variable Shade" entity type can be used within Savant programming so
that the Savant Pro App will report accurate shade position states.

HVAC in KNX
As with many other HVAC control protocols, heating and cooling in KNX are treated as two separate systems. However, with KNX they are generally
controlled using separate commands. In most cases, turning ON the heat does not automatically turn OFF the cool. For these types of systems, a sub-
action must be added to the main action to achieve desirable system behavior.

Feedback for Triggers


For KNX devices that will only provide feedback to Savant for use within a State Trigger, to display on a custom screen, or for any other custom
programming, the Generic device type should be used. This category is a catch-all for KNX data points that do not map directly to a currently supported
Savant service. Custom UI or State Trigger programming within RacePoint Blueprint will be needed for integration of anything using this device type.

Missing Data
When importing data from a KNX file, it is possible that some information may be missing. When entering datapoints into Savant programming, any
missing data must be acquired from the KNX programmer for the site before proceeding.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 3 of 17
3. Blueprint Configuration

3.1. Add KNX Profile to a Configuration


From an open Blueprint configuration do the following:
1. Click Show Library. 5. Place the KNX controller in the Layout window.
2. Search for KNX. 6. Select the KNX controller.
Components
7. Make Network connection to the KNX Controller.
All Components ? 8. A pop-up window appears, Enter the IP Address of the KNX
All Manufacturers All Control Types gateway.

KNX 2

Components TL Rating Comment


IP connections need host address
Generic
KNX (Dual Setpoint) [IP]
10.0.100.79
Generic
KNX (Single Setpoint) [IP]
Cancel OK
3. Select the KNX Profile to be used, and drag into a Global Zone.
Choose Single or Dual Setpoint to match the HVAC control
system on site. 9. Repeat these steps for each KNX gateway that the Savant Host will
4. Name the device. be communicating with.

Enter a unique name for the component

KNX Controller

? Cancel Create

IMPORTANT!
DO NOT use the KNX-Lighting profile. It will not work with the KNX Manager.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 4 of 17
3.2. Import KNX Datapoints
To import data from a KNX system, the .knxproj file or an exported .xml from the ETS is required.
After the the KNX profile(s) have been added to a configuration, do the following:
1. Place the .knxproj/.xml file to be imported on the Desktop. 7. Review the imported data.
2. Generate Services.
3. Go to Tools > Settings > KNX Manager, Lighting 0 Import as: Lighting device to Gateway: KNX Controller

or Switch Control 0/0

Click the KNX Manager Shortcut on the tool bar. KNX Manager Garage 0/0/1 1.001
7 8
4. Click Import. Basement 0/0/2 1.001

Switch Feedback 0/1

Dimming Control 0/2

Dimming Feedback 0/3

KNX Controller Scenes 0/4

Shades 1 Import as: Shade device to Gateway: KNX Controller

HVAC 2 Import as: HVAC device to Gateway: KNX Controller

9
Cancel Import Datapoints Create Devices

8. Set Gateway.
9. Click Import Datapoints.

Import

5. Browse to the Desktop and select the .knxproj/.xml file.


6. Click Import.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 5 of 17
3.3. Add Devices
This section shows how to add devices to the KNX Manager.
To add devices do the following:
1. Generate Services. 5. Select the device being added.
2. Go to Tools > Settings > KNX Manager, This example is adding Lighting switches.
or
Click the KNX Manager Shortcut on the tool bar. KNX Manager Single Setpoint HVAC
3. Select the KNX Controller. Dual Setpoint HVAC
4. Click the .
5 Lighting Switch
Lighting Dimmer
Lighting SCENE
KNX Controller
Shade
Variable Shade
Inverted Variable Shade

Generic device
6. Enter the number of devices of the selected type to add.

How many Lighing Switch devices would you like


to add?

Cancel OK

7. Click OK.
8. Repeat steps 3 through 6 for each type of device to be added to
4 the KNX Manager.

Import

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 6 of 17
3.4. Programing an Entity
This section describes how to program an entity using a Lighting Switch as an example. Other entity types may have more actions or states to be
programmed; follow the same steps for each action or state.
Once datapoints have been imported, the installer must review, correct, and enter all data for the integration to function as desired.
From an open Blueprint configuration, do the following:
1. Generate services.
2. Go to Tools > Settings > KNX Manager,
or
Click the KNX Manager Shortcut on the tool bar. KNX Manager
3. Import KNX datapoints.
IMPORTANT INFORMATION!
If the datapoints have already been imported, doing this again will NOT duplicate entires.
4. Use the disclosure triangles to open the desired section.
O’Sullivan Castle

6 Imports

Filter Imports:
KNX Controller Name Address

4 Lighting Basement
Garage
0/0/1
0/0/2
Switches - 0/0/3

5 Switch 1 -
Basement
0/0/4
0/1/1
Switch 2 Garage
-
7 0/1/2
0/1/3
Dimmers
- 0/1/4
Scenes Entry 0/2/1
Front Hall 0/2/2
Climate 0/2/3
Family Room

5. Select a device to enter data.


6. Click the disclosure triangle on the Imports.
7. Scroll though imported data to find the selected device.
NOTE: The list is ordered by Address.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 7 of 17
8. Name the device.
Name Address DPST ID PUID Type Description

Basement 10 0/0/1 1.001 P-0000-0_GA-3 25 Switching control address for actuator channel 1
Garage 0/0/2 1.001 P-0000-0_GA-4 26 Switching control address for actuator channel 2
- 0/0/3 1.001 P-0000-0_GA-5 27 Switching control address for actuator channel 3
- 0/0/4 1.001 P-0000-0_GA-6 28 Switching control address for actuator channel 4
Basement 0/1/1
0/1/2
1.001
1.001
13 P-0000-0_GA-8
P-0000-0_GA-7 29
30
Switching feedback of actuator channel 1
Switching feedback of actuator channel 2
Garage
- 0/1/3 1.001 P-0000-0_GA-9 31 Switching feedback of actuator channel 3
- 0/1/4 1.001 P-0000-0_GA-10 32 Switching feedback of actuator channel 4
Entry 0/2/1 5.001 P-0000-0_GA-11 33 Dimming control address for actuator channel C1
Front Hall 0/2/2 5.001 P-0000-0_GA-12 34 Dimming control address for actuator channel C2
Family Room 0/2/3 5.001 P-0000-0_GA-13 35 Dimming control address for actuator channel C3
Name Gateway Address Type Room
Basement 8 KNX Controller 1 Switch Basement 9
Actions

Group Address Value DPST


OFF 0/0/1 0 1.001
Action to switch the circuit OFF.

Group Address Value DPST


ON 0/0/1 1 1.001
Action to switch the circuit ON.

Group Address Value DPST


? 0/1/1 ? 1.001
Query the cicurit’s status.

States

Group Address Comparator Value DPST


OFF 0/1/1 is equal to 0 1.001
The circuit is considered to be OFF when the conditions are met.

Sync

9. Select the Savant User Zone.


10. Right-click the Control datapoint for the device in the imported data.
11. Select Set Data to OFF Action.
Set Data to ? Action
Set Data to OFF Action 11
Set Data to ON Action

Set Data to OFF State


Set Data to ON State
12. Repeat steps 10 and 11 for the ON Action.
13. Right-click the Feedback datapoint for the device in the imported data.
14. Select Set Data to ? Action.
15. Repeat steps 13 and 14 for the ON State and OFF State.
IMPORTANT!
–– The Query action uses the feedback address.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 8 of 17
Adding a sub-Action (Optional)
This section details additional steps for when the user experience requires more than one thing to be done in a single request. The example below
adds a sub-Action to turn off the Heat when the Cooling is turned on.
After the steps in the section above, do the following:
1. Right-Click on the heat control datapoint to be added to the COOL Action.
2. Select Add Data to COOL Action.
Set Data to ? Action
Set Data to SP Action
Set Data inside HEAT Action
Add Data to HEAT Action
Set Data to OFF Action
Set Data inside COOL Action
Add Data to COOL Action 2
Set Data to AUTO Action

Set Data to CT State


Set Data to SP State
Set Data to HEAT State
Set Data to COOL State
Set Data to OFF State
Set Data to AUTO State

NOTE: Adding an action will alway adds it to the end of the list.
3. Check/Enter
First Floot Fan (FB) the Value.
Name Gateway Address Type Room
First Floor T-Stat KNX Controller 1 Single Living Room

Actions

Group Address Value DPST


COOL 2/0/2 1 20.102
Action to set the HVAC Mode to COOL. 2/0/1 0 20.102

Group Address Value DPST


HEAT 2/0/1 1 20.102
Action to set the HVAC Mode to HEAT.

Group Address Value DPST


OFF 2/0/1 0 20.102
Action to set the HVAC Mode to OFF.

Group Address Value DPST


? 2/1/1 ? 20.102
Query the HVAC status. Generally include all feedback GroupAddresses. 2/1/2 ? 20.102
2/1/3 ? 20.102
2/1/4 ? 20.102

4. Repeat these steps for every Action that needs to have subAction(s) added.
IMPORTANT!
–– This also can be done with States. However if more than one item is listed, ALL must be true for the state to be set.
–– All feedback datapoints should be added to the Query action. For example: for a thermostat the query actions should contain the feedback
datapoints for HVAC Mode(s), Current Temperature, and Setpoint(s) so the start-up polling actions will populate all the states needed for the
system to display in the UI.
–– Sub-actions within an outgoing command are executed in order. For example, if heat Off should take place before cool On, ensure the sub-
actions are ordered accordingly.
Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 9 of 17
3.5. Sync Data Table
The process used to Sync a data table must be done separately for each data table that is being used (HVAC, Lighting, etc.).
Form an open Blueprint configuration do the following:
1. Generate Services.
2. Go to Tools > Settings > KNX Manager,
or
Click the KNX Manager Shortcut on the tool bar. KNX Manager
3. Use the disclosure triangles to open the desired section.
4. Select a device. This example uses Filter
a Imports:
lighting switch.
KNX Controller Name Address DPST ID PUID Type Description

Lighting Basement 0/0/1 1.001 P-0000-0_GA-3 25 Switching control address for actuator channel 1
Garage 0/0/2 1.001 P-0000-0_GA-4 26 Switching control address for actuator channel 2
Switches - 0/0/3 1.001 P-0000-0_GA-5 27 Switching control address for actuator channel 3

Basement 4 -
Basement
0/0/4
0/1/1
1.001
1.001
P-0000-0_GA-6
P-0000-0_GA-7
28
29
Switching control address for actuator channel 4
Switching feedback of actuator channel 1
Garage Garage 0/1/2 1.001 P-0000-0_GA-8 30 Switching feedback of actuator channel 2
- 0/1/3 1.001 P-0000-0_GA-9 31 Switching feedback of actuator channel 3
Dimmers
- 0/1/4 1.001 P-0000-0_GA-10 32 Switching feedback of actuator channel 4
Scenes Entry 0/2/1 5.001 P-0000-0_GA-11 33 Dimming control address for actuator channel C1
Front Hall 0/2/2 5.001 P-0000-0_GA-12 34 Dimming control address for actuator channel C2
Climate 0/2/3 5.001 P-0000-0_GA-13 35 Dimming control address for actuator channel C3
Family Room
Blinds Name Gateway Address Type Room
Basement KNX Controller 1 Switch Basement

Actions

Group Address Value DPST


OFF 0/0/1 0 1.001
Action to switch the circuit OFF.

Group Address Value DPST


ON 0/0/1 1 1.001
Action to switch the circuit ON.

Group Address Value DPST


? 0/1/1 ? 1.001
Query the cicurit’s status.

States

Group Address Comparator Value DPST


OFF 0/1/1 is equal to 0 1.001
The circuit is considered to be OFF when the conditions are met. 5

Import Imported Data Available Sync

5. Click Sync.
6. Review the Data Table.
7. Click Done.
8. Repeat steps 2 though 7 for each data table that needs to be synced.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 10 of 17
Appendix: KNX Manager Index

Device Window
Search allows the user to filter the entries by name, address (Virtual Address), or
A Search Bar
KNX Group Address.
A
B KNX Gateway(s) The KNX Gateway(s) placed in the configuration.
KNX Controller B List of devices/categories that have been added to the above KNX Gateway.
Lighting C Devices Device types include Lighting, Climate/HVAC, Shades/Blinds, and Generic (catch
all).
Switches
Add a device to the currently selected Gateway. A pop over menu (shown below)
Basement
with the currently available devices.
Garage Single Setpoint HVAC
C Dual Setpoint HVAC
Dimmers
Lighting Switch
Scenes Lighting Dimmer
D Add Device
Lighting SCENE
Climate
Shade
Blinds
Variable Shade
Inverted Variable Shade

Generic device

Remove the selected device(s). More than one device can be selected at once, but
E Remove Device
can not be used to remove an entire group (Lighting, HVAC, etc)
Import datapoints from an ETS file or an exported XML file from ETS. The import
process can attempt to automatically add Devices as they are found (based on
a singular format), and will provide KNX datapoint information for all devices
F Import Button
during each work session even if auto-creation for some devices fails. The user
can choose to skip the auto-creation of devices and simply import datapoints if
preferred. For more information see the Import Window section below.
An indicator displayed when there is imported KNX Datapoint information
G Data Indicator
available to view within the Imported Data window.

D E F G

Import Imported Data Available

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 11 of 17
Import Window
A Data Preview Displays the imported data for review
Lighting 0 Import as: Lighting device to Gateway: KNX Controller
Drop-down to select device type to
Switch Control 0/0 B Device Type
B C import as.
Garage 0/0/1 1.001 Select the KNX Gateway placed in the
A C Gateway Selection
Basement 0/0/2 1.001
configuration.

Switch Feedback 0/1 D Cancel Closes widow, clearing imported data.

Dimming Control 0/2 Imports the Datapoints into the KNX


E Import Datapoints
Manager.
Dimming Feedback 0/3
Creates device based on selections.
Scenes 0/4

F Create Devices IMPORTANT! This feature only works if


Shades 1 Import as: Shade device to Gateway: KNX Controller the data is in the exact format that this
tool expects.
HVAC 2 Import as: HVAC device
D E
to Gateway: KNX Controller
F

Cancel Import Datapoints Create Devices

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 12 of 17
Details Window
The name of the Device. What will show
Name Gateway Address Type Room
A Device Name
Basement A KNX Controller 1 Switch Basement
in the UI.
Actions
B C D DPST E The KNX Gateway the Device is assumed
Group Address Value B KNX Gateway
OFF 0/0/1 0 1.001
to be connected to.
Action to switch the circuit OFF.

G H I The Savant Entity address. The Virtual


C Savant Address
Group Address Value DPST
Address to be used for control
ON
F
0/0/1 1 1.001
Action to switch the circuit ON.
D Device Type The entity that will be controlled.

Group Address Value DPST The Savant User Zone this device is
? 0/1/1 ? 1.001 associated with. This is the location from
Query the cicurit’s status. E Room
which the device will be selectable within
States the UI.
J
The list of common Actions or States
Group Address Comparator Value DPST
OFF 0/1/1 is equal to 0 1.001

O
The circuit is considered to be OFF when the conditions are met.
P supported by this Device. For some
K L M N F Actions/States devices there are less common items that
Sync can be added. The lists can be collapsed
by using the disclosure triangle.
G Action Group Address Enter the addressing from imported data, or add manually based on information obtained from the site's KNX programmer.

H Action Value Enter the value that needs to be sent to the KNX Group Address for this action to be completed.

Enter the DataPointSubType (DPST) of the KNX Group Address. This determines how the data is written when the command is
I Action DPST
sent out.
Actions: Add or Remove a subAction or KNX Datapoint to be controlled when this Action is run. This can be useful for cases
J and Buttons where a single Savant Action must control more than one KNX Datapoint.
States: Add or Remove an additional KNX Datapoint to be evaluated to make the state true.
K State Group Address Enter the addressing from imported data, or add manually based on information obtained from the site's KNX programmer.

Describes how the value received for the Group Address will be evaluated by the Host to set the corresponding state value within
L Comparator Savant. If the logic evaluates to True, the state value within Savant State Center will match the value for the entry. In this example,
if the value for Group Address 0/1/1 is equal to 0, the state value within Savant State Center will be set to OFF.
M State Value Enter the value that needs to be found at the KNX Group Address for this state to be true.

Enter the DataPointSubType (DPST) of the KNX Group Address. This determines how the data is interpreted when the data is
N State DPST
received.
Add or Remove an Action or State supported by this Savant Entity. The list provided in the popover should be one word in the
O and Buttons
context of a UI element. See Additional Actions and States section for more information.
Sync the service currently highlighted in the Device List View with its respective Data Table. This will bring up the data table for
P Sync Button
any manual editing and confirmation of data.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 13 of 17
Additional Actions and States
The menus in this section are different based on the selected entity. All lighting entities have the same menu however they have different items that auto
populate based on which lighting entity. The options presented in this menu are determined based on the selected entity type, with different sets of possible
states and actions for Lighting Devices, Shade Devices, Generic Devices, and Climate/HVAC Devices.
While all entities of the same type will display the same menu options, specific devices within the same entity type will be auto-populated with different options
from that list. For example, a Lighting Switch will auto-populate different actions and states than a Lighting Dimmer. The same is true for Variable vs Non-
Variable Shades, etc.
The tables below show the menus for each entity type, describe the relevant actions and states, and provide details on their functions.

HELPFUL INFO
–– Options that are grayed out have already been added.
–– Some options presented for the entity type may not be valid for the individual selected device. For example, a SET action is not a valid action for a
Lighting Switch.

Lighting Devices Shade Devices

Add ? Action Add ? Action Query action Add ? Action Query action
Add ? Action
Add SET Action Sets the intensity of a Add SET Action Sets the level of a variable
Add SET Action Add INVERTEDSET Action Add SET Action
Add ON Action dimmable lighting load. shade.
Add OPEN Action
Add OFF Action Add INVERTEDSET Sets the level of a variable
Add ON Action Turns on a lighting switch. Add CLOSE Action
Add SCENE Action Add STOP Action Action shade with an inverted value.
Add OFF Action Turns off a lighting switch
Add LEVEL State Add LEVEL State Sends an OPEN command
Add INVERTEDLEVEL State
Add ON State Activate a single Scene Add OPEN Action to the shade, (generally this
Add OPENED State
Add OFF State Add SCENE Action defined in the KNX Add CLOSED State moves the shade up).
Add STATUS State programing. Add MOVING State
Add STOPPED State
Sends an CLOSED command
Add STATUS State Add CLOSE Action to the shade, (generally this
Add LEVEL State Shows current intensity of a dimmable load.
moves the shade up).
Conditions that must be met for the selected load to
Add ON State Add STOP Action Stops the shade at the current level while in motion.
be considered ON.
Shows the shade's current position on a standard
Conditions that must be met for the selected load to Add LEVEL State
Add OFF State scale of 0 (fully closed/down) to 100 (fully open/up).
be considered OFF.
Add INVERTEDLEVEL Shows the shade's current position on an inverted
Add STATUS State Text status for the load at the selected address.
State scale of 0 (fully open/up) to 100 (fully closed/down).

Generic Devices Add OPENED State The shade is considered to be Open.

Add CONTROL Sets the value of a custom Add CLOSED State The shade is considered to be Closed.
Action datapoint. Add MOVING State The shade is considered to be Moving.
Add CONTROL Action Queries the value of a Add STOPPED State The shade is considered to be Stopped.
Add ? Action Add ? Action
custom datapoint.
Add STATUS State Text status of the shade.
Add FEEDBACK State
Sets the value reported to
Add FEEDBACK State Savant State Center for a
custom datapoint.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 14 of 17
Climate/HVAC Devices

Add ? Action Add ? Action Query action Fan Mode is considered to be Auto when these
Add FANAUTO State
Add OFF Action conditions are met.
Add HEAT Action Sets the HVAC system to
Add OFF Action
Add COOL Action Off. Add FANCIRCULATE Fan Mode is considered to be Circulate when
Add AUTO Action
State these conditions are met.
Add EHEAT Action Sets the HVAC system to
Add FANON Action Add HEAT Action
Heat mode. System is considered to be in Emergency Heat
Add FANAUTO Action Add EHEAT State
Add FANCIRCULATE Action mode when these conditions are met.
Sets the HVAC system to
Add FANOFF Action Add COOL Action
Add FANSPEED Action Cool mode. Add SP State Setpoint reported by the HVAC system.
Add CP Action
Add SP Action Sets the HVAC system to Add CP State Cool Point reported by the HVAC system.
Add HP Action Add AUTO Action
Auto mode. Add HP State Heat Point reported by the HVAC system.
Add OFF State
Add HEAT State Sets the HVAC system to Current Temperature reported by the HVAC
Add EHEAT Action Add CT State
Add COOL State Emergency Heat Mode. system.
Add AUTO State
Add FANON State Sets the HVAC system Outside Temperature reported by the HVAC
Add FANOFF State Add FANON Action Add OT State
Add FANAUTO State
Fan mode to On. system.
Add FANCIRCULATE State
Add EHEAT State
Add FANAUTO Sets the HVAC system Add CH State Current Humidity reported by the HVAC system.
Add SP State Action Fan mode to Auto.
Add CP State Add OH State Outside Humidity reported by the HVAC system.
Add HP State Add FANCIRCULATE Sets the HVAC system
Add CT State
Action Fan mode to Circulate. Fan (G) Relay is considered Active when these
Add OT State Add GRELAYACTIVE State
Add CH State
conditions are met.
Sets the HVAC system
Add OH State Add FANOFF Action Add GRELAYNOTACTIVE Fan (G) Relay is considered Not Active when
Add GRELAYACTIVE State Fan mode to Off.
Add GRELAYNOTACTIVE State State these conditions are met.
Add W1RELAYACTIVE State Add FANSPEED Sets the HVAC system
Add W1RELAYNOTACTIVE State Action Fan Speed. Add W1RELAYACTIVE Heat (W1) Relay is considered Active when these
Add Y1RELAYACTIVE State
State conditions are met.
Add Y1RELAYNOTACTIVE State Sets the Cool Point. (Used
Add SPEED State Add CP Action Add W1RELAYNOTACTIVE Heat (W1) Relay is considered Not Active when
in Dual setpoint systems.)
State these conditions are met.
Sets the Set Point. (Used in Single setpoint
Add SP Action Add Y1RELAYACTIVE Cooling (Y1) Relay is considered Active when
systems.)
State these conditions are met.
Sets the Heat Point. (Used in Dual setpoint
Add HP Action Add Y1RELAYNOTACTIVE Cooling (Y1) Relay is considered Not Active
systems.)
State when these conditions are met.
System is considered to be Off when these
Add OFF State Speed value of the Fan reported by the HVAC
conditions are met. Add SPEED State
system.
System is considered to be in Heat mode when
Add HEAT State
these conditions are met.
System is considered to be in Cool mode when
Add COOL State
these conditions are met.
System is considered to be in Auto mode when
Add AUTO State
these conditions are met.
Fan Mode is considered to be On when these
Add FANON State
conditions are met.
Fan Mode is considered to be Off when these
Add FANOFF State
conditions are met.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 15 of 17
Imported Data Window
O’Sullivan Castle

Imports
A
Filter Imports:
B
Name Address DPST ID PUID Type Description

Basement 0/0/1 1.001 P-0000-0_GA-3 25 Switching control address for actuator channel 1
Garage 0/0/2 1.001 P-0000-0_GA-4 26 Switching control address for actuator channel 2
- 0/0/3 1.001 C P-0000-0_GA-5 27 Switching control address for actuator channel 3
- 0/0/4 1.001 P-0000-0_GA-6 28 Switching control address for actuator channel 4
Basement 0/1/1 1.001 P-0000-0_GA-7 29 Switching feedback of actuator channel 1
Garage 0/1/2 1.001 P-0000-0_GA-8 30 Switching feedback of actuator channel 2
- 0/1/3 1.001 P-0000-0_GA-9 31 Switching feedback of actuator channel 3
- 0/1/4 1.001 P-0000-0_GA-10 32 Switching feedback of actuator channel 4
Entry 0/2/1 5.001 P-0000-0_GA-11 33 Dimming control address for actuator channel C1
Front Hall 0/2/2 5.001 P-0000-0_GA-12 34 Dimming control address for actuator channel C2
Family Room 0/2/3 5.001 P-0000-0_GA-13 35 Dimming control address for actuator channel C3
Name Gateway Address Type Room

Window disclosure
A The window can be collapsed or expanded using this disclosure triangle.
triangle
This filter tool to minimize the amount of datapoint in the Imported Data Window. Enter text in this field to filter the displayed
B Filter Imported Data
datapoints based on Name, Address, DPST, ID, or Description.
Displays the KNX Datapoints imported using the Importer tool. Right-clicking on a datapoint will bring up a menu to insert that
C Imported Data
datapoint into an Action or a State with all data it has. Or use the data as a reference for manual entry.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 16 of 17
Important Notice

Disclaimer
Savant Systems, LLC. reserves the right to change product specifications without notice, therefore, the information presented herein shall not be construed
as a commitment or warranty.
Savant Systems, LLC. shall not be liable for any technical or editorial errors or omissions contained herein or for incidental or consequential damages
resulting from the performance, furnishing, reliance on, or use of this material.

Patents
Certain equipment and software described in this document is protected by issued and pending U.S. and foreign patents.
All products and services are trademarks or registered trademarks of their respective manufacturer.

Coypright
This document contains confidential and proprietary information protected by copyright. All rights reserved. Copying or other reproduction of all or parts
of this document is prohibited without the permission of Savant Systems.

Trademarks
© 2019 Savant Systems, LLC. All rights reserved. Savant, Savant App, TrueImage, Savant Host, Now You Can, RacePoint Blueprint, Single App Home,
TrueCommand, TrueControl, and the Savant logo are trademarks of Savant Systems, LLC.
AirPlay, Apple, AirPort Express, AirPort Extreme, Apple TV, Apple Remote Desktop, FireWire, iMac, iTunes, iPad, iPad mini, iPad Air, iPhone, MacBook, Mac
and OS X are trademarks or trade names of Apple Inc. iOS is a trademark of Cisco®. Android, Google, Google Play, and other Google marks are trademarks
of Google, Inc. Wi-Fi is a registered trademark of the Wi-Fi Alliance®. HDMI® is a trademark of HDMI Licensing, LLC. MOTU® is a registered trademark of
Mark of the Unicorn, Inc. Luxul is a registered trademark of Luxul Wireless. NETGEAR®, the NETGEAR Logo and ProSAFE are trademarks of NETGEAR, Inc.
Extreme™ is a trademark of Extreme Networks, Inc.
All other brand names, product names, and trademarks are the property of their respective owners.

Technical and Sales Support


Savant Systems, LLC is dedicated to providing prompt and effective support in a timely and efficient manner.
–– To contact Savant Support, access the Savant Customer Community and enter a support Case ticket.
–– To contact Savant Sales, visit Savant.com and select Contact Us to locate a local sales representative in your area.

Savant KNX Manager Programing Guide Copyright © 2019 Savant Systems, LLC
009-1863-00 | 190920 17 of 17

You might also like