BMW GT1-MANUALen

BMW Service

Participant's ManualBMW Diagnosis, Programmingand Information Systems

The information contained in this Participant's Manual is intended solely for the participants ofthis seminar run by BMW Aftersales Training.

Refer to the latest relevant "BMW Service" information for any changes/supplements to theTechnical Data.

Information status: January 2005

[email protected]

© 2005 BMW AGMünchen, Germany. No part of this publication may be reproduced without the priorwritten permission of theBMW AG, München.VS-12 Aftersales Training

Participant's ManualBMW Diagnosis System

Structured troubleshooting

All information on one user interface

Troubleshooting with test modules

Measuring system inclusive

Notes on this Participant's Manual

Symbols used

The following symbols are used in this Participant's Manual to facilitatebetter comprehension and to draw attention to important information.

3 contains information for better understanding of the describedsystems and their functions.

1 identifies the end of an item of information.

Current content of Participant's Manual

In view of the constant further developments in the design and equipmentof BMW vehicles deviations may arise between this Participant's Manualand the vehicles made available as part of the training course.

The background material refers exclusively to left-hand drive vehicles.The controls are in part arranged differently in right-hand drive vehiclesthan shown on the graphics in the Participant's Manual.

Additional information sources

Further information on the individual vehicle topics can be found in thefollowing information systems:

- BMW diagnosis system

- Workshop Systems Documentation

- SBT BMW Service Technology.

ContentsBMW Diagnosis System

Objectives 1

Introduction 3

DIS Diagnosis and Information System 3

Functions 5

Sequence of BMW diagnosis 5Vehicle identification 7Quick test 9Input of fault patterns/symptoms 10Test schedule 11Control unit functions 12Fault memory entries 15Component activation 18Wiring diagrams 20Function descriptions and notes 21Plug views 22

7

ObjectivesBMW Diagnosis System

Reference material for practical applicationsto accompany you throughout the training course

This Participant's Manual is intended toexplain the structure and operation of the DISdiagnosis software.

The manual is designed as an accompanimentthroughout the training course andsupplements the seminar content specified byBMW Aftersales Training. It is suitable forprivate study and also as a reference work.In preparation for the technical training and in

conjunction with the practical exercises intraining, it is designed to enable the participantto carry out diagnosis work in conjunction withthe BMW diagnosis system.

It is essential to have completed the Diagnosisand Programming Systems module sectionbefore being able to attend all further vehicle-and system-specific seminars in technicaltraining.

Please do not forget to work throughthe Training and InformationProgram (SIP) on this topic.Basic knowledge ensurescompetence in theory and practicalapplications.

1

8

IntroductionBMW Diagnosis System

DIS Diagnosis and Information System

Communication in diagnosisThe sequence of diagnosis communication,i.e. the rules for transmitting and receiving datatelegrams, is identical for all control units inBMW vehicles.

The speed of data transmission has increasedsince the launch of the E65. Since thencommunication between diagnosis systemand control units has followed the rules of thecross-manufacturer KWP2000 protocol (KeyWord Protocol 2000). This specification laysdown all the time conditions and commandsrequired for data communication. The BMWGroup has extended this specification with theBMW FAST protocol (fast access for serviceand testing).

This BMW FAST protocol has made itpossible to increase the transmission ratebetween diagnosis system and control unitfrom 9,600 bits/second to 115,000 bits/second.

The increase in data transmission, thestandardized behaviour of the control units indiagnosis mode and the use of a gatewaymodule between diagnosis system and databuses in the vehicle enable all the diagnosisfunctions to work reliably and quickly in spiteof the increase in the number of control unitsand the wealth of data buses.

3

8

Diagnosis sequence - General

The established diagnosis systems BMWDISplus and Group Tester One GT1 areavailable for diagnosing the model series.

The basic diagnosis sequence proceeds viathe brief test to fault pattern/symptomselection and then to the test schedule. Testmodules, wiring diagrams, functiondescriptions, pin assignments, installationlocations and plug views are available tosupport troubleshooting.

As of the E65 all the selection pages havebeen adapted to the system structure of the"Distributed Functions". In addition, thefollowing modifications have been made:

• Control unit functions:Standard structure of the fault memories inthe control unit functions through allsystems.

• Function descriptions:Standard structure of the functiondescriptions for all "Distributed Functions".

• Installation locations:Depiction of the installation locations withoverview and detailed view.

Only the basic sequence of a diagnosis inconjunction with the BMW diagnosis systemis described in this Participant's Manual. Thehardware (connections, components, etc.) aredescribed on the "Workshop SystemsDocumentation" CD.

DIS as information system

As well as its function as a tester, the BMWdiagnosis system is also available in itscapacity as an information system. Thematching vehicle type can be selected bymeans of manual selection without a vehiclehaving to be connected via an interface. All theinformation contained in the BMW diagnosissystem (DIS and TIS), such as e.g. wiringdiagrams, function descriptions, plug and pinassignments, is then available.

1 - BMW Diagnosis and Information System

4

9

FunctionsBMW Diagnosis System

Sequence of BMW diagnosis

Diagnosis startBefore diagnosis is started, an interface mustbe connected to the vehicle access. Thediagnostic head, the optical testing andprogramming system OPPS and the opticalprogramming system OPS are available asinterfaces.

The access to the vehicle is either thediagnosis socket or the standardized OBDplug for all manufacturers.

The diagnosis can then be started. For thispurpose, the corresponding vehicle must beselected in the "Diagnosis start" screen.

3 The vehicle must always be supplied withexternal voltage during diagnosis (connectcharger). 1

1 - Diagnosis Start model selection

5

9

First the vehicle is identified. Identification ismade either by means of the "Central codingcode" (ZCS) or in the vehicle order (VO). Ineach case vehicle identification datapermitting type allocation of the vehicle arestored.

Once the vehicle order is used (from E65) alarge part of the equipment can also beautomatically detected.

The ZCS is stored in the control unit for theelectronic immobilizer (EWS) while the vehicleorder is stored in the Car Access System(CAS) (or footwell module FRM E87, E90).

If communication with the EWS or CAS is notpossible due to a fault, the vehicle order is readout from the light module (LM).

If the vehicle order cannot be read out, it ispossibly the select the vehicle type manually.

6

9

Vehicle identification

Vehicle order

The vehicle order contains all the importantequipment features of the vehicle in additionto the type code.

3 The advantage of the vehicle order is thatit can store considerably more equipmentfeatures than the central coding code (ZCS).This makes it possible to make a reliable anddetailed vehicle identification. 1

The assembly numbers of the drive controlunits are stored in the vehicle during assemblyand can no longer be altered. It is thereforepossible at any time to identify which partnumbers of the control units were allocated tothe vehicle during production.

2 - Vehicle order data

Index Explanation Index Explanation

1 Vehicle identification number 7 Paint code

2 Production location 8 Upholstery code

3 Production time 9 Optional extras (SA)

4 Type code 10 Assembly number DME1

5 Build date 11 Assembly number DME2

6 Model series 12 Assembly number EGS

7

9

Vehicle equipment

Once the vehicle order has been evaluated,the identification data are output in the "BMWDiagnosis Vehicle Identification" screen.

The read-out data are output in the followingorder:

• Model series

• Model

• Version

• Model year

• Vehicle identification number

In addition, all the control units installedaccording to the vehicle order are marked witha black bar in the three vehicle equipmentwindows (Drive, Chassis, Body). This function

is known as "Preassignment of vehicleequipment".

The function is possible from CD V 28.0!

Only the preassigned control units areinterrogated during the quick test.

If a control unit installed in the vehicle is notdisplayed in the preassignment, an individualquick test must be carried out for this controlunit after the quick test. The individual quicktest is initiated by touching the text linefeaturing the control unit name on the screen.

No preassignment

Reasons for no preassignment may be:

• Control unit has been retrofitted but notprogrammed. The programming must becarried out.

• Fault during evaluation of the vehicle order.

3 - BMW Diagnosis Vehicle Identification

Index Explanation

1 Identification data

2 Drive

3 Vehicle equipment

4 Body

5 Chassis

8

9

Quick test

The quick test is also carried out in the "BMWDiagnosis Vehicle Identification" screen.

