Altair EEvision™

Quick Start Guide

Introduction

EEvision is a server-based tool for the automatic schematic generation and on-the-fly exploration of E/E architectures and wiring harness CAD data. It takes as an input connectivity data in EDB format, which can be generated by a direct export from the used harness CAD tool, by a conversion of intermediate harness exchange formats (e.g. KBL), or by a direct import of a connectivity list in Microsoft Excel format. The client software provides a GUI to control all EEvision features for the display and exploration of E/E architecture data. EEvision including the GUI can be used as is, however, it is possible to fully integrate a GUI-less version of EEvision into e.g. a service tool (Windows, Linux, and cloud applications) and control it from there using its API.

Starting with an EDB file

Requesting the EEvision base URL, or starting the standalone executable will bring up the EDB file selection dialog (a screenshot is displayed on the right side). This EDB selection dialog lists all EDBs on the server. The demo environment comes with an automotive example EDB suv.edb, which contains 599 components and 3112 wires and supports all major EEvision features. Clicking EEvision BASIC or EEvision PRO loads the database and redirects to the EEvision GUI. The PRO version of the tool includes additional EEvision plugins, such as the Multicore window described below, but it requires extra licensing.

Starting with customer KBL files

If the connectivity input data is available as customer KBL files, then a separate converter tool is needed to convert the KBL files into one EDB file, before to continue with Starting with an EDB file. The document kbl2edb describes the details the usage of the converter tool. This converter tool kbl2edb is available in the package's edb directory and is a batch-only tool, controlled by command line arguments, to be called like:

kbl2edb options -o output.edb *.kbl

Starting with an Excel file

If the connectivity input data is available in Microsoft Excel format, then a separate converter tool is needed to convert the Excel file into an EDB file, before to continue with Starting with an EDB file. The document excel2edb describes the details of the required Excel-based input format. This converter tool excel2edb is available in the package's edb directory and is a batch-only tool, controlled by command line arguments, to be called like:

excel2edb options input.xlsx output.edb

Loading EDB Objects and Exploring the E/E Architecture

In the following, an object denotes an arbitrary element in the EDB database (component, connector, cavity, wire, multicore, or module).

Figure 2: EDB Live Search and Loading Objects

The Live search allows the user to search the complete EDB for object names and attributes (e.g. description, signal name, ...) and instantaneously lists the search results in the result window (Fig. 2). The search can be further restricted by selecting the desired object type and subtype. For each entry in the result window, the respective object can be loaded as a new schematic (Load), it can be added to the current schematic (+), or it can directly be extracted (>) -- see below for more information about extraction.

At each point in time, connected (but not yet shown) elements can be added incrementally resp. interactively by double-clicking the connected cavity, connector or component (Fig. 3). In case the schematic gets confusing over time, EEvision provides the opportunity to regenerate the schematic from scratch (Regenerate) or to perform local optimizations (Optimize, see also config.autoOptimize).

Figure 3: Incremental Navigation and Schematics Optimization

The main feature to explore the E/E architecture in the EEvision environment is the Extract function, which searches the database for the vicinity of an arbitrary selected object (a single click selects an object and shows its name in the search field) and displays the extraction as a new schematic (Fig. 4). For multiple selected objects (multiple selection by shift-click) Extract triggers an automatic path extraction and adds all objects and paths to the schematic.

Figure 4: Context Extraction

Exploration of Electrical Connectivity

When selecting a wire in Net mode, all electrically connected wires (through inline connectors and splices) are selected as well (Fig. 5). Clicking the Load button extracts all selected wires with the same electrical potential and shows them as a new schematic.

Figure 5: Showing Electrical Potential

The Info window opens a table showing all attributes of the selected object (Fig. 6). The same information is shown in a balloon window when right clicking the object in the schematic.

Figure 6: Showing Object Attributes

The balloon window is customizable and can be enriched by object specific images (e.g. showing the device or its mounting location).

Figure 7: Multicore Window

The multicore window (MC) shows a tree structure of all multicores which are visible in the current schematic (Fig. 7). Clicking a multicore or one of its wires in the multicore window selects and centers the respective objects in the schematic. Conversely, selecting a wire in the schematic marks its entry in the multicore window.

Activating the logical mode (More/Logical) restarts the current session and abstracts in a pre-processing step from purely connecting elements like inline connectors or splices. Thus, this mode automatically provides a logical view of the E/E architecture.

Grouping of Objects

EDB objects can be grouped by using EDB modules, which allow for example to define 100% configurations in order to filter a 150% EDB to a vehicle-specific database in a pre-processing step. Additionally, the information of objects belonging to specific functions or buses can be stored in modules, which can be loaded and displayed as a whole (Fig. 8). The example EDB suv.edb contains many function and bus modules accessible by selecting the object type Module in the search field.

Figure 8: Showing Functions and DTCs

EEvision Settings

The settings dialog (Fig. 9) allows to configure both the appearance of the schematics and the behavior of the search and extractor functions. The initial values are set in the eev.conf file (JSON format).

Figure 9: EEvision Settings Dialog

Among others, the following items can be configured in the settings dialog:

Copyright © 2018–2024 by Altair Engineering Inc.
All rights reserved.