fdiDTM

What it is

A bridge component that dynamically parses DD / FDI packages into DTMs at runtime for device-driver asset reuse between FDT and FDI / EDDL.

What it is not

It is not an FDI Host and does not provide an unconditional compatibility commitment for all DD / FDI packages, advanced displays, or vendor extensions.

Verification path

Places DD / FDI package reuse, DTM runtime form, and FDT-version boundaries on one verification path so teams can assess whether existing device-description assets can be handled through a bridge component.

Decision inputs

Confirm protocol scope, DD / FDI package capability boundaries, FDT-version conditions, and unsupported advanced-display items before moving to specifications, sample validation, or a technical discussion.

Device suppliers

Reuse DD / FDI packages and assess whether they can enter a DTM usage path.

System integrators

Confirm HART / Profibus device integration, parameter access, and FDT-version conditions.

Pre-sales / solution managers

Differentiate fdiDTM, an FDI Host, vendor-specific DTMs, and advanced-display capability boundaries.

Existing DD / FDI package

Assess whether an existing device-supplier DD / FDI package can enter a DTM usage path.

FDT access boundary

Confirm HART / Profibus device integration boundaries under FDT 2.0 or FDT 3.0.

Reuse versus dedicated development

Assess FDI / EDDL asset reuse separately from the dedicated DTM development path.

FDT versions

FDT 2.0 and FDT 3.0.

Protocol scope

Device integration within the HART and Profibus protocol scope.

DD execution scope

Parameter read, parameter write, and execution of DD-defined commands.

FDT 3.0 scope

Cross-platform operation and browser DTM UI apply only to the FDT 3.0 version.

Integration role

A bridge between DD / FDI packages and the FDT runtime form in the Device Driver Development and Diagnostics Reuse path. It helps reuse existing device-description assets but does not replace vendor-specific DTMs, an FDI Host, or a complete device application.

Version boundary

Cross-platform and browser DTM UI statements apply only to FDT 3.0 and must not be extended to other versions.

Not covered

It is not equivalent to an FDI Host; METHOD, AXIS / WAVE / GRID, and other advanced displays are not covered; compatibility is not promised for all DD / FDI packages without conditions.