Functionality and Use Andreas Espen, Agentilo GmbH.

Functionality and Use Andreas Espen, Agentilo GmbH

EITT – Contents EITT – Intended use EITT – Test project
EITT – Main components Pixit Header: contents and functions Telegram Sequences Work flow: How to create a telegram sequence How to configure bus connections Overview of Telegram Types Telegram attributes and sequence configuration Tracebuffer: contents and functions Advanced topics Support of RF testing Support of KNX data security Automation API Planned development

EITT – Aim of the software
EITT may be used for: 1. Test of compatibility of KNX devices against KNX Interworking requirements, i.e. first and foremost the KNX standardized data types (Volume 8/7/1) (in case of new stack/system developments) KNX OSI layer requirements (rest of Volume 8) 2. Documentation Forms needed for registration/testing Test results

EITT – Aim of the software
EITT may be used at: 1. KNX accredited test labs: use of tool for KNX certification tests 2. KNX member companies: KNX Development department: Preparation of certification campaign Manufacturers’ test labs: Climate/stress tests, … Production: quality control end tests (via included Automation API)

EITT – Basic functionality
To test the compliance of KNX devices to the KNX Interworking requirements: EITT simulates inputs to a BDUT EITT expects outputs from a BDUT EITT checks for differences and shows the results.

EITT – Test project components
EITT offers functions and tools to import and amend device data of interest from ETS: "Pixit data". to define one or more sequences of ‘to be transmitted’ and/or ‘to be expected’ telegrams, scheduled in time: "Telegram sequences". to store and examine the results of sequence evaluation: "Tracebuffer". Pixit data, Telegram sequences and the Tracebuffer build the content of EITT documents (.ctl-files).

The PIXIT Header

The PIXIT Header - Device infos
The PIXIT contains the device data of interest related to the product certification: General device information, communication objects, parameters.

The PIXIT Header – Communication object data
Communication object data: object number, function, name, object size, priority, flags, group addresses, DPT (if available), comments (if available).

The PIXIT Header – Import device data from ETS
Get the PIXIT data: Import from ETS project.

The PIXIT Header – operations on / with PIXIT
Manual completion of information missing in ETS project.

Creation of telegrams in a Telegram Sequence.

Automatic comments during telegram reception, based on PIXIT data. Name and Function fields. Group address comment from ETS (as imported from ETS). Manually entered comment in PIXIT Header Window. Can be switched on/off via menu.

The PIXIT Header – Parameter data
Export of a list of implemented objects and parameters needed for certification submission.

Telegram Sequences

Set of telegrams to send to the BDUT / to be expected from the BDUT.
Telegram Sequences Set of telegrams to send to the BDUT / to be expected from the BDUT. One or more telegram sequences per EITT document. Organized by a Telegram Sequence Manager, which allows to - create, - open, - close, - rename, - delete, - import, - export, - print Telegram Sequences, - open .ctl – Files, - close .ctl – Files (EITT documents).

Telegram Sequences – Work Flow
1. Step: Create Telegrams to send to the BDUT, create telegrams to be expected from the BDUT. by menu, toolbar or by using the Pixit Header Windows 2. Step: Edit telegram fields directly in telegram sequence grid.

3. Step: Edit telegram attributes to configure the sequence evaluation. 4. Step: Create Comments to document the telegram sequence.

5. Step: Configure bus connections. 6. Step: Start telegram sequence evaluation.

7. Step: Check evaluation result, examine the tracebuffer window

Telegram Sequences – Configure Bus Connections
Multiple bus connections can be used in one Telegram Sequence. Default: If set, the connection will be used as default connection. If a telegram has no connection assigned, the default connection will be used to send or receive the telegram. Only one bus connection of each type (Bus/Local) can be set as default connection. Name: Symbolic name of the bus connection for usage in the Telegram Sequence.

Telegram Sequences – Bus Connections
The name of the FALCON bus interface connection, which is used to establish the KNX bus communication. A click in the connection column opens a dropdown menu to select one of the configured FALCON connections. Activate: Enables or disables the bus connection. If the ‘Activate’ option is not checked, EITT does not open the bus connection. Bus/Local: Determines if the connection is used for local service tests (see chapter 'Local Service Testing'). If 'Local' is selected, the bus connection will be used to send or receive 'Local Service' telegrams.

Pei: To properly encode the telegrams, which have to be sent to the bus interface, the user must select the EMI type of the connected interface. EITT is not able to automatically detect the EMI type. Layer: Sets the communication layer. The bus connection can be established in Link Layer Mode, Busmonitor Mode and in Raw Mode. In Raw Mode EITT switches the interface to raw mode and uses the ‘L_RAW.req’ service to send telegrams. The usage of Raw Mode requires the installation of Falcon version 2.0 or higher on the PC and an interface that supports Raw Mode.

