Home

EDIABAS Documentation

1. Figure 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 1 Sequence control kernel 2 ECU description file interpreter SGBD Interpreter 3 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 14 EDIABAS USER MANUAL 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 Hand
2. EED response 3 256 response 4 apiResultiInt variable EED set printf Speed S d variable Figure 3 8 2 Job sequence The application program can read the results delivered from 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 18 EDIABAS USER MANUAL 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 a MS WINDOWS 95 98 ME NT4 2000 XP WIN32 MS WINDOWS 3 11 95 98 ME WIN16 Pocket PC 2002 2003 WINCE a SCO OpenServer 5 a ONS 4 23 Throughout this manual MS WINDOWS is used for WIN32 and WIN16 Throughout this manual MS WINDOWS CE is used for Pocket PC 2003 and Pocket PC 2002 The development environment for ECU description files is only available under MS WINDOWS Throughout this manual SCO UNIX is used for SCO OpenServer 5 19 EDIABAS USER MANUAL 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 1 RUNTIME SYST
3. TracePath Path of the Trace files Path INI AP BEST D max trace file size in KB D 32767 INI AP BEST 1024 CodeMapping file path of the code page path INI AP BEST only with code conversion UbattHandling Supply voltage ON OFF handle as 0 OFF 1 ON INI API BEST error Note the process ID is only indicated with EDIABAS for WIN32 38 EDIABAS USER MANUAL 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 Port Port Port number 1000 30000 30000 INI INI AP BEST 2 RemoteHost Name or IP address of name addresse INI AP remote system TimeoutConnect timeout in milliseconds for 1000 59000 INI AP BEST 5000 connection setup TimeoutReceive timeout in milliseconds for 1000 59000 INI AP BEST 5000 receipt of a message TimeResponsePending Time in milliseconds Zeit in 500 59000 INI AP BEST 2000 Millisekunden between alive messages Not supported with EDIABAS V6 4 0 TimeoutFunction Timeout in milliseconds for 5000 59000 INI AP BEST 59000 a for a long IFH function for example send_and_receive The complete timeout is TimeoutFunction TimeoutReceive RemoteHost Name or IP address of the Name address INI AP BEST computer to be controlled remotely 4 5 3 Select the hardware inte
4. EDIABAS USER MANUAL 5 7 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 and debug information stored in BEST object files Call STRIP 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 Example strip N dh testv prg Remove the debug information and help texts from file testv prg 57 EDIABAS USER MANUAL A _GLOSSARY API Application Programming Interface EDIABAS interface up to the application Application Application program for executing the diagnostics and coding ECUs BEST BEschreibungssprache fur STeuergerate Description language for ECUs Description file Contains all data and methods which are required for describing the diagnostic function of an ECU Device Logical device used for connecting the interface Diagnostic concept Conventions according to ISO in which access to the diagnostic data is described in ECUs DLL Dynamic Link Library Dynamic function library under MS Windows Linked at the to
5. Communication DLL for remote diagnostics 22 EDIABAS USER MANUAL 4 1 1 4 Files for SCO UNIX The RUNTIME SYSTEM contains the following files readme install uinstall profile apiset bin apiboot bin apiclose bin apitest bin bestinfo bin devclose bin pe bin printver bin ebasd bin ediabas bin ipc ini bin ipcctrl que bin setlog bin tracer bin tracer que Installation notes Installation program Uninstall program Profile extension Script to set environment variables Start script for EDIABAS End script for EDIABAS EDIABAS test program Display BEST object file contents Script to close the interface driver Password editor PE Output of EDIABAS version EDIABAS runtime system Program controlling communication software IPC configuration file Reference file Script for controlling the installation messages EDIABAS tracer Reference file 4 1 1 5 Files for QNX The RUNTIME SYSTEM contains the following files readme install uinstall sysinit add ediabas ini bin apiboot bin apiclose bin apikill bin apisys bin apisys cfg bin apitest bin apitrace bin bestinfo bin devclose Installation notes Installation program Uninstall program Extension for system initialization file EDIABAS configuration file Start script for EDIABAS End script for EDIABAS Program to Stopp communication software Program to start communication software Configuration file of communication so
6. INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a API library MAKE file for producing libapi a Object file for producing libapi a Object file for producing libapi a the delivery diskette APPLICATION EDIABAS USER MANUAL api obj dynamic o api obj log o api obj process o api obj profile o api obj psig o api obj scolib o api obj svmsg o api obj tracesco o api obj watchdog o Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a Object file for producing libapi a 4 1 2 5 Files for QNX The following
7. PC 48 4 9 3 Procedure for remote diagnostics AAA 48 4 10 EDIABAS Parallel Operatnon eee 48 5 Help DROGMAINS EEN 50 ERT STA NEE 50 eR D GOIN RE ont oot Gt eo Glad ees ou eda ER 50 ese OIG EE 50 5 24 PE Password Eqitor E 51 e DEV CHO S Ee 52 54 BE STING O EE 52 5 57 eene 54 eB E 55 eR STRIP EEN 57 EDIABAS USER MANUAL 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 Version 5a Version 5b Version 5c Version 5d Version 5e Version 6 Version 6c Revised for EDIABAS V5 1 0 Extended for EDIABAS V5 5 0 Extended for remote diagnostic Win32 Configuration for IFH Trace Revised the XTRACT output functionality Extended for QNX Extended for EDIABAS V6 0 0 Revised for EDIABAS V6 4 4 EDIABAS USER MANUAL 2 Introduction 2 1 About this manual This manual describes how to operate the EDIABAS Electronic Diagnostic Basic System 2 2 Notational conventions The following typographical conventions are used throughout this manual Example SAMPLE C apiJob APIREADY expression option result argument constant job hal whil E 1 e lo Test Description Uppercase denotes file names registers and operating system commands Bold faced type identifies keywords and operators
8. 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 lt port number lt 30000 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 46 EDIABAS USER MANUAL TCP RemoteHost lt Name addresses of remote controlled PC gt Port lt Port from remote controlled IFH gt TimeoutConnect lt Timeout for connection setup gt TimeoutReceive lt Timeout for Receive gt TimeoutFunction lt Timeout for IFH gt 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 47 EDIABAS USER MANUAL 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 lt Interface gt NetworkPr
9. apiclose 4 6 5 QNX If EDIABAS was selected to automatically start during the installation the system must be re started Otherwise EDIABAS must be manually started with Super User access rights usr ediabas bin apiboot The EDIABAS configuraiton file ediabas ini is read only once the first time the application is accessed Applications access EDIABAS via the library libapi a linked to the application program Normally EDIABAS must not be terminated If however this is necessary the instruciton below can be used usr ediabas bin apiclose 4 7 Un install When un installed all EDIABAS delivery packages are removed from the system Subdirectory ECU or ecu under SCO UNIX containing the ECU description files is only deleted when this is requested by the user The subdirectory ECU and the residing ECU description files are generally not deleted 4 7 1 MS WINDOWS The Uninstall manual is not part of this documentation 43 EDIABAS USER MANUAL 4 7 2 MS Windows CE The Uninstall manual is not part of this documentation 4 7 3 SCO UNIX EDIABAS software can be un installed using the program UINSTALL All programs which access EDIABAS must be terminated prior to un installing software EDIABAS software is to be removed in the following way 1 Log in as Root or Super User login root 2 Stop any active EDIABAS software and delete the EDIABAS software using uinstall usr ediabas uinstall The un install pr
10. compiler BEST 2 runtime library BEST 2 debugger BestView Help file for BEST 2 debugger BEST development environment BestBoard EDIABAS test application EDIABAS test application EDIABAS test application ECU description file for transparent mode source code Example group description file BEST 1 Example variant description file BEST 2 BEST tutorial files 4 1 3 3 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 31 EDIABAS USER MANUAL 4 2 System requirements 4 2 1 MS WINDOWS In order to use EDIABAS under MS WINDOWS the following requirements must be meet IBM PC AT or 100 compatible system with at least an 80386 processor For EDIABAS RUNTIME SYSTEM WIN32 for MS WINDOWS 95 98 ME a network installation is required For the remote function of the EDIABAS RUNTIME SYSTEM for WIN32 a network installation with TCP IP is required 4 2 2 MS WINDOWS CE In order to use EDIABAS under MS WINDOWS CE the system requirements has to be meet A Pocket PC 2002 2003 compatible system is required For EDIABAS RUNTIME SYSTEM for WINCE a network installation of TCP IP is required 4 2 3 SCO UNIX In order to user EDIABAS u
11. deleted 5 1 1 SCO UNIX This program can only be called by the Superuser UINSTALL deletes all programs in the EDIABAS directory also EDIABAS external software After executing the program all API or API or EDIABAS entries should be deleted in etc profile Call usr ediabas uinstall Example login root usr ediabas uinstall 5 1 2 QNX Only the Superuser can invoke this program UINSTALL can be used to delete all programs in the EDIABAS directory also EDIABAS external software Call usr ediabas uinstall Example login root 50 EDIABAS USER MANUAL usr ediabas uinstall 5 2 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 lt Label gt consists of 1 to 10 ASCII characters in ANSI code where only ASCII characters are permitted in the range 20h lt lt ASCII character gt lt 7Eh The character 40h is i
12. files are contained on the delivery diskette APPLICATION DEVELOPMENT KIT and are copied to the target system readme install api cc api c api cc apiipc c api cc callback c api cc errors c api cc errortxt c api cc help c api cc job c api cc jobdata c api cc qnx c api cc results c api cc trace c api include api h api include apimsg h api include aspekte h api include bip h api include callback h api include config h api include ediabas h api include error h api include help h api include job h api include jobdata h api include kernel h api include msgipc h api include qnx h Installation notes Installation program Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a INCLUDE fil
13. 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 45 EDIABAS USER MANUAL 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 protected or not beginning with version 5 5 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
14. runtime 7 process ID 8 debug trace BipDebugLevel Debug level in ECU description 0 32767 INI API BEST files EcuPath Path of the ECU description files of the ECU Path of the ECU description er files Path INI API BEST pest EdiabasIniPath Path of the configuration file Path INL AP BEST EDIABAS INI used only if this exists IfhTrace Control of IFH Trace 0 OFF INI API BEST 1 User interface 2 interface 3 timestamp 37 EDIABAS USER MANUAL Hin Trace Control of IFH network trace 0 aus INI APHBESF 0 Only available with XREMOTE ET 2 Interface 3 timestamp Hardware interface INI AP BEST EDIC IgnitionHandling Ignition ON OFF handle as error 0 OFF 1 ON INI API BEST LoadWin32 Selection of EDIABAS systems 0 EDIABAS Tor INI AP BEST Windows for WIN16 applications WIN16 9x ME 0 G Windows 1 EDIABAS for NT 2000 WIN32 XP 1 NetworkProtocol Select network protocol for the TCP INI AP BEST remote diagnostics RetryComm Repetition on communication error 0 OFF 1 ON INI API BEST Simulation Control of ECU simulation 0 OFF 1 ON INI API BEST 0 SimulationPath 1 Path of the ECU simulation files INI API BEST SystemResults Control whether to store ignition 0 donotstore INI API BEST 1 supply voltage and job status o system results 1 store TaskPriority Priority setting for EDIABAS 0 0 10 INI API BEST optimal setting 1 lowest priority
15. toolsBEST 2 Compiler BEST 2 Debugger and BEST development environment The following files are contained on the delivery diskette BEST DEVELOPMENT KIT 29 EDIABAS USER MANUAL 4 1 3 1 Files for WIN32 The delivery package BEST DEVELOPMENT KIT contains the following files README32 BDK BIN BEST2WIN EXE BIN BEST2WIN HLP BIN B2RUNTIM LIB BIN BESTVW32 EXE BIN BESTVW32 HLP BIN BESTBD32 EXE BIN RUN1632 EXE BIN RUN16 EXE BIN APITST32 EXE BIN APITAL32 EXE BIN JOBLOO32 EXE ECU TMODE B1V ECU TESTG B1G ECU TESTV B2V TUTORIAL Installation notes BEST 2 compiler Help file for BEST 2 compiler BEST 2 runtime library BEST 2 debugger BestView Help file for BEST 2 debugger BEST development environment BestBoard Help program for BestBoard Help program for BestBoard EDIABAS test application EDIABAS test application EDIABAS test application ECU description file for transparent mode source code Example group description file BEST 1 Example variant description file BEST 2 BEST tutorial files 30 EDIABAS USER MANUAL 4 1 3 2 Files for WIN16 The delivery package BEST DEVELOPMENT KIT contains the following files README BDK BIN BEST2WIN EXE BIN BEST2WIN HLP BIN B2RUNTIM LIB BIN BESTVIEW EXE BIN BESTVIEW HLP BIN BESTBRD EXE BIN APITESTW EXE BIN APITALKW EXE BIN JOBLOOPW EXE ECU TMODE B1V ECU TESTG B1G ECU TESTV B2V TUTORIAL Installation notes BEST 2 compiler Help file for BEST 2
16. 3 1 Files for WNI2 EE ESA 30 4 1 3 2 Files for WINTIG sse 31 4 1 3 3 DOCUMENTATION sese ee eee eee 31 4 2 EE HELENE 32 BD DE AE TC 16161 S oisinendenanen peia ER 4 2 2 MS WINDOWS CE EE 32 ADB e ET ER 42 4 e KE ER 4 3 Installing fOr the first me cevecesecesccenecenecesecesceevereneresecesceeserencee 33 4 3 1 MS WINDOWS E 33 SE et IN od foo Jd hn fons fant Dd ee 33 433 ANK EE 34 4 4 EDIABAS program patha sse 35 4 4 1 MS WINDOWS n 35 AAD SCO TOI a et eee edhe es one one eee 35 44 3 QNX cso ee ie le aed 35 4 5 EDIABAS COMMOUAUON EEN 36 4 5 1 Search sequence of EDIARBAG IN 36 4 5 2 Configuration Overview sese eee eee eee eee 37 4 5 3 Select the hardware interface sss eee eee eee eee eee 39 4 5 4 MS WINDOWS eege 39 e EICH 40 E e EE 40 4 5 7 Directory of ECU description files AAA 40 4 5 8 Character Set Conmversion 40 EDIABAS USER MANUAL 4 5 9 WINTIGI32 Umsetzung 41 4 6 Start and terminate EDIARBAG eee 41 4 613 WINI sce ee 42 719 py ame TO oe ne UR RA BRON BANC RAS BRCUR AN BRHTRAW BRAUN BAHT RANT ERATE AH BRNER GAR 42 40 3 WING ESen cect ci eet oh cet eh hc eh Neh heh Vee hel oh it 42 E ee E 42 4 6 5 9 eege 43 e EE ET Ten UE 43 4 7 1 MS WINDOWS ce eee 43 41 2 MSWindows CE EE 44 4 e ee E EE A4 o Me KEE A4 4 8 Protection mechanism AAA 45 4 9 Remote diagnostics iniiaiee aeiia 46 4 9 1 EDIABAS INI on the local PC 46 4 9 2 EDIABAS INI on the remote controlled
17. EDIABAS USER MANUAL 4 1 2 1 Files for WIN32 The APPLICATION DEVELOPMENT KIT contains the following files README32 ADK Installation notes API WIN32API H General C C header files for all libraries API WIN32 APICALLS C C C source code of APIW32 LIB and APIW32MT LIB API WIN32 APIDLL H C C header file for API32 DLL Windows DLL Interface API WIN32 VC60 APIW32 LIB API Library for single Thread API WIN32 VC60 APIW32MT LIB API Library for multi Thread API WIN32 VB60 API BAS Basic Modul for Visual Basic 6 0 API WIN32 VB40 API BAS Basic Modul for Visual Basic 4 0 BIN APITST32 EXE EDIABAS test application ECU TESTG PRG Example for group description file ECU TESTV PRG Example for variant description file 4 1 2 2 Files for WIN16 The APPLICATION DEVELOPMENT KIT contains the following files README ADK Installation notes API WIN16 API H General C C header files for all libraries API WIN16 APICALLS C C C source code of APIW LIB API WIN16 APIDLL H C C header file for AP DLL WINDOWS DLL Interface API WIN16 VC15 APIW LIB API Library for Microsoft Visual C 1 52 Large Model API WIN16 VB30 API BAS Basic Modul for Visual Basic 3 0 API WIN16 VB40 API BAS Basic Modul for Visual Basic 4 0 BIN APITESTW EXE EDIABAS test application ECU TESTG PRG Example for group description file ECU TESTV PRG Example for variant description file 4 1 2 3 Dateien unter WINCE The APPLICATION DEVELOPMENT KIT contains the following fi
18. EDIABAS USER MANUAL USER DOC EDIABAS Electronic Diagnostic Basic System USER MANUAL INSTALLATION GUIDE VERSION 6c Copyright BMW AG created by Softing AG EDIABAS USER MANUAL Contents CONnteNtS Ee ee 2 1 Revision history ssssssssssssssseeeeeeeeeeeeeeeeeeeeeee e 5 2 Introduction EE 6 E EENHEETEN 6 2 2 Notational conventions EE 6 2 3 Special features terms acCropnvnms nnn 7 2 4 Trademarks eege 7 3 GOTTA DEE 8 3 1 Diagnostics and Coding of e E 8 3 2 Problem Re Tu tte EE 8 3 3 Approaches to problem sching 10 3 4 Implementing solutions with EDIABAS sse 12 DD ele EE 12 3 6 Tei R eicae EEN 15 3 7 Description language BEST E 15 3 8 SEQUENCE Si EE EE E 16 SE Ee 19 4 Installation and administration ccccceeeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaes 20 4t Te Le 20 4 1 1 Delivery package RUNTIME GvGTEM 20 4 1 1 1 Files for CG 20 4 1 1 2 Files for WIND sss eee eee 22 Dua GEM Files for WINCE 208 cacao een RRR aR 22 4 1 1 4 Files for SCO UNIX sf cscccececenscececedscececeussececevegeresenccts 23 4 14 15 Files for GC KEE 23 4 1 1 6 Documentation sese eee eee 24 4 1 2 Delivery package APPLICATION DEVELOPMENT KIT 24 4 1 2 1 Files for EE 25 EDIABAS USER MANUAL 4 1 2 2 Files for WINTI6G ee 25 4 1 2 3 Dateien unter WINCE sese 25 4 1 2 4 Files for SCO UNIX EE 27 4 1 2 5 EEN 28 4 1 2 6 Documentation AAA 29 4 1 3 Delivery package BEST DEVELOPMENT KIT 29 4 1
19. EM 2 APPLICATION DEVELOPMENT KIT 3 BEST DEVELOPMENT KIT 4 1 1 Delivery package 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 4 1 1 1 Files for WIN32 The RUNTIME SYSTEM contains the following files README32 Installation notes BIN lt PaRwortdatei gt Name of password file 8 characters The file has no extension Example 07DE3473 BIN PE EXE Password Editor PE BIN ANSIZOEM TAB Codemapping table BIN EDIABAS INI Example EDIABAS configuration file example BIN EBAS32 DLL EDIABAS runtime system BIN EBAS32 EXE EDIABAS visualization BIN API32 DLL Access to the EDIABAS runtime system BIN APIVB32 DLL Access to the EDIABAS runtime system for Visual Basic BIN TRACEX32 EXE Trace server BIN BESTINFO EXE Dispaly of BEST object file contents BIN BESTVER EXE Version test of BEST object files BIN XTRACT EXE Display of the help texts of BEST object files 20 EDIABAS USER MANUAL BIN STRIP EXE BIN IFHSRV32 EXE BIN NMSIFH32 DLL BIN VMC32 DLL BIN XEDIC32 DLL BIN XREMOT32 DLL BIN NETTCP32 DLL BIN NETPRO32 DLL ECU TMODE PRG Remove the debug and help texts in BEST object files IFH server for remote diagnostics IFH service for remote diagnostics Access to connec
20. EX32 EXE EBAS32 DLL loads the interface handler Access of applications to EDIABAS takes place via API32 DLL 4 6 2 WIN16 The first time an application accesses EDIABAS EDIABASW EXE is automatically started EDIABASW EXE subsequently loads the configured Interface Handler EDIABASW EXE is accessed by applications via API DLL 4 6 3 WINCE When an application with access to EDIABAS is started the EDIABAS components APICE DLL EBASCE DLL and TRCSRVCE EXE are automatically loaded During the first access to EDIABAS EBASCE DLL loads the configured Interface Handler Access of applications to EDIABAS takes place via APICE DLL 4 6 4 SCO UNIX After installing EDIABAS see Installing from diskette for the first time shut down and re boot the system After installation EDIABAS will automatically be booted and shut down by the system The EDIABAS configuration file ediabas ini is only read once the first time an application program is accessed EDIABAS is accessed by applications via the library libapi a which is bounded to the application program Normally EDIABAS is started up or shut down automatically during the corresponding system processes In addition EDIABAS can be manually started up or shut down with Super User authorization Manual EDIABAS startup if EDIABAS does not run yet 42 EDIABAS USER MANUAL usr ediabas bin apiboot Manual EDIABAS shutdown if EDIABAS is already running usr ediabas bin
21. abas ecu 33 EDIABAS USER MANUAL TracePath usr ediabas SimulationPath usr ediabas ecu ApiTrace 0 lfhTrace 0 Simulation 0 3 Copy and install the new APPLICATION DEVELOPMENT KITs Calling install Substitute drive for mount dev fd 135ds18 mnt mnt install mnt umount dev fd 135ds18 4 3 3 QNX 1 Log in as either Root or Super User login root 2 Copy and install the EDIABAS RUNTIME SYSTEM After inserting the diskette EDIABAS RUNTIME SYSTEM invoke install substitute the drive for mount dev fd mnt mnt install mnt umount mnt You will be prompted during the installation whether EDIABAS is to automatically be started each time the system is booted If EDIABAS is to beautomatically started install Accordingly adapts the system initialization file sysinit lt node EDIABAS requires the message queue server Mqueue from QNX This must first be run BEFORE starting EDIABAS Example for starting Mqueue in sysinit lt node gt bin mqueue amp Configure EDIABAS via the configuration file etc ediabas ini see EDIABAS configuration Example 34 EDIABAS USER MANUAL Configuration EcuPath usr ediabas ecu TracePath usr ediabas SimulationPath usr ediabas ecu ApiTrace 0 IfhTrace 0 Simulation 0 3 Copy and install the APPLICATION DEVELOPMENT KIT After inserting the diskette EDIABAS APPLICATION DEVELOPMENT KIT invoke install Substitut
22. aded in the program memory when EDIABAS is started and causes all EDIABAS result strings to be automatically converted to the desired character format 40 EDIABAS USER MANUAL The code page ANSIZOEM TAB which is part of the delivery converts the ANSI Windows character set into the OEM DOS character set For the conversion each character of an EDIABAS result string is replaced by the corresponding character from the code page For conversion the character to be replaced is used as an index which points to the new character on the code page Example ANSI Character Set Windows OEM Character Set DOS G 0x47 G 0x47 E 0x45 E 0x45 R 0x52 R 0x52 A 0xC4 A 0x8E T 0x54 T 0x54 For converting for example the character A from the ANSI character set Windows to the OEM character set DOS the code 0xC4 must be replaced by Ox8E For characters which have no counterpart in the other code is indicated 4 5 9 WIN16 32 Umsetzung For the operating systems Windows 9x ME NT4 2000 XP an automatic conversionof EDIABAS WIN16 calls to EDIABAS WIN32 is possible D LoadWin32 0 Using EDIABAS WIN16 m LoadWin32 1 Using EDIABAS WIN32 with conversion of all API calls 4 6 Start and terminate EDIABAS 41 EDIABAS USER MANUAL 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 and TRAC
23. ancement and testing of programs are repeated more than once The apparent differences in the job definitions and objectives of the EDIABAS USER MANUAL individual phases discourage the view for mutuality namely each the same component ECU 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 Development Production Customer Service Lab test End of line Service tester Test vehicle Diagnostics Error analysis Coding Common communication basis Fig 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 10 EDIABAS USER MANUAL This operating system lt 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 th
24. e 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 Client Speed 2000 UPM Job Job Server ECU 010110101 Fig 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 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 11 EDIABAS USER MANUAL 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 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 cr
25. e for producing libapi a INCLUDE file for producing libapi a INCLUDE file for producing libapi a 28 EDIABAS USER MANUAL api include results h INCLUDE file for producing libapi a api include sigserv h INCLUDE file for producing libapi a api include trace h INCLUDE file for producing libapi a api include traceapi h INCLUDE file for producing libapi a api include typedef h INCLUDE file for producing libapi a api include unixdef h INCLUDE file for producing libapi a api include version h INCLUDE file for producing libapi a api lib libapi a API library api make makefile Make file for producing libapi a api obj aspekte o Object file for producing libapi a api ecu testg prg Test group description file api ecu testv prg Test variant description file 4 1 2 6 Documentation The following documentation refers to the delivery package APPLICATION DEVELOPMENT KIT API USER MANUAL Description of how the API libraries are used Sample programs Operation of the APITEST program API INTERFACE Description of the API interface and how to operate it API FUNCTION REFERNCE Description of the API functions TRANSPARENT MODE Description of the interface for transparent mode INTERFACE DESCRIPTION Transparent mode 4 1 3 Delivery package 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
26. e the drive for mount dev fd mnt mnt install mnt umount mnt 4 4 EDIABAS program paths 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 SPATHS PATH c ediabas bin sOLDPATH 4 4 2 SCO UNIX The EDIABAS subdirectory bin is automatically entered in the search path 4 4 3 QNX The search path is left unchanged during installation The complete path must be specified when calling EDIABAS programs 35 EDIABAS USER MANUAL 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
27. eated the term Basic System has been used by Softing This Basic System in Electronic Diagnostics is called EDIABAS Electronic DlAgnostic BASic System 3 5 Structure EDIABAS has a fixed structure independent of the operating system employed 12 EDIABAS USER MANUAL Applicaiton program EDIABAS API EDIABAS runtime system m ECU description files Sequence control ECU description file interpreter SGBD Interpreter Interface Handler IFH Figure 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 13 EDIABAS USER MANUAL 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 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
28. ecuted 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 lt SGBD gt The Password Editor returns the value 1 in the case of an error otherwise 0 NOTE Only the Password Editor included in the EDIABAS installation can be used 5 3 DEVCLOSE Close the interface driver This program is only available under SCO UNIX and QNX If after using EDIABAS an EDIABAS external software wants to access the interface driver and this is still in the open state the interface driver can be closed with the program DEVCLOSE Call devclose 5 4 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 e File name e Revision number e Last user operator output of maximum 63 characters date of the last change e List of all jobs 52 EDIABAS USER MANUAL Call bestinfo sgbd Example bestinfo testv prg Produces output example BEST object file testv prg BIP version S 03 03 00 00 Revision number 2 0 Last modification by softing sag Os 1993 5 Jobs INITIALISTERUNG IDENT CHECK BINPARA WAIT BESTINFO ready U Thu Mar 25 16 33 10 53 EDIABAS USER MANUAL 5 5 BESTVER Version test of ECU description files This program is onl
29. ftware EDIABAS test program Trace of communication software Display BEST object file contents Script to close the interface driver 23 EDIABAS USER MANUAL bin ediabas EDIABAS runtime system bin pe Password editor PE bin pinstall Installation program bin setlog Script for controlling the installation messages bin sigserv Signal server ecu tmode prg ECU description file for transparent mode 4 1 1 6 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 on EDIABAS error messages ECU SIMULATOR Description of the ECU Simulator 4 1 2 Delivery package 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 6 0 WIN32 Microsoft Visual C C 1 52 WIN16 Microsoft Visual Basic 6 0 WIN32 Microsoft Visual Basic 4 0 WIN32 and WIN32 a Microsoft Visual Basic 3 0 WIN16 The following development systems are available for MS WINDOWS CE a Microsoft eMbedded Visual C 4 2 SP2 Pocket PC 2003 SDK WINCE a Microsoft eMbedded Visual C 3 0 Pocket PC 2002 SDK WINCE 24
30. g Os ECUCOMMENT Description file WIHTOUT access to the interface ECUCOMMENT Orignal TESTV B1V JOBNAME initialization JOBCOMMENT Initialization RESULT DONE RESULTTYPE int RESULTCOMMENT 1 if ok otherwise 0 JOBNAME IDENT JOBCOMMENT Determine the identification string ESULT JOB_ STATUS SULTTYPE string ESULTCOMMENT Returns OKAY or ERROR PARAMETER Ag o RESULTCOMMENT Returns OKAY or ERROR PARAMETER 55 EDIABAS USER MANUAL 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 lt Table name gt lt Column gt lt Column gt Example of a BEST 2 source file table beispielTabelle 2 COLUMN1 COLUMN2 COLUMN3 Linel xtract generated Line2 these texts Line3 automatically WR aA D L job name beispielJob comment Start of comment comment Table beispielTabelle SPALTE2 comment End of comment XTRACT outputs the following lines in the example above JOBNAME beispielJob JOBCOMMEINT Start of comment JOBCOMMEINT xtract generated JOBCOMMEINT these Text JOBCOMMENT automatically JOBCOMMEINT End of comment SPALTE3 56
31. h 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 EDIABAS USER MANUAL 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 error 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 Communication with ECUs Development Production Customer Service Lab test End of line Service tester Test vehicle Diagnostics Error analysis Communicaiton Communication Communicaiton Data conditioning Data conditioning Data conditioning Fig 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 adv
32. he 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 16 EDIABAS USER MANUAL 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 Request to DME Request to DME V3 READ_SPEED READ_SPEED I Determine the variant in the group ECU description file DME IDENTIFICATION DME V3 READ_SPEED Figure 3 8 1 ECU description file and job selection 17 EDIABAS USER MANUAL 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 Application EDIABAS int data apiJdob DM REA job name READ SPEED result SPEED type integer sy char response send and receive respons tel readspeed U gt 59 04 02 03 lt 59 05 03 05 05
33. initialized Even ECU description files can modify configuration values during EDIABAS runtime NOTE These values are only valid however during the job 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 Under SCO UNIX and QNX EDIABAS first searches for file EDIABAS INI corresponding environment variable EDIABAS_ CONFIG_DIR T the environment variable was not set or file was not found in the directory search is made in the directory etc If the file was not found in the directory etc search was made in the EDIABAS program directory subdirectory BIN 36 EDIABAS USER MANUAL 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 ApiTrace Control of the API Trace 0 OFF INI API BEST 1 user trace 2 time stamp 3 process ID 4 API trace 5 time stamp 6
34. ler provides simulation of ECUs Thus EDIABAS based application programs can also then be tested when the applied ECUs do not exist 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 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
35. les 25 EDIABAS USER MANUAL API WIN32API H API APICE LIB General C C header files for all libraries API Library 26 EDIABAS USER MANUAL 4 1 2 4 The following files are contained on Files for SCO UNIX DEVELOPMENT KIT and are copied to the target system readme install api cc api c api cc apiipc c api cc callback c api cc errors c api cc errortxt c api cc help c api cc job c api cc jobdata c api cc results c api cc sco c api cc trace c api include api h api include apimsg h api include aspekte h api include bip h api include callback h api include config h api include ediabas h api include error h api include help h api include job h api include jobdata h api include kernel h api include msgipc h api include results h api include sco h api include sigserv h api include trace h api include traceapi h api include typedef h api include unixdef h api include version h api lib libapi a api make makefile api obj aspwrap o api obj cfg o Installation notes Installation program Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a Source file for producing libapi a
36. llegal A lt Password gt consists of 6 to 10 ASCII characters in ANSI code where only ASCII characters are permitted in the range 20h lt lt ASCII characters gt lt 7Eh The Password Editor is controlled via the command line It offers the following functionalities e Display all commands of the Password Editor This Password Editor function represents a help function and displays all available commands Call pe e 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 e Add anew 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 lt Label gt lt Password gt e Enable an entry in the password file Disabled entries can be re enabled again Possible more than one Call pe e lt Label gt 51 EDIABAS USER MANUAL e 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 lt Label gt e 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 ex
37. nder SCO UNIX a computer system which satisfies the following requirements is required IBM PC or 100 compatible with at least a 80486 processor a SCO OpenServer 5 s 12 MB RAM a 3 5 in diskette drive 5 25 in on request 4 2 4 QNX A computer system which satisfies the following requirements is required in order to use EDIABAS under QNX IBM PC or 100 compatible with 80386 processor or higher 32 EDIABAS USER MANUAL a ONS 4 23 12MBRAM a 3 5 diskette drive 4 3 Installing for the first time 4 3 1 MS WINDOWS The installation manual for MS WINDOWS is not part of this documentation 4 3 2 SCO UNIX All shell scripts listed in this chapter require the kernel shell for execution IMPORTANT Pre installed EDIABAS software version 1 3 0 or later can automatically be removed during the installation optional Older EDIABAS versions however must manually be deleted PRIOR TO installing the new EDIABAS RUNTIME SYSTEM see also readme file The step by step procedure is subsequently listed 1 Log in as Root or Super User login root 2 Copy and install the new EDIABAS RUNTIME SYSTEMs Calling install substitute the drive for mount dev fd 135ds18 mnt mnt install mnt umount dev fd 135ds18 Configure EDIABAS using the EDIABAS configuration file ediabas ini see EDIABAS configuration Example EDIABAS sample configuration in ediabas ini Configuration Interface EDIC EcuPath usr edi
38. nufactures themselves and contractors The ECUs tested and produced by suppliers are installed in the vehicle at 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 3 2 Problem definition If a large number of ECUs whic
39. 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 Italics designate placeholders for values to be entered by the programmer e g file names Words enclosed in square brackets may be optionally specified Curvy braces and vertical strokes characterize entries from which only one must be selected except when in square brackets An ellipsis three dots which directly follows an expression indicates that several expressions of the same type can follow This syntax designates examples user entries program outputs and error messages A column or a row comprising three dots indicates that a section of an example was intentionally omitted Reference to a document in References EDIABAS USER MANUAL 2 3 Special features terms acronyms An explanation of abbreviations used in this and all other EDIABAS documentation can be found in chapter GLOSSARY 2 4 Trademarks Microsoft MS MS DOS WINDOWS WIN32 and Pocket PC are registered trademarks of the Microsoft Corporation SCO SCO UNIX and OpenServer are registered trademarks of Santa Cruz Operation Inc QNX is a registered trademark of QNX Software Systems Ltd EDIABAS USER MANUAL 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 ma
40. ogram uinstall allows EDIABAS software to be removed without removing the ECU description files optional WARNING Softing external software in the directory usr ediabas will be deleted Always assure in advance that this is stored in another directory 3 Delete all API or EDIABAS entries in etc profile 4 7 4 QNX The EDIABAS software can be un installed using the program UINSTALL Before un installing the software all programs which access EDIABAS must be terminated first The EDIABAS software is to be un installed again in the following manner 1 Log in as Root or Super User login root 2 Stop any active EDIABAS software and delete EDIABAS software using uinstall usr ediabas uinstall 44 EDIABAS USER MANUAL IMPORTANT First assure that no Softing external software resides in the directory usr ediabas since this will also be deleted 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 conten
41. otocol TCP TCP Port lt Port of the remote controlled IFH gt Example of EDIABAS INI for the remote controlled PC Configuration Interface EDIC NetworkProtocol TCP TCP Port 5000 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 4 10 EDIABAS Parallel Operation EDIABAS for WIN32 CE and SCO UNIX enable different application programs to access EDIABAS at the same time In contrast to the other EDIABAS platforms WIN32 CE and SCO UNIX has no single one EDIABAS which runs all application programs consecutively Instead a separate EDIABAS runs for each application program and if nec is started and under WIN32 CE finished automatically 48 EDIABAS USER MANUAL Parallel operation of several interfaces of the same type is only possible if this is supported by the corresponding interface software Under SCO UNIX up to 64 application programs may access on EDIABAS at the same time 49 EDIABAS USER MANUAL 5 Hel rograms 5 1 UINSTALL Remove the EDIABAS software This program is only available under SCO UNIX and QNX UINSTALL deletes all installed EDIABAS delivery packages The subdirectory ECU or ecu under SCO UNIX and QNX containing the ECU description files is not
42. rface 4 5 4 MS WINDOWS The hardware interface has to be set in the configuration file EDIABAS INI Interface 39 EDIABAS USER MANUAL The following hardware interfaces are currently supported a SOFTING EDIC The corresponding interface driver is NOT a constituent of the delivery package RUNTIME SYSTEM 4 5 5 SCO UNIX In the SCO UNIX version the hardware interface driver cannot be set The corresponding setting Interface in EDIABAS INI is ignored It is not part of the RUNTIME SYSTEM 4 5 6 QNX In the QNX version the hardware interface driver cannot be set The corresponding setting Interface in EDIABAS INI is ignored It is not part of the RUNTIME SYSTEM 4 5 7 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 4 5 8 Character Set Conversion The representation of characters not defined in the 7 bit ASCII character set such as 0 or a depends on the code table used by the operating system If SGBDs are developed on a computer different from the target computer and the computers do not use the same code table the representation of the EDIABAS result string may differ in the two computers This problem can be avoided with the EDIABAS configuration CodeMapping A code page to be defined with this configuration file with 256 characters is lo
43. scription files By means of BestView the sequence of a job can be exactly tracked variable contents can be monitored displayed and modified 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 t
44. the application only at runtime ECM Electronic Control Module Abbreviation for ECU ECU Electronic Control Unit Abbreviation EDIABAS Elektronik DIAgnose BASissystem Electronic Diagnostic Basic System API runtime system and Interface Handler EDIC Enhanced Diagnostic Interface Computer IFH InterFace Handler Software interface for operating the EDIC functions Communication with the EDIC interface occurs via the EDIC driver 58 EDIABAS USER MANUAL Job Method in the ECU description file which reads data from the ECU Runtime system EDIABAS runtime system with BEST interpreter The runtime system processes a job issued via API by loading and interpreting the corresponding ECU description file In addition to the ECU specific parameters these ECU description files contain the corresponding rules methods and sequences for processing jobs SGBD SteuerGerateBeschreibungsDatei ECU Electronic Control Unit description file SG SteuerGerate See ECU Electronic Control Unit Control device variant Functionally different versions of ECU groups No difference is made in version type e g country version coding variant The ECU is also to be conceived as an ECU variant for only one version within an ECU group 59
45. the job INITIALISIERUNG initializes the ECU description file the optional job ENDE de initializes the ECU description file and the job IDENTIFIK CATION in a group description file determines the currently installed ECU variant 3 7 Description language BEST Jobs are formulated in an own description language for ECUs called BEST BEschreibungssprache fur STeuergerate 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 15 EDIABAS USER MANUAL 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 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 de
46. ting management for remote diagnostics EDIC IFH IFH for remote diagnostics Communication DLL for remote diagnostics Communication DLL for remote diagnostics ECU description file for transparent mode 21 EDIABAS USER MANUAL 4 1 1 2 Files for WIN16 The RUNTIME SYSTEM contains the following files README BIN PE EXE BIN ANSIZOEM TAB BIN EDIABAS INI BIN EDIABASW EXE BIN API DLL BIN APIVB DLL BIN BESTINFO EXE BIN BESTVER EXE BIN XTRACT EXE BIN STRIP EXE BIN XEDIC DLL ECU TMODE PRG 4 1 1 3 Installation notes Password Editor PE Codemapping table EDIABAS configuration file EDIABAS runtime system Access to the EDIABAS runtime system Access to the EDIABAS runtime system for Visual Basic Dispaly of BEST object file contents Version test of BEST object files Display of the help texts of BEST object files Remove the debug and help texts in BEST object files EDIC IFH ECU description file for transparent mode Files for WINCE The RUNTIME SYSTEM contains the following files BIN lt passwordfile gt BIN EBASCE DLL BIN APICE DLL BIN TRCSRVCE EXE BIN VWMCCE DLL BIN XREMOTCE DLL BIN NETTCPCE DLL BIN NETPROCE DLL Name of password file 8 characters The file has no extension Example 07DE3473 EDIABAS runtime system Access to the EDIABAS runtime system Trace server Access to connecting management for remote diagnostics IFH for remote diagnostics Communication DLL for remote diagnostics
47. ts 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 BEST2WIN see BEST User Manual sections 5 1 and 5 2 NOTE Only the programs PE and 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
48. y 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 R RevMAJ RevMIN username LV Packageversion sgbd en 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 Revision number Last change By Package version Revision number Last change By Package version 03 03 00 00 2 0 Thu Mar 25 16 33 10 1993 softing sag Os 00000000 1 6 Wed Nov 24 12 41 50 1993 Softing 00000020 Output of the last user is limited to a maximum of 63 characters 54 EDIABAS USER MANUAL 5 6 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 F objectfile s outdir XTRACT shows an overview of options Option F pipes the output is a file with the extension biv or big The directory can be specified where the output file is to be produced Wildcards can be used in objecttile Example Xtract F testv prg Produced file testv biv containing the following ECU TESTV ORIGIN softing sag Os REVISION 2 0 AUTHOR softing sa

EDIABAS Documentation

Contents

Download Pdf Manuals

Related Search

Related Contents