EDIABAS User's Guide Page 1 of 117

EDIABAS User's Guide

· User Manual/Installation Guide

· Error Reference

· ECU Simulator

EDIABAS User's Guide

User manual and installation guide

More:

1. Revision history

2. Introduction

3. General

4. Installation and administration

5. Help programs

EDIABAS User's Guide > User manual and installation guide

1. Revision history
Version 3.0 Created overview and User Manual/Installation Guide

Version 3.0A Combined above documents

Version 3.0B Added Rev., Glossary and Introduction
Version 4.1 Revised for EDIABAS V4.1.0
Version 5 Revised for EDIABAS V5.1.0
Version 5a Extended for EDIABAS V5.5.0
Version 5b Extended for remote diagnostic Win32
Version 5c Configuration for IFH Trace
Version 5d Revised the XTRACT output functionality
Version 5e Extended for QNX

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 2 of 117

Version 6 Extended for EDIABAS V6.0.0

Version 6c Revised for EDIABAS V6.4.4
Version 7a Extended for WinCE
No more support for DOS, Win16, QNX
No more support for Win9x/98/ME
Extended for EDIABAS V7.1.0
BEST/2-Compiler for Win32
Support for Pocket PC 2005/Windows Mobile 2005 (WinCE),
XTRACT with optional XML output
Version 7b Extended help programs for EDIABAS V7.1.6
Version 7c Revised for Pocket PC 2003/Windows Mobile 2003 (WinCE),
Description of XEthernet parameters related to ediabas.ini
No more support for SCO UNIX
Version 7d Extended for EDIABAS V7.2.0
Support for Windows Vista (Win32)
Version 7e Extended for EDIABAS V7.2.0
Revised configuration overviews
Revised for Tracer extensions
Version 7f Extended for EDIABAS V7.2.0
Revised delivery overviews
Version 7g Extended for EDIABAS V7.2.0
Revised delivery overviews
No more support for Pocket PC 2005/Windows Mobile 2005 (WinCE)
Version 7h Extended for EDIABAS V7.2.0
Revised configuration overview
Version 7i Revised for EDIABAS V7.2.0
Version 7k Extended for EDIABAS V7.2.0
Revised delivery overview (XNUL)
Version 7l Extended for EDIABAS V7.2.0
Revised delivery overview (BestView online help)
Version 7m Extended for EDIABAS V7.2.0
Revised delivery overview (.NET4.0/VC2010/Win7SDK)
Version 7n Extended for EDIABAS V7.2.0
Revised configuration overview for XEthernet
Version 7o Extended for EDIABAS V7.3.0
Support for Windows 7 (Win7)
Revised delivery overview (BEST2, BEST2WIN)
Extended for help program PE (exit codes)
Version 7p Extended for EDIABAS V7.3.0

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 3 of 117

Support for Win64 (x64)

EDIABAS User's Guide > User manual and installation guide

2. Introduction
More:

2.1 About this manual

2.2 Notational conventions

2.3 Special features, terms, acronyms

2.4 Trademarks

EDIABAS User's Guide > User manual and installation guide > 2. Introduction

2.1 About this manual

This manual describes how to operate the EDIABAS (Electronic Diagnostic Basic System).

EDIABAS User's Guide > User manual and installation guide > 2. Introduction

2.2 Notational conventions

The following typographical conventions are used throughout this manual:

Example Description
SAMPLE.B2V Uppercase denotes file names, registers and operating
system commands.
job, string, while Bold-faced type identifies keywords and operators of the
language BEST/2 and BEST/s as well as the API functions.

These words must be written exactly as specified in syntax

descriptions.
expression Italics designate placeholders for values to be entered by
the programmer; e.g., file names.
[option] Words enclosed in square brackets may be optionally
specified.
{ result | Curvy braces and vertical strokes characterize entries from
argument } which only one must be selected, except when in square
brackets.
[constant...] job... An ellipsis (three dots) which directly follows an
expression indicates that several expressions of the same

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 4 of 117

type can follow.

hallo="Test"; This syntax designates examples, user entries, program
outputs and error messages.
while() { A column or a row comprising three dots indicates that a
section of an example was intentionally omitted.
.

.}
[1] Reference to a document in References.

EDIABAS User's Guide > User manual and installation guide > 2. Introduction

2.3 Special features, terms, acronyms

An explanation of abbreviations used in this and all other EDIABAS documentation can be found
in chapter "GLOSSARY".

EDIABAS User's Guide > User manual and installation guide > 2. Introduction

2.4 Trademarks

Microsoft, MS, MS-DOS, Windows, Windows Vista, WIN32, WIN64 and Pocket PC are registered
trademarks of the Microsoft Corporation.

SCO, SCO UNIX and OpenServer are registered trademarks of Santa Cruz Operation, Inc.

EDIABAS User's Guide > User manual and installation guide

3. General
More:

3.1. Diagnostics and coding of ECUs

3.2. Problem definition

3.3. Approaches to problem solving

3.4. Implementing solutions with EDIABAS

3.5. Structure

3.6. Job concept

3.7. Description language BEST

3.8. Sequences

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 5 of 117

3.9. Availability

EDIABAS User's Guide > User manual and installation guide > 3. General

3.1. Diagnostics and coding of ECUs

ECUs (Electronic Control Units), are developed by various participating members including
component suppliers of the Automobile Industry, vehicle manufacturers themselves and
contractors. The ECUs tested and produced by suppliers are installed in the vehicle by the
automobile manufacturer, if applicable coded (programmed) specifically for the vehicle via their
diagnostic interface and tested for proper functioning in the vehicle. Whenever an error occurs, the
cause of error is determined and remedied by means of "Electronic Diagnostics" accompanied by a
computer-based testing system. After the vehicle has been delivered, errors occurring within the
scope of "Inspection and Service" are corrected in the shop. Once again, "Electronic Diagnostics"
are applied. When an ECU is swapped in the shop, the defective unit is repaired by the
manufacturer, and its proper functioning is tested, by means of "Electronic Diagnostics". The newly
installed ECU may need to be re-coded again on the premises according to vehicle specifications.

In accordance with this life cycle, coding and testing ECUs is an often recurring and prescribed job
duty for:

• Development of the ECU

• Testing of the ECU in the test lab

• Tests in the test vehicle

• Manufacturing of the ECU

• Final inspection of the ECU

• Installing and checking of the ECU in the pre-assembly

• Vehicle-relevant coding of the ECU

• Function test in the vehicle

• Final inspection of the vehicle

• Servicing or debugging in scope of Customer Service

• Replacing and re-programming in the shop

• Repair of the ECU

EDIABAS User's Guide > User manual and installation guide > 3. General

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 6 of 117

3.2. Problem definition

If a large number of ECUs which, in part, have been developed and supplied by several
manufacturers are employed in several model series of vehicles, an extremely high percentage of
ECU fluctuations results, since the on-going advancements of the subsystems occur in the life span
of a vehicle series. In comparison, engines can be considered which are employed in several
different designs in the same body of a vehicle series.

Due to the discontinuation and new use of ECUs as well as technical changes to ECUs, the
modifications required in coding and testing systems (modification, commissioning, test) increase
over-proportionally. The expenditure of documentation and the risk of errors increase.

Due to intense »dissection« of tasks in large companies and sequential procedures, the steps
mentioned above lead to multiple processing, extending from the development of an ECU via
production to Customer Service:

Bild 3.2-1: Previous state

Coding and testing programs are individually created in diverse areas: At the ECU developer; in the
test department; in pre-production; in customer service; ECU repair center. This means, based on
the documentation pertaining to an ECU, the steps involving development (or advancement) and
testing of programs are repeated more than once! The apparent differences in the job definitions
and objectives of the individual phases discourage the view for mutuality, namely each the same
component ECU.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 7 of 117

EDIABAS User's Guide > User manual and installation guide > 3. General

3.3. Approaches to problem solving

The identical parts of the system mentioned above can be used multiply by all application programs
following a non-recurring development phase. This occurs in sense of a type »operating system«
developed for ECU communication, for which a matching »communication driver« is provided for
each ECU.

Bild 3.3-1: Desired state

Hence, similar to how a conventional operating system conceals information behind special
functions (e.g., about precise access to hard disks/to the screen), this »operating system« also
conceals the exact information about access to an ECU.

This »operating system« is not fixed to the application programs or even combined with one
another in data regions. Instead, it only provides »services«. These services can be issued from the
application program and are subsequently processed (when desired) time independently of these.
The result of this »service« can then be processed by the application after it has been executed. The
application program (the Client) and the operating system (the Server) only exchange
messages and data with one another.

The Server translates, the raw data received from the ECU into the symbolic data requested by the
application program.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 8 of 117

Bild 3.3-2: Compiler function

In this process, the Server, itself, is not equipped with its own intelligence, but stores its knowledge
about the individual ECUs in easily (i.e., even at runtime) exchangeable data modules. These data
modules contain the complete (or only the required) knowledge about translation of the binary ECU
data into symbolic data.

Each Client (i.e. application program) is provided with a software interface that conceals the
operating system-dependent part for exchanging the messages under a uniform procedural
interface. Several application programs can send their jobs to the server in time-sharing mode; i.e.,
as soon as an application program frees the server, the next pending job can be processed.

EDIABAS User's Guide > User manual and installation guide > 3. General

3.4. Implementing solutions with EDIABAS

All approaches for problem-solving mentioned above have been implemented in EDIABAS.
EDIABAS can therefore be regarded as an »operating system for communication with ECUs
in Client/Server architecture«. Since, however, the term »operating system« would be extremely
confusing in this relationship and, in this case, a common basis for other application programs
would be created, the term »Basic System« has been used by Softing. This "Basic System" in
"Electronic Diagnostics" is called:

Elektronic DIAgnostic BASic System = EDIABAS

EDIABAS User's Guide > User manual and installation guide > 3. General

3.5. Structure

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 9 of 117

EDIABAS has a fixed structure independent of the operating system employed.

Bild 3.5-1: EDIABAS structure

Figure 3.5-1 illustrates the basic structure of the individual sub-components as well as the data and
communication paths.

The ECU-specific knowledge of EDIABAS is stored in the ECU description files (SGBDs). The
ECU description files are created "variant orientated"; i.e. exactly one variant-specific ECU
description file (SGBD) exists for each ECU variant. A superior, group ECU description file can
exist for all ECUs of a group (in general, these are ECUs with the same address). Which variant of
this group is connected to the diagnostics bus can be determined using the methods contained in
this file.

The ECU description files are loaded and interpreted by the EDIABAS runtime system when

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 10 of 117

instructed by an application program. The file name of the ECU description file (no extension) is
the name with which the application programs reference an ECU "variant" or ECU "group".

Bild 3.5-2: ECU description file and group ECU description file

The main constituent of EDIABAS is the "runtime system". This runtime system can be
subdivided into three essential parts:

• Sequence control (kernel)

• ECU description file interpreter (SGBD Interpreter)

• Interface Handler (IFH)

Sequence Control determines the behavior of the entire system and contains the communication
interface to the application programs. It is responsible for the file and error management.

The ECU description file interpreter (SGBD Interpreter) converts the binary ECU data into
symbolic data. It interprets the data, files, methods and sequences contained in the ECU description
file, initializes the communication with the ECU and returns the self-determined results of the
sequential control for forwarding to application program.

The Interface Handler (IFH) is an exchangeable software module which, depending on the
hardware interface employed, can be integrated in various versions by the user. A data request to
the ECU is transposed by the Interface Handler into a job for the currently applied hardware
interface. The data returned from this interface are appropriately filtered from interface-dependent
parts and, in this way, can be evaluated independent of the interface hardware used. Even the errors
returned from the interface are standardized to the internal error messages. In addition, the Interface
Handler provides simulation of ECUs. Thus, EDIABAS-based application programs can also then
be tested when the applied ECUs do not exist.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 11 of 117

In order to simplify access to EDIABAS, a software interface is linked to each application program.
This interface controls access to EDIABAS via a pre-defined procedural interface. This so-called
»Application Programming Interface« (EDIABAS-API) handles the system-dependent
communication of the runtime system. The data received from the runtime system are managed
within the EDIABAS-API for the application program. In this way, the runtime system is freed
from managing this data, therefore allowing it to be structured considerably compacter.

EDIABAS User's Guide > User manual and installation guide > 3. General

3.6. Job concept

As already shown in the general approaches of problem-solving, EDIABAS, as Server, offers

"services" to the Clients. These services are called Jobs. A job is a self-contained task to read and
evaluate data from the ECU. It may be called at any time without consideration of the job sequence
(principle of independence). After completing processing, the job returns results which can be used
by the application program. The jobs are not permanently programmed in EDIABAS, but are a
constituent of the "ECU description files" (SGBDs). They are labeled according to their function;
e.g. READ_ERRORMEMORY or READ_ENGINESPEED. There are also jobs which are
automatically called by the runtime system and therefore "must" or "may" exist in each description
file. These include the job INITIALISIERUNG, (initializes the ECU description file), the optional
job ENDE (de-initializes the ECU description file) and the job IDENTIFIKATION in a group
description file (determines the currently installed ECU variant).

EDIABAS User's Guide > User manual and installation guide > 3. General

3.7. Description language BEST

Jobs are formulated in an own description language for ECUs called BEST (BEschreibungssprache
für STeuergeräte). This description language exists in two variations. The first variant is a low-
level, assembler-similar language called BEST/1. The second variant is the high-language version
BEST/2 with 'C'-like syntax.

In general, all ECU description files are written in BEST/2. In BEST/2, jobs are defined similar to
functions; i.e., a job header exists which lists all I/O parameters. Variables and fields can be defined
and used within a job. All necessary arithmetic operators are variable. An extensive library contains
functions for manipulating data and communicating with the ECU. The language, itself, contains
almost all control structures known by 'C'. The ECU description files defined in this way must be
converted into a format which can be read by the runtime system. This must be performed using a
compiler (BEST2/BEST2WIN) prior to use in EDIABAS. On one hand, this occurs because of
performance reasons and, on the other hand, so that syntax errors can be excluded during the
runtime.

The Source Text Debugger BestView is available to test the compiled BEST/2 description files.
By means of BestView, the sequence of a job can be exactly tracked: variable contents can be
monitored, displayed and modified.

EDIABAS User's Guide > User manual and installation guide > 3. General

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 12 of 117

3.8. Sequences

A job is issued in the application program by means of the API functions apiJob, apiJobData or
apiJobExt. These functions require at least two specifications: First, the ECU to be addressed (or
the ECU group) and, second, the job which is to be executed.

These two specifications are sent to the EDIABAS runtime system. The runtime system first
determines whether this data concerns an ECU "variant" or an ECU "group". If a group was
addressed, the job IDENTIFIKATION in the group description file is automatically processed. If a
valid ECU variant was determined from the job IDENTIFIKATION, the associated variant file is
automatically loaded with the assistance of the result VARIANTE as if the name had already been
transferred from the application program. The variant file processes the job requested by the
application program. A job may either appear directly in the variant file or in the base file. Base
files are ECU description files referenced from the variant file and which can be considered as a
part of the variant file. Afterwards, the results of this job are made available to the application
program.

Whenever a description file is re-addressed (i.e. after each change), first the job ENDE of the last
loaded ECU decryption file is called. This call is made only when the job ENDE exists in the file. It
enables the hardware to be de-initialized. Afterwards the job INITIALISIERUNG is called in the
new description file. This job must exist in each description file (obligatory) and can be used to
initialize the interface hardware. Only now is the specified job executed. When the same job is
called again, no standard job is executed anymore.

If an error occurs in one of the sub-components when processing a job, processing is immediately
aborted, and an error message is returned to the application program. In this case, any results are
deleted. In this situation, the job INITIALISIERUNG is automatically called again before re-
calling the same job.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 13 of 117

Bild 3.8-1: ECU description file and job selection

As a job is being processed, its commands are sequentially interpreted. Any communication
requests to the ECU are forwarded by the Interface Handler and processed. The results determined
are sent to the application program.

Applikation EDIABAS Steuergerät

int data;

apiJob("DMEV3",

"READ_SPEED"...);
job ( name:
READ_SPEED;

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 14 of 117

result: SPEED;

type: integer

... ) {

char response[];

send_and_receive
(response,
tel_readspeed);
-> 59 04 02 03
<- 59 05 03 05
05
SPEED=response[3]*256
+

response[4];

}
apiResultInt
(&variable,
.........”SPEED”,
set);

