vcdm 6.8 feature presentation€¦ · > c#-based value rules (for computation / checks) and >...

V2.0 | 2020-01-08

Webinar 8-Apr-2020

Mastering Emission- or Safety-Critical CalibrationsFeature Presentation vCDM 6.8

2

THIS IS NOT A PRODUCT SPECIFICATION The information contained in this document represents the current view of Vector on the issues discussed as of the date of publication. Because Vector must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Vector, and Vector cannot guarantee the accuracy of any information presented. This document is for informational purposes only. Vector MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Vector may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to the patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Vector.

Vector does not make any representation or warranty regarding specifications in this document or any product or item developed based on these specifications. Vector disclaims all express and implied warranties, including but not limited to the implied warranties or merchantability, fitness for a particular purpose and freedom from infringement. Without limiting the generality of the foregoing, Vector does not make any warranty of any kind that any item developed based on these specifications, or any portion of a specification, will not infringe any copyright, patent, trade secret or other intellectual property right of any person or entity in any country. It is your responsibility to seek licenses for such intellectual property rights where appropriate. Vector shall not be liable for any damages arising out of or in connection with the use of these specifications, including liability for lost profit, business interruption, or any other damages whatsoever. Some states do not allow the exclusion or limitation of liability or consequential or incidental damages; the above limitation may not apply to you.

DISCLAIMER

3

� vCDMstudio

Project Explorer

Parameter Value Rules / Checks

Log File Improvements

Support Additional Databases

Agenda

4

vCDMstudio - Redesigned Interface With Ribbon and Application Menu

vCDMstudio

� Same look and feel like as in CANape

� Restructuring the old menus that had too many entries

� File operations are now all in the application menu (Backstage)

Backstage

5

� Classifications (ie. relevant for safety, emissions) can be assigned to parameters (A2L Annotations)

� The feature can be activated by a new vCDMstudio Option

� Classified parameters are highlighted in vCDMstudio

� Classifications can be displayed as attribute columns

� Parameters can be filtered by classification

� Parameter changes on classified parameters are logged

Parameter Classification

vCDMstudio

/begin CHARACTERISTIC ampl

“Amplitude"

VALUE 0x28278 __UBYTE_S

0 ampl.CONVERSION 0 150

/begin ANNOTATION

ANNOTATION_LABEL

“Emission"

ANNOTATION_ORIGIN

"PARAMETERCLASSIFICATION"

/begin ANNOTATION_TEXT

“Annotation line 1"

"Annotation line 2"

/end ANNOTATION_TEXT

/end ANNOTATION

A2L Example Definition Display as attribute columns Display parameter properties

6

vCDMstudio – More Features

vCDMstudio

� New window type for comparing multiple parameter sets

� Information about the calibration process of all loaded parameter sets

� Fast switching between different sorting criteria

� New Popup-Menu to sort to dedicated attributes

� Merging of parameter sets

� Improvement of the message or error analysis after the action has been executed

� Additional filters for main categories

7

� It is now possible to deliver files (parameter sets) into vCDM from vCDMStudio Main perspective

� License “Option vCDM” or “Rich Client” required

� Parameter set must be opened with A2L

� Delivery possible into datasets, component libraries or project inbox

� Alternative approach to dataset management (Upload/Download datasets into vCDMstudio)

Parameter sets import from vCDMstudio (Main perspective)

vCDMstudio

12

Impressions

vCDMstudio

� CANape Option vCDM in vCDMstudio connects the local dataset management with the server-based calibration projects and their datasets

Get datasets from vCDM Server

Connect to vCDM Server with user/passwordDeliver a parameter set to a vCDM Server Calibration Project

Submit your local changes

Update local dataset project

13

To access vCDM Server calibration data,

simply click Get Datasets

Download vCDM Calibration Projects to vCDMstudio

vCDMstudio

vCDM Server LoginSelect vCDM Calibration Project

Select Datasets

Select local folder

� The dataset are now available on the local PC.

� The “Shared” icons indicates that these dataset are connected to a central project

14

Offline calibration edit / copy / compare

vCDMstudio

� Dataset can be

edited and compared

with local calibration

data

Local calibration dataLocal datasets, with origin in vCDM Server

15

Upload of calibration changes to the vCDM Server

vCDMstudio

To submit your changes to the vCDM Server Project,

Simply click “Upload Changes”

The local changes are analyzed..

..displayed for review..

Change dataset

Add comments or attachments

.. Delivery files generated..

.. And assigned to the target vCDM Server datasets.

