Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

To import the configuration of a KNX project into a management application like an OPC server, the ETS offers an export function called "Export OPC". This export functionality provides only basic information about the KNX installation.

The NETx BMS App Secure is a user-friendly way to import the entire KNX project and its meta-information into the NETx BMS Platform Core Server. The output of the NETx BMS App Secure for ETS is an enhanced export file that contains the used KNX group addresses, the deployed KNXnet/IP routers and interfaces, and the full ETS project structure including the network topology (areas, lines, devices, and communication objects) as well as the building and trade view.

In addition, the app detects the configured IP addresses of the KNXnet/IP routers and interfaces. For KNXnet/IP routers and interfaces that support KNXnet/IP Security, the necessary security configuration is exported, too. Based on the topology of the KNX project, the app automatically assigns the KNX group addresses to the respective routers and interfaces that are later used to access them. Thus, a manual, time-consuming and error-prone assignment of the KNX group addresses to the KNXnet/IP routers and interfaces is not necessary anymore. Using the NETx BMS App Secure, the entire KNX project including the well-known ETS view can be imported into the NETx BMS Platform Core Server in a fast and intuitive way.

All ETS apps have to be validated by the KNX Association. In addition, an ETS app can only be installed with a valid ETS license (ETS lite, ETS Pro or ETS Supplementary) – ETS apps cannot be used with the demo mode of ETS. The following steps explain how the NETx BMS App Secure can be installed within your ETS installation.

How does the NETx BMS App Secure work?

During the export, the app searches for all communication objects of all devices in all lines which are connected to KNX group addresses. The KNX group address is the identifier to communicate with the communication object. Since we use IP we also need to know the IP address of the KNXnet/IP router or interface that we have to use. So, to communicate with a communication object we need both the KNX group address and the IP address.

The ETS App automatically searches for routers and interfaces that have a static IP address set. It searches first in the KNX line where the group address is assigned. If no valid router or interface is found, it searches within the main line. If still nothing was found, it searches within the backbone. If there is also no router or interface with a static IP address, it will ask you to enter one. Here you have the opportunity to enter a new IP address or choose an existing router or interface.

This is the correct and most reliable way to import KNX data. Although the Core Server provides the BROADCAST gateway that sends to all gateways simultaneously, using the BROADCAST gateway should be avoided. The reason is that BROADCAST means “all KNXnet/IP routers and interfaces together”. This in turn means that if you send a telegram from OPC to a group address that is assigned to BROADCAST, the BMS server sends a group telegram to EACH gateway. If you have 50 gateways it will send 50 telegrams to each router. Since KNXnet/IP routers also forward telegrams between their lines (based on filtering), this generates a lot of traffic there. Therefore, BROADCAST should only be used if KNXnet/IP routing (routing between KNX lines) is not activated.

Installation

Get the NETx BMS App Secure and a license for free from my.knx.org and go through the installation process.

  1. Open the KNX online shop located at https://my.knx.org and log in with your KNX account. Use your KNX account name (starting with "KNX") and your password.
  2. Although our NETx BMS App Secure is free of charge, you have to "order" it within the KNX online shop. Change to the tab "Shop" and then to "ETS Apps". Locate our the NETx BMS App Secure within the list of available apps. The easiest way is to select the category "Project Export". Click on the "Buy" button to add it to your basket.
  3. Then click on the "basket" and press "Checkout" to start the ordering. Follow the instructions of the ordering wizard. As mentioned before, the NETx BMS App Secure is completely free of charge. However, you have to finish the ordering process to a valid NETx BMS App Secure license.


  4. After having finished the ordering process, change to the tab "My Products" and locate the NETx BMS App Secure within your product list. As next, download the ETS app installation package. This is done by clicking on the button "Download". You will get a file called "nxaETSBMSAppSecure.etsapp". Stored it on your hard disk.



  5. Install the ETS app to your ETS: Open the ETS and click on "Apps ... active" within the bottom right corner of the status bar of ETS. Within the list, click on the "+" button and select the installation packages "nxaETSBMSAppSecure.etsapp" that you have downloaded before.



  6. Although our NETx BMS App Secure is free of charge, a license has to be installed. This license is coupled to your ETS license. Therefore, it is only possible to use an ETS app if you have valid ETS license (lite, professional or supplementary).
    First, the dongle ID of your ETS license has to be determined. Open the ETS and click on "License ..." within the bottom right corner of the status bar of ETS. Within the license dialog, you will find your dongle ID (starting with "KNX- ..."). Copy the dongle ID to the clipboard by pressing the "copy" button and write down the dongle ID.



  7. Now, go back to KNX online shop which your web browser (log in again if you have been logged in meantime). Change to "My Account" and to the tab "My Products" and locate the NETx BMS App Secure within your product list. Within the column "Product License" paste in the dongle ID. Afterwards, click on the button "Add Key". This will generate a new license file which can be downloaded via the link that is named after your dongle ID. Download the ZIP file and extract it on your harddisk. You will get a file with the extension ".license".
  8. Now go back to your ETS. Click again on  "License ..." within the bottom right corner of the status bar of ETS. Within the license dialog, click on the "+" button and select the license file that you have downloaded before. If everything is working you will find a new entry "NETx BMS App Secure".
  9. Close the license dialog and click again on "Apps ... active" within the bottom right corner of the status bar of ETS. Within the apps list, you should find now our NETx BMS App Secure as active with a valid license.

