Tests fine on voltmeter. Voltage appeara to vary linearly, ohms are within spec. Whole different picture thru pcm. Blips between 0 and 31%. IAT was also drifting all over the place. Iat tests bad. Figured that was problem but still have TPS drift with IAT disconnected. Idles at 1550 showing target idle of 4500 or so. Ive checked grounds, power connections. Going to replace iat connect vss and hope for less wierdness. Im not sure what to make of it all.
Steve, FYI, I just uploaded a tune to a B-body PCM (94 Roadmaster wagon) that I had previously uploaded a tune using EEHack 4.0 in december 2015. It took several attempts before I could read successfully due to Mode 13 (Security?) failures, and I was unable to write using EEHack 4.0 because of continual Mode13 failures. So I downloaded EEHack 4.6, selected B-body and attempted to connect but I couldn't. So I selected F-body and was able to connect, read and flash just fine.
EDIT - This was using a direct programming harness I built between the PCM and the laptop, NOT through the vehicle.
Last edited by sherlock9c1; 09-01-2016 at 09:21 PM.
Hi Sherlock, wondering if you're missing syracuse at all and the snow? Should be starting soon :) I just downloaded it last night too. Just to get a looksee in the house. Does it let you the scalars and tables like TunerPro does? Seems like mostly logging, loading and reading. And some very basic settings. Couldn't find anything 'deeper' Is there a trick?
There is a lot to read in this post but i wanted to ask? is anyone working on the EE Hack XDF for the 2bar ve tables and spark tables? I know Cats offers a 2bar file in which i have but with the success of EE hack and the nice logger is there a way to implement into the XDF and the datalogger?
i've tuned a few 2 bar lt1s and i just do it in my head, dividing by two is just too easy
if you wanted to just rename the table columns to make it easier to view that'd be nice too, post your work so we can all benefit. i could do it myself if there was enough demand.
as far as eehack goes, that'd be easy for the most part. the definition is human readable, just find the map conversion values and change the multiplier. but that doesn't deal with the analyzer, of course... if that's really important i'll consider doing it too?
Update: After removing the three fuses I mentioned above, I was able to use eeHack to flash a tune in my car. So its stable enough to do that when the offending systems have been silenced.
Hmm i thought the cats file had more resolution but i guess not its still bound to 16 columns. I guess the scalling could work but would be nice if we could patch to 2bar and not have to do the math. I also am not at all any good at coding, so if i mess with your code im sure id wreck it and my computer would explode.
increasing the table resolution is possible, you need a space big enough for the larger table, then simply move it and reconfigure it. the benefit would be minimal as map isn't used at a very high resolution anyway.Hmm i thought the cats file had more resolution but i guess not its still bound to 16 columns. I guess the scalling could work but would be nice if we could patch to 2bar and not have to do the math. I also am not at all any good at coding, so if i mess with your code im sure id wreck it and my computer would explode.
why don't you just edit the tables you want to change and enter the new column values? it'll be really easy. you can manually copy the column values out of tunercat's 2 bar definition file if you want to avoid doing the math, they'll be the same.
Attachment 10935
i wish we could figure out what those systems are and how to silence them...Update: After removing the three fuses I mentioned above, I was able to use eeHack to flash a tune in my car. So its stable enough to do that when the offending systems have been silenced.
Posting Permissions
Reply With Quote
Bookmarks