Bmw INPA Ediabas, NCS Expert tool, WinKFP

[Admin]

• INPA. Interpreter for test procedures. User documentation. 74 pages. Language - English.

This document is designed to help users to understand the interpreter for test procedures (INPA); readers of this user documentation are given an overview of the possible applications and the components of the INPA that are visible for the user in section 3.
Section 5 describes the structure of the test procedure description files, the principle procedure used for tests and the language elements (for example including the functions of the standard library) used to describe (and to execute) tests. This will enable readers to formulate and run tests in a test procedure description language. The listing of the language element in sub-section 5.3 is also intended to act as a reference.
Section 6 provides a rough overview of the software structure and the components of the INPA procedure system. This section is intended to explain the outline relationships between the modules in terms of software update action.
This INPA user documentation is aimed at the following:
· Staff in departments at BMW, who define or change test procedures in the production departments
· Staff in departments at BMW, who define laboratory tests
· Developers of application programs who include test proce3dures in the electronic diagnostic system (ELD) on the production line
· Software developers, who are responsible for INPA system support

Contents:

1 INTRODUCTION .................................................. .................................................. ............................. 2
1.1 Table of contents.......................................... .................................................. ....................... 3

2 OVERVIEW.......................................... .................................................. .............................................. 5
2.1 Release status............................................ .................................................. .......................... 6

3 SYSTEM DESCRIPTION....................................... .................................................. ............................ 8

4 INSTALLATION AND CONFIGURATION..................................... .................................................. ... 11
4.1 Installation...................................... .................................................. ................................... 11
4.1.1 Requirements for operating the interpreter .................................................. ............ 11
4.1.2 Files after installation...................................... .................................................. ........ 11
4.1.3 To set up the interpreter .................................................. ......................................... 12
4.2 Configuration .................................................. .................................................. ................... 13
4.2.1 General program configuration..................................... ............................................ 13
4.2.2 Structured script selection .................................................. ...................................... 15
4.2.3 Error mask-out files .................................................. ................................................ 17
4.2.3.1 General........................................... .................................................. ........... 17
4.2.3.2 Format and content .................................................. ................................... 17
4.2.3.3 Processing in INPA .................................................. ................................... 20
4.2.3.4 Example .................................................. .................................................. .. 21
4.2.3.5 Example AAB.FAB........................................... ........................................ 23
4.2.4 Command line options........................................... .................................................. . 25

5 TEST PROCEDURE DESCRIPTION FILES............................................. ......................................... 26
5.1 File structure .................................................. .................................................. .................... 26
5.1.1 Pragmas .................................................. .................................................. ............... 26
5.1.2 Includes .................................................. .................................................. ................ 27
5.1.3 Imported functions......................................... .................................................. ......... 27
5.1.4 External function declarations .................................................. ................................ 28
5.1.5 Global data definitions .................................................. ............................................ 28
5.1.6 test procedure description .................................................. ...................................... 28
5.2 Procedure principle for tests............................................. ................................................. 29
5.3 Language elements .................................................. .................................................. ......... 30
5.3.1 User-defined functions .................................................. ........................................... 31
5.3.2 Imported functions......................................... .................................................. ......... 31
5.3.3 Screen display........................................... .................................................. ............. 34
5.3.4 Menu control........................................... .................................................. ................ 36
5.3.5 State machines.......................................... .................................................. ............. 36
5.3.6 Logic tables .................................................. .................................................. .......... 38
5.3.7 Control structures .................................................. .................................................. . 39
5.3.8 Functions of the standard library .................................................. ............................ 41

6 SOFTWARE STRUCTURE .................................................. .................................................. ............ 56
6.1 Parser............................................ .................................................. ..................................... 57
6.2 Data administration .................................................. .................................................. ......... 58
6.3 Object administration.................................... .................................................. .................... 58
6.4 Interpreter....................................... .................................................. ................................... 58
6.5 Library functions and external DLL’s .................................................. .............................. 59
6.6 INPA localisation support-DLL’s............................................. ........................................... 59
6.7 Development tools used .................................................. .................................................. . 59

