Dorny1
Jr. Member
Karma: +0/-0
 Offline
Posts: 31
|
 |
« on: March 06, 2013, 10:08:14 PM »
|
|
|
says i need a bin file with the ecu swnumber of 1027260857...I have a 2001.5 Audi S4, and it's, dare i say it, VAST tuned...
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #1 on: March 06, 2013, 10:12:18 PM »
|
|
|
So read your binary from your ecu and use that? What's the issue?
Failing that, what's the vag-number of the ecu? You may be able to find a stocker that would work.
|
|
|
|
|
Logged
|
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 experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
|
nyet
|
|
« Reply #2 on: March 07, 2013, 10:31:24 AM »
|
|
|
says i need a bin file with the ecu swnumber of 1027260857...I have a 2001.5 Audi S4, and it's, dare i say it, VAST tuned...
use VCDS to find out which version it is and download it here http://nyet.org/cars/files/stock |
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #3 on: March 07, 2013, 10:32:39 AM »
|
|
|
I'm kinda thinking VAST changed the sw number.
1037360857 is an m-box, I haven't found any reference to the number he posted.
|
|
|
|
|
Logged
|
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 experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
|
nyet
|
|
« Reply #4 on: March 07, 2013, 10:34:43 AM »
|
|
|
I'm kinda thinking VAST changed the sw number.
1037360857 is an m-box, I haven't found any reference to the number he posted.
i'm guessing the OP just made a typo... |
|
|
|
|
Logged
|
|
|
|
Dorny1
Jr. Member
Karma: +0/-0
Offline
Posts: 31
|
|
« Reply #5 on: June 13, 2013, 03:24:12 PM »
|
|
|
I'm going to give it another whack here tonight at the track. I think they encrypted it and thats why...however still doesn't make sense why i cant just pull the logs off of it.
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #6 on: June 13, 2013, 03:43:59 PM »
|
|
|
What's the error?
If it's for software mismatch it tells you exactly what you need to change it to.
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #7 on: June 13, 2013, 03:45:54 PM »
|
|
|
I'm going to give it another whack here tonight at the track. I think they encrypted it and thats why...however still doesn't make sense why i cant just pull the logs off of it.
No one is encrypting anything that would prevent logging. |
|
|
|
|
Logged
|
|
|
|
Dorny1
Jr. Member
Karma: +0/-0
Offline
Posts: 31
|
|
« Reply #8 on: June 13, 2013, 03:52:12 PM »
|
|
|
Didn't think that would stop logging, but once again it's been awhile and i'm looking at working with it tonight at the track, to see how its running.
|
|
|
|
|
Logged
|
|
|
|
Dorny1
Jr. Member
Karma: +0/-0
Offline
Posts: 31
|
|
« Reply #9 on: June 13, 2013, 04:33:55 PM »
|
|
|
No luck...kind of stuck used the how to on audizine, found its a 8D0907551M through VCDS. Yet no success...DAMN VAST!
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #10 on: June 14, 2013, 05:12:02 AM »
|
|
|
No one is encrypting anything that would prevent logging.
Really?  Disable WriteMemoryByAddress and EcuX and ME7L go the way of the dodo. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #11 on: June 14, 2013, 05:34:46 AM »
|
|
|
Really? Disable WriteMemoryByAddress and EcuX and ME7L go the way of the dodo. I didn't say it wasn't possible just that no one does it. Why would you? I doubt that Vast disabled it only on his car. |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #12 on: June 14, 2013, 10:21:52 AM »
|
|
|
I didn't say it wasn't possible just that no one does it.
Why would you?
I doubt that Vast disabled it only on his car.
It is incorrect that "no one does it". As to why would you - it's very easy to read the ECU if you have access to writeMemoryByAddress as things are executed from RAM. You can upload a subroutine into RAM and then run it which will dump for example contents of entire memory over OBD II, and this is how some tools read and write these ECU's. If you want to stop people easily reading your tune via OBD you have to do this. Basically if ME7Logger works on an ECU, you can dump everything over OBD. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #13 on: June 14, 2013, 11:13:58 AM »
|
|
|
I can tell you for a fact that isn't his problem.
I also think that you would lose alot of customers on this platform by doing that. There's other ways to block OBD reading that leave this intact although that obviously wouldn't prevent reading as you described.
Blocking reading is pointless anyway. Encryption is the only worthwhile attemp at tune protection IMO.
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #14 on: June 14, 2013, 11:18:27 AM »
|
|
|
His problem is most assuredly a software mismatch. He just needs to edit the ecu file with his specifics. Super easy stuff.
Has anyone else noticed that most (I want to say all, but I haven't checked) of the ram variables are in the same place across different flash numbers?
|
|
|
|
|
Logged
|
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 experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
|
