Documentation map Click any component to open its documentation — subsystem boxes lead to the overview chapters (the cards below), the inner boxes to the class reference pages.
Interfaces - drive EITT programmatically Document model & editing Execution Transport Known issues Aggregated 'flagged, not fixed' defects across the codebase. Build & release process Automation API (COM) COM / IDispatch interface to drive EITT from an external program. REST API HTTP / JSON automation interface alongside the COM API. Test-plan & sequence model The telegram-sequence / plan model at the heart of an .eittproj document. Pixit Headers The application-layer description of the device under test (PIXIT proforma). Telegram Property System The right-hand property sheet: every telegram/comment field, grouped and editable. Datapoint Types The DPT value model and its XML/XSD catalogue - encodings, ranges, tolerances, decoding. Conformance Tests Load signed test templates, apply profiles, compile selected tests into plans. Plan Evaluation Engine The runtime that executes a plan against a device - send, wait, match, verdict. Security Send and verify secured KNX traffic - KNX Data Security and secure KNXnet/IP. Trace & filter The trace buffer of every sent/received telegram, with filters and triggers. Communication layer Every transport EITT uses to talk to a device: KNXnet/IP, TP1/USB, CoAP, HTTP, DNS. CI process What a build machine needs to turn a fresh clone into a signed installer. CI jobs Every pipeline job in one table - gated against .gitlab-ci.yml. SBOM & vulnerability scan The shipping bill of materials and its nightly OSV scan. EittPort DocObj PlanObj EittApiServer EittApiHandler Certtdoc Plan Tseqitem Tseqman Pixit PixitEtsImport PixitTestValues TelProp DPT attributes Tolerances DPT Eisvalue KnxDatapointTypes ConformanceTests ConformanceTestMgr ConformanceTestView Planeval Sequence evaluation planevrs Planevsq SecurityHandler KnxCrypto SecurityTables Traclist Tracfilt Tractrig KnxNetIP LocComm EittCoAPMgr UsbComm drive drive generate plans run secured traffic verdicts send / receive Aggregated 'flagged, not fixed' defects across the codebase. COM / IDispatch interface to drive EITT from an external program. HTTP / JSON automation interface alongside the COM API. The telegram-sequence / plan model at the heart of an .eittproj document. The application-layer description of the device under test (PIXIT proforma). The right-hand property sheet: every telegram/comment field, grouped and editable. The DPT value model and its XML/XSD catalogue - encodings, ranges, tolerances, decoding. Load signed test templates, apply profiles, compile selected tests into plans. The runtime that executes a plan against a device - send, wait, match, verdict. Send and verify secured KNX traffic - KNX Data Security and secure KNXnet/IP. The trace buffer of every sent/received telegram, with filters and triggers. Every transport EITT uses to talk to a device: KNXnet/IP, TP1/USB, CoAP, HTTP, DNS. What a build machine needs to turn a fresh clone into a signed installer. Every pipeline job in one table - gated against .gitlab-ci.yml. The shipping bill of materials and its nightly OSV scan. Model & documents Interfaces Testing & security Looking for a specific class or file? Browse all source-reference modules →