Getting Started

Working on tractive systems (which includes but is not limited to engine(s), motor(s), inverter(s), high voltage battery packs and high voltage cables) requires special experience and training.

Incorrect installation or use of GEMS Electronic Control units (ECUs) or software may lead to electrical / mechanical damage, injury or even death. As such, installation must only be performed by users with experience with electronic control systems and a competence of Windows based computer software.

All accompanying documentation must be read thoroughly before installation is attempted.

If you are in any doubts regarding the fitting and use of this product, please contact your reseller or GEMS directly at tech.support@gems.co.uk

General Engine Management Systems (GEMS) Ltd shall not be held responsible for any mechanical or electrical damage or personal injury occurring whilst using this product. Neither shall GEMS be held responsible for damage, injury or death caused by the misuse, misunderstanding or miscalibration of this product.

Installing GWv4

Download and run the installer from gems.co.uk/downloads/software. For more details, see Installation.

Licensing GWv4

A license is required for useful operation of the software. There are different types of license that will allow different types of ECU to be used with GWv4.

Software licenses are installed via License....

For more details on software licenses and Dongles, see Licensing the Software.

GWv4 Quick Start

Upon starting GWv4 for the first time, the Quick Start window will be shown which offers some convenient links for commonly used features:

The Start Page The Start Page

The Quick Start page automatic popup can be suppressed by unchecking Show Quick Start At Startup. You can show the start page again at any time from Start Page.

Installing an ECU Definition File

Interaction with an ECU or Calibration file requires and ECU Definition File to be installed.

The easiest way to install ECU definition files (*.ecudef / *.gin / *.a2l) is to drag & drop the file from Windows File explorer onto the application. Alternatively when connecting to an ECU or opening a Calibration file the software will guide you through the process of installing one.

For more details, see ECU Definition Files.

Opening a Calibration File

A calibration file contains a copy of the ECU configuration memory - this contains all the values to which tables / maps / options have been calibrated. From the main menu select Open Calibration...Ctrl-O and select the calibration you wish to open, or New Calibration... to start a new calibration.

Starting from a blank calibration will typically be a lot of work to get up-and-running with. We would therefore recommend that a base calibration is used as a starting point rather than a blank calibration, depending upon your application. Many base calibrations are available online (gems.co.uk/downloads). Alternatively, contact GEMS.

Note

Calibration files are sometimes referred to as ‘map’ or ‘mapping’ files. This terminology could be confused with ‘map’ objects (e.g. The Fuel Map), so the term ‘calibration’ is used in the GWv4 software.

Working with Calibrations

Calibrations are conceptually made up of the following objects:

  • Maps - ‘Matrix’ objects with 2 input axes and a 3rd output value axis. This allows a value to be produced based on two other variables via a look-up table.

    For example, the Fuel Map maps Engine Speed and Engine Load onto an injection pulsewidth value. A map can be viewed as a 3D Map Graph, Map Grid, or Map Slice.

  • Tables - ‘Vector’ objects with a single input axis and an output axis. This allows one value to be produced based on the value of another via a look-up table.

    For example Boost limit outputs the channel Boost Limit, based on an input Engine Speed. Tables can be viewed as a Table Graph or a Table Grid.

  • Options - ‘Scalar’ objects - options represent a single values that can be changed by the user - for example Fuel Cut.

    Options can be displayed in a Option Full List or a Option Selection List.

The values of all these objects collectively defines the calibration.

All the available objects for the ECU that is currently loaded into the workspace are displayed in the Views.

To upload the current calibration to the ECU from the main menu select: ECU | Upload Current Calibration, or click the ‘Upload Current Calibration’ button on the tool bar. This will connect to the currently connected ECU and upload the calibration into it.

For more please read the Calibrations section.

Channels / Measurements

Channels can also be viewed in GWv4. Channels are updated in real-time by the ECU and are not stored within the ECU’s configuration. So channels are not part of the Calibration; rather they are readings / measurements of current values - for example Engine Speed.

Channels can be viewed as:

Note

In prior versions of GWv4, Channels were known as Parameters. Since this has overlap with the semantically different Simulink.Parameter, the naming was changed to Channels. Scalar (single-valued) Simulink.Signal values map onto Channel, as do scalar A2L MEASUREMENTs. Channels are always scalar values. However, it is possible to have Table or Map objects that are not stored in the Calibration and are essentially Measurements.

Setting up the Workspace

GWv4 has a very flexible workspace with many objects for displaying and edit your calibration in the best possible way. See the Workspace and Tabs sections for more details.

Connecting to an ECU

  1. Check that your communications lead is properly connected.
  2. Check your Connection Settings.
  3. Check that your ECU has power.
  4. Click ‘Connect’, or Press Shift+F7. When you connect, the calibration in the ECU will be downloaded and displayed.

If you are having problems connecting, refer to Connection Troubleshooting.

Storing ECU Changes Permanently

Depending upon the ECU type / configuration, changes made to the Calibration whilst ‘online’ to the ECU may not be ‘saved’ in the ECU immediately.

Either use Auto Store to turn on automatic storage, or manually store changes using Store Changes in ECUCtrl+K.

See Storing Calibration Changes Permanently for more details and a discussion on why this is optional.