Note: Even if you can produce product data files at any time if the product data contains no errors, unless the product is registered it will not be possible to instantiate devices in ETS with this data. To test an unregistered product, use the Create ETS test project function.
To create a knxprod or vd* file
·If there is already a MT project containing all necessary data, the following steps can be skipped.
oCreate a new MT project
oAdd all required files to the project using the Add Existing Item command
§the mtxml files containing the application program, hardware and catalog descriptions, as well as any translations
§any baggage files
·Execute the Build » Build Solution command.
This will first do a complete check of the product data and then create the target file.
The output file is created in the subdirectory out of the project directory.
If any registration-relevant data has changed since the last knxprod/vd*/knxei export, during the Build new hash values are calculated and written to the *.mtxml file.
If an affected *.mtxml file is open, you will be prompted to re-load the file after the build.
If the project contains many *.mtxml files it is useful to close all open mtxml files before building the output file to avoid these prompts.
The build can be automated.