All the preassigned control units areaddressed and identified in the quick test.Then the fault memory of the control unit isread out.

The result of the quick test is displayed withone of the following two symbols:

• ! Control unit could be identified and nofault is stored in the control unit.

• X A fault is stored in the control unit.

3 In view of the "Networked Functions" it isabsolutely necessary to carry out the quicktest for the subsequent diagnosis sequence.The quick test is the only way of identifyingconnected faults and faults in the data buses.1

Furthermore a quick test must be carried outso that a control unit can be recorded in the"Check control unit/Control unit functions"program section. The control unit versionmust be determined before the control unit isrecorded in the control unit functions.

If in the quick test a preassigned control unit isnot marked with "!" or "X", diagnosiscommunication cannot be established withthe control unit. Diagnosis mode with thecontrol unit is thus not possible.

In the above example, diagnosis mode is notpossible with the EMF Electromechanicalparking brake control unit.

Causes of no diagnosis communication beingpossible may be:

• Voltage supply to the control unit faulty

• Bus connection faulty

• Control unit is not activated/woken (terminal15WUP to EMF)

• Internal control unit fault

4 - List of control units 5 - Control unit not found

9

9

Input of fault patterns/symptoms

Vehicle systems and faulty functions can beselected in symptom selection.

The BMW diagnosis system draws up a testschedule, which is to lead to the fault cause.

The most probable fault causes are listed bypriority and enable the most important teststeps to be worked through in a structuredmanner in the relevant system.

6 - Symptom selection diagnosis

Index Explanation

1 Vehicle subsystem

2 Perception

10

9

Test schedule

After the fault patterns/symptoms are entered,the test schedule is accessed by touching the"right arrow button". Before the screen isoutput, test modules are assigned and sortedfor all the stored faults and for the input faultpatterns/symptoms of symptom selection.The list of test schedules can besupplemented with personally created testschedules. These test schedules are selectedin the "Function selection" menu.

When the "BMW diagnosis test schedule"screen is output, this brings up an overview ofall the test modules which must be carried outin order to check all the components whichhave an influence on the existing faults.

The test module is started by touching the textline on the screen.

Work-through status

The work-through status of the test modulesis constantly displayed in the test schedule.There is an "end marker" in the test module forthis purpose. This end marker is only set whenthe test module has been fully carried out.

The last page of a test module generallyfeatures the following text:

"Test module is endedContinue with testing schedule"

The end marker is set if after this page theuser returns to the test schedule by touchingthe "right arrow button". In the test schedulethe marker "indicates" that the test modulehas been properly completed.

3 Test modules should always be workedthrough completely! 1

7 - BMW Diagnosis test schedule

Index Explanation

1 DIS test schedule

11

9

Control unit functions

The control unit functions provide a quickoverview of all the diagnosis functions of thecontrol units. They are selected by means ofthe "Check control unit/Control unit functions"screen button.

From the control unit functions the user canuse the "left arrow button" to return to the startscreen. It is important here to remember tocancel the activated diagnosis function beforequitting the control unit function (activatedfunctions are not automatically deactivated).

Diagnosis functionsThe diagnosis functions of a control unit arebasically subdivided into the following maingroups:

• Identification

• Read fault memory

• Delete fault memory

• Component activation

• Diagnosis requests

In the case of control units for which a testcode is documented in the diagnosis protocol,the following function is also provided:

• Read test code

In addition, further system-specific diagnosisfunctions may be provided, such as e.g.:

• Read alarm memory

• Read adaptation values

• etc.

8 - BMW Diagnosis Check control unit/Control unit functions

12

9

Identification

All the identification data stored in the controlunit can be read with the "Identification"control unit function. The data structure isidentical for all the control units on account ofthe BMW FAST diagnosis protocol.

The results in detail:

BMW part number (part number, basiccontrol unit)

Part number of the control unit.In the case of drive control units, part numberof the basic control unit without data record.

Coding index

The coding data dependent on the control unitsoftware or hardware are denoted by means ofthe coding index. The coding index isevaluated by the coding program.

Date of manufacture (DD.MM.YYYY)

Date of manufacture of the control unit.Displayed in Day.Month.Year format.

Diagnosis index

The diagnosis functions dependent on thecontrol unit software or hardware are denotedby means of the diagnosis index. Thediagnosis index is evaluated by the diagnosisprogram.

9 - BMW Diagnosis Check control unit/Control unit functions

Index Explanation

1 Identification data

13

9

Hardware number

Hardware number of the control unitelectronics.

Supplier

Manufacturer of the control unit (companyname).

Function software

Software number of the function software.The function software is responsible for thesequence of system functions.

Message catalogue

Number of the message catalogue used. Themessage catalogue defines which informationis sent over the data buses in the vehicle. Italso specifies whether a message is sent onlyon request or in a fixed time base.

Operating software

Software number of the operating software(basic software).

Variant index

The different versions of a control unit aredenoted by means of the variant index.

Long identification

For the engine control units, there is also anextended identification, the "Longidentification".

The "Long identification" contains additionalidentifications. These identifications are setout in the table below:

Identification Explanation

Assembly number Part number of the programmed drive control unitwith data record.

Authority number Identification number of the control unit forauthorities.

Programming date Date when the control unit was last programmed.

Kilometre reading onprogramming

Kilometre reading when the last programming tookplace.

Program status number A distinction is made between program and datawhen a drive control unit is programmed.The program status number is the versionidentification of the program part which was writtento the control unit during programming.

Data record number Version identification of the data record which waswritten to the control unit during programming.

14

9

Fault memory entries

Fault memory

The basic structure of the fault memory is thesame for all the control units in the E65.

Fault location

• 27A6 Fuel injector, cylinder 1

The fault location indicates which fault acontrol unit has detected. The 4-figure code atthe start of the text line is the fault number asa hexadecimal number. In the event of queries,the fault location can be clearly identified usingthe fault number.

Fault type

• Short circuit to positive (P0262)

• Fault currently not present

• Fault would cause warning lamp (MIL) tolight up

For each fault the fault types are output asadditional information. The fault types indicatewhich fault symptom and which fault statusare present.

In the case of drive control units, the systemalso indicates whether a warning lamp is alsoactivated when the fault occurs.

Excerpt from the"BMW Diagnosis Check control unit/Control unitfunctions" screen:

27A6 Fuel injector, cylinder 1

Short circuit to positive (P0262)

Fault currently not present

Fault would cause warning lamp (MIL) to light up

Frequency 15

Logistic counter 3

1st at kilometre reading 1413 km

1st at engine speed 2613 rpm

1st at engine temperature 91 °C

2nd at kilometre reading 1812 km

2nd at engine speed 3345 rpm

2nd at engine temperature 94 °C

Last at kilometre reading 2134 km

Last at engine speed 1645 rpm

Last at engine temperature 93 °C

15

9

Fault symptom

Possible fault symptoms may be:

• Short circuit to positive

• Short circuit to ground

• Open circuit

• Signal or value above threshold (i.e. asetpoint value has been exceeded)

• Signal or value below threshold (i.e. asetpoint value has been undershot)

• No signal or value

• Implausible signal or value

In the case of drive control units, the P code(P0262) is also output with the fault symptom.The P code is stipulated by law for all exhaust-gas-related faults and is assigned to allmanufacturers.

Fault status

The fault status indicates whether the fault iscurrently present or not. It must be borne inmind here that control units differ greatly whenit comes to fault detection. Many control unitsdetect a fault only when the correspondingfunction is being executed (e.g. doormodules). Other control units use special testsequences to detect faults (e.g. DME). Thefault status therefore does not indicate thefault status currently present in the vehicle butrather the status that existed when the lastfault check was conducted by the control unit.

Warning lamp status

Is only displayed with drive control units.

Frequency counter

• Frequency 15

The control unit records in the frequencycounter how often a sporadic fault hasoccurred. The frequency counter is increasedby 1 each time the fault status changes from"currently not present" to "currently present".

Logistic counter (only partly)

• Logistic counter 3

In some control units the logistic counter isoutput as well as the frequency counter. Thelogistic counter indicates how long a fault afterit has been entered in the fault memory hasnot occurred for. The logistic counter'smethod of counting is as follows:

The logistic counter is set to the value 40when a fault occurs for the first time. When thecontrol unit detects that the fault is no longerpresent, the value of the logistic counter isdecreased by 1 when the control unit isdeactivated. As long as the fault has the status"currently not present", the logistic counter isagain decreased by 1 when the control unit isdeactivated. If however the fault statuschanges to "currently present" again, thevalue 40 is stored in the logistic counter again.

A low value in the logistic counter thereforeindicates that a fault has not occurred forsome time.

16

9

Environmental conditions

For each fault, one or more conditions whichwere present at the point when the faultoccurred are stored as additional information.The kilometre reading is also stored as anenvironmental condition for all faults. Furtherconditions can also be stored, e.g.:

• Outside temperature

• Engine speed

• Supply voltage

• etc.

These environmental conditions can also bestored twice or up to three times for each fault.In this case:

• Display 1st at environmental conditionswhen the fault occurred for the first time

• Display 2nd at environmental conditionswhen the fault occurred for the second time

• Display Last at environmental conditionswhen the fault occurred last

Because of the large memory spacerequirement for the environmental conditions,most of the control units only have thekilometre reading as an environmentalcondition. In addition, this is only stored once.If the kilometre reading is only present once, itis always the kilometre reading when the faultoccurred last.

Diagnosis requestsThe inputs and some of the internal controlunit values can be read out from the controlunit by means of diagnosis requests.

However, the distributed functions call fordetailed system knowledge. It is for examplenot always clear to identify which control unit isprocessing the status of a switch. Thus, thecentral locking button in the E65 for operatingthe central locking may be integrated in thecontrol panel of the heater/air conditioner butthe switch status is recorded by the CarAccess System (CAS).

Furthermore, there are no setpoint values forthe analogue values in the diagnosis requests.

Therefore, in order to test components, thetest modules should be used as a rule.

17

9

Component activation

Some of the outputs of the control units canbe activated by means of componentactivation.

Because of the extensive function operationsonly few component activations can be carriedout in the control unit functions.

Very many component activations can only becarried out within the test modules. Therelevant notes and instructions on componentactivation must be observed without fail.

Function and component selection

Function and component selection is the tableof contents of all the diagnosis documents andtest modules.

In Function and component selection thevehicle electrical system is "broken down" intoits functions and subfunctions.

The left column on the screen lists the mainfunction groups, such as e.g. locking andsecurity functions.

The middle column lists the subfunctions,such as e.g. power window - driver's door. Theright column list the component groupsinvolved in the subfunction.

10 - BMW Diagnosis Function and component selection

Index Explanation

1 Main function groups

2 Subfunctions

3 Component groups

18

9

Component group, i.e. the combination ofindividual components (e.g. switch, leads,control unit input) into a group that can betested by means of diagnosis ormeasurement.

Example: When the status of a switch is readby means of diagnosis, this enables theswitch, the leads and the control unit input tobe tested.

3 In the case of the individual subfunctions,all the component groups which make asignificant contribution to the function areshown. The individual switches, drives orsignals can be connected to different controlunits here.

The components of a component group aretested by means of the test moduleconnected to the component group which isrecorded by means of "Test schedule"selection in the "Test schedule" screen. 1

"Supply" component group

The test module for testing the voltage supply,the bus connection and the internal faults of acontrol units called up by means of the"Supply" component group. The componentgroup brings up a wiring diagram of thissubsection and a function description for thecontrol unit (component description).

If diagnosis communication is not possible fora control unit, the cause of the fault can bedetermined by means of the test module.

The "Supply" component group of a controlunit (e.g. "Door module, driver's door, supply")is assigned to all the subfunctions in which thecontrol unit makes a significant contribution tothe function.

Bus functions

The data buses and gateway modules havebeen combined in the "Bus functions"selection. The function is subdivided into thefollowing "subfunctions":

• K-CAN functions

• PT-CAN functions

• MOST functions

• Gateway functions

• byteflight.

Block diagrams, function descriptions and testmodules are provided for all the data buses.

The test modules for testing the optical fibreswith the optical fibre tester are located underthe subfunctions MOST functions andbyteflight functions.

In addition, the MOST bus is provided with the"Ring break diagnosis" test module, which canbe used to pinpoint the fault location in theevent of a total failure of the MOST ring.

19

9

Wiring diagrams

In contrast to the previous breakdown of thewiring diagrams, the wiring diagrams as of theE65 have been drawn up primarily for thesubfunctions. A wiring diagram thereforefeatures all the components which arerequired for the function.

These wiring diagrams are selected byselecting the subfunction in the middlecolumn of Function and component selection.As previously, the display screen is then calledup by selecting the "Documents" screenbutton.

Wiring diagrams for the component groupsare only provided in the following cases:

• For the component groups in the enginemanagement and transmission controlfunctions

• For the "Supply" component groups

• For component groups which are used inseveral functions (e.g. switches on thesteering wheel, brake light switch).

In addition, wiring diagrams for connectors,ground connections and components for thecontrol units and storage locations of theadapter plugs can be called up by means of"hotspots".

11 - BMW diagnosis document display

Index Explanation

1 Power window, driver's door

20

9

Function descriptions and notes

The function descriptions of the systems havesince the E60 been included in the "TechnicalInformation System" TIS. The test modules ofthe systems feature notes and information onthese function descriptions (SI Technik).

In addition to the function descriptions, notesand background information on thecorresponding test modules are featured inthe DIS.

Installation locations

The way is which the installation locations aredepicted has been changed in order to make iteasier to find components. These installationlocation pictures are also created directly fromthe virtual space data (CAD data). It is thuspossible to respond very quickly to changes inthe vehicle electrical system.

The installation location picture shows thelocation of components, plugs andconnectors.

The large picture shows the detailed view inthe vehicle. The numbers provide a referenceto the wiring diagram.

The small picture in the top left corner showsthe installation location from a larger

perspective (arrow) so that the position in thevehicle can be identified.

The installation locations are selected asbefore by means of the "hotspots" in thewiring diagram.

In addition, installation locations, pinassignments, plug views and wiring diagramscan be selected by selecting "Component andsignal information" from the "Function andcomponent selection" screen. However, it isimportant to bear in mind that all thecomponents and signals of a model series arealways listed in this overview. Componentswhich are not installed are not blanked out.

12 - Depiction of installationlocation

21

9

Plug views

All plugs with more than 2 pins are providedwith plug views which show the shape of theplug and the numbering of the pin sockets.The plug views are called up by means of the"hotspots" in the wiring diagram.

The picture in the top left corner is an adaptersymbol. The number is the adapter number ofthe adapter cable matching the connector.

13 - Depiction of pin assignment

22

Participant's ManualBMW Programming System

Software creates flexibility in the vehicle

Interfaces to BMW and our vehicles

Reliability ensured by efficientprogramming preparation

Programming - standard procedure inevery BMW workshop


Symbols used









- SBT programming with CIP and Progman


ContentsBMW ProgrammingSystem

Introduction 1

Functional principle 3

Hardware necessary for using CIP In theworkshop 3Procedure for changing the software 10Data flow during programming 12Operation 16

Service information 33

Summary 39

6

IntroductionBMW Programming System

Software applications in control units

After leaving the production line, it is possibleto adapt the software of an ever increasingnumber of control units in our vehicles. Thestock of vehicles will rapidly grow to a multipleof today's 350,000 vehicles worldwide.

The provision of software and programmingvehicles will therefore become core processesin every BMW service workshop. Today,retrofits and conversions as well as servicingand repairs of electronic components can becorrespondingly adapted by programming inthe current BMW series.

In this context, a distinction is made betweenthree different options. Each of these optionsrepresents a change or adaptation to thesoftware and functions. However, differentprocedures are implemented for this purpose:

A distinction is made between threemeasures:

• Coding

• Individualization

• Programming

Coding

Control units are adapted to the respectivecontrol unit as part of the coding procedure.This means functions and characteristic mapsare enabled or activated, depending on:

• The country-specific version

• The vehicle equipment

• The vehicle type

Individualization

As part of individualization, e.g. car and keymemory, certain customer-specific settingsare implemented in electrical systems. Thisoption is becoming ever more widespread inthe control and operation of our vehicles.However, settings relevant to safety will, alsoin the future, be implemented by the BMWprogramming system.

