genericDTM
genericDTM is a generic device integration component based on the FDT standard. When no vendor-specific DTM is available, it provides a basic access path for supported fieldbus profiles. It is not a full replacement for a vendor-specific device DTM.
Associated solution package: Device Driver Development and Diagnostic Reuse.
What it is / is not
What it is
A generic DTM path for basic device access when no vendor-specific DTM is available.
What it is not
A complete replacement for a vendor-specific DTM, or a commitment to vendor-specific extended parameters or private diagnostic models.
User value
Validate basic access
When no vendor-specific DTM is available, genericDTM provides a path that can be validated first, helping teams assess basic parameter access and device identification.
Keep capability boundaries clear
For device suppliers, system integrators and pre-sales teams, distinguish basic access from vendor-specific DTMs, extended parameters and private diagnostic models. Do not present basic access as a commitment to full device functionality.
Who it is for
System integrators
On-site equipment has no vendor-specific DTM, and basic access needs to be checked first.
Device suppliers and partners
Assess whether a HART or PROFIBUS PA device is suitable for a basic access path.
Pre-sales and solution managers
Distinguish basic parameter access from vendor-specific extended parameters and private diagnostic models.
Typical use cases
No vendor-specific DTM is available on site, and basic HART or PROFIBUS PA access needs to be validated.
A pre-sales team needs to assess whether a generic access path is sufficient to enter an initial PoC.
A partner needs to explain the difference between basic connectivity and vendor-specific extensions.
Core capabilities
HART edition
HART 5 / 6 / 7 and basic parameter access.
PROFIBUS edition
Access to devices that conform to the PROFIBUS PA profile.
Automatic matching
When no vendor-specific DTM is available, genericDTM can provide a basic access path.
Architecture and integration relationship
genericDTM is part of the Device Driver Development and Diagnostic Reuse path as a tool for filling a basic-access gap. It is intended first for basic parameter access and device-identification assessment, not dedicated device functions, vendor extensions or a complete diagnostic model.
Applicable standards / versions / environment
Do not extrapolate HART edition capabilities to PROFIBUS edition, or PROFIBUS edition capabilities to HART.
Customer prerequisites
HART genericDTM
Provide a HART device, communication interface, FDT Frame, network and access permissions.
genericDTM - PROFIBUS
Provide an FDT Frame Application, communication DTM, PROFIBUS device, network and communication environment.
Responsibility boundary
Device behavior and communication stability are outside the product responsibility boundary.
Out-of-scope boundaries
- Vendor-specific DTMs.
- Vendor-specific extended parameters or private diagnostic models.
Related solutions
Device Driver Development and Diagnostic Reuse
Driver Path Selection Guide
FAQ / contact
Device Integration FAQ
Technical discussion
Arrange a genericDTM technical discussion to confirm device protocols, generic commands and vendor-extension boundaries. TBD
Contact: products@mm-software.com
Evidence and resources
Related solution: Device Driver Development and Diagnostic Reuse.
Resource handoff: Product specification index, FAQ, PoC Preparation Checklist, Security, Permissions and Audit.
Next Step
Get the genericDTM specification or fact-boundary description | Arrange a genericDTM technical discussion and confirm applicability boundaries TBD | Return to the Device Driver Development and Diagnostic Reuse solution