CK5
Register an account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members.

$E6 ~ $OE ~ $OD ~ $31 ~ $42 VE Fixer Spread Sheet

Here's 2 I built from the origanal ALDL files. One for engine and one for trans. All the ones I have seen done are seperate, I bleive data is sent on two differant outputs? Both these should work fine.

When you use then save me a datalog xdl from TunerPro for each. With datalogs I can check/test/adjust them.
 
Last edited:
Here's 2 I built from the origanal ALDL files. One for engine and one for trans. All the ones I have seen done are seperate, I bleive data is sent on two differant outputs? Both these should work fine.

When you use then save me a datalog xdl from TunerPro for each. With datalogs I can check/test/adjust them.

I'll do it tomorrow.

Thanks Mark!!
 
Mark, here is a quick 20 minute trip on the motor. I'll get the trans data later tonight.


Dave, how do you get the history gram to populate the fields? I have that small log I attach to this post but I can't figure out how to get the BLMs to populate.
 
Should popoulate when recording... but gone when you stop and save recording. Then run recording again and this time get them or export the log as file for excell. csv I think is the format.
 
Wow, doesn't seem like there is a file attach to that post. Let me try again.

The BLMs don't populate while replaying the datalog.


Here is the engine log.


I can get the log to play back. I do not get the history tables to populate. I was able to export the data log file to an excel .csv. I think, at this point, I'd choose DataMaster for the 7060.

dave w
 
I can get the log to play back. I do not get the history tables to populate. I was able to export the data log file to an excel .csv. I think, at this point, I'd choose DataMaster for the 7060.

dave w

Yeah, I pretty much use that all the time. What I really want is to get the 45kpa out of TP.
 
Since you got a good excell csv file I looked at some of the settings in that ADX and changed them. It was getting a glitch from something in the datastream. Here is a new one if and when you have time to try it?
 
Last edited:
Since you got a good excell csv file I looked at some of the settings in that ADX and changed them. It was getting a glitch from something in the datastream. Here is a new one if and when you have time to try it?

I tried the new V2.adx. I used the same data log from the previous post. I am not able to see the history tables populate.

dave w
 
Well that was my first attempt at making one from scratch... looks like I need more practice. Normally I do it hands on and it is much easier... thanks for helping...

Make sure those files I made disappear so no one gets them thinking they are working please. I am trying to delete the attachments...
 
Well that was my first attempt at making one from scratch... looks like I need more practice. Normally I do it hands on and it is much easier... thanks for helping...

Make sure those files I made disappear so no one gets them thinking they are working please. I am trying to delete the attachments...


Well I guess you are pretty close. It does at least show the correct values when looking at the dash, which it did not befor.
 
Last edited:
Well maybe I will try that history table again. I made the one in 1227747 $42..

Ahhh I see what I did wrong... let me have coffee and wake up I may try that again...
 
Well I guess you are pretty close. It does at least show the correct values when looking at the dash, which it did not befor.
Well when I look at your recorded datalog it looks correct and gets a glitch and all number jump? Maybe it was the log, does data stay steady when you are connected or recording?

If it is steady then maybe zipping it is messing it up. Next time you record in TP and save the recording email it to me without zip.

I fixed the BLM and Knock history tables and they do populate. So here's another to try.
 
Last edited:
Well when I look at your recorded datalog it looks correct and gets a glitch and all number jump? Maybe it was the log, does data stay steady when you are connected or recording?

If it is steady then maybe zipping it is messing it up. Next time you record in TP and save the recording email it to me without zip.

I fixed the BLM and Knock history tables and they do populate. So here's another to try.


No they do flicker a bit. I read somewhere on thirdgen about a fix for it. I'll see if I can find it.

It seem there is still something a miss. Look at some of the numbers in the average history numbers.

TPblms.jpg
 
Last edited:
Ah, yeah, sorry missed this one... something weird is happeneing last 2 rows till high map? ... and a couple numbers I would not use up top...

What is strange is th $85 is same type PCM as a lot of others that have no specail commands? Like one ADX I just built from scratch for LT1 PCM, wow what a learning experiance that was... over 100 hours but it's accurate and steady as a rock...

Look at your origanal wiring diagram and see if the serial wire from PCM is alone to pin M on ALDL, or if it has a wire from some where else connected to it from?


If you send me the data log from TP I can use it and find the problem... I found that thread on third gen and can add that to the adx... it's just adding a nuber to return data packet...
 
Once those glitches/jumpy is data logged it's there, no way to test so they won't help... if one of these below work send me a data log saved straight from TunerPro, should be xdl file extension, so I can practice/test and work on other things.

But I made 2 new adx files for $85. Version V3.1 has a pause, this was a cure for that glitchy data so try it first.

Then try V3.2, it has pause but also a silence 0xF5 which is transmission, which is what I think you have been getting as data as the address is same on most, some different, some missing. Engine data is 0xF4 and is a slave ECM, so the transmission needs to be silenced and engine needs to be triggered. Anyway try them both and let me know if either worked and got rid of glitch!

These are both engine only. If one works we can add trans or make a separate for trans.
 
Last edited:
Once those glitches/jumpy is data logged it's there, no way to test so they won't help... if one of these below work send me a data log saved straight from TunerPro, should be xdl file extension, so I can practice/test and work on other things.

But I made 2 new adx files for $85. Version V3.1 has a pause, this was a cure for that glitchy data so try it first.

Then try V3.2, it has pause but also a silence 0xF5 which is transmission, which is what I think you have been getting as data as the address is same on most, some different, some missing. Engine data is 0xF4 and is a slave ECM, so the transmission needs to be silenced and engine needs to be triggered. Anyway try them both and let me know if either worked and got rid of glitch!

These are both engine only. If one works we can add trans or make a separate for trans.

Mark,

Neither of these new files would log. When I would try to connect and start the record they both had a flashing bar at the bottom indicating an error.

I double check that I was doing it right by loading your first file and it would connect and record fine.
 
Well when this flu passes and I feel alive again or will to live I will look back at them...

I was just informed by the guru of ADS, ADX Author Robert Saar that the pause is a patch it seems to fix issues in some, real issue looks to be importer in TPV5 does not account for CheckSum in reply. So adding a byte to total bytes received in reply is the cure... Although I have made them steady/solid with one, or other, or both.

So good testing! :waytogo:

You went back and saw origanal was still hooking up when others failed. This gives me solid info to get this adx working!

Just can't think right now... back to bed...
 

Latest Posts

Top Bottom