Starting the NETx BMS App Secure

After installation and licensing of the NETx BMS App Secure, the NETx BMS App Secure should be available within your ETS. Open any ETS project and open the menu "Extras". Within this menu you will find a sub menu "NETxAutomation Software GmbH". Open the sub menu and select the entry "NETx BMS App Secure".

The user interface of our NETx BMS App Secure will be shown.

To learn how our NETx BMS App Secure can be used, please take a look at our tutorial KNX 1

Further information

Changelog

VersionDateNotes
1.0.0.9

TBD

Improvements

  • Unassigned KNX group addresses are exported as comments now
  • LaMPS Export: Support for Siemens gateways Twin plus N 141/21, plus N 141/03 and Twin N 141/31 with new firmware.
  • LaMPS Export: detected emergency lights are added to gateway device list now.

Fixes

  • Group addresses of devices with module configuration are not detected – fixed.
  • LaMPS Export: DPT mapping of Siemens KNX/DALI Gateway N 141/03, N 141/21, N 141/31 is faulty – fixed.
1.0.0.8

 

Improvements

  • LaMPS Export: Support for ABB DG/S 1.64.5.1 and ABB DG/S 2.64.5.1
  • LaMPS Export: Support for Theben DALI-Gateway KNX plus, DALI-Gateway S64 KNX and DALI-Gateway S128 KNX
  • Improved user message if no assigned group address is found.
  • Redesign of GUI selection options
  • Add project name to gateway location
1.0.0.7

 

Fixes

  • Manually added KNXnet/IP routers are not saved correctly – fixed.

Improvements

  • Added support for NETx MP Server
  • Group address assignment: normal KNX lines have a higher priority than main lines or backbone
  • Support for new Zennio KNXnet/IP routers and interfaces
  • LaMPS Export: Support for new Ipas, Schneider, Merten and MDT gateways
  • LaMPS Export: Support for Legrand gateways
  • LaMPS Export: Support for new application version of Siemens gateways
1.0.0.6

 

Improvements

  • LaMPS Export: Support for new Jung gateways
  • LaMPS Export: Support for Eelectron gateways
  • LaMPS Export: Support for HDL gateways
  • LaMPS Export: Support for B.E.G. gateways
1.0.0.5

 

New features
  • Support for Zennio IP routers and interfaces added

Fixes

  • LaMPS Export: assignment issue of KNXnet/IP routers fixed
  • Possible wrong selection for manually added KNXnet/IP routers and interfaces fixed
1.0.0.2

 

Improvements

  • LaMPS Export: Support for Siemens N141/02 added
  • Support for BMS Platform added

Fixes

  • LaMPS Export: Missing ABB DG/S x.64.1.1 DPT Mapping added
1.0.0.1

 

Fixes

  • LaMPS export: path for emergency mapping was missing
  • LaMPS export: missing DPT information for Siemens gateways

Improvements

  • LaMPS export: support for Zennio and EAE gateways added
  • LaMPS export: logging output for unused gateways added
1.0.0.0

 

New features
  • Export of Secure KNXnet/IP routers and interfaces
  • Export of KNX/DALI gateways for NETx LaMPS module




  • No labels