Hiiiizzzaaahhhh i finally figured out how to do it!!!!
#3
Burning Brakes
Thread Starter
for a '91....
a) i needed a GP1 adapter...
b) some spare (1) 27sf512 chips to burn and reflash...
c) discover said chips are fake knock offs that moates knew about and still sent out, used said chips anyways...
d) an HDR1 connector to get original programming off of the memcal...
e) an APU1 emulator/reader/writer...
for aldl reading - inside software issues of tunerprortv5 I had to
a) get the super_8dm2.xdf file
b) 1227730_8d.adx file
c) these were converted over from the:
super_8dm2.ecu file...
1227730_8d.ads file...
d) i had to modify the ADX file...
under: Acquisition, expand commands cross, select mode 1 aldl dump request, change Body Size (Dec) to 67 (from 66).
e) in tools, preferences, data acquisition/eumlation, change: "configure plug-in componet", from serial data acquisition to shared with emulator.
f) tools, start/stop data scan. (it may have auto-connected on it's own anyways at the point in time i changed the preferences options...)
this got me to reading with aldl cable on the apu1 I did not attempt to record the log file yet, but it did give me access to realtime updates thought the aldl cable.
for aldl reading and logging - under tunerprortv4
A) same crap... need a .xdf file, and an .ads file, BUT - it has to be a tunerprortv4 file. (however there is no need to convert)
B) i had to change under preferences, aldl/emulation, from MAX232 to autoprom.
C) tools, to ALDL logging, setup, then there is a select log file option (though there wasn't a create log file option...)
D) click the: select log file, create: a new log file.
E) open the new log file you created and start recording the log file in that. (you will get an error if you just try to hit record as it wont know where your recording too nor have a loaded log file)
for reading, erasing or burning,
under either tunerprort v5 or v4,
a) tools, moates PROM/IO option, put in blank chip into zif socket on apu1.
b) read chip. save buffer to file..
c) load buffer file under, file, to open .bin file.
d) edit said .bin file.
e) save said .bin file.
f) tools, moates PROM/IO option, load file to buffer, select said .bin file, erase chip, program chip, verify chip w/ buffer
e) place chip in GP1 adapater
f) figure out which end is up
g) stick memcal onto GP1 adapter
h) stick adapter into car
i) f*cking panic and pray motor doesn't blow up
j) turn key, start engine.
to read stock memcal see, options about reading chip inside moates utility.
a) use the HDR1 adapter to read the .bin file off the stock memcal.
b) spend 5 hours figuring out above said options, figuring out which end is up, and which ways to have the little buttons at the back of the APU1 set when doing the above said steps.
(note: you cannot reprogram the stock memcal either, i tried... several times... on accident, lol.)
a) i needed a GP1 adapter...
b) some spare (1) 27sf512 chips to burn and reflash...
c) discover said chips are fake knock offs that moates knew about and still sent out, used said chips anyways...
d) an HDR1 connector to get original programming off of the memcal...
e) an APU1 emulator/reader/writer...
for aldl reading - inside software issues of tunerprortv5 I had to
a) get the super_8dm2.xdf file
b) 1227730_8d.adx file
c) these were converted over from the:
super_8dm2.ecu file...
1227730_8d.ads file...
d) i had to modify the ADX file...
under: Acquisition, expand commands cross, select mode 1 aldl dump request, change Body Size (Dec) to 67 (from 66).
e) in tools, preferences, data acquisition/eumlation, change: "configure plug-in componet", from serial data acquisition to shared with emulator.
f) tools, start/stop data scan. (it may have auto-connected on it's own anyways at the point in time i changed the preferences options...)
this got me to reading with aldl cable on the apu1 I did not attempt to record the log file yet, but it did give me access to realtime updates thought the aldl cable.
for aldl reading and logging - under tunerprortv4
A) same crap... need a .xdf file, and an .ads file, BUT - it has to be a tunerprortv4 file. (however there is no need to convert)
B) i had to change under preferences, aldl/emulation, from MAX232 to autoprom.
C) tools, to ALDL logging, setup, then there is a select log file option (though there wasn't a create log file option...)
D) click the: select log file, create: a new log file.
E) open the new log file you created and start recording the log file in that. (you will get an error if you just try to hit record as it wont know where your recording too nor have a loaded log file)
for reading, erasing or burning,
under either tunerprort v5 or v4,
a) tools, moates PROM/IO option, put in blank chip into zif socket on apu1.
b) read chip. save buffer to file..
c) load buffer file under, file, to open .bin file.
d) edit said .bin file.
e) save said .bin file.
f) tools, moates PROM/IO option, load file to buffer, select said .bin file, erase chip, program chip, verify chip w/ buffer
e) place chip in GP1 adapater
f) figure out which end is up
g) stick memcal onto GP1 adapter
h) stick adapter into car
i) f*cking panic and pray motor doesn't blow up
j) turn key, start engine.
to read stock memcal see, options about reading chip inside moates utility.
a) use the HDR1 adapter to read the .bin file off the stock memcal.
b) spend 5 hours figuring out above said options, figuring out which end is up, and which ways to have the little buttons at the back of the APU1 set when doing the above said steps.
(note: you cannot reprogram the stock memcal either, i tried... several times... on accident, lol.)
Last edited by mistaben; 09-04-2011 at 07:49 AM.
#4
Burning Brakes
Thread Starter
-> lol... try and find steps that succinct else where on the internet... a lot of reading, alot of advice, alot of emails, and even some phonecalls to get that to work.
now onto my tuning questions....
there seriously has to be an easier way to map this out in excel and use some kind of auto macro function to chop the excel datalogs, average em, auto calculate a VE number for me, and then break it down by RPM's and kPA.... man I wish i would have paid attention in my finance classes in college. they were all excel based courses too, and I didn't learn a darn thing on how to use excel....
however I am still talking with the GF that I would like to make a wife. *shrugs* I guess you have to have priorities.......
Last edited by mistaben; 09-04-2011 at 07:59 AM.
#5
Le Mans Master
Member Since: Aug 2000
Location: Sydney Australia
Posts: 8,837
Likes: 0
Received 30 Likes
on
29 Posts
#6
Burning Brakes
Thread Starter
this was the correct definition filed pulled off their site right? even though it opens as a .pdf then open an autologtune from datamaster
and enter in a target blm of 128?
http://www.tunercat.com/pdfs/ecm_$8d.pdf
or do I have to purchase this:
http://www.tunercat.com/ $8D definition file?
why does it give me an adjustment of 1 across all ranges? or is it finished? i just punch in the new VE tables and be done with it? - it can't be that easy... that doesn't make any sense either it says I have a dead spot in my engine then...
like a VE of about 0% in the area of 2000RPMS and 50kpa.... then scales back up to 80% and 90% on either side of the kpa graph. bad log file I have some logs with the motor off//not running... or a bad definition file?
so wait what does this do? is this for LT1 engines only? it doesn't do l98 engines then?
and enter in a target blm of 128?
http://www.tunercat.com/pdfs/ecm_$8d.pdf
or do I have to purchase this:
http://www.tunercat.com/ $8D definition file?
why does it give me an adjustment of 1 across all ranges? or is it finished? i just punch in the new VE tables and be done with it? - it can't be that easy... that doesn't make any sense either it says I have a dead spot in my engine then...
like a VE of about 0% in the area of 2000RPMS and 50kpa.... then scales back up to 80% and 90% on either side of the kpa graph. bad log file I have some logs with the motor off//not running... or a bad definition file?
so wait what does this do? is this for LT1 engines only? it doesn't do l98 engines then?
Last edited by mistaben; 09-04-2011 at 07:32 PM.
#8
Burning Brakes
Thread Starter
they apparently got a bad batch from somewhere and shipped them out anyways. let me see if I can find the link to where it said that.