printf("Speed: %
d",variable);

Bild 3.8-2: Job sequence

The application program can read the results delivered by EDIABAS by means of the function
apiResultXXX, whereby various formats are supported. In this process, data is converted whenever
possible. Thus, for example, the result speed (e.g. rpm) which was calculated as integer in the
description file can be requested in real format by the application program.

EDIABAS User's Guide > User manual and installation guide > 3. General

3.9. Availability

The EDIABAS runtime system and the EDIABAS application development environment have been
designed as easy-to-port systems. They are presently available for the following platforms:

• MS-WINDOWS 7/XP (WIN32/x86)

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 15 of 117

• MS-WINDOWS 7 (WIN64/x64)

Throughout this manual MS-WINDOWS is used for WIN32/WIN64.

The development environment for ECU description files is only available under MS-WINDOWS.

EDIABAS User's Guide > User manual and installation guide

4. Installation and administration

More:

4.1. Delivery packages

4.2. System requirements

4.3. Installing for the first time

4.4. EDIABAS program paths

4.5. EDIABAS configuration

4.6. Start and terminate EDIABAS

4.7. Un-install

4.8. Protection mechanism

4.9. Remote diagnostics

4.10. Proxy Operation

4.11. EDIABAS Parallel Operation

4.12. EDIABAS controller service

4.13. EDIABAS Multi-Threading operation

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.1. Delivery packages

A total of three delivery packages are currently available. The scope of function is explained in
detail in the following sections:

• RUNTIME SYSTEM
• APPLICATION DEVELOPMENT KIT

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 16 of 117

• BEST DEVELOPMENT KIT

More:

4.1.1. RUNTIME SYSTEM

4.1.2. APPLICATION DEVELOPMENT KIT

4.1.3. BEST DEVELOPMENT KIT

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages

4.1.1. RUNTIME SYSTEM

The delivery package RUNTIME SYSTEM available for all systems listed in section
"Availability". This package is the basis for all other EDIABAS delivery packages. RUNTIME
SYSTEM must always be installed.

The delivery package allows application programs to run diagnostic sequences via EDIABAS.

More:

4.1.1.1. Files for WIN32

4.1.1.2. Documentation

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages > 4.1.1. RUNTIME SYSTEM

4.1.1.1. Files for WIN32

The RUNTIME SYSTEM contains the following files:

README32 Installation notes

BIN\<password file> Name of password file (8 characters). The file has no
extension.

Example: 07DE3473
BIN\API32.DLL Access to the EDIABAS runtime system (WIN32)
BIN\API64.DLL Access to the EDIABAS runtime system (WIN64)
BIN\API64.EXE WIN64/WIN32 API mapper
BIN\APINET32.DLL Access to the EDIABAS runtime system via .NET framework
(WIN32)
BIN\APIVB32.DLL Access to the EDIABAS runtime system for Visual Basic
(WIN32)
BIN\APIVBNET32.DLL Access to the EDIABAS runtime system for Visual Basic

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 17 of 117

via .NET framework (WIN32)

BIN\BESTINFO.EXE Display of BEST object file contents
BIN\BESTVER.EXE Version test of BEST object files
BIN\EBAS32.DLL EDIABAS runtime system (WIN32)
BIN\EBAS32.EXE EDIABAS visualization (WIN32)
BIN\EBASCC32.DLL Access to the EDIABAS controller service
BIN\EBASCS32.EXE EDIABAS controller service
BIN\EBASMT32.DLL EDIABAS multi-threading runtime system (WIN32)
BIN\EBASMT32.EXE EDIABAS multi-threading help process (WIN32)
BIN\EDIABAS.INI.Example EDIABAS configuration file example
BIN\IFHPRO32.EXE IFH proxy
BIN\IFHSRV32.EXE IFH server for remote diagnostics
BIN\NETPRO32.DLL Helper DLL for network access
BIN\NETTCP32.DLL Helper DLL for network access
BIN\NMSIFH32.DLL IFH service for remote diagnostics via XREMOTE
BIN\PE.EXE Password Editor
BIN\RDRIFH32.EXE IFH Redirector for proxy operation
BIN\SDKHLP32.DLL Helper for Win7 SDK
BIN\STRIP.EXE Remove the debug and help texts in BEST object files
BIN\TRACEX32.DLL Trace access
BIN\TWFILE32.DLL Trace writer for local file output
BIN\VMC32.DLL Access to connecting management for remote diagnostics via
XREMOTE
BIN\VMCICOM32.DLL Access to connecting management for remote diagnostics via
XRPLUS

Note: Not included in the standard delivery!

BIN\VMFCHK32.EXE Helper process for connecting management

Note: Not included in the standard delivery!

BIN\XEDIC32.DLL IFH for EDIC
BIN\XEDICC32.DLL IFH for EDICC

Note: Not included in the standard delivery!

BIN\XENET32.DLL IFH for Ethernet

Note: Not included in the standard delivery!

BIN\XNUL32.DLL IFH dummy
BIN\XPROXY32.DLL IFH for proxy operation
BIN\XREMOT32.DLL IFH for remote diagnostics with IFH server/NMSIFH
BIN\XRPLUS32.DLL IFH for remote diagnostics with IFH server/NMSIFHPLUS

Note: Not included in the standard delivery!

BIN\XSTD32.DLL IFH for STD

Note: Not included in the standard delivery!

BIN\XTELE32.DLL IFH for TeleServices

Note: Not included in the standard delivery!

BIN\XTRACT.CSS CSS for display of XTRACT XML output
BIN\XTRACT.EXE Display of the help texts of BEST object files

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 18 of 117

BIN\XTRACT.XSD XSD for processing of XTRACT XML output

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages > 4.1.1. RUNTIME SYSTEM

4.1.1.2. Documentation

The following documentation refers to the delivery package RUNTIME-SYSTEM (or to

EDIABAS in general):

COMMENTS Comments on this version (optional)

USER MANUAL

INSTALLATION GUIDE This document

ERROR REFERENCE contains an overview of EDIABAS error messages

ECU SIMULATOR Description of the ECU Simulator

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages

4.1.2. APPLICATION DEVELOPMENT KIT

The delivery package APPLICATION DEVELOPMENT Kit is available for all systems listed in
section "Availability". This package allows application programs to be developed which use
EDIABAS.

The following development systems are supported under MS-WINDOWS:

Microsoft Visual C/C++ 2010 (WIN32, WIN64)

Microsoft Visual C/C++ 2008 (WIN32, WIN64)

Microsoft Visual C/C++ 6.0 (WIN32)
Microsoft Visual Basic 6.0 (WIN32)
Microsoft Visual Basic 4.0 (WIN32)
Microsoft Visual C#.NET / Visual Studio 2010 + .NET Framework 4.0 (WIN32)
Microsoft Visual Basic.NET / Visual Studio 2010 + .NET Framework 4.0 (WIN32)
Microsoft Visual C#.NET / Visual Studio 2008 + .NET Framework 3.5 (WIN32)
Microsoft Visual Basic.NET / Visual Studio 2008 + .NET Framework 3.5 (WIN32)
Microsoft Visual C#.NET / Visual Studio 2005 + .NET Framework 2.0 (WIN32)
Microsoft Visual Basic.NET / Visual Studio 2005 + .NET Framework 2.0 (WIN32)
Microsoft Visual C#.NET / Visual Studio 2003 + .NET Framework 1.x (WIN32)
Microsoft Visual Basic.NET / Visual Studio 2003 + .NET Framework 1.x (WIN32)

More:

4.1.2.1. Files for WIN32

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 19 of 117

4.1.2.2. Files for WIN64

4.1.2.3. Documentation

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages > 4.1.2. APPLICATION DEVELOPMENT KIT

4.1.2.1. Files for WIN32

The APPLICATION DEVELOPMENT KIT contains the following files:

README32.ADK Installation notes

API\WIN32\API.H General C/C++ header files for all libraries
API\WIN32\APICALLS.C C/C++ source code of API libraries
API\WIN32\APIDLL.H C/C++ header file for API32.DLL

(Windows DLL Interface)

API\WIN32\VB40\API.BAS Basic module for Visual Basic 4.0
API\WIN32\VB60\API.BAS Basic module for Visual Basic 6.0
API\WIN32\VC60\APIW32.LIB API library for single-Thread
API\WIN32\VC60\APIW32MT.LIB API library for multi-Thread
API\WIN32\VC2008\API32.LIB API library for Visual C/C++ 2008
API\WIN32\VC2010\API32.LIB API library for Visual C/C++ 2010
API\NET\VB2003\API.VB Basic module for Visual Basic.NET 2003 / Visual
Studio 2003 with .NET Framework 1.x
API\NET\VB2005\API.VB Basic module for Visual Basic.NET 2005 / Visual
Studio 2005 with .NET Framework 2.0
API\NET\VB2008\API.VB Basic module for Visual Basic.NET 2008 / Visual
Studio 2008 with .NET Framework 3.5
API\NET\VB2010\API.VB Basic module for Visual Basic.NET 2010 / Visual
Studio 2010 with .NET Framework 4.0
BIN\APITAL32.EXE EDIABAS test application

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages

4.1.3. BEST DEVELOPMENT KIT

The delivery package BEST DEVELOPMENT KIT is only available for MS-WINDOWS. This
package allows ECU description files to be developed.

The delivery package comprises, among other toolsBEST/2 Compiler, BEST/2 Debugger and
BEST development environment.

The following files are contained on the delivery diskette BEST DEVELOPMENT KIT:

More:

4.1.3.1. Files for WIN32

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 20 of 117

4.1.3.2. Documentation

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages > 4.1.3. BEST DEVELOPMENT KIT

4.1.3.1. Files for WIN32

The delivery package BEST-DEVELOPMENT-KIT contains the following files:

README32.BDK Installation notes

BIN\BEST1.EXE BEST/1 assembler (Win32)

BIN\BEST2.CHM Help file for BEST/2 compiler

BIN\BEST2.EXE BEST/2 compiler (Win32)

BIN\BEST2WIN.EXE BEST/2 compiler (Win32)

BIN\BEST32.DLL Help file for BEST2WIN (Win32)

BIN\B2RUNTIM.LIB BEST/2 runtime library

BIN\BESTVW32.CHM Help file for BEST/2 debugger

BIN\BESTVW32.EXE BEST/2 debugger: BestView

TUTORIAL\*.* BEST-tutorial files

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.1. Delivery packages > 4.1.3. BEST DEVELOPMENT KIT

4.1.3.2. Documentation

The following documentation refers to the delivery package BEST-DEVELOPMENT-KIT:

BEST USER MANUAL Programming description of a BEST/2 Description

file. How to operate the supplied programs.
BEST/2 FUNCTION REFERENCE Description of the BEST/2 function
BEST/2 LANGUAGE DESCRIPTION Syntactic description of the BEST/2 language.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.2. System requirements

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 21 of 117

More:

4.2.1. MS-WINDOWS

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.2. System requirements

4.2.1. MS-WINDOWS

In order to use EDIABAS under MS-WINDOWS, the following requirements must be met: IBM
PC/AT or 100% compatible system with at least an Pentium processor.

For the remote or proxy function of the EDIABAS RUNTIME SYSTEM for WIN32 a network
installation with TCP/IP is required.

For access of .NET Applications to EDIABAS the corresponding EDIABAS RUNTIME SYSTEM
is required. Additionally the .NET Framework 1.x/2.0/3.5 must exist on the target system.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.3. Installing for the first time

More:

4.3.1. MS-WINDOWS

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.3. Installing for the first time

4.3.1. MS-WINDOWS

The installation manual for MS-WINDOWS is not part of this documentation.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.4. EDIABAS program paths

More:

4.4.1. MS-WINDOWS

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.4. EDIABAS program paths

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 22 of 117

4.4.1. MS-WINDOWS

The EDIABAS subdirectory BIN is to be entered in the search path of the system.

Example for AUTOEXEC.BAT:

SET OLDPATH=%PATH%

PATH=c:\ediabas\bin;%OLDPATH%

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.5. EDIABAS configuration

The EDIABAS runtime behavior can be influenced via the EDIABAS configuration.

The EDIABAS configuration consists of information pairs which are listed in the area
[Configuration] of file EDIABAS.INI. In this process, each line here describes a configuration
element and its configuration setting:

Configurationelement = Configurationsetting

The configuration settings are read from file EDIABAS.INI when EDIABAS is first initialized.
The default setting (see Table section 4.5.1) is assumed when configuration settings are missing or
when file EDIABAS.INI does not exist.

All modifications of configurations in EDIABAS.INI must be made manually. NOTE:

Modifications are only valid after EDIABAS has been re-started.

Certain configuration elements can also be modified at EDIABAS runtime by application

programs. NOTE: These configuration changes only remain valid until EDIABAS is re-initialized.

Even ECU description files can modify configuration values during EDIABAS runtime. NOTE:
These values are only valid, however, during the job.

More:

4.5.1. Search sequence of EDIABAS.INI

4.5.2. Configuration overview

4.5.3. Select the hardware interface

4.5.4. Directory of ECU description files

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.5. EDIABAS configuration

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 23 of 117

4.5.1. Search sequence of EDIABAS.INI

Under MS-WINDOWS EDIABAS first searches for file EDIABAS.INI corresponding

environment variable EDIABAS_CONFIG_DIR. If the environment variable was not set or file was
not found in the directory, search is made in the Windows directory. If the file was not found in the
windows directory, search was made in the EDIABAS program directory (subdirectory BIN).

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.5. EDIABAS configuration

4.5.2. Configuration overview

All configuration elements are listed below along with setting options and default values.

Each configuration element contains a description whether and how a modification is to be made
(INI: via EDIABAS.INI, API: by application, BEST: by ECU description file).

All configuration elements in the following table are listed in the section CONFIGURATION.

ELEMENT Note Setting Change Default

ApiTrace Control of the API Trace 0 (OFF) INI API 0
BEST
1 user trace

2 + time
stamp

3 + process
ID **

4 API trace

5 + time
stamp

6 + runtime

7 + process
ID **

8 debug trace
BipDebugLevel Debug level in ECU 0 .. 32767 INI API 0
description files BEST
BipEcuFile File name of the currently String INI API -
loaded ECU description BEST
file (group or variant file):

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 24 of 117

only valid during job

execution
BipErrorLevel Error-Level in ECU 0 .. 32767 INI API 0
description file BEST
ClampHandling This configuration element 0 (OFF) INI API 1
only applies to the 1 (ON) BEST
interfaces XSTD and
XREMOTE/XRPLUS.
XSTD: Automatically read
clamps for ignition and
supply voltage.
XREMOTE/XRPLUS:
Transmits the query of the
clamp states over the
remote connection
EcuPath Path of the ECU Path INI API .
description files BEST
EdiabasIniPath Path of the configuration Path INI API
file EDIABAS.INI used BEST
(only if this exists)
EdiabasVersion EDIABAS version String INI API
BEST
IfhTrace Control of IFH Trace 0 (OFF) INI API 0
1 User BEST
interface
2 + interface
3+
timestamp
IfhnTrace Control of IFH-network- 0 (OFF) INI API 0
trace. Only available with 1 User BEST
XREMOTE. Interface
2 + Interface
3+
timestamp
IfhVersion IFH version String INI API
BEST
Interface Hardware interface String INI API EDIC
BEST

IgnitionHandling Ignition ON/OFF handle as 0 (OFF) INI API 1

error 1 (ON) BEST

LoadWin32 Selection of EDIABAS- 0 (EDIABAS INI API Windows

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 25 of 117

systems for WIN16- for WIN16) BEST 9x/ME: 0

applications (EDIABAS Windows
for WIN16 or automatic .. NT/2000/XP/Vista:
conversion to EDIABAS 1
for WIN32) 1 (EDIABAS
for WIN32)
LogLevel Logging of fatal errors in 0 (OFF) .. 1 INI API 0
EDIABAS.LOG (WIN32) (ON) BEST
NetworkProtocol Select network protocol for TCP INI API -
the remote diagnostics BEST
RetryComm Repetition on 0 (OFF) .. 1 INI API 1
communication error (ON) BEST
Session Name of the EDIABAS- String INI API
Session BEST
ShowIcon Displaying EDIABAS 0 (OFF) .. 1 INI API 1
icons within system tray (ON) BEST
(WIN32)
Simulation Control of ECU simulation 0 (OFF) .. 1 INI API 0
(ON) BEST
SimulationPath Path of the ECU simulation Path INI API .
files BEST
SystemResults Control whether to store: 0 (do not INI API 1
ignition, supply voltage store) BEST
and job status -system
results ..

1 (store)
TaskPriority Priority setting for 0 .. 10 INI API 0
EDIABAS (0 = optimal BEST
setting, 1 = lowest priority)
TraceBuffering Buffering of trace files 0 (OFF) .. 1 INI API 0
(WIN32) (ON) BEST
TraceHistory History of archived trace 0 .. 999 INI API 0
files (WIN32), 0 = BEST
compatibility mode
TracePath Path of the Trace files Path INI API .
BEST
TraceSize max. trace file size in KB 0 .. 32767 INI API 1024
BEST
TraceSync Control whether to 0 (OFF) .. 1 INI API 1
generate sync informations (ON) BEST
in trace files (WIN32)
TraceWriter Trace writer (WIN32): <DLL> INI API

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 26 of 117

Complete DLL path+name BEST

UbattHandling Supply voltage ON/OFF 0 (OFF) .. 1 INI API 1

handle as error (ON) BEST

** Note: the process ID is only indicated with EDIABAS for WIN32.

The configuration elements for the network protocol TCP (section TCP) are listed in the following
table. This section is only required when the value TCP has been assigned to the configuration
element NetworkProtocol in section CONFIGURATION.

ELEMENT Note Setting Change Default

Port Port number 1000...30000 INI API -
BEST
RemoteHost Name or IP address name/address INI API -
of remote system BEST
TimeoutConnect timeout in 1000 ... 59000 INI API 5000
milliseconds for BEST
connection setup
TimeoutReceive timeout in 1000 ... 59000 INI API 5000
milliseconds for BEST
receipt of a message
TimeResponsePending Time in milliseconds 500 ... 59000 INI API 2000
Zeit in BEST
Millisekunden
between alive
messages. Not
supported with
EDIABAS V6.4.0
TimeoutFunction Timeout in 5000 ... 59000 INI API 59000
milliseconds for a BEST
for a long IFH
function (for
example
send_and_receive).
The complete
timeout is:
TimeoutFunction +
TimeoutReceive.
DisconnectOnApiEnd Connection 0 (off) .. 1 (on) INI API 0
shutdown by apiEnd. BEST
InitCmd0 Initialization Hex string INI API -
InitCmd1 command. The slave e.g. BEST
… (especially OPPS) InitCmd1=FE,04,00,03,01

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 27 of 117

InitCmdn gets it by
configuration
element.

The configuration elements for the Ethernet interface (section XETHERNET) are listed in the
following table. This section is only required when the value ENET has been assigned to the
configuration element Interface in section CONFIGURATION.

ELEMENT Note Setting Change Default

RemoteHost Name or IP address of name/address INI API -
the vehicle, automatic OR BEST
connection by setting Autodetect
Autodetect
IfhRemoteHost timeout in milliseconds name/address INI API -
for connection setup OR BEST
Autodetect
Headerformat Format of the used 0 .. 1 INI API 0
network package BEST
header.
0=6 byte header,
1=3 byte header
Testeraddress Sequence of possible F1..FF INI API -
tester addresses, BEST
standard address F1 will
be replaced.
ControlPort TCP port number of 1000...59000 INI API 6811
control port BEST
DiagnosticPort TCP port number of 1000...59000 INI API 6801
diagnostic port BEST
TimeoutConnect timeout in milliseconds 1000 ... 59000 INI API 20000
for vehicle connection BEST
setup
IgnitionCacheInterval Period in milliseconds 0 ... 10000 INI API 500
the last retrieved BEST
ignition state from the
vehicle is cached. After
expiration of this time
the ignition state will be
retrieved from the
vehicle again on request
from the EDF.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 28 of 117

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.5. EDIABAS configuration

4.5.3. Select the hardware interface

More:

4.5.3.1. MS-WINDOWS

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.5. EDIABAS configuration > 4.5.3. Select the hardware interface

4.5.3.1. MS-WINDOWS

The hardware interface has to be set in the configuration file EDIABAS.INI (Interface).

The following hardware interfaces are currently supported:

SOFTING EDIC

The corresponding interface driver is NOT a constituent of the delivery package RUNTIME
SYSTEM.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.5. EDIABAS configuration

4.5.4. Directory of ECU description files

The directory of the ECU description files (referred to as SGBDs) to be used is to be entered
manually in EDIABAS.INI (EcuPath).

For further information, read the section "Administration".

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.6. Start and terminate EDIABAS

More:

4.6.1. WIN32

4.6.2. WIN64

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 29 of 117

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.6. Start and terminate EDIABAS

4.6.1. WIN32

When an application with access on EDIABAS is started the following components are loaded
automatically: API32.DLL, EBAS32.DLL, EBAS32.EXE, EBASCC32.DLL and
TRACEX32.DLL. EBAS32.DLL loads the interface handler.

In multi-threading mode the EDIABAS component EBASMT32.DLL is loaded instead of

EBAS32.DLL. For every further application thread an instance of the EDIABAS component
EBASMT32.EXE is started and terminated again when the application is closed.

Access of applications to EDIABAS takes place via API32.DLL.

Access of .NET applications (x86) to EDIABAS takes place via APINET32.DLL.

EDIABAS terminates automatically when the associated application is closed.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.6. Start and terminate EDIABAS

4.6.2. WIN64

When an application with access on EDIABAS is started the following components are loaded
automatically: API64.DLL, API64.EXE and the EDIABAS/WIN32 runtime system.

Access of applications to EDIABAS takes place via API64.DLL.All calls to EDIABAS/WIN64

will be redirected to the EDIABAS/WIN32 runtime system. The processing of ECU description
files and all interface calls are running within the EDIABAS/WIN32 runtime system.

The multi-threading mode is not supported.

Access of .NET applications (x64) is not supported.

EDIABAS terminates automatically when the associated application is closed.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.7. Un-install

When un-installed, all EDIABAS delivery packages are removed from the system. The
subdirectory ECU containing the ECU description files is only deleted when this is requested by
the user.

More:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 30 of 117

4.7.1. MS-WINDOWS

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.7. Un-install

4.7.1. MS-WINDOWS

The Uninstall manual is not part of this documentation.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.8. Protection mechanism

EDIABAS accesses ECU description files (SGBDs) for processing API jobs (see chapter 3). ECU
description files are developed as source code (B2V-, or B2G file) in BEST/2 and subsequently
compiled into an object format (PRG-, or GRP file) using the BEST compiler for use with
EDIABAS. The object files are loaded and executed at runtime by the runtime system.

In order to protect ECU description files in object format, EDIABAS offers a protection
mechanism. This mechanism not only prevents unauthorized reading of file contents (job names,
table names, table contents, etc.) but also prevents unauthorized use by users (non-authorized
external companies or private persons). The ECU description files are protected in two ways: 1)
File information is coded and not written in plain-language text and 2) the file cannot run under a
non-authorized EDIABAS runtime system; i.e. it cannot be loaded by EDIABAS. Thus,
information cannot be read from the ECU description files, and jobs within cannot be executed.