7 APPENDIX A LANGUAGE DEFINITION .................................................. ......................................... 60

8 APPENDIX B EXAMPLE OF A TEST PROCEDURE DESCRIPTION .............................................. 67

[Admin]

• Guide how to start winkfp for programming. GET STARTED WITH WinKFP 5.1
  In this guide you will find info how to update WinKFP with files from progman or ISTA

[Admin]

• Frequently Asked Questions zum Thema EDIABAS, INPA und Tool Set. 28 pages. Language - German.

Contents:

1 Fehlermeldungen EDIABAS........................................... ................................................. 4
1.1 Driver Error............................................. .................................................. .................... 4
1.2 DirectNt.sys kann nicht geöffnet werden .................................................. .................... 4
1.3 IFH-0002: Interface ist nicht angeschlossen oder meldet sich nicht.............................. 4
1.4 IFH-0003: Datenuebertragung HOST/Interface gestoert .............................................. 4
1.5 IFH-0010: Datatransmission to controlunit disturbed .................................................. .. 5
1.6 IFH-0013: Command not implemented....................................... .................................. 5
1.7 Error: EBAS32.EXE not found or illegal version!.......................................... ................. 5
1.8 EDIABAS Fehler: Error (95) SYS-0005: OBJECT FILE NOT FOUND.......................... 6
1.9 Createfile_error: OPEN CONNECTION; IFH 0018- INITIALIZATION ERROR ............. 6
1.10 Batterie und Zündung wird nicht erkannt .................................................. .................... 6

2 Fehlermeldungen INPA.............................................. .................................................. ... 8
2.1 API.DLL oder API32.DLL kann nicht gefunden werden. ............................................... 8
2.2 Fehlermeldung-0020: Falscher oder fehlender Treiber. Das Programm wird
abgebrochen! .................................................. .................................................. ......... 10
2.3 SYS-00002: SG-Variantenbeschreibungsdatei nicht gefunden................................... 11
2.4 INPA Fehler: Fehler beim Übersetzen 􀃆 Abbruch!.......................................... ........... 11
2.5 INPA Fehler: Opening Inpa – Übersetzungsfehler returned a_0x2 ............................. 12
2.6 INPA Fehler: Es erscheint nur ein weißer Bildschirm beim Ausführen von
INPALOAD.EXE .................................................. .................................................. ..... 13
2.7 INPA Fehler: DTM wird nicht mehr unterstützt....................................... ..................... 13
2.8 INPA Fehler: Bridge16.exe kann nicht initialisiert werden........................................... 14
2.9 Fehler beim Öffnen der Fehlerdatei 􀃆 Abbruch: .................................................. ...... 14

3 Fehlermeldungen Tool-Set .................................................. ......................................... 15
3.1 EDIABAS Fehler 100: SYS-0010: INITIALIZATION ERROR...................................... 15
3.2 EDIABAS Fehler 126 (nur bis Ediabas V6.4.x) .................................................. ......... 15
3.3 IFH-0006: Command not accepted und IFH-0018: Inizialisation Error und IFH-0038
Interface Command not implemented....................................... .................................. 15
3.4 IFH-0006: Command not accepted.......................................... ................................... 16
3.5 IFH-0009: SG nicht angeschlossen oder meldet sich nicht......................................... 17
3.6 SYS-0005: SG-Beschreibungsdateien nicht gefunden. Das Programm wird
abgebrochen! .................................................. .................................................. ......... 17
3.7 Tool-Set Fehler: Run-time error ’372’ .................................................. ....................... 17
3.8 Tool-Set Fehler: Run-time error ’5’ – Invalid Procedure Call ....................................... 18
3.9 Tool-Set Problem: Wird eine SGBD geöffnet, erscheint nur die Sanduhr und die SGBD
wird nicht geladen........................................... .................................................. .......... 18
3.10 EDIABAS Fehler 20 : IFH-0010: Datatransmission to Controlunit distubed................. 18
3.11 Das Laden einer SGBD in das Tool-Set dauert sehr lange......................................... 19

