View Single Post
      07-09-2022, 06:29 AM   #1
m_fife
First Lieutenant
m_fife's Avatar
United_States
123
Rep
339
Posts

Drives: 2018 M5
Join Date: Jan 2013
Location: USA

iTrader: (0)

ISTA Tuning Detection

There has been a lot of speculation in many threads on how BMW detects tuning flash and piggybacks. In this thread (https://f90.bimmerpost.com/forums/sh....php?t=1932870) I got the idea to run the tune detection job in ISTA on my M5 and review the logs, as I am not (and have not) been tuned I've got no issue running the job.

Before we get into the log files I want to give a quick background on how BMW does tune detection it is a 2-step process. The first happens the moment they plug the car in and ISTA downloads the FASTA data. An initial tuning check is run, if this flags as tuning possible I believe it will add TDX03 to the Vehicle Order (VO). This is similar to the TD1/TB1/TG1/TE1 process with Audis.

If the initial tuning check suspects tuning, the tech will run ABL-DIT-AS1214_TD_BASIC (See screenshots). This will conduct a detailed data pull from every module in the car, it took 30 minutes on my car over ENET (may be faster with an ICOM).

When everything is done ISTA will compile a .zip.log data package containing many log files. The most relevant file is the IstaOperation log. It contains both the initial operation (in cleartext) and the data dump (raw data). So here we go:

Initial Check:
2022-07-08 12:34:06.940 INFO [T] ISTA: [16] ABL_GEN_AG9999_TD_IDENT.Datenauslesen_und_Auswerte n_VM() - LogStatement. StructuredString: Tuning detection suspicion criteria (Pre). StructureElementValues: tuning suspicion code :000000000000 0: engine ecu CAL-ID | CVN:9CF5E197 | 9CF5E197 (WH: 39318 / MM: False / low-Ilevel: False)
1: engine ecu BTLD CAL-ID | CVN:F29CDEE9 | F29CDEE9
1: engine ecu SWFK CAL-ID | CVN:9277591A | 9277591A
1: engine ecu SWFL CAL-ID | CVN:11F09478 | 11F09478
2: tuning DTCs detected in engine fault memory:no DTC found
3: tuning DTCs detected in engine secondary fault memory :no DTC found
4: programing counter engine ecu: (job answer | threshold):2 | 7.613 5: programing counter engine ecu: (calculated):2
6: calculated reprogramming engine ecu: (calculated):no flashback
7: max. temperatures in the exhaust line (TOXIPRE | TPRE): DDE8 diesel only
8: plug and play variante suspected : V1, FS: 0 / 7, IS: 0 / 5 |
8: plug and play DTCs suspected :FS: - ; IS: - |
9: speed average in relation to operating hours [km | 6 min digit | km/h]:26130 | 39318 | 6.64581107889516
10: PE [det | all]:0 | 2
11: manual detection or exclusion :- x: reason for TDX03:no reason

As for the raw data I'm going to need some help from some computer science gurus as I don't know how to do the raw byte - hexadecimal thing. If someone wants to help out I can send you the logs. I do know that once the data has been pulled it is uploaded to BMW and viewed online using a system called FBM (https://www.e90post.com/forums/showthread.php?t=651281).

I was initially going to upload the logs to the world but 1. they are too large for BimmerPost (IstaOperation log is 28mb) and I've removed my VIN from all the files, but I'm pretty sure it is stored in the raw data somewhere.

I hope this was informative for everyone and someone can help out with the detailed check.
Attached Images
  
__________________
2018 Alpine White ///M5
Appreciate 4
onfireX53618.50
ZulaM580.00
Holset275.50
FSociety3812.50