Diagnostic Kernel PRODIS.MCD

PRODIS.MCD is the implementation of the diagnostic programming interface according to ISO 22900-3, which emerged from the ASAM MCD-3D 3.0.0 standard.

An essential functionality of PRODIS.MCD is the control unit communication: Diagnostic services parameterized by the diagnostic application are converted into a byte stream according to the rules stored in ODX and sent to the control unit via the D-PDU API. The hexadecimal coded responses received from the controller are also interpreted taking into account the associated ODX descriptions and transmitted as readable data to a diagnostic application.

In addition, PRODIS.MCD provides an efficient implementation of interfaces for executing flash and coding routines.

PRODIS.MCD combines memory efficiency with unsurpassed performance and provides maximum flexibility through configurability. PRODIS.MCD has proven to be the best performing MVCI system in the market and is used in vehicle development and production as well as in workshops and connected vehicle applications.

Monitoring the health of mission-critical vehicles is made easy by integrating the diagnostic capabilities of PRODIS.MCD as part of a telematics control unit.

To reduce the TCO by adding diagnostics capabilities to your commercial vehicle by integrating the diagnostics stack in a telematics control unit.

PRODIS.MCD can be used both off-board, or integrated as part of a Virtual Diagnostics ECU as part of a diagnostics domain controller for connected vehicle applications.

Benefits

MCD supports the ODX versions ODX 2.0.1, ODX 2.1.0 as well as the international ISO standard ODX 2.2.0 (ISO 22901-1).
All three ODX source formats are converted by an ODX converter into a uniform binary target format. For the conversion of ODX source data into the compact and modular runtime format, the console application (ODX Converter) or optionally a user program with user interface (PDX Builder) can be used.
Full integration into the PRODIS suite: PRODIS.MCD is an integral component of the PRODIS.RTS and PRODIS.WTS diagnostic runtime systems and thus also a basis for the PRODIS.Authoring and PRODIS.Automation

MCD is compatible to DSA test equipment, e.g. the DSA MDI-G4, smartMDI, WDI-2 or MFT-4 but also to other vendor’s test equipment, if this supports the D-PDU API.
MCD is compatible with various processor architectures such as i386, PowerPC, ARMv7, ARMv8 or AMD64.
PRODIS.MCD is portable and can run on various platforms such as Windows, various Linux distributions, QNX or ios.

Kernel Features

Platform Independence

PRODIS.MCD is implemented in ANSI C++ and can thus be compiled for any platform featuring an appropriate compiler

Integration

PRODIS.MCD is equipped with all currently standardized interface technologies (Java, C++, DCOM) and can thus be integrated into diagnostic applications with various technologies.

Ease-of-Use

PRODIS.MCD can be installed on a Windows PC via Windows 32-bit and 64-bit setups and can be addressed immediately with real ODX data via an installed diagnostics test client.

System-specific packages are created for installation on Linux-based systems.

Scalability

PRODIS.MCD’s memory management reads the needed diagnostic data on demand and in a fine-grained manner from disk, thus protecting memory resources.

Independence

PRODIS.MCD communicates with vehicle communication interfaces (e.g. DSA’s MDI-G4, smartMDI or WDI-2, Vector’s CANCardX or ETAS’ MDI) via any standard compliant D-PDU API, e.g. PRODIS.PDU.

DoIP is fully supported.

Performance

PRODIS.MCD is extremely powerful; against vehicle simulations below the D-PDU-API up to 5000 diagnostic services per second are executable.

Reliability

PRODIS.MCD has been in use for more than 15 years and has matured into a reliably working product in every application.