4 Allgemeine Fragen .................................................. .................................................. .... 20
4.1 Wie findet man heraus, ob die serielle Schnittstelle COM1 belegt ist? ....................... 20
4.2 Wie startet man INPA?............................................. .................................................. 21
4.3 Wie kann ich zwischen OBD- und ADS-Interface wechseln?...................................... 21
4.4 In welcher Verzeichnisstruktur wird die OBD.ini gespeichert? .................................... 21
4.5 Wie finde ich heraus, welches Interface ich bei INPA installiert habe? ....................... 22
4.6 Wie finde ich heraus, welches EDIABAS-Package installiert ist?................................ 22
Frequently Asked Questions
BMW Group zum Thema
EDIABAS, INPA und Tool-Set Seite 3 von 28
TI-430 Maresa Praxenthaler Stand 21.09.2004
4.7 Wie deinstalliert man EDIABAS bzw. INPA?............................................. .................. 22
4.8 Wie unterscheide ich, ob der EDIABAS-Server als 16-Bit- oder als 32-Bit-Applikation
läuft? .................................................. .................................................. ...................... 22
4.9 Was ist der Unterschied zwischen \EDIABAS\bin\ToolSet.exe und
\EDIABA\bin\Tool32.exe? .................................................. ......................................... 23
4.10 Was ist eine SGBD und wie steht sie im Zusammenhang mit EDIABAS? .................. 23
4.11 Wo sind die einzelnen SGBD-Namen und deren Bedeutung im Klartext aufgeführt? . 23
4.12 Was ist ein Job?.............................................. .................................................. ......... 23
4.13 Was bedeuten SGBDen mit dem Namen _xxx? .................................................. ....... 24
4.14 Wozu dient die Gruppendatei? .................................................. ................................. 24
4.15 Diagnoseindex..................................... .................................................. ..................... 24
4.16 Variantenindex.................................... .................................................. ...................... 24
4.17 Welche Bedeutung hat die Datei EDIABAS.ini?...................................... .................... 25
4.18 Wie hängt die Simulationsdatei mit der Tracedatei zusammen?................................. 26
4.19 Warum der XBD-Generator? .................................................. .................................... 27
4.20 Welche Vorraussetzungen werden für einen Remote-Zugriff über TCP/IP benötigt? . 27
4.21 Was ist das VC-Tool und wann wir es eingesetzt? .................................................. ... 27
4.22 Was ist der KVP-Editor?........................................... .................................................. 28

[Admin]

• EDIABAS - Electronic Diagnostic Basic System. ERROR REFERENCE. 73 pages. Language - English.

This manual describes the general structure of an error. All errors which can occur in EDIABAS are listed, including the respective methods of correction.

Contents:

Contents.......................................... .................................................. ..............2

1. Revision history........................................... ..........................................3

2. Introduction...................................... .................................................. ....4
2.1. About this manual............................................ ........................4
2.2. Notational conventions....................................... .....................4
2.3. Special features, terms, acronyms.......................................... 5

3. General Information....................................... ........................................6
3.1. Error symbol and error code.............................................. ......6
3.2. Message and output of an error............................................. .6
3.3. How errors affect program execution......................................7

4. List of errors............................................ ...............................................8
4.1. IFH, Interface Handler........................................... ..................9
4.2. Runtime system............................................ ...................................34
4.2.1. BIP, BEST Interpreter....................................... ....................34
4.2.2. SYS, sequence control........................................... ..............41
4.3. API, Application Programming Interface......................................... 55
4.4. Network........................................... ........................................64
4.5. Applikation....................................... ........................................72

A. References........................................ .................................................. ....73

[Admin]

