pcmhacking.net

I tested e92 DTC and it worked flawless. The e38 code offset is broken. Didn`t identify correctly when the 10000 offset is needed. I will get you some e92 for future use, and the odd ball e38 that didn`t need offset.

kur4o wrote:The e38 code offset is broken. Didn`t identify correctly when the 10000 offset is needed.

0.15.15

"Fixed" with hack: Try to use offset -0x10000, but if first PID is > 0x10, don't use.

Good work. I hope that e38 issue is not widespread with other pcms and hope I can finally figure the pattern of offset vs no offset.

It will definitely help with table discovery since there is also some random -$10000 offset used.

It seems the find PIDs isn't working anymore on p1-p59. I can get other versions to work but none of the latest.

0.15.16

PID search -button removed and search made automatic.

joukoy wrote:0.15.16

PID search -button removed and search made automatic.

I think a checkbox will work better, for manually turning it off.

I found some bug for dtc search that mess the search only on v6 1mb for some reason and it looks like it is an old bug. It does find the mil status correctly but at the end some FFFFFFFF comes from nowhere.

On the debug log it is
mil start:good
mil end:good
mil start:good
mil end:good
MIL:FFFFFFFFF

That ffs come from nowhere.

On the seek table can we improve it with adding some notes field, that will display data for rows and ram address. We can go even further and if the ram address is matched with some of the pid search, fill the note box with the extra pid info.
for example rows:xx;ram1:a876:pid-number:pid name;ram2:a897:pid-number:pid-name

On the seek config some dispay only row characheter can be implemented

For example 34 74 [r]19 4e b9 or 34 74 [r]* 4e b9
[r] can be something else and it will display the rows of the table in decimal

[r1] * * or [r1] a1 76 will display the ram1 address
[r2] * * or [r2] a1 87 will display the ram2 address

The config is your choice. It can use some of the config logic of the table search for compatability or make a new set.

I think the table search misses only the display only as row. It must be * to get it displayed correctly in row column.

Edit: The dtc search bug is found at version 15.11-on.

Also found some e67 bins that dtc search code offset is not applied correctly.
Since your at dtc already I guess a separate settings for code offset for dtc table and dtc search, and some better logic, or better hack patch.

0.15.17

dtc search bug fixed
Added basic row search functionality, for example:
34 74 r 19 4e b9 or 34 74 @ @ @ @

There was already possibility for "a separate settings for code offset for dtc table and dtc search"
You can add one value or comma separated values to "conditionaloffset", for example:
code,status,mil
code,mil
status

I tried the row search, but can`t seem to configure it right.

The string I test was for mbt spark on ls1

74 19 20 7c @ @ @ @ 4e b9 * * * * 36

19 is the rows

I tried

74 r @ 20 7c @ @ @ @ 4e b9 * * * * 36
74 r@ 20 7c @ @ @ @ 4e b9 * * * * 36
74 r19 20 7c @ @ @ @ 4e b9 * * * * 36
74 r 19 20 7c @ @ @ @ 4e b9 * * * * 36

No one seems to work. It doesn`t find the table so I guess it is something with the syntax.

Should I restart the program between seek-table.xml save or it is reladed automaticaly on opening the file.

The v6 1mb dtc search now work as expected.

kur4o wrote:I tried the row search, but can`t seem to configure it right.

The string I test was for mbt spark on ls1

74 19 20 7c @ @ @ @ 4e b9 * * * * 36

19 is the rows

I tried

74 r @ 20 7c @ @ @ @ 4e b9 * * * * 36
74 r@ 20 7c @ @ @ @ 4e b9 * * * * 36
74 r19 20 7c @ @ @ @ 4e b9 * * * * 36
74 r 19 20 7c @ @ @ @ 4e b9 * * * * 36

No one seems to work. It doesn`t find the table so I guess it is something with the syntax.

Should I restart the program between seek-table.xml save or it is reladed automaticaly on opening the file.

The v6 1mb dtc search now work as expected.

Use:
74 r 20 7c @ @ @ @ 4e b9 * * * * 36
... But you get hit from different address than
74 19 20 7c @ @ @ @ 4e b9 * * * * 36

TableSeek.xml should be reloaded automatically