Programming

Programming (also known as flashprogramming) loads a new program in thecontrol unit. A distinction can be madebetween control units with:

• Program status and

• Program and data status

The program status of the control unitcorresponds to the operating system andcontrols the computer program in the controlunit. The data status involves thecharacteristic maps and characteristic curvesspecific to the vehicle, engine andtransmission. The CIP programming programmakes the correct selections automaticallywhile programming the respective control unit.After programming the control unit, anynecessary coding procedures areimplemented automatically.

In this participant's manual, the coding,individualization and programming proceduresare referred to collectively as "programming".

1

6

Advantages of software adaptation

• Simple and fast option for retrofits andconversions without the need to replacecontrol units

• Improvement of existing functions

• Introduction of new functions

• Reduction of hardware variants

• Fast response to market requirements

Example

The display range of the E65 control displaywas improved. The software necessary for thispurpose was loaded in connection with modelyear change 2004.

This example clearly shows how a functioncan be simply and quickly improved byreprogramming. There was no need to changethe hardware, in this case the control display.

New system structureA new program structure has beenimplemented with the introduction ofProgman based on the Software ServiceStation platform.

The advantage of Progman is that severalvehicles can be programmed simultaneouslywith one Software Service Station (SSS). This

feature ensures that software updates can beimplemented in the ever greater volumes ofvehicles also in the future. The BMWdiagnosis systems used to date can be usedas operator control terminals.

1 - E65 control display, old version

2 - E65 control display, new version

2

7

FunctionsBMW Programming System

Hardware necessary for using CIP In the workshop

Various hardware components are required forcoding, individualization and programmingprocedures in the dealership network. TheSoftware Service Station functions as thecentral computer.

Coding, individualization or programmingprocedures will only be possible with theSoftware Service Station.

The prerequisite for programming proceduresis at least one programming station perworkshop with the following equipment:

• 1 Software Service Station (SSS)

• 1 OPPS (optical testing and programmingsystem) or OPS (optical programmingsystem)

• 1 Battery charger

• Workshop network (printer)

The following devices can be additionally usedin connection with Progman:

• DISplus

• GT1

An overview of the workshop networkand its components is provided in thefold-out page at the end of thisdocument.

A detailed description of the workshopnetwork and all hardware componentscan be found on the "DocumentationWorkshop Systems" CD.

General preconditionsTo avoid unnecessary problems caused byexternal intervention and interruptions in theprogramming procedure, the programmingstation must not be made accessible tocustomers. The cables must not crossthrough-traffic.

3 The programming procedure may beterminated if a bus signal is generated as theresult of activation of electric loads duringprogramming. The programming procedureshould be repeated following termination. Inexceptional cases it may be necessary toreplace the control unit if communication is nolonger possible. 1

Consequently, valuable time is lost where theprogramming station could be used for otherpurposes. The SSS does not need to beplaced directly at the vehicle. It can be installedin any protected position

provided it has a network connection.

In addition, a battery charger must be availableper programming station.

A network printer should be connected in thevicinity of the programming stations so thathard copies can be created if necessary.

To avoid damage, the network cables shouldbe routed to the vehicle in such a way that theyare completely protected.

The programming stations should generallybe installed inside the workshop. If this is notpossible the programming station installedoutdoors must be protected from theinfluences of weather and made inaccessiblefor customers.

3 Generally the interfaces must beconnected by cable during programming. 1

Control units can now only beprogrammed with the SoftwareService Station.

3

7

Hardware operating conditions

Software Service StationThe Software Service Station (SSS) replacesthe DISplus and Group Tester One diagnosissystems as the programming system.Together with the optical programmingsystems (OPPS/OPS), the Software ServiceStation offers a powerful and scalable platformfor programming, coding and individualizationof the vehicles of the BMW Group.

In the first expansion stage, the SoftwareService Station can be used on all BMW andMINI model series and for all Rolls-Roycemodels as from late 2004.

As on the DISplus and GT1, data is supplied tothe Software Service Station by means ofDVD-ROM and CD-ROM. Additional data isprovided by online updates with JETstream.The application software SGS (control unitcoding for older model series) and CIP

(coding, individualization, programming) canbe used in the first expansion stage.

Device Operating temperature Relative humidity

GT1 +3 °C - +43 °C 10 - 80 % (no condensation)

OPPS/OPS +3 °C - +43 °C 10 - 90 % (no condensation)

SSS +10 °C - +35 °C 10 - 90 % (no condensation)

Monitor SSS +3 °C - +35 °C 10 - 90 % (no condensation)

1 - Software Service Station

4

7

OPPS/OPS/diagnostic head

OPPS

The optical testing and programming systemOPPS, the optical programming system OPand the diagnostic head can be used togetherwith the software Service Station to serve asthe interface to the vehicle. The OPPS wasused for diagnosis of the byteflight andMOST bus systems used for the first time inthe E65 (fibre optics).

Corresponding to the model and equipment(see information diagnosis coding IDC), inaddition to the OBD socket, MOST DirectAccess is used in connection with the OPPSto shorten the programming time required forMOST control units compared toprogramming via the OBD socket only (30 to60 percent depending on the control unit).

In addition to the optical testing andprogramming system OPPS, the opticalprogramming system OP has been availablesince mid-2003. In the same way as theOPPS, the optical programming system OPScan be used for connecting the SoftwareService Station to the vehicle.

3 The connection cables for the OBDsocket and MOST Direct Access can beconnected in any order. As soon as the OPPS/OPS detects the connection to MOST DirectAccess, programming data are sent via thisaccess link as required.

No error message is displayed if MOST DirectAccess is disconnected during theprogramming procedure. The programmingdata are still sent via the MOST output. Amessage indicating that a fault occurredduring programming is then provided in thefinal report. 1

Description of the LEDs

LED next to the mains power connection:

LEDs next to the MOST connection:

2 - Optical testing and programming system Index Explanation

Green,flashinglight

OPPS/OPS free

Green,steady light

OBD connection

Green,flashingrapidly

Software update activated

Orange,steady light

Self-test active/fault

Index Explanation

Red LED Voltage supply

YellowLED

Data transfer

Green LED Bus lock

5

7

Differences between OPPS and OPS

Optical testing of the byteflight is notpossible with the optical programming systemOPS. The OPS does not feature the pc-boardand the set of adapters necessary for testingthe byteflight.

The optical programming system OPS cannotbe used for optical testing applications and isemployed solely for optical programming ofthe MOST. The set of adapters necessary fortesting MOST control units is not included inthe standard OPS equipment. However, theOPS can be used to test the MOST whenused together with the set of adaptersprovided with each OPPS.

Diagnostic head

The OPPS/OPS is not necessary on vehicleswith no fibre optics conductors (e.g. E83,E85). The diagnostic head is still used onvehicles with no MOST bus to serve as theinterface to the vehicle.

3 The diagnostic head must not be used forprogramming on vehicles with MOST DirectAccess. The optimum programming times areachieved only with the OPPS or the OPS. 1

3 - Optical programming system

4 - Diagnostic head

6

7

Multichannel programming

The CIP decides what data paths are to beused for programming depending on the typeof vehicle.

The options for using various channels differdepending on the model and equipmentconfiguration. The following variants arepossible:

During the programming procedure, thedisplay screen shows whether programming isperformed on one or two channels.

The graphic below shows parallelmultichannel programming.

The final report indicates whether the controlunits were programmed via the OBD socket orMOST Direct Access.

Type of programming Explanation

Single-channel programming All programming data are routed via the OBD socket inconnection with single-channel programming.

Multichannel programming,sequential

In connection with sequential multichannel programming, theprogramming data are sent sequentially (one after the other)via the OBD socket and via MOST Direct Access.

Multichannel programming,parallel

In connection with parallel multichannel programming, theprogramming data are sent simultaneously via the OBDsocket and via MOST Direct Access.

5 - Multichannel programming

Index Explanation

1 Connection, OBD socket

2 Connection, MOST DirectAccess

3 Connection, BMWprogramming system

7

7

