The new WB code

turbodig

Active member
Time to make it official....

I've been working on some new WB o2 code for the last year or so.
From the testing that's been done so far, it appears to be a go.


True-WB o2 code for the '749/$58 Sunbird/SyTy ECM.

Features:

AFR field in Datamaster/Diacom will read the real AFR value, not just
some number that you need to re-calculate. IE, 12.5:1 in the scan tool
really is 12.5:1

Fits in the stock 16k code space, so it'll work on Ultimates or other
multi-chip arrangements.

Uses the same wiring and pinout as the previous WB code.

Restrictions:

Currently only calibrated for the DIY-WB, as I don't have voltage to
AFR curves for anything else.

Don't do anything with factory test mode! If you don't know what this
is, you don't have to worry.

Subject to the same DIY license agreement- not for commercial use.
This code cannot be included in a commercial offering. If somebody
already has purchased a commercial chip, and then cons somebody
with a burner to patch their chip for them, that's ok. Basically, this
code is not to be sold as someone's chip "feature". This really hasn't
been a problem in the past to my knowledge, so I don't think it will
in the future. Nonetheless, those are the rules.

Also, with the patch comes a nice, easy way to apply it- Patcher 1.0.
Basically, the syntax goes as follows:

patcher.exe <file to patch> <patch data file>

The patch data file is included, and will default to ptchfile.txt

This will output a new patched file of <file to patch>.pch . Rename this
to whatever you want, and burn away.

Patcher will also detect if you have a larger than stock binary, and will
attempt to patch all the positions in that binary. Meaning: if you have
a binary from your Ultimate, patcher will patch all the positions in that
chip.

You can also select to patch only one position of a binary, if you want.

Patcher has other redeeming uses, particularly if you want to change
data in all the positions of an Ultimate. I used it to disable EGR on all
the positions, would also be good to lower/change the coolant temp
turn-on threshold of things.


While the code has been tested successfully on a few vehicles, I'd like
to get some more test results back, as to how well it's working. Send
DM/Diacom files to: turbodig@yahoo.com

As far as support, there is none, unless I feel like it on that particular day.
Read the readme in the zip file for more details.

Oh, yeah, I suppose I should inform people where to find it:

ftp://ftp.diy-efi.org/incoming/sytypatcher.zip

Later,

Dig
turbodig@yahoo.com
'91 Sy - 11.94@112
 

leroy

Donating Member
Great stuff Dig! Where did you put the lookup table?

I was used to re-calculating, almost doing it without thinking.

Jim
 

Tydriver

TurboLS6 Powa'
Nice Job Dig, and thanks for your contributions once again.. Man it must hurt to squeeze that big brain of yours into a head..

Anyhow, thanks again really appreciate it.
 

jwaller

Evil Genius/SyTy Guru
awesome bro...congrats...... keep up the good work.... now all I have to do is recal it for my WB... :)
 

10secTy

Sy-Ty builder and Tuner
Yep Thanks Dig the Code works Great!!!!!!! I have tried it out on a truck it rocks!!! Thanks again.

Nolan
 

turbodig

Active member
smeagol said:
Nice work Dig!

I was using another program to do exactly what you have accomplished, over here --> http://www.chitownsyty.com/bg/chipstuff/hex/hex_editing.htm

Yep, they're pretty much the same that way.
Patcher's data file is pretty direct, it's just a text file with the raw binary
in there. Start each line with the address, separate it with a :, and type
in your data.

Next version will be a while, but I'm planning on setting it up to support
any chip density... so it'll work on pretty much any platform.

Motorola has some s19 file tools that do pretty much the same things,
but they're a lot clunkier to use.


Later,

Dig
 

turbodig

Active member
leroy said:
Great stuff Dig! Where did you put the lookup table?

There's a lot of code space in there, once you start looking for things
that never get used in normal operation.

Gotta give credit to Bob Raucher for the idea of writing over the test
mode code. He had sent me some code a while back that was in that
area, and it gave me the idea to stick my WB code in there.

I've got some other code projects that are going to end up sitting in
there; init DC correction factor for MAT, and a VE vs. MAP and RPM
table that uses a 3 bar index.

Addresses are in that text file, if you're interested. I'll set up a tunercat
table for it, eventually.... it'll be easier to re-calibrate that way.

I was used to re-calculating, almost doing it without thinking.

Jim

You can still do that, if you miss it. I set up desired EGR to be the raw
A/D data, / 2.56. 50% = 2.5v, etc.


Later,

Dig
 

BillC

New member
smeagol said:
Now if we could only convince Bill to integrate this kinda software into Promgrammer, and some pretty interface for drag & drop .... maybe right after he's done getting the emulator to work with Promgrammer eh?
:p
I could put this code mod into Promgrammer, it would be just like the F71 scaling hack. Would be fairly simple, just more bytes to change. However, I am concerned that it might violate Dig's "license" -- since Promgrammer is shareware (pay-after-trying) and some people use Promgrammer when tuning chips commercially (or at least, while getting paid for custom tuning).

Dig:
Would it be okay with you if I built this new code change into Promgrammer? Are there any restrictions you would require on this? What is the format of the calibration table (length vs width, conversion formula, row and column headings, etc)?

Smeagol:
Don't count on the emulator interface happening any time soon. :( Just too many other things going on, including trying to fix that godforsaken false knock (which I might have finally found, but have to do more testing first to be sure).
 

