File → Export to translator → Functional data…
![]() | In order to import the configuration created in T.A.P.P.S. into the respective controller, the logical circuit diagram in the drawing must be converted to a respective data format (functional data). |
![]() | For faulty or invalid links in the drawing, the error log is displayed with a respective error message. Functional data can only be created when all links are valid and complete. |
Operating system A2.28 should preferably be used for older UVR1611 units (serial number < 41674 and factory operating system < A3.00). An operating system A3.xx should only be used with these units if this is absolutely necessary, i.e. when the functionality of this new version is required. In particular, A3.xx operating systems cause a markedly slower reaction time with older units during operation.
So that TAPPS can be used to produce function data for the current operating system as well as for version A2.28, the minimum requirements (operating system and serial number) are determined for the function data generated from the drawing and displayed in the compiler window.
Before functional data (*.dat) is created by the compiler, the path and the name of the target file can be changed. Contrary to the drawing, the file name may be longer than 8 characters. The selected target path is also used as the basic setting for future projects.
Basic settings for the CAN network (node number, enable, etc.), which could already have been made during parameterizing of the network variables or the CAN data logging.
The selected file is created from the logical circuit diagram in the drawing. This file includes the configuration in a data format with corresponds to the controller. This functional data (*.dat) can subsequently be imported into the UVR1611with the help of the Memory Manager program and a Bootloader.
Once the functional data have been successfully created, the program window can be closed.