Application program data sheet

Configuration

Select the configuration mode of the product:

• S-Mode without DCA: Select this option in case of a System Mode product without DCA
• S-Mode with DCA: Select this option in case of a System Mode product with DCA
• E-Mode
  • PB-Mode
  • Ctrl server mode
  • Ctrl client mode
  • LTE mode
• PC-tool via non-KNX connection: Select this option when the device can also be configured by means of an external software that is installed on a PC for which you need to connect to the device thereby using a UTP cable or a USB interface.   

Functional Block Compliance

KNX guarantees the compatibility and runtime Interworking independently of the configuration mode by fixing elementary functions in so-called Functional Blocks. Functional blocks group a number of inputs, outputs and parameters. If your product has a functionality for which there is a Functional Block, then it is indispensable that you select this Functional Block as per Volume 6/30/1 where you can find a list of all Functional Blocks for which one or more Functional Block profiles exist:

• Name: Select the Functional Block Name
• Profile: State to which profile flavors the Functional Block complies with: E.g. for FB Dimming Sensor Basic, Volume 7/20/1 states two possible profile flavors: number 1 and number 2. You have to state which one you comply with.

Note: Functional Blocks are only mandatory if there are so-called FB Profiles foreseen (e.g. in the case of dimming actuator, movement detector etc.). If there is no Functional Block profile foreseen, then you do not need to enter a Functional Block in the registration application.

For more information on the use of a Functional Block e.g. see FB Dimming Actuator Basic explained.

Implemented group address at delivery

Used Medium

Overview datapoint types

This overview contains a list of all implemented datapoints. This list is retrieved from the Manufacturer Tool project/*.knxei file. The manufacturer has to make sure that the “ComObjectsRefs” section contained in the Static part of the application program in the Manufacturer Tool is completed meticulously. The following guidelines are helpful when creating a product database: 

• In the MT Project: Select the correct Datapoint type by its main number and sub number, e.g.
  [1.1] DPT_Switch. Avoid using generic Datapoint types like e.g. 1.xxx (only to be used in cases when a group object can be used for several purposes).
• If the Datapoint selected is not supported by ETS, enter a generic “Datapoint type” and create a note thereby stating the correct datapoint type.
• Multiple different DPT main types may not be used for a group object. E.g. a group object with an unsigned value such as 7.001 (U16) AND a float value such as 9.001 (F16) at the same time.
• You can always provide additional information with regard to a group object, thereby adding useful information by using the “Actions” menu.

Original application

Binary code (S19, S28, S37)

• unchanged: application program contains fewer parameters/ fewer group objects:
  • No tests required at all, provided that the original application program has been tested successfully.
• unchanged: only new parameters (i.e., no dummy parameters) are added to an already certified binary image file:
  • Tests required: Conformity tests can be reduced to the full testing of the extended functionality and a random test of the unchanged part of the application program.
• unchanged: new parameters address other locations in an already registered binary image file
  • Complete retest required
• Other: If none of the above, state which changes the application program has undergone.

Reference application