16

Conflict Management

vCDMstudio

Conflicting changes (the calibration is already changed by a different user) are indicated.

To solve conflicts, simply click “Merge in conflict resolution view”

Conflicting parameter changes

by other users are indicated,

and conflicts can be resolved.

17

Change Tracking for calibration changes

vCDMstudio

The change history of the

Server project shows every

change of calibrations over time.

18

vCDMstudio

� Project Explorer




Agenda

19

Motivation

Project Explorer

Reasons for change

� Replace configuration tree for projects and datasets

� Many new possibilities to structure and display projects (realized in last versions)

� Realize last major item: Display attribute values in project explorer

� Close some minor functionality gaps

20

Attribute as Columns

Project Explorer

21

� To select the columns use the Ribbon View | Options | Configure columns


Project Explorer

22

� Or via the context menu on the columns


Project Explorer

23

� Available in Project Explorer and Configuration tree – only for Datasets without workpackages!

� All datasets in vCDMstudio are editable

Edit multiple datasets simultaneously

Project Explorer

24

vCDMstudio

Project Explorer

� Parameter Value Rules / Checks



Agenda

25

� Unified concept:

The previously existing

> C#-based value rules (for computation / checks) and

> Parameter range checks

have been merged into a new common concept*.

� It is clearly distinguished between> Check rules

> Computation rules (automatically modify value)

� The best of both worlds is provided:> C#-based scripting rules (Most powerful, But: Needs coding skills)

> Predefined value (check) rules (Very intuitive to use)

> Somehow „between both“: Expression / formula – based rules

� Management, UI, Export/Import and Logging have been improved

� Rule execution integrated in most relevant use cases

*Side note for existing users: Migration may need manual steps (Done by Vector Support upon request)

Overview


26

� Range(Min, Max)

> Range check for parameters for lower and/or upper value

> Applies for scalars, axis, curves, maps, value blocks(1D/2D)

> New in 6.8: Range check considers quantization („same HEX value“ paradigm)

> NOTE: The feature „Dataset Validation Range Checks“ is replacedExisting Range checks are migrated to the new method

� Envelope(Min, Max)

> Dimensional range check for parameters for lower and/or upper shapes

> Applies for axis, curves, maps, value blocks(1D/2D)

> Simple import and edit using vCDM Studio and parameter set files

� Gradient(Max)

> Check for gradient (delta_x / delta_y) of the function values for a dimension

> Applies for curves, maps, value blocks(1D/2D)

� Monotony(Monotonous | strictly)

> Monotony check for axis

> Applies for axis, curves, maps

New Predefined Parameter Value Checks


27

Parameter Value Rule Editor: Example for Monotony rule


28

� Expressions are a compromise between predefined rules and explicitly coded rules> Aligned with formulas in A2L standard (Dependent Characteristics, Conversions)

> C/C++/C# Style

> Arithmetic operators + - *, Logical operators (And/Or), Bit Operations (e.g. Bitmasks), Some Math functions like Sin(), for details see A2L standard

> References to multiple other parameters are possible

> Input field for expression (like Excel formula) => In later versions probably a full-blown editor will be provided

Expression rules


Example:

Value of myParam must be > 0 if bit5 of myFeatureControllingParam is set

