flamy
Full Member
Karma: +6/-0
 Offline
Posts: 56
|
 |
« Reply #15 on: April 08, 2017, 11:03:46 PM »
|
|
|
It's a register to (de-)activate each output stage of the ECU.
|
|
|
|
|
Logged
|
|
|
|
QuickS4
Full Member
Karma: +6/-6
Offline
Posts: 72
|
|
« Reply #16 on: April 08, 2017, 11:30:19 PM »
|
|
|
Wait, it runs in CMD? My brain is tired hahaha
Sent from my Pixel XL using Tapatalk
|
|
|
|
|
Logged
|
|
|
|
|
SB_GLI
|
|
« Reply #17 on: April 09, 2017, 07:04:08 AM »
|
|
|
I've had mixed results on a few bins I tried this on. In some cases, it will incorrectly detect eskonf, it others it will detect the correct one, but also find another incorrect eskonf. Attached is an 032HS. This one does find eskonf, but it also finds anot
I find it just easier to manually find eskonf anyway. It's always right before kfkhfm, which is a super easy map to find.
|
|
|
|
|
Logged
|
|
|
|
rotax
Newbie
Karma: +10/-0
Offline
Posts: 22
|
|
« Reply #18 on: April 09, 2017, 03:07:08 PM »
|
|
|
The tool is only made to find ME7.5 ESKONF in 4 cylinder bins.
What kind of bin files did it fail on? (examples please...)
Due to the way it searches it sometimes do find byte groups that are false positives or at least not the primary ESKONF, i've seen up to 3 ESKONF hits in one file.
2 of them seems legit as an ESKONF but the third one is wierd.
I do find it really unplausable that there would be just random byte groups that really matches the rules, they are most probably variants of ESKONF settings used in certain situations, variant coding could perhaps explain their existence.
|
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #19 on: April 09, 2017, 03:15:50 PM »
|
|
|
I do find it really unplausable that there would be just random byte groups that really matches the rules, they are most probably variants of ESKONF settings used in certain situations, variant coding could perhaps explain their existence. i ran the tool and it said the eskonf was in 29xxxh range. totally wrong. also, apparently vdubnation did not read his output before commenting on the tool "works awesome", because his address is 4xxxh. most definitely not correct either. |
|
|
|
|
Logged
|
|
|
|
hopsis
Full Member
Karma: +13/-4
Offline
Posts: 174
|
|
« Reply #20 on: April 09, 2017, 08:34:00 PM »
|
|
|
I'm getting false results with 8 cylinder bins also. It's a nice tool anyway, thank You.
|
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #21 on: April 09, 2017, 08:43:46 PM »
|
|
|
I'm getting false results with 8 cylinder bins also.
He mentioned it was only meant for the 4 cylinder bins. |
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
nyet
|
|
« Reply #22 on: April 09, 2017, 08:56:34 PM »
|
|
|
For the record, this sort of tool is VERY hard to make general.. i spent weeks on me7sum to work with a variety of binaries.. just supporting all of the 2.7t variants was hard enough.
That said, though, looking at the source, there might be an easier way to detect where eskonf is based on looking for ASM calls instead of map value matching.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
flamy
Full Member
Karma: +6/-0
Offline
Posts: 56
|
|
« Reply #23 on: April 10, 2017, 01:51:55 PM »
|
|
|
I'm getting false results with 8 cylinder bins also. It's a nice tool anyway, thank You.
6/8-cylinder ECUs have a larger ESKONF register that is not compatible to the ones of the 4-cylinder ECUs. |
|
|
|
|
Logged
|
|
|
|
hopsis
Full Member
Karma: +13/-4
Offline
Posts: 174
|
|
« Reply #24 on: April 10, 2017, 08:39:14 PM »
|
|
|
Yep, 13 bytes I believe.
|
|
|
|
|
Logged
|
|
|
|
flamy
Full Member
Karma: +6/-0
Offline
Posts: 56
|
|
« Reply #25 on: April 11, 2017, 01:59:24 PM »
|
|
|
Yep, 13 bytes I believe.
Right. |
|
|
|
|
Logged
|
|
|
|
pedrosousa
Full Member
Karma: +3/-0
Offline
Posts: 75
|
|
« Reply #26 on: September 09, 2017, 08:50:46 AM »
|
|
|
Is normal to have a report of 3 ESKONF locations?
The file it's a 4B0906018DH 366497
|
|
|
|
|
Logged
|
|
|
|
|
vwnut8392
|
|
« Reply #27 on: November 06, 2017, 01:49:47 PM »
|
|
|
Very cool tool! Great work!
|
|
|
|
|
Logged
|
|
|
|
Borg
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #28 on: September 09, 2018, 01:46:05 AM »
|
|
|
sequence FF FF 00 F0 3F F0 2C found at some address A is false positive,its part of some subroutine @ A-0x59 or near.
|
|
|
|
|
Logged
|
|
|
|
360trev
Full Member
Karma: +68/-2
Offline
Posts: 235
|
|
« Reply #29 on: October 12, 2018, 09:57:25 AM »
|
|
|
I've just had to implement this for the Ferrari specific DEKON function which has both ESKONF_L and ESKONF_R (left and right banks) using dual ecu concept, however inspecting DEKON on other variants there aren't that many different versions which means you can get pretty good support by using a needle/mask to find the DEKON code which references the ESKONF. Then extract value and segments and derive offset directly to the ESKONF data. This is the guarenteed way to make it work reliably without any false positives.
Take a look at source-code on my github for the Ferrari Swiss Army Knife tool. I haven't yet done other non Ferrari variants yet but if there is any interest let me know and I'll look into it...
|
|
|
|
|
Logged
|
|
|
|
|