After the installation, the EDIABAS runtime system first assumes a state in which only
unprotected ECU description files can be executed. ECU description files are protected by means
of passwords specified for the runtime system and for the ECU description files. Passwords for
the runtime system are specified using the Password Editor (PE) (see section 5.3), whereas
passwords in the ECU description files are entered using the BEST compiler BEST2/BEST2WIN
(see BEST User Manual sections 5.1 and 5.2).

NOTE: Only the programs PE and BEST2/BEST2WIN included in the current EDIABAS
installation can be used for specifying passwords.

To protect an EDIABAS system, perform the following two steps:

1. In order to protect the EDIABAS runtime system, system passwords must be defined (at least
one) using the Password Editor (see section 5.3).

2. Next, all ECU description files used must be compiled with at least one password from the list
of the passwords entered above (see BEST user Manual, sections 5.1 and 5.2).

At runtime, the data read when loading the ECU description file must first be decoded.
Afterwards, the runtime system checks whether one of the passwords from the ECU description
file is known by the runtime system. If the runtime system recognizes at least one password from
the ECU description file, the ECU description file can be executed. The EDU description files
which are not protected with a password can be executed from every EDIABAS runtime system

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 31 of 117

(protected or not) beginning with version 5.5

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.9. Remote diagnostics

EDIABAS for WIN32/CE allows access to diagnostic interfaces and, consequently, cabled ECUs
which are connected to another PC.

This requires a network connection of local and remote-controlled PC via TCP/IP as well as a
WIN32 operating system supported by EDIABAS.

The application and EDIABAS run on the local PC, whereas the Interface Handler (IFH) as well as
the IFH server run on the remote-controlled PC. Before the remote-controlled PC can be accessed,
the IFH server IFHSRV32.EXE must be started first.

The remote control is enabled or controlled via the EDIABAS configuration file EDIABAS.INI.
EDIABAS is configured manually on both PCs.

The EDIABAS configuration parameters TracePath and SimulationPath are not transmitted to
the remote-controlled PC from the local PC. Instead, the corresponding configuration parameters of
file EDIABAS.INI (contained on the remote-controlled PC) are used.

The network protocol TCP (entry NetworkProtocol) as well as a user-selectable port number is to
be specified on both PCs. The port number must be identical on both PCs and must not collide with
the other TCP applications (1000 < port number < 30000).

More:

4.9.1. EDIABAS.INI on the local PC

4.9.2. EDIABAS.INI on the remote-controlled PC

4.9.3. Procedure for remote diagnostics

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.9. Remote diagnostics

4.9.1. EDIABAS.INI on the local PC

The configuration file EDIABAS. INI must be edited on the local PC in accordance with the list
depicted below. The assignment REMOTE to the configuration element Interface causes remote
control of the PC, which is specified with the entry RemoteHost. Specification of a logical
computer name requires a corresponding HOSTS file or a DNS service.

[Configuration]
Interface = REMOTE
NetworkProtocol = TCP

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 32 of 117

[TCP]
RemoteHost = < Name/address of remote-controlled PC >
Port = < Port from remote-controlled IFH >

TimeoutConnect=< Timeout for connection setup >

TimeoutReceive=< Timeout for Receive >

TimeoutFunction=< Timeout for IFH >

Example of EDIABAS.INI for the local PC:

[Configuration]
Interface=REMOTE
NetworkProtocol=TCP

[TCP]
RemoteHost=193.29.29.175
Port=5000

TimeoutConnect=2000

TimeoutReceive=2000

TimeoutFunction=50000

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.9. Remote diagnostics

4.9.2. EDIABAS.INI on the remote-controlled PC

Configuration file EDIABAS.INI must be extended on the remote-controlled PC in accordance

with the list depicted below.

[Configuration]
Interface=<Interface>
NetworkProtocol=TCP

[TCP]
Port=< Port of the remote-controlled IFH >

Example of EDIABAS.INI for the remote-controlled PC:

[Configuration]
Interface=EDIC
NetworkProtocol=TCP

[TCP]
Port=5000

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 33 of 117

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration >
4.9. Remote diagnostics

4.9.3. Procedure for remote diagnostics

1. Install EDIABAS on the local or remote-controlled PC.

2. Install the EDIABAS configuration on the local and remote-controlled PC.

3. Start the IFH server on the remote-controlled PC.

4. Start the application on the local PC.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.10. Proxy Operation

Note: The functionality described in this chapter is not included in the standard delivery!

The proxy interface connection permits central interface handling with separate sending and
reception of telegrams under Win32.

In proxy mode all access of an interface type are passed to a proxy running in the background,
which then processes the interface access. The proxy is automatically started once for every
interface type and then centrally serves all EDIABAS applications for this interface. Up to 16
EDIABAS applications can simultaneously be served per proxy.

If more than one EDIABAS application simultaneously access a proxy, the specifications of the
first EDIABAS application are valid. The other EDIABAS applications may not set diagnostic
interface parameters colliding with those of the first EDIABAS application. Simultaneous access to
a ECU address are serialized by the proxy, i.e. in case of a running send/receive, any further access
to the concerned ECU is delayed until the former send/receive has been concluded. The proxy
operation cannot be combined with the EDIABAS server operation. Functional addressing is not
permitted for proxy operation.

Proxy operation is only applicable for interfaces supporting the separate sending and reception of
telegrams under Win32.

The proxy operation can be activated by the configuration file EDIABAS.INI or at runtime with
apiInitExt. This can be done by prefixing the interface to be used with die identifier proxy
(separated by a colon).

The communication between proxy connection (XPROXY32.DLL) and proxy (IFHPRO32.EXE) is

executed via a configurable TCP/IP range starting by default from Port 6700. All unknown
interface types use port offset +0, i.e. only 1 unknown interface type can be operated at a time.

The used port range can be configured in ediabas.ini:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 34 of 117

[IfhProxy]

Port=6700 ; Start of the port range, Default = 6700

For operation with a firewall the used port range has to be activated.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.11. EDIABAS Parallel Operation

EDIABAS for WIN32 enable different application programs to access EDIABAS at the same time.
Each application program has its own EDIABAS, which is started and finished automatically.

Parallel operation of several interfaces of the same type is only possible if this is supported by the
corresponding interface software.

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.12. EDIABAS controller service

The EDIABAS controller service for WIN32 offers monitoring functionality according to the
earlier EDIABAS versions until 7.1. The simultaneous access of several applications to the same
interface (parallel operation) is blocked during operation of the EDIABAS controller service
(interface locking)

EDIABAS User's Guide > User manual and installation guide > 4. Installation and administration

4.13. EDIABAS Multi-Threading operation

By default EDIABAS for Win32 offers parallel operation based on the process, where all threads of
an application share a common EDIABAS runtime system.

EDIABAS under Win32 offers the function of switching to multi-threading operation. During
multi-threading operation every application thread gets assigned its own EDIABAS runtime
system. At the moment of switching NO application must be registered with EDIABAS, i.e. the
switch must not occur during apiInit/apiInitExt..apiEnd of an application.

After activation of the multi-threading functionality a later deactivation isn’t possible any more. By
default the multi-threading functionality is inactive.

EDIABAS User's Guide > User manual and installation guide

5. Help programs
More:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 35 of 117

5.1 PE (Password Editor)

5.2. BESTINFO

5.3. BESTVER

5.4. XTRACT

5.5. STRIP

EDIABAS User's Guide > User manual and installation guide > 5. Help programs

5.1 PE (Password Editor)

The Password Editor (PE) manages the passwords of a protected EDIABAS version. The Password
Editor is called PE.EXE. A password entry consists of a public label and associated, secret
password. The password is only used once in the entry. Only the password label is then used for all
further accesses.

A maximum of 10 label/passwords can be entered.

Labels/passwords which have once been entered cannot be deleted anymore. If this is desired,
EDIABAS must be re-installed.

Each label/password can be disabled or enabled (more than once possible). A disabled
label/password behaves during runtime as if it did not exist.

A <Label> consists of 1 to 10 ASCII characters in ANSI code, where only ASCII characters are
permitted in the range: 20h <= <ASCII-character> <= 7Eh. The character '@' (40h) is
illegal.

A <Password> consists of 6 to 10 ASCII characters in ANSI code, where only ASCII characters
are permitted in the range: 20h <= <ASCII characters> <= 7Eh.

The Password Editor is controlled via the command line. It offers the following functionalities:

Display all commands of the Password Editor

This Password Editor function represents a help function and displays all available

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 36 of 117

commands.
Call: pe
View all labels of the password file
With the Password Editor, the labels of all passwords which are known by the runtime
system can be displayed along with their status (enabled/disabled).
Call: pe -v
Add a new entry in the password file
Enter a new label/password in the EDIABAS runtime system. A total of 10 entries are
possible. When entries are added, they automatically are assigned the status "enabled".
Call: pe -a <Label>=<Password>
Enable an entry in the password file
Disabled entries can be re-enabled again. Possible more than one.
Call: pe -e <Label>
Disable an entry in the password file
Entries which have been entered can be disabled. In ECU description files sequence,
disabled entries behave as entries which do not exist. Possible more than once.
Call: pe -d <Label>

Check whether an ECU description file on the installed on the EDIABAS system can be
executed.
The Password Editor can also be used to check whether ECU description files can be
executed in connection with the installed EDIABAS system. For this purpose, the password
editor fetches the passwords from the ECU description file and compares them to the system
passwords.
Call: pe -c <SGBD>

Whenever the Password Editor exits, the user must confirm this by entering any key. The prompt
can be suppressed with option -Q.

The Password Editor returns the value 1 in the case of an error, otherwise 0.

In the case of the function Check, different values are defined:

0 if at least 1 SGBD password is the same

= "EXECUTABLE (on installed EDIABAS)"

1 in appearance of a general error

2 if no SGBD password is the same

= "NOT EXECUTABLE (on installed EDIABAS)"

3 if no SGBD password is defined

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 37 of 117

= "EXECUTABLE (not protected)"

NOTE: Only the Password Editor included in the EDIABAS installation can be used.

EDIABAS User's Guide > User manual and installation guide > 5. Help programs

5.2. BESTINFO

Display of ECU description file contents

The program BESTINFO allows the output of the following information regarding the specified
ECU description file (object format):

• File name

• Revision number

• Last user (operator) (output of maximum 63 characters), date of the last change

• List of all jobs

Call:

bestinfo [-Q] sgbd

Example:

bestinfo testv.prg

Produces output (example) :

BEST object file : testv.prg

BIP version : 03.03.00.00

Revision number : 2.0

Last modification by softing.sag.Os , Thu Mar 25 16:33:10 1993

5 Jobs:

INITIALISIERUNG

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 38 of 117

IDENT

CHECK

BINPARA

WAIT

BESTINFO ready.

Whenever the program BESTINFO exits, the user must confirm this by entering any key. The
prompt can be suppressed with option -Q.

EDIABAS User's Guide > User manual and installation guide > 5. Help programs

5.3. BESTVER

Version test of ECU description files

This program is only available under MS-WINDOWS. It allows the versions of ECU description
files (object format) to be tested. In addition it allows specification of a uniform version number of
the package for several description files.

Call:

BESTVER [-Q] [-R revMAJ.revMIN username] [-V packageversion] sgbd(s)

Example:

bestver -R 1.6 Softing -V 20 testv.prg

Modifies the revision (revision 2.0 becomes 1.6, and author becomes Softing) and specifies a
package version number (20). The following is output:

TESTV.PRG

BIP version : 03.03.00.00

Revisionnumber : 2.0

Last change : Thu Mar 25 16:33:10 1993

By : softing.sag.Os

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 39 of 117

Package version : 00000000

==>

Revisionnumber : 1.6

Last change : Wed Nov 24 12:41:50 1993

By : Softing

Package version : 00000020

Output of the last user is limited to a maximum of 63 characters.

Whenever the program BESTVER exits, the user must confirm this by entering any key. The
prompt can be suppressed with option -Q.

EDIABAS User's Guide > User manual and installation guide > 5. Help programs

5.4. XTRACT

Display help texts from ECU description files

This program is only available under MS-WINDOWS. XTRACT can be used to display the help
texts stored in the BEST object files.

