NefMoto

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...

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.

use VCDS to find out which version it is and download it here

http://nyet.org/cars/files/stock

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...

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.

What's the error?

If it's for software mismatch it tells you exactly what you need to change it to.

No one is encrypting anything that would prevent logging.

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.

No luck...kind of stuck used the how to on audizine, found its a 8D0907551M through VCDS. Yet no success...DAMN VAST!

Really? :P
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.

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.

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.

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?

if you want we can setup a remote session and i could see whats going on ?

remote works for me. However...it doesn't matter much if they'd loose customers...cause they lost a bunch and are out of business. Really hate their customer support. yeah nefmoto cant read the ecu either. I'm pretty sure its disabled so i cant adjust the tune myself which sucks but it sucks i can only log via vcds and a variable at a time.

You are mistaken, but let's leave this at that... If it's not the problem in this case, so be it, I am just saying what can be the issue in some cases.

My opinion that you would deter alot of customers is wrong?

I don't know of a single US tuner that does this.

For vendors who don't want customers with a clue anyway (they're a hassle to deal with), it makes sense.

The people who want to log are outliers anyway, especially with newer cars.

For ME7, though, i'd think that it is shifting towards real enthusiasts who DO want logging capabilities.

Still, that said, the customers who care are a minority,  IMO.

P
Keeping in context...we are talking about a B5 S4 and that is why I specifically stated "on this platform".

Indeed, 99% don't know anything about how an ECU works, and those who do and want to tinker I have special agreements with anyway.