ChkSum: This option is available only for raw mode. If set, Eitt calculates and adds checksums while sending telegrams. If not set, Eitt sends the given telegram data directly to the BCU without adding a checksum. Adjust: Enables an automatic adjustment of the source/destination addresses to local interface address. Adapt: Enables an automatic adjustment of the physical address of the local interface (!) to the one specified in the sequence.

EITT provides two different bus connection lists: Default Bus Connections Independent from the currently loaded EITT project. Project specific Bus Connections Valid for currently loaded and active EITT project (.ctl-file) only. Important to run a sequence on different PC. Can be activated / deactivated. Can be automatically created from the default bus connection during project creation.

Telegram Sequences – Telegram attributes
Common telegram attributes for most telegram types: Can be configured in the 'Telegram Properties Window', which shows the attributes of the currently selected telegram. Source address OUT: Individual address of the BDUT. IN: Individual address of the connected BCU. Destination address Group address of the communication object to test. Control field Priority, repetition flag. Routing counter Apci Frame type

Telegram Sequences – Telegram Types
Datapoint type related telegrams: Interpretation and commenting values according to DPT Automatic evaluation of tolerance values

Non-DPT: Ability to create telegrams for group objects not using standardised data types.

Management Telegrams Automatic calculation of sequence numbers. Accepts wildcard characters '?' in the telegrams 'Data' field for OUT telegrams. Creation of general 'User-Data' service telegrams is possible. Tolerance values for ADC-Read.

Polling Telegrams Selection of polling service (L_PollData.req, L_PollData.conf). Edit slot numbers. Edit polling slots. Accepts wildcard characters '?' in the telegrams 'Data' field for OUT telegrams.

Faulty Telegrams Allows incorrect values into fields. Allows wildcard characters '?' in to be expected faulty telegrams. EITT will transmit the telegram data without modification to the BCU. Requires BCU supporting 'Raw Mode' Layer.

Local Services Telegrams Testing of local services. Local Service telegrams will be sent / expected via the bus connection marked as 'Local'.

Comments: Telegram Sequence and Tracebuffer documentation.

Telegram Sequences – Summary
Available telegram types: DPTx.x Telegrams Non-DPT Management Telegrams Polling Services Local Services Faulty Telegrams Comment Lines Configure the telegram sequence behaviour: Transmit mode Time to next telegram Wait end time flag Telegram blocks Telegram cycles Automatic address adjust Comment commands

→ The telegram sequence will be evaluated as fast as possible!
Telegram Sequences – Telegram attributes Transmit Mode In: Telegram will be sent to the BDUT. OUT: Telegram will be expected from the BDUT. Time to next Telegram IN: Period of time that EITT waits after sending the current telegram. OUT: Period of time that waits for the expected telegram. Stop command available. Wait end time Flag Wait: EITT waits for the end of the 'Time to next Telegram' period. The telegram sequence will be evaluated in a fixed time! No wait: EITT continues the sequence immediately after having received the correct telegram. → The telegram sequence will be evaluated as fast as possible!

Cycles IN: Amount of send repetitions. The send time distance between sending is given by the value of 'Time To Next'. OUT: Amount of telegrams which EITT expects in the given 'Time To Next' period. Under development: Use of a time period instead of a cycle count: IN: EITT repeats sending until the given time period has elapsed. OUT: EITT expects the specified OUT telegram for an undetermined number of times within the specified time period. At least one specified OUT telegram must be received in the given time period.

Building telegram blocks Send a telegram to the BDUT Then wait for one or more answers, but no longer than 0,2 seconds. Use the function 'Build Telegram Blocks' from the Edit – menu and let EITT do the work:

Automatic address adjust Problem: If the address of the locally connected BCU changes, then all source addresses of all telegrams need to be changed. Solution: EITT automatically adjusts all source addresses before evaluating a telegram sequence. This feature is related to a BCU connection. Can be switched off/on for each telegram.

Inverse Evaluation Use case: The BDUT shall not ACK a specific telegram. A missing ACK (normally displayed as an evaluation error) shall be evaluated as a positive result.

Inverse Evaluation:

Evaluation in loop mode EITT repeats telegram sequence evaluation. A number of loops can be specified. Unlimited loop execution is selectable. The number of executed loops is visible in the tracebuffer.

Telegram Sequences – Summary of Edit functions
Sort telegrams. Column wise telegram filter. Search & Replace telegram content. Usage of bookmarks: Insert, Edit, Jump to next bookmark, Select bookmark.

