The user interface style has been reworked and shows a flat design.
Support of KNX Data Security Testing: EITT now supports the encoding and decoding of telegrams according to the application note 158 'KNX Data Security'.
For negative KNX Data Security tests, it is possible to set some security attributes as 'intentionally invalid'.
New Datapoint types: EITT now allows the creation of all Datapoint types specified in Volume 3/7/2.
Support of system conformance tests and data security tests: Based on templates provided by the KNX Association, EITT allows the user to create telegram sequences in accordance to the test specifications laid down in Volume 8 of the KNX Standard.
Support for bus load testing: EITT offers busload generator functionality in accordance with Volume 3/2/2 of the KNX Standard.
Automatic update of Datapoint specifications, busload templates, system conformance templates and handbook from the KNX server.
Change of bus driver: EITT now uses Falcon 5 instead of Falcon 2.
Support of direct USB Frame Testing: EITT now offers a new telegram type 'USB Frame'. This new telegram type can be used in telegram sequences to directly send or expect data from USB ports.
Introduction of 'Automatic Fields' in the 'Telegram Properties Window': To allow an easier change of BDUT and EDI addresses, EITT offers the option to enter the value 'automatic' as input for source address and destination address. During telegram sequence evaluation, EITT replaces these values by the automatic field values given by the user in the 'Automatic Fields' dialog (menu 'Options' → 'Automatic Values …'). Additionally the domain address and the serial number of a number of management telegrams can also be set by the automatic fields option.
Acceptance of multiple OUT telegrams in a cycle: If a cycle value * is entered for an OUT telegram, EITT accepts all occurrences of this telegram until the time to next period has expired. At least one telegram must be received in the given 'time to next' period.
For an IN telegram, it is now possible to enter a time period (format: hh:mm:ss) instead of a cycle number (e.g. 00:02:20, means 0 hours, 2 minutes and 20 seconds). If a time period is entered, EITT cyclically sends the IN telegram for the given time period with the time to next telegram send distance.
It is now mandatory to enter a comment, if a telegram in the trace buffer is set to MF or MP.
In the Connection Monitor, it is now possible to change the address of the locally connected BCU.
The trace buffer Search&Replace filter was extended. It is now possible to filter telegrams by a telegram number range.
The A_FunctionPropertyExtState_Response management telegram was reworked.
It is now possible to use wildcards for A.R.S in LTE telegrams: EITT allows entering the wildcard 0 for 'Appartment', 'Room' or 'Subzones' tags in LTE telegrams. The input of 0 is possible, when the following telegram attributes are selected:
The Automation API was extended by 3 new functions:
GetDataAsCSV2 allows exporting telegram sequences in a given format (parameter value 0 implies EITT3, value 1 EITT 4.2 and value 2 EITT 4.3).
SetCycleLimit2 allows setting the cycle limit value as string in the new format (*, time e.g. 00:02:30, cycle number).
ShowCommentCommandDialogs allows disabling / enabling the comment command dialogs.
A new function was introduced, which allows the user to reset all comments in a telegram selection by the default comment (menu 'Edit' → 'Reset Comments to Default Comment').
A new function was introduced, which allows the user to change the address type in a telegram selection. The address type change is available for management telegrams, DPT telegrams and non DPT telegrams (menu 'Edit' → 'Change Address Type to ...'). The following conversions are available: Address type to P2P connection oriented, to P2P connection less, to Group and to Broadcast (Group + Destination address 0). Attention: EITT changes the related telegram fields, even if the type change results in a FAULTY telegram!
EITT is now able to show the date of telegram reception in the tracebuffer (menu 'Trace ' → 'Telegram Style' → option 'Date').
The 'PC Options' dialog was extended: It is now possible to set the tracebuffer limit and the tracebuffer save path in the 'PC Options' dialog (instead of changing the corresponding registry value).
A new timing behavior has been added for telegram sequence evaluation: EITT version 4.3 and all previous versions use fixed time distances to send telegrams. These time distances are given by the 'Time To Next Telegram' value of a telegram to send. When a telegram has been sent by EITT, then EITT waits for the given time ('Time To Next Telegram' value of the telegram sent). When this time period has expired, EITT sends the next telegram, regardless if an acknowledge could be received or not. A new timing option modifies this interpretation of the 'Time To Next Telegram' value: The 'Time To Next Telegram' will only be taken into account when the acknowledge of the sent telegram was received by EITT or after a default timeout has expired. The default wait time is set to 3 seconds. The timing behavior (fixed time slots or variable after receiving ACK) can be selected in the option tree.
EITT evaluates a comment given by a comment command before evaluating the command (e.g. '@[w …' waits before sending the telegram). If the 'Time to Next Telegram' value of a telegram or a set of telegrams is 0, then all comment commands will be evaluated before sending / receiving the telegrams. Thus, in case of using the comment command '@[t', the telegram comments are not directly visible in front of the related telegram entry in the tracebuffer. EITT now allows to display the result of the comment command '@[t' directly in front the related telegram, even when used in a telegram bloc (with wait = 0). This new behavior can be selected in the option tree.
User Interface & Functionality
'F4' settings ('Select Telegrams' dialog) will be saved.
It is now possible to delete all inactive telegrams of a telegram sequence in one go (menu 'Edit' → 'Delete Inactive Telegrams').
The function 'Delete Media Info in Selection' now resets the 'Evaluate RF Info' field.
The Trace buffer Toolbar now contains a Print Layout Button.
The length of the recent file list was extended.
The function 'Delete media info' resets the 'Evaluate RF Info' field too.
Evaluation of RF Byte: The 'Route Last' flag can now be checked.
The connection name is displayed in the 'Raw Trace Window'.
The 'Time to next telegram' value in the print-out can be displayed after the telegram data instead of in front of the telegram data (menu 'View' → 'PDF/Clipboard Telegram Style' → dialog 'PDF/Clipboard Display Settings' → option 'Time after telegram'.
User Interface & Functionality
A bug was corrected related to MemoryExtendedWrite, MemoryExtendedWriteResponse and MemoryExtendedReadResponse telegrams with no data. These telegrams were converted to FAULTY telegrams after saving and reloading the .ctl file.
The bug where text 'Cancel' in some dialogs was changed into 'Abbrechen' is now corrected.