((phy(X1)>0)||(phy(X2)&0x0010000=0)

29

Multiple rules for the same parameter can be defined in a so-called „ruleset“

� Rulesets can either be defined:

� Directly on software level

� As independent objects, and linked into the software („Create ruleset container“ in ribbons)

� Multiple „Rulesets“ (e.g. for different types of checks / different responsibles) can be added

� Planned for future versions: Define rulesets on project level

� Accessible via software dashboard

� Project explorer with „software nodes in tree“ or

� „Software“ dashboard page on project + zoom

� Export and import

� Via XML (All rule types) or

� Via 2 Min/Max Parameter Sets (e.g. CDFX File) as reference values => Envelope / range checks

� Multiple rules now possible for one parameter

� Especially needed for non-scripted rules

� Improved storage: Rules are stored more performant and efficiently in database.

Ruleset management


30

Ruleset management


34

Parameter Value Rules can now be executed on additional use cases:

� Dataset Check-in / HEX Freeze

> Check rules and computation rules (Result is written into calibrated content , then copied into HEX)

� Export HEX / Parameter sets

> Check rules are executed.

> Computation rules are only done local within export file, not written back into calibrated content

> On frozen datasets, no rules are executed (Dataset is consider as „confirmed and locked“)

� Calibration file import

> Only check rules are executed. No dataset context, checks are done on source files + A2l!

� Behavior can be configured on domain or project level (Page „Value Rules“)

� Check parameters

> Optional - Like other checks. Cannot be pre-configured

� Additional information for existing C# script users

> Use case context is passed in. Note that if checks are activated for delivery, no dataset context is passed-in. If you want to use your existing C# scripts and activate checks at delivery, please review them (see vector-provided templates for details

Use case integration


36

Use case integration


37

� The execution of value checks / rules is tracked to support safety and emission compliance

� This is done on the following use cases > Dataset Checkin / HEX Freeze

> Explicit „Execute value rules“ action

� Log files are automatically created and available via log viewer> „Data processing logs“ tab on dataset dashboard, (See also separate chapter on logging in this presentation)

> „State“ clearly indicates what happened

> Checks: Ok, Not ok, Fatal errors (e.g. error in user-defined C# rule), Value to check was not available

> Computation: OK and value changed, OK but same value as before, Fatal Error

Improved logging


39

vCDMstudio

Project Explorer


� Log File Improvements


Agenda

40

� Alternative “Data Processing Logs” View

� “Flat List” mode allows to simply filter log messages (via Type Ahead)

Log file dashboard


42

� More detailed state, e. e.g. on freeze distinguish between

� “Value identical” (Everything OK, same HEX value) and

� “Copied” (New value in HEX) and

� “Copied but modified by system” (e.g. set to A2L limits)

� New “Category” that is oriented on impact for calibration

� Error: User should review and fix problem (e.g. copy failed)

� Items to review: No error, but maybe impact for calibration (New parameter, changed value for default data) => Everything that may affect the calibration and changed from “outside” calibration (SW development)

� Items changed: Regular change. E.g. changed value in HEX, changed default data on software change

� No change: Everything OK and same value

Status Handling


43

� Additional improvement

� Zoom button

� Export LAB file reworked (Exports filtered amount)

� Filter “Only mine” (based on parameter permissions)

� Export Files (via Ribbon) allows export of underlying XML file (for automatic processing)

Improved dashboard


44

� Also available in vCDMstudio

� Concept like “interactive” copy log

� Directly jumps to values

� Hint: Currently only via “Option vCDM” (not via “Edit Dataset from Rich Client”)

Log file viewer in vCDM Studio


45

vCDMstudio

Project Explorer



� Support Additional Databases

Agenda

46

Motivation


Current situation

� Only Oracle supported as database (11.2g and 12.1c)

Reasons to change this

� Oracle license policies are complex and prohibitive

� Oracle database management has notion of complexity

� Oracle in the cloud only possible with special contracts

� Reduce architecture complexity of vCDM server

47

� vCDM supports Oracle (12c / 18c / 19c) and MariaDB, starting with Version 6.8

� “MariaDB Server is one of the most popular database servers in theworld. It’s made by the original developers of MySQL and guaranteed to stay open source. Notable users include Wikipedia, WordPress.com and Google.” (Source: www.mariadb.org)

� All vCDM functionality is available on both DB platforms

> Limitations for vCDM 6.8 @ Maria DB

> Maximum 30 users

> Only one (1) vCDM Domain

> No customer-specific configurations

> Use-case permissions only on project-level, not dataset-level

� Constraints

> No data migration of existing installations from Oracle DB to MariaDB

� Requirements for vCDM 6.8 on MariaDB

> MariaDB 10.4.<latest-stable> + DB Client (mariadb-java-client-2.4.x.jar) -> both available on https://mariadb.org/download/ for free

vCDM with MariaDB


Additional reading: www.mariadb.org

48

� The availability of MariaDB as database concludes an internal project

� This project spanned across 3 vCDM versions

� Although unnoted – it affected also the existing database implementation with Oracle

> Oracle-Only implementations were replaced by generic implementations

� Performance considerations:

> As part of our product quality assurance we benchmark the performance across versions

> A suite of test cases is executed on a regular basis

> These test case track the performance of typical vCDM use-cases

> V6.8 Test results indicate a 20% performance gain over V6.6 for selected use-cases – both on Oracle

Note:

Performance results vary depending on system sizing, system load and use-cases

Test results on customer system may exceed these results, or might show worse results

vCDM with MariaDB


49 © 2019. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V2.0 | 2020-01-08

Author:Michael VogelVector Germany

For more information about Vectorand our products please visit

www.vector.com

vcdm 6.8 feature presentation€¦ · > c#-based value rules (for computation / checks) and >...

Documents