turbodig

Active member
BillC said:
Dig:
Would it be okay with you if I built this new code change into Promgrammer? Are there any restrictions you would require on this? What is the format of the calibration table (length vs width, conversion formula, row and column headings, etc)?

Regarding building the code right in there, I don't think that'll fly.

But, nothing's stopping you from building a function that reads that
datafile in, and then applies that to the chip that's being worked on.

That absolves you of the initial license thing, and if somebody uses your
program to sell a chip (with the WB), they're the ones violating the
agreement.

Would be kinda neat to have the ability to read in a datafile for "merge"
capabilities....

It should take you all of 2 minutes to figure out the syntax of the txt
file.

Regarding the format of the table itself, I'll have to look at my notes.
Shouldn't be too tough to create a table for it.

Wouldn't be a bad idea to do this for a TunerCat dat file, now that I
think of it...


Later,

Dig
 

Sy769

Donating Member
Thanks Dig for your work on this.

Bill all I can say is please :D

You guys never cease to amaze me with how you share your work and make it easier to tune these trucks. Without the kindness and creativity from many of you a lot of us would probably be stuck with running a Detonationmaster chip. Thanks to all of you..you know who you are :D
 

BillC

New member
turbodig said:
BillC said:
Dig:
Would it be okay with you if I built this new code change into Promgrammer? Are there any restrictions you would require on this? What is the format of the calibration table (length vs width, conversion formula, row and column headings, etc)?

Regarding building the code right in there, I don't think that'll fly.
Hmmm, well, that's your call. I was thinking of having it appear as just another parameter, like F71_SCALE, except that it would be binary: enabled or disabled. When enabled, it would write in your mod. When disabled, it would restore the original bytes.

turbodig said:
But, nothing's stopping you from building a function that reads that datafile in, and then applies that to the chip that's being worked on.
Since you've already written Patcher, and since it already does what you proposed above, I don't think it's really worth the effort to put that functionality into Promgrammer as well. Especially considering that most people using Promgrammer are using it specifically so they don't have to deal with hex.

turbodig said:
That absolves you of the initial license thing, and if somebody uses your program to sell a chip (with the WB), they're the ones violating the agreement.
Unfortunately, it's the same problem either way. Regardless of whether a person/company runs Patcher, runs a future version of Promgrammer, or simply pokes in the bytes by hand, if they sell the resulting chip containing your WB O2 logging commercially, they will violate your license. If a person or company decides to violate your license, it won't really matter where they got the code or how they installed it.

I can, if you wish, put a licensing statement in the instructions regarding this mod, and even credit you with the work. Would that be acceptable?

Building the code mod into Promgrammer has two benefits: 1. It helps protect the user from screwing something up that can't be fixed in the normal editing windows. 2. It will let them revert to the original code if they change their minds or they need to use the factory test mode.

turbodig said:
It should take you all of 2 minutes to figure out the syntax of the txtfile.
No prob. :D

turbodig said:
Regarding the format of the table itself, I'll have to look at my notes. Shouldn't be too tough to create a table for it.
Since you said that it was only calibrated for the DIY-WB, it seemed like an editing capability could be useful. :wink:
 

smeagol

Active member
Hey Bill, how about a feature in promgrammer to allow opening of multi-chip programs (2/4/16/32 bins in single file) to possibly make changes to every program at certain locations?

Want to eliminate EGR in all programs? or change fan turn on temps in all programs? Open the single large binary file, edit, and apply change to all programs at that offset..

Might be too much to ask, but it'd mean the patcher program would only be used for the code changes. This would require someone to go through a bit more work to use patcher, to do the code changes etc.

Or maybe incorporating patcher into promgrammer as Dig has mentioned, then tying it into the compare function. Open a bin, change some bytes, save it, compare it to the original file, and option to create a patchfile (text) from the comparison possibly?

It sounds like Dig is saying it's ok to use patcher, and incorporate it into Promgrammer, just don't have the wb code thrown into it, and able to be "turned on" with a couple of clicks.

I don't think that the wb code needs to have edit capabilities, that is, it doesn't change any table readouts, it doesn't need to be edited, it just needs to be added to a bin, so there's no need to have the code itself as part of Promgrammer. Hmmm just re-read your post Bill, I see what you are saying about the table, and making it edit-able for other inputs. Maybe Dig would allow the incorporation of the code, just that when you click WB02 code ON, your calibration table is zeroed out ?? 8)


Anyways, about the patcher stuff, I dunno, I've just gotten lazy, and If I can't use a gui to drag and drop, or click my way to get a function done, I just am slow to get it done, as with using a command line, or doing raw hex editing. :lol:
 

ty1548

Member
Would there be any interest in displaying the WB O2 volts (or conversion to A/F ratio) on an Ultimate chip display? (This would be a new design for future release, couldn't be done in the existing ones). Would you rather see the mv value or the associated A/F ratio?

For those that are reburning the EPROMS and still using the Ultimate hardware, I can reprogram the display to select and display anything you want. In other words, if you only want 8 settings, I can reprogram it to cycle through 8 addresses and display whatever you want for each one.

Look for an upcoming post in the lounge forum for a complete discussion of what I can do in future versions.

Todd
Ty 1548
 
Top