Product Information
Table of Contents 1 Introduction to vcdm... 3 1.1 Overview of Advantages... 3 1.2 Supported File Formats... 4 1.2.1 Object files... 4 1.2.2 Parameter set files... 4 1.2.3 ECU description files... 4 1.2.4 Report formats... 4 1.4 Further Information... 5 2 Functions... 6 2.1 Highlights... 7 3 Project and Variant Management... 8 4 Import and Merge Calibration Data... 9 5 Generate ECU Files... 10 6 Software Changes... 10 7 Reports and Data Mining... 11 8 Enhanced Methods for Calibration Variant Management... 13 9 Managing Parameter Dependencies... 14 10 CDM Studio Editor... 15 11 Guided Working Mode... 16 12 E-Mail Notification... 17 13 Collaboration on the Road... 17 14 Data Exchange OEM / Supplier... 18 15 Domain-specific Views... 18 16 Documentation... 19 17 Automation... 19 18 Training Classes... 19 V2.1 8/2016 Valid for vcdm Studio from Version 5.8. 2
1 Introduction to vcdm vcdm (Vector Calibration Data Management) is the database-supported platform for calibration teams. Work results are efficiently merged. Potential data conflicts are avoided, detected and resolved. All changes to data can be tracked. Data versions are consistent and have a high level of data quality. A large number of variants can be handled reliably. Data mining and report functions ensure effective monitoring of project progress and quality, and they increase the efficiency of the calibration process. The calibration data can be graphically displayed and manually edited using the CDM Studio Editor. As a scalable solution, vcdm supports teams and departments in application data management and can also be used as a cloud solution. Figure 1: Clearly structured vcdm user interface for professional calibration data management 1.1 Overview of Advantages > Work packages, parameter and use case permissions can be utilized to avoid conflicts. If conflicts occur, they are detected and can be conveniently resolved. > All operations are optimized for a large number of variants. > Data is saved in an ECU-independent internal data format. In this way transformations between ECU and engineering notations are prevented. Data analysis and report functions can be processed very efficiently. > The modern system architecture supports globally distributed teams. > CDM Studio is part of vcdm and can be used without database connection for file based operations. > Domain-specific views visualize certain aspects of the application data in a clear form. 3
> Data protection through roles and rights at the dataset level > Efficient variant management for derivatives and components 1.2 Supported File Formats Calibration tools generate and require a number of file formats. 1.2.1 Object files Object files contain the ECU code and the calibration data. vcdm can update this calibration data without having to recompile the ECU software. Supported formats: > Intel-HEX > Motorola S-Record 1.2.2 Parameter set files These files transport the calibration data in physical form, in a representation that matches the numeric and graphic display in the calibration tools. Supported formats: > DAMOS DCM > CSV/CVX > MSR PaCo > ASAM CDF 2.0 > CANape PAR > MATLAB m files 1.2.3 ECU description files ECU description files contain the structure of the ECUs. These files are necessary for transformation of the data between object files and parameter set files. Supported formats: > ASAM A2L > CANape DB (read only) 1.2.4 Report formats vcdm generates different types of reports. Depending on the purpose of the report, the data can be generated in a format for further processing such as Excel or more static formats such as PDF. Supported formats: > Excel > PDF > Word > PowerPoint > HTML File extensions for the formats can be configured in any desired way. Other formats may be added upon request. 4
1.3 vcdm Options > MCD Tool Integration Add-On: This add-on can be used to call the most frequently used functions of vcdm directly from the calibration tools CANape and INCA. This add-on is supplied with the product and can be installed as an option without incurring additional costs. Figure 2: CANape Integration > Programming interfaces: Nearly all vcdm functions are available via a scripting interface and can be executed by automated scripts. The vcdm server offers a SOAP-based web service interface for integration in enterprise applications. Both of these interfaces are supplied with the product and can be used without incurring additional costs. > Web Frontend: The vcdm server offers a way to access frequently used functions via a web browser. This is the ideal way to permit the connection of external organizations or occasional users. Use of the web frontend requires separate licensing. > Local Repository Server: To efficiently access data from remote sites, it is possible to replicate the data to these sites. For this purpose, a separate license of the vcdm repository servers is necessary for each of the sites. > Collaboration on the road: Project and datasets can be exported to a lightweight vcdm system. The system can be taken to remote test grounds. It provides the full vcdm functionality. The changes are later imported back into the central system. 1.4 Further Information Various documents related to vcdm are available on the Internet. Benefit from valuable know-how in the form of technical articles or product videos. For more information, go to the Vector Download Center. 5
2 Functions The functions of vcdm support all phases of the calibration process: Figure 3: Overview calibration process in vcdm > Create calibration projects > Define calibration variants and their attributes (features) > Set up work packages and permissions > Import calibration files > Review changes > Merge parameter sets > Detect and resolve conflicts > Generate updated ECU files > Transform existing calibration data to new ECU software > Graphically compare and manually manipulate data with CDM Studio editor > Establish consistency criteria and checks > Calibration history and overview of incorporated work packages > Prepare ECU software for production > Access to all functions via automation interfaces > Report and data mining functionality > Guided mode for new and sporadic users > Export and import of projects to support test sessions > Management of component libraries > Documentation of application expertise > Special views for special tasks (e.g. OBD blocking behavior) 6
2.1 Highlights The feature highlights of vcdm are: > Highly scalable system, tested in globally distributed organizations with hundreds of users > ECU-independent storage of calibration data > Consistent tracking of the history of imported and merged calibration data > All operations optimized for a large number of variants > All imported parameter sets (work packages) are managed as independent artifacts and linked to the assigned variants. The reuse of files within the variants can be clearly tracked. In this way, files and work packages can be easily kept consistent in large number of calibration variants. > The powerful CDM Studio editor is used to display and manipulate calibration data > The dependencies of parameters and attributes can be managed. This dependency can be used to automatically assign imported files to the correct variants, to check consistency of variants or to repair inconsistencies. > Configurable consistency criteria and checks > Extensive programming interfaces > Simplified access for sporadic users and parameter set import > Integration in CANape and INCA calibration tools > Web access for external organizations and occasional users > Support of all commonly used data formats > Domain-specific views of data Figure 4: Project browser in web frontend 7
3 Project and Variant Management vcdm offers a number of functions for managing projects and variants. These functions are normally executed by a project manager, also referred to as data integrator: > Managing projects and variants: vcdm can be used to manage any number of projects. In each project, there may be any number of independent data variants, each of which contains a desired range of parameters. > Product properties: Product properties such as engine displacement, legal emissions limits or gearbox properties may be assigned to the variants. The list of product properties can be supplemented in any desired way. Figure 5: Definition of calibration variants > Structuring the variants: To handle a very large number of variants, these can be displayed in the tree with the help of attributes. The view can be specified based on rules or set up on a user-specific basis. The various revision statuses are shown below each variant. Figure 6: Variant management in automatically generated folders > Automatic history tracking: All changes to the variants are automatically tracked in a history. Developments over time and parameter set imports are tracked precisely and can be retrieved later in a few seconds. > Defining work packages and rights: To coordinate the import of calibration data in a team, work packages and rights can be defined. Rights may be assigned in a scaled way from the project to variant and even individual parameters. 8
Figure 7: Work packages can be easily defined in the editor 4 Import and Merge Calibration Data These actions are performed by the calibrators or data integrators. 9
Figure 8: Import wizard for parameter sets > Consistency check at parameter set import: When importing calibration data, consistency conditions such as permissions, work packages, value ranges and other properties are checked. > Optimizing for large numbers of variants: Filters and intuitive representation of the variants help the user to identify all of the variants needed for a parameter set import. > Merging the data: Imported parameter sets can be conveniently merged. If conflicts occur, they are detected and resolved. > Quality data: At the parameter set import, status information and comments can be added and attachments can be included. It is also possible to link imports to issue tracker and requirements management systems. > Optimized user interface: The complexity of the user interface can be reduced to a minimum for the data import. This lets sporadic users quickly learn how to submit data. > Integration in calibration tools: A supplemental feature is the direct parameter set import from the CANape and INCA calibration tools. > Excel import and export: Import templates can be exported and reused in Excel. 5 Generate ECU Files After all necessary calibration data has been imported and merged; the project manager (data integrator) generates a new, updated revision of the ECU software: > Consistency checks: Configurable consistency checks are also performed for Intel-HEX and Motorola S-Record generation. > Naming rules: HEX names can be automatically generated based on configurable rules. > Preparation for production: The new ECU software can be generated in a form in which it can flow directly into the production process. Checksums and signatures may be inserted in the ECU file for this purpose (HEX post treatment). 6 Software Changes If the ECU base software changes, all calibration data must be adapted to the new calibration software. > Optimized for mass operation: This operation can be executed on many dozens or even hundreds of variants simultaneously. > Parameter renaming: Renaming of parameters is supported. > Seamless history: The software change does not interrupt the history. > Parallel work on ECU software versions: After a software change operation, the old software version is still accessible and new revisions could be created. The software versions of the calibration variants are represented in independent branches. > Reports: Changes between A2L files can be exported into an Excel report. > Rule based data migration: vcdm and CDM Studio provide a wizard that enables suppliers, software developers and experienced calibrators to define complex transformation rules. These rules are necessary, if new ECU software versions introduce complex parameter property changes. The rules are later incorporated into the software change process of vcdm. The existing calibration data it then automatically transformed to the new ECU layout. > Possible scenarios that can be handled in this way: > Unit changes: Automatically transform seconds to milliseconds. > Parameter type changes: Convert curves to maps. 10
7 Reports and Data Mining vcdm offers a number of reports that can provide important information within just a few seconds: > Data comparison: It is possible to compare various variants. The result can be presented graphically in CDM Studio or could be exported to Excel. The report incorporates A2L information, parameter values, quality information, parameter maturity, work package and permission assignments and much other information. A template mechanism can be used to apply the report on different use cases without repeated configuration efforts. Figure 9: Map comparison exported to Excel > Parameter value instances: This analysis shows the different values of a parameter occurring in different variants and projects. This analysis can be used to optimize parameters or a consistency check. Figure 10: Evaluate occurrences of parameter values in calibration variants > Parameter history: This report answers the question: Who made what change when and from which source? What was the initial value, and to which value was the parameter changed? 11
Figure 11: Parameter history in dashboard > List of work package contributions: This report provides the sum of imported calibration files that make up a variant. The history is tracked over as many revision levels as desired. > Calibration quality: The quality of the calibration can be tracked over time or over variants. Figure 12: Calibration progress report > Data review with CDM Studio: CDM Studio is the best tool for offline data reviews. By utilizing the filter and compare functions, also complicated review matters could be handled. Possible changes are comfortable merged into vcdm dataset. 12
8 Enhanced Methods for Calibration Variant Management vcdm offer various methods to keep a huge number of calibration variants consistent. The mechanism can be applied independently or combined according to the needs of an organization. Figure 13: Methods for variant management in vcdm > Attribute: Attributes can be attached to calibration variants in order to define their semantics. Based on these attributes it is possible to identify and filter variants. Furthermore data is automatically assigned from component libraries to datasets based on these attributes. > Calibration Matrix: The calibration matrix presents the available work packages, their instances (parameter set file variant) and the assignment to calibration variants. Via the calibration matrix, work package files can be exchanged. Export to and import from Excel is possible. Figure 14: Calibration matrix shows work packages, their instances and the assignment to datasets 13
> Derived variants: If there are only few differences between variants, this is best handled by derived variants (e.g. test bench versus street test variants). Most parameters in a derived variant originate from the basic variants. Only a small number of parameters are managed within the derived variant. Most values are reused of from the base variant. Changes in the base variant are dynamically resolved and immediately available within the derived variant. > Component libraries: Parameter set that represent a good base for new calibration variants could be managed in component libraries. Via the attribute, the library content can be automatically aligned with library data. Figure 15: Basic principle of component libraries > Dependency management of parameters: This function is elaborated in the proceeding chapter. 9 Managing Parameter Dependencies This function can be used to manage the dependencies between parameters and variant properties. This function has an enormous effect on the efficiency of the application process: > Data distribution to variants: Data can automatically be distributed to variants. The individual calibration engineer only requires a little knowledge about the structuring of the variants. > Consistency check: Variants can be automatically checked for consistency. 14
Figure 16: Identify and resolve inconsistencies via dependency management. > Automatic filling of variants: New variants can for the most part be prefilled from ongoing project data. Inconsistent variants are automatically repaired. 10 CDM Studio Editor CDM Studio is part of both CANape and vcdm, and it offers a number of important functions: > Graphic display of characteristic curves and maps: Characteristic maps can be compared to one another and can even be graphically placed within one another. Figure 17: Compare two maps graphically in CDM Studio 15
> Manipulating data: Data can be manipulated graphically or numerically. Refined functions are offered such as interpolation and value range checks at parameter manipulation. > Standalone mode: CDM Studio can also be used as a standalone tool. More details are elaborated within the CDM Studio product information document or the corresponding web page www.vector.com/cdm_studio. 11 Guided Working Mode New users and occasional users can quickly learn about the use cases of vcdm in the guided mode. The vcdm Client starts with the guided mode as the default mode for new users. Available actions are shown as a function of the existing data and the current role. In the example shown, the project manager logs on in a system without a project. So, the user must first create a project. Figure 18: Easy project creation because the project leader is guided through the process by a wizard The user is guided through the process of creating the project with the help of a wizard. Afterwards, what is known as the dashboard is opened, which shows the status of the project and presents the available actions. Figure 19: Fast overview of the project in the dashboard 16
The project manager is now automatically guided through the calibration process. Step-by-step, data variants (datasets) are created, calibration files are imported and merged, datasets are frozen, and program revision changes are executed. Only those actions are shown that it would make sense to execute in the given context. As in the project, each dataset also has its own dashboard that can be used to conveniently access all data and actions. The guided working mode restricts the functionality based on the role of the connected user. Calibrators can only import and export data and generate reports. The configuration of all these operations is supported by wizards. Figure 20: Startup screen for calibrators 12 E-Mail Notification > For many events in vcdm, it is possible to generate E-mail notifications. Recipients of the E-mail do not necessarily require an account for vcdm. Sporadic users can be invited to log in again. Managers can be informed if a series release is available. > Via a template mechanism, important information can be added to the E-mail. Example: If axes values have changed, the name of the affected dataset variants can be included in the E-mail. 13 Collaboration on the Road > To support calibration engineers during testing as well, a project and its datasets can be imported into a local database system. This system offers the same functionality like a centrally managed vcdm system. Application engineers mix their data, generate new datasets, and migrate existing datasets to new software levels. Calibrators merge their data, generate new datasets, and migrate existing datasets to new software levels. 17
> All team collaboration, report and data mining functions are available. > The import and export process is started by the users. But the actual data is asynchronously managed by the central and lightweight server system. The user can close the client application and does not need to wait until the operation is completed. 14 Data Exchange OEM / Supplier > If supplier and OEM operate a vcdm system, they can automatically synchronize the calibration data of the calibration variants. > The synchronization takes place time triggered without user interaction. > To loosely couple both systems, the data transfer takes place via file shares or FTP. The data transfer can be encrypted. To exclude data from the export (e.g. calibration remarks), data can be filtered. 15 Domain-specific Views Certain aspects of the calibration data require a transposed representation so that the expertise can be better recognized. An example is the memory-optimized storage of the parameter assignment of diagnostic functions, which can be read only from the parameter-oriented display. In this case, vcdm and CDM Studio provide a clear display of the situation with the Function Inhibition Matrix. Figure 21: Domain-specific expansion with the Function Inhibition Matrix Other domain-specific views can be integrated in vcdm as part of the standard product or on a customer-specific basis. 18
16 Documentation Calibration data can be documented in various ways: > Import of quality information from CDF 2.0 or PaCo format. > Post-documentation of parameter values following import of datasets or on the basis of datasets. > Documentation of application expertise of parameter definitions, functions, groups, or trouble codes. > Import of documentation from Excel or programming interface > Use of documentation in ready-made or customer-specific reports Figure 22: Documentation of functions (manage application expertise) 17 Automation > Extensive programming interfaces are available. They can be used in Visual Basic or C# programs to automate vcdm. > The vcdm server offers web service interfaces for integration in corporate applications such as product lifecycle management systems. > HEX names can be generated based on rules. 18 Training Classes In the framework of our training program, we offer various training courses and workshops on vcdm at our classrooms in Stuttgart and locally at our customers business sites. You will find more information on individual training events and dates online at: www.vector-academy.com 19
Get More Information Visit our website for: > News > Products > Demo software > Support > Training classes > Addresses www.vector.com