Z69

I finally got around to testing all the bins I wanted to include support for. Here are the links-


8D_305WB.zip
8D_AUJPwb.zip
8D_Vettewb.zip

It is for ALDL use only. No CL WB yet.

Here is the thread that started it.

WB Code Requirements

BenDoe91z28

Thank! I shall download and reconfigure the BIN you gave me immediatly, just in case something had changed. I'm sorry to bug you so much.

I have configured by BIN so that the input is coming through on pin A3, but still havn't figured out how to get TP to read the output through ALDL. I'm assuming that I need to create a new "ALDL" value and am researching how to do that on TGO. Anybody out there care to help?

JP86SS

iTrader: (1)

In the text file it says that word 37 (IAC Min steps) will be the output for the actual AFR.
You wont need to change anything to get the reading.

When selecting the sensor,
the appropriate scaling for a 10 to 20:1 AFR is setup and your ALDL scanner can read it as such by applying the formula shown after the sensor.

From the txt file:
Option Flag 1
Bit 0 : DIY / TechEdge v1.0 Sensor (Nonlinear Output)
Bit 1 : FJO (Nonlinear Output)
Bit 2 : AEM Nonlinear Output
Bit 3 : TechEdge v2.0 (Linear Output) [AFR = (Volts * 2) + 9]
Bit 4 : PLX Linear Output [AFR = (Volts * 2) + 10]
Bit 5 : Innovate Linear Output (1V - 2V) [AFR = Volts * 10]
Bit 6 : AEM Linear Output [AFR = (Volts * 2) + 10]
Bit 7 : Zeitronix (Nonlinear Output)

Correct me if I'm incorrect on this Z'69.

Z69

He needs your ADS file to see it JP.

You'll notice in the ecu I included that word 35 is listed in the
constant section. Just change it to 0035 in TP and save the bin/burn it. The 7730 ads file on Marks' site has #35 FP volts in it.
Or you could simply edit the FP volts item in the ADS.
Change the 35 to a 37 and edit the description to WB AFR.
The rest stays the same I think. Or you could copy all the settings in the FP volts item in a new item. But change the above. I thought there was a txt file or something on TP for creating an ecu. The ads edit is very similar.

I used #37 for Datamaster support. I included all tha aldl info so people could swap it to whatever they want.


Nothing changed in the bin from what I sent you.
Only the txt info file changed. I kept adding stuff as people asked questions. It was getting long and most things are covered so I stopped on it.

Don't confuse word #35 with ram location 0035. They are two different things. But coincidently have the same numerical value.

JP86SS

iTrader: (1)

[QUOTE]Originally posted by Z69
He needs your ADS file to see it JP.

Guess I have to finish that now.
I have it as far as I can go but I'm stuck on a couple of the 16 bit arithmatical things that nobody uses anyway.
Weather here is b-e-a Utilful this weekend with the airshow and such going on so I'll be outside driving for most of it.
$3.30 a gallon or not !!

junkcltr

iTrader: (1)

You two do some great work. It is good to hear that you are taking a break this weekend.

J

Z69

I remembered that I didn't do a checksum in TP after patching the bins. So if your bin is dated prior to 9/3/05 you will have to do a save in TP to recalc the checksum.
I also noticed I didn't put a $ in front of the 0035 for the change to the aldl list in my asm file. So all the bins have word 37 set to $0023 instead. I fixed both of these and e-mailed Craig to update the files for me.
All the bins should have a 9/4 date to have the corrections.
Sorry for any inconvience.

You can download the correct files here till Craig gets' the old ones updated.

8D_305wb
8D_AUJPwb
8D_vettewb

BenDoe91z28

Z69,
I'm still having trouble with my scanner. Attached in this post are my settings. I have the pin set to come in on F14. I went to scan the sensor, and all that was returned was the value 12.00V with no change in that value with RPM or anything. Any suggestions?

BenDoe91z28

another

BenDoe91z28

another one

69 Ghost

iTrader: (1)

I will be posting a Super8dm definition to support this in the near future that will incorporate the JP86SS AUJP hac definitions. Still working out naming conventions as JP86SS has done this work also!

Craig Moates

I love seeing these screenshots of custom ADS files along with custom BINs.

Just figured I'd say, makes me happy...

Z69

Check what word 37 in the constants is set for.
It should be $0035 to show afr.
I was wrong about the posted bins not being different.
There was actually two small differences.

JP86SS

iTrader: (1)

Maybe this will clarify it (or just add more trouble)
From the screenshot ther, your multiplier does not match what was listed in the text file. Here's what I did but haven't confirmed it works yet.

JP86SS

iTrader: (1)

I haven't tried yet but the idea just came to me that if I include ALL of the sensor selections as each having a #37 they should all be running and just ignore the ones you don't use.
Do you know if TP will puke out the values with 10 listings for the 37 address?

That way they are all right there to begin with.

Just re-adjusting clicking rockers now, may get a chance to verify that works later today.