• EDIABAS (Electronic Diagnostic Basic System) - BEST USER MANUAL. 73 pages. Language - English.

This manual sets out the principles for creating control unit description files and describes the use and options of the development support programs. This manual does not go into any great depth about BEST/1 language. As a general rule all control unit description files can be formulated in BEST/2 notation which is easier to read. You will find a detailed description of the BEST/1 language in [3]. General information about EDIABAS and control unit description files is given in Reference [2].

Contents:

1. Revision history 4

2. Introduction 5
2.1.About this Manual 5
2.2.Conventions 5
2.3.Special features, definitions, acronyms 6
2.4.Trademarks 6

3. General Information 7
3.1.Job concept 7
3.2.ECU description files (SGBDs) 7
3.2.1. Group description files 7
3.2.2. Variant description files 8
3.2.3. Basic description file 8
3.3.Standard jobs 11
3.3.1. Standard job INITIALISIERUNG 12
3.3.2. Standard job IDENTIFIKATION 14
3.3.3. Standard job ENDE 14
3.4.Variant identification 14
3.5.Filenames 16

4. Tutorial 17
4.1.Preconditions 17
4.2.Getting started 18
4.3.Step 1: The frame 19
4.4.Step 2: Minimum version 22
4.5.Step 3: Control unit parameters 23
4.6.Step 4: Control unit communication 25
4.7.Step 5: String and Data functions 28
4.8.Step 6: Result sets 29
4.9.Step 7: Table processing 31
4.10.Step 8: Real processing and result request 34
4.11.Step 8: Job parameter 37
4.12.Binary parameters and binary results 38

5. BEST Tools 40
5.1.BEST2WIN 41
5.2.BestBoard 43
5.2.1. General Information 43
5.2.2. Menu overview 44
5.2.3. Toolbar 46
5.2.4. Application programs 46
5.2.5. Developing a description file with BestBoard 47
5.3.BestView 49
5.5.2. User Interface 50
5.5.3. Selecting a Description File 53
5.5.4. Updating a Description File 55
5.5.5. Selecting a Job 56
5.5.6. Setting Breakpoints 59
5.5.7. Display and Alteration of Variables 60
5.5.8. Execution of a Job 61
5.5.9. Menus 62

A. Limits and restrictions 71

B. REFERENCES 73

[Admin]

• EDIABAS (Electronic Diagnostic Basic System). BEST/2 LANGUAGE DESCRIPTION. 27 pages. Language - English.

BEST is the acronym for 'BEschreibungssprache für STeuergeräte' (description language for control units). In EDIABAS this description language is used to meet the requirement for an application-independent description facility. During the program runtime the system loads and interprets description files in which information about the control units such as addresses and conversions is hidden (encapsuling). BEST/2 description language therefore provides the means to convert data stored in the control units into control unit independent values such as engine speed or control unit number. Only data actually required by the application is downloaded (information hiding).
A language with a syntax based on assembler language, BEST/1, already exists for this purpose. However although BEST/1 is good for test purposes and simple programming it is difficult to read and understand.
The more readable BEST/2 language was developed based on C language to resolve these problems. C was chosen because it is in widespread use, is structured and contains only a few language elements that are easy to learn.
BEST/2 is a problem-oriented language, with special functions that are called by library functions. The only exception to this rule is the result manager which is a fundamental part of the language definition.
There are no storage definitions because the virtual processor used with BEST/2 has no memory apart from the stack that is already available in the processor.

Contents:

1. INTRODUCTION TO BEST/2................................................. ...............5

2. TEXT CONVENTIONS....................................... ....................................6
2.1. Comments 6
2.2. Names 6
2.3. Reserved words 6
2.4. Constants 6
2.4.1. Integer constants 7
2.4.2. Char constants 7
2.4.3. String constants 7
2.4.4. Lists (Data) constants 7
2.5. Sizes 7
2.6. Syntax notation 7
2.7. What does a name mean 8
2.8. Objects and L values 8

