use custom commands in the advanced tab in eehack
command like 0xE4 [length] 0x02 0x02 0x45 [checksum] will dump the memory at 0x0245 at a length of 64 bytes
you need kur4o's e-side comms patch for it to work on e-side memory, as modes 0x02 and 0x03 are disabled by default on the e-side
I`ve explored and compared alot of bins, but never found a difference in the code part, even between 94 and 95 there are 2 bytes difference in the code part and it`s mode 4 tcc dc valve related.
Did you find some vette specific code part to look at?
I can try different approach with small tables loading via command mode. The max will be 17 bytes long, even though it can be expanded.
I will use some of the aldl modes that are not used. On eside mode 07, 08, 09, 0a, 0b, 0c are not used and can be forced to do intersting stuff as code execution, loading tables, switching bits and so on. For example you send empty mode 7 request It execute some code and switch sd to maf untill memory is cleared or battery disconnected. I guess the limit will be free ram memory.
Do you think multi mode support will be possible?
it's easy to just grab data; my concern is logging the data, playing it back, graphing it, etc.Do you think multi mode support will be possible?
it has to be a fixed set of data that doesn't change all the time, since every time it changes i pretty much have to change my log format.
that'd be awesome.For example you send empty mode 7 request It execute some code and switch sd to maf untill memory is cleared or battery disconnected. I guess the limit will be free ram memory.
not really, i thought '95 y-body ecms had a bunch of weirdo error checking that earlier ones didn't.Did you find some vette specific code part to look at?
speaking of which, do you know anything about the 'vette rear o2 sensor? (there is one...) does it have an AD channel? there's no error for it...
Bookmarks