August 31, 2017
This Tech support fromobdexpress.co.uk:
Ford VCM IDS 3with error messages "not VCI†and "not licenseâ€
Not connected to VCI (No VCIs Detected)
IDS software - Productionlicensenot found
An active IDS software license is not found and is required for vehicle communications.
Solved!!
Go toFVDI2 Quick Start, then IDS Ford,
Works like a charm.
Note: you are supposed to update IDS software before using FVDI2 Quick Start
Terminator Software V4.6 Download Link:
ford ids v106.01 software download free: (only tested with VCM IDS 3 )
mazdav106 software download free: (only tested with VCM IDS 3 )
(Source:http://blog.obdexpress.co.uk/2017/08/31/solved-vcm-ids-3-not-connected-to-vci-license-not-found/)
Posted by: OBDexpress.co.uk at
09:36 AM
| No Comments
| Add Comment
Post contains 113 words, total size 9 kb.
August 29, 2017
Do
Perhaps not. Ktag should be a better choice to read Siemens/Delphi in BOOT mode.
ECU programming
Withkessv2 master:
I tried it on
I
the Kees V2 said to me: "Wake Up Error".
I have read about this error and there are solutions about "Format the TF Card" inside or similar.
Note: This Kess V2 comes from a good and reliable seller, so maybe the problem is that this ECU cannot be read by OBd2
It is
This is the car list
I tried picking
use this cable:
Read almost all the posts related to this topic. Nowiconfirmedproblemis
my
This is the Right side :
The left side (viewing
The ECU is located under the A/C Filter. At the Left of the Hood.
See pictures:
It is a DELPHI like
" data-blogger-escaped-data-mce-src="http://blog.obdexpress.co.uk/wp-content/uploads/2017/08/ktag-kess-read-w211-delphi-dcm-3.2-8-450x600.jpg" data-blogger-escaped-style="height: auto; max-width: 100%;" data-orig-src="http://blog.obdexpress.co.uk/wp-content/uploads/2017/08/ktag-kess-read-w211-delphi-dcm-3.2-8-450x600.jpg" height="600" src="https://images-blogger-opensocial.googleusercontent.com/gadgets/proxy?url=http%3A%2F%2Fblog.obdexpress.co.uk%2Fwp-content%2Fuploads%2F2017%2F08%2Fktag-kess-read-w211-delphi-dcm-3.2-8-450x600.jpg&container=blogger&gadget=a&rewriteMime=image%2F*" width="450" />
Engine sticker:
Siemens/Delphi can be done
It’sdelphidcm3.2ecu.Need BDM
This is whatifound, aboutdelphidcm3.2ecuwith aBDM100 programmer
Source from :
Posted by: OBDexpress.co.uk at
09:54 AM
| No Comments
| Add Comment
Post contains 268 words, total size 23 kb.
August 24, 2017
I have thekess5.017interface, very fast shipping by DHL after 3
I tested for this moment
Berlingo 9HX:onlyreadIDfromengineandworks ok
PSA BoschEDC
Skoda Octavia 1.9AXR
BMW
BMW
Ford Mondeo
K-line and CANboth OK
VW
2008Sprinters withEdc16:
....
Works well
I also confirmed some features, as they stated:
- KESS V5.017 can support car/truck/tractor/Bike...support both 12V and 24V vehicle..and newer vehicles
2.KESS V5.017 has no token limited for all compatible vehicles
3.KESS V5.017 has no grey protocols ..full protocols such as EDC17/k-line/DSG/DQ200 DQ250 DQ500 Gearbox/ST10....
4.KESS V5.017 read and write ECUs via OBD easily, Do not need to disassemble ECU...more user-friendlythan KTAG V7.020
5. KESS V5.017 doconnectinternet ...Online operation..no need disable thenetworkconnectiononpurpose before use
All in all,
It works well and it is a cheap Clone in China.If people want to rework, they can buy some Murata Filters.
You can
Attachkess5.017pcbrework.. wish it helps. I haven't tried on any real car
Before rework
Reworking
Worked with the software
Src:
Posted by: OBDexpress.co.uk at
09:14 AM
| No Comments
| Add Comment
Post contains 246 words, total size 19 kb.
August 23, 2017
It’s about Ford ECU reading/writing, with help ofKess V2 5.017 CarListDownload:
|
Model |
Type |
Version |
Engine code |
KW |
HP |
Fuel |
MY |
ECU |
Kess protocol |
Ktag ground |
Ktag protocol |
||
|
Ford |
B-Max |
(I) |
1000 12V |
66 |
90 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
|
Ford |
B-Max |
(I) |
1000 EcoBoost |
M1JA |
88 |
120 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
B-Max |
(I) |
1000 EcoBoost |
SFJA |
74 |
100 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
B-Max |
(I) |
1400 16V |
66 |
90 |
Petrol |
2013 |
SIEMENS |
EMS2102 |
130 |
|||
|
Ford |
C-Max |
(I) |
1600 TDCi |
G8DA |
80 |
110 |
Diesel |
2007 |
BOSCH |
EDC16C34 |
77 |
Bdm(MPC5xx) |
60 |
|
Ford |
C-Max |
(I) |
1600 TDCi |
GPDA |
66 |
90 |
Diesel |
2007 |
BOSCH |
EDC16C3 |
72 |
Bdm(MPC5xx) |
11 |
|
Ford |
C-Max |
(I) |
1800 TDCi |
KKDA |
85 |
115 |
Diesel |
2007 |
SIEMENS |
SID202 |
76 |
||
|
Ford |
C-Max |
(I) |
1800 TDCi |
KKDA |
85 |
115 |
Diesel |
2007 |
SIEMENS |
SID803A |
76 |
Bdm(MPC5xx) |
78 |
|
Ford |
C-Max |
(I) |
2000 TDCi |
G6DA |
100 |
136 |
Diesel |
2007 |
SIEMENS |
SID202 |
76 |
||
|
Ford |
C-Max |
(I) |
2000 TDCi |
G6DA |
100 |
136 |
Diesel |
2007 |
SIEMENS |
SID803 |
75 |
||
|
Ford |
C-Max |
(I) |
2000 TDCi |
G6DA |
100 |
136 |
Diesel |
2007 |
SIEMENS |
SID803A |
76 |
Bdm(MPC5xx) |
78 |
|
Ford |
C-Max |
(II) |
1000 EcoBoost |
M1DA |
92 |
125 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
C-Max |
(II) |
1000 EcoBoost |
M2DA |
73 |
100 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
C-Max |
(II) |
1600 EcoBoost |
JQDA |
110 |
150 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1200 |
|
Ford |
C-Max |
(II) |
1600 EcoBoost |
JQDA |
110 |
150 |
Petrol |
2013 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
C-Max |
(II) |
1600 TDCi |
T1DA |
85 |
115 |
Diesel |
2011 |
SIEMENS |
SID807 |
Boot(Tricore) |
1178 |
|
|
Ford |
C-Max |
(II) |
1600 TDCi |
T1DA |
85 |
115 |
Diesel |
2011 |
SIEMENS |
SID807 |
404 |
Boot(Tricore) |
1511 |
|
Ford |
C-Max |
(II) |
1600 TDCi |
T3DA |
70 |
95 |
Diesel |
2011 |
SIEMENS |
SID807 |
Boot(Tricore) |
1178 |
|
|
Ford |
C-Max |
(II) |
1600 TDCi |
T3DA |
70 |
95 |
Diesel |
2011 |
SIEMENS |
SID807 |
404 |
Boot(Tricore) |
1511 |
|
Ford |
C-Max |
(II) |
2000 TDCi |
TXDB |
103 |
140 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
Ford |
C-Max |
(II) |
2000 TDCi |
TXDB |
120 |
163 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
Ford |
C-Max |
(III) |
2000 TDCi |
110 |
150 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
C-Max |
(III) |
2000 TDCi |
125 |
170 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Contour |
2000 Zetec |
97 |
125 |
Petrol |
1996 |
FORD |
EEC-V |
242 |
||||
|
Ford |
Contour |
2500 V6 Duratec |
125 |
170 |
Petrol |
1996 |
FORD |
EEC-V |
242 |
||||
|
Ford |
Contour |
(II) |
2500 V6 Duratec |
145 |
195 |
Petrol |
1998 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Contour |
(II) |
2500 V6 Duratec |
149 |
200 |
Petrol |
1999 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Cougar |
2000 16V |
94 |
128 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Cougar |
2500 V6 |
123 |
167 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Courier |
1400 16V |
66 |
90 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Courier |
1600 16V |
76 |
103 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Crow Victoria |
4600 V8 |
162 |
220 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Crow Victoria |
4600 V8 |
165 |
224 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Crow Victoria |
4600 V8 |
176 |
239 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Crow Victoria |
4600 V8 |
184 |
250 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
EcoSport |
1000 Zetec Supercharged |
70 |
95 |
Petrol |
2004 |
FORD |
EEC-VI |
233 |
||||
|
Ford |
EcoSport |
1400 TDCi |
50 |
68 |
Diesel |
2004 |
SIEMENS |
SID802/SID804 |
66 |
||||
|
Ford |
EcoSport |
1500 Ti-VCT |
UEJ |
82 |
112 |
Petrol |
2013 |
CONTINENTAL |
EMS2211 |
Boot(Tricore) |
1749 |
||
|
Ford |
EcoSport |
1600 Zetec |
82 |
111 |
Petrol |
2004 |
FORD |
EEC-V |
242 |
||||
|
Ford |
EcoSport |
2000 Duratec |
107 |
145 |
Petrol |
2004 |
FORD |
EEC-VI |
233 |
||||
|
Ford |
EcoSport |
(II) |
1500 TDCi |
ENUG |
67 |
91 |
Diesel |
2013 |
BOSCH |
EDC17C10 |
486 |
Boot(Tricore) |
1197 |
|
Ford |
Edge |
2000 TDCi |
132 |
180 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
Jtag(Nexus) |
300 |
||
|
Ford |
Edge |
2000 TDCi Biturbo |
154 |
210 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
||||
|
Ford |
Endeavour |
2500 TDCi |
105 |
143 |
Diesel |
BOSCH |
EDC16C7-7 |
289 |
Bdm(MPC5xx) |
11 |
|||
|
Ford |
Endeavour |
3000 TDCi |
115 |
156 |
Diesel |
BOSCH |
EDC16C7-7 |
289 |
Bdm(MPC5xx) |
11 |
|||
|
Ford |
Escape |
2000 16V |
85 |
115 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Escape |
2000 EcoBoost |
TPBA |
176 |
240 |
Petrol |
2013 |
BOSCH |
MED17.2.2 |
414 |
Boot(Tricore) |
1200 |
|
|
Ford |
Escape |
2300 16V |
113 |
153 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Escape |
3000 V6 |
147 |
200 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Escort IV |
1600 8V |
66 |
90 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Escort IV |
1800 16V |
85 |
115 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
E-series |
4600 V8 |
188 |
255 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
E-series |
5400 V8 |
188 |
255 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
E-series |
6800 V10 |
224 |
305 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
E-series |
7300 TD |
POWERSTROKE |
202 |
275 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Esplorer |
(V) |
2000 T 16V |
Ecoboost |
176 |
240 |
Petrol |
2011 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Everest |
2200 16v TDCi |
ZSD-422 |
118 |
160 |
Diesel |
2015 |
SIEMENS |
SID209 |
Boot(Tricore) |
1510 |
||
|
Ford |
Everest |
3000 TDCi |
115 |
156 |
Diesel |
BOSCH |
EDC16C7-7 |
289 |
Bdm(MPC5xx) |
11 |
|||
|
Ford |
Everest |
3200 20v TDCi |
P5AT |
143 |
194 |
Diesel |
2015 |
SIEMENS |
SID209 |
Boot(Tricore) |
1510 |
||
|
Ford |
Excursion |
7300 TD |
POWERSTROKE |
184 |
250 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Expedition |
5400 V8 |
221 |
300 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
Explorer |
4000 V6 |
154 |
210 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Explorer |
4600 V8 |
215 |
292 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
Explorer |
5000 V8 |
158 |
215 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
F-150 |
4200 V6 |
149 |
202 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
F-150 |
4600 V8 |
182 |
248 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
F-150 |
5400 V8 |
221 |
300 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
F-150 |
7300 TD |
POWERSTROKE |
184 |
250 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
F-250 |
3,9L 4BT |
Cummins ISBe |
147 |
200 |
Diesel |
2008 |
BOSCH |
EDC7C1/C2 |
221 |
Bdm(MPC5xx) |
31 |
|
|
Ford |
F-250 |
(SUPERDUTY) |
5400 V8 |
221 |
300 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
F-250 |
(SUPERDUTY) |
6700 V8 |
298 |
400 |
Diesel |
BOSCH |
EDC17CP05 |
Boot(Tricore) |
1197 |
|||
|
Ford |
F-250 |
(SUPERDUTY) |
6800 V10 |
266 |
362 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
F-350 |
(SUPERDUTY) |
5400 V8 |
221 |
300 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
F-350 |
(SUPERDUTY) |
6400 V8 |
260 |
350 |
Diesel |
2008 |
SIEMENS |
SID 902 |
Bdm(MPC5xx) |
577 |
||
|
Ford |
F-350 |
(SUPERDUTY) |
6800 V10 |
266 |
362 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
F-450 |
(SUPERDUTY) |
5400 V8 |
221 |
300 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
F-450 |
(SUPERDUTY) |
6800 V10 |
266 |
362 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
Fiesta |
(IV) |
1242 Zetec |
DHA |
55 |
75 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
||
|
Ford |
Fiesta |
(IV) |
1400 Zetec |
FHA |
66 |
90 |
Petrol |
1999 |
FORD |
EEC-V |
242 |
||
|
Ford |
Fiesta |
(IV) |
1600 16V |
L1 |
76 |
103 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
||
|
Ford |
Fiesta |
(V) |
1242 Duratec |
M7JA |
51 |
70 |
Petrol |
2003 |
SIEMENS |
SIM210 |
67 |
||
|
Ford |
Fiesta |
(V) |
1242 Zetec |
FUJA |
55 |
75 |
Petrol |
2002 |
SIEMENS |
SIM19 |
392 |
||
|
Ford |
Fiesta |
(V) |
1300 Duratec |
A9JA |
51 |
70 |
Petrol |
2001 |
FORD |
EEC-V |
242 |
||
|
Ford |
Fiesta |
(V) |
1300 Duratec |
BAJA |
44 |
60 |
Petrol |
2001 |
FORD |
EEC-V |
242 |
||
|
Ford |
Fiesta |
(V) |
1400 TDCi |
KVJA |
51 |
70 |
Diesel |
2010 |
BOSCH |
EDC17C10 |
486 |
Boot(Tricore) |
1197 |
|
Ford |
Fiesta |
(V) |
1400 TDCi Duratorq |
F6JA |
50 |
68 |
Diesel |
2001 |
SIEMENS |
SID802/SID804 |
66 |
||
|
Ford |
Fiesta |
(V) |
1400 Zetec-S |
FXJA |
59 |
80 |
Petrol |
2001 |
SIEMENS |
SIM210 |
67 |
||
|
Ford |
Fiesta |
(V) |
1600 Zetec-S |
FYJA |
74 |
100 |
Petrol |
2001 |
SIEMENS |
SIM210 |
67 |
||
|
Ford |
Fiesta |
(V) |
2000 ST 150 Duratec-ST |
N4JB |
110 |
150 |
Petrol |
2005 |
FORD |
EEC-VI |
233 |
||
|
Ford |
Fiesta |
(VI) |
1000 8V |
48 |
65 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Fiesta |
(VI) |
1000 8V |
Supercharger |
70 |
95 |
Petrol |
FORD |
EEC-VI |
233 |
|||
|
Ford |
Fiesta |
(VI) |
1000 EcoBoost |
M1JE |
92 |
125 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Fiesta |
(VI) |
1000 EcoBoost |
SFJA |
73 |
100 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Fiesta |
(VI) |
1242 Duratec |
SNJA |
60 |
82 |
Petrol |
2008 |
SIEMENS |
EMS |
130 |
||
|
Ford |
Fiesta |
(VI) |
1400 TDCi Duratorq |
F6JA |
50 |
68 |
Diesel |
2008 |
SIEMENS |
SID206 |
129 |
||
|
Ford |
Fiesta |
(VI) |
1400 TDCi Duratorq |
F6JA |
50 |
68 |
Diesel |
2009 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
Ford |
Fiesta |
(VI) |
1400 Ti-VCT |
71 |
96 |
Petrol |
2010 |
SIEMENS |
EMS2205 |
Boot(Tricore) |
1663 |
||
|
Ford |
Fiesta |
(VI) |
1400 Zetec-S |
SPJA |
71 |
96 |
Petrol |
2008 |
SIEMENS |
EMS |
130 |
||
|
Ford |
Fiesta |
(VI) |
1500 TDCi |
UGJ |
55 |
75 |
Diesel |
2012 |
BOSCH |
EDC17C10 |
486 |
Boot(Tricore) |
1698 |
|
Ford |
Fiesta |
(VI) |
1600 Duratec TI-VCT |
HXJA |
88 |
120 |
Petrol |
2008 |
SIEMENS |
EMS |
130 |
||
|
Ford |
Fiesta |
(VI) |
1600 ST |
JQDA |
135 |
182 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Fiesta |
(VI) |
1600 TDCi |
TZJ |
70 |
95 |
Diesel |
2012 |
BOSCH |
EDC17C10 |
486 |
Boot(Tricore) |
1197 |
|
Ford |
Fiesta |
(VI) |
1600 TDCi Duratorq |
HHJC |
66 |
90 |
Diesel |
2008 |
BOSCH |
EDC16C34-2.20 |
77 |
Bdm(MPC5xx) |
60 |
|
Ford |
Fiesta |
(VI) |
1600 Ti-VCT |
88 |
120 |
Petrol |
2010 |
SIEMENS |
EMS2205 |
Boot(Tricore) |
1663 |
||
|
Ford |
Focus |
(I) |
1400 Zetec |
FXDA |
55 |
75 |
Petrol |
1998 |
FORD |
EEC-V |
242 |
||
|
Ford |
Focus |
(I) |
1600 Zetec |
FYDA |
74 |
100 |
Petrol |
1998 |
FORD |
EEC-V |
242 |
||
|
Ford |
Focus |
(I) |
1800 Endura-DI |
BHDA |
55 |
75 |
Diesel |
1999 |
FORD |
EEC-V |
171 |
||
|
Ford |
Focus |
(I) |
1800 Endura-DI |
C9DA |
66 |
90 |
Diesel |
1998 |
FORD |
EEC-V |
171 |
||
|
Ford |
Focus |
(I) |
1800 TDCi Duratorq |
F9DA |
85 |
115 |
Diesel |
2001 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|
Ford |
Focus |
(I) |
1800 TDCi Duratorq |
FFDA |
74 |
100 |
Diesel |
2002 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|
Ford |
Focus |
(I) |
1800 Zetec |
EYDB |
85 |
115 |
Petrol |
1998 |
FORD |
EEC-V |
242 |
||
|
Ford |
Focus |
(I) |
2000 Zetec |
EDDF |
96 |
130 |
Petrol |
1998 |
FORD |
EEC-V |
242 |
||
|
Ford |
Focus |
(II) |
1600 Duratec |
74 |
100 |
Petrol |
2004 |
SIEMENS |
SIM28 |
67 |
|||
|
Ford |
Focus |
(II) |
1600 Duratec |
85 |
115 |
Petrol |
2004 |
FORD |
EEC-VI |
233 |
|||
|
Ford |
Focus |
(II) |
1600 Duratec |
85 |
115 |
Petrol |
2004 |
SIEMENS |
SIM29 |
67 |
|||
|
Ford |
Focus |
(II) |
1600 Duratec Ti-VCT |
HXDA |
85 |
115 |
Petrol |
2004 |
SIEMENS |
EMS |
130 |
||
|
Ford |
Focus |
(II) |
1600 TDCi |
G8DA |
81 |
110 |
Diesel |
2004 |
BOSCH |
EDC16C3 |
72 |
Bdm(MPC5xx) |
11 |
|
Ford |
Focus |
(II) |
1600 TDCi |
G8DA |
81 |
110 |
Diesel |
2004 |
BOSCH |
EDC16C34 |
77 |
Bdm(MPC5xx) |
60 |
|
Ford |
Focus |
(II) |
1600 TDCi |
HHDA |
66 |
90 |
Diesel |
2005 |
BOSCH |
EDC16C34 |
77 |
Bdm(MPC5xx) |
60 |
|
Ford |
Focus |
(II) |
1800 Duratec |
QQDB |
92 |
125 |
Petrol |
2006 |
FORD |
EEC-VI |
233 |
||
|
Ford |
Focus |
(II) |
1800 Flexifuel |
Q7DA |
92 |
125 |
Petrol |
2006 |
SIEMENS |
SIM29 |
67 |
||
|
Ford |
Focus |
(II) |
1800 TDCi |
KKDA |
85 |
115 |
Diesel |
2002 |
SIEMENS |
SID202 |
76 |
||
|
Ford |
Focus |
(II) |
1800 TDCi |
KKDA |
85 |
115 |
Diesel |
2008 |
SIEMENS |
SID803A |
76 |
Bdm(MPC5xx) |
78 |
|
Ford |
Focus |
(II) |
2000 16V |
97 |
132 |
Petrol |
2004 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Focus |
(II) |
2000 16V |
103 |
140 |
Petrol |
2004 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Focus |
(II) |
2000 Duratec |
AODA |
107 |
145 |
Petrol |
2004 |
FORD |
EEC-VI |
233 |
||
|
Ford |
Focus |
(II) |
2000 TDCi |
G6DA |
100 |
136 |
Diesel |
2004 |
SIEMENS |
SID803 |
75 |
||
|
Ford |
Focus |
(III) |
1.6 |
NGD |
77 |
105 |
Petrol |
2011 |
CONTINENTAL |
EMS2204 |
Boot(Tricore) |
1749 |
|
|
Ford |
Focus |
(III) |
1.6 Ti-VCT |
PND |
92 |
125 |
Petrol |
2011 |
CONTINENTAL |
EMS2204 |
Boot(Tricore) |
1749 |
|
|
Ford |
Focus |
(III) |
1000 EcoBoost |
M1DA |
92 |
125 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Focus |
(III) |
1000 EcoBoost |
M2DA |
88 |
100 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Focus |
(III) |
1600 EcoBoost |
JQDA |
110 |
150 |
Petrol |
2011 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1200 |
|
Ford |
Focus |
(III) |
1600 EcoBoost |
JQDA |
110 |
150 |
Petrol |
2013 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Focus |
(III) |
1600 TDCi |
T1DA |
85 |
115 |
Diesel |
2011 |
SIEMENS |
SID807 |
404 |
Boot(Tricore) |
1511 |
|
Ford |
Focus |
(III) |
1600 TDCi |
T3DA |
70 |
95 |
Diesel |
2011 |
SIEMENS |
SID807 |
404 |
Boot(Tricore) |
1511 |
|
Ford |
Focus |
(III) |
2000 TDCi |
TXDB |
120 |
163 |
Diesel |
2011 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
Ford |
Focus |
(IV) |
2000 TDCi |
110 |
150 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Focus |
(IV) |
2000 TDCi |
136 |
185 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Focus RS |
(I) |
2000 RS |
HMDA |
158 |
215 |
Petrol |
2002 |
FORD |
EEC-V |
242 |
||
|
Ford |
Focus RS |
(II) |
2500 Duratec RS |
JZDA |
224 |
305 |
Petrol |
2009 |
BOSCH |
ME9 |
272 |
Bdm(MPC5xx) |
76 |
|
Ford |
Focus RS |
(II) |
2500 RS500 |
JZDA |
257 |
350 |
Petrol |
2010 |
BOSCH |
ME9 |
272 |
Bdm(MPC5xx) |
76 |
|
Ford |
Focus ST |
(I) |
2000 ST170 |
ALDA |
127 |
173 |
Petrol |
2002 |
FORD |
EEC-V |
242 |
||
|
Ford |
Focus ST |
(II) |
2500 Duratec ST |
HYDA |
166 |
225 |
Petrol |
2005 |
BOSCH |
ME9 |
272 |
Bdm(MPC5xx) |
76 |
|
Ford |
Focus ST |
(III) |
2000 ST EcoBoost |
R9DA |
184 |
250 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1200 |
|
Ford |
Freda |
2500 TD |
N/A |
109 |
Diesel |
2001 |
MITSUBISHI |
E6T0xx |
Jtag(Mitsubishi) |
318 |
|||
|
Ford |
Fusion |
(I) |
1400 16V |
FXJA |
59 |
80 |
Petrol |
2002 |
SIEMENS |
SIM210 |
67 |
||
|
Ford |
Fusion |
(I) |
1400 TDCi |
F6JA |
50 |
68 |
Diesel |
2002 |
SIEMENS |
SID802 |
66 |
||
|
Ford |
Fusion |
(I) |
1400 TDCi |
F6JA |
50 |
68 |
Diesel |
2002 |
SIEMENS |
SID804 |
66 |
||
|
Ford |
Fusion |
(I) |
1600 16V |
FYJA |
74 |
100 |
Petrol |
2002 |
SIEMENS |
SIM210 |
67 |
||
|
Ford |
Fusion |
(I) |
1600 TDCi |
HHJA |
66 |
90 |
Diesel |
2004 |
BOSCH |
EDC16C34 |
77 |
Bdm(MPC5xx) |
60 |
|
Ford |
Fusion |
(I) |
2300 16V |
118 |
161 |
Petrol |
2005 |
FORD |
EEC-VI |
233 |
|||
|
Ford |
Fusion |
(I) |
3000 V6 |
163 |
224 |
Petrol |
2005 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Fusion |
(I) |
3000 V6 |
176 |
240 |
Petrol |
2009 |
CONTINENTAL |
JDS0 |
Bdm(MPC5xx) |
343 |
||
|
Ford |
Fusion |
(II) |
2000 EcoBoost |
TPBA |
176 |
240 |
Petrol |
2013 |
BOSCH |
MED17.2.2 |
414 |
Boot(Tricore) |
1200 |
|
Ford |
Galaxy |
1800 TDCi |
85 |
115 |
Diesel |
SIEMENS |
SID202 |
76 |
|||||
|
Ford |
Galaxy |
1800 TDCi |
85 |
115 |
Diesel |
SIEMENS |
SID803A |
76 |
Bdm(MPC5xx) |
78 |
|||
|
Ford |
Galaxy |
1900 TDI |
66 |
90 |
Diesel |
BOSCH |
EDC15P+ |
10 |
|||||
|
Ford |
Galaxy |
1900 TDI |
81 |
110 |
Diesel |
BOSCH |
EDC15P+ |
10 |
|||||
|
Ford |
Galaxy |
1900 TDI |
85 |
115 |
Diesel |
BOSCH |
EDC15P+ |
10 |
|||||
|
Ford |
Galaxy |
1900 TDI |
96 |
130 |
Diesel |
BOSCH |
EDC15P+ |
10 |
|||||
|
Ford |
Galaxy |
1900 TDI |
110 |
150 |
Diesel |
BOSCH |
EDC15P+ |
10 |
|||||
|
Ford |
Galaxy |
2000 16V |
85 |
115 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Galaxy |
2000 TDCI |
100 |
136 |
Diesel |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|||
|
Ford |
Galaxy |
2200 TDCI |
125 |
170 |
Diesel |
2008 |
BOSCH |
EDC16CP39-6.40 |
225 |
||||
|
Ford |
Galaxy |
2300 16V |
103 |
140 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Galaxy |
2800 V6 24V |
176 |
240 |
Petrol |
BOSCH |
ME7.X 8Mbit |
39 |
|||||
|
Ford |
Galaxy |
(II) |
1600 EcoBoost |
JQDA |
120 |
160 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1200 |
|
Ford |
Galaxy |
(II) |
1800 TDCi |
FFWA |
74 |
100 |
Diesel |
2006 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
Ford |
Galaxy |
(II) |
1800 TDCi |
QYWA |
92 |
125 |
Diesel |
2006 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
Ford |
Galaxy |
(II) |
2000 16V |
TBWA |
107 |
145 |
Petrol |
2006 |
FORD |
EEC-VI |
233 |
||
|
Ford |
Galaxy |
(II) |
2000 TDCi |
96 |
130 |
Diesel |
2006 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
Galaxy |
(II) |
2000 TDCi |
103 |
140 |
Diesel |
2006 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
Galaxy |
(II) |
2000 TDCi |
103 |
140 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
|
Ford |
Galaxy |
(II) |
2000 TDCi |
120 |
163 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
|
Ford |
Galaxy |
(II) |
2200 TDCi |
126 |
172 |
Diesel |
2010 |
BOSCH |
EDC17CP42 |
Boot(Tricore) |
1197 |
||
|
Ford |
Galaxy |
(III) |
2000 TDCi |
110 |
150 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
Jtag(Nexus) |
300 |
|
|
Ford |
Galaxy |
(III) |
2000 TDCi |
132 |
180 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
Jtag(Nexus) |
300 |
|
|
Ford |
Galaxy |
(III) |
2000 TDCi Biturbo |
154 |
210 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Ka |
(I) |
1000 8V |
48 |
65 |
Petrol |
1999 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Ka |
(I) |
1000 8V |
ZH10JRB |
38 |
52 |
Petrol |
1997 |
FORD |
EEC-V |
242 |
||
|
Ford |
Ka |
(I) |
1300 8V |
A9A |
51 |
69 |
Petrol |
2002 |
FORD |
EEC-V |
242 |
||
|
Ford |
Ka |
(I) |
1300 8V |
BAA |
44 |
60 |
Petrol |
1996 |
FORD |
EEC-V |
242 |
||
|
Ford |
Ka |
(I) |
1300 8V |
JJB |
37 |
50 |
Petrol |
1996 |
FORD |
EEC-V |
242 |
||
|
Ford |
Ka |
(I) |
1600 16V |
CDB |
70 |
95 |
Petrol |
2003 |
SIEMENS |
SIM24 |
67 |
||
|
Ford |
Ka |
(I) |
1600 16V |
CDB |
70 |
95 |
Petrol |
2003 |
SIEMENS |
SIM42 |
67 |
||
|
Ford |
Ka |
(II) |
1300 TDCi |
FD4 |
55 |
75 |
Diesel |
2008 |
MAGNETI MARELLI |
MJD6F3 |
137 |
Bdm(MPC5xx) |
85 |
|
Ford |
Ka |
(II) |
1300 TDCi |
FD4 |
55 |
75 |
Diesel |
2008 |
MAGNETI MARELLI |
MJD8DF |
296 |
Jtag(Nexus) |
303 |
|
Ford |
Kuga |
1600 EcoBoost |
JQDA |
110 |
150 |
Petrol |
2011 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1200 |
|
|
Ford |
Kuga |
2000 EcoBoost |
TPBA |
176 |
240 |
Petrol |
2013 |
BOSCH |
MED17.2.2 |
414 |
Boot(Tricore) |
1200 |
|
|
Ford |
Kuga |
2000 TDCi |
G6DG |
100 |
136 |
Diesel |
2008 |
SIEMENS |
SID803A |
76 |
Bdm(MPC5xx) |
78 |
|
|
Ford |
Kuga |
2000 TDCi |
TXDA |
120 |
163 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
|
Ford |
Kuga |
2000 TDCi |
UFDA |
103 |
140 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
|
Ford |
Kuga |
2000 TDCi |
UKDA |
100 |
136 |
Diesel |
2008 |
SIEMENS |
SID202 |
76 |
|||
|
Ford |
Kuga |
2500 T Duratec |
HYDB |
147 |
200 |
Petrol |
2009 |
BOSCH |
ME9 |
272 |
Bdm(MPC5xx) |
76 |
|
|
Ford |
Kuga |
(II) |
2000 TDCi |
88 |
120 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Kuga |
(II) |
2000 TDCi |
110 |
150 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Kuga |
(II) |
2000 TDCi |
132 |
180 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Maverick |
3000 V6 |
149 |
203 |
Petrol |
FORD |
EEC-VI |
233 |
|||||
|
Ford |
Mondeo |
(II) |
1600 16V |
66 |
90 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Mondeo |
(II) |
1800 16V |
66 |
90 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Mondeo |
(II) |
1800 16V |
92 |
125 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Mondeo |
(II) |
1800 TDDI |
85 |
115 |
Diesel |
FORD |
EEC-V |
171 |
||||
|
Ford |
Mondeo |
(II) |
1800 TDDI |
96 |
130 |
Diesel |
FORD |
EEC-V |
171 |
||||
|
Ford |
Mondeo |
(II) |
1800 TDDI |
RFN |
66 |
90 |
Diesel |
1996 |
FORD |
EEC-V |
171 |
||
|
Ford |
Mondeo |
(II) |
2000 16V |
96 |
130 |
Petrol |
FORD |
EEC-V |
242 |
||||
|
Ford |
Mondeo |
(II) |
2000 TDCI |
85 |
115 |
Diesel |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
||
|
Ford |
Mondeo |
(II) |
2000 TDCI |
85 |
115 |
Diesel |
FORD |
EEC-V |
242 |
||||
|
Ford |
Mondeo |
(II) |
2000 TDCI |
96 |
130 |
Diesel |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
||
|
Ford |
Mondeo |
(II) |
2000 TDCI |
96 |
130 |
Diesel |
DELPHI |
MPC 555 + 29F400 |
171 |
Bdm(MPC5xx) |
20 |
||
|
Ford |
Mondeo |
(II) |
2000 TDCI |
96 |
130 |
Diesel |
FORD |
EEC-V |
242 |
||||
|
Ford |
Mondeo |
(III) |
2000 16V |
CJBA |
107 |
145 |
Petrol |
2000 |
FORD |
EEC-VI |
233 |
||
|
Ford |
Mondeo |
(III) |
2000 TDCi |
SDBA |
66 |
90 |
Diesel |
2000 |
FORD |
EEC-V |
242 |
||
|
Ford |
Mondeo |
(III) |
2200 TDCi |
QJBA |
114 |
155 |
Diesel |
2004 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|
Ford |
Mondeo |
(III) |
2500 V6 |
LCBD |
125 |
170 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
||
|
Ford |
Mondeo |
(IV) |
1600 EcoBoost |
JTBB |
118 |
160 |
Petrol |
2011 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Mondeo |
(IV) |
1800 TDCi |
QYBA |
92 |
125 |
Diesel |
2007 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
Ford |
Mondeo |
(IV) |
2000 EcoBoost |
TPBA |
176 |
240 |
Petrol |
2010 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1586 |
|
Ford |
Mondeo |
(IV) |
2000 TDCi |
AZBA |
96 |
130 |
Diesel |
2007 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
Ford |
Mondeo |
(IV) |
2000 TDCi |
QXBA |
103 |
140 |
Diesel |
2007 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
Ford |
Mondeo |
(IV) |
2000 TDCi |
QXBA |
103 |
140 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
Ford |
Mondeo |
(IV) |
2000 TDCi |
TXBA |
120 |
163 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
Ford |
Mondeo |
(IV) |
2200 TDCi |
KNBA |
147 |
200 |
Diesel |
2010 |
BOSCH |
EDC17CP42 |
Boot(Tricore) |
1197 |
|
|
Ford |
Mondeo |
(IV) |
2200 TDCi |
Q4BA |
125 |
175 |
Diesel |
2008 |
BOSCH |
EDC16CP39-6.40 |
225 |
||
|
Ford |
Mondeo |
(IV) |
2200 TDCi |
Q4BA |
126 |
175 |
Diesel |
2010 |
BOSCH |
EDC17CP42 |
Boot(Tricore) |
1197 |
|
|
Ford |
Mondeo |
(V) |
1600 TDCi |
85 |
114 |
Diesel |
2014 |
BOSCH |
EDC17C10 |
Boot(Tricore) |
1698 |
||
|
Ford |
Mondeo |
(V) |
2000 TDCi |
110 |
150 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Mondeo |
(V) |
2000 TDCi |
132 |
180 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Mondeo |
(V) |
2000 TDCi Biturbo |
154 |
210 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
Mondeo ST |
(II) |
2500 ST200 Duratec |
SGA |
151 |
205 |
Petrol |
1999 |
FORD |
EEC-V |
242 |
||
|
Ford |
Mondeo ST |
(IV) |
2500 Duratec ST |
HUBA |
162 |
220 |
Petrol |
2007 |
BOSCH |
ME9 |
272 |
Bdm(MPC5xx) |
76 |
|
Ford |
Mustang |
(GT 500) |
4600 V8 |
235 |
319 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
Mustang |
(GT) |
4600 V8 |
221 |
300 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
Mustang |
(GT) |
5400 V8 |
368 |
500 |
Petrol |
FORD |
EEC-VI |
233 |
||||
|
Ford |
Mustang |
(VI) |
2300 16v EcoBoost |
231 |
314 |
Petrol |
2014 |
BOSCH |
MEDG17.0 |
414 |
|||
|
Ford |
Puma |
(I) |
1400 Zetec |
FHD |
66 |
90 |
Petrol |
1997 |
FORD |
EEC-V |
242 |
||
|
Ford |
Puma |
(I) |
1600 Zetec |
L1W |
76 |
103 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
||
|
Ford |
Puma |
(I) |
1700 Zetec |
MHA |
92 |
125 |
Petrol |
1997 |
FORD |
EEC-V |
242 |
||
|
Ford |
Puma ST |
(I) |
1700 ST160 Duratec |
118 |
160 |
Petrol |
1999 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Ranger |
2200 16v TDCi |
GBVAJQJ |
110 |
150 |
Diesel |
2011 |
SIEMENS |
SID208 |
397 |
Boot(Tricore) |
1510 |
|
|
Ford |
Ranger |
2200 16v TDCi |
GBVAJQW |
92 |
125 |
Diesel |
2011 |
SIEMENS |
SID208 |
397 |
Boot(Tricore) |
1510 |
|
|
Ford |
Ranger |
2200 16v TDCi |
ZSD-422 |
88 |
118 |
Diesel |
2015 |
SIEMENS |
SID209 |
Boot(Tricore) |
1510 |
||
|
Ford |
Ranger |
2200 16v TDCi |
ZSD-422 |
118 |
160 |
Diesel |
2015 |
SIEMENS |
SID209 |
Boot(Tricore) |
1510 |
||
|
Ford |
Ranger |
2300 16V |
105 |
143 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Ranger |
2500 |
122 |
166 |
Petrol |
2011 |
CONTINENTAL |
EMS2207 |
Boot(Tricore) |
1749 |
|||
|
Ford |
Ranger |
2500 TD |
N/A |
109 |
Diesel |
2001 |
MITSUBISHI |
E6T0xx |
Jtag(Mitsubishi) |
318 |
|||
|
Ford |
Ranger |
2500 TDCi |
105 |
143 |
Diesel |
BOSCH |
EDC16C7-7 |
289 |
Bdm(MPC5xx) |
11 |
|||
|
Ford |
Ranger |
3000 TD |
POWERSTROKE |
122 |
164 |
Diesel |
SIEMENS |
SID 901 |
236 |
||||
|
Ford |
Ranger |
3000 TDCi |
115 |
154 |
Diesel |
BOSCH |
EDC16C7-7 |
289 |
Bdm(MPC5xx) |
11 |
|||
|
Ford |
Ranger |
3000 V6 |
109 |
148 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Ranger |
3200 16v TDCi |
SAFA |
147 |
200 |
Diesel |
2011 |
SIEMENS |
SID208 |
397 |
Boot(Tricore) |
1510 |
|
|
Ford |
Ranger |
3200 20v TDCi |
P5AT |
147 |
200 |
Diesel |
2015 |
SIEMENS |
SID209 |
Boot(Tricore) |
1510 |
||
|
Ford |
Ranger |
4000 V6 |
152 |
207 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
S-Max |
1800 TDCi |
FFWA |
74 |
100 |
Diesel |
2007 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
S-Max |
1800 TDCi |
QYWA |
92 |
125 |
Diesel |
2007 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
S-Max |
2000 TDCi |
QXWA |
103 |
140 |
Diesel |
2006 |
SIEMENS |
SID206 |
119 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
S-Max |
2200 TDCI |
Q4BA |
125 |
175 |
Diesel |
2008 |
BOSCH |
EDC16CP39 |
225 |
|||
|
Ford |
S-Max |
2500 Duratec ST |
HUWA |
162 |
220 |
Petrol |
2006 |
BOSCH |
ME9 |
272 |
Bdm(MPC5xx) |
76 |
|
|
Ford |
S-Max |
(II) |
1600 EcoBoost |
JQDA |
120 |
160 |
Petrol |
2012 |
BOSCH |
MED17.2 |
414 |
Boot(Tricore) |
1200 |
|
Ford |
S-Max |
(III) |
2000 TDCi |
88 |
120 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
Jtag(Nexus) |
300 |
|
|
Ford |
S-Max |
(III) |
2000 TDCi |
110 |
150 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
Jtag(Nexus) |
300 |
|
|
Ford |
S-Max |
(III) |
2000 TDCi |
132 |
180 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
Jtag(Nexus) |
300 |
|
|
Ford |
S-Max |
(III) |
2000 TDCi Biturbo |
154 |
210 |
Diesel |
2015 |
DELPHI |
DCM6.X |
536 |
|||
|
Ford |
S-Max + |
2000 TDCi |
TXWA |
120 |
163 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
|
Ford |
S-Max + |
2000 TDCi |
TYWA |
85 |
115 |
Diesel |
2010 |
DELPHI |
DCM3.5 |
262 |
Jtag(Nexus) |
302 |
|
|
Ford |
S-Max + |
2200 TDCi |
Q4WA |
126 |
175 |
Diesel |
2010 |
BOSCH |
EDC17CP42 |
Boot(Tricore) |
1197 |
||
|
Ford |
S-Max + |
2200 TDCi |
Q4WA |
150 |
200 |
Diesel |
2011 |
BOSCH |
EDC17CP42 |
Boot(Tricore) |
1197 |
||
|
Ford |
Taurus |
(IV) |
3500 V6 EcoBoost |
272 |
365 |
Petrol |
2010 |
BOSCH |
MEDG9.8.1 |
Bdm(MPC5xx) |
279 |
||
|
Ford |
Thunderbird |
3800 V6 |
107 |
145 |
Petrol |
FORD |
EEC-V |
242 |
|||||
|
Ford |
Transit |
FY |
2000 |
63 |
85 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Transit |
FY |
2000 |
74 |
100 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Transit |
FY |
2000 |
88 |
120 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Transit |
FY |
2000 TDCi |
101 |
137 |
Diesel |
2002 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|
|
Ford |
Transit |
FY |
2000 TDCi |
FIFA |
92 |
125 |
Diesel |
2002 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|
Ford |
Transit |
FY |
2000 TDDi |
92 |
125 |
Diesel |
2000 |
FORD |
EEC-V |
171 |
|||
|
Ford |
Transit |
FY |
2400 |
66 |
90 |
Petrol |
2000 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Transit |
FY |
2400 |
92 |
125 |
Petrol |
2004 |
FORD |
EEC-V |
242 |
|||
|
Ford |
Transit |
FY |
2400 DI |
88 |
120 |
Diesel |
2000 |
FORD |
EEC-V |
171 |
|||
|
Ford |
Transit |
TT9 |
2200 TDCi V347 |
P8FA |
63 |
85 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2200 TDCi V347 |
PGFA |
103 |
140 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2200 TDCi V347 |
QVFA |
81 |
110 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2200 TDCi V347 |
QWFA |
96 |
130 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2200 TDCi V347 |
SRFA |
85 |
115 |
Diesel |
2008 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2400 TDCi V347 |
H9FB |
103 |
140 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2400 TDCi V347 |
JXFA |
85 |
115 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
2400 TDCi V347 |
PHFA |
74 |
100 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TT9 |
3200 TDCi V348 |
SAFA |
147 |
200 |
Diesel |
2006 |
VISTEON |
DCU102 |
113 |
Boot(ST) |
37 |
|
Ford |
Transit |
TTF |
2200 TDCi E5 |
74 |
100 |
Diesel |
2012 |
SIEMENS |
SID208 |
397 |
Boot(Tricore) |
1510 |
|
|
Ford |
Transit |
TTF |
2200 TDCi E5 |
103 |
140 |
Diesel |
2012 |
SIEMENS |
SID208 |
397 |
Boot(Tricore) |
1510 |
|
|
Ford |
Transit Connect |
1800 DI Duratorq |
BHPA |
55 |
75 |
Diesel |
2002 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|
|
Ford |
Transit Connect |
1800 TDCi Duratorq |
55 |
75 |
Diesel |
2002 |
SIEMENS |
SID206 |
76 |
Bdm(MPC5xx) |
82 |
||
|
Ford |
Transit Connect |
1800 TDCi Duratorq |
66 |
90 |
Diesel |
2002 |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
||
|
Ford |
Transit Connect |
1800 TDCi Duratorq |
HCPA |
66 |
90 |
Diesel |
2004 |
SIEMENS |
SID206 |
76 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
Transit Connect |
1800 TDCi Duratorq |
RWPA |
81 |
110 |
Diesel |
2006 |
SIEMENS |
SID206 |
76 |
Bdm(MPC5xx) |
82 |
|
|
Ford |
Transit Tourneo |
1800 TDCi |
66 |
90 |
Diesel |
DELPHI |
MPC 555 |
171 |
Bdm(MPC5xx) |
20 |
|||
|
Ford |
Windstar |
3000 V6 |
147 |
200 |
Petrol |
FORD |
EEC-V |
242 |
|||||
Src:http://blog.obdexpress.co.uk/2017/08/23/kess-v2-5-017-car-list-download-for-ford-ecu-programming/
Posted by: OBDexpress.co.uk at
11:07 AM
| No Comments
| Add Comment
Post contains 3919 words, total size 368 kb.
August 22, 2017
VCM2 clone SP177-C1best price:159euro(08/22/2017-08/31/2017)
the price back to205 euroafter 10 days
VCM2 Wifi SP177-C1 is thebest qualityChina clone
Cloned VCM2 SP177C1 from others: most are more expensive than VCM2 clone inobdexpress.co.uk
VCM2 SP177C1 best price from us: 159 euro
(cheaper price only because this item is listed for promotion, not quality issues)
DO NOT SAY YOU CAN BUY A VCM2 clone AT A BETTER PRICE
QUALITY TALKS. You will get what you pay for.
- What else you should read before your purchase:
VCM2 clone reviews:
VCM2 SP177C or SP177C1 reviews:
VCM2 clone reviews:
VCM2 SP177C or SP177C1 reviews:
Src:
http://blog.obdexpress.co.uk/2017/08/22/vcm2-clone-where-to-buy-at-the-best-price/
Posted by: OBDexpress.co.uk at
03:48 AM
| No Comments
| Add Comment
Post contains 113 words, total size 11 kb.
August 18, 2017
Renault CAN CLIP reviews :
Renault CAN CLIP
ImanagedinstallClip 146 on MacBook Air with VMWARE FUSION and Windows 7 32 bit.
It works well.
I have a
When I connect my CAN Clip, Windows doesn’t recognize the hardware.
Windows can’t detect the unit. But I tested the CAN Clip in
[HELP]how to help Windows (Virtual Machine) to detect
Verify
[VIDEO]how to run Renault CLIP diagnostic software
[NOTE]Renault CAN CLIP what windows can work on?
Renault CAN CLIP windows 7: YES
Renault CAN CLIP windows XP: YES
Renault CAN CLIP windows 8: need luck
Renault CAN CLIP windows 8.1: need luck
Renault CAN CLIP windows 10: need luck
Posted by: OBDexpress.co.uk at
02:41 AM
| No Comments
| Add Comment
Post contains 184 words, total size 14 kb.
August 17, 2017
InObdstar X300Pro3 KeyMaster, Toyota/Lexus software has been updated to Version v31.09, which now can reset Toyota G Key Immo (Key type G chip (72)).
Resetimmobilizerwhen all keys lost situation as in the following steps described below.
Go to the key master with Toyota/Lexus v31.09
Loading…
Initializing…
Authorizing…
Select Immobiliser-> Type 2 (with G 72)-> Resetimmobilizer(all key lost)
Select Immobiliser
Type 2 (with G 72)-
Resetimmobilizer(all key lost)
Switch ignition off, then enter
Switch ignition off and remove the key
Configuring the system…
Switch ignition on, then enter
Configuring the system…
The security light now turns on fixed ( not blinking )
Switch ignition off and remove the key
For make 1 key only, turn on with the new key for 5 seconds, then turn on/off for 5 times until the security light goes off
Turn on with the key
Now the car can start
Successfully reset Toyota G chip
Attachment: photos of G chip reset
Source :
Posted by: OBDexpress.co.uk at
07:48 AM
| No Comments
| Add Comment
Post contains 179 words, total size 7 kb.
August 16, 2017
Here is Free download Mazda IDS v106 software to work
http://pan.baidu.com/s/1qYnwXIk
Password: r5oi
Released by AllscannerVxdiag Vcx Nano
Mazda IDS 106.00 download free
https://mega.nz/#!qgYzRSqR!wRrh4jDELcFVG2YISV6P-_nFKpJKgDChyqo2H-rEGmE
IDS 106.02
https://mega.nz/#!2t5CADKR!dfjtRV2_yC4TFtZkaBXPx_rku3ejY5K97Cz_tVgLyQU
No pass
Shared by SCOTT via the MHH forum
How to setup Vxdiag Vcx Nano Mazda IDS 106:
http://blog.obdexpress.co.uk/2017/07/12/download-install-ford-mazda-ids-106/
How to
Install M-IDS, install latest VCXManger, update the firmware
Why Mazda IDS 106 say it’s 105 version:
You may get that error that installed version is not 106.00 … and even when you run the 106.00installationagain … it says it’s 105.06A.
Just edit reg to match the
Then it should install.
Posted by: OBDexpress.co.uk at
02:25 AM
| No Comments
| Add Comment
Post contains 119 words, total size 13 kb.
August 14, 2017
You don’t need the USB cable or power cord for everyday use. As long as
A 169.254.x.x means the computer has a physical ethernet link, but cannot get an IP address from your router/pc.
1. Set computer to fixed IP address 192.168.0.1
2. Connect USB to VCI POD
3. In web browser, connect to 172.22.22.22
4. Under Network Settings, change radio button from "Obtain an IP address automatically from a DHCP server†to "Use the following IP address and settingsâ€
5. Under IP Settings, change IP Addr: 192.168.0.10
6. Disconnect USB.
7. Plug in Ethernet to VCI POD and computer. Connect
8. In web browser, now connect to 192.168.0.10 (it will also be visible in WiTech)
1. Put empty card into
2. Connect to notebook by LAN not USB
3. Run IE and go to address 172.22.22.22 (or fixed IP address you manually assigned), select software update, and in
a. Look at the folder Program Files\DCC Tools\wiTECH Server\install\bundles vservera.upgrade-
b. On Windows 10 x64: C:\Program Files (x86)\DCC Tools\wiTECH\jserver\install\bundles vservera.upgrade-
Random Tip
Contents of VCI POD SD Card are hidden. Windows cannot mount or view.Linux can!(hint hint)
http://blog.obdexpress.co.uk/2017/08/14/how-to-connect-witech-to-vci-pod-laptop-via-ethernet/
Posted by: OBDexpress.co.uk at
06:31 AM
| No Comments
| Add Comment
Post contains 410 words, total size 8 kb.
August 11, 2017
I solved it this way.
1. OpenTaskmanageran Killall Processes of SDconnect Toolkit(Tkserver.exe, Tktray.exe).
2. Go to DTS install folder and find the folder with the Tkserver.exe in it.
3. Delete this folder.
4. Install SDconnect toolkit from here
Free download SDconnect Toolkit on Mega
encryption key: fQAtu6sTOfHFhfQi5ZObBJr742wGa7_CXuLY33JLhfc
(BTW, you can install this SDConnect toolkit
5. Go to original SDconnect Path (C:\Program Files (x86)\Mercedes-Benz\SDconnect Toolkit\)
6. CopyfilesToolkit.ini+ SDVersion.dll
7. Paste Toolkit.ini in C:\ProgramData\I+ME ACTIA\Toolkit\ and SDVersion.dll in Install-Directory of the new SDconnect Toolkit.
8. Start SDconnect Toolkit
SDconnect Toolkit – device diagnostic
Testresultfor Part D:
Posted by: OBDexpress.co.uk at
08:39 AM
| No Comments
| Add Comment
Post contains 165 words, total size 11 kb.
August 10, 2017
Topic: Is possible
Fgtech4EDC17CP14Reviews:
Works great
Tested in boot mode, read&write eeprom+flash ok
Galleto v54 clone read -
read
Tested ok read/write
I have tested clone, perfectly worked many times on this ECU, both reading/writing via OBD and boot mode. Regards!
Galletto v54 EDC17success:
EDC17CP14 03L906022G Read/Write ok (OBD and boot mode)
BMW edc17 in boot mode ok
BMW E87 116D 2.0 EDC17C06 Bootmode r/w ok
BMW X6 3.0D 2012 and 2013 (306 and 245hp)BOSCH EDC17CP45 read/write BOOT ok
bmw3/5/7 series: edc16c31/35obdr/w ok, edc17 in boot mode ok
bmwx3 edc17 read write ok
Landrover /jaguarEDC17CP11 read out in boot mode ok, not tried write yet.
citroenC3 II 2012read/wrotetricoreEDC17C10
VW EDC17CP14 and Galletto v54 write in boot mode
PSA edc17cp10 no problem read/write
Galletto v54 EDC17failed:
BMW F10 2010y EDC17CP45 TPROT10 on the bench...boot SAK1797 onlyecudata...can
Jaguarxmedc17 read fail
Opel insignia Edc17c19 read ok
Porsche 2012 MY - VAG EDC17CP44 read\write in boot mode failed - could not disable TPROT
Sirius32make
Galletto v54EDC17Questions & Answers:
Q: Galletto works fine
Q: Galletto v54 checksum not supported, how to do?
A:0. Read Original ALL with Galletto boot mode. It will give you "All" file (4,224kb), internal flash+external flash+eeprom, (in my case).
1. Paste mod internal flash (make sure checksums are already correct) into the original 'all' file. Align correctly. Internal flash starts at 00, so it is easy.
2.Triplecheckthatthe paste is ok!
3. Flash modded "all" file in Galletto. This is done using "Write All" button.
4. It takes much longer to flash a file with differences. It took about 6+ minutes
5. Read All to verify!
6. Compare with Hex Editor.
Q: Is it possible to attempt to flash the big 4.2 MB 'all' file (int flash, ext flash,
can I paste my changes there, and checksums too?
I flashed the original 4224kb 'all' file back to
Risky, but I guess I was brave enough. The boot pin accidentally untouched,
I repositioned boot pin, reconnected power, and it continued error free!
After, I did a verification read of all.
100% identical to original
Now I will paste my internal flash mods (with checksum corrected already) into the 4224kb file, and flash that.
Q: How to delete
A:example:
009298 - Diesel Particle Filter; Differential Pressure Sensor
P2452 - 000 - Elect. Malfunction - MIL ON
find the p code in the p code
location: 190a7a
p code table start: 190654
get your hex calculator!
190a7a - 190654: 426. divide by 2, 213.
find your vag
example:
table start location: 18569e
18569e + 213: 1858b1. this is the location of the p2452dtc. 00 this byte.
no
same process as me7 except /2 instead of /8.
http://blog.livedoor.jp/obd2express/archives/1067035862.html
Posted by: OBDexpress.co.uk at
07:41 AM
| No Comments
| Add Comment
Post contains 597 words, total size 13 kb.
August 09, 2017
Xhorse VVDI Prog and Xprog, which is better?
|
Type |
||
|
MC9S12DP crack |
Yes |
Yes |
|
MC9S12XD crack |
Yes |
Yes |
|
MC9S12XE crack |
Yes |
Yes |
|
MC65HC(9)08 crack |
Yes |
No |
|
CDC32XX crack |
Will be available |
Yes |
|
M35080V3 erase encrypted sites |
Yes |
Yes |
|
M35080V6 erase encrypted sites |
Yes |
Yes |
|
080D0 erase encrypted sites |
Yes |
No |
|
160D0 erase encrypted sites |
Yes |
No |
|
24Cxx read/write |
Yes |
Yes |
|
24Exx read/write |
Yes |
Yes |
|
25Cxx read/write |
Yes |
Yes |
|
25xxx read/write |
Yes |
Yes |
|
95xxx read/write |
Yes |
Yes |
|
95Pxx read/write |
Yes |
Yes |
|
93Cx6 read/write |
Yes |
Yes |
|
TC8910x read/write |
Yes |
Yes |
|
MC965HC05 read/write |
Will be available |
Yes |
|
MC9S12H read/write |
Yes |
Yes |
|
MC9S12P read/write |
Yes |
Yes |
|
MC9S12XH read/write |
Yes |
Yes |
|
MC9S12XS read/write |
Yes |
Yes |
|
ATMEGA read/write |
Yes |
Yes |
|
XC236x read/write |
Yes |
Yes |
|
MAC724x read/write |
Will be available |
Yes |
|
AT89x5x read/write |
Will be available |
No |
|
ATtiny read/write |
Will be available |
No |
|
PIC read/write |
Yes |
No |
|
RSF212xx read/write |
Yes |
No |
|
M308xx read/write |
Yes |
No |
|
uPD70F3xxx read/write |
Yes |
No |
|
ST6xxx read/write |
Will be available |
No |
|
ST10Fxxx read/write |
Yes |
No |
|
STM8 read/write |
Yes |
No |
|
STM32 read/write |
Will be available |
No |
|
MSP430 read/write |
Will be available |
No |
|
TMS37xxx read/write |
Will be available |
No |
In summary,
Xprog is a good universal programmer for various chips and MCUs in automotive.
But if you can pay more,
Tip:VVDI PROG vs Xprog-m vsR270vsOrange5 clone:
- faster to clear 35080, 080D0, 160D0 (within 10S)
- more stable than Xprog-m to read MC9S12 series chips
- faster to attack MC9S12series chips
- less error than Orang5 to read some EEPROM that Orange 5 fail to recognize
- with voltage attack function for use
- with
CANbus,K- useLinefor
It covers chips that Xprog supports, works with less error than Orange 5, has the function of r260+r270
Posted by: OBDexpress.co.uk at
08:43 AM
| No Comments
| Add Comment
Post contains 298 words, total size 89 kb.
August 08, 2017
Here is how to
Bosch MG 7.9.8:
This ECU is installed on Kia cars, Hyundai with automatic transmission. Operation with this computer is carried out using the bookmark M7.9.8.ECU is based on a 16-bit processor ST10F275.
MARKING AND INTERCHANGEABILITY BY:
The full alphanumeric code of the marking contains in itself enough
A large set of characters and looks something like this:
PM98D442E / DGFD_836CFS2_5000, where
PM98D442E – Software ID (Software ID)
DGFD_836CFS2_5000 – Hardware ID (Calibration ID)
Explanation:
PM95D442E \ DGFD_836CFS2_5000
The software PM95D442E says that the P / O from the motor processor
BOSH M7.9.8 and installed software D442E.
ATTENTION!
ALL firmware COMPATIBLE only Within one software
Calibrations of DGFD_836CFS2_5000 mean the following
D – cars
G – Gasoline engine (
FD – HYUNDAI _i30
May be:
– AM – KIA_Soul
– LD – KIA_Cerato
– TD – KIA_Cerato
– ED – KIA_Ceed
– JB – KIA_Rio
– MC – Hyundai_Accent, Verna
– HD – Hyundai_Elantra
– PB – Hyundai_i20
– PA – Hyundai_i10
5 – ECU Manufacturer
3 – Toxicity standards according to the European standard (3-E3, A-E3, 4-E4, H-E4)
6 – Engine capacity (4 – 1.4 liters, 6 – 1.6 liters)
CFS- Complete set (including presence-absence of IMMO survey)
– With (D) ES MT Immo Off
– With (D) FS MT Immo
– With (D) PS AT Immo Off
– C (D) QS AT Immo
Where is the first "C†marking for HYUNDAI vehicles
"D†marking for KIA vehicles
2_5000 – version of software calibrations
On vehicles with automatic transmission under the marking of the engine block software
Marking of the software of the processor of the automatic transmission.
T – means that this software refers to the transmission processor (transmission)
HD – Hyundai_Elantra
2C – indicates the gear ratio of GP
16 – the volume of the engine with which the transmission operates in pairs
UB2 – software version
The ECU supports the programming modes:
Connect
Read / Write FLASH (
Attention! All programming commands must be executed from the computer, which is translated in the reprogramming mode, except for the "Establish communication†mode, which is used to transfer the unit from the diagnostic mode to the reprogramming mode.
This block
The correct size of FLASH firmware for Bosch ECU computer is 7.9.8 – 832 KB (851968 bytes).
11 Switching voltage
Left connector:
12 CAN-H (connected via J2534 device)
27 CAN-L (connected via J2534 device)
56 Non-disconnecting voltage
59 K-line (motor)
Right connector:
2 ECU mass
6 Power supply
84 K-line (automatic transmission)
To transfer the computer to the programming mode, it must be modified. For finalization, it is necessary to disassemble the computer and connect three red and three blue contacts on the board (shown in the figure below). White color indicates unused contacts for better orientation.
(Fg Galletto v54 read MG7.9.8
Then you need to connect to the computer in accordance with the connection diagram below. Then you can perform operations with the computer.
for car withautomatic transmission:
connector A (small) 11, 56 = +12v
59 = K-Line
connector B (large) 1,2,3 = computer weight
(just connect any of the indicated contacts)
84 = K-Line, automatic transmission
Note: The corresponding K-Line must be connected depending on what operations are to be performed (with the automatic transmission or the engine).
you need two 12+
82= 12+
83= 12+
85= K-Line
2= Ground
ATTENTION!
To avoid problems with "falling asleepâ€, the computer must be filled in the unit
Modified software calibrated on the basis of "native†software, i.e.
Software ID type
M98C441C
Modified firmware should, if possible, be the same.
All flash players allow you to determine the ID of the Basic software of a specific ECU.
It looks something like this:
Credits to:
http://chiptung.narod.ru/Bosch_MG_7_9_8.html
http://chiptuner.ru/content/bsl_mg798/
http://www.digital-kaos.co.uk/forums/showthread.php/457340-me7-9-8-mg7-9-8/
NO ONE BUT YOURSELF ARERESPONSIBLE OFWHAT YOU’LL TRY.
GOOD LUCK.
http://www.obdexpress.co.uk/service/how-to-use-fgtech-galletto-v54-for-bosch-mg798-21595.html
Posted by: OBDexpress.co.uk at
07:01 AM
| No Comments
| Add Comment
Post contains 739 words, total size 53 kb.
August 07, 2017
To program the PCM with As-built information viaFord IDS software:
Enter the Module Programming menu in the IDS
Select As-built and then the PCM
If the PCM is not listed in the As-built tab, use the following process to manually enter the information.
Select the IDS logo in the upper left corner of the screen.
Select the Pocket knife in the lower left corner of the screen.
Select "Update/Special Functions†from the Miscellaneous menu.
Enter 53061 into the blue box and click the tick.
Return to the Module Programming menu and select PMI then the PCM.
Follow the on-screen prompts and enter the As-built data when the IDS prompts for it. This data is available from the OASIS report for this VIN under the As-built tab. It has also been provided below for your convenience.
Complete the PMI process by continuing with the on-screen directions.
Complete the PMI process by continuing with the on-screen directions.
To get As Built Data, go to Motorcraftservice.com
Under Non-Subscription Resources, click on Quick Guides.
13 dot points down you willfine, "Module Build Data (As-Built)â€
Enter "Module Build Dataâ€
Enter the VIN# then submit. As Built Data will then be displayed inIDSinterface.
Some codes/info listed here as an example:
Use at your own risk!
00008 – IDENT_APPLY_PATCHES_VIA_FLOPPY
00009 – IDENT_UPDATE_PTU_FROM_FLOPPY
32287 – IDENT_LAUNCH_APP_MCP_REST
60503 – IDENT_LAUNCH_REGRESSION_RECORDER
27001 – IDENT_LAUNCH_FT_EOL_CP_MZ_01
32247 – IDENT_LAUNCH_SERVICE_ROUT
24040 – IDENT_ENABLE_VALIDATION_MODE
24041 – IDENT_DISABLE_VALIDATION_MODE
23761 – IDENT_LAUNCH_APP_FT_DATA_REC
81105 – IDENT_LAUNCH_APP_TSBSSMLIST
53061 – IDENT_IGNORE_MCP_INHALE
26503 – IDENT_LAUNCH_APP_VVAG
81104 – IDENT_LAUNCH_APP_FTW_SHIP_MODE_01
29124 – IDENT_TOGGLE_FORD_EXTRANET_INTRANET_URLS
60274 – IDENT_LAUNCH_CCC_ENGINEERING_APP
32227 – IDENT_LAUNCH_PROPSHAFT_BAL_APP
48712 – IDENT_LAUNCH_GENERIC_RCM_CONFIG_APP
28487 – IDENT_LAUNCH_FT_ICCMSP_MZ_01_APP
28097 – IDENT_TOGGLE_BATTERY_MONITORING
70263 – IDENT_LAUNCH_GENERIC_DIAG
71863 – IDENT_MCP1
63296 – IDENT_LAUNCH_FTW_RKE_MODE_01_APP
08080 – IDENT_LAUNCH_DETAILED_NETWORK_DIAG
32267 – IDENT_LAUNCH_APP_ENG_SUPPORT_TOOL
Posted by: OBDexpress.co.uk at
06:08 AM
| No Comments
| Add Comment
Post contains 294 words, total size 14 kb.
August 04, 2017
Loooong post here....
BMW INPA how to use- with frequently asked questions:
INPA EDIABAS download:
Inpa diver.zip(unknown security)
Inpa 5.0.1.zip(unknown security)
Inpa 5.0.2.zip(tested & worked on Windows XP)
INPA cable: K+DCAN cable switch mode:
Old K+Dcan cable vs K+DCAN cable switch mode:
http://blog.obdexpress.co.uk/2016/04/27/2016-new-bmw-kdcan-cable-with-switch-vs-old-inpa-dcan-cable/
Credits to BMW Group!
I take no credit for composing the package, just sharing it
Table of Contents
1. EDIABAS Error Messages.............................................................................................. 4
1.1 Driver Error................................................................................................................... 4
1.2 DirectNt.sys can’t be opened........................................................................................ 4
1.3 IFH-0002: Interface isn’t connected or doesn’t respond................................................ 4
1.4 IFH-0003: Data transmission HOST/Interface failed..................................................... 4
1.5 IFH-0010: Data transmission to control unit disturbed .................................................. 5
1.6 IFH-0013: Command not implemented......................................................................... 5
1.7 Error: EBAS32.EXE not found or illegal version! .......................................................... 5
1.8EDIABAerror: Error (95) SYS-0005: OBJECT FILE NOT FOUND ............................ 6
1.9 Createfile_error: OPEN CONNECTION; IFH 0018- INITIALIZATION ERROR............. 6
1.10 Battery and Ignition notrecognised.............................................................................. 6
1.11 Warning when starting OBD Setup............................................................................... 7
1.12 ERROR C1015: Too Many String Variables in Job....................................................... 8
1.13 Failure: EDIABAS Fehler 159, NET-0009: TIMEOUT................................................... 8
1.14 Failure: The name of the file or folder can’t be changed............................................... 9
2 Error Message INPA...................................................................................................... 10
2.1 APLDLL or API32.DLL can’t be found. ....................................................................... 10
2.2 Error Message 0020: Incorrect or Missing Driver. Theprogrammewill be aborted!.... 12
2.3 SYS-00002: ECU variation description file not found.................................................. 12
2.4 INPA Error: Error at Compiling à Abort! .................................................................... 13
2.5 IFH-0018:InizialisationError –INPAdoesn’t work but Toolset yet ............................. 14
2.6 IFH-0027: IFH not found à The Programm was aborted! .......................................... 14
2.7 INPA Error: Opening Inpa – Transmission error returned a_0x2 ................................ 15
2.8 INPA Error: Only a white screen appears when you run INPALOAD.EXE. ................. 15
2.9 INPA Error: DTM is no longer supported .................................................................... 16
2.10 INPA Error: Bridge16.exe can’t be initialised .............................................................. 16
2.11 Error when opening the error file à abort:.................................................................. 17
2.12 Compiler: File: \INPA\DEUTSCH\***.OUT not found! ................................................. 17
3 Tool Set Error Messages.............................................................................................. 18
3.1 EDIABAS error 100: SYS-0010: INITIALIZATION ERROR ........................................ 18
3.2 EDIABAS Error 126 (only up to Ediabas V6.4.x)......................................................... 18
3.3 IFH-0006: Command not accepted and IFH-0018: Initialization Error and IFH-0038:
Interface Command not implemented......................................................................... 18
3.4 IFH-0006: Command not accepted............................................................................. 19
3.5 IFH-0009: ECU isn’t connected or doesn’t respond.................................................... 20
3.6 SYS-0002: ECU OBJECT FILE NOT FOUND............................................................ 20
3.7 SYS-0005: Controller description file not found. Theprogrammewill be aborted! ...... 20
3.8 ToolSet Error: Runtime error ’372’.............................................................................. 21
3.9 Tool Set Error: Run-time error ’5’ – Invalid Procedure Call ......................................... 21
3.10 Tool Set Problem: If an SGBD is opened, then only the hourglass appears and the
SGBD is not loaded. ................................................................................................... 21
3.11 EDIABAS error 20: IFH-0010: Data transmission to control unit disturbed ................. 21
3.12 EDIABAS Error 134: API-0014: Result not found ....................................................... 22
3.13 It takes too long to load an SGBD in the Tool Set ...................................................... 22
3.14 Black Windows in the Tool Set ................................................................................... 22
4 General Questions
........................................................................................................ 23
4.1 Installation of EDIABAS and INPA.............................................................................. 23
4.2xBD-Export of SGBDs, Group SGBDs, INPA scripts and INPA configuration files using
the ECCO Web Client ................................................................................................ 23
4.3 How can I find out if the serial interface COM1 has been taken?................................ 25
4.4 How do I start INPA?.................................................................................................. 26
4.5 How can I switch between OBD and ADS interfaces? ................................................ 26
4.6 In which directory structure is OBD.ini saved?............................................................ 27
4.7 How can I find out what interface I installed with INPA? ............................................. 27
4.8 How do I find out what EDIABAS package is installed?.............................................. 27
4.9 How can I uninstall EDIABAS or INPA?...................................................................... 27
4.10 How can tell if the EDIABAS server is running as a 16-bit or a 32-bit application? ..... 27
4.11 What is the difference between \EDIABAS\bin\ToolSet.exe and
\EDIABA\bin\Tool32.exe?........................................................................................... 28
4.12 What is an SGBD and what is its connection to EDIABAS? ....................................... 28
4.13 Where are the individual SGBD names and theirmeanings givenin plain English?... 28
4.14 What is a Job? ........................................................................................................... 28
4.15 What do SGBDs with the name _xxx mean?.............................................................. 29
4.16 What is the group file used for?.................................................................................. 29
4.17 Diagnostics Index ....................................................................................................... 29
4.18 Variation Index ........................................................................................................... 29
4.19 What is the meaning of the file EDIABAS.ini? ............................................................ 29
4.20 How is the simulation file connected to the trace file?................................................. 31
4.21 Why have an XBD Generator? ................................................................................... 31
4.22 What are the prerequisites for remote access via TCP/IP? ........................................ 31
4.23 What is the VC Tool and when is it used? .................................................................. 32
4.24 What is the KVP Editor?............................................................................................. 32
; color: #ba1111; cursor: default; display: inline-block; height: 9px !important; user-select: all; width: 9px !important;" href="https://www.blogger.com/null" name="1">1. EDIABAS Error Messages
1.1 Driver Error
Messagecomes along with an ADS or OBD connector.
This error occurs if another program or device has taken the COM1 port of your PC.
If you want to work with EDIABAS or INPA, please make sure that the COM1 port is not
taken.
1.2 DirectNt.sys can’t be opened
This error only occurs with an NT computer if the ADS driver hasn't been installed.
The instructions for installing the ADS driver can be found in the "Installation Guide/Update
Guide†ADS_DOKU.pdf in the directory C:\EDIABAS\Hardware\ADS\ or on the Intranet page
http://www5.muc/ti4-web/ti-430/german/themen/Diagnose.htm.
1.3 IFH-0002: Interface isn’t connected or doesn’t respond
Reason: In the Ediabas.inifile, the interface is set toSTD:FUNK. However, you have
connected an ADS or OBD connector.
Solution: Modify the interface setting in Ediabas.ini.
1.4 IFH-0003: Data transmission HOST/Interface failed
Reason 1: In the Ediabas.inifile, the interface is set toSTD:OBD. However, you have
connected an ADS connector.
Solution 1: Modify the interface setting.
Reason 2: The data transmission failed when sending (e.g. short circuit in the line).
Solution 2: Get rid of the short circuit, for example.
Reason 3: Connector not connected or no power supplied.
Solution 3: Check whether the connector is connected and is supplied with power.
Reason 4: The device manager has been used to disable the FIFO buffer for COM1.
Solution 4: In the device manager (Windows XP: Enter "Start†à "Control Panel†Ã
"System†à "Hardware†à "Device Manager†à Ports (COM & LPT)), and then
select COM1 from the ports. Then under the "Port Settings†tab, select
"Advancedâ€. There must be a check-mark by "Use FIFO buffers†and "8†must be
selected for the receive buffer and transmitpuffer.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage5of32
TI-430 Andreas Schandl Release date: 29.09.2006
1.5 IFH-0010: Data transmission to control unit disturbed
This problem can occur with XP computers with the OBD interface.
Reason: With Windows XP, it is not possible to automatically set the receive and transmit
buffers using OBDSetup.exe, like in Windows NT.
Solution: Set the receive and transmit buffers to 8 as shown in the following:
Use Start à My Computer à Control Panelà System à Hardware à Device
Manager à Ports (COM & LPT) and then clickwiththe right mouse button to call
up the properties of the COM port that is being used. Under the Port Settings tab,
set the Data bits of the receive and transmit buffers to 8.
1.6 IFH-0013: Command not implemented
Reason: The error was caused by anotherprogrammethat accessed the COM1 interface.
Usually, the "HotSyncâ€programmeis installed on the computer for theorganiser.
Solution: Check theprogrammesthat are started automatically when Windows is started.
1.7 Error: EBAS32.EXE not found or illegal version!
This error occurs if the path variable is setwiththe path C:\EDIABAS\BIN in the system and
user variables (Start à My Computer à Control Panel à System à Advanced and then in
the "Environment" tab).
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage6of32
TI-430 Andreas Schandl Release date: 29.09.2006
1.8 EDIABAS error: Error (95) SYS-0005: OBJECT FILE NOT FOUND
Reason 1: No SGBD in C:\EDIABAS\ECU
Solution 1: Copy the SGBD into the Ecu directory.
Reason 2: No group file in C:\EDIABAS\ECU (for group call)
Solution 2: Copy the group file to C:\EDIABAS\ECU
Reason 3: No path definition C:\EDIABAS\BIN
Solution 3: Set the system variable (see 2.1)
Reason 4: Incorrect path definition in EDIABAS.INI
Solution 4: Set the EcuPath path in Ediabas.ini to C:\EDIABAS\ECU
Reason 5: The SGBD name contains reserved characters or is too long. Only 8 characters
are allowed (a-z, A-Z, 0-9, "_").
1.9 Createfile_error: OPEN CONNECTION; IFH 0018- INITIALIZATION
ERROR
ADS Interface:
The following error appears when Ediabas is started:Createfile_error: OPEN
CONNECTION
OBD Interface:
The following error appears when Ediabas is started:Error 28: IFH 0018- INITIALIZATION
ERROR. (Also see Section 3.3)
Reason: Ediabas is attempting to access port COM1. However, the port doesn't exist, or it
has been taken by anotherprogramme(e.g. HotSync from Palm, infrared).
Solution: Install a COM1 interface or free it.
1.10 Battery and Ignition notrecognised
Reason: With a Dell Latitude D600 laptop, pin 9 has no function and it is therefore not
able to correctlyrecognisethe battery status.
Solution 1: Use OBD via USB, see C:\EDIABAS\BIN\INI.PDF Chapter 2.2 for this.
Solution 2: The laptop is connected to the docking station.
Solution 3: Workaround for the OBD driver as of February 2004: A file "OBD.ini†must be
created in the directory C:\WINDOWS for Windows XP, or alternatively
C:\WINNT for Windows NT, with the following entry. This is because with
UBATT=OFF, the battery status is not determined via hardware, but is
permanently set to "Battery voltage availableâ€.Alsosee OBD_DOKU.pdf in the
\Ediabas\Hardware\OBD directory.
Entry in OBD.ini:
[OBD]
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage7of32
TI-430 Andreas Schandl Release date: 29.09.2006
UBATT=OFF
1.11 Warning when starting OBD Setup
A warning occurs when starting C:\EDIABAS\HARDWARE\OBD\OBDSetup.exe. After You
want to start Tool Set or INPA You will get the following error message:
Reason: The value of the variable DWORD (here RxFIFO) can not be set by
OBDSetup.exe.
Solution: You have to set the value of theDWORTin the registry. You have to open the
Regedit by using Start à Ausführen… à enterregedità OK. Choose the
following path in theregedit: HKEY_LOCAL_MACHINE Ã System Ã
CurrentControlSet à clickon Services. On the right side of thewindowYou can
cklickon the name of the DWORd value which is defective (here RxFIFO). Enter
the value 8 with the base hexadecimal. Click Okanclose theregedit. Now You
can start the Tool Set or INPA without an error.
If You have warnings for other DWORDs whenstartigOBDSetup.exe, You will
have to set the value of thecoloum„Expected" for the wrong value in the registry.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage8of32
TI-430 Andreas Schandl Release date: 29.09.2006
1.12 ERROR C1015: Too Many String Variables in Job
Reason: In a job only a maximum of 6 string-variables is acceptable.
Solution: You have to reduce the number of variables.
1.13 Failure: EDIABAS Fehler 159, NET-0009: TIMEOUT
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage9of32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The configuration for theremotehostis false.
Solution 1: Set the correspondingnetworknamefor theremotehostin the configuration file
EDIABAS.INI.
Reason 2: Theinface-cable on the OPPS is not correct.
Solution 2: You need a special OPPS-Cable for the connection with the CAN-BUS. (since
type series L6)
Reason 3: In theremotecontrolthe OPPS-interface is used by default (since EDIABAS 7.0).
Theremotecontrolbetween two PC’s is not possible with this configuration.
Solution 3: Close alldiagnosticapplicationsand EDIABAS-Processes that are running and
open the file "remote_mit_pc.bat†in the directory C:\EDIABAS\bin.
1.14 Failure: The name of the file or folder can t be changed
Reason: EDIABAS or another component of EDIABAS is still open.
Solution: You have to shut down thediagnosticapplicationand EDIABAS. If necessary, the
fileexplorerand the editors which access the EDIABAS-Directory have to close
as well.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage10of32
TI-430 Andreas Schandl Release date: 29.09.2006
; color: #ba1111; cursor: default; display: inline-block; height: 9px !important; user-select: all; width: 9px !important;" href="https://www.blogger.com/null" name="2">2 Error Message INPAs
2.1 APLDLL or API32.DLL can’t be found.
When calling INPA under Windows NT, the following error messages appear:
Reason 1: The path C:\EDIABAS\BIN has not been set in the ‘Path’ system variable.
Solutionwith Windows NT:
Set the system variable: Please log into your system as the administrator with administrator
rights. Use Start à My Computer à Control Panel to call the "System†menu. In the
"Environment†tab, double click the system variable ‘Path’.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage11of32
TI-430 Andreas Schandl Release date: 29.09.2006
Go to the end of the field value. There, enter a semicolon and then enter the path
C:\EDIABAS\BIN. Click "Set†and "OKâ€.
Solutionwith Windows XP:
Set the system variable: Please log into your system as the administrator with administrator
rights. Use Start à Control Panel to call the "System†menu. Under "Advanced†and the
"Environment†tab, double click the system variable ‘Path’.
Go to the end of the variables field value. There, enter a semicolon and then enter the path
C:\EDIABAS\BIN.
Click "OKâ€.
Completely restart your computer!!! (Don’tloginunder a new name or the like.) It should no
longer be a problem to call INPA.
Reason 2: Ediabas is not installed, only INPA is.
Solution 2: Install Ediabas.
When calling INPA under Windows 95, 98, the following error message appears:
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage12of32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason: The path C:\EDIABAS\BIN has not been set in the ‘Path’ system variable.
Solution: Set the system variable:
Open the file Autoexec.bat in the directory C:\ by clicking it with the right mouse key with the
shift key pressed, and then select "Open withâ€. The best thing is to use the Notepad to
display the file.
Now, at "pathâ€, enter the path c:\ediabas\bin.
Save the change and close the file.
Completely restart your computer!!! (Don’tloginunder a new name or the like.)
2.2 Error Message 0020: Incorrect or Missing Driver. Theprogrammewill
be aborted!
Conditions:
You have access to \\smuc0900\sg. You are linked to this drive and would like to start an
INPA script.
Reason 1: Missing Ediabas.inifile in C:\Winnt.
Reason 2: You are not connected to the controller.
For developers: Simulation is not switched on in the Ediabas.inifile.
Solution: Copy the Ediabas.inifile from C:\Ediabas\Bin to C:\Winnt.
2.3 SYS-00002: ECU variation description file not found.
The error occurs when starting an INPA script.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage13of32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The *.prg SGBD is not located in the path C:\Ediabas\Ecu.
Solution 1: Copy the *.prg SGBD into the ECU directory.
Reason 2: The external table T_GRTB.prgdoesn’t exist in the directory C:\EDIABAS\ECU
or it is obsolete.
Solution 2: Copy the file into the ECU directory or update the external table using the ECCO
Web Client.
2.4 INPA Error: Error at Compilingà Abort!
The following error message appears when starting an INPA script.
Reason 1: An INPA script with the ending IPO was started by theprogrammeINPA.EXE
instead of by theprogrammeINPALOAD.EXE.
Solution 1: Only start INPA scripts that end with IPO withINPALOAD.EXE.
Reason 2: The selected INPA script doesn’t exist in the C:\INPA\SGDAT\ directory.
Solution 2: Update the INPA scripts using the ECCO Web Client.
Reason 3: INPA Version 5.0.1: The INPA script *.IPO can’t be started with a double-click in
the directory C:\INPA\SGDAT\*.IPO.
Solution 3: Update to Version 5.0.2.
Reason 4: INPA Version 5.0.1: The desktop link of an INPA script doesn’t work.
Solution 4: The target path must be expanded to include the INPALOAD path. To do this,
click the desktop link once with the right mouse button and go to ‘Properties’.
Expand the target path to include C:\INPA\BIN\INPALOAD.exe for Windows NT
(see Fig.) and C:\EC-Apps\INPA\BIN\INPALOAD.exe for Windows XP.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage14of32
TI-430 Andreas Schandl Release date: 29.09.2006
Grund 5: The file startger.ipo of thegermaninstallation and the filestartus.ipo of the
englishinstallationdon’texist in the directory \INPA\CFGDAT\.
Lösung 5: Install INPA once again.
2.5 IFH-0018:InizialisationError – INPA doesn’t work but Toolset yet
The error occurs ifa SGBDis running by INPA or CASCADE. If the same SGBD is loaded in
the Toolset it will notoccureaninizialisationerror.
Reason 1: The communications port COM1 doesn’ exist, but COM3 yet. The Toolset is
working without theinizialisationerror,because the file OBD.ini exists in the
directory C:\Ediabas\bin\. But the file OBD.ini has to exist in thedirecory
C:\Windows.
Solution 1: Copy the file OBD.ini in the directory C:\Windows or create a new one. (Creation
of OBD.ini q.v. 3.3).
Grund 2: q.v. 3.3
Lösung 2: q.v. 3.3
2.6 IFH-0027: IFH not foundà The Programm was aborted!
The error occurs when starting INPA.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage15of32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The setting for the interface in the configuration file Ediabas.inidoesn’t exist.
Solution 1: Please do the settings for the interface e.g.:
Interface = STD:OBD
Reason 2: The setting for the interface in the configuration file Ediabas.ini is
Interface=STD:OMITEC, but the OMITEC driver isn’t installed correctly.
Solution 2: Install the OMITEC driver with the instructions
InstructionforOMITECInstallation.pdf via the GIS server.
Reason 3: The setting for the interface in the configuration file Ediabas.ini is
Interface=OMITEC, but the correct setting isInterface=STD:OMITEC.
Solution 3: Please do the settings for the interfaceInterface=STD:OMITEC.
Reason 4: The old OMITEC driver wasn’t uninstalled correctly.
Solution 4: Please uninstall the old OMITEC driver with the instructions
InstructionforOMITECInstallation.pdf via the GIS server.
2.7 INPA Error: Opening Inpa – Transmission error returned a_0x2
Reason: During the installation of Ediabas/Inpa, the configuration "Without configurationâ€
was selected.
Solution: When running the installationprogramme, select a configuration, e.g. "BMW
Plant 1.1 Munichâ€.
2.8 INPA Error: Only a white screen appears when you run INPALOAD.EXE.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage16of32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The api.dll or api32.dll file has been manually copied into the WINDOWS
directory with Windows XP and into the WINNT directory with Windows NT.
Solution 1: Delete the file api.dll or alternatively api32.dll from the WINDOWS or alternatively
the WINNT directory. The file may only exist in the directory \EDIBAS\BIN\.
Reason 2: You have installed the 32-bit version of INPA (as of Version 5.0.1) and have not
performed an update of the INPA scripts.
Solution 2: Update the INPA scripts using the ECCO Web Client.
2.9 INPA Error: DTM is no longer supported
Reason: This error message appears if INPA.INIhas been copied from Version 4.7.7 to
Version 5.x.x.
Solution: Since it can’t be excluded that even more files from the old version have been
mixed with the new ones, the old ones must be deleted, or alternatively
reinstalled (see Chapter 5). Reinstall INPA using the Global Information Service
(GIS) https://gis.bmw.com.
2.10 INPA Error: Bridge16.exe can’t beinitialised
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage17of32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: A 16-bit INPA script has been started with the 32-bit version of INPA (as
of Version 5.0.1).
Solution 1a): Update the INPA scripts using the ECCO Web Client.
Solution 1b): Convert the INPA script to the standard ‘includes’ for the 32-bit version.
To do this, contact the respective person responsible for INPA at TI-43x
(see \\smuc0900\sgref\Referenz\Referenz.inp)
Reason 2: A 16-bit DLL has been found, which means the developer of the INPA
scriptis using a 16-bit DLL.
Solution 2: The developer of the INPA script must convert the DLL to 32-bit.
2.11 Error when opening the error fileà abort:
Reason: This error occurs with Windows XP because the user doesn’t have the correct
rights to change files in the directory C:\INPA\Bin.
Solution: The user needs "Power user†rights or the user needs the appropriate write rights
to the "INPA†directory.
2.12 Compiler: File: \INPA\DEUTSCH\***.OUT not found!
Reason: The path C:\EDIABAS\BIN has not been set in the ‘Path’ system variable.
Solution: Set the path C:\EDIABAS\BIN in the ‘Path’ system variable. (q.v. chapter 2.1).
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage18of32
TI-430 Andreas Schandl Release date: 29.09.2006
; color: #ba1111; cursor: default; display: inline-block; height: 9px !important; user-select: all; width: 9px !important;" href="https://www.blogger.com/null" name="3">3 Tool Set Error Messages
3.1 EDIABAS error 100: SYS-0010: INITIALIZATION ERROR
Reason: This message comes when an SGBD has an automatic concept switch between
multiple diagnostics logs and is not connected to the controller.
Solution: Connect the controller.
3.2 EDIABAS Error 126 (only up to Ediabas V6.4.x)
Reason: This error message appears if you start the Tool Set while an INPA script is
running. This is also true the other way round. The reason for this is that only one
programmecan access EDIABAS at a time.
Solution: Therefore, before you start the ToolSet, you must exit INPA!!!
3.3 IFH-0006: Command not accepted and IFH-0018: Initialization Error and
IFH-0038: Interface Command not implemented
Errors IFH-0006 and IFH-0018 occur if any SGBD is loaded in the Tool Set. Error IFH-0038
is generated when loading the utility file into the Tool Set.
Reason 1: The error was caused by anotherprogrammethat accessed the COM1
interface. Thisprogrammecould be "HotSync†for Palm or "ActiveSyncâ€
forlpack.
Solution 1: Check theprogrammesthat are started automatically when Windows is
started (see Chapter 4.1).
Reason 2: The COM1 interface is taken by a serial printer.
Solution 2: Uninstall the printer.
Reason 3: The infrared interface is active.
Solution 3: Deactivate the infrared interface.
Reason 4: There is no COM1 interface (COM3 instead, for example)
Solution 4a): Install the COM1 interface.
Solution 4b): Create a file with the name OBD.ini and make the following entry to set
the existing serial interface (COM3, for example):
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage19of32
TI-430 Andreas Schandl Release date: 29.09.2006
[OBD]
Port = Com3
The file OBD.ini must be saved in the directory C:\WINDOWS\ for
Windows XP or in directory C:\WINNT\ for Windows NT up to the Ediabas
Package 1.3 and as of Ediabas Package 1.4 in directory
C:\EDIABAS\BIN\. The current version of the Ediabas Package can be
seen in the files C:\EDIABAS\version.txt or C:\EDIABAS\package.pdf.
Reason 5: Only for IBM notebooks: The COM1 interface is reserved for the docking
station; the COM3 interface is installed instead.
Solution 5a): see solution 4b:
Solution 5b): Set the COM3 port to COM1: In the device manager (Windows XP:
Select "Start†à "Control Panel†à "System†à "Hardware†and then
select COM3 from the ports under the menu item "Device Managerâ€.
Then use the right mouse button à "Properties†à "Port Settings†Ã
"Advanced†to reach the "Advanced Settings for COM3â€. Set COM1 in the
COM Port Number. The message that COM1 is already taken can be
ignored in this case.
Reason 6: The old OMITEC driver wasn’t uninstalled correctly.
Solution 6: Please uninstall the old OMITEC driver with the instructions
InstructionforOMITECInstallation.pdfvia the GIS server.
3.4 IFH-0006: Command not accepted
This error occurs ifa SGBDis loaded in the Tool Set when the OBD connector is being used.
Reason 1: ODB has actually been set as the interface in Ediabas.ini, but the Tool Set uses
the multi-instance with another interface, e.g. K-Line. The setting for themultiinstance
and the interfaces used here is made in the file Tool32.ini in the
directory C:\Windows (for Windows XP) or alternatively C:\Winnt (for Windows
NT). Then, the entries in Tool32.ini, or alternatively the interface apply and not
the ones in Ediabas.ini. The use of multi-instance in the Tool Set is identified in
the title bar, for example with "Tool32:1â€, for single multi-instance.
Solution 2: Enter the interface that is being used in Tool32.ini ordisablemulti-instance with
the entry "Noâ€.
Reason 2:A SGBDis loaded in the Tool Set when the diagnosis protocol UDS is being
used. For UDS-SGBDs You have to use the interface OMITEC but in the
EDIABAS.ini the setting fort heinterfaceist„STD:OBD".
Solution 2: Change the setting forthrinterface to „interface =STD:OMITEC" in the
EDIABAS.ini file. The OMITEC connector has to be stressed by the voltage (blue
blinking). If the connector can’t be stressed by the voltage and You want to load
the SGBD yet, You will use the simulation mode. You can activate the simulation
mode e.g. with themenue„configuration -> EDIABAS". Notice, if you want to use
the simulation mode, a simulation file for the interface will have to exist in the
simulation path.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage20of32
TI-430 Andreas Schandl Release date: 29.09.2006
3.5 IFH-0009: ECU isn’t connected or doesn’t respond
Reason 1: In the Ediabas.inifile, the interface is set toSTD:ADS. However, you have
connected an OBD connector.
Solution 1: Modify the interface setting.
Reason 2: The ignition is switched off.
Solution 2: Switch the ignition on.
Reason 3: The device manager has been used to disable the FIFO buffer for COM1.
Solution 3: In the device manager (Windows XP: Enter "Start†à "Control Panel†Ã
"System†à "Hardware†à "Device Manager†à Ports (COM & LPT)), and select
COM1 from the ports and under the "Port Settings†tab, select "Advancedâ€. There
must be a check-mark by "Use FIFO buffers†and the highest possible setting
must be selected for the receive buffer.
3.6 SYS-0002: ECU OBJECT FILE NOT FOUND
Reason 1: If the external table T_GRTB.prgdoesn’t exist in the directory C:\EDIABAS\ECU\
the error message will be displayed when You execute the job
IDENT_FUNKTIONAL of a functional SGBD.
Solution 1: You have to download the external table using the ECCO Web Export and copy it
in the directory C:\EDIABAS\ECU\.
Reason 2: The SGBD, which You want to start doesn’t exist in the directory
C:\EDIABAS\ECU or is an old one.
Solution 2: You have to download the SGBD using the ECCO Web Client and copy it in the
directory C:\EDIABAS\ECU\.
3.7 SYS-0005: Controller description file not found. Theprogrammewill be
aborted!
Reason 1: The SGBD is not located in the path C:\Ediabas\Ecu.
Solution 1: Copy the SGBD into the Ecu directory.
Reason 2: This error occurs if the EcuPath in Ediabas.ini(C:\Ediabas\Bin) isn’t set to
C:\EDIABAS\ECU.
Solution 2: Set the correct path.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage21of32
TI-430 Andreas Schandl Release date: 29.09.2006
3.8 ToolSet Error: Runtime error ’372’
The following error message appears.
Reason: The old version msflxgrd.ocx exists under c:\winnt\system32.
Solution:msflxgrd.ocx under c:\Ediabas\bin must be registered. To do this, select "Startâ€
à "Run…†and executeregsvr32 :\ediabas\bin\msflxgrd.ocx in the window and
confirm with "OK".
The following must be entered for Windows XP: "regsvr32 c:\ediabas\bin\
msflxgrd.ocx"
3.9 Tool Set Error: Run-time error ’5’ – Invalid Procedure Call
Reason: The Tool Set was started twice in a very short period of time.
Solution: Close all Tool Set processes that are running and start the Tool Set again with
only one double-click.
3.10 Tool Set Problem: If an SGBD is opened, then only the hourglass
appears and the SGBD is not loaded.
Reason: An old version Richtx32.ocx exists under c:\winnt\system32.
Solution: Richtx32.ocx under c:\Ediabas\bin must be registered. To do this, select "Startâ€
à "Run…†and execute "regsvr32 :\ediabas\bin\richtx32.ocx" in the window and
confirm with „OK".
The following must be entered for Windows XP: „regsvr32 c:\ediabas\bin\
richtx32.ocx"
3.11 EDIABAS error 20: IFH-0010: Data transmission to control unit
disturbed
Reason 1: When using the EDIC card, the error message is issued when executing the
IDENT job.
Solution 1: Changes must be made in the file "XEDICC.ini†in the "...\Ediabas\Bin" directory.
There, the parameters set for high-speed must be commented out and the
parameters for low-speed must be enabled:
;highspeed:
;Interface=1;
;Presc=0x01;
;SJW=0x01;
;TSEG1=0x08;
;TSEG2=0x07;
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage22of32
TI-430 Andreas Schandl Release date: 29.09.2006
;lowspeed:
Interface=2;
Presc=0x0A;
SJW=0x02;
TSEG1=0x05;
TSEG2=0x02;
Reason 2:A SGBDis loaded in the Tool Set when the diagnosis protocol UDS is being
used. You use the interface OMITEC but the connector isn’t stressed by the
voltage (no blue blinking).
Solution 2: Connect the OMITECwitthe vehicle. The OMITEC connector has to be stressed
by the voltage (blue blinking). If the connector can’t be stressed by the voltage
and You want to load the SGBD yet, You will use the simulation mode. You can
activate the simulation mode e.g. with themenue„configuration -> EDIABAS".
Notice, if you want to use the simulation mode, a simulation file for the interface
will have to exist in the simulation path.
3.12 EDIABAS Error 134: API-0014: Result not found
The error occurs ifa SGBDis loaded in the Tool Set when the diagnosis protocol UDS is
being used and the Job FS_LESEN is being executed.
Reason: You use the setting "read error like INPAâ€, but the Toolset can’t support the
function yet for UDS-SGBDs.
Solution: Please remove the setting "read error like INPA†in themenue"configuration ->
Toolsetâ€.
3.13 It takes too long to load an SGBD in the Tool Set
Loading motor or transmission SGBDs takes an above average amount of time.
Reason: Large SGBDs often contain many and extensive tables and their information has
to be loaded.
Solution: Under the Configuration menu item in the Tool Set and then Tool Set, the
checkmarkby the selection of table information must be removed.
3.14 Black Windows in the Tool Set
After loadinga SGBDone or more windows of the Tool Set are black windows.
Reason: The registration of therichtextboxis invalid.
Solution: You have to register therichtextbox. Execute the batch file REGSVR32.BAT in
the directory C:\Ediabas\bin\.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage23of32
TI-430 Andreas Schandl Release date: 29.09.2006
; color: #ba1111; cursor: default; display: inline-block; height: 9px !important; user-select: all; width: 9px !important;" href="https://www.blogger.com/null" name="4">4 General Questions
4.1 Installation of EDIABAS and INPA
The Installation of EDIABA,INPAand NFS have to be donewebbasedvia the Global
Information Service (GIS). You can reach the GIS homepage with the following link:
https://gis.bmw.com/.
In the forum „BMW Standard Tools Werk" You can find the installation data of EDIABAS,
INPA and NFS. The pathistshownbelow:
BMWStandardToolsWerk
Standard Tools/ Tool InstallationWerk
EDIABAS
INPA
NFS
Foraccesrights for the GIS forum „BMW Standard Tool Werk" sendanmailto
Referenz@bmw.de stating the name the Q/QX numberan thereason. We can give access
rights for this forum only for colleagues from the Tdepartements. Colleagues from other
departments andsupplierescan get the installation via the GIS forum „BMW Standard Tools
Entwicklung". You can apply for access rights using the following link:
https://gis.bmw.com/gis/d/toolsantrag.htm.
Please pay attention to theintallationinstructions which You can get in the same directories
of the installation data. After theintallationYou have to download the SGBDs, INPA scripts,
Group SGBDs, INPA configuration files and external tables using the ECCO Web Client.
Which data You have to download is described in the following chapter 4.2.
4.2xBD-Export of SGBDs, Group SGBDs, INPA scripts and INPA
configuration files using the ECCO Web Client
The update of SGBDs, group SGBDs, external tables, INPA scripts and INPA configuration
files can be donewebbasedusing the ECCO Web Client.
You can apply foraccesrigthsfor ECCO at the user service center (Tel. 089-382-55555)
stating Your valid Q/QT/QX number.
You can reach the homepage of the ECCO Web Clients with the following link:
http://www6.muc/ppea. AfterloginYou have to select the linkxBDExport in the navigation
bar and You can see the search screen. You have the possibility to search for a single file or
search for all files assigned to a certain typeserieor search fora several release periods.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage24of32
TI-430 Andreas Schandl Release date: 29.09.2006
If You have installed EDIABAS You will need following files:
- ï€ SGBD_Revisionen
- ï€ GRP_SGBD_Revisionen
- ï€ ExterneTabelle_Revisionen
If You have installed INPA You will need following files:
- ï€ SGBD_Revisionen
- ï€ GRP_SGBD_Revisionen
- ï€ ExterneTabelle_Revisionen
- ï€ Inpa_Script_Revisionen
In the column „Verfügbare Dateitypen" You have to select the data types.These columnis
very importantvorthe export of the files, i.e. the data types which are selected will be
exported. Please payattentiononthe correct selection.
If You have installed EDIABAS You will select the following data types:
- ï€ SGBDprg_english or SGBDprg_deutsch
- ï€ SGBDgrp
- ï€ EXTABprg_english or EXTABprg_deutsch
If You have installed INPA You will select the following data types in addition to the data
types above:
- ï€ INPAipo_english or INPAipo_deutsch
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage25of32
TI-430 Andreas Schandl Release date: 29.09.2006
- ï€ Select also „Benutzereinst.verwenden"
- ï€ Select also „INPA-Konf.-Dateien"
After the download of the necessary files You have to copy the files in the right directories:
EDIABAS data:
1 …\EDIABAS\ECU\
- SGBDen: SGBDprg_deutschà alle*.prg-Dateien
- externe Tabellen: EXTABprg_deutschà T_GRTB.prg, T_PCOD.prg
- Gruppen-SGBDen: SGBDgrp_deutschà alle*.grp-Dateien
INPA data:
1 …\INPA\SGDAT\
- INPA scripts: INPAipo_englishà all *.ipo files
1 …\INPA\CFGDAT\
- INPA-Konfig-Files: INPA_Konfig_xBD_Download_eng.zip
à all *.ger files or *.eng files
Inpa.ini file
ger =germanINPA config, eng =englishINPA config
If You have problems with thexBDExport using ECCO Web Client please call the user
service center: Tel. 089-382-55555 or send a mail to ECCO hotline: ecco.hotline@bmw.de.
4.3 How can I find out if the serial interface COM1 has been taken?
There is a way to find out if the serial interface, forexampleCOM1, has been taken, but it is
not possible to find out whatprogrammehas taken the interface.
As described in the respective sections of Chapter 3, theprogrammesthat most often take
COM1 are HotSync for the Palm and ActiveSync for thelpackor a Nokia software. In order
to establish whether theseprogrammesare automatically started when you start the
computer, please check your ‘Autostart’ settings. Do this by making sure that these
programmesdon’t appear in the following directories:
- C:\Documents and Settings\All Users\Startmenu\Programs\Autostart\
- C:\Documents and Settings\Your QX Number\Startmenu\Programs\Autostart\
Another way to check theutilisationof COM1 is to look in the system information. The
system information can be run with the DOS commandwinmsdin an input prompt (Start Ã
Run… à enterwinmsdà OK). Here, it is important that you only runwinmsdif the Ediabas
server is closed. Under the path System Summary à Components à Ports à Serial, the
information about the active serial ports COM1, COM2, and so on will be shown if they exist.
The current value can be seen in the element "Busyâ€. If this value is "Noâ€, then the interface
is free, and if it is "Yesâ€, then the interface has been taken by aprogramme. You can’t find
out whatprogrammeit is here.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage26of32
TI-430 Andreas Schandl Release date: 29.09.2006
4.4 How do I start INPA?
Start Inpa using Inpaload.exe in C:\Inpa\Bin or alternatively C:\EC-Apps\Inpa\Bin or use
Start à All Programs à EDIABAS INPA ELDI NCS NFS à INPA(_.IPO) to start the general
reworkingprogramme. This corresponds to calling Inpaload.exe under
smuc0900\sg\Inpa\Bin or alternatively C:\Inpa\Bin.
4.5 How can I switch between OBD and ADS interfaces?
Prerequisite:
The appropriate driver must be installed for the interface that you want to use. In the
installation guide for INPA (http://smuc0900/TI-430 or http://smuc0900/TI-430 under Subjects Ã
EDIABAS /INPA Ã EDIABAS or INPA), you can look up how a driver is installed.
Now, you can change the interface directly in the fileEdiabas.ini(C:\EDIABAS\BIN). You
only have to make the appropriate change to the line where the interface is entered.
Interface =STD:OBD, i.e the OBD interface will be used.
Interface = ADS, i.e the ADS interface will be used.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage27of32
TI-430 Andreas Schandl Release date: 29.09.2006
For the case that OBD is being used via USB, an additional entry isnecessary inOBD.ini.
See C:\EDIABAS\BIN\INI.PDF for this.
4.6 In which directory structure is OBD.ini saved?
If the OBD.ini file exists, then in order to not run the interface via COM1 by default (compare
to 1 i), then the OBD.ini file must be saved in the directory C:\WINDOWS\ for Windows XP
or in directory C:\WINNT\ for Windows NT up to the Ediabas Package 1.3 and as of Ediabas
Package 1.4 in directory C:\EDIABAS\BIN\. The current version of the Ediabas Package can
be seen in the files C:\EDIABAS\version.txt or C:\EDIABAS\package.pdf.
4.7 How can I find out what interface I installed with INPA?
To do this, you have 2 possibilities:
- Call Start à All Programs à EDIABAS INPA ELDI NCS NFS à EDIABAS Tool32. In
the configuration menu, select Ediabas. There, you will find the desired information in the
interface line.
- However, you can also check in theEdiabas.ini(C:\EDIABAS\BIN) to see what
interface you have installed. For the OBD interface, you will find the line ‘Interface =
STD:OBD’and for the ADS Interface the line ’Interface = ADS’.
4.8 How do I find out what EDIABAS package is installed?
The version of the currently installed Ediabas package can be seen in the files
C:\EDIABAS\version.txt or C:\EDIABAS\package.pdf.
4.9 How can I uninstall EDIABAS or INPA?
You uninstall INPA by deleting the Ediabas and Inpa folders under C:\.
Reason: No registry entries are made during the installation.
4.10 How can tell if the EDIABAS server is running as a 16-bit or a 32-bit
application?
Under Windows 95 and 98, the EDIABAS server runs as a 16-bit version.Thecan be
recognisedby the yellowEin the task bar.
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage28of32
TI-430 Andreas Schandl Release date: 29.09.2006
Under Windows NT4 and XP, the EDIABAS server runs as a 32-bit version. This can be
recognisedby the greenEin the task bar.
Note:
As of 2003, there is the EDIABAS Version 6.4. This can also run as a 32-bit application
under Windows 95/98 and XP.
4.11 What is the difference between \EDIABAS\bin\ToolSet.exe and
\EDIABA\bin\Tool32.exe?
Tool32.exe is current and when it is started, the Ediabas server will start as a 32-bit
application. ToolSet.exe is an old version and is required under Windows 3.11.
4.12 What is an SGBD and what is its connection to EDIABAS?
The controller description files (SGBD) contain the controller-specific know-how. Each SGBD
contains the order telegram of the respective controller and decodes its reply telegrams. In
the process, the raw data (bytes) is converted into directlyuseablevariables (Data types: int,
long, real, string), i.e the error code is converted into error text.
For each controller variation, there is exactly one variation-specific SGBD.
The SGBDs are loaded and interpreted by the EDIABAS runtime system by an application
programmewhen the order is issued. The file name of the SGBD (without extension) is the
name with which the applicationprogrammeaddresses a controller variation or controller
group.
4.13 Where are the individual SGBD names and theirmeanings givenin
plain English?
Click the "Show†Version List SGBD button on the â€Dienste Tool†interface. There will be a
list of all SGBDs by name with the current version number, the person responsible at BMW,
and the name of the associated controller. It is only possible to access the version list when
the network is in operation or it can be viewed at \\smuc0900\Referenz\Referenz.sgbd.
4.14 What is a Job?
Jobs are services that EDIABAS provides. They aren't hard coded inEDIABAS,but are a
maincomponent of each SGBD.
Each job has a fixed name and any number of results. Jobs are independent of each other.
There is no data exchange between jobs.
A job corresponds to a function with one complete order. It usually reads data from a
controller,analysesit and returns results that can be used directly by different applications.
A job normally works with one diagnostics telegram (multiple in exceptional cases).
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage29of32
TI-430 Andreas Schandl Release date: 29.09.2006
4.15 What do SGBDs with the name _xxx mean?
SGBDs that begin with "_†(e.g. _LWS5), contain jobs that are only intended for development
(e.g.: writing the ident data). These SGBDs are not used in production or in customer service.
4.16 What is the group file used for?
Among other things, INPA uses group files to select the respective SGBD. The group
identifies the controller and starts the corresponding SGBD. The choice is made using the
diagnostics, and as of E65 using the variation index in addition.
The group files are located in C:\EDIABAS\ECU and have the following naming convention:
D_00xx.grp were assigned up to the E65; xx = the controller address; For example:
D_0032.grp = transmission. The name D_??????.grp is assigned after the E65 and is
legible; for example D_KLIMA.grp or D_MOTOR.grp, etc.
Updating the group files as of the E65 has changed since February 2004. The table with the
information about which controller must load which SGBD, depending on the diagnostics and
variation index, was moved from the group file to an external table. At runtime, theswappedout
table C:\ECU\T_GRTB.prg is used. Therefore, it is now only necessary to update this
table and not D_??????.prg.
Additional Information for SGBD Developers:
In the file STD_GRTB.b2s, the diagnostics andvariationindexes of the individual SGBDs
can be seen as well as the group file to which the respective SGBD is assigned. You can
find the file STD_GRTB.b2s on drive \smuc0900\sg\ in directory \Referenz\Ediabas\Include\.
4.17 Diagnostics Index
- a) Who creates it? Reinhold Drexel, TI-430
- b) What is it used for? Identification of the controller
- c) When does it change? When a new SGBD is due
4.18 Variation Index
- a) Who creates it? Data handling team
- b) What is it used for? Identification of the ECU
- c) When does it change? When the SGBD and/or the PABD changes (PABD, if
something in ECU programming changes), e.g. if the
authentication changes or a timing has changed).
4.19 What is the meaning of the file EDIABAS.ini?
Ediabas.ini is the configuration file. Normally, no changes must be made here after the
installation. One reason for a change to Ediabas.ini is, for example, if you want to work with
a simulation file, i.e. there doesn’t have to bea ECU.
The Ediabas.ini can be found in the \Ediasbas\Bin directory.
EcuPath:
The group files (d_*.grp) and SGBDs (*.prg) are found in the path given for EcuPath. In the
developer versions, it also contains *.b2v, *.b2s and *.txt files.
SimulationPath:
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage30of32
TI-430 Andreas Schandl Release date: 29.09.2006
The path given in the SimulationPath is where the simulation files are located for groups
(d_*.sim) and for SGBDs (*.sim), whichareonly relevant to SGBD and INPA developers.
TracePath:
If ApiTrace and/orlfhTraceare activated, then the traces will be stored there with api.trc and
ifh.trc.
TraceSize:
You can set the size of the trace files ApiTrace and IfhTrace. If 1024 is set, then the
maximum size of the file is 1 MB; for 512, it is a maximum of 500 KB.
ApiTrace:
The ApiTrace file is activated by replacing the zero with a number from 1 to 7. The api.trc file
contains the job and result names with their data. If ApiTrace is not needed, this should be
set to zero to increase the performance of EDIABAS. You can find information about the
trace level in the Ediabas documentation.
IfhTrace:
ThelfhTracefile is activated by replacing the zero with a number from 1 to 3. The ifh.trc file
only consists of the telegrams that have been sent (INPUT) and received (OUTPUT). If
lfhTraceis not needed, this should be set to zero to increase the performance of EDIABAS.
Simulation:
Simulation is used to check the SGBDs and INPA scripts without being directly connected to
a ECU. This function is activated by changing the zero to 1.
Interface:
You can directly change the interface here. You only have to make the appropriate change
to the line where the interface is entered.
Example:
Interface =STD:OBD, i.e the OBD interface will be used.
Interface = ADS, i.e the ADS interface will be used.
The prerequisite is to have the appropriate driver installed for the interface.
Excerptformthe Ediabas.inifile:
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage31of32
TI-430 Andreas Schandl Release date: 29.09.2006
4.20 How is the simulation file connected to the trace file?
There is one simulation file for each ECU. In this file are the ECU’s request and reply
telegrams. This file has the same name as the ECU description file,howeverit has the
ending "*.SIM†(e.g. DME31.SIM).
There is also a separate simulation file for each interface that is to be simulated. The
filename is made up of the name of the interface with the ending "*.SIM†(e.g. EDIC.SIM).
The setting of the EDIABAS configuration element calledInterfacewill be used as the
interface name. The interface-specific return values are in the interface simulation files.
The trace file records the telegrams that have been sent (INPUT) and received (OUTPUT).
The recording of such traces can be enabled in the Tool Set in the menu bar under
"Configuration†as well as in the Ediabas.iniconfiguration file.
A simulation file can be automatically created from the ifh.trc trace file by using
trace2sim.exe. This tool is found in \\smuc0900\sg\Ediabas\Sim\ trace2sim.exe.
4.21 Why have an XBD Generator?
Before the introduction of the SGBD generator, the source code was edited with a text editor
(up to 40,000 lines). For this purpose, it was necessary to learn the special, C-based
programming language BEST/2 (description language for ECU). Manual programming is
known to be very prone to errors (copy & paste), and it is very difficult to implement the
guidelines specified in the diagnostics specification sheet part 5 as the SGBD becomes
larger.
Now, the SGBD Generator is to be used to create an SGBD by means of menu-driven input
of the data, in which the BMW guidelines are kept. This should result in less effort for the
developer, but it definitely requires a certain amount of practice in working with the SGBD
Generator. A major advantage is the automatic integration of standard ‘include’ files,
whereby new standard ‘includes’ can be added without further ado (new sample XML).
4.22 What are the prerequisites for remote access via TCP/IP?
EDIABAS for WIN32 makes it possible to access the diagnostics interfaces and the attached
ECUs that are connected to another PC. The prerequisite for this is a network connection of
locally and remotely controlled PCs via TCP/IP as well as a WIN32 operating system that is
supported by EDIABAS.
Applications and EDIABAS run on the local PC and the interface handler (IFH) as well as the
IFH-Serverrunon the PC to be remotely controlled. Before accessing the remotely
controlled PC, the IFH server IFHSRV32.EXE must be started. The remote control is
activated,or alternatively controlled using the EDIABAS configuration file EDIABAS.INI. The
EDIABAS configuration must be performed manually on both PCs.
The EDIABAS configurationsTracePathandSimulationPathare not transferred from the
local PC to the remotely controlled PC, rather the respective configurations of the
EDIABAS.INIfile that is on the remotely controlled PC is used.
The network protocol TCP (NetworkProtocolentry) as well as a freely selectable port
number must be given on both PCs. The port number must be identical on both PC and
must not collide with other TCP applications (1000 < port number < 30000).
Frequently Asked Questions
BMW Group about
EDIABAS, INPA and the Tool SetPage32of32
TI-430 Andreas Schandl Release date: 29.09.2006
4.23 What is the VC Tool and when is it used?
VC Tool (version check) can be used to check the versions of the files that are created
during the installation of EDIABAS. When it runs, the tool compares the files specified in the
files BMW_bin.pid,BMW_hw.pidand BMW_rest.pid with regard to their creationdataand
creation time. That way, changes made incorrectly in the EDIABAS files can be detected and
corrected.
After running, the VC Tool creates a text file called VC.log in which the comparison is given
with the specific results. This file is stored in the directory where the VC Tool is found
(C:\EDIABAS).
4.24 What is the KVP Editor?
KVP stands for continuous improvement process. The KVP Editor can be called when using
the INPA Tool. This is mainly used in reworking and in the plant. Here, the user has the
possibility to enter his name and telephone number and then enter an error description and
improvement request and then to send the form directly to the person responsible at BMW.
Source:http://blog.obdexpress.co.uk/2017/08/04/how-to-use-bmw-inpa-ediabas-5-0-2/
Posted by: OBDexpress.co.uk at
06:30 AM
| No Comments
| Add Comment
Post contains 7775 words, total size 213 kb.
August 03, 2017
2017 Tech2Win
Free download Opel Tech2WinPCMCIA V182Spanish:
Password:mhhauto.com
Free downloadTech2win 32MB PCMCIA Card V182.000English:
Part 2:
Password:
Download Tech2Win PCMCIA 32GB Card Bin FilesMulti-Language (EN; DE; FR; IT):
For all files above
Work on Tech2win only
NEVER TESTED by professionals
To avoid SECURITY issues, please go tohttp://www.obdexpress.co.uk/wholesale/tech2-diagnostic-scanner-for-gm-
Tested software includes:
Tech2Win GM English 32.007
Tech2Win SAAB English 148
Tech2Win OPEL English 165 (Cars from 1997-2014)
Tech2Win Holden English 149 (Cars from 1999-2013)
Tech2Win SUZUKI English 01.210.020
Tech2Win ISUZU English K line 11.53;
Tech2Win ISUZU English CAN line 107.021
For 12V CARsonly (no trucks)!!!
Programming withTIS2000: cars before the 2007 year
(You are taking
GM
GM-English 32.007 1991-2013
GM-Germany 32.007 1991-2013
GM-Spanish 31.007 1991-2013
OPEL
OPEL-EnglishV1801997-2014
OPEL-Italian 133.001 1997-2012
OPEL-Germany85.001 1997-2008
OPEL-Spanish 91.001 1997-2009
SUZUKI
SUZUKI-English 01.210.020
SAAB
SAAB-English 148.000
ISUZU
ISUZU-English CAN-BUS 107.021 2010-
ISUZU-English K-Line 11.62 1996-2013 (new add)
Holden
HOLDEN-English V149 1999-2013
Here are FAQs
How to get this bin file to work ?? I have tech2win working but don’t know where to copy this bin file into….??
open TECH2WIN> select option Modify/View > choose
You can change your image with this or make new configuration
OR
Just rename this bin file Quickstart.bin and swap it with your old
How the hell to combine the files back to 1 bin file??
Extract with
How to load software on a 32GB card on a Tech2 scanner?
Insert
Tech2 card writer is one of them but the method is much slower
Source:
Posted by: OBDexpress.co.uk at
03:12 AM
| No Comments
| Add Comment
Post contains 399 words, total size 38 kb.
August 02, 2017
Free download ford ids v106.01 software: only works with VCM IDS3
https://mega.nz/#!LERyzJqI!KRokMKKIbEBB-sQ44aIAscN1pffUGRpoWT5L-A3f7nk
Fordids100:100% work perfect
http://www.obdexpress.co.uk/wholesale/best-ford-
Downloadmazdaids v106 software on
nly
Mazdaids96:100% tested and works great
How to install VCM2 Fordids100 on VMware machine:
How to install Mazdaids98 on WinXP, Win7, Vmware:
Auto diagnostic & programming tool for Ford/Mazda:
VCM2 clone, VXDIAG VCX NANOford/mazda, VCM IDS 3…all ok
Ford diagnostic tool which best:
VCM2 china clone:
VCM2 sp177c or sp177c1:
VXDIAG VCX NANO ford/mazda:
VCM IDS 3:
Posted by: OBDexpress.co.uk at
09:35 AM
| No Comments
| Add Comment
Post contains 100 words, total size 17 kb.
August 01, 2017
Test
Purpose:Ride Height Calibration
Vehicle specification:
Vehicle: NAV
Engine type: 4V
Capacity: 5.4L
Transmission: Automatic
Fuel type: Gasoline
Emission level: Federal Emission
Ford diagnostic tool:AllscannerVXDIAG VCX NANO Ford
Diagnostic system:Ford IDS v86 v100 v101
Procedure: How to
Turn the ignition to the ON position
Exit the vehicle, close all doors and allow…to kneel height (approx. 45 seconds)
With the ignition ON…into DRIVE and then back into PARK
Exit the vehicle, close all doors…to trim height
(approx. 45 seconds)
Open the left front door
Measure the ride height
On the following screen, adjust the ride height and then save the newly calibrated values (while outside the vehicle)
Test result:
Ford IDS v86 Ride Height Calibration on Navigator 2004: Failed
Ford IDS v100 Ride Height Calibration on Navigator 2004: Failed
Ford IDS v101 Ride Height Calibration on Navigator 2004: Failed
Vxdiag vcx nano Ford cannot supportLincoln Navigator 2004
Error:
Error:
Error:
Posted by: OBDexpress.co.uk at
09:45 AM
| No Comments
| Add Comment
Post contains 197 words, total size 21 kb.
Here is the step -by -step procedure to updateSKP1000 Key ProgrammerFirmware online.
Before update firmware of SKP1000, please take out the TF card and insert it into the card reader, then plug into the computer USB port. Double click "My Computerâ€, find out †local Disk (H
, right click to choose "Formatâ€.
Tip: Tick on the "Quick format†and click "Start.
After complete format, go to the official site to download the update file, then copy and paste the file into the TF card,
Click on "Firmware updateâ€.
Firstly choose "System firmware updateâ€, press "Yesâ€, the
Update successfully shown as below.
Press "No†to back
Choose †Adapter firmware updateâ€,
Done.
Posted by: OBDexpress.co.uk at
02:40 AM
| No Comments
| Add Comment
Post contains 150 words, total size 4 kb.
32 queries taking 0.1089 seconds, 147 records returned.
Powered by Minx 1.1.6c-pink.