Call:

XTRACT [-Q] [-F -X[ML]] objectfile(s) [outdir]

XTRACT -? (shows an overview of options)

Option -F pipes the output is a file with the extension .biv or .big. The options –X and –XML
cause an output in XML format (file with the extension .xml). The directory can be specified where
the output file is to be produced. Wildcards can be used in objectfile.

Whenever the program XTRACT exits, the user must confirm this by entering any key. The prompt
can be suppressed with option -Q.

Example:

xtract -F testv.prg

Produced file testv.biv containing the following:

ECU:TESTV

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 40 of 117

ORIGIN:softing.sag.Os

REVISION:2.0

AUTHOR:softing.sag.Os

ECUCOMMENT:Description file WIHTOUT access to the interface

ECUCOMMENT:Original: TESTV.B1V

JOBNAME:INITIALISIERUNG

JOBCOMMENT: Initialization

RESULT:DONE

RESULTTYPE:int

RESULTCOMMENT:1 if ok, otherwise 0

JOBNAME:IDENT

JOBCOMMENT:Determine the identification string

RESULT:JOB_STATUS

RESULTTYPE:string

RESULTCOMMENT: Returns: OKAY or ERROR_PARAMETER

...

RESULTCOMMENT: Returns: OKAY or ERROR_PARAMETER

Automatic table output:

For improved documentation of BEST objects, XTRACT also offers the functionality to output the
entries of a table instead of a BEST/2 comment. For this purpose, a BEST/2 comment must have
the following structure:

comment: table <Table name> < Column > [ < Column > ... ]

Example of a BEST/2 source file:

...

table exampleTable[2][]=

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 41 of 117

{ "COLUMN1", "COLUMN2", "COLUMN3" },

{ "Line1", "xtract", "generated" },

{ "Line2", "these", "texts" },

{ "Line3", "automatically", "!" }

};