3. CONVERSIONS....................................... ..............................................9
3.1. Characters and integers 9
3.2. Unsigned integers 9
3.3. Arithmetic conversions 9

4. EXPRESSIONS....................................... ............................................10
4.1. Simple expressions 10
4.2. Unary operators 10
4.3. Multiplication and division 11
4.4. Addition and subtraction 12
4.5. Shift operations 12
4.6. Comparisons 12
4.7. Equality comparisons 13
4.8. AND gating of bits 13
4.9. Exclusive OR gating of bits 13
4.10. OR gating of bits 13
4.11. Logic AND gating 14
4.12. Logic OR gating 14
4.13. Assignments 14
4.14. Lists of expressions 15

5. DECLARATIONS...................................... ...........................................16
5.1. Type names 16
5.2. Declarators 16
5.3. Initializers 17
5.4. Predefined Macros 17

6. STATEMENTS........................................ .............................................18
6.1. Compiler instructions 18
6.1.1. #include 18
6.1.2. #define 19
6.1.3. #undef 19
6.1.4. #asm #endasm 19
6.2. Assignments and procedure calls 20
6.3. Blocks 20
6.4. "if" statements 20
6.5. "while" statement 21
6.6. "do" statement 21
6.7. "switch" statement 22
6.8. "break" statement 22
6.9. "continue" statement 22
6.10. "return" statement 23

7. GLOBAL DECLARATIONS...................................... ...............................24
7.1. Header 24
7.2. Jobs 24

8. AREAS OF APPLICATION....................................... ..........................26

9. RUNTIME LIBRARY........................................... .................................27

[Admin]

• EDIABAS (Electronic Diagnostic Basic System). BEST/2 FUNCTION PRIMER. 183 pages. Language - English.

The runtime library provides functions for control unit communication, string handling and error handling for use in BEST/2 description files. These functions provide access to the interface handler access to external data access to host system functions (e.g. time) and functions that are regularly needed for general programming tasks (e.g. strings).
This runtime library is very important because it provides facilities which the rudimentary BEST/2 language does not have.
All functions have been generated in BEST/1 to avoid performance losses!

Contents:

1. Revision history 8

2. Introduction 9
2.1. About the Runtime Library 9
2.2. Conventions 10
2.3. Special features, definitions, acronyms 11

3. Overview 12
3.1. Using the runtime library 12
3.1.1. Calling library functions 12
3.1.2. Paths and filenames 12
3.2. Functions of the runtime library by categories 13
3.2.1. Communication functions 14
3.2.2. Interface functions 15
3.2.3. Result and parameter management 16
3.2.4. String functions 17
3.2.5. Conversion functions 18
3.2.6. Real functions 19
3.2.7. Data functions 20
3.2.8. File functions 21
3.2.9. Sequence control 22
3.2.10. Error handling 23
3.2.11. Time handling 24
3.2.12. Table handling 25
3.2.13. Configuration 26
3.2.14. Control unit specific functions 27

4. Clamp states 28

