-
Next might be a test write but I don`t recommend you try it yet if it is not urgent.
Polishing the definition file will be a short term project so you can have a good logging tool.
Did you managed to connect to the test bench pcm? Are both the same service number.
-
I don't plan on doing anything with the one in my car, next week things are supposed to start opening up around here. I will go pick up a couple of spares from the salvage yard to practice with. Polishing the definition file; Is that something you are working on or do I , I'm still really green at this. Haven't messed with this bench anymore yet. Thanks again for all your help.
-
1 Attachment(s)
Today I was able to connect to my bench unit and download the bin, I think it may be the same as mgb1 since the same guy tuned both of them. I think the bench unit has a bad injector driver as it will only fire 3 injectors.
-
Went out twice today to log data with eehack_v6 and when i tried to disconnect it locked up and would not respond. both times it eventually closed without saving data. I've done a couple of short runs and it worked fine.
-
Try saving the logs before disconnecting. Actually I never tried to disconnect first and save later, so don`t know if it is normal behavior.
Can you a test a connect disconnect button without logging. Just press connect and when it is connected press disconnect. DOes it freeze again. If it is there is some bug in the program or again win10 issue.
A quick compare of the files shows that they are tuned differently or one is stock the other modded.
I will polish the def file when I get a chance so you can log some good viable data.
-
just so you know i'm 50% of the way towards making flashhack work with your V6. it should be really safe as long as you don't cut ECM power. i'll let kur4o test it before anyone else though
-
The first test tries in the garage without data logging when I would close the program it would ask if I wanted to save logs so that's how I have been doing it. On the two short drives it worked fine the longer drives (30+ minutes) is when I had problems. I will try again later today.
-
I have one with a bad injector driver that I will practice on and then pick up another good one to practice with.
-
Remember too, the 93's are not the same PCM as the 94/95 PCMs. It uses specific programming, and while the Winflash OBDII tool will program it, the Tunerpro ADX will work, the XDF will NOT WORK with anything 1993 other than the W-body 3100 engine PCM.
You may need to get a 94/95 PCM if you want to get into it too far.
-
Did some more data logging, still have a couple of issues and questions. Still having a problem with eehack freezing up on longer runs,not always able to save logs.
Would like to be able to maximize the screens, top down in direct sunlight it is almost impossible to see.
When using the analyzer, is it possible to select a single log rather than analyze all logs?
-
Figured out how to analyze individual logs.
-
Did some more data logging and playing with trimalyzer. Was able to analyze logs and load into tuner pro and modify ve table. unable to load new modified bin into eehack_v6. Not $EE bin.
Saw that the knock count was extremely high(over 5000) still using the stock sensor for the 3400, ordered one for a 3.4.
Still reading and learning.
-
the knock count itself means nothing, it depends how many knocks occur. a single knock event can show up as thousands of counts
eehack's analyzer should map your knock events so you can see where they occur and how severe they are
-
95 minutes of logs, 369,076 counts and 800 events.
Reading the OBD1 swap article says the knock sensor should match the car the ECM came out of. I figured I would do that first.
-
Tried more data logging tonight, if I go longer than about 10 minutes EEHACK_V6 freezes and will not respond and I lose the data for that run. If I stop and save the log along the way it's ok, but if I go too long it will not respond. "EEHACK not responding"