Esys 22w manual

E-Sys does not conduct a consistency check in respect of the function mask. This is done only during the coding operation by the programming system and leads to coding abort.

The changes can be accepted in the tree view with icon in the bottom right-hand section of the window. The FDL must be saved do not save it under a different name!

Target users of these functionalities are primarily specialist departments performing a corroboration function and control unit developers. In Verification mode net coding data, function data lists and vehicle profiles for various vehi- cle orders can be generated automatically and saved in Trace files for further use. In addition, it is also possible to generate and save system variant tables for various vehicle orders from KIS. The GUI for coding verification is shown below: Edit FA can be used to open the loaded vehicle order list in the Vehicle Order Edi- tor if necessary for revision.

The vehicle profile can be populated and displayed for individual vehicle orders via the context menu click with the right mouse button on FA entry calcu- late FP the related vehicle order entry is marked in green. If all vehicle orders of the loaded list are to be used for verification, the root element in the FA tree FAList must be selected. If all boundary conditions are met CAF files to be verified have been selected and vehicle order entries have been marked , verification can be started with button Start Verification.

All specified CAFs with all marked vehicle orders are verified. The scope of checks conducted when verifying CAFs is dependent on the Trace settings. Note: If at least one Trace recording is activated, a Trace directory must be specified to allow verification to be started. The result of a verification run is displayed in the form of a report at the end. A CAF can be used successfully to code a control unit only if precisely one function value and, consequently, one coding value exists for each function occurring in a CAF after evaluation via a vehicle order.

All other results, such as multiple function values double hits or no func- tion value zero hits lead to abort of coding of the control unit. The more FA elements or FP elements are used for control of coding of a control unit, the greater will be the number of differing vehicle orders required to cover the combinatorial analysis. Ideally, one vehicle order should be created and used for verification for each vehicle profile element used in the CAF.

E-Sys then searches all basic variants con- tained in the SVT and performs the actions as described in Chapter 4. In principle, this type of verification is a string of individual CAF verifications. The required KIS knowledge base and the evaluation of logic must be available in the data directory for this purpose KIS shares are available after importing the corresponding I-Step container.

Select a main series in the selection box at the left, and the selection box at the right is then automatically populated with the I-Steps supported by the KIS knowledge base for the main series. After selecting the I-Step to be verified, the next step is to load an FA list, analogously to individual CAF verification, and mark the required vehicle orders see Chapter 4.

The relevant fields can be populated with the context menu Edit. When doing this, note the required length of the relevant entry. To assist you, E-Sys shows the entry fields bordered in red until the entry is complete. How- ever, E-Sys does not offer the option of calculating the checksum!

The individual entries must comprise precisely 3 alphanumeric characters. Incorrect entries or in- complete entries are shown by a red border around the entry field.

The entry can be transferred to the FA by clicking on icon. An analogous procedure is used to edit existing vehicle order lists. Entire vehicle orders can be deleted from the FA list with the context menu at FA level. This functionality is required primarily for Expert Mode TAL processing since it allows only FA lists with only one vehicle order to be processed.

After all required FA elements have been entered, the vehicle profile can be calculated via the context menu at FA level calculate FP, and the vehicle order can consequently be checked for validity.

If a valid vehicle order exists, the vehicle profile is shown in the vehicle profile tree in the right-hand section of the window. Errored entries unknown SAs, model codes or build level are displayed as an error message. Note: Vehicle orders can be edited and new vehicle orders can be created conveniently with tool FA-Generator FA Generator that is also distributed through GIS since all FA elements of a main series including description are available in this case.

It is saved in the ZGW primarily for vehicle recognition via Ethernet. The VCM data has already essentially been described in the section on vehicle data. In addi- tion, some of the functions are identical or similar to the functions of Expert Mode Coding and are described in more detail there.

The display area is located in the upper section of the VCM GUI, and the control area is located on several tabs beneath. The controls in the control area are arranged so that they correspond to the arrangement of the related data display in the display area.

There is a cross at the top right for each display for rejecting the currently loaded data and deleting the displays. The File menu, Reset menu entry, can be used to reject all data and delete the contents of all views. These control units are marked specially in the SVT. An FA from the FA list can be activated via a context menu. The same applies accordingly to the SVTactual. In this case, the assignment is made indirectly by opening the file in the corresponding field SVTtarget or SVTactual respectively.