(Re-) Assign datapoint types to telegrams. CSV Import / Export of telegrams sequences. Print telegram sequences to PDF.

Copy telegrams via Drag&Drop from other sequences or from Tracebuffer. Telegram clipboard for 'Telegram snippets'.

Telegram Sequences – Comment commands
Comment Commands – wait or suspend sequence evaluation Suspend telegram sequence evaluation and wait for a specified time period: Give the user time to perform some test related actions. Can be used in telegram comments or in comment lines.

Comment Commands – check for receive errors if transmit mode OUT Stop telegram evaluation if a telegram could not received Count receive errors counter>). Stop on predefined limits. Use EITT for quality control during production: Check values from a temperature sensor. Count tolerance violations. Suspend sequence evaluation.

Comment Commands – display receive error counters Reset error counters. Change limits during sequence evaluation. EITT suspends evaluation, if a limit is reached.

Telegram Sequences – Protected Sequences
It is possible to ‘lock’ a telegram sequence: EITT creates a copy of the locked sequence. EITT prevents from editing the locked sequence. The user is allowed to edit the copy, but not the original (locked) sequence. A password is required to ‘unlock’ the sequence. The differences between the locked sequence and its copy will be marked by color. It is easy to find changes between the original sequence and the modified copy. Can be used to reduce test effort when testing product modifications only.

Telegram Sequences – Protected Sequences

The Tracebuffer

Tracebuffer The Tracebuffer Window displays all telegrams sent by EITT and all telegrams received from the bus. The Tracebuffer shows the results of telegram sequence evaluation. One Tracebuffer per EITT document (.ctl file) Several display options. Several telegram style options. Search, filter and trigger functionality.

Tracebuffer

Tracebuffer – General display options
Received telegrams only. Sent telegrams only. Failed telegrams only. Display service names instead of telegram bytes. Display encrypted telegram, if telegram is secured (confidential / authentication). Display ACK / NAK / BUSY in busmonitor or raw mode. Use display filter.

Tracebuffer – General display options
Display options: Display services OFF / ON

Tracebuffer – Display filter
Display filter: A set of criteria (RF serial no., priority, source address, destination address), which will be applied to the Tracebuffer. Specifies the telegrams to be shown in the Tracebuffer Window. Does not affect the content itself !

Tracebuffer – Display filter
Operations: Apply to Tracebuffer, Activate/Deactivate, Rename, Delete, Export as CSV file, Import.

Tracebuffer – Trace Trigger
Telegram triggers: Similar to filters (a set of telegram attribute criteria). If a trigger is active, the telegrams that do not comply with the trigger condition, will not be transferred (!) in the tracebuffer. The recording of telegrams starts after the x-th trigger event and is related to the telegram, which has fulfilled the trigger condition.

Tracebuffer – Trace Trigger

Tracebuffer – Further options / operations
Find and show related telegram in Telegram Sequence. Compare received / expected telegrams. Set AF result (automatic failed) to MP (manually passed). Insert / Edit / Delete comment lines. Find next / previous failed telegram (via toolbar button). Find telegrams, which fulfill a set of conditions (addresses, telegram numbers, serial numbers, …). Clear / Import / Export tracebuffer content. Print tracebuffer. Automatic save of content to file, if a certain telegram limit is reached.

Advanced Topics – Support of RF testing
EITT allows to enter, edit and display RF specific telegram attributes: RF Serial Number Data of the RF info byte 'Address extension' flag of the telegram control field. Usage of telegram coloring in the Tracebuffer Usage of telegram whitelist to prevent from evaluation of interfering RF transmitters.

Display / Edit RF specific attributes in the Telegram Properties Window. RF info byte data RF serial number LFN automatic / fix Evaluation options:

Address Extension field: In the Telegram Properties Window an extra field named 'Address Extension' is available with the following settings: serial number: system broadcast not restricted to domain. domain address: broadcast restricted to domain

Display / Edit of 'RF info byte' and 'RF Serialnumber' in the Telegram Sequence Window… … and the Tracebuffer.

Usage of colors and nicknames for RF serialnumber evaluation:

Usage of a RF serialnumber white list:

Advanced Topics – Support of KNX Data Security
EITT allows to enable encoding of telegrams according to the KNX data security protocol. Encoding and decoding of telegrams according to the application note 158/13 v01 ‘KNX Data Security’. Supports encoding / decoding of LinkLayer Telegrams. Creation of SA_SYNC service telegrams for sequence number synchronization. Dialogs to enter security keys and sequence numbers. Tracebuffer coloring and display of symbolic key names. Extended log capabilities: logging of encoding / decoding steps.

Display / Edit security specific attributes in the Telegram Properties Window. Enable encoding Set security type Set SBC flag Set Tool-Access flag Enter security key (from table / fixed) Enter sequence number (from table / fixed)

