DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
Invert the 0-5v output of the WB, and change that to a 0-1v output. Then modify the code as needed to run variable AFRs (to actually benefit from the above work).
The only caveat is the resolution of the 8 bit A/D converters. You'd have a hard time getting any sort of resolution and dynamic range. You can either have one or the other, but not both. Basically theyre pretty much useless for anything that requires any sort of precision. I had some stuff that I was working on for the PCM, but it didnt really look feasible to have something that would be able to provide decent control over a wide range of AFRs.
Did that, confirmed exactly except for the 4 id locations. should be good to go.
Just need to find a good spot to put the code.
Thinking of using one of the delays that only do an RTS.
Looking now...
Ok not sure where to put it yet.
Round 2 tomorrow night. Assembly time
Stick it in with another a/d read and use a jsr to the RTS to ensure the test ch read gets completed. Or stick it in the same spot as the Davis WB patch.
OK, you're getting in deep now
First, the "0x" means the value is in hex.
Same as designating with "$".
This lets you know that it is not a decimal value.
So when you see $13 or 0x13, it is actually decimal value of 19.
Next, no need to disassemble the bin.
The bin has already been disassembled and commented into a source code.
It is the file with the .asm extension.
Kudos to whoever put thier time into doing it, very nice job.
You also have the added bonus of the file being made "relocatable" which means most if not all of the actual code has been made to reference lables.
Rather than having to keep the file pieces sequential so the addressing of each part is exactly the same as when the file was created, this allows you to insert stuff in the middle and the jumps to sections will still work.
Originally a command would state "jump to L1234".
Well if you moved the code down by inserting something before L1234, then the jump would land at the wrong point. Not good.
By making the location "labeled" "L1234", where ever you put the code with L1234: it would jump to it.
There are other rules of not exceeding 128 when jumping, etc but you get what I mean.
Now...
Using this file you can see everything that is going to happen and what values will be used in the calculations. Now all you have to do is learn the language. Easier said than done, for sure.
Back to the objective,
What we are trying to do:
Make the ECM read the voltage at a certain pin.
There are two types of inputs and outputs,
"Digital (on/off, high/low) and
"Analog" (0-5 volts, 0-1 volt) whatever but it is variable not just on/off.
Each pin that can have a voltage input applied to must have an identification to the ECM. these are assigned channels.
Here is a listing from the hac file:
Code:
; Table FDMPRES
;
0x0170 ; A/D, Ch 0, **UNUSED**
; A/D, Ch 1, Batt V
0x0172 ; A/D, Ch 2, o2 sense v
; A/D, Ch 3, **UNUSED**
0x0174 ; A/D, Ch 4, Coolant temp, 4K
; A/D, Ch 5, TPS V
0x0176 ; A/D, Ch 6, Fuel pump V
; A.D, CH 7, Diagnostic pin B V
; < 0.8 = grounded
; 0.8 < V < 2.0 = fact test mode
; > 3.05 = road test mode
0x0178 ; A/D, Ch 8, MAT Temp
; A/D, Ch 9 **UNUSED**
0x017A ; A/D, Ch 10,MAF sensor
; A/D, Ch 11 **UNUSED**
If you look at the schematics of your wiring you will see they go to the appropriate sensor.
To read the sensor you must know the channel you want to read.
These are numbered in hex as $10, $20, $30 for channel 1, 2, 3 repectively etc.
There is a "routine" of commands involved to do a read that you will not need to go in depth on at this point. All you need to do is "load" the channel number into the "A" register using this command.
"LDAA (insert TAB or space here) #0x10"
The # sign designates that this is a value, not an address to get a value from. So instead of going to location 0x10 and getting the value stored there, USE 0x10. This is channel 1.
The next command would be to "Jump" to the subroutine" that will make the actual read.
This is:
JSR LF2F7 ; Jump to code at "label" LF2F7
The result will be placed in the processors "A" register when done.
Then you want to keep the value that you just obtained so you "Store" it.
STAA L0170 (or whatever memory location is not used by the code)
This is not the code area but active memory space and is very limited on these things.
So to finish this chapter...
LDAA $00 ; load number zero to select channel
JSR LF2F7 ; Do read of Analog channel (result in A register)
STAA L**** ; store for later use
Now change the display in the ALDL listing to display address L**** that you chose above in place of the existing address.
On to chapter 2..
I'm in the asm file. APYP7165-relocatable (ASM FILE) 6E.zip
Now do I simply paste the following anywhere in the code? Is their a "body" section like html code? LDAA $00 ; load number zero to select channel
JSR LF2F7 ; Do read of Analog channel (result in A register)
STAA L0170 ; store for later use
LD9AA: lsra ; A = 2 x LV8
ldx #LC441 ; Index to table: Highway Mode A/F vs LV8
ldab #0x10 ; Offset = 16d
jsr LF3F2 ; 2D Lk Up (offset in B subbed from A)
clrb ; B = 0, A = A/F ratio
psha ; transfer A & B
pshb ; to
pulx ; X
ldd #0xFFFF ; D = 65535d
idiv ; X = D/X, D = remainder
ldab *L000D ;START UP A/F Ratio (2 bytes)
ldaa #0x01 ; A = 1
bra LD9F8 ;
Now after I simply "paste" the following into the code... I have to:
Change the aldl display location:
.dw 0x0127 ;51, Run tot Dist Run, (.0005mi/bit)
.dw 0x0019 ;52, Eng Run Time, Sec .dw 0x001A ;53, LSB
;*********************************
.dw 0x0036 ;54, Minor Lp mode word #2
;
; Bit 0 = 1= OVERDRIVE ON
I will change it to: .dw 0x0170 ;53, LSB
This should take care of doing any work inside tunerpro, correct?
Quote:
Originally Posted by Z69
Stick it in with another a/d read and use a jsr to the RTS to ensure the test ch read gets completed. Or stick it in the same spot as the Davis WB patch.
Mind giving me an example?
Quote:
Originally Posted by Z69
I forgot apyp had a relocatable asm out.
You should do a JP_APYP_WB bin and post it.....
Word... Even if someone did post one, I'de like to look at the code to learn about it more...
Thankyou Z69 and John for the help. 6E guys will worship you.. lol
I can't wait for my car to be the ginnie pig... (how do u spell ginnie???)
The only caveat is the resolution of the 8 bit A/D converters. You'd have a hard time getting any sort of resolution and dynamic range. You can either have one or the other, but not both. Basically theyre pretty much useless for anything that requires any sort of precision. I had some stuff that I was working on for the PCM, but it didnt really look feasible to have something that would be able to provide decent control over a wide range of AFRs.
In the computer world, what is the difference between resolution and dynamic range? How about a 16bit A/D?
In the computer world, what is the difference between resolution and dynamic range? How about a 16bit A/D?
I'll go into resolution but dynamic range will need to wait until the end.
8 bit resolution (which your ECM is) = 0-255 steps. So what ever you want to "count" will only be in that many steps. 5 vols / 255 = 0.0196 Volt steps.
That is the smallest change the processor can read. anything in between gets rounded to the nearest value.
16 bit values combine two consecutive locations to allow working with bigger values. (they are always consecutive locations)
16 bit resolution can read -32676 to + 32676 or 65535 steps.
as you can see the resolution is much greater and math functions can be much more accurate using higher resolution.
The Dynamic range statement concerns the ability to control something quickly with only a small range of input values. If a small correction is needed and the feedback (from the WB) is really coarse like 8 bit but limited to 1/5 the range using only a 0-1 volt scale then it will be difficult to stabilize the operation due to overcorrection/under-correction of the feedback signal.
Back to the topic at hand...
to prepare for the future you will need the tools of the trade.
Go to the "Source Code for dummies..." thread and find the post to the files below if you haven't already done so.
Install the dewtronics assembler and the linking program "ASLink".
i think it comes with it but I may be wrong.
Find a copy of "bin convert" BINCVT.EXE and put it in the same folder as the assembler.
that way when you're done inserting the code (that we will do next) you will be ready to use it.
i believe all of the files are linked in that thread (Thanks to Cobra289 IIRC)
Actually all the links are in the Word document that he made describing the process performed in the thread. You can download his full dissertation on it on Moates website here File Manager - Browsing directory /5) Source Code and Hacks/How to disassemble/
Its the 8Da.zip file
Yes, we will be pasting that code in "somewhere" and here's my best guess where to put it.
This is the "segment Table listing the routines that are executed.
Code:
LCC32: .dw LCC52 ; SEG 0, Do nothing, exit w/RTS
.dw LEF52 ; SEG 1, Output Bit Sig', (TCC, CCP etc)
.dw LE08F ; SEG 2, Vss Calc
.dw LFA3B ; SEG 3, Log RAM to H.U.
.dw LEA8E ; SEG 4, Misc 100 Msec
.dw LEE8A ; SEG 5, A/C, Clsd Lp & Cool FAN
.dw LF4EF ; SEG 6, Log RAM to MCU, Cool A/D
.dw LEB74 ; SEG 7, L.U. Coolant var's
.dw LCC52 ; SEG 8, Do Nothing, exit w/RTS
.dw LE375 ; SEG 9, Inj Air Managment
.dw LEC2D ; SEG A, Lk UP Man Air temp Var's
.dw LDEF1 ; SEG B, EGR
.dw LE781 ; SEG C, Can Purge
.dw LF0E8 ; SEG D
.dw LDDE6 ; SEG E, TCC (A/D voltage convert)
.dw LED91 ; SEG F, Fuel/Air Major Lp
We need to find one that doesn't seem to be too full and then insert our JSR in there.
Seg 7 looks to be a good candidate.
Use the "find" function and search for the address (Label) LEB74.
Note: don't be confused by the term label. The "L" used to indicate "Line" number within the program.
If this were not changed to be a label (by adding ":") where the line used to be,
The code would still jump to that Line, not that Label.
Anyway,
You will find this
Code:
;**************************
;MAJOR LOOP SUBROUTINE, SEG 7
;
;LK UP Coolant var's
;
;**************************
;
; LK UP Rich/Lean Offset Vs Coolant Temp
;
; TBL = BIN VAL
;
LEB74: ldaa *L005D ; COOLANT
cmpa #0xD0 ; 208d = 115c
bls LEB7C ; BR IF LT 115c
; ... else
ldaa #0xD0 ; USE 115c MAX FOR LK UP
LEB7C: ldx #LC4AD ; Rich/Lean Offset Tbl
jsr LF3FF ; Call 2d Lk Up, No Offset (A = Ind. Var.)
staa *L00D8 ; Lean Offset, (if Cool) fm Tbl
We will now edit this area to move the "ldaa..." stuff down to the next line leaving the label LEB74: where it is.
New code =
Code:
;*****************************************************
;MAJOR LOOP SUBROUTINE, SEG 7
;
;LK UP Coolant var's
;
;*****************************************************
;
; LK UP Rich/Lean Offset Vs Coolant Temp
;
; TBL = BIN VAL
;
LEB74: LDAA #0x00 ; load number zero to select channel
JSR LF2F7 ; Do read of Analog channel (result in A register)
STAA L0170 ; store for later use
; ADDED ABOVE LINES FOR WB READ AT CHANNEL 0
ldaa *L005D ; COOLANT
cmpa #0xD0 ; 208d = 115c
bls LEB7C ; BR IF LT 115c
; ... else
ldaa #0xD0 ; USE 115c MAX FOR LK UP
LEB7C: ldx #LC4AD ; Rich/Lean Offset Tbl
jsr LF3FF ; Call 2d Lk Up, No Offset (A = Ind. Var.)
staa *L00D8 ; Lean Offset, (if Cool) fm Tbl
Putting the acual code here will run each time this routine is executed.
My original plan was to put the code at the end of the current code and then put a jump here to go there and then return.
If we do this it is not even needed, it will just run.
Now you make the change in the ALDL output word.
Do it exactly as you have shown above.
SAVE THE FILE WITH A NEW NAME.asm !!
Use APYPWB.asm so the commands to follow in the next step are easier to follow.
You have now successfully edited the source and are ready to make it runable.
To make the file usable there are several steps.
1.) Fist you have to "assemble" it. (Using the Dewtronics Assembler program)
This will also create documents with full address listings that will help you locate any errors that may occur.
2.) Then the assembled files will be linked together (by ASLink program)
this will take the assembled files and create an "S19" file.
3.) to convert the S19 into a binary format file you will use "Bincvt.exe"
Then the file will be able to be opened in TunerPro for editing as you normally would.
You MUST load it and perform a save so the checksum is updated to reflect the code changes that were made.
Once the bin has been saves, dump it to a chip and start your car (Hopefully without a SES light)
The steps to perform this are also listed in Cobra289's document but I will state them again here.
This procedure assumes you have the assembler installed at C:\AS
Adjust the procedure for your installed location.
Get a DOS command prompt window. (type "command" in the run box)
type "CD \" enter (gets you to the root of c drive)
type CD AS enter (gets you into the "AS" directory)
Type "AS6811 -xlosf APYPWB.asm"
No errors should be reported
Type "ASLINK -C enter (starts the linker)
Type "APYPWB.asm" enter (designates the file to work with)
Type "-S" enter (creates the "S19" file
Type "-E" enter (Exits the linker)
Type "BINCVT APYPWB.S19" enter (this makes your bin file)
The process should look like this attachment.
Now, open TunerPro and load this bin file.
Save the bin. (checksum now updated) File is ready to run.
Setup your "compare files" to look at this file and the file you started with "APYP 6E.bin"
Do a compare on the two files using the difference tool.
**** be sure to check the box to look at defined items only ***
You will only get the calibration differences then.
Otherwise all of the code being shifted will show everything from the location you changed forward as being different.
The only difference should be the checksum because it was updated.
Now you should setup YOUR original file that you have been running in your car in the compare setup box.
Select your original bin with the check mark to be the compare file.
Then run the difference tool and do a difference scan on it compared to the new WB file. This will allow you to copy your existing spark, fuel tables etc to the new bin.
Now go outside and confirm this works
Hopefully there will be a sucess story at this point. Usually its not that easy though.
Create the entry in the ADS as shown here.
Now you can see it.
Don't forget that the engine run time counter will display screwy now.
Try changing it to 8 bit and only the address word 52 will be shown. Might still read somewhat then.
Good luck
JP
Did you mean "xlos" instead of "xlosf"?
The "Source code for dummies....Ask questions here!" thread said nothing about an "f" after "xlos".
*EDIT*
nevrmind, that didn't change anything... I'm still getting the same error.
__________________
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
Looks like an error because the file can't be found.
Did you install the assembler into "C:\AS" ??
If not then you must get the command prompt to that directory to execute it.
that is probably why you got the error.
The "F" is a neat feature that Z'69 turned me on to.
It shows which addresses were relocated during the assembly.
They are then marked in the LST file for you. Nothing you really need but a neat.
Looks like an error because the file can't be found.
Did you install the assembler into "C:\AS" ??
If not then you must get the command prompt to that directory to execute it.
that is probably why you got the error.
The "F" is a neat feature that Z'69 turned me on to.
It shows which addresses were relocated during the assembly.
They are then marked in the LST file for you. Nothing you really need but a neat.
Yes, it was installed to C:\AS
This is what happened when I tried it the other way...
When you are at the prompt in the C:\AS directory.
Type "dir *.exe" and see if the AS6811.exe exists
Mine is installed at 00ECM\AS
As you see in this pic
I don't understand all the other folders you typed the command to (like symantec etc they would have nothing to do with it unless they are inthe path to the executable.
I'm having problems with the aslink, it's hard to write out the full address of each file with it.
Symantec is Norton Firewall... Could this be what's screwing stuff up? Your download folder "ASXXXX" doesn't have a subfolder called "Symantec"? How could a firewall make random folders? I hope this is not the case...
__________________
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
Copy everything from the folder where AS6811 is located to the C:\AS folder.
Make things easier.
Edit:
I think you are using a newer version. I saw that directory structure on the website.
This is the version I use (don't remember if I'm using the optimized or not)
They both work and don't have that crazy structure to them. Alan Baldwin's Assembler Package
might make things easier.
Copy everything from the folder where AS6811 is located to the C:\AS folder.
Make things easier.
Edit:
I think you are using a newer version. I saw that directory structure on the website.
This is the version I use (don't remember if I'm using the optimized or not)
They both work and don't have that crazy structure to them. Alan Baldwin's Assembler Package
might make things easier.
I downloaded the 1.5 version. What a difference...
Attached is the successful DOS screen. Look over it and see if it looks alright.
*EDIT*
APYPWB.bin is now alive, I'm about to go out an test it!!!!
Hopefully this is the final little problem. But when I created a new ADS entry and tried to save it, I got the following error message:
Mismatched ADS and XDF File
*EDIT*
I tried using RednGold86Z's xdf file: GTA 165 6E 6-7-06 TPS AE
The new ADS entry saved without errors. Now it's time to try it out!
__________________
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
If the ADS is edited the default file no longer matches the xdf for datatracing ability. No biggie.
You need to go to the XDF menu and select "edit header info".
Go to the association tab and select your current ADS file.
The message will then go away.
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
For about a minute long data run. The csv file is over 900MB in size with 4793 samples... Help? I can't even view it in excel due to its size....
Ok, there's more... None of the sensor data is reading correctly in tunerpro replay thing...
*EDIT*
nevermind, just tried it on my other laptop and it all works...
__________________
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
Ok, there's more... None of the sensor data is reading correctly in tunerpro replay thing...
*EDIT*
nevermind, just tried it on my other laptop and it all works...
Glad to see you are sorting it out
Sometimes you get ahead of yourself and cut corners that come back to bite you.
Glad it worked in the position we put it in or we'd be back to doing it again
You can double check my math for the ADS too.
there's a thread called "scaling the moates A/D" that I detailed the calculations. They look good to me but it never hurts to have another brain.
(yea, I left myself open on that one)
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
Why would you want a patch when you have full source code?
Grab the files we indicated, make the small changes and reassemble.
Good to go and you're set to make any future changes as well.
Dirtbik3r never did this before and was successful by trying.
Try it, you'll like it
I'm not 100% sure the way we did it was the best way, you may see a better way to do it in the process.
Could put it up on Moates site (after testing it to be sure there are no ill effects)
Everything in this thread tells you how to do it. Nothing less, nothing more. If you find a place to host the bin, I'll post it.
Quote:
Originally Posted by JP86SS
Why would you want a patch when you have full source code?
Grab the files we indicated, make the small changes and reassemble.
Good to go and you're set to make any future changes as well.
Dirtbik3r never did this before and was successful by trying.
Try it, you'll like it
I'm not 100% sure the way we did it was the best way, you may see a better way to do it in the process.
Could put it up on Moates site (after testing it to be sure there are no ill effects)
Why would you want a patch when you have full source code?
Grab the files we indicated, make the small changes and reassemble.
Good to go and you're set to make any future changes as well.
Dirtbik3r never did this before and was successful by trying.
Try it, you'll like it
I'm not 100% sure the way we did it was the best way, you may see a better way to do it in the process.
Could put it up on Moates site (after testing it to be sure there are no ill effects)
I'm 90% sure there isn't any bad effects. The timing problem I'm currently having is not related.
How much different would the AUJM bin work with the above method? Anyone?
__________________
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
What are the differences? The values or the bin itself...
__________________
Bilstiens shocks/struts, Heavy Duty Sway Bar, I-Rotors Front drilled/slotted, HPS Brake Pads, spohn adj. lower control arms, spohn adj panhard bar, subframe connectors, wonder bar, ford 9" rear end /w 3.89's, Rear willwood 12.5" disks /w 4piston calipers and integrated E-Brake, SPDC 360 crate engine, new painless MAF TPI wiring harness, msd 6al Box and 8.5mm wires, MSD pro billet distributer, vortec holley stealth ram, Modified prom =) (165 ECM), and of course I can't forget the 4th gen ebony lether seats.
There isn't a hac of the aujm.
So you can't do it near as easily.
You would need to do a patch instead, or at a minimum hac the bin.
And then make it relocatable. Then stick your stuff in.
Code wise there should be little difference between the bins.
But only a one difference is all it takes to prevent you from doing it.
Using the bin you started with will save you lots of time.
__________________ 00 S10 416 LS3 4L80E AWD - in progress
89 GTA 355 A4 sold
69 rS 383 A3 sold
68 SS 468 M4 sold
There isn't a hac of the aujm.
So you can't do it near as easily.
You would need to do a patch instead, or at a minimum hac the bin.
And then make it relocatable. Then stick your stuff in.
Code wise there should be little difference between the bins.
But only a one difference is all it takes to prevent you from doing it.
Using the bin you started with will save you lots of time.
The APYP work perfectly besides the fact that the timing was jumping all over. As soon as I tried the AUJM, the problem was solved... Could the APYP bin from moates be bad possibly? I had a thread about this 2 weeks ago. Anyway, thanks for the info.
Thanks to you guys (JP86SS & Dirtbik3r) for working so hard on this wideband hack it works beautifully. I do have one question or problem when I use a chip with the wideband hack i have a constant service engine light. If i use a chip without the wideband hack no service engine light. Is this something you have experienced or seen before.
You shouldnot have a service light on, That means there is a problem.
To confirm if it is due to the changes made, put AA in the mask ID byte.
Burn the chip and try it.
If the SES goes away then double check that you have the checksum correct (automatically calculates in TP when saved) and put the original value back into the ID byte. If you made the mod in a hex editor then the checksum would not have been updated.
I tried putting AA in the mask ID and I still get an SES light. I can easily burn a chip to make the light go away so I can get the car inspected and then use the WB hac chip for datalogging. I would appreciate any other suggestions.
they would have nothing to do with it unless they are inthe path to the executable. 