Group Tester One/DISplusAs from 09/2004, the BMW diagnosissystems GT1 and DISplus will be used asoperator control terminals for programmingprocedures. The BMW diagnosis systems willthen be used only to control the programmingsequences. The actual programming will beperformed solely by the Software ServiceStation. There will be no data for programmingprocedures on the BMW diagnosis systems.The two BMW diagnosis systems usedifferent connections.

The DISplus is integrated in the workshopnetwork by means of a network cable. TheGT1 can be incorporated in the workshopnetwork by way of a radio remote interfaceproviding increased flexibility in everydayworkshop operation as no cable connectionsare necessary.

Workshop networkThe workshop network plays a key role in theexpansion of the CIP programming software.All devices for programming, control/operationand the interfaces to the vehicles areincorporated in the workshop network. Allfuture expansions will be based on a networkoperable in the workshop. In addition to theperviously described devices, the workshopnetwork comprises the following elements:

• 19" cabinet and patch panel

• Switch

• Access point

• Printer

• Cabling and network sockets

19" Cabinet

The 19" cabinet serves the purpose ofaccommodating the switch, patch panel andthe socket strip for powering thesecomponents. The 19" cabinet must besecured against a wall in a central, protectedlocation in the workshop.

The patch panel accepts the network cables.The network cables installed in the workshopare connected to terminal strips at this panel.From the patch panel, the individual cable

looms are connected via flexible patch cablesto the switch. This arrangement preventscable breaks and connections can e changedquickly and simply.

Switch

The 19" cabinet also houses several switches.The switch is the central distributor in theoverall BMW workshop network. The switchestablishes the data exchange between theindividual devices, the connection to theinterfaces in the vehicles and ultimately theconnection to BMW.

Access point

The access point establishes with wirelessconnection of the diagnostic head and GT1control elements with the workshop network.The access point is also connected to theswitch.

6 - Group Tester One

8

7

Vehicle accessDepending on the vehicle model andequipment configuration, various accesspoints are provided on the vehicle forconnecting the OPPS/OPS/diagnostic headinterfaces.

• OBD socket

• MOST Direct Access

OBD socket

The OBD socket is standardized for allmanufacturers. The OBD socket must belocated in the vehicle interior and beaccessible from the driver's seat.

The OBD socket is closed off by a cap. Thepins 7 and 16 are bridged on the end cap sothat the diagnosis link (TxD line) is connectedto terminal 30 and protected from interferencepulses. A resistor (820 ohms) is installed in thejumper (bridge) for the purpose of attenuatingvoltage peaks.

MOST direct access

MOST Direct Access is always installed onvehicles equipped with a MOST bus. Inaddition to the OBD socket, the MOST DirectAccess must be connected for programmingpurposes.

Access to the vehicle differs corresponding tothe model. A detailed description can be foundin the BMW Service Information - TechnicalSBT 00 03 03 (054).

7 - OBD socket (E60)

Index Explanation

1 End cover

2 End cap

3 OBD socket

8 - MOST Direct Access (E60)

Index Explanation

1 End cover

2 Left mounting bracket, glovecompartment

3 Glove compartment

4 Protective cap for MOST DirectAccess

5 MOST Direct Access (flashconnector)

9

7

Procedure for changing the software

An important prerequisite for ensuringtrouble-free programming is the correctpreparation of the vehicle. Specialrequirements apply to the individual BMWmodels. These requirements are describedunder the IDCs (information, diagnosis and

coding). The measures that apply to all BMWmodels are described in the following.

3 A diagnostic procedure must first beperformed on the vehicle prior to anyprogramming. Programming must not bestarted before faults in the vehicle electricalsystem are ruled out. 1

Preparatory measures

Correct preparation of the vehicleavoids errors during programming.

Attention Points to be observed

Engine

Turn off engine, ignition key turned to terminal 0

Manual gearbox/SMG

- Transmission in neutral- Parking brake applied

Automatic transmission

- Transmission in position P- System temperature below 80 °C

Attention: Do not apply parking brake on vehicles equipped with theelectromechanical parking brake.

Electric loads

All electric loads, lights and direction indicator lights switched off.

Wipe/wash system switched off. Make sure that the wipers can movefreely. The wipers may be activated during programming. On noaccount block the wipers.

10

7

Battery

The battery should be sufficiently charged at the start of theprogramming procedure (12.6 V).

Battery charger

Connect battery charger (see Service Information - Special tools/equipment 02 03 098 350). Do not connect or disconnect the chargerduring programming. The system voltage must not drop below 12.6 Vduring the programming procedure.

Diagnosis

Perform quick test.

Using the diagnosis system, rectify any problems before programmingand clear stored fault codes.

Programming

Check CKM values, also observe individual settings on the vehicle(function specific to model series) if applicable, start programmingprocedure.

Attention: The data status of the Software Service Station mustalways be kept updated!

Vehicle with MOST bus

Program with OPS/OPPS only. Make sure that the current firmware isinstalled.

Make sure that no switches, radio etc. are operated duringprogramming as this could terminate the programmingprocedure.

Attention Points to be observed

11

7

Data flow during programming

Data flow in the workshop network

The entire communication with the controlunits in the vehicle takes place from theSoftware Service Station (red data route).

The BMW diagnosis systems GT1 andDISplus can be used as operator controlterminals. The processes in the SoftwareService Station can be monitored andcontrolled on the display screens of the BMWdiagnosis systems (blue data route). TheBMW diagnosis systems are not directlyconnected to the vehicle.

3 The programming data are sentexclusively by the Software Service Station viathe workshop network to the vehicle. 1

The workshop network is a basicprerequisite for programming. Theactual programming procedure isexecuted solely by the SoftwareService Station.

9 - Data flow in the workshop network

Index Explanation

1 Software Service Station

2 Switch

3 Data route between BMW diagnosissystem and Software Service Station

4 Data route between SoftwareService Station and vehicle

5 Battery charger

6 Interface (here OPS)

7 BMW diagnosis system (here GT1)

12

7

Data flow in the vehicleThe data exchange between the SoftwareService Station and the individual control unitstakes place via different routes in the variousvehicle models.

The first step in all cases is to read out thevehicle order, the vehicle data status and thekilometre reading. Depending on the vehiclemodel, the vehicle order and the vehicle datastatus are stored in the car access system orin the electronic vehicle immobilizer. this datais also stored redundantly in the followingcontrol units corresponding to the vehiclemodel:

• Light module - E6x, E52, E53, E38, E39

• Light switch cluster - E46, E83, E85

• Footwell module - E87

The vehicle order is essential forprogramming. The vehicle order must berequested and obtained if not available ordamaged.

3 The vehicle order can be called up onlywhen there is a data link set up to the controlunits and the control units are operatingcorrectly. 1

Reading out vehicle order

By way of example of the E87, the graphicbelow shows the data link necessary forreading out the vehicle order, the vehicle datastatus and the kilometre reading. In addition tothe components in the workshop network, thefollowing components in the vehicle areinvolved in the communication procedure:

• Diagnosis bus

• Junction box (gateway function)

• K-CAN

• Car access system

• Instrument cluster

• Footwell module

10 - Data flow in the vehicle

13

7

Programming the control units

Various access points can be used forprogramming the control units in the vehicle.The control units in the MOST systemnetwork are programmed via MOST DirectAccess (flash connector).

The remaining control units in the K-CAN, PT-CAN and F-CAN bus systems areprogrammed via the OBD interface.

The DME, FZD and CDC control units areprogrammed in the following example.

In addition to the components in the workshopnetwork, the following components in thevehicle are involved in the communicationprocedure:

• Diagnosis bus


• K-CAN

• Roof functions centre

• PT-CAN

• Digital Motor Electronics

• MOST bus

• CD changer

• Top-HiFi amplifier

• Universal charging and hands-free facility

• Radio 2


14

7

Problems involved in the case of fault

Vehicle diagnosis cannot be performed withthe programming system.

In the following example, there is a break in thepower supply to the radio 2 (fuse defective).As a result, communication is down in theentire MOST bus. All MOST bus users areshown as "did not respond/incorrectresponse" in the action plan. A diagnosticprocedure must be started if this situationoccurs during programming.

In addition to the components in the workshopnetwork, the following components in thevehicle are involved in the communicationprocedure:

• Diagnosis bus


• K-CAN

• Roof functions centre

• PT-CAN

• Digital Motor Electronics