JP86SS

iTrader: (1)

Easier for people to ignore or delete the entries they don't use than to add them (If it works)
I think it will be OK but if someone wants to give it a quick try and let me know that would be cool.
This file HAS KNOWN ISSUES and is not final. That being said, any feedback on it would be great (especially on some of the items that I commented as being wrong) Check the comments in the definition if something seems to read strange. I'm more concerned with the WB stuff but if you know how to correct one of the items, send me an e-mail.

Jp
Http://www.wideopenwest.com/~Johnand...27730 JP50.ads

OK, it works.
Right click and "save as" (unless you want to read it )

JP86SS

iTrader: (1)

This is what I did.
Created an entry for all of the sensor options.

JP86SS

iTrader: (1)

I tried it with an old log file and all values changed appropriately so I don't see a problem doing this.
Just hide the ones you are not using with the "visible" check box in the definition editor.
I went back and made all the WB "not visible" so just turn on the one you have.

EDIT:
Latest file has 9-5-2005 with 10:08 pm timestamp in case you picked it up earlier than this post.
Fixed TPS % (Didn't work), PS Cramp reveresed, a few 16 bit items had 255 limit (doh!), 4th gear switch was reversed.

69 Ghost

iTrader: (1)

For ECU definitions and possibly XDF definitions you will see problems with multiple values defined in the same area. It appears that the system will like one but the others will give erronous results. The easiest way is to define everything and then remove what is not needed which is what makes sense for the ADS setup in this case with the WBO2 stuff. For things like VE extended patched tables it would be a preference to have them in a location that is not used as the original 6400RPM extended VE table. JP86SS your mailbox is full!

While we are on the subject can anybody tell me the pin locations that to be used on the 7727 -waterproof vette computer is? The factory A3 pin is the secondary cooling fan. The ludis ECM site shows pin conections for the 7730 but not the 7727 so I cannot crossreference this.

JP86SS

iTrader: (1)

Delete..Delete.. Delete...
Should be ok now

I dug through all my wiring files and can only find the "carline" diagrams on the 727. Nothing that can reference that extra TPS2 input.
It is U6 pin 13, Channel 0, if that helps.
Sorry.
Jp

Z69

727 pin http://www.cruzers.com/~ludis/triplugecm.html

The patch does all the afr math.
It will always store the afr at ram $0035 regardless which sensor is chosen. If raw is chosen, it will put the raw counts
into $0035.
So you only need one ads item reading #37.
Set it up the same way as the FP volts is I think.
I always set it up as an integer with a factor of one.
But no decimal seems to bother people.
I didn't even notice after a few minutes.
Now I remember, I wanted to be able to see the raw value too. So I left it as an integer so I could see that too.
You'll need to put a note in on how to set the item up if people want to check the actual 0-5v signal too.
I've seen .02 volts per count put out. I'm not sure why it's not .0196 instead.- 5/256

I know I've had two items in an ads set to the same word and no problem.

Craig Moates

Integer of 0 = 0v, integer of 255 = 5v. So it's really 5/255.

JP86SS

iTrader: (1)

So in all cases the output is already scaled for 10-20:1 AFR?
Just rechecking. I couldn't follow the non-linear stuff in the patch so I wasn't sure if each selection had a specific need for a calculation.
Have a few other questions for you Z' offline tonight.

-=Jeff=-

Excellent... Now I just need to get an ADS file that works with the 91 Vette.. for tunerpro

92GTA

iTrader: (11)

Ok, I've been running the WB modified AXXF with my custom modded ads file and the included xdf for a couple weeks now and all works great. Thank you!!!

My question now, how do I get the extended upper VE table mod added to this so I can tune my upper RPM's? Can someone post all the needed tools and files to either patch my bin or maybe someone can post the AXXF bin posted already modded for that feature?

Very much appreciated!

Oh, and what about modded it for using a 2-bar MAP sensor for boost?

Also I'm assuming the Innovative LC-1 will work with the Innovative option already included for working with the LM-1 right?

JP86SS

iTrader: (1)

Yes, set the output to a range of 1 to 2 V and it will work fine

There were previous patches to add extended tables by Rbob and then another by Z'69. Quick search should turn them up.
Not sure if they worked for the manuals though.

I don't have the other answers

92GTA

iTrader: (11)

Hmm, so I just can't select the "WB AFR (Innovate Linear) and it work? I figured the LM-1 and the LC-1 would have used the same sensor and thus output the exact same raw data

K, I found the old post and downloaded the files but for some reason it won't patch my bin, errr.

BTW, the AXXF is the auto bin NOT the manual, just an FYI.

Thanks.

vernw

iTrader: (2)

AXYC is the manual BIN that Scott did the WB patch for.

Dyno Don

iTrader: (7)

Is that for sure AXYC?
I use AXXD & AXXC neither are patched yet.
Maybe soon?

69 Ghost

iTrader: (1)

BTW. Just a quick question/comment. Why are you using a Vette bin? There is additional code but really the only difference is that it incorporates a oil temp sensor into the mix. If you are not running one then you should just condsider using SAUJP. It would probably make things easier in the long run.

Z69

For wb use with the extended VE, use S_AUJP_V3WB as 69ghost refered.

8D 2 bar map code is in the research phase.

The LM1 and LC1 do use the same sensor. The user has to verify the output for either unit is set to 1-2 volts for the Innovate linear option. Or if 0-5v is desired. The Raw bit needs selected and the afr conversion done external to the aldl stream.
Patched for what? The 305wb.zip has both in it.
If you mean extended ve. Then use s_aujpv3 or the axcn patch for an AT or MT car.
Just swap the cal data in if you need it for a 305 car.
You'll need to learn to use Tunerpro for that I believe.
And con the complete xdf out of one of us. Or use a hex editor.
S_AUJP_V4 will work with either trans in an fbody.
Well I still need to test it in an 4l60 car.

92GTA

iTrader: (11)

Where is this S_AUJP_V3WB ? I don't see it on Moates.net or here via search. Also what xdf and ads do I use with it and what WB's does it work with? I'm also presuming that there is no check engine light problem with it correct?

Let me know when the 2 bar map sensor hack goes from research into development and I will be more than happy to help test it since we are both in Bakersfield.

Thanks!

Z69

You might try reading the whole thread again.
OR maybe just the first post......

2 bar is out of my hands currently.
Some $58 users are working on extracting the boost related code.

92GTA

iTrader: (11)

Oh geez I feel stupid as heck right now

I was doing text searches for the files name to save time and it screwed me, lol.

Thanks!

ryan.h

iTrader: (2)

So the WB input is fed into the unused pin A3? And this just gives you the ability to datalog with a wideband, I guess in addition to the stock narrowband?

Are the specifics on how this was done in the other thread? I'm very much interested in porting this to some other code, but don't even know where to start...

Z69

Those bins are setup to work with multiple sensors.
The code for it was a merging of several individual patches available. And then adding the missing sensors tables.
The original code was written by 1981TTA.
He gave me the code and I adapted it to 8D.
But he doesn't want the actual code made public.
If all you want is to make your specific sensor work with your specific bin. Then you need to make a patch to read an empty input pin on your ecm. And edit the aldl stream to spit that value out. The place to start is the Source code for dummies thread.
And figure out what was done with some of the patches available.
Once you learn enough, you could disassemble one of the bins to see what was done. Or make your own patch.

ryan.h

iTrader: (2)

Thanks. How did you determine a free address (in RAM is it???) to store the A3 input data?

I think my code is different enough to warrant a new address, so any help there would be appreciated... Don't want to overwrite anything I might need...

Oh, and what channel is A3? (I'll have to check the schem. in case it's listed there)

edit again: okay, TPS2 goes to a MUX and it looks like it's channel 9? I assume then I have to send 0,0,0 to MuxA,MuxB,MuxC before reading ch 9...

JP86SS

iTrader: (1)

A3 is U6-Ch-0
the channel 9 reference is the MUX to the U6 device.
Just use the existing code to do the read of U6.
you just supply the channel number before calling the routine.
USES ROUTINE AT LE2DC (MUST LOAD CHANNEL NUMBER PRIOR TO CALLING)
Look in the tuning guide or search for a thread called "I/O Addressing"
Good info there on how it works.

BTW, This is just an example for AUJP, other bins have different locations.
Are you writing your own ?

ryan.h

iTrader: (2)

I guess I still have a lot to learn then. When I see this:

I just see the bolded "load channel 9" of U5. I'll probably be writing my own for the 3.1 v6 $A1 code. Blargh.

Learning assembly is worse than learning French. At least when you're learning French, you don't have to do mental math to know what's being said.

ryan.h

iTrader: (2)

ahh! found it! excellent! Answered most of my questions. Looks like my quote above is the actual MUX reading sub. No point in trying to decode that, all I need to know is channel in, MUX a/d data out. Still don't know how I'd find an unused address to store it though...

Z69

You also need to make sure you don't do consecutive reads too close together. IDK where to close is.
And don't forget the # symbol in the code.
Spent many hours trouble shooting only to find that I'd droped the # symbol when I pasted the patch into my aujp source code. The patch had #$xx while the source needed
#0xZZ. I think I kept loading ram loc 0000 into A instead of just a zero value.

92Z

iTrader: (1)

After i apply the patch to my .bin, would this be the correct memory location to change for the FJO non-linear wideband? Any help appreciated.

JP86SS

iTrader: (1)

Looks good to me
$2000, bit 1
Should be good to go if your wiring into the default pin and your sensor output is correct.

92Z

iTrader: (1)

Thanks for the quick reply. I just patched the .bin. Looks different than original so i guess its good! I am by no means a code man at all. But with the help and support of the people like you and the Thirdgen PROM community i am learning more and more everyday. Thanks again!!