Creation of SA_SYNC service telegrams. New EITT telegram type: SA_SYNC service. EITT allows editing of the local and the remote security sequence number field of a SA_SYNC telegram. Automatic calculation / Fixed sequence number. Allows editing of the Challenge bytes.

SA_SYNC service telegram attributes:

Configuration of security keys in the 'Security Configuration Table'.

Configuration of sequence numbers in the 'Sequencenumber Table'.

Encrypted telegrams in the Tracebuffer Secured and successfully decrypted data telegram. Successfully decrypted SA_SYNC telegram. Decryption error (e.g. no or wrong key). Successfully decrypted telegram, sequence number wrong.

Encrypted telegrams in the Tracebuffer – show encrypted frame. APCI SCF Sec. Seq. Number Data MAC

Extended data logging – shows encryption data calculation steps:

Advanced Topics – Automation API
EITT provides its internal objects and a set of functions for data manipulation and sequence control. According to Microsoft's DCOM specification. Language independent, can be used by script languages. The API allows writing applications to control EITT. Available operations: Open EITT projects (.ctl-files). Browse through the objects of an EITT project. Configure bus connections. Access and manipulate data in Telegram Sequences. Start telegram sequence evaluation. Check result of telegram sequence evaluation. Description of the API available in the EITT Help File.

Advanced Topics – Automation API objects

Access to the root object: 'Application Object' Precondition: EITT must be properly installed (not copied) on the PC. The setup program registers EITT in the registry database of the PC as the program that is the provider of the initial object, called: EITT. Application („Program ID“) Registry: HKEY_CLASSES_ROOT: Eitt.Application = Eitt Eitt.Application\protocol\StdFileEditing\server = c:\Program Files (x86)\Eitt4V43\Bin\eitt43.exe Eitt.Application\CLSID = {9f44a470-caa3-11d0-a }

VB Script sample Example: Start EITT, create the initial object, retrieve the version number and open a given CTL file. Set Eitt=CreateObject( "Eitt.Application" ) If (Eitt Is Nothing Then) MsgBox ( "Error: Eitt not loaded !" ) End If nMainVersion = Eitt.GetMainVersion() nSubVersion = Eitt.GetSubVersion() MsgBox( "Eitt loaded, API version: " & nMainVersion & "." & nSubVersion ) Set ProjectFile=Eitt.OpenProjectFile( "c:\eitt43\workshop\example1.ctl" ) If ProjectFile Is Nothing Then At this point, Eitt has been started, the version numbers has been retrieved and the CTL has been opened. The user can see EITT with the CTL file loaded.

Example: Open telegram sequence, changes BCU and BDUT addresses, start sequence evaluation. // Get sequencemanager object and parameter sequence Set SequenceManager = ProjectFile.GetSequenceManager() Set SequenceItem = SequenceManager.GetSequence( „SetCycle_3_min“ ) // Iterate over all telegrams of the sequence to change the source and // destination addresses Set TelegramItem = SequenceItem.GetFirstTelegram() while (Not TelegramItem Is Nothing) if (TelegramItem.GetTransmitMode() = 0) Then // communication way IN TelegramItem.SetSourceAddress( nLocalAddress ) TelegramItem.SetDestinationAddress( nBdutAddress ) else // communication way OUT TelegramItem.SetSourceAddress( nBdutAddress ) TelegramItem.SetDestinationAddress( nLocalAddress ) End If Set TelegramItem = SequenceItem.GetNextTelegram() Wend SequenceItem.Start()

EITT – Planned developments
Interpretation of management telegram data according to datapoint types Support of system conformance tests Automatic creation of telegram sequences according to the test specification described in volume 8/3/7 for lower layer tests.

Multiple PIXIT Headers in one EITT project (.ctl-file). Automatic creation of predefined 'Telegram sequence snippets' on the basis of the PIXIT Header. A set of predefined telegrams per datapoint type. Right click on a communication object in the PIXIT Header. Select one of the available snippets from context menu. Automatic insertion of object data to the snippet telegrams (addresses / comments). Insert modified snippet to the currently active Telegram Sequence. Support of more datapoint types. Sequence control directly in EITT via internal use of scripting language. Use of FALCON 5.

Web: 91

Functionality and Use Andreas Espen, Agentilo GmbH.

Similar presentations

Presentation on theme: "Functionality and Use Andreas Espen, Agentilo GmbH."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Functionality and Use Andreas Espen, Agentilo GmbH.

Similar presentations

Presentation on theme: "Functionality and Use Andreas Espen, Agentilo GmbH."— Presentation transcript:

Similar presentations

About project

Feedback