Read the bottom of my first post. Was able to connect data only but readings are not accurate. This before the I found that the ecu was missing the WR wire on back side of circuit board.
Ok, I just saw the error connecting bit, I read in more detail now.
It sounds like echo setting in OSE plugin is not right or you have the wrong ADX. Can you post a screenshot of what it looks like while its logging and tell us what ADX you're using, and the settings you have in OSE Plugin?
"also, any links to delcohacking take me to bellet.net which does not seem right. there's a fair few links to delcohacking on the instructions im reading through."
Good spot. I have killed delcohacking.net as I dont have a https certificate for it and so it was throwing warnings and google was indexing it and sending people there instead of here. I did a search and replace across the forums to update links, but I never thought to check the PDFs for the NVRAM. I'll do that. In the mean time you can use the FAQ area (the green ? in the top right, or in my signature below my post) which has links to same places, but pointing to pcmhacking.net.
sorry for the delayed reply.
Ive uploaded 2 screen shots of the TP dash display with IGN on ENGINE OFF. im looking at the engine RPM and temps, engine is also cold, has not been started today at all.
previously ive connected with the engine running and the dash stays the same.
RPM sits at 180 but jumps to 8000 randomly.
temps are all hot
ive also put up a screen shot of the ADX im using.
1.64 hz is very very slow. And you are seeing that without errors, so its probably not anything to do with echo. But the data looks very wrong, too. I am not sure what to suggest, I've not seen a failure that looks like that before. Normally you'd get nothing, or you'd get errors. Slow speed, bad data, but no errors and non-sense data is new to me.
Are you sure its 12p? If it was connecting to the wrong OS, like 11P maybe you could get such weirdness? What is the service number of the PCM? Or perhaps a buggy version of Tunerpro? Or some other software interfering on your laptop is the more likely options. Or I guess damaged hardware before it was sold to you is also possible but that seems unlikely as its not an outright failure. Final option is electrical interference in the car, or bad ALDL connection but I also think that is unlikely as the outcome for those faults would either present as no data or errors logged by tunerpro.
Not entirely sure if it should be 11p or 12p. I picked 12p because ecu come out of a VP v6.
the service number sticker has been removed from the case so im also unsure of that as well.
I have factory reset the laptop and reinstalled all software for TP and still the same results.
Car does have a Bee-R adjustable limiter installed and some SAAS gauges.
Just swapped over to a 11p ADX to see what would happen
tired both 1 bar ADX files, both had different results. will attach screen shots.
OSE_$11P V104 1Bar.adx This adx had low speed and alot of errors, dash seemed somewhat accurate but once car was started the dash did not change.
OSE_$11P V104 1Bar Message 11.adx this adx had high speed and 0 errors but dash is no accurate.
If the computer looks square from the side, its 12P, if it looks rectangle, then its 11P. But now you are getting errors at 11P and VN fits with the square 808 type for 12P. So I guess that's not it.
Can you the delco ose flashtool and read a bin? would be interesting to see if that works and if you can read it and post it we can look if its an older version or something, as well as you have whatever was on there as a backup. If the hardware is all good (certainly not sure about that at this stage, the only think that makes me think that could be the case is that you dont get errors with the 12P adx and you do with the 11P adx which gives me some confidence in the wiring and less confidence in the data on the NVRAM) so if someones trashed it somehow before selling it you might need to flash in a fresh copy of the latest to get working. But see if you can read it first without errors before trying that then if that works and once we know whats on it we can advise what to try next.