job ( name = exampleJob;

comment : Start of comment

comment : table exampleTable COLUMN2 COLUMN3

comment : End of comment

...

XTRACT outputs the following lines in the example above:

...

JOBNAME:exampleJob

JOBCOMMENT:Start of comment

JOBCOMMENT: "xtract" "generated"

JOBCOMMENT: "these" "texts"

JOBCOMMENT: "automatically" "!"

JOBCOMMENT:End of comment

...

EDIABAS User's Guide > User manual and installation guide > 5. Help programs

5.5. STRIP

Remove (strip) the extra information from ECU description files

This program is only available under MS-WINDOWS. STRIP can be used to remove the help text

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 42 of 117

and debug information stored in BEST object files.

Aufruf:

STRIP [-Q] [-N] dh sourcefile(s) [outdir]

STRIP -? (Shows an overview of options)

Parameter d indicates that the debug information is to be removed, whereas parameter h indicates
that the help texts are to be removed. The directory can be specified where the output file is to be
produced. If an object file is overwritten which already exits, STRIP requests the user for re-
confirmation. This interrogation can be suppressed with option -N.

Whenever the program STRIP exits, the user must confirm this by entering any key. The prompt
can be suppressed with option -Q.

Example:

strip -N dh testv.prg

Remove the debug information and help texts from file testv.prg.

EDIABAS User's Guide > User manual and installation guide

GLOSSARY
API

Application

BEST

Description file

Device

Diagnostic concept

DLL

ECM

ECU

EDIABAS

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 43 of 117

EDIC

EdicApi

IFH

Job

Runtime system

SGBD

SG

Control device variant

EDIABAS User's Guide

EDIABAS Error Reference

More:

1. Revision history

2. Introduction

3. General Information

4. List of errors

A. References

EDIABAS User's Guide > EDIABAS Error Reference

1. Revision history
Version 3.0 First release

Version 3.0A Enhanced error message descriptions (partially)

Version 3.0B Enhanced error message descriptions (complete)

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 44 of 117

Version 4.1 Revised for EDIABAS V4.1.0

Version 5 Revised for EDIABAS V5.1.0

Version 5a Error corrections

Extended for EDIABAS 5.5.0

Version 5b New: IFH-0037 to IFH-0040

Version 5c Extended for QNX

Version 6 Extended for EDIABAS 6.0.0: BIP-0012, BIP-0013 and IFH-0041 to IFH-0059

Version 6b Revised for EDIABAS V6.4.4

Version 7 Extended for EDIABAS 6.4.5: NET-0021, NET-0022

Extended for EDIABAS 6.9.0: BIP-0017

Modified for EDIABAS 6.9.1: IFH-0060 to IFH-0065
Extended for EDIABAS 6.9.1: IFH-0066 to IFH-0071
Extended for EDIABAS 6.10.0: IFH-0072 to IFH-0073
Extended for EDIABAS 7.0.0: BIP-0018, API-0016 to API-0017
No more support for DOS, WIN16, QNX

Version 7a Improvement of interface error descriptions

No more support for SCO UNIX

Version 7b Revised for EDIABAS V7.2.0

Version 7c Revised for EDIABAS V7.2.0

EDIABAS User's Guide > EDIABAS Error Reference

2. Introduction
More:

2.1. About this manual

2.2. Notational conventions

2.3. Special features, terms, acronyms

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 45 of 117

EDIABAS User's Guide > EDIABAS Error Reference > 2. Introduction

2.1. About this manual

This manual describes the general structure of an error. All errors which can occur in EDIABAS
are listed, including the respective methods of correction. General information regarding
EDIABAS and ECU description files is described in [2].

EDIABAS User's Guide > EDIABAS Error Reference > 2. Introduction

2.2. Notational conventions

The following typographical conventions are used throughout this manual:

Beispiel Beschreibung
SAMPLE.B2V Uppercase denotes file names, registers and operating
system commands.
job, string, while Bold-faced type identifies keywords and operators of the
language BEST/2 and BEST/s as well as the API functions.

These words must be written exactly as specified in syntax

descriptions.
expression Italics designate placeholders for values to be entered by
the programmer; e.g., file names.
[option] Words enclosed in square brackets may be optionally
specified.
{ result | Curvy braces and vertical strokes characterize entries from
argument } which only one must be selected, except when in square
brackets.
[constant...] job... An ellipsis (three dots) which directly follows an
expression indicates that several expressions of the same
type can follow.
hallo="Test"; This syntax designates examples, user entries, program
outputs and error messages.
while() { A column or a row comprising three dots indicates that a
section of an example was intentionally omitted.
.

.}
[1] Reference to a document in References.

EDIABAS User's Guide > EDIABAS Error Reference > 2. Introduction

2.3. Special features, terms, acronyms

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 46 of 117

An explanation of all abbreviations used in this and all other EDIABAS documentation can be
found in the publication "EDIABAS User Manual" in chapter "GLOSSARY".

EDIABAS User's Guide > EDIABAS Error Reference

3. General Information
Erroneous functions such as time-out during ECU communication can occur during the execution
of EDIABAS. An erroneous function recognized by EDIABAS is reported as an EDIABAS error.

More:

3.1. Error symbol and error code

3.2. Message and output of an error

3.3. How errors affect program execution

EDIABAS User's Guide > EDIABAS Error Reference > 3. General Information

3.1. Error symbol and error code

An error symbol structured as follows is assigned to each error:

The Origin of an error denotes the EDIABAS-internal program area where the error was detected.
The following areas are possible:

IFH Interface Handler (run-time system)

BIP BEST Interpreter (run-time system)

SYS Run-time System (run-time system)

API API (Application Programming Interface)

NET Network (run-time system)

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 47 of 117

RUN SGBD (ECU description file)

Errors having the same Origin can be differentiated using a 4-digit error number. If an error does
not exist, it is identified by the pseudo error symbol EDIABAS_ERR_NONE.

An integer value, the error code, is assigned to each Error symbol. The value 0 indicates that an
error was not recognized by EDIABAS (error symbol EDIABAS_ERR_NONE).

EDIABAS User's Guide > EDIABAS Error Reference > 3. General Information

3.2. Message and output of an error

An error recognized by EDIABAS is reported to the application program and can only be output
there.

An application program can independently determine the type and way an error is handled,
whereby basically only the following error information can be fetched by EDIABAS:

Error code ( with API function apiErrorCode )

Error text ( with API function apiErrorText )

Document [1] describes, in detail, the procedure on how an application program recognizes and
issues (outputs) errors.

EDIABAS User's Guide > EDIABAS Error Reference > 3. General Information

3.3. How errors affect program execution

An error which occurs while a job is being processed causes the job to be aborted and an error
message to be issued to the application program. All job results stored up to this point are deleted.
If an error occurs during the initialization of EDIABAS (apilnitXxx) by the application program,
initialization is aborted.

An error remains stored until an application program (apiJobXxx call) starts a new job, re-
initialization is performed via apiInitXxx, or a device change is performed with apiSwitchDevice.

The errors API-0005 and API-0014 will be deleted during the next result query (apiResultXxx).

EDIABAS User's Guide > EDIABAS Error Reference

4. List of errors
This chapter lists all errors which are reported by EDIABAS. In accordance with the place of
origin, subdivision into IFH, BIP, SYS and API is made.

All errors are represented in the same way:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 48 of 117

Error code Error text Error symbol

Meaning:
Causes:
Error correction:
Target system WIN

Error code represents the error (as a value) reported by EDIABAS. This value can be fetched by
the application from EDIABAS using the function apiErrorCode.

Error text shows the error reported by EDIABAS in text format. This error text can be fetched by
the application program from EDIABAS using the function apiErrorText.

Error symbol corresponds to the error assignment in file API.H, in which the error symbol is
defined as a constant.

Each error description comprises the sections Meaning, Causes, Error correction and Target
system. Errors are explained in section "Meaning". The causes of an error are described in a
corresponding section. All measures described in section "Error correction" are always to be
observed or carried out.

Section "Target system" informs the user under which EDIABAS target system the error can occur.
If an error cannot occur on an EDIABAS target system, the corresponding target system is crossed
out.

Each target system is assigned an:

WIN = EDIABAS / MS-WINDOWS

More:

4.1. IFH, Interface Handler

4.2. Runtime system

4.3. API, Application Programming Interface

4.4. Network

4.5. Application

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors

4.1. IFH, Interface Handler

10 IFH-0000: INTERNAL ERROR EDIABAS_IFH_0000

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 49 of 117

Meaning: This error indicates an illegal EDIABAS program state.

Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

11 IFH-0001: UART ERROR EDIABAS_IFH_0001

Meaning: Overflow of a data buffer in the device driver of the interface
or undefined error message from the driver.
Causes: More data are sent to the driver than this buffer can receive.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

IFH-0002: NO RESPONSE FROM EDIABAS_IFH_0002

INTERFACE
12
Meaning: The diagnostic bus interface connected does not respond.
Causes: The interface is not connected.

The interface is not supported by the Interface Handler.

No voltage is supplied to the interface.

No firmware is loaded in the interface (download version of

the interface).
Error correction: Check if the correct interface is properly connected.
Target system: WIN

13 IFH-0003: DATATRANSMISSION TO EDIABAS_IFH_0003

INTERFACE DISTURBED
Meaning: A response from the interface was incorrectly received
(characters were lost, protocol frame incorrect, etc.).
Causes: Contact problems in the cables between the host system and
the interface.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 50 of 117

Error correction: Check the cables between the host system and the interface.
Target system: WIN

IFH-0004: ERROR IN INTERFACE EDIABAS_IFH_0004

COMMAND
14
Meaning: Unknown command to the interface.
Causes: The requested interface function is not available in the
interface used.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

15 IFH-0005: INTERNAL INTERFACE EDIABAS_IFH_0005

ERROR
Meaning: This error indicates an illegal program status of the diagnostic
bus interface.
Causes: A program result of the interface cannot be processed.
Error correction: If an error repeatedly occurs, temporarily interrupt its voltage
supply in order to reset the interface.

If an error still occurs after interrupting of the voltage supply,

re-load the firmware of the interface.

Please contact SOFTING if the error still continues to occur.

Target system: WIN

IFH-0006: COMMAND NOT ACCEPTED EDIABAS_IFH_0006

16
Meaning: The interface fails to accept the sent command.
Causes: While ECU communication is active, the interface accepts not
further send command. If cyclic sending of a message is
started (BEST1: xsendf; BEST2: send_frequent), ECU
communication is continuously active.
Error correction: The frequent mode must be aborted prior to re-sending a

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 51 of 117

message or setting ECU parameters (BEST1: xstopf; BEST2:

stop_frequent).
Target system: WIN

IFH-0007: WRONG UBATT EDIABAS_IFH_0007

17
Meaning: This error occurs when either no voltage is currently supplied
to the D bus or when the voltage is too small. In addition, this
error can also be caused by short circuits on the D bus. The
error message is issued only following BEST commands which
access the D bus. These are:

Send and receive a message

Request the ECU keybytes and identification data

This error message is suppressed for all other BEST

commands of the Interface Handler (e.g. read the ports or set
ECU parameters). As soon as the correct voltage is applied on
the D bus, an error message no longer occurs after executing
the BEST commands above.
Causes: No (or too small) voltage supplied on the D bus.
Error correction: Supply voltage to the D bus.
Target system: WIN

18 IFH-0008: CONTROLUNIT CONNECTION EDIABAS_IFH_0008

ERROR
Meaning: Erroneous connection between the interface and the ECU.
Causes: Short circuit on the TxD or RxD .
Error correction: Remove short circuit.
Target system: WIN

19 IFH-0009: NO RESPONSE FROM EDIABAS_IFH_0009

CONTROLUNIT
Meaning: The ECU is not connected or does not respond.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 52 of 117

Causes: The ECU is not connected (or not properly).

The ECU is not supplied with voltage.

The ECU is addressed with a wrong address.

The ECU parameters are incorrect (concept, times, etc.).

Error correction: Erroneous connection between the interface and the ECU.
Target system: WIN

20 IFH-0010: DATATRANSMISSION TO EDIABAS_IFH_0010

CONTROLUNIT DISTURBED
Meaning: The data transmission between the interface and the ECU is
disturbed.
Causes: Disturbance on the diagnostic line.

The interface EDIC is not loaded with the diagnostics protocol

requested in the ECU description file (SGBD).
Error correction: Repeat the last job.

Download the required EDIC firmware.

Target system: WIN

IFH-0011: UNKNOWN INTERFACE EDIABAS_IFH_0011

21
Meaning: This error is inapplicable for EDIABAS V3.0.0 or later.

The error code and associated constants do not exist due to

compatibility reasons.
Causes: -
Error correction: -
Target system: WIN

22 IFH-0012: BUFFER OVERFLOW EDIABAS_IFH_0012

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 53 of 117

Meaning: Overflow in one of the internal data buffers of the Interface

Handler.
Causes: IFH-internal buffer overflow.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

23 IFH-0013: COMMAND NOT EDIABAS_IFH_0013

IMPLEMETED
Meaning: The BEST command called is not supported by the Interface
Handler.
Causes: An interface is connected in which the functionality appears
behind the BEST command is not integrated.
Error correction: Replace the interface or upgrade the interface driver.
Target system: WIN

24 IFH-0014: CONCEPT NOT EDIABAS_IFH_0014

IMPLEMENTED
Meaning: IFH-internal buffer overflow.

The error code and associated constants do not exist due to

compatibility reasons.

You can set this error using the BEST2 function make_error
Causes: -
Error correction: -
Target system: WIN

25 IFH-0015: UBATT ON/OFF ERROR EDIABAS_IFH_0015

Meaning: This error message occurs whenever the supply voltage on the
D bus was temporarily interrupted before the Interface Handler
accesses the interface. If the interruption continues to exist
during the current access to the interface, the error message
"IFH-0007: WRONG UBATT" occurs instead. After the error
message is issued, the status flag in the interface which

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 54 of 117

displayed this error is automatically deleted by the Interface

Handler.
Causes: The voltage supplied on the D bus was temporarily interrupted.
Error correction: Repeat the job.

If the error is to be generally suppressed for all application

programs, set the EDIABAS configuration element
UbattHandling to 0.
Target system: WIN

26 IFH-0016: IGNITION ON/OFF ERROR EDIABAS_IFH_0016

Meaning: This error message occurs whenever the ignition was disabled
after the last access of the Interface Handler to the interface,
even when it had been re-enabled again in the meantime. The
reason for this error message cannot be determined from the
current status of the ignition. The current status of the ignition
must be interrogated with the corresponding BEST command
(BEST1: xignit; BEST2: get_ignition_voltage). After the error
message is issued, the status flag in the interface which caused
the error message is automatically deleted by the Interface
Handler
Causes: Ignition disabled.
Error correction: Enable the ignition and repeat the last job.

If the error is to be generally suppressed for all application

programs, the EDIABAS configuration element
IgnitionHandling must be set to 0.
Target system: WIN

IFH-0017: INTERFACE DEADLOCK EDIABAS_IFH_0017

ERROR
27
Meaning: The BUSY condition of the interface is too long (greater than
„deadlock“ timeout).
Causes: The ECU response time is greater than “deadlock” time.

Several blocks are expected after sending a message to which

the ECU which does not respond (can be set via BEST
command "xawlen").
Error correction: The ECU response time is greater than “deadlock” time.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 55 of 117

Set the response length to (BEST1: xawlen {0.i,0.i}; BEST2:

set_answer_length).
Target system: WIN

28 IFH-0018: INITIALIZATION ERROR EDIABAS_IFH_0018

Meaning: Error at initialization of the interface handler
Causes: The Interface Handler was not initialized (shouldn't occur,
since the initialization automatically occurs with apiInit).
Error correction: Re-initialize your interface.
Target system: WIN

29 IFH-0019: DEVICE ACCESS ERROR EDIABAS_IFH_0019

Meaning: Execution of the BEST command which accesses the Interface
Hander is denied.
Causes: This error message always occurs whenever access is made to
the Interface Handler via a BEST command and the device
driver of the interface still has not been opened.
Error correction: The connection to the driver must first be produced in the ECU
description file. (BEST1: xconnect, BEST2:
open_communication). This is why this command must be
placed before the first command which accesses the Interface
Handler; i.e. this command should principally appear in the
jobs "INITIALIZATION" and “ENDE”.
Target system: WIN

30 IFH-0020: DRIVER ERROR EDIABAS_IFH_0020

Meaning: Error when accessing the device driver of the interface.
Causes: The voltage supplied on the D bus was temporarily interrupted.
Error correction: The driver installation is to be checked according to the
installation instructions enclosed with the interface used.

Use EDIC as interface; then check your EDIC API installation

in Windows.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 56 of 117

IFH-0021: ILLEGAL PORT EDIABAS_IFH_0021

31
Meaning: Specification of an illegal port number in the ECU description
file (SGBD).
Causes: Illegal port numbers are used In the BEST commands (BEST1:
xgetport and xsetport, BEST2: ifgetport and ifsetport).
Error correction: Correction of the port number in the ECU description file.
Target system: WIN

32 IFH-0022: DRIVER STATUS ERROR EDIABAS_IFH_0022

Meaning: The Interface Handler cannot interpret the status message of
the device driver included in the interface.
Causes: The driver responds with an undefined status message.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

33 IFH-0023: INTERFACE STATUS ERROR EDIABAS_IFH_0023

Meaning: The Interface Handler cannot interpret the status message.
Causes: The interface responds with an undefined status message.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

IFH-0024: CANCEL FAILED EDIABAS_IFH_0024

34
Meaning: Error when resetting the DPRAMs. This error only occurs in
connection with EDIC versions communicating via DPRAM
with the PC.
Causes: The DPRAM and/or the device driver of the interface are in an

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 57 of 117

undefined state.

Communication problem between the device driver of the

interface and the EDIC firmware.
Error correction: Repeat the job.

Re-load the EDIC firmware.

Target system: WIN

35 IFH-0025: INTERFACE APPLICATION EDIABAS_IFH_0025

ERROR
Meaning: Error when opening the device driver of the interface (BEST1:
xconnect, BEST2: open_communication). This error only
occurs together with EDIC versions communicating via
DPRAM with the PC.
Causes: The firmware was not loaded in EDIC.

Error correction: Download the corresponding EDIC firmware.

Target system: WIN

IFH-0026: SIMULATION ERROR EDIABAS_IFH_0026

36
Meaning: Error in connection with the ECU Simulator.
Causes: Syntax error in one of the simulation files.

One of the simulation files is missing or placed in the wrong

directory (see description of the ECU Simulator). Simulation
files created with MS-DOS/WINDOWS were not converted to
the Unix format before being used with Unix.
Error correction: Correction of the erroneous simulation file(s) (see description
of the ECU Simulator).
Target system: WIN

IFH-0027: IFH NOT FOUND EDIABAS_IFH_0027

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 58 of 117

37
Meaning: The Interface Handler is not installed.
Causes: EDIABAS attempts to access the Interface Handler although
this is not (or incorrectly) installed.
Error correction: Check your application whether the correct interface handler or
driver is installed.

After the configuration has been corrected, terminate the

Interface Handler and EDIABAS, and re-start:

WIN32: EDIABAS is automatically closed with the

application (automatic restart)

Re-start the application program.

Target system: WIN

IFH-0028: ILLEGAL IFH VERSION EDIABAS_IFH_0028

38
Meaning: A wrong Interface Handler version is installed.
Causes: Your EDIABAS requires a different Interface Handler version
than that which is installed.
Error correction: Re-install the required EDIABAS version and possibly the
Extension Disk.

Re-install the required interface driver version, respectively.

Target system: WIN

39 IFH-0029: ACCESS DENIED EDIABAS_IFH_0029

Meaning: Access to the Interface Handler is presently not possible.
Causes: Only one program can access the Interface Handler at the same
time. When a program accesses the Interface Handler, this was
already connected to another program.
Error correction: Terminate all programs which currently access the Interface
Handler.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 59 of 117

IFH-0030: TASK COMMUNICATION EDIABAS_IFH_0030

ERROR
40
Meaning: Communication between EDIABAS and the Interface Handler
is disturbed.
Causes: Communication data from the Interface Handler are erroneous
or the communication medium is damaged. If the Interface
Handler does not respond within a specified time, this error is
also issued..
Error correction: If this error repeatedly occurs, re-start the application program.
If the error is still not corrected, re-start your system.
Target system: WIN

41 IFH-0031: DATA OVERFLOW EDIABAS_IFH_0031

Meaning: The input buffer is full.
Causes: Excessive data is transferred from EDIABAS to the Interface
Handler.
Error correction: Not possible by the user. If this error still occurs, please
contact SOFTING.
Target system: WIN

IFH-0032: IGNITION IS OFF EDIABAS_IFH_0032

42
Meaning: This error messages occurs whenever the ignition is disabled
while the Interface Handler accesses the ECU.
Causes: The ignition is disabled.
Error correction: Enable the ignition, and repeat the last job.
Target system: WIN

44 IFH-0034: CONFIGURATION FILE NOT EDIABAS_IFH_0034

FOUND
Meaning: This error message occurs whenever the configuration files for
the EDIC API couldn't be found.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 60 of 117

Causes: The EDIC API configuration files do not exist (or do not reside
in the correct directory).
Error correction: Re-install EDIC. If the error should continue to occur, please
inform SOFTING.
Target system: WIN

IFH-0035: CONFIGURATION ERROR EDIABAS_IFH_0035

45
Meaning: At least one configuration element in one of the interface
configuration files is incorrectly configured.
Causes: Erroneous configuration e.g. of an EDIC API configuration
element.
Error correction: Re-install your interface.

Target system: WIN

46 IFH-0036: LOAD ERROR EDIABAS_IFH_0036

Meaning: This error message occurs when an error occurs while loading
the EDIC firmware.
Causes: Erroneous configuration.

EDIC is not connected.

Error correction: Check the cables and the EDIC API configuration (was a
*.LOG file created?).

If necessary, re-install the EDIC (firmware). If this error

should continue to occur, inform SOFTING.
Target system: WIN

IFH-0037: LOW UBATT EDIABAS_IFH_0037

47
Meaning: This error occurs whenever a voltage is currently supplied to
the D bus and when a connected ECU does not respond. The

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 61 of 117

error message is issued only after BEST command which

access the D bus. These are:

Send and receive a message.

Request the ECU keybytes and identification files.

This error message is suppressed for all other BEST
commands of the Interface Handler (e.g. read the ports or set
ECU parameters). As soon as the correct voltage is supplied to
the D bus, no error message is issued anymore after executing
the BEST commands above.
Causes: The supply voltage is too low on the D bus, and the ECU does
not respond.
Error correction: Increase voltage supply on the D bus.
Target system: WIN

48 IFH-0038: INTERFACE COMMAND NOT EDIABAS_IFH_0038

IMPLEMENTED
Meaning: The command used by the Interface Handler to the interface is
not supported by the interface.
Causes: The current interface version does not support the command
used.
Error correction: Install an interface which supports the commands used.
Target system: WIN

49 IFH-0039: EDIC USER INTERFACE NOT EDIABAS_IFH_0039

FOUND
Meaning: Component EDICX32.EXE couldn't be found
Causes: Component EDICX32.EXE is missing in the installation
Error correction: Re-install the EDIC. If this error should continue to occur,
inform SOFTING.
Target system: WIN

50 IFH-0040: ILLEGAL EDIC USER EDIABAS_IFH_0040

INTERFACE VERSION

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 62 of 117

Meaning: The version of the EDIC user interface does not match the
version of the EDIC API.
Causes: EDIC API was installed incorrectly or parts of the EDIC API
(EDIC32.DLL, EDICX32.EXE) reside in the Windows
directory.
Error correction: Delete all components of the EDIC API (EDIC32.DLL,
EDICX32.EXE) which reside in the Windows directory.

Re-install the EDIC. If this error should continue to occur,

inform SOFTING.
Target system: WIN

IFH-0041: ILLEGAL PARAMETERS EDIABAS_IFH_0041

51
Meaning: Faulty function parameter transfer to the EDIC API.
Causes: A function of EDIC API received parameters not within the
range of values.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

52 IFH-0042: CARD INSTALLATION ERROR EDIABAS_IFH_0042

Meaning: Error during installation of the EDICcard.
Causes: The EDICcard could not be installed correctly.
Error correction: Re-install EDIC. If this error should continue to occur, please
inform SOFTING.
Target system: WIN

53 IFH-0043: COMMUNICATION TRACE EDIABAS_IFH_0043

ERROR
Meaning: Error in the EDIC communication trace.
Causes: No access to DPRAM possible.
Error correction: Re-install EDIC. If this error should continue to occur, please
inform SOFTING.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 63 of 117

Target system: WIN

IFH-0044: FLASH ERROR EDIABAS_IFH_0044

54
Meaning: An error was found during the flash process of the EDIC
firmware.
Causes: Faulty EDIC API configuration, the firmware is corrupted, or
the EDIC is not connected.
Error correction: Check the EDIC connectors on the computer and the EDIC
API configuration (EDICHW.INI and EDICFW.INI).
Target system: WIN

55 IFH-0045: RUNBOARD ERROR EDIABAS_IFH_0045

Meaning: An error has occurred during initialization of the EDIC-PC3.
Causes: Faulty EDIC API configuration.
Error correction: Check your EDIC API configuration (EDICHW.INI and
EDIC-PC3 configuration).
Target system: WIN

56 IFH-0046: EDIC API ACCESS ERROR EDIABAS_IFH_0046

Meaning: An error has occurred during starting of the application
program.
Causes: An application program in another directory already uses the
EDIC API.
Error correction: Terminate the other application program and restart your
application program.
Target system: WIN

IFH-0047: PLUGIN ERROR EDIABAS_IFH_0047

57

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 64 of 117

Meaning: A plug-in DLL could not be loaded, or access to this DLL was
not possible.
Causes: Faulty EDIC API configuration, plug-in DLL not found, or the
plug-in DLL needs another DLL which was not found.
Error correction: Cannot be performed by the user. If this error should re-occur,
please inform the company which has implemented your plug-
in DLL.
Target system: WIN

58 IFH-0048: PLUGIN FUNCTION ERROR EDIABAS_IFH_0048

Meaning: One function in a plug-in DLL could not be accessed.
Causes: The function in the plug-in DLL is missing or implemented
incorrectly.
Error correction: Cannot be performed by the user. If this error should re-occur,
please inform the company which has implemented your plug-
in DLL.
Target system: WIN

IFH-0049: CSS DEVICE DETECTION EDIABAS_IFH_0049

59 ERROR
Meaning: A C&SS EDIC was not found.
Causes: Faulty configuration, or the necessary system resources (IRQ,
memory) are not available.
Error correction: Please check the EDIC API configuration (EDICHW.INI, the
driver, IRQ and memory configuration).
Target system: WIN

200 IFH-0050: ENTRY IN DYNAMIC EDIABAS_IFH_0050

CONFIGURATION NOT FOUND
Meaning: During the dynamic reloading of protocols, an internal error
has occurred.
Causes: An entry in the EDIC API configuration file for the dynamic
reloading of protocols is faulty or missing.
Error correction: Re-install the firmware. If the same error should occur again,

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 65 of 117

please inform the company which has implemented your

application program.
Target system: WIN

IFH-0051: INTERNAL DYNAMIC EDIABAS_IFH_0051

PROTOCOL ERROR
201
Meaning: During the dynamic reloading of protocols, an internal error
has occurred.
Causes: An illegal program status of the EDIC API has occurred.
Error correction: Cannot be performed by the user. If this error should re-occur,
inform SOFTING.
Target system: WIN

202 IFH-0052: CONCEPT NOT AVALIABLE EDIABAS_IFH_0052

Meaning: The selected concept is not available.
Causes: For the selected concept, no firmware is available or has been
configured in the EDIC API configuration.
Error correction: Re-install the firmware. If this error should continue to occur,
please inform the company which has implemented your
application program.
Target system: WIN

203 IFH-0053: ILLEGAL CONCEPT ID EDIABAS_IFH_0053

Meaning: Illegal concept number.
Causes: The selected concept number has an illegal value.
Error correction: Cannot be performed by the user. If this error should occur,
please inform the company which has implemented your
application program.
Target system: WIN

204 IFH-0054: ILLEGAL FUNCTION EDIABAS_IFH_0054

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 66 of 117

PARAMETER
Meaning: An interface function was called with an illegal parameter.
Causes: An illegal program status of the interface handler or driver has
occurred.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

205 IFH-0055: CANNOT LOAD PROTOCOL EDIABAS_IFH_0055

TABLES
Meaning: The dynamic reloading of protocol tables has failed.
Causes: Faulty firmware configuration in the EDIC API configuration.
Error correction: Re-install the firmware. If this error should continue to occur,
please inform the company which has implemented your
application program.
Target system: WIN

206 IFH-0056: ILLEGAL CHANNEL EDIABAS_IFH_0056

Meaning: Transfer of an illegal channel number to EDIC API.
Causes: An illegal channel number was passed to EDIC API.
Error correction: Cannot be performed by the user. If this error should occur,
please inform the company which has implemented your
application program.
Target system: WIN

207 IFH-0057: ERROR READ DIGITAL EDIABAS_IFH_0057

INPUTS
Meaning: Error during reading of a digital EDIC input.
Causes: An error has occurred during reading of a digital EDIC input.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 67 of 117

208 IFH-0058: ERROR SET DIGITAL EDIABAS_IFH_0058

OUTPUTS
Meaning: Error during setting a digital EDIC output.
Causes: An error has occurred during the setting of a digital EDIC
output.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

209 IFH-0059: ERROR READ ANALOG EDIABAS_IFH_0059

INPUTS
Meaning: Error during reading an analog EDIC input.
Causes: An error has occurred during the reading of an analog EDIC
input.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

210 IFH-0060: RESUME AFTER SUSPEND EDIABAS_IFH_0060

STATE
Meaning: The computer was in suspend state when communication with
EDIC occured.
Causes: See above.
Error correction: Terminate your application program and restart it.
Target system: WIN

211 IFH-0061: INVALID ECU PARAMETERS EDIABAS_IFH_0061

FORMAT
Meaning: Invalid ECU parameters were used.
Causes: See above.
Error correction: Check the ECU parameters or inform SOFTING.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 68 of 117

Target system: WIN

212 IFH-0062: BAD ECU PARAMETERS EDIABAS_IFH_0062

BUFFER
Meaning: The buffer passed for reading the ECU parameters was too
small.
Causes: See above.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

213 IFH-0063: INVALID BUS EDIABAS_IFH_0063

CONFIGURATION
Meaning: The requested bus configuration (e.g. baudrate) couldn’t be set.
Causes: ECU parameters are incorrect.
Error correction: Cannot be performed by the user. If this error should occur,
please inform SOFTING.
Target system: WIN

214 IFH-0064: INVALID CONNECTION EDIABAS_IFH_0064

SETTINGS
Meaning: The connection to EDICnet could not be established.
Causes: EDICnet is not connected or the network configuration is
faulty.
Error correction: Check the network configuration. Check that EDICnet is
connected.
Target system: WIN

215 IFH-0065: FIRMWARE UPDATE ERROR EDIABAS_IFH_0065

Meaning: An error occured while updating the firmware of EDICnet.
Causes: The network connection is bad.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 69 of 117

The firmware files are missing or faulty.

Error correction: Check the network configuration. Rerun EDIC setup.
Target system: WIN

216 IFH-0066: CHANNEL ERROR EDIABAS_IFH_0066

Meaning: No free communication channel is available.
Causes: An attempt was made to open a communication channel, but
all available communication channels are in use.
Error correction: Close occupied channels.
Target system: WIN

217 IFH-0067: ECU RESPONSE PENDING EDIABAS_IFH_0067

Meaning: An ECU response is pending.
Causes: During the execution of a functional request an attempt was
made to send a non-empty telegram.
Error correction: Edit the ECU description file.
Target system: WIN

218 IFH-0068: TESTER ADDRESS ERROR EDIABAS_IFH_0068

Meaning: The available tester addresses are already being used. The
tester address used by the ECU description file (SGBD) or
substituted by the IFH erse is already in use on the connected
vehicle.
Causes: No more alternative tester address substitution could be done,
since no or no sufficient tester address substitution was
configured.
Error correction: Close one of the separate tester connections to the vehicle

Extend the tester address substitution.

Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 70 of 117

219 IFH-0069: GATEWAY ERROR EDIABAS_IFH_0069

Meaning: The central gateway ECU reported a system error.
Causes: The specific cause of the error lies in the vehicle or gateway
ECU.
Error correction: Repeat the last job.
Target system: WIN

220 IFH-0070: SYSTEM ERROR EDIABAS_IFH_0070

Meaning: A severe system error occured in the interface handler.
Causes: No sufficient system resources for correct function could be
obtained.
Error correction: Restart the EDIABAS application.

If this error should occur, please inform SOFTING.

Target system: WIN

221 IFH-0071: TELEGRAM FORMAT ERROR EDIABAS_IFH_0071

Meaning: The passed telegram format is not correct.
Causes: A telegram that doesn’t comply with the protocol was passed
to the interface handler for transmission.
Error correction: Correct the telegram to be sent.
Target system: WIN

222 IFH-0072: ECU ACCESS COLLISION EDIABAS_IFH_0072

Meaning: Access to the ECU couldn’t be granted, since another channel
was already communicating with the same ECU.
Causes: See above.
Error correction: Check the communication access of the connected ECU
description files (SGBD). Avoid access from several
simultaneously running SGBDs to the same ECU.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 71 of 117

223 IFH-0073: PROXY ERROR EDIABAS_IFH_0073

Meaning: Proxy error.
Causes: An error occured in the proxy component during internal
processing and assignment of applications to communication
channels.
Error correction: Terminate your application program and restart it. If this error
should occur, please inform SOFTING.
Target system: WIN

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors

4.2. Runtime system

More:

4.2.1. BIP, BEST Interpreter

4.2.2. SYS, sequence control

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors > 4.2. Runtime system

4.2.1. BIP, BEST Interpreter

60 BIP-0000: INTERNAL ERROR EDIABAS_BIP_0000

Meaning: The error indicates an illegal EDIABAS program state.
Causes: Program result cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

61 BIP-0001: OUT OF RANGE EDIABAS_BIP_0001

Meaning: Job parameter too long or illegal index when accessing string
registers.
Causes: This error usually always occurs whenever access is made to
an array variable with a calculated index and this is too large.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 72 of 117

Example: for max. array size 1024

i=100;

array[100*i]=50;
Error correction: Check all array accesses in your job if they contain an index
which is possibly invalid. The indexes must not exceed the
max. array size.
Target system: WIN

62 BIP-0002: IFH FUNCTION ERROR EDIABAS_BIP_0002

Meaning: The Interface Handler function cannot be executed.
Causes: Error when calling an Interface Handler function.
Error correction: Runtime system

Target system: WIN

63 BIP-0003: OBJECT FILE ERROR EDIABAS_BIP_0003

Meaning: Error when reading the ECU description file.
Causes: The ECU description file is possibly damaged or a
transmission error occurred when accessing via a network.
Error correction: If the error repeatedly occurs, re-compile the description file.
Target system: WIN

64 BIP-0004: ILLEGAL OPCODE EDIABAS_BIP_0004

Meaning: Erroneous ECU description file.
Causes: The ECU description file is possibly damaged or a
transmission error occurred when accessing via a network.
Error correction: If an error repeatedly occurs, re-compile the description file
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 73 of 117

65 BIP-0005: STACK OVERFLOW EDIABAS_BIP_0005

Meaning: Overflow of the BEST stack.
Causes: The 2 KB stack area in the BEST interpreter is too small to
execute the job. Either the job has a nesting depth which is too
large or one of the functions form the runtime library is
erroneous and does not clear the affected stack area.
Error correction: Simplify the erroneous job or determine the function which
issued this error.
Target system: WIN

66 BIP-0006: BEST FILE ERROR EDIABAS_BIP_0006

Meaning: Error when processing a BEST data file.
Causes: An error occurred in one of the BEST data commands. If this
occurs when opening the file (fopen), either the file does not
exist or it cannot be read. If the error occurred when
positioning the file pointer (BEST2 functions fseek, fseekln),
attempt was made to position the pointer outside of the file. In
the case of a read command, the error refers to a real read
problem.
Error correction: Check whether the file to be searched exists. If yes, test the
accesses to the file within the job.
Target system: WIN

67 BIP-0007: DIVISION BY ZERO EDIABAS_BIP_0007

Meaning: Division by 0.
Causes: Division by 0 occurred while a job was being executed.
Error correction: Check whether a division by 0 can occur in the code of a job.
Trap this case before the division! Example:

if(a==0)

b=1000;

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 74 of 117

else

b=1000/a;
Target system: WIN

68 BIP-0008: BEST BREAK EDIABAS_BIP_0008

Meaning: Interruption by the description file.
Causes: The command "break" (BEST/1) was called in the description
file. This command can be installed, for example, for testing
purposes in the ECU description file (SGBD).
Error correction: Remove this command form the description file.
Target system: WIN

69 BIP-0009: BEST VERSION ERROR EDIABAS_BIP_0009

Meaning: Erroneous BEST version of the ECU description file.
Causes: The ECU description file addressed was compiled by a
compiler which is not compatible with this EDIABAS version.
Error correction: Compile the ECU description file using the compiler included
in this EDIABAS version.
Target system: WIN

70 BIP-0010: CONSTANT DATA ACCESS EDIABAS_BIP_0010

ERROR
Meaning: Error when accessing constants (tables).
Causes: This error occurs with the table commands. If the specified
table or table column does not exist, this error message is
issued.
Error correction: Check whether the names of the tables and columns specified
in the ECU description file agree with the actually existing
tables.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 75 of 117

71 BIP-0011: REAL ERROR EDIABAS_BIP_0011

Meaning: Over or underflow of a mathematical function
Causes: This error occurs in connection with the real processing
functions. The representable numeric range was exceeded or
fallen short of for an arithmetical operation.
Error correction: Check the function parameters specified in the ECU
description file which were transferred to the real functions for
computing real values.
WIN

72 BIP-0012: PLUG IN NOT FOUND EDIABAS_BIP_0012

Meaning: The plug-in component was not found.
Causes: Before an ECU description file can access a plug-in
component, this component must be installed in your system.

The error occurs because the plug-in component does not exist.
Error correction: For eliminating the error, contact the developer of the ECU
description file.
WIN

73 BIP-0013: PLUG IN ERROR EDIABAS_BIP_0013

Meaning: Faulty call of the plug-in component.
Causes: In the plug-in component, an error has occurred.
Error correction: For eliminating the error, contact the developer of the ECU
description file.
WIN

74 BIP-0014: PLUG IN VERSION ERROR EDIABAS_BIP_0014

Meaning: Wrong version of Plug-In component
Causes: No correct Plug-In component for ECU description file.
Error correction: No correct installation of EDIABAS system.
WIN

75 BIP-0015: PLUG IN STACK ERROR EDIABAS_BIP_0015

Meaning: Error in Plug-In component.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 76 of 117

Causes: Error in Plug-In component

Error correction: Contact the developer of the Plug-In component.
WIN

76 BIP-0016: PLUG IN FUNCTION NOT EDIABAS_BIP_0016

FOUND
Meaning: Error in Plug-In component.
Causes: Error in Plug-In component
Error correction: Contact the developer of the Plug-In component.
WIN

77 BIP-0017: IFH CHANNEL ERROR EDIABAS_BIP_0017

Meaning: Faulty interface communication channel.
Causes: This error occurs with the interface commands. It is generated,
if the given interface channel doesn’t exist or the maximum
number of available interface channels is exceeded
Error correction: Check the interface channels given in the ECU description file.
Target system: WIN

78 BIP-0018: SYSTEM ERROR EDIABAS_BIP_0018

Meaning: Resource problem of the operating system.
Causes: The applications require to many system resources.
Error correction: Should this error occur repeatedly, you should terminate other
application programs. If this doesn’t fix the error, your system
has to be restarted.
Target system: WIN

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors > 4.2. Runtime system

4.2.2. SYS, sequence control

90 SYS-0000: INTERNAL ERROR EDIABAS_SYS_0000

Meaning: The error indicates an illegal EDIABAS program state.
Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 77 of 117

91 SYS-0001: ILLEGAL FUNCTION EDIABAS_SYS_0001

Meaning: The error indicates an illegal EDIABAS program state.
Causes: The application program transferred an illegal communication
to EDIABAS.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

92 SYS-0002: ECU OBJECT FILE NOT EDIABAS_SYS_0002

FOUND
Meaning: The ECU variant description file couldn't be found.
Causes: Either the description file does not exist in the EDIABS search
path or the search path is wrong.

EDIABAS search path:

The EDIABAS configuration element EcuPath describes the

EDIABAS search path. When the configuration setting does
not exist, the current directory is used by EDIABAS as the
search path.
Error correction: Description file does not exist:

Copy the requested description file in the EDIABAS search

path.

Search path is wrong:

Terminate the application program, and assign the correct path

to configuration element EcuPath.

In case the configuration changes, terminate EDIABAS, and

re-start:

WIN32: EDIABAS is automatically closed with

the application (automatic restart)

Re-start the application program.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 78 of 117

Target system: WIN

93 SYS-0003: ECU OBJECT FILE ERROR EDIABAS_SYS_0003

Meaning: Error when reading the ECU variant description file.
Causes: Description file may be damaged or transmission errors
occurred while accessing via a network.
Error correction: If an error repeatedly occurs, re-compile the description file.
Target system: WIN

94 SYS-0004: ILLEGAL FORMAT OF ECU EDIABAS_SYS_0004

OBJECT FILE
Meaning: Illegal format of the ECU variant description file.
Causes: The description file is damaged.
Error correction: Re-compile the description file.
Target system: WIN

95 SYS-0005: OBJECT FILE NOT FOUND EDIABAS_SYS_0005

Meaning: The ECU description file couldn't be found.
Causes: Either the description file does not exist in the EDIABAS
search path or the search path is wrong.

EDIABAS search path:

The EDIABAS configuration element EcuPath describes the

EDIABAS search path. If a configuration setting does not
exist, the current directory is used by EDIABAS as the search
path.
Error correction: Description file does not exist:

Copy the required description file in the EDIABAS search

path.

Search path is wrong:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 79 of 117

Terminate the application program, and assign the correct path

to configuration element EcuPath.

In case the configuration changed, terminate EDIABAS, and

re-start:

WIN32: EDIABAS is automatically closed with

the application (automatic restart)

Re-start the application program.

Target system: WIN

96 SYS-0006: GROUP OBJECT FILE ERROR EDIABAS_SYS_0006

Meaning: Error when reading the ECU group description file.
Causes: The description file may be damaged or transmission errors
occurred when accessing via a network.
Error correction: If the error repeatedly occurs, re-compile the description file.
Target system: WIN

97 SYS-0007: ILLEGAL FORMAT OF GROUP EDIABAS_SYS_0007

OBJECT FI LE
Meaning: Illegal format of the ECU group description file.
Causes: The description file is damaged.
Error correction: Re-compile the description file.
Target system: WIN

98 SYS-0008: JOB NOT FOUND EDIABAS_SYS_0008

Meaning: The job couldn't be found in the ECU description file.
Causes: The job is missing in the description file, or the description file
is wrong.
Error correction: Check if the desired job exists in the description file. The
program BESTINFO (contained in the RUNTIME SYSTEM)
can be used to list all job names:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 80 of 117

bestinfo <Name of the description file with path and

extension>

Also check exactly if the job is spelled correct.

If the desired job does not exist in the description file, extend
the description file by the job.
Target system: WIN

99 SYS-0009: NO INITIALIZATION JOB EDIABAS_SYS_0009

Meaning: The job INITIALISIERUNG couldn't be found in the ECU
description file.
Causes: The job INITIALISIERUNG is automatically executed by
EDIABAS; however, the job is missing in the description file.
Error correction: The description file is to be extended by the job
INITIALISIERUNG.
Target system: WIN

100 SYS-0010: INITIALIZATION ERROR EDIABAS_SYS_0010

Meaning: The job INITIALISIERUNG indicates an erroneous
initialization.
Causes: The job INITIALISIERUNG is automatically executed by
EDIABAS. Whether the initialization was successful or not is
reported with the result DONE:

DONE = 0 Error during initialization

DONE <> 0 Successful initialization

An error occurred during the job INITIALISIERUNG. The

result DONE was therefore 0.
Error correction: If an error repeatedly occurs, please contact the developer of
the description file.

The program BESTINFO (contained in the RUNTIME

SYSTEM) can be used to list the names of the description file
developer:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 81 of 117

bestinfo < Name of the description file with path

and extension>
Target system: WIN

101 SYS-0011: NO IDENTIFICATION JOB EDIABAS_SYS_0011

Meaning: The job IDENTIFIKATION couldn't be found in the ECU
group description file.
Causes: The job IDENTIFIKATION is automatically executed by
EDIABAS; however, the job is missing in the description file.
Error correction: The description file is to be extended by the job
IDENTIFIKATION.
Target system: WIN

102 SYS-0012: IDENTIFICATION ERROR EDIABAS_SYS_0012

Meaning: The job IDENTIFIKATION in the ECU group description file
couldn't identify the ECU variant.
Causes: The job IDENTIFIKATION is automatically executed by
EDIABAS. Whether the identification was a success or not is
displayed with the result VARIANTE:

Variant couldn't be identified:

VARIANTE = < empty >

Variant successfully identified:

VARIANTE = < Name of the ECU variant

description file without extension>

An error occurred during job IDENTIFIKATION. The result

VARIANTE was therefore empty.
Error correction: If an error repeatedly occurs, please contact the developer of
the description file.

The program BESTINFO (contained in the RUNTIME

SYSTEM) can be used to list the name of the description file
developer:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 82 of 117

bestinfo < Name of the description file with path

and extension>
Target system: WIN

103 SYS-0013: UNEXPECTED RESULT EDIABAS_SYS_0013

Meaning: An illegal result was returned either in the job
IDENTIFIKATION of the ECU group description file or in the
job INITIALISIERUNG of the group or variant description
file.
Causes: The job IDENTIFIKATION may only return the result
VARIANTE, and the job INITIALISIERUNG may only return
the result DONE.

Another result, however, was returned in one of the jobs

mentioned.
Error correction: If an error occurs, please contact the developer of the
description file.

The program BESTINFO (contained in the RUNTIME

SYSTEM) can be used to list the name of the description file
developer:

bestinfo < Name of the description file with path and

extension>
Target system: WIN

104 SYS-0014: ILLEGAL FORMAT EDIABAS_SYS_0014

Meaning: The error indicates an illegal EDIABAS program state.
Causes: A result format cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 83 of 117

105 SYS-0015: TASK COMMUNICATION EDIABAS_SYS_0015

ERROR
Meaning: Communication between EDIABAS and the application
program is disturbed.
Causes: Communication data from the application program is incorrect.
Error correction: If this error repeatedly occurs, re-start the application program.
If the error is still not corrected, re-start your system.
Target system: WIN

106 SYS-0016: ILLEGAL CONFIGURATION EDIABAS_SYS_0016

Meaning: EDIABAS configuration couldn't be executed.
Causes: An illegal configuration setting resides in the EDIABAS
configuration file EDIABAS.INI.
Error correction: Terminate the application program, and check all EDIABAS
configuration settings.

After correcting the configuration, terminate EDIABAS, and

re-start:

WIN32: EDIABAS is automatically closed with

the application (automatic restart)

Re-start the application program.

Target system: WIN

107 reserviert for future EDIABAS versions EDIABAS_SYS_0017

Meaning

108 SYS-0018: END JOB ERROR EDIABAS_SYS_0018

Meaning: A processing error occurred in the job ENDE.
Causes: The job ENDE is automatically executed by EDIABAS. An

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 84 of 117

error occurred while a job was being processed, or a result was

returned.
Error correction: If an error repeatedly occurs, please contact the developer of
the description file.

The program BESTINFO (contained in the RUNTIME

SYSTEM) can be used to list the name of the description file
developer:

bestinfo < Name of the description file with path

and extension>
Target system: WIN

109 SYS-0019: TIMER ERROR EDIABAS_SYS_0019

Meaning: Error when requesting a timer by EDIABAS.
Causes: All timers under Windows are already used by other Windows
programs.
Error correction: Terminate other Windows programs with timer use; e.g.
Windows clock programs.
Target system: WIN

110 SYS-0020: BASE OBJECT FILE NOT EDIABAS_SYS_0020

FOUND
Meaning: The ECU base description file couldn't be found.
Causes: Either the EDIABAS search path does not exist in the
description file, or the search path is wrong.

EDIABAS search path:

The EDIABAS configuration element EcuPath describes the

EDIABAS search path. If a configuration setting does not
exist, the current directory is assumed by EDIABAS as the
search path.
Error correction: Description file does not exist:

Copy the required description file in the EDIABAS search

path.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 85 of 117

Search path is wrong:

Terminate the application program, and assign the correct path

to the configuration element EcuPath.

If the configuration changed, terminate EDIABAS, and re-

start:

WIN32: EDIABAS is automatically closed with

the application (automatic restart)

Re-start the application program.

Target system: WIN

111 SYS-0021: BASE OBJECT FILE ERROR EDIABAS_SYS_0021

Meaning: Error when reading the ECU base description file.
Causes: The description file may be damaged, or transmission errors
occurred while accessing via a network.
Error correction: If the error repeatedly occurs, re-compile the description file.
Target system: WIN

112 SYS-0022: ILLEGAL FORMAT OF BASE EDIABAS_SYS_0022

OBJECT FILE
Meaning: Illegal format of the ECU base description file.
Causes: The description file is damaged.
Error correction: Re-compile the description file.
Target system: WIN

113 SYS-0023: PASSWORD ERROR EDIABAS_SYS_0023

Meaning: Error when starting the EDIABAS runtime system.
Causes: The EDIABAS system was incorrectly installed, or the
installation was subsequently changed by manually copying
files.
Error correction: Re-install EDIABAS.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 86 of 117

Target system: WIN

114 SYS-0024: ILLEGAL PASSWORD EDIABAS_SYS_0024

Meaning: The ECU description file cannot be executed.
Causes: The ECU description file is protected with passwords which
are not known by the runtime system.
Error correction: If the description file exists as source code (B2G, B2V), re-
compile the description file with a password known by the
system.

If the description file only exists in object format (GRP, PRG),

the error cannot be corrected.
Target system: WIN

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors

4.3. API, Application Programming Interface

120 API-0000: INTERNAL ERROR EDIABAS_API_0000

Meaning: The error indicates an illegal EDIABAS program state.
Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

121 API-0001: USER BREAK EDIABAS_API_0001

Meaning: The job was aborted.
Causes: The job was aborted by the application program. Abortion of
EDIABAS by the application program (apiEnd) can also abort

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 87 of 117

a job in progress.
Error correction: Please contact the developer of the application program.
Target system: WIN

122 API-0002: MEMORY ALLOCATION EDIABAS_API_0002

ERROR
Meaning: Not enough working memory (RAM).
Causes: The working memory does not suffice for the results returned
from the job.
Error correction: If this error repeatedly occurs, terminate other application
programs in order to increase the working memory available.
Target system: WIN

123 API-0003: RESULT SETS OVERFLOW EDIABAS_API_0003

Meaning: The job returns too many result records.
Causes: The maximum possible number of result records comprises
65535. Too many result records were returned from the job.
Error correction: Reduce the number of result records in the job.

If applicable, contact the developer of the description file.

The program BESTINFO (contained in the RUNTIME

SYSTEM) can be used to list the name of the description file
developer:

bestinfo < Name of the description file with path

and extension>
Target system: WIN

124 API-0004: RESULTS OVERFLOW EDIABAS_API_0004

Meaning: The job returned too many results.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 88 of 117

Causes: The maximum possible number of results within a result

record is limited to 65535. From the job, too many results were
returned within a record set.
Error correction: Reduce the number of results within the result record.

If applicable, please contact the developer of the description

file.

The program BESTINFO (contained in the RUNTIME

SYSTEM) can be used to list the name of the description file
developer:

bestinfo < Name of the description file with path

and extension>
Target system: WIN

125 API-0005: ILLEGAL RESULT FORMAT EDIABAS_API_0005

Meaning: Illegal result format.
Causes: A result cannot be converted into the format desired by the
application program. This is the case when arbitrary formats
are converted from or into the APIBINARY format. Also, an
error can occur when converting a value from or into the
APITEXT format.
Error correction: Please contact the developer of the application program for
matching the result format to the description file (or vice
versa).
Target system: WIN

126 API-0006: ACCESS DENIED EDIABAS_API_0006

Meaning: Access of the application to EDIABAS is currently not
possible.
Causes: At the time no further application programs can access
EDIABAS.
Error correction: If this error repeatedly occurs, terminate a program with access
to EDIABAS.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 89 of 117

127 API-0007: INCORRECT EDIABAS_API_0007

CONFIGURATION FILE
Meaning: Error when reading configuration file ipc.ini, or application
program uses an old version of API library.
Causes: The path of configuration file ipc.ini must be stored in the
environment variable IPC_CONFIG (only with UNIX).

The error occurs with wrong or unassigned environment

variable IPC_CONFIG. Also, the error then occurs when the
configuration file ipc.ini does not exist in the path specified by
the environment variable IPC_CONFIG.The error also occurs
when the application program uses an old version of API
library.

Error correction: Check the assignment of the environment variable

IPC_CONFIG. When the environment variable IPC_CONFIG
is properly set, check if configuration file ipc.ini exists. Your
application program must contain read access to configuration
file IPC.INI and a compatible version of the API library.
Target system: WIN

128 API-0008: TASK COMMUNICATION EDIABAS_API_0008

ERROR
Meaning: Communication between the application program and
EDIABAS is disturbed.
Causes: Communication data from EDIABAS are erroneous, or the
communication medium is damaged. If EDIABAS does not
respond within a specified time, this error is also issued.
Error correction: If this error repeatedly occurs, re-start the application program.
If the error is still not corrected, re-start your system.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 90 of 117

129 API-0009: EDIABAS NOT FOUND EDIABAS_API_0009

Meaning: EDIABAS is not installed or cannot be found.
Causes: Before an application program accesses EDIABAS, this must
be installed on your system. EDIABAS must be started prior to
starting an application program.

The error occurred due to a fail start of EDIABAS.

Error correction: Terminate the application program, and check whether
EDIABAS is correctly installed on your system

Start EDIABAS if this has not already been done:

WIN: Occurs automatically

Re-start your application program.

Target system: WIN

130 API-0010: ILLEGAL EDIABAS VERSION EDIABAS_API_0010

Meaning: Wrong EDIABAS version installed.
Causes: The application requires a different EDIABAS version than
that which is installed.
Error correction: Install the required EDIABAS version.

If applicable, contact the developer of the application program.

Target system: WIN

131 API-0011: ILLEGAL ECU PATH EDIABAS_API_0011

Meaning: Illegal ECU path.
Causes: The configuration element EcuPath is assigned with an invalid
path
Error correction: Terminate the application program, and correct the
environment variable ECU.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 91 of 117

132 API-0012: SIGNAL SERVER NOT FOUND EDIABAS_API_0012

Meaning: This error doesn’t exist any more from EDIABAS V7.0.0.

The error code and associated constants still exist for

compatibility.
Causes: -
Error correction: -
Target system: WIN

133 API-0013: INITIALIZATION ERROR EDIABAS_API_0013

Meaning: Error in initializing EDIABAS.
Causes: The application program did not initialize EDIABAS
(apilnit/apiInitExt) prior to accessing EDIABAS.
Error correction: Please contact the developer of the application program.
Target system: WIN

134 API-0014: RESULT NOT FOUND EDIABAS_API_0014

Meaning: Error interrogating a result.
Causes: The result requested from the application program was not
returned in the required result record by the job.
Error correction: Add result in the result record.

If applicable, contact the developer of the application program.

Target system: WIN

135 API-0015: HOST COMMUNICATION EDIABAS_API_0015

ERROR
Meaning: Communication between API-DLL and EDIABAS is
disturbed.
Causes: Communication data from EDIABAS are erroneous, or the

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 92 of 117

communication medium is damaged. If EDIABAS does not

respond within a specified time, this error is also issued.
Error correction: If this error repeatedly occurs, re-start the application program.
If the error has still not been corrected, re-start your system.
Target system: WIN

136 API-0016: RESULT OVERFLOW EDIABAS_API_0016

Meaning: Job result too long.
Causes: The job result buffer provided by the application is not
sufficient.
Error correction: Contact the developer of the application program to discuss the
job result buffer in the description file.
Target system: WIN

137 API-0017: ARGUMENT OVERFLOW EDIABAS_API_0017

Meaning: Job argument too long.
Causes: The job argument passed to the description file is too big.
Error correction: Contact the developer of the application program to discuss the
job in the description file.
Target system: WIN

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors

4.4. Network

150 NET-0000: INTERNAL ERROR EDIABAS_NET_0000

Meaning: The error indicates an illegal program EDIABAS state.
Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 93 of 117

Target system: WIN

151 NET-0001: UNKNOWN ERROR EDIABAS_NET_0001

Meaning: Unknown error.
Causes: Network communication is disturbed.
Error correction: If this error repeatedly occurs, re-start the application program.
If this error is still not corrected, re-start your system.
Target system: WIN

152 NET-0002: ILLEGAL VERSION EDIABAS_NET_0002

Meaning: Illegal version of NET<Protocol>-DLL.
Causes: The version of NET<Protocol>-DLL does not match the
version of the EDIABAS components XREMOTE/XRPLUS
or IFH server.
Error correction: Re-install the required EDIABAS version.
Target system: WIN

153 NET-0003: INITIALIZATION ERROR EDIABAS_NET_0003

Meaning: Error when initializing the network.
Causes: The network software cannot be simultaneously operated by
several clients (EDIABAS and BestView).
Error correction: Terminate EDIABAS or BestView.
Target system: WIN

154 NET-0004: ILLEGAL CALL EDIABAS_NET_0004

Meaning: The error indicates an illegal EDIABAS program state.
Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error still happens to occur,
please contact SOFTING.
Target system: WIN

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 94 of 117

155 NET-0005: NO SUPPORT EDIABAS_NET_0005

Meaning: The error indicates an illegal EDIABAS program state.
Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error still happens to occur,
please contact SOFTING.
Target system: WIN

156 NET-0006: ACCESS DENIED EDIABAS_NET_0006

Meaning: The network access is denied.
Causes: The network software cannot be simultaneously operated by
the client (EDIABAS or BestView) and server (IFH-Server).
Error correction: Check the value of the EDIABAS configuration element
Interface, and terminated the client or server.
Target system: WIN

157 NET-0007:SYSTEM ERROR EDIABAS_NET_0007

Meaning: Resource problem of the operating system.
Causes: The applications require too many system resources.
Error correction: If this error repeatedly occurs, terminate other application
programs. If this error is still not corrected, re-start your
system.
Target system: WIN

158 NET-0008: NETWORK ERROR EDIABAS_NET_0008

Meaning: General network problem.
Causes: The network cannot be correctly operated.
Error correction: If this error repeatedly occurs, re-start the application program.
If this error is still not corrected, re-start your system.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 95 of 117

Target system: WIN

159 NET-0009: TIMEOUT EDIABAS_NET_0009

Meaning: Communication partner does not respond.
Causes: The communication setup or the communication with the
communication partner is not possible.

The communication partner is known in the network.

Error correction: Check the transmission medium.

Check whether the communication partner properly runs.

Check whether the IFH server runs on the system of the

communication partner.

Check whether the EDIABAS configuration element Port of

the communication partner agrees with the own system.

If this error continues to occur, re-start the application.

Target system: WIN

160 NET-0010: BUFFER OVERFLOW EDIABAS_NET_0010

Meaning: The error indicates an illegal EDIABAS program state.
Causes: A program result cannot be processed.
Error correction: Not possible by the user. If this error happens to occur, please
contact SOFTING.
Target system: WIN

161 NET-0011: ALREADY CONNECTED EDIABAS_NET_0011

Meaning: Communication could not be established.
Causes: The connection to the communization partner is already
established.
Error correction: If this error repeatedly occurs, re-start the application program.
If the error is still not corrected, re-start your system.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 96 of 117

Target system: WIN

162 NET-0012: NO CONNECTION EDIABAS_NET_0012

Meaning: No connection to the communication partner.
Causes: Communication with the communication partner is not
possible, since no connection exists.
Error correction: If this error repeatedly occurs, re-start the application program.
If the error is still not corrected, re-start your system.
Target system: WIN

163 NET-0013: CONNECTION DISTURBED EDIABAS_NET_0013

Meaning: Connection to the communication partner disturbed.
Causes: Communication with the communication partner is disturbed.
Error correction: Check the transmission medium.

Check whether the communication partner properly runs.

If the error is still not corrected, re-start your system

Target system: WIN

164 NET-0014: CONNECTION ABORTED EDIABAS_NET_0014

Meaning: No connection to the communication partner.
Causes: Communication was aborted by the communication partner.
Error correction: Check the communication partner, and re-start the application
program.
Target system: WIN

165 NET-0015: HOST NOT FOUND EDIABAS_NET_0015

Meaning: The other communication partner or its network address
couldn't be found.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 97 of 117

Causes: Invalid EDIABAS configuration element RemoteHost.

Error correction: Check the EDIABAS configuration element RemoteHost, and
re-start the application program
Target system: WIN

166 NET-0016: HOST ERROR EDIABAS_NET_0016

Meaning: Communication partner couldn't be reached.
Causes: Communication setup or communication with the
communication partner is not possible.

The communication partner is known in the network.

Error correction: Check whether the communication partner properly runs.

Check the EDIABAS configuration element Port.

Target system: WIN

167 NET-0017: PROTOCOL NOT EDIABAS_NET_0017

AVAILABLE
Meaning: Protocol or network manager NET<Protocol>-DLL not
available.
Causes: Erroneous EDIABAS configuration element NetworkProtocol
or missing NET<Protocol>-DLL in the EDIABAS\program
directory.
Error correction: Check the EDIABAS configuration element
NetworkProtocol.

EDIABAS must be re-installed with the correct configuration

value.
Target system: WIN

168 NET-0018: UNKNOWN PROTOCOL EDIABAS_NET_0018

Meaning: Unknown network protocol.
Causes: Unassigned EDIABAS configuration element

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 98 of 117

NetworkProtocol.
Error correction: Assign the network protocol to be used (e.g. TCP for TCP/IP)
to the EDIABAS configuration element NetworkProtocol.
Target system: WIN

169 NET-0019: UNKNOWN SERVICE EDIABAS_NET_0019

Meaning: Unknown network service or port.
Causes: Unassigned EDIABAS configuration element Port.
Error correction: Assign the port number to be used to the EDIABAS
configuration element Port. The port number of the
communication partner must agree with that of the own system
Target system: WIN

170 NET-0020: UNKNOWN HOST EDIABAS_NET_0020

Meaning: Unknown communication partner.
Causes: Unassigned EDIABAS configuration element RemoteHost.
Error correction: Assign the host name or the host address of the communication
partner to the EDIABAS configuration element RemoteHost.
Target system: WIN

171 NET-0021: SERVER NOT FOUND EDIABAS_NET_0021

Meaning: Communication partner is not avilable.
Causes: IFH server not running
Error correction: Check IFH server is running

Target system: WIN

172 NET-0022: SECURITY ERROR EDIABAS_NET_0022

Meaning: During communication a security problem occured
Causes: Missing access rights

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 99 of 117

Error correction: Check access rights

Target system: WIN

EDIABAS User's Guide > EDIABAS Error Reference > 4. List of errors

4.5. Application

EDIABAS_RUN_0000
250 RUN-0000
..
.. .. EDIABAS_RUN_0099
RUN-0099
349
Meaning: No valid status in SGBD.
Causes: Error was set by SGBD.
Error correction: Contact the devolper of the ECU description file.
Target system: WIN

In ECU description files(SGBD) an SGBD-specific EDIABAS runtime error can be provoked.

Appraisal and reaction to the error must be coordinated with the SGBD’s developer.

EDIABAS User's Guide > EDIABAS Error Reference

A. References
[1] EDIABAS: API Interface Description

[2] EDIABAS: User Manual

EDIABAS User's Guide

ECU Simulator
More:

1. Revision history

2. Introduction

3. General

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 100 of 117

4. Overview

5. Control

6. Error messages

7. Syntax and contents of the simulation files

8. Simulation files

A. References

EDIABAS User's Guide > ECU Simulator

1. Revision history
Version 3.0 First release

Version 3.0A Revised

Version 4.1 Revised for EDIABAS V4.1.0
Version 5 Revised for EDIABAS V5.1.0
Version 5a Extended for EDIABAS V5.5.0
Version 5b Extended for QNX
Version 6 Revised for EDIABAS V6.0.0
Version 6a Revised for EDIABAS V6.4.4
Version 7 No more support for DOS, Win16, QNX
Revised für EDIABAS V7.0.0
Version 7a Improvement of interface error descriptions
Version 7b Revised for EDIABAS V7.2.0
Version 7c Revised for EDIABAS V7.2.0

EDIABAS User's Guide > ECU Simulator

2. Introduction
More:

2.1. About this manual

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 101 of 117

2.2. Notational conventions

2.3. Special features, terms, acronyms

EDIABAS User's Guide > ECU Simulator > 2. Introduction

2.1. About this manual

This manual describes how to use the ECU (Electronic Control Unit) Simulator integrated in
EDIABAS. General information about EDIABAS and the ECU description files can be found in
[1].

EDIABAS User's Guide > ECU Simulator > 2. Introduction

2.2. Notational conventions

The following typographical conventions are used throughout this manual:

Example Description
SAMPLE.B2V Uppercase denotes file names, registers and operating
system commands.
job, string, while Bold-faced type identifies keywords and operators of the
language BEST/2 and BEST/s as well as the API functions.

These words must be written exactly as specified in syntax

descriptions.
expression Italics designate placeholders for values to be entered by
the programmer; e.g., file names..
[option] Words enclosed in square brackets may be optionally
specified.
{ result | Curvy braces and vertical strokes characterize entries from
argument } which only one must be selected, except when in square
brackets.
[constant...] job... An ellipsis (three dots) which directly follows an
expression indicates that several expressions of the same
type can follow.
hallo="Test"; This syntax designates examples, user entries, program
outputs and error messages.
while() { A column or a row comprising three dots indicates that a
section of an example was intentionally omitted.
.

.}
[1] Reference to a document in References.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 102 of 117

EDIABAS User's Guide > ECU Simulator > 2. Introduction

2.3. Special features, terms, acronyms

An explanation of the abbreviations used in this and all other EDIABAS documentation can be
found in the publication "EDIABAS User Manual" in chapter "GLOSSARY".

EDIABAS User's Guide > ECU Simulator

3. General
The response behavior of the diagnostic bus interface and the ECUs can be simulated in EDIABAS.
This scope of functions is designated ECU Simulator. The ECU Simulator is a constituent of
EDIABAS. From the user and the application program view, EDIABAS behaves identically in
simulation and normal mode. So-called "simulation files" control the ECU Simulator.

The ECU Simulator is an indispensable tool for developing and testing ECU description files and
application programs. In simulation mode, jobs from the ECU description files can be executed
without a real diagnostic bus interface and ECU.

EDIABAS User's Guide > ECU Simulator

4. Overview
The ECU Simulator is a part of the Interface Handler (IFH) and, hence, EDIABAS. It is accessed
EDIABAS-internally via the general procedural IFH interface. There are no special access
functions for the ECU Simulator which exceed the normal functional scope of the API interface;
i.e. no special adaptations have to be made to the application program. The ECU Simulator is
controlled via a series of simulation files which determine how the ECU Simulator is to respond to
the requests of jobs to the diagnostic interface or ECUs.

Neither device drivers nor diagnostic bus interface and ECU are required for simulation.

EDIABAS User's Guide > ECU Simulator

5. Control
The ECU Simulator is controlled via three different types of "simulation files". These files are text
files and can therefore be edited using every text editor. Since the simulation files are closed again
after each access, an ECU description file can be debugged in the development environment under
Windows, and a simulation file can simultaneously be edited.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 103 of 117

More:

5.1. EDIABAS configurations for simulation

5.2. Interface simulation file

5.3. ECU simulation file

EDIABAS User's Guide > ECU Simulator > 5. Control

5.1. EDIABAS configurations for simulation

The ECU Simulator is enabled and disabled by means of the EDIABAS configuration element
Simulation:

Simulation = 0 (Simulation disabled)

Simulation = 1 (Simulation enabled)

The path containing the ECU simulation files is determined using the EDIABAS configuration
element SimulationPath:

SimulationPath = < directory >

The interface to be simulated is determined by the configuration element Interface:

Interface = < Name of the hardware interface >

EDIABAS User's Guide > ECU Simulator > 5. Control

5.2. Interface simulation file

There is an interface simulation file for each diagnostic bus interface supported by EDIABAS with
which the behavior of the interface can be simulated (see section "Simulations files/Interface
simulation file").

EDIABAS User's Guide > ECU Simulator > 5. Control

5.3. ECU simulation file

ECU simulation files can be created for each ECU by the user. These files can be used to simulate
the response behavior of the ECUs (see section "Simulation files/ECU simulation file").

EDIABAS User's Guide > ECU Simulator

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 104 of 117

6. Error messages
In simulation mode, a series of error messages have a different cause as than in normal EDIABAS
operation. These error messages are listed below:

IFH-0002: NO RESPONSE FROM INTERFACE

This error message is issued when attempt is made to access simulation data which do not
exist in the file when accessing an interface simulation file (e.g., when a certain message or
label is not found).

IFH-0009: NO RESPONSE FROM CONTROLUNIT

This message is issued when attempt is made to access data which do not exist in the file
when accessing an ECU simulation file (e.g., when a certain message or label is not found).

IFH-0026: SIMULATION ERROR

This error message is issued whenever:

• The interface simulation file is not found.

• The ECU simulation is not found.
• The simulation files under UNIX are not lowercase.
• The simulation file has an incorrect file format (e.g., CR-LF instead of only LF at the
end of the line under UNIX).
• An error occurs when accessing (e.g., open, close, read, syntax) a simulation file.
• A certain block in a simulation file cannot be found.
This error message does not occur in normal EDIABAS operation.

EDIABAS User's Guide > ECU Simulator

7. Syntax and contents of the simulation files

Each simulation file consists of both function blocks in which several labels (text marks) may exist
and comments. Function blocks are described in the section following the next.

Each function block begins with a heading (title) which must be enclosed in square brackets and
ends before the beginning of a new function block or with the file end. Related data (e.g., request
messages to an ECU or response messages of an ECU) are both combined in a function block.

A label is assigned to each date (e.g., a message, a version number or a voltage). The label
represents the "Name" of the date:

; This is a comment

;Function block:

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 105 of 117

[Function block]

Label1 = 10000 ;Comment to Label1

Label2 = 00,01,02 ;Comment to Label2

More:

7.1. Syntax

7.2. Function blocks

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files

7.1. Syntax

The names of function block headings and labels may consist of the following characters:

"A"-"Z", "a"-"z", "0"-"9" ,"_"

All names (both the name of the block heading and the name of a label)can be written in either
upper- or lowercase (e.g., "Version" or "version"). The length of a name must not exceed 63
characters.

An assignment must follow each label (except in the block Response) (e.g., UBatt = 13000).

Valid delimiters are blanks and tab characters.

Binary data (interface messages or ECU messages) are written in hexadecimal format and are
separated by a comma (e.g., "01,02,0A,0a,FF"). No delimiters may appear within the binary string
except for the characters "X" or "x" (both upper- or lowercase is allowed) and "_". The upper- or
lowercase characters "X" or "x" in a block "REQUEST" may represent a number in a binary data
string. (e.g., 0X for 00 to 0F, XA for 0A to FA and XX for 00 to FF). Agreements with arbitrary
characters can be caused using this 'X' character in blocks which represent data from the interface
handler to the interface or ECU. An underscore "_" represents a message with a length of null.

Example:

[REQUEST] ;Block heading

;Label with message assignment

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 106 of 117

id_lesen = 06,00,01,00,07,00

;Label with message assignment

ram_lesen = 06,00,01,XX,XX,XX

; Response is made to all messages

; beginning with 06,00,01 and 6 characters long

;For message of the length 0

empty = _

;Label with voltage assignment (mV))

voltage = 12000

Comments always begin with a semicolon (";"). Afterwards, all characters up to the end of the line
comprise the comment. Comments may consist of all characters.

Example:

; One-line comment

[BLOCK] ; Comment following a block title

Label = 1234 ; Comment following an assignment

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files

7.2. Function blocks

The name of a function block heading is enclosed in square brackets, whereby delimiters are not
allowed within. The sequence of the blocks within the simulation file is arbitrary. Section
"Simulation files" describes which function blocks are to be entered in the matching simulation
files.

Example:

[BLOCK]

The following function blocks exist:

More:

7.2.1. VERSION

7.2.2. POWERSUPPLY

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 107 of 117

7.2.3. IGNITION

7.2.4. PORT

7.2.5. REQUEST

7.2.6. RESPONSE

7.2.7. LOOPTEST

7.2.8. KEYBYTES

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.1. VERSION

Block title: VERSION

Description: This block contains the version number of the interface firmware (especially
EDIC) as 2 bytes in hexadecimal notation, separated by comma.

Two bytes in the sequence <Low byte> <High byte> come from the interface.
The <High byte> has the value 00; t <Low byte> contains the version
number.

Label: Version

Example:

Low byte High byte Dec. value Version number

1E 00 30 3.0

Version = 1E,00

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.2. POWERSUPPLY

Block title: POWERSUPPLY

Description: This block contains the value for the battery voltage in millivolts as decimal
notation. The values of the system results UBATTCURRENT and
UBATTHISTORY can also be determined in this block.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 108 of 117

Label: Ubatt

Example:

Ubatt = 12000 ;Millivolts

Label: UbattCurrent

Example:

UbattCurrent = 1 ; Ubatt is on

Label: UbattHistory

Example:

UbattHistory = 0 ; Ubatt was off

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.3. IGNITION

Block title: IGNITION

Description: This block contains the voltage value at the ignition in millivolts as decimal
notation. The values of the system results IGNITIONCURRENT and
IGNITIONHISTORY can also be determined in this block.

Label: Ignition

Example:

Ignition = 12000 ;Millivolts

Label: IgnitionCurrent

Example:

IgnitionCurrent = 0 ; Ignition is off

Label: IgnitionHistory

Example:

IgnitionHistory = 0 ; Ignition was off

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 109 of 117

Function blocks

7.2.4. PORT

Block title: PORT

Description: This block contains the values which are applied at the individual ports. The
values at the ports zero to eight are the voltages on the analog inputs in
millivolts (EDIC). The value at port nine is the digital value of the jumper
field (EDIC).

Labels: Port_0 bis Port_9

Example:

Port_5 = 5000 ;Millivolts

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.5. REQUEST

Block title: REQUEST

Description: This block contains the requests (messages) to the interface or an ECU. A label
is assigned to each request. The label names in this block can be selected by
the user. For each label, the block "RESPONSE" must contain a label with
the same name to which the response to the corresponding request is
assigned. If the request contains an "X", this character represents an arbitrary
number. If the request contains "_ , the character represents a message with
the length 0.

Label: Any

Example:

Telegramm1= _

Telegramm2= 01,02,XX,03

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.6. RESPONSE

Block title: RESPONSE

Description: This block contains the responses to the requests contained in block

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 110 of 117

"REQUEST". This block may also contain labels without assignments; in this case, 0 bytes are
returned as a (valid) response message.

Label: See REQUEST

Example:

Telegramm1= 11,22,33,44

Telegramm2= 55,66,77,88

diagEnde =

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.7. LOOPTEST

Block title: LOOPTEST

Description: This block contains the result of the line test. 0 designates that the test is not
OK; 1 designates that the test is OK.

Label: Looptest

Example:

Looptest = 1 ;Test OK

EDIABAS User's Guide > ECU Simulator > 7. Syntax and contents of the simulation files > 7.2.
Function blocks

7.2.8. KEYBYTES

Block title: KEYBYTES

Description: This block returns the key bytes and the identification data of an ECU (when
provided in ECU concept).

Label: Keybytes

Example:

Keybytes = 01,02,04,07 ;....

EDIABAS User's Guide > ECU Simulator

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 111 of 117

8. Simulation files
More:

8.1. Interface simulation file

8.2. ECU simulation file

EDIABAS User's Guide > ECU Simulator > 8. Simulation files

8.1. Interface simulation file

A separate simulation file exists for each interface to be simulated. The file name consists of the
interface name with the extension ".SIM" (e.g. EDIC.SIM). The name of the simulation file must
be written in lowercase under UNIX. The simulation file must exist in the correct file format (under
MS-DOS/WINDOWS CR-LF, under UNIX only LF at the end of the line. The setting of the
EDIABAS configuration element is to be used as the interface name Interface. The interface
simulation files contain the interface-specific return values. The following function blocks are to be
entered in this file:

• VERSION
• POWERSUPPLY
• IGNITION
• PORT
• LOOPTEST
• REQUEST
• RESPONSE

A special mechanism was implemented for the interface EDIC for sending and receiving an ECU
message in raw mode; i.e., the data are sent 1:1 to the diagnostic bus interface without
interpretation. Sending and receiving an ECU message is conducted in the following manner:

1. Send a message to an ECU (control bytes 04,00 + message data). For this purpose, the request
message is entered with leading underscore in the block REQUEST.

[REQUEST] ; Request messages to the interface

_send_id_lesen = 04,00,01,00,00,03,00,00

The interface responds with BUSY for acknowledgment (control bytes 01,00). This response is
entered under RESPONSE.

[RESPONSE] ; Responses from interface

_send_id_lesen = 01,00

2. In order to read the ECU response from the diagnostic bus interface, the interface status must be
interrogated (control bytes 07,00). This request is entered again under REQUEST.

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 112 of 117

[REQUEST] ; Request message to the interface

_send_id_lesen = 04,00,01,00,00,03,00,00

requestState = 07,00

If the control bytes 07,00 are sent directly after an ECU message request, the response does not
appear under the same label as the request (in the example "requestState"). Instead, however, it
under the label of the ECU message request (now, however, with a leading "X" (in the example
"Xsend_id_lesen").

[RESPONSE] ; Interface response

_send_id_lesen = 01,00

Xsend_id_lesen = 02,00,0D,01,F6,30,32,38,35,30,30,36,30,30,34;,...

requestState = 00,00

The response appears under the same label as the request (in example "requestState" only when the
control bytes 07,00 are sent without pervious ECU message request.

Example:

;*************************************************

;*********** Simulation file for EDIC ************

;*************************************************

[VERSION] ; Version number of the interface

Version = 5

[POWERSUPPLY] ; Supply voltage

Ubatt = 12000 ; Supply voltage in millivolts

UbattCurrent = 1 ; Supply voltage is on

UbattHistory = 1 ; Supply voltage was on

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 113 of 117

[IGNITION] ; Ignition

Ignition = 12000 ; Ignition voltage in millivolts

IgnitionCurrent = 1 ; Voltage in on

IgnitionHistory = 0 ; Voltage was off

[PORT] ; Input values for the ports 0 to 8

Port_0 = 10

Port_1 = 21

Port_2 = 32

Port_3 = 43

Port_4 = 54

Port_5 = 65

Port_6 = 76

Port_7 = 87

Port_8 = 98

[REQUEST] ; Request messages to the interface

reset = 01,00

resetParameter = 02,00

setParameter = 03,00,03,00,02,10,01,00,00,D0,07,F4,01,01

stopFrequent = 06,00

requestState = 07,00

requestIdent = 08,00

requestLastMsg = 09,00

version = 0A,00

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 114 of 117

loopTest = 0B,00

baudrate = 20,00,00 ;Baud rate is 9600 Baud

readJumper = 21,00

setDigiOut = 22,00,FF,FF ; Set all outputs

setProgVlt = 23,00,10,27,01 ; Voltage at 10 volts

getAnalog = 24,00,00 ; Analog input 0

switchSiR = 26,00,E8,03 ;1000 ms

_send_id_lesen = 0X,00,01,00,00,03,00,00

_send_fs_loeschen = 0X,00,01,00,00,03,00,05

_send_diagende = 0X,00,01,00,00,03,00,06

_send_fs_lesen = 0X,00,0A,00,00,03,00,07

_send_ack = 0X,00,01,00,00,03,00,09

[RESPONSE] ; Responses from interface

reset = 00,00

resetParameter = 00,00

setParameter = 00,00

stopFrequent = 00,00

requestState = 00,00

requestIdent = 00,00,04,01,09,03,0D,01,F6,30,32,38,31,30,30;,...

requestLastMsg = 00,00

version = 00,00,03,00

loopTest = 0A,00

baudrate = 00,00

readJumper = 00,00,3F

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 115 of 117

setDigiOut = 00,00

setProgVlt = 00,00

getAnalog = 00,00,E8,03 ;1000 millivolts

switchSiR = 00,00

_send_id_lesen = 01,00

Xsend_id_lesen = 02,00,0D,01,F6,30,32,38,35,30,30,36,30,30,34;,...

_send_fs_loeschen = 01,00

Xsend_fs_loeschen = 02,00,03,00,09

_send_diagende = 01,00

Xsend_diagende = 02,00

_send_fs_lesen = 01,00

Xsend_fs_lesen = 02,00,10,DB,FC,B2,04,8A,00,05,A5,03,1A,01,02;,...

_send_ack = 01,00

Xsend_ack = 02,00,03,00,09

[LOOPTEST] ; Result of the Looptest

Looptest = 1

EDIABAS User's Guide > ECU Simulator > 8. Simulation files

8.2. ECU simulation file

A simulation file exists for each ECU for which contains an own diagnostic bus address. This file
contains the request and the response messages of the ECU. Except for the extension ".SIM" (e.g.
DME31.SIM), this file has the same name as the ECU description file. The name of the simulation
file must be written is lowercase under UNIX. The simulation file must exist in the correct file
format (under MS-DOS/WINDOWS CR-LF, under UNIX only LF at the end of the line). The
following function blocks are to be entered in these files:

• REQUEST

• RESPONSE
• KEYBYTES

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 116 of 117

Example:

;****************************************************

;********* Simulation file for the DME31 **********

;****************************************************

[REQUEST] ; Request message to the ECU

empty =_

id_lesen = 03,00,00

ram_lesen = 06,00,01,00,00,00

fs_loeschen = 03,00,05

diagende = 03,00,06

fs_lesen = 03,00,07

ack = 03,00,09

adr_lesen = 03,00,0B

[RESPONSE] ; Response from the ECU

empty =

id_lesen = 0D,00,F6,31,31,31,31,31,31,31,31,31,31,0D,00,F6,32;,...

ram_lesen = 04,00,FE,64

fs_loeschen = 03,00,09

diagende = ; No response received from the DME

fs_lesen = 04,00,FC,00,03,00,09 ; No error

ack = 03,00,09

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020
EDIABAS User's Guide Page 117 of 117

adr_lesen = 0F,00,FA,5E,88,FF,FF,FF,FF,FF,FF,FF,FF,E5,0E,0F,00;,...

[KEYBYTES] ; Keybytes of the ECU

keybytes= 01,02,00,00,0D,00,F6,31,31,31,31,31,31,31,31,31,31,03;,...

EDIABAS User's Guide > ECU Simulator

A. References
[1] EDIABAS: BEST/2 Function Primer

[2] EDIABAS: ECU Simulator

[3] EDIABAS: BEST/1 - Language and Interpreter

[4] EDIABAS: User Manual

[5] EDIABAS: BEST/2 - Language Description

[6] EDIABAS: API User Manual

file:///C:/Users/sgtma/AppData/Local/Temp/~hhD033.htm 7/16/2020