OPEN SOURCE · WINDOWS

Your virtual
KNX installation.

Program push buttons, lighting actuators and sensors directly in ETS. Operate your installation and trace its bus telegrams without physical KNX hardware.

Illustrated demoLINE 1.1
FLOOR PLAN / APARTMENT (ILLUSTRATION)
Living room colour
TELEGRAM1.1.1 → 0/0/1 · Write · 1
THE REAL THING

This is vKNX.

The illustration above is a mock-up. These are pictures of the program itself, with devices that have been addressed and downloaded like real ones.

vKNX · FLOOR PLAN
vKNX floor plan with lamps, blinds and sensors, and a light control with a colour wheel opened on top of it

Your own floor plan with live symbols. Click a symbol to operate the device, here a light control screen with a colour wheel.

See all screenshots →
WORKFLOW

From ETS to lights on.

01 / INSTALLATION

Build the installation

Choose a push button and a switch actuator in vKNX. Import their product files into ETS and add both devices to your project.

02 / ETS

Program the devices

Link the push button and the actuator output with a group address. Press the programming button in vKNX, then download the individual address and application from ETS.

03 / SIMULATION

Trace the telegram

Press the button on the floor plan. Watch the output change, then find the sender, group address and value in the telegram monitor.

RECENTLY ADDED

Colour, presence and energy.

Light control with a colour wheel

The info display can now be a light control screen: on and off, brightness, and a colour wheel or a colour temperature. Together with the new colour dimming actuator it gives students RGB (DPT 232.600) and tunable white to work with in ETS.

Info display with a colour wheel next to a colour dimming actuator with an RGB and a white channel

Presence detector and energy meter

The presence detector switches the light on movement, with a follow-up time and a brightness threshold you can try from its card. The energy meter adds up the loads you give it and reports power, energy and current, with a limit that can raise an alarm.

Cards of a presence detector and an energy meter

A floor plan that is quicker to build

Select several symbols and align or distribute them, undo a mistake, and give each floor its own drawing. In use, a click on a symbol opens the device’s operating card right on the plan.

Floor plan in edit mode with three symbols selected and alignment buttons
FOR TEACHING

Made for the classroom.

NO HARDWARE

Every student has a full installation

vKNX runs on an ordinary Windows computer and shows up in ETS as a KNX interface. The devices are programmed the way real ones are.

SHARE

Hand out a finished installation

Export the devices with their addresses and ETS downloads, the floor plans and the icons as one .vknx file. The receiver opens it and can operate it, also without ETS.

SEE WHAT HAPPENS

Outputs, levels and telegrams

Cards and the floor plan show lamps, dimming levels and blind positions. The telegram monitor shows who sent what to which group address.

LINES AND COUPLERS

Topology that behaves like the real thing

Build several lines and areas with couplers. A telegram only crosses a coupler when the filter table ETS downloaded lets it through.

KNX DATA SECURE

Secure commissioning without the hardware

Two secure devices with a device certificate to type into ETS. Students see what changes when group telegrams are encrypted.

FLOORS

A building, not just a room

Up to eight floors, each with its own drawing. Place lamps, blinds, sensors and buttons where they sit in the building.

PRODUCT CATALOGUE

18 virtual
products.

The project’s teaching devices cover everything from a single lighting circuit to installations with multiple KNX lines.

Push buttons, lighting and blinds

  • Push button, 4 keysSwitching, dimming or blinds on each key.
  • Slider push buttonOn and off, plus a slider that sends a brightness value.
  • Switch actuatorSwitched outputs with status objects.
  • Dimming actuatorSwitching, relative dimming, brightness value and status.
  • Colour dimming actuator NewAn RGB channel and a tunable white channel.
  • Blind actuatorBlinds that move up and down to a position, with alarm inputs.

Sensors and room climate

  • Binary inputContacts and switches as inputs on the bus.
  • MultisensorMeasured values sent at an interval set in ETS.
  • Presence detector NewLight on movement, with follow-up time and brightness threshold.
  • Weather stationWeather values for alarms, for example to the blind actuator.
  • Room thermostatSetpoint, operating modes and a control value for heating.
  • Heating actuatorValve outputs driven by the thermostat’s control value.
  • Energy meter NewPower, energy and current, with a load limit.

Display, logic and topology

  • Info displayScreens with values from the bus, and a light control with a colour wheel.
  • Logic moduleLogic and timers built in an editor inside vKNX, plus a time master.
  • CouplerConnects lines and areas, with the filter table from ETS.

KNX Data Secure

  • Secure push buttonCommissioned with a device certificate; sends encrypted telegrams.
  • Secure switch actuatorIgnores plain telegrams to its secured group objects.
DOWNLOAD

Download vKNX

  1. Open the latest release on GitHub and download vKNX-Setup-x.y.z.exe (the installer; no administrator rights needed). Prefer not to install? Download vKNX-x.y.z-windows.zip, unzip it and run it.
  2. Windows may warn about an “unknown publisher”, because the program is not code-signed. Choose “More info”, then “Run anyway”.
  3. Start vKNX from the start menu and allow it through Windows Firewall on private networks, so ETS can find the interface. If the computer has no Microsoft WebView2, the installer downloads it during setup.
  4. Later, update from inside the program: cog icon, then “Check for updates”.
↓ Go to GitHub Releases
FAQ

Questions and answers

The things people run into most often, and what to do about them.

Why can’t I download to a device?

Go through these in order:

  1. In ETS the connection must be the vKNX interface. The status at the top of vKNX should say “Interface ready”.
  2. Windows Firewall must allow vKNX on private networks (port 3671, UDP and TCP).
  3. The interface line in vKNX (Settings → Interface for ETS) must match your ETS project. With several lines, see the question about lines and couplers below.
  4. The device needs its individual address first. See the next question.

The Installation view in vKNX shows a checklist for each device and hints about what ETS has just tried, for example “programming button not pressed”.

ETS cannot assign the address, or the device does not answer.

Press the programming button on exactly one device in vKNX. Its indicator turns red, and only that device answers ETS. Then choose “Program individual address” in ETS, and download the application afterwards.

ETS says the address already exists.

Another device, or the interface itself, already uses that address. Look at the device you have downloaded to and check the address on its card in vKNX. Then change the address in your ETS project to a free one and download again. The Installation view warns about duplicate addresses and about an address that equals the interface’s tunnel address.

The download fails because the APDU length is short (15).

ETS asks the interface how long telegrams may be. If it sees 15 instead of 254, ETS refuses downloads that need long telegrams. Versions before 0.12.1 could end up with 15 when the computer was busy while vKNX started. Update to the latest version (cog icon, then “Check for updates”).

If it still happens: restart vKNX, and open an issue on GitHub with vknx.log and console.log attached. They are in %LOCALAPPDATA%\vKNX\data. A line starting with [interface] in vknx.log shows when vKNX had to put the value back to 254.

I have several lines and couplers. What should the interface line be?

Set the interface to the main line. With lines 1.1, 1.2 and 1.3, choose 1.0 in Settings → Interface for ETS, and use the same topology in your ETS project. Then ETS reaches every line through the couplers.

Download the couplers first. A coupler filters group telegrams with the table ETS calculates, so a telegram that does not arrive on another line is often a missing entry in that table.

Are my addresses and downloads kept?

Yes. vKNX saves a device a few seconds after ETS has done something to it (an address, a download, a restart) and again when the program closes. After the next start the devices still have their addresses and downloads, also the KNX Data Secure ones, and ETS can continue with a partial download.

Only a forced stop in the middle of a download can lose its last few seconds. What is only live, such as a lamp being on, starts over.

Why does ETS list “KNX Association” as manufacturer?

vKNX uses a test manufacturer ID that ETS shows as KNX Association. The products are not made or certified by KNX Association. If an older vKNX version is already in the ETS catalogue and ETS complains when you import the new product files, remove the old vKNX entries from the catalogue first and import again.

Which ETS version do I need?

ETS 6, which is bought separately from KNX Association. The project author has tested with ETS 6.4.1. Other versions have not been tested.

Why does the monitor show “Unknown DPT”?

vKNX decodes values from the data types that the products declare. If a group address is used by devices with different types, or by no device at all (for example a telegram ETS sends to an address nobody uses), the monitor shows the raw bytes and “Unknown DPT”.

How do I give my students a finished installation?

In Settings → Share, choose “Export installation”. You get one .vknx file with the devices, their addresses and ETS downloads, the floor plan and the icons. The receiver opens Settings → Share, chooses “Import installation…”, sees what is in the file and confirms. The import replaces their whole installation, and their old one is saved as backup-before-import.vknx.

What is only live, such as lamps being on or the position of blinds, is not in the file. The file also contains the security keys of secure devices, and to change parameters or group addresses the receiver still needs your ETS project, so send it along.

Windows warns me when I install or start vKNX.

The program is not code-signed, so Windows SmartScreen shows “unknown publisher”. Choose “More info”, then “Run anyway”. The first start also asks for a firewall exception, which ETS needs to find the interface.

Can vKNX connect to a real KNX installation?

No. vKNX simulates the bus itself. ETS talks to it like to a KNXnet/IP interface, but nothing reaches physical KNX devices.

Still stuck? Open an issue on GitHub. Attach vknx.log and console.log, and the exact text of the ETS message if there was one.

GET STARTED

Your first installation

  1. Download the Windows installer from GitHub Releases, install it and launch vKNX.
  2. Open your ETS 6 project. Follow the project guide to prepare and import the product files (.knxprod).
  3. Select vKNX as the KNXnet/IP interface in ETS and program your first push button.
Open the ETS guide ↗