This is for the 8746 61 mask.
Included in the zip; ecu file, the ram locations w/descriptions, and instructions on how to edit bin files to output different ram locations.
http://www.moates.net/fileman/index....%20Definitions

 

That is cool.

 

excellent. Thanks Jon!

Do you want the older version deleted from the share?

 

Jon, I have been wanting to find out knock retard for some time but I didn't have a clue how. I am still stuck and hope you or someone can help me through this..
Right now I have tuner cat and pocket programmer and have been tuning and burning with that set up. My timing is set up so I have no knock counts but I understand that doesn't necessarily mean anything per posts on this site.

I downloaded tunerpro, and dowloaded jon's ecu (8746) file.
i even figured out how to make the changes to the ecu file that jon suggested in his how to use.txt.

So now I have the ecu file modified but I don't know how to proceed from here. I have gone to tunerpro site but it doesn't show you how step by step. How do I get the bin and the ecu mods from tunerpro to the pocket programmer?

man, i don't even know the right questions to ask.

Maybe someone can set me on the right path.

thanks...........bob

 

Do you have the fixed ecu files up yet? I haven't checked your site in a while but when I get home I'll send you a couple newer ecu's with comments and removed bugs/mistakes. One will be EVERYTHING, the other will include the basics.
Thanks again for your excellent software support.

 

Jon,
i just did this to the eprom id locations. I put 0061h in 0x0414 and 0x0415. then I put 006Dh in 0x0416 and 0x0417. I did split them up into msb and lsb. I saved the bin I was using. Now, my PROM ID will show the final sa and the knock sa? how will I interpret that since it comes across the WinALDL screen as a decimal number?
thanks!!!

 

Here's how I visualize the tuning process and maybe this will help. First off you have calibration code stored on the eprom. Using the pocket programmer you read that calibration into a buffer. The buffer sits on your computer and just hangs out in memory. Then you save the buffer to a file, this file is a binary file (*.bin) and now you have something to edit and save on your computer. Now you use Tunerpro or any other tuning software to open up the bin file. The bin file is a bunch of code and the tuning software doesn't know what to do with it (unless it's intelligent and reads the mask ID which you can setup in Tunerpro ). Selecting the correct *.ecu file you can now edit the bin file and save it as a new file. Take this new file, load it into the pocket programmers software buffer and then program device (eprom in this case) with buffer. All done, plug and play with your new calibration.
Does this answer your question?
Using the aldl ecu file I uploaded you can edit a bin file and program it to the eprom. This new eprom will tell the ecm to output the new ram locations into the ALDL datastream to be collected through Winaldl (or any other similar datalogging software). In Winaldl, since the code changed and it doesn't have an "ecu" type file it will think that nothing has changed so for this reason you need to datalog raw values. Then using something like excel you can convert the raw values into bytes (from 0 to 255, 00h-FFh) and from there convert into real world values. An example is battery voltage. A typical real world battery voltage is 13.6 volts. The raw data for this is 136 or 88h . Winaldl knows this location is battery volts so it will display the correct decimal place location. If I get the time (which I doubt I will until next week), I'll put together either an excel file or write a program that will display and do the conversions for you automatically, you just specify the winaldl datalog file location and bin file you used, it will do the rest . Aren't I a nice guy .

 

No, I mean do you want the old version(s) removed from craigs share.

 

Okay, I burned the hex values into the bin for locations 0x0414, 415 (00, 61h) and 0x0416, 417 (00, 6Dh). I got the WinALDL data for Knock retard, but I got a big fat zero for the total SA in the PROMID A row. The retard worked fine...too well because it showed me where I was still getting a knock retard.
Thanks, Jon!

 

Jon, you are a nice guy, and that explanation sure helped this old carb guy out. Thanks man, I think I just got it to work after I read your post and figured out that you had to right click on the edit box to get raw hex values to input.

I burned two chips as a test. One without the ECU edit change and the other with the changes you suggested. At idle in the driveway the unedited bin showed 4 under the promida and 98 under promidb and 138 under volts. I then did the edits you suggested to the same bin and at idle both promida and promidb showed 0 and volts showed 147. I assume the 147 means 14.7 AFR (jeees, I hope so) when I reved it up in neutral, both prom locations spit out a few numbers quickly, so does this sound like I got this working?? Seems like it to me !!!

Ok, I will play around with this and look foreward to your help on interpreting the numbers that are now comming out of the prom Id areas.

Also, sorry about this, but when I data log, I just run winaldl and show the Blm or spark table and then when I am done, it has a spot at the bottom where you can save the table and data. which I print out later. Real simple but, When I go to the raw data table, I don't see a place to save this stuff? I will keep looking but if anyone gets a chance can you tell me how to datalog and save the raw stuff??

Jeesss, I am once again starting all over, but am turning into an addict

Many Many thanks ..............bob

 

Similar results here, except mine had zeroes in the PROM ID A row.

 

Need to place $62 in the PROMID A location of $415 (and $00 at $414).

Here is a thread over on the TBI board that covers a lot of high performance TBI tuning:

https://www.thirdgen.org/techbb2/sho...hreadid=210908

RBob.