4. Library functions 31
4.1. Using the function primer 31
ascii2ascii 33
ascii2hex 34
atoi 35
ator 36
atoy 37
bcd2ascii 38
bittest 39
bytetest 40
callPlugIn 41
clear_error 43
close_communication 44
datacat 46
dataclear 47
datacmp 48
datacopy 49
dataerase 50
datainsert 51
datalen 52
datarevers 53
dataset 54
doNewInit 55
enableIfhTrace 56
enableIgnitionHandling 57
enableUbattHandling 58
fclose 59
fopen 60
fread 61
freadln 62
fseek 63
fseekln 64
ftell 65
ftellln 66
get_battery_voltage 68
get_error 69
get_error2 70
get_ignition_voltage 71
get_trap_mask 74
generateRunError 75
getasciidate 76
getasciitime 77
getCfgString 79
getdate 80
getETXblock 81
gettickcount 84
gettime 85
hex2ascii 86
ifboot 87
ifgetport 88
ifinfo 89
ifloopt 91
ifrawmode 92
ifrecv 93
ifrequeststate 94
ifreset 95
ifsend 96
ifsetport 97
ifsireset 98
iftype 99
ifvers 100
incProgressPos 101
isDebugLevel 102
isSimulation 103
itoad 104
itoax 105
itor 106
make_error 108
new_set_of_results 109
open_communication 110
parcount 111
realadd 113
realdiv 115
realmul 116
realresult 117
realsub 118
recv_frequent 119
recv_keybytes 120
rtoa 121
rtoi 122
send_and_receive 123
send_frequent 124
set_answer_length 125
set_communication_pars 128
set_program_voltage 146
set_repeat_counter 147
set_trap_mask 148
set_variable_result 151
setProgressRange 152
shdataget 153
shdataset 154
stop_frequent 155
strcat 156
strcmp 157
strcpy 158
strcut 159
strerase 160
strinsert 161
strlen 162
strncpy 163
strrevers 164
tab2fix 165
tab_suche_index 166
tabget 169
tabline 170
tabseek 171
tabset 172
tabsetext 173
updateInfo 175
userbreak 176
var_result_data 177
var_result_long 178
var_result_real 179
var_result_string 180
wait 181
waitex 182

LIST OF REFERENCES 183

[Admin]

• EDIABAS (Electronic Diagnostic Basic System). API User Manual. 12 pages. Language - English.

This manual describes how application, programs can be created and maintained with access to the Electronic Diagnostic Basic System (EDIABAS). It describes the use of the tools and the various options available. A general description of the interface is contained in [3]. A detailed description of all API functions can be found in [4]. General information about EDIABAS and about the ECU (Electronic Control Unit) description files (SGBDs) is described in [2].

Contents:

1. Revision history........................................... ..........................................3

2. Introduction...................................... .................................................. ....4
2.1. About this manual............................................ ........................4
2.2. Notational conventions....................................... .....................4
2.3. Special features, terms, acronyms.......................................... 5
2.4. Trademarks........................................ .....................................5

3. General Information....................................... ........................................6
3.1. API INCLUDE file.............................................. ......................6
3.2. API Library........................................... ...................................7

4. Using the INCLUDE File and Library........................................... .........8
4.1. WIN32/16/CE Application Programs.......................................8
4.1.1. Microsoft Visual C++ 6.0............................................... ......8
4.1.2. Microsoft Visual C++ 1.52.............................................. .....8
4.1.3. Microsoft Visual Basic 6.0, 4.0, 3.0.....................................9
4.1.4. Microsoft eMbedded Visual C++ 4.0 SP2, 3.0....................9
4.1.5. DLL (Dynamic Link Library) Interface..................................10
4.2. SCO-UNIX Application Programs.......................................... ..10
4.3. QNX Application Programs.......................................... ...........10

A. REFERENCES........................................ .................................................1 2

[Admin]

• EDIABAS (Electronic Diagnostic Basic System). API FUNCTION PRIMER.

This manual describes the constants and functions that are available in the EDIABAS-API interface. Reference [5] gives a detailed description of their use. Linking into a development environment is described in Reference [6]. You will find general information about EDIABAS and control unit description files in Reference [4].

Contents:

1. Update history 4

2. Introduction 5
2.1. About this Manual 5
2.2. Conventions 5
2.3. Special features, definitions, acronyms 6

3. Data types, constants and error messages 7
3.1. Data types 7
3.2. Constants 8
3.3. Error messages 9

4. API function Primer 11
4.1. Using the function primer 11
4.2. Functions 11
apiBreak 12
apiCallBack 13
apiEnd 14
apiErrorCode 15
apiErrorHandler 16
apiErrorText 17
apiGetConfig 18
apiInit 19
apiJob 22
apiJobData 23
apiJobExt 24
apiJobInfo 25
apiResultBinary 26
apiResultByte 27
apiResultChar 28
apiResultDWord 29
apiResultFormat 30
apiResultInt 31
apiResultLong 32
apiResultName 33
apiResultNumber 34
apiResultReal 35
apiResultsDelete 36
apiResultSets 37
apiResultsNew 38
apiResultsScope 39
apiResultText 40
apiResultVar 41
apiResultWord 42
apiSetConfig 43
apiState 44
apiSwitchDevice 45
5. Other Functions 46
enableServer 46
closeServer 47

A. List of references 48

[Admin]

• EDIABAS (Electronic Diagnostic Basic System). API INTERFACE DESCRIPTION. 44 pages. Language - English.

This manual describes the use of constants and functions that are available in the EDIABAS-API interface. Reference [3] gives a detailed description of these functions. Linking into a development environment is described in Reference [4]. You will find general information about EDIABAS and control unit description files in Reference [2].

Contents:

1. UPDATE HISTORY 5

2. INTRODUCTION 6
2.1. About this manual 6
2.2. Conventions 6
2.3. Special features, definitions, acronyms 7

3. GENERAL 8
4. OPERATING THE API INTERFACE 9
4.1. Initializing and abort of EDIABAS 9
4.2. API jobs 10
4.2.1. Jobs with an unknown variant 11
4.2.2. Jobs with a defined variant 12
4.2.3. Standard jobs 12
4.2.3.1. Standard job INITIALISIERUNG 12
4.2.3.2. Standard job IDENTIFIKATION 14
4.2.3.3. Standard job ENDE 14
4.2.4. Virtual jobs 14
4.2.4.1. Virtual job _JOBS 15
4.2.4.2. Virtual job _JOBCOMMENTS 15
4.2.4.3. Virtual job _VERSIONINFO 15
4.2.4.4. Virtual job _ARGUMENTS 16
4.2.4.5. Virtual job _RESULTS 16
4.2.4.6. Virtual job _TABLES 17
4.2.4.7. Virtual job _TABLE 17
4.3. API Results 18
4.3.1. Data management 18
4.3.2. Identifying results 20
4.3.2.1. Identifying the name of the control unit variant 21
4.3.2.2. Identifying the number of result sets 22
4.3.2.3. Identifying the number of results in a result set 22
4.3.2.4. Identifying a result name using the result index 22
4.3.2.5. Identifying the format of a result 24
4.3.3. Result types and formats 24
4.3.3.1. Result types 24
4.3.3.2. Result formats 25
4.3.4. Application result fields 27
4.3.4.1. Creating an application result field 27
4.3.4.2. Creating a reference to the application result field 28
4.3.4.3. Deleting an application result field 28
4.4. Device switching 28
4.5. API Sequence control 29
4.5.1. Job control 30
4.5.1.1. Automatic job execution 30
4.5.1.2. Cyclical polling 30
4.5.1.3. Call-Back option 31
4.5.1.4. Job abort 32
4.5.2. Application Locking 32
4.5.2.1. Locking an application program to EDIABAS 32
4.5.2.2. Canceling the lock with EDIABAS 33
4.5.2.3. Access by several application programs to EDIABAS 34
4.5.3. Parallel Processing (only WIN32/CE and SCO-UNIX) 35
4.5.4. Application Locking (not WIN32/CE and SCO-UNIX) 35
4.5.4.1. Binding an Application Program to EDIABAS 36
4.5.4.2. Clearing a Binding to EDIABAS 36
4.5.4.3. Access of more than one Application Program to EDIABAS (not WIN32/CE and SCO-UNIX) 36
4.6. Configuration 37
4.6.1. Determining the configuration 37
4.6.2. Modify the configuration 38
4.7. Trouble shooting 38
4.7.1. Identifying the cause of an error 38
4.7.2. Using an Error Handler 38
4.7.3. Procedure for error analysis when initializing and identifying results 39
4.7.4. Clearing an error 39

5. APPLICATION EXAMPLE 40

A. LIST OF REFERENCES 44