What's new
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

eagle mark said:
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...
Click to expand...

Thanks Mark. Sorry that you're not feeling well.
 
arg... me too...

there was a major flaw in byte count? It was off by 3? I really don't know how I missed it? :dunno:

But here is a pack of 4. Start with V4. It is same as V3 but with correct byte count. Then the normal subtle changes that have been needed to make other adx files work. V4.1, V4.2, V4.3

Like before good testing would probably start with that know file that connects but glitches. This way we know your cable/USB/Com port etc are in sync. Then V4 and may be done, if fail V4.1 is actaully written correctly from ALDL file with an engine connect set first before data reply, V4.2, V4.3...
 
Last edited:
Mark,

Thanks again.


I tested as you suggest, first with the working file and then the 4 new ones you uploaded.


All 4 of the new files will connect without error and display right around 8.23 hrz, but when I pull up the item list or the dash there is not data show.

I test each file 3 times and also retested the version 3 stuff as well.
 
:doah:

I'm sick and shouldn't be doing this sorry... I obviously did something right to wrong file or?
 
OK you said they all connected and showed good mz and no errors! So I looked and had connection right but monitor wrong. This is V4 with just monitor changed to engine reply instead of macro...

It's hard to do this without the vehicle and I'm a newb at writing these but have a few under my belt. I only get involved with good testers and you have helped wonderfully! :waytogo:
 
Last edited:
v4.5 - it tries to connect but never completes the connection. It sit with a messaged in the connect box - DA Connecting. I've let it try to connect for 30 seconds.
 
I thought I had it, just not feeling well enough to do much properly right now... fever is not good...
 
We seemed to have passed what was needed? V4 connected but showed no data, right? Well it shouldn't have because the reply numbers were off... so I went backwards here. We are back to V4 and V4.1 corrected. Make sure you remove or move all old files because these are named the same.
 
Last edited:
Mark,

The 4.1 is rock solid! It connects, displays all data in the item list and dash board perfectly. It also populates the BLMs, I was watching current average and it was very nice.

The knock history seem to be off. It was only putting knocks in the far right. I'll do some more testing on this over the weekend. I have a 2 hour drive up to a friends how so I get all that data.

FWI: The 4 version did connect, and did display items and dash. But, in the dash display it had the flashing display glitch we have seen in other users videos. I'm hoping this will help you resolve the glitching in further files.


Now, since you are a role, have you seen this file over at Moates?

http://www.moates.net/documentation.php?documentation_id=29

It is a write up a guy did on putting the LM-1 wide band O2 data stream into a ads file. I thought it might mean something to you. I'd try it but I don't want to screw up the great work you have done.

Thanks a ton!!
 
Woo Hoo! With a 102 fever...

I didn't read the link but I know they use the EGR pintle wire which is 0 to 5 volt. Same as wide band. It's already been done on $OD and $OE adx files so should be easy to add a value to $85. I have an AutoProm I wire my LC-1 into and a value added to each of my files so WideBand data is in same file. The $42 files have it in as well.

Fixed the knock history table in this one... had a wrong value in x axis Baro KPA and should be MAP kpa.
 

Attachments

  • $85-16147060-V4.1 Fixed Knock.zip
    6.3 KB · Views: 3
eagle mark said:
Woo Hoo! With a 102 fever...

I didn't read the link but I know they use the EGR pintle wire which is 0 to 5 volt. Same as wide band. It's already been done on $OD and $OE adx files so should be easy to add a value to $85. I have an AutoProm I wire my LC-1 into and a value added to each of my files so WideBand data is in same file. The $42 files have it in as well.

Fixed the knock history table in this one... had a wrong value in x axis Baro KPA and should be MAP kpa.
Click to expand...


Well, in that walk through file they are using the moates autoprom and the LM1 is wired to the inputs on the autoprom and then the ads is configured to pull the data down that way. I do not believe the bin is modified.

I'll test up the file tomorrow and give feed back.
 
Exactly. That was my second example. The Lc-1 is the same thing. A wide band controller based on 0 to 5 volts. Go grab the $42-1227747-V3.adx and it has three channels set for the AutoProm circuts. Adding values is easy. If you need help let me know. :waytogo:
 
eagle mark said:
Exactly. That was my second example. The Lc-1 is the same thing. A wide band controller based on 0 to 5 volts. Go grab the $42-1227747-V3.adx and it has three channels set for the AutoProm circuts. Adding values is easy. If you need help let me know. :waytogo:
Click to expand...


Mark, on the new site/forums where are your files located? I can't seem to find them now.

[edit] I found the files but I can't seem to locate the $42 V3 adx. [/edit]

Also, I read a note about doing emulation and that the checksum must be disabled. Is this the case?

This is the note: Typically, checksum disable or update checksum should be selected. Use a setting of “AA at 08” for 28 pin applications, and “AA at 04” for 24 pin ECMs.
 
Last edited:
Here's the link to forum that has a thread for each ECM info. We keep building so each ECM has what it needs there. 1227747 $42 is about the fourth thread down but that can change.
http://www.gearhead-efi.com/Fuel-In...o-Definition-Files-Wiring-Diagrams-Tuner-Info

I will help you learn to work on your adx if you need be, but it is something you should learn to do. It is the only software you can customize the way you want. Loads of options. I have written several how toos in TunerPro Talk.

Making them work is hard part and there's no book or school. We have the only thread on Internet on how to learn. Still it is not cut and dry schooling. Most of it is only known by GM or Scan Tool makers.

Your also lucky that the XDF has a parameter named Mask ID, so you don't have to change bin in hex. Your's will say 85. Change it to AA, then upload bin to AutoProm and click verify, if OK them emulate and start the rig. You are now running off the bin in your laptop and can make changes in XDF and save or in tables a button for Commit to change. Real Time tuning. Don't forget record and you will have a data log to look back on and see change.

If you spend some time in your ADX and XDF you can also set up Data Tracing. Whatever cell fuel is using, coming in through ADX in your fuel table will have a bubble in XDF main fuel VE table so you know exactly where to make a change.
 
I found it the thread with the files. Thanks.

I look in the xdf file but I don't see a Mask ID all I see is PROM ID. Am I looking in the wrong place?
 
There's a few xdf, one I saw had Mask ID one did not. I will give you the ones I have and combining all info would make for a better XDF and a worthy project. :bow:
 

Attachments

  • 85v1.1.zip
    19.5 KB · Views: 1
Thanks again, Mark.

When combining the info is it just openning a second copy of Tpro and coping from one to the other using the clipboard?

I see that if you do Tools > Custom Tools > New TunerPro Instance, now open an XDF in each of them, compare the data, find the missing data (Mask ID), right click the item and copy to clipboard, go to other Tpro window and add the item.
 
You must log in or register to reply here.

Latest Posts

Top Bottom