The filter settings can be opened with the icon in the top right-hand corner of the SVT display. Note: The filter settings are not reset by clearing the display. Activating an FA automatically calculates the related FP and displays it. The text field in which the VIN is displayed cannot be edited. A related status is shown in the status bar for each of the actions executed.

The data loaded is shown in the display area. If an FA has been read from an ECU beforehand but not yet saved, a corresponding warning message is displayed. The current FP is always saved to a file with Save As…. The data read is shown in the display area.

However, it is assigned in E-Sys directly to the FA as additional information, i. However, only a valid FA-FP combination can be written in this case, i. If no CAS is available, a corresponding error message is displayed. Control unit exchange identification Detect exchanged ECUs starts a routine in the VCM that polls the serial numbers of all con- trol units and compares them with the serial number reference list.

The result of the control unit exchange identification list with diagnostic addresses of the control units that have been exchanged is displayed in the SVT display. However, this does pre-require that the SVTtar- get have been read out and displayed successfully beforehand.

This means that a control unit exchange identification can be executed only if the SVTtarget has been read beforehand from the control unit. If this routine fails, E-Sys displays an error message.

Another condition for successful execution of the control unit exchange identification is that a serial number refer- ence list has been created in the VCM. If one of these procedures fails, a corresponding error message is displayed in E-Sys. A corresponding error message with a reference to the fact that there is no SVTtarget is displayed in E-Sys. A corresponding error message with refer- ence to the fact that there is no SVTactual is displayed in E-Sys.

Backup partner data Read Data reads all backup-related data FA, I-Steps from the backup partner and displays it in the display area. As with the Code functionality, multiple selection of control units to be read out is possible here as well.

The precondition for read-out of control units, as is also the case with coding, is that the CAFs required in accordance with the SVT view be present in the file system.

After read-out, both files are saved automatically to the file system. The file name of an NCD file corresponds to the name of the CAF used for read-out of a control unit, but with file extension ncd e. The net coding data is written to the file in Motorola S-Record format, e. The file name of an FDL file corresponds to the name of the CAF used for read-out of a control unit, but with file extension fdl e.

This is done with the aid of an FDL. This is done either by read-out of the control unit see Chapter 2. If this function has been called for the first time after E-Sys is launched, you are prompted to enter your personal PIN. Notes: A vehicle order with valid VIN number must be loaded and activated in order to allow you to write a valid coding check stamp for the code FDL function.

The vehicle order itself is not used for coding in this case. A control unit is coded with this function independently of the vehicle order to the as-delivered values specified in the CAF. The CPS value corresponds to the last seven digits of the VIN of the vehicle order used to code a control unit and is written automatically to a control unit at the end of each coding operation. Alternatively, this function can also be applied to a total vehicle electrical system.

If all CPSs have been read out, the user can check whether all codable control units have been coded to match the vehicle in which they are fitted as well. An FDL is the result of a read-out operation of coding data of a control unit and always corresponds to the CAF that was used to read out the coding data but ex- tended with the values read out and their interpretation in the logical coding data layout.

FDL Editor and CAF Viewer differ only in respect of the content of the tree view FDL has additional sub-branches with coded values read out and are described together under a gen- eral heading at this point.

Both modules can be found in the module bar at the left beneath Editors and viewers. This assignment can be made by selecting a Func- tion Value from a set of possible Function Values in accordance with a coding condi- tion or by calculating the Function Value with a calculation job e. This may be an individual numeric expression or a set of numeric expressions that are actually written to a control unit e.

The expression may be vehicle profile-dependent or job-dependent o Functions: bracket element around all codable functions of a data group o Function: designation of the codable function o Comment: comment on the codable function o Storage information: information on the position of the codable function in the memory layout Start: byte number of the start of the codable function in a data group End: byte number of the end of the codable function in a data group Size: describes the ratio of memory mapping of a codable function to a memory unit 1 byte.

Test step ID: reference ID for the function checklist, electrical system. Interpreted function value: name of the function value determined on the basis of the coding value read out for a codable function value as- sumes value UNKNOWN if no correspondence is found between cod- ing values in CAF and coding values read out from the control unit.

Read coding values: the numeric coding values actually read out from the control unit Test step ID: reference ID for the function checklist, electrical system as above If necessary, the filter can be used to show the remaining infor- mation from the underlying CAF.

You can search by function names in the FDL using the search mask option for sub-text search. If you click on Edit in the context menu on the required function value, a drop-down list is displayed showing existing function values.

After you select a function value, the corresponding coding value for the se- lected function value in accordance with underlying CAF is automatically entered in the FDL beneath element Werte Values.

One exception relates to so-called calculated functions whose coding values are only deter- mined by the system during runtime e. Only function value calculated value is displayed in the drop-down list of these functions. Mark branch Werte Values beneath the required func- tion for this.

The existing coding values are then displayed in the text field in the bottom part of the window and the coding values contained can be edited.

When doing this, note that sev- eral coding values must be separated by semicolons, followed by a space. Errored or incom- plete entries are indicated by a red border around the text field. This procedure can also be used to edit coding values of calculated functions.

Note: Editing coding values should be left to experts with adequate knowledge of a control unit since this could otherwise allow invalid coding values to be written to a control unit and, under certain circumstances, this could lead to damage the control unit software. Also, when entering coding values, ensure that the number or quantity of coding values match the func- tion mask.

E-Sys does not conduct a consistency check in respect of the function mask. This is done only during the coding operation by the programming system and leads to coding abort. The changes can be accepted in the tree view with icon in the bottom right-hand section of the window. The FDL must be saved do not save it under a different name! Target users of these functionalities are primarily specialist departments performing a corroboration function and control unit developers.

In Verification mode net coding data, function data lists and vehicle profiles for various vehi- cle orders can be generated automatically and saved in Trace files for further use. In addition, it is also possible to generate and save system variant tables for various vehicle orders from KIS. The GUI for coding verification is shown below: Edit FA can be used to open the loaded vehicle order list in the Vehicle Order Edi- tor if necessary for revision.

The vehicle profile can be populated and displayed for individual vehicle orders via the context menu click with the right mouse button on FA entry calcu- late FP the related vehicle order entry is marked in green. If all vehicle orders of the loaded list are to be used for verification, the root element in the FA tree FAList must be selected. If all boundary conditions are met CAF files to be verified have been selected and vehicle order entries have been marked , verification can be started with button Start Verification.

All specified CAFs with all marked vehicle orders are verified. The scope of checks conducted when verifying CAFs is dependent on the Trace settings. Note: If at least one Trace recording is activated, a Trace directory must be specified to allow verification to be started. The result of a verification run is displayed in the form of a report at the end.

A CAF can be used successfully to code a control unit only if precisely one function value and, consequently, one coding value exists for each function occurring in a CAF after evaluation via a vehicle order. All other results, such as multiple function values double hits or no func- tion value zero hits lead to abort of coding of the control unit.

The more FA elements or FP elements are used for control of coding of a control unit, the greater will be the number of differing vehicle orders required to cover the combinatorial analysis. Ideally, one vehicle order should be created and used for verification for each vehicle profile element used in the CAF.

E-Sys then searches all basic variants con- tained in the SVT and performs the actions as described in Chapter 4. In principle, this type of verification is a string of individual CAF verifications.

The required KIS knowledge base and the evaluation of logic must be available in the data directory for this purpose KIS shares are available after importing the corresponding I-Step container.

Select a main series in the selection box at the left, and the selection box at the right is then automatically populated with the I-Steps supported by the KIS knowledge base for the main series. After selecting the I-Step to be verified, the next step is to load an FA list, analogously to individual CAF verification, and mark the required vehicle orders see Chapter 4.

The relevant fields can be populated with the context menu Edit. When doing this, note the required length of the relevant entry. To assist you, E-Sys shows the entry fields bordered in red until the entry is complete. How- ever, E-Sys does not offer the option of calculating the checksum!

The individual entries must comprise precisely 3 alphanumeric characters. Incorrect entries or in- complete entries are shown by a red border around the entry field. The entry can be transferred to the FA by clicking on icon. An analogous procedure is used to edit existing vehicle order lists. Entire vehicle orders can be deleted from the FA list with the context menu at FA level. This includes, in particular, background processes, such as the indexing service for desktop search or automatic defragmentation services.

Workaround for display problems under Windows E-sys. CR — Customize Esys released notes and welcome screen for privacy, and complete Diaglog settings. KA — Esys-Log should write off the vehicle order used in the TAL processing as a file name so that you can understand this later. What is BMW E-sys? Lock unlock sound confirmation 2. Can operate the navigation menu including watching dvd when driving 3.

Display engine output and torque meter purely fun, look engine output 4. Cancel confirmation screen big screen boot delay 5.