The entire MOST bus is inoperative due tofailure of the radio 2. Consequently,programming data cannot be sent via this bussystem.

3 If several control units are indicated as"did not respond/incorrect response", thisnormally points to a fault in the area of thegateway or bus systems. 1


15

7

Operation

Explanation of terms - Progman and CIPAs from 09/2004, Progman (programmingmanager) will adopt functions from the BMWdiagnosis and programming systems andprovide new operating and control options.The software will still be available on a CD andDVD. The CD contains a new operatingsystem (Windows XP Embedded). Thecurrent operating system of the BMWdiagnosis systems will no longer be used.

The DVD contains CIP and all administrationand configuration tools in connection withprogramming procedures.

Progman involves a new program structure.With the Software Service Station functioningas the platform. The necessary data are sentvia CD/DVD and JETstream.

Modified operating procedurethrough new functions. New menusfor multiple vehicle programming.

Platform: Software Service Station Software Update

CIP DVDor Delta viaJETstream

Progman basic CD

Index Explanation

1 Progman - programming system

2 JETstream - online data update

3 Administration - basic settings and administration interfaces Progman

4 Multiconsole/multisession - operation via various devices/management ofseveral vehicles

5 CIP - program part for programming BMW vehicles

6 Windows XP Embedded - operating system

16

7

Progman

The new programming manager (Progman)facilitates parallel programming of up to fivevehicles (different model series and differentvehicle data statuses) that are programmablewith CIP.

JETStream

JETStream is the basic application for theonline data update of the diagnosis andprogramming systems DISplus, GT1 andSSS.

With the introduction of JETstream it ispossible for the first time to make dataavailable online for the diagnosis andprogramming systems. It forms the basis forconsiderably faster and more efficientinformation exchange from and tot heworkshops of the worldwide dealershipnetwork.

Administration tool

The administration tool provides the samesetting options as before with the BMW

diagnosis systems. Progman, however, givesrise to several changes and additions:

• Installation of JETStream printer

• Administration of OPPS/OPS/diagnostichead

Multiconsole/Multisession

Progman makes it possible to simultaneouslyprogram several vehicles with differentoperating units (GT1/DISplus). Consequently,it is therefore necessary to manage severalvehicles on the display screen of the SoftwareService Station or of the operating units (GT1/DISplus).

With Progman it is possible to distinguishbetween vehicles by using various features(e.g. vehicle number plate). The selectedvehicles are ultimately released forprogramming. The CIP software is responsiblefor the actual programming procedure.Operation and control of the administrationprogram is described in the following chapter.

Index Explanation

Multiconsole The multiconsole function makes it possible to control programmingprocedures both via the Software Service Station as well as via the BMWdiagnosis systems GT1 and DISplus.

Multisession The multisession function makes it possible to program several vehiclessimultaneously.

17

7

Operating system

Progman is a new tamper-proof operatingsystem for programming applications at BMW.Progman utilizes Windows XP Embeddedwhich, from now on, will serve as the basis forall further programs required for programmingapplications. No changes can be made to theoperating system of this Windows variant andit can be used only in connection with thecorresponding hardware (Software ServiceStation).

The change in operating system gives rise tochanges in the operation and controlprocedures in Progman. The OPPS/OPS/diagnostic head must be assigned either todiagnosis or to programming. A detaileddescription of the operation and controlprocedures is provided in the next chapter.

CIP

The program part CIP is responsible for theactual programming tasks. This program partdefines what data statuses are to be assignedto what vehicles. The actual vehicleprogramming procedure runs via CIP.

Progman operation and controlThe possibility of simultaneouslyprogramming several vehicles with oneSoftware Service Station and the newoperating system have resulted in changes inoperating and control procedures.

Administration - Vehicle interfaces

After connecting the interface (OPPS/OPS/diagnostic head) to the vehicle, the interface isdisplayed in the corresponding menu and canbe selected.

18

7

Progman start screen

Upper screen area

The following functions are available in theupper area of the screen:

• Administration

• Help - this menu contains online help toProgman

• Hardcopy - the screen view can be printedout by pressing the Hardcopy button

• Home - Home always brings the user backto the start screen

Right-hand area of screen

The right-hand area of the screen shows thevehicles already in the Progman system.

• Orange lettering means - interactionnecessary, systems waiting for input (thesymbol serves as an added indication)

• Black lettering means - input field can bemaximized, details are then shown. Theremaining run time of the current action isdisplayed.

• Grey lettering means - session being usedand cannot be selected by another user.

Lower screen area

New sessions can be created in the lower areaof the screen and existing sessions can besorted according to name and status.

In the Progman startscreen, functions can beselected in three areas:

• Upper screen bar

• Right-hand area ofscreen

• Lower screen bar

Index Explanation

1 Upper screen area

2 Orange - interaction necessary

3 White - detailed view available

4 Grey - session in progress

5 Sorting according to name

6 Right-hand area of screen

7 Sorting according to name

8 Lower screen area

9 New session

19

7

Interface

Status

"Status" indicates the operating status of thecorresponding interface. This is followed bythe description of the colours and symbols.

As soon as a newsession is started, theinterface previouslyconnected to the vehiclecan be selected from thelist of three interfaces.The followinginformation is shown inthis screen:

• Status

• Interface name

• Version

• IP address

• External interface

Index Explanation

1 Status

2 Interface name

3 Version

4 IP address

5 External interface

20

7

Symbol Description

Green background - interface is free and can be selected

Grey background - interface not detected

- It is currently being shut down or started up

- It is unconfigured referred to the sub-network in which it islocated

Red background - the interface is occupied and is notavailable for a session

It is possible to query the configuration and the current session.

Black lettering - interface can be selected

Grey lettering - interface cannot be selected as it is notavailable or cannot be reached

Black question mark - interface is unconfigured referred tothe sub-network in which it is located

Grey question mark - connection to interface is notpossible, the device cannot be reached

Black gearwheels - the interface is currently being usedexclusively. Only the configuration data can be queried.

Diagnostic head

OPS

OPPS

21

7

Examples of possible combinations

Interface name

An interface name can be freely assigned toeach interface so as to simplify definition of theinterface in the workshop.

Version

The firmware version indicates the softwareupdate the selected interface (OPPS/OPS/diagnostic head) is currently using. Followingthe installation of a software update of a newsoftware, the firmware version is transferredautomatically after initial connection with theinterface. The information shown in this fieldkeeps the user updated with regard to thecurrent status.

IP address

The IP address (internet protocol address) is auniquely assigned address for each device inthe workshop network.

This address consists of a number blockwhich is normally structured as follows.

Example of a number block:

192.168.100.10

The addresses must be structured such thateach device in the network is distinguishedfrom all the others. In this way, it can bedefined exactly and uniquely identified in theworkshop network.

External interface

This column indicates whether the currentinterface is an external interface. Externalinterfaces are located in external sub-networks and can be used in connection withthis Software Service Station.

Symbol Description

OPS with grey background and grey question mark

The OPS is in its own sub-network and is currently being startedup or shut down.

Interfaces in their own sub-network are indicated only when theyare connected.

Interfaces from external sub-networks are always shown. Whenthey are not connected, they are indicated as a grey question markon a grey background without the interface symbol.

OPPS with grey background and black question mark

A black question mark means that the OPPS is unconfigured,referred to the sub-network in which it is used.

Diagnostic head with red background and blackgearwheels

The diagnostic head is currently being used. New firmware isloaded in this case.

The diagnostic head is not available for a session. Theconfiguration can be queried.

22

7

Session

Depending on the workshop organization,vehicle licence plate numbers can be usedthat are assigned to the vehicles.

These licence plate numbers are assigned tothe interfaces (OPPS/OPS/diagnostic head),thus ensuring the vehicle can be identified onthe screen.

The screen keyboard can be operated eithervia touch-screen or a mouse. Information canbe additionally entered via the keyboard inconnection with the Software Service Station.

The interfaces can beassigned to the vehicleson the "Session" screen.Freely selectablenumber and lettercombinations can beused for this purpose.There are no restrictionsin this case. Followingexamples are possible:

• Vehicle licencenumber

• Cone/guide number

• Vehicle identificationnumber

• Type/colour

Index Explanation

1 IP address of interface

2 Freely selectable identifier

3 Interface name

4 Keyboard

23

7

Model series SELECTION

The correspondingBMW model is selectedunder model seriesselection.

The previously enteredidentification is shown inthe upper area of thescreen.

Index Explanation

1 Model series selection

24

7

Action plan

3 An action plan must be worked throughcompletely in all cases. 1

The jobs or proceduresnecessary for creating aconsistent vehicle areshown in the action planbased on the logicintegrated in the CIP.

This means control unitsmay be shown that needto be replaced,programmed or coded.

The aim is to ensure thatcontrol units of onevehicle can interact.

Index Explanation

1 Vehicle data (model series and vehicle identification number) and time are shown.

2 Vehicle order - the optional equipment of the vehicle is defined in the vehicle order.

3 Vehicle data status - current data status of the vehicle.

Target data status - data status after working through the action plan.

Vehicle model (E060), data status year, data status months, data status description.

4 List of control units to be programmed, old and new part numbers of the controlunits, data path for programming.

25

7

Vehicle data status and compatibilitymanagement module

To ensure the consistency of the control unitswith respect to each other, the vehicle datastatus of the vehicle is compared with the dataof the compatibility management module onthe Software Service Station. The basis for thedefinition of the vehicle data status is thevehicle order that is read out of the car accesssystem and the light module. Various vehicledata are stored in the vehicle order (vehicledata status, optional equipment etc.). Thevehicle order is shown in the action plan.

The vehicle data status describes aconstructional status that ensures all controlunits of a vehicle model are compatible witheach other. The vehicle is thereforeconsistent. As soon as an action plan iscreated, the actual vehicle data status iscompared to data in a database (compatibilitymanagement module). All hardware andsoftware versions of control units are stored inthe compatibility management modulereferred to the vehicle data status. The CIPassigns a specific measure to the vehicle if a

hardware or software version does not agreewith that of the vehicle. This measure may bea software update or a control unitreplacement so that the vehicle then achievesthe target data status.

3 In all cases, a trouble-free vehicleelectrical system is assumed before a controlunit replacement or software update! 1

Loading software

As soon as the "Load Software" operation isactivated, the window can be minimized toallow other vehicles to be processed. Thefollowing information and buttons are shown:

• Current operation

• Vehicle identifier

• Button to minimize the screen

• Time required to complete the action

After "Minimize" is selected, the Progmanstart screen reappears and a new session canbe started.

26

7

Session

Session status

The status indicates what processes oroperation are currently active in this session. Inthis case, the Software Service Station waitsfor a user action. Once this action has beenexecuted, the programming can continue orbe concluded.

The orange and whitebuttons in the list on theright-hand edge of thescreen can be selectedat any time. As soon as avehicle is selected, themost important data ofthe vehicle and theprogramming tools areshown in the left-handarea of the screen.

Index Explanation

1 Interface name

2 IP address

3 Vehicle identification number

4 Session status

5 CIP version used for programming

6 SSS name - name of SoftwareService Station

27

7

Final report

The vehicle data status and the target datastatus should agree following successfulprogramming.

The executed actions are shown in thefollowing. Successful or terminated actionsare indicated by a green tick or a red crosspreceding the action.

The final reportdocuments all executedjobs on completion of ameasure. In addition tothe executed jobs, itprovides information onthe time the action isexecuted and on thevehicle.

Index Explanation

1 The time (date/time), vehicle (model series/vehicle identification number) andthe data statuses (vehicle data status/target data status) are shown in this areaof the action plan.

2 The programmed control units are shown in this area.

3 The executed actions are shown in this area.

28

7

Example

In this example, the following executed actionsare indicated under Item 3:

Finally, a vehicle context test is performed in allcases and also shown in the final report.

Index Explanation

Action plan selected Indicates that an action plan was selected and executed.

CKM backup successful Car and key memory values were stored on the programmingsystem.

ANT programmed Indicates what control units were programmed and how the partnumbers changed.

Data status savedsuccessfully

A new vehicle data status was stored in the control unitsresponsible for this purpose.

CKM recreationsuccessful

Car and key memory values were written back to the vehicle.

ASK adjustmentsuccessful

The installed control units and their sequence are stored in theregistration file of the audio system controller.

29

7

General CIP operation and control

Special measures

The special measures function should only beused when the normal procedure forautomatically determining and workingthrough an action plan is not successful. In thiscase, individual control units can beprogrammed using the special measuresfunction and in some cases software errorscan be rectified.

After implementing the special measures, itmay be necessary to work through furthermeasures with the remaining control units.These measures must be performed in allcases otherwise an inconsistent vehicle will becreated where fault can occur.

Complete coding

The complete coding function may benecessary when vehicle functions do not workor do not work correctly on completion ofprogramming. The complete coding functionoverwrites all coding-relevant settings of allcodable control units.

Retrofit

Assemblies such as the air conditioningsystem for instance can be retrofitted via theretrofit menu. This retrofit procedure with CIPadapts the systems to the overall vehicleelectrical system and systems network.

The vehicle must be in a fault-free conditionprior to implementing a retrofit/conversion.The vehicle order in the vehicle will not bechanged if a fault is determined while workingthrough the action plan (red cross in final

report). In this case, the retrofit/conversionshould be carried out again with CIP.

Conversion

A conversion involves changing individualfunctions in a control unit.

Car and key memory

The letter I stands for individualization of thevehicle and key settings for the customer.Since the market introduction of the E65, theoptions of individually adapting a vehicle tocustomer-specific requirements have beenadopted from the operator interface of theBMW diagnosis system in the programmingenvironment CIP.

Since the market introduction of the E60, ithas been possible to implement varioussettings in the vehicle itself. The exact scopeof settings can be found in the IDCs for theindividual models.

Personal profile

As from the market introduction of the E87,the majority of settings can be implemented inthe vehicle itself. The individualization of thevehicle is now known as "Personal Profile" (fora detailed description please refer to theParticipant's Manual Personal Profile).

Only settings which are difficult tocomprehend for the customer (e.g. anti-theftalarm system, tilt alarm sensor) are stillimplemented in the CIP under the retrofit/conversion menus.

30

7

Subsequent measuresIndividualization data may be lost as soon as acontrol unit is replaced or programmed. CIPconsequently assigns measures for renewedlearning of these individualization data.Depending on the system, this is implementedautomatically by CIP, e.g.

• Power window characteristic curve

Other systems require intervention from theoutside, e.g.

• Initialization of active steering (diagnosis)

Subfunctions of the systems operate only inconnection with such initialization. Forexample, the control unit responsible forpower window control must be relearned.

For instance, the degree of stiffness and endstops of the individual side windows arerelearned. CIP activates this procedureautomatically.

Quick test

In all cases, a quick test must be performed with the BMW diagnosissystem after programming. With CIP it is not possible to ensure that allfault code memories are cleared reliably.

Bus rest

All control units must assume sleep mode after programming. For thispurpose, allow the vehicle to rest for at least 5 minutes at terminal 0.

The following indicators show inactive bus systems in the variousvehicle models.

• E65 -CAS slot

• E60/E61 - Child safety lock LED

• E87 - Start/Stop unit

The bus system is inactive as soon as the light goes out.

31

8

Service informationBMW Programming System

Administration Progman

Overview

Interfaces

The OPPS/OPS and diagnostic head can bemanaged and configured in the interfacesmenu.

Settings

The Software Service Stations can bemanaged under the settings menu. Theadministration of more than one SoftwareService Station will be possible after the nextupdate.

User interface

The languages can be set in Progman directlywithout the need for reinstallation in theadministration.

The setting options in the interfaces menu aredescribed in the following.

The following settingoptions are provided inthe "Administration"menu:

• Interfaces

• Settings

• User interface

Index Explanation

1 Administration overview - theSoftware Service Stations andinterfaces are configured here

2 Interfaces

3 Settings

4 User interface

33

8

Interfaces

All active interfaces areshown as soon as the"interfaces" button isactivated.

The buttons in the right-hand area of the screenare activated and can beselected by clicking onone of these interfaces.

Index Explanation

1 Overview - the search for interfaces can be re-activated by pressing this button.The list of interfaces is not updated for as long as this screen is active. The list isupdated when the "Overview" button is clicked again.

2 Configuration - interfaces can be configured by clicking on this button.

3 Update interface - the firmware of the interface can be checked and updated byclicking on this button.

4 Self-test - the interfaces (OPS/OPPS/diagnostic head) can be checked by meansof this self-test.

5 External interface - external interfaces can be added or removed via this button.

34

8

Configuration

Interface name

The interface name can be freely assigned.The interface name should have a uniquenomenclature that makes it possible to definethe individual interface and to assign it ineveryday use in the workshop.

MAC address

The MAC address (Media Access Control) isthe hardware address of each network device(network card, switches) that are used forunique identification of the device in thenetwork.

IP address

Unique addresses must be assigned to theworkshop devices to facilitate the exchange ofdata packages between them.

IP sub-network screen

The IP sub-network screen indicates the partof the IP address that describes the sub-network. The standard address is255.255.255.0.

The data in this area of the administrationmenu should be managed by a networkadministrator. After entry, the data areconfirmed again. The interface then performsa reset. The settings are stored after the reset.

Gateway

The gateway represents an interface betweenthe various networks.

The interfaces for theindividual BMWworkshop network canbe adapted in the"Configuration" menu.

The setting options aredescribed in thefollowing. The screenkeyboard can beoperated from thetouch-screen or bymeans of the mouse.

Index Explanation

1 Device type - OPPS in this case

2 Interface name

3 MAC address

4 IP address

5 IP sub-network screen

6 Gateway

35

8

Update Interface

The firmware version ofthe interface and of theSoftware Service Stationcan be checked in the"Update Interface"menu.

An update is performedautomatically if thefirmware version is nolonger the current one orif the versions of theinterface and of theSoftware Service Stationdiffer from each other.

This is then followed bya reset in order to startthe new firmware.

Index Explanation

1 Update Interface

2 Interface name

3 Last update - the date of the last update is shown here

4 Latest firmware status of Software Service Station

5 Latest firmware status of selected interfaces

36

8

Self-test

The interfaces can bechecked to ensure theyare operating correctly inthe "Self-test" menu.

One or two test loopsare required for thispurpose depending onthe type of interface.The result can beprinted out.

Index Explanation

1 Interface name

2 Device type OPPS/OPS/diagnostic head

3 User instructions for self-test

4 Test loop for MOST Direct Access

5 Test loop for byteflight

37

8

External interface

Interfaces must be removed if they are nolonger to appear in the selection list.

This ensures that the list only shows theinterfaces that are to be used in connectionwith the Software Service Station.

External interface

Interfaces in externalsub-networks can beadded or removed in the"External Interface"menu.

Depending on thesystem structure, it ispossible that other sub-networks are defined insub-areas of theworkshop network.Interfaces from externalsub-areas must beadded in this menu inorder to connect them toa Software ServiceStation as required.

Index Explanation

1 "External interface" menu

2 Adding an external interface

3 Removing an external interface

38

9

SummaryBMW Programming System

Summary of new features

The following table provides a summary of themost important information on programmingapplications at BMW.

This list outlines the main points in conciseform and provides the opportunity ofrechecking the most important facts providedin this Participant's Manual.

The Software Service Stationadopts the key role in theprogramming procedure.

Software Service Station

BMW vehicles can now only be programmed with the SoftwareService Station. The Software Service Station establishes aconnection with the vehicle and sends the programming data via thevehicle interfaces to the control units.

BMW diagnosis systems

The BMW diagnosis systems Group Tester One and DISplus can stillbe used as operator control terminals.

The BMW diagnosis systems are connected to the Software ServiceStation their screens show corresponding information and they serveas the remote control of the Software Service Station.

Progman

New screen masks and new user functions have been developed toaccommodate the expanded options with Progman.

Up to five vehicles can be programmed simultaneously with Progman.Progman also makes it possible to manage programming proceduresvia various terminals.

39

Participant's ManualBMW Information System

Technical information

Function descriptions

Repair instructions

Detailed information


Symbols used









- BMW diagnosis system


- SBT BMW Service Technology.

ContentsBMW Information System

Introduction 1

Information on BMW Technology 1

9

IntroductionBMW Information System

Information on BMW Technology

The technical information systems arebecoming ever more important in thetroubleshooting process of modern systemsin automotive engineering. Sound informationon the technology used is therefore necessaryfor the diagnosis and repair of complexsystems.

The technical information systems at BMWcontain e.g. information on the mode ofoperation of the systems and technical details(pin assignments, cable colours, setpointvalues, installation locations, etc.).

Information optionsTo ensure reliable fault diagnosis, it isbecoming increasingly important to have asound knowledge of the correct function ofthe many systems and their subfunctions.Only when the correct function is known can afault be evaluated.

Function descriptions

The necessary information can be foundpredominantly in the SBT functiondescriptions and in the Participant's Manualsof the Aftersales Academy. In conjunction withthe vehicle, the technician can build up apicture of the correct mode of operation of thevehicle systems.

On top of the function descriptions, thefollowing information systems are available:

• BMW Diagnosis System (DISplus and GT1)

• Technical Information System (TIS)

• Product and Measures ManagementAftersales (Puma).

BMW Diagnosis System

As well as their functions as diagnostic testerand measuring equipment, the BMW DISplusand GT1 diagnosis systems are designed tocommunicate and convey information. Asfrom the E65 mainly background informationand special knowledge for diagnosticpurposes are described in the functiondescriptions relating to the relevant systems.

As well as the function descriptions, there isthe option of outputting wiring diagrams withall the detailed information and installation andstorage locations of the adapter cables for theelectrical systems in the vehicle.

Technical Information System TIS

The "Technical Information System" offersprimarily technical background information toall subjects covering all aspects of the vehicle.

In addition to repair instructions, it containstightening torques, the latest ServiceInformation bulletins and much more. Thecorresponding vehicle type can be selected byselecting a model or entering the vehicleidentification number.

Puma

The Puma online platform (Product andMeasures Management Aftersales) providesusers online in no time at all with currentproblems and how to solve them. Even in thecase of systems in the vehicle with poordiagnostic capabilities, figures based oncolleagues' experience can greatly simplifytroubleshooting.

All the information systems together provide astrong foundation for efficient repair anddiagnosis work. The function and operation ofthe systems are designed to be as intuitive aspossible and therefore require hardly anyexplanation.

A detailed description and operatinginstructions can be found in the SIP "Problemand Measures Management in Aftersales". It isessential to have worked through this SIP tobe able to attend this seminar.

In relation to the basic functions described inthe SIP, the following improvements havebeen made above all in the categorization offault symptoms:

1

9

1. Structurally improved fault pattern/symptom selection

The most important new features are:

• Separate classification of navigationsystems into High and Low navigation

• Division of telephone fault patterns/symptoms based on optional extrasthrough creation of Cordless KeypadHandset, Universal Charging andHandsfree Kit and TCU telephones

• Grouping of chassis control systems underthe "Chassis systems" fault location

• Combination of control display (CID) andmonitor into "Display/Monitor", of DSP andTopHifi into "Option 677/DSP/TopHifi" andof CD changer and MMC into "CD/DVDChanger"

• Additions for E87 and E64

• Creation of a new "Services" section for alltelematics and online services

• Creation of CIP with separate classificationinto programming, coding, CKM and therelevant control units

• Corrections, such as deletion of multipleentries and rectifications of the allocation offault location and fault type

• Additions to already existing fault patterns/symptoms, e.g. for diagnosis, airbag, etc.

• Omission of the "Component information"fault type since this is no longer requiredwith the separate finding categoriza

2. Extended Search

It is possible under "Extended Search" toenter repeatedly the location and type ofdetection as well as main group/subgroup. It isthus possible to search for several paths,thereby increasing the possibility of finding thesought-after measure. The E-Series, theengine and the body are as before repeatedlyselectable and deselectable with the Ctrl key.

2

Dieser Text muss hier stehen, damit die Seite vom API-Client nicht gelöscht wird.Dieser Text ist notwendig, damit die Seite nicht quergestellt wird.!

BMW ServiceAftersales Training

D-80788 München

Fax +49 89 382-34450
:

BMW GT1-MANUALen

Documents

Transcript of BMW GT1-MANUALen