After this long I'm just going to throw it out there and let you guys have some fun with it. I've been messing with it long enough and its just not going to get much better anytime soon.
Use the "Use Folder" option when decompressing the zip file.
Please read the docs before posting issues here.

I never got to test out the launch mode stuff before the snow came so be careful with that one. All other functions have been tested allot and don't seem to have any problems.
Not sure how much support I can give with the manual trans stuff but will do what I can.

Details on features can be found in this thread:
https://www.thirdgen.org/forums/diy-...r-aujp-v4.html

The definition files are NOT supported and are only included as a reference.
Edit the items into your existing files.
The included XDF, ADS, and ScannerPro definitions are the files I use and there are probably errors mixed in that I haven't noticed yet. If you do use them and find something shoot me an e-mail or PM.

Also be sure to download the "Inputs" document.
It shows how to use the additional inputs on a 730 and how to set them up in your datastream. Had to be two zip files to upload. Thanks to MonteCarSlow for giving me a head start on how to do them at the Pow-Wow last summer.

I forgot to mention there is a version for the NVSRAM module also included for those that are using it. The ScannerPro definition has VE display and a rough MPG calculation as well. Something $8D has been lacking.

Many thanks go out to Z69', Junkcltr, 1981TTA, VernW,Traxion, RBob, and many others for the input and background information provided that made this possible.

Merry Christmas and a Tuning New Year!!!

 

JP,

GO to sleep man!

Great job!
Thanks to all the people (Santa's) involved.

Regards from the cold country The Netherlands.
PS
We are all ready skating at the channels! (not me!)

 

Thanks JP.
Maybe I'll get to try out this spring.
I hope everyone that uses your files realize how much time and work you have put into your project, FOR FREE!
Hail to you.
Ron

 

Thank you sir!

Once I get my coolant leak fixed, I'll try out the manual trans stuff for ya

-jason

 

I guess this means there is a Santa Claus......lol

 

..... This page intentionally left blank

I have been reading through the doc you made up. Thank you for the hard work, attention to detail is great!. I have one question, I still don't really understand most of the DIY stuff, if I use the Wideband switches do I use the WB in place instead of the NB? Or do I use one of the other inputs mentioned about the hardware? Or is the WB for logging purpose only. Sorry for the questions, I have ben reading for a few years but I dont really get it.

 

Thank you VERY much, I wave been patiently waiting for this for a long time. I Have 2 projects that will use this in mid 2008.

 

What a nice Christmas

 

Yes, only for logging. The NB is still used like normal.
The extra inputs (as detailed in the second document) show how to use a second WB if you want also. Can be used for Trans temp, Fuel pressure, Exhaust Temp or any other sensor that outputs 5 volts.
The additional inputs are for display of "linear" items easily or can have a lookup table in an ADS file if your sensor is not a straight line scaled output.
Having the signals in the datastream keeps the data in sync with other readings.
Very handy

 

I'm confused, where's the actual files at? I see you edited the post because the link was bad, is there a new link we should be after or is this on the Moates site?
Nevermind, figured it out, for those who didn't understand it is on Moates site under file downloads and uploads at the bottom.

 

Thank you.. Have a Merry Christmas and a Happy New Year

 

like JP said, be sure to read & understand the documents before using S_AUJP_V4, there are a good number of changes. if you don't read them, you will have problems

i thought i would say i have used the wideband input by cutting E10 & wiring the 0~5 volt output of my wideband controller to my ECM for data logging of the WB in TunerPro & then setup it up in TP, it works! it matches almost exactly what is shown in the logging software for my ZT2.

just as i started to play with launch mode, my AutoProm developed a problem & i haven't had a chance to send it in for repairs yet.

to those who have worked on this, a huge , you guys rock!

 

Sweet, I'll have to try it out! Good work!

Just got the TA back from the paint booth so it's time to start tinkering with him again.

 

I can confirm that dual widebands on two of the extra inputs works fine, adding fuel pressure as well.

 

From my experimentation it appears I goofed on the Launch mode somewhere.
There is no spark retard happening when engaged.
I so no ill effects with any other functionality, just isn't doing its thing.
acts like my code section is never being executed.
I'll be looking into that but wanted to let you know not to beat your rides trying to prove if it works.
Bench finally has speed input running again, that's how I found it wasn't working.
Jp

 

OK guys,
I have relocated the problem areas and all seems good now.
There is a new version of the S_AUJP V4 posted on Moates site under Custom Binaries".
S_AUJP V4 1026.zip

The new version is mainly to correct the bin for use with the NVSRAM module.
This version has items changed so be careful when copying your current calibration info over. The extended table will need to be manually entered if you used it.
Read the doc for instructions Please.
Items at locations >L8993 will need to be manually re-entered because of relocation.

The XDF has been changed so that the NVSRAM version can use the same XDF as the std version.
XDF has suffix of "a" on it.

You can tell the new bin versions by looking at the Sequence # L8004
= 4A is the standard version for use in 730
= 4B is the NVSRAM version

I did add one feature to this version (V4 1026) that is not in the old one (V4 1024).
For myself and others who use a switcher, You can now have your program number at location L800A (Custom ID 1) for a zero to 15 display.
The ALDL can display this in the "Engine/Vehicle Speed Ratio" item (nobody uses that anyway) at item # 16.
Changes will be displayed instantly to show when the program changed.
The revised documentation has instructions how to set that up.

I've wanted to do that for some time now because its hard to mark logs at points where programs were changed. This will help identify what program was running at the time. Guys without switchers can still use this to identify versions if desired.

The Launch mode code still does not work. No ill effects, just doesn't do what I expected. Future version hopefully will have that corrected.
I've been running the bin for a couple weeks now and havn't seen any problems.
Please report any good bad or ugly.
Jp

 

First of all, thanks for all the hard work on this JP, and everyone else.

I finally got my car on the road after the new engine/trans install so I've been using SAUJP_V4 since umm, Saturday.

I have one question for now (actually I have a billion, but I think only one of them deserves asking.)

Is there any reason for all the extra fuel at in the low MAP range (to shoot flames on decel)? This is basically the file I uploaded with some modifications to the mid and higher MAP areas. I didn't touch the low MAP stuff.

 

I have the previous version and I've made some minor tweaks, but nothing to alter the lower end like that...anyway, here's an image.

 

BIG MODS, thats not going to run.
i just opened the updated version of V4 & it shows me the same thing.
it looks like we did something wrong, or maybe something happened to either the bin or the def file
wait to see what JP has to say.
i would recommend you don't try to even start the motor with that. if you already have, don't start it again with that bin.

 

Actually, it does run with it and I have been driving it with that file for the past couple days.

I think the low map situatious aren't too frequent so it hasn't been a factor for me. I've been pushing in the clutch during decel since I don't have a VSS and the engine will stall. I just didn't know if that fuel was added in as a "band-aid" for something else in the code that was changed (or to blow flames out the pipes ).

 

WTF

Will need to look at that.

The Extended table should not be used unless you have translated YOUR VE table into it. Even if the ridge wasn't in there its highly unlikly it would run well.

 

That's kinda what I thought, but wanted to make sure.
My VE table is going to be nothing like a stock TPI and since it is a brand new engine I don't have anything else to start with. Given that I don't necessary think it would be a bad table to start with, unless there is something else I should know. This will be my first time tuning an engine with this level of modifications (350 w/ Flat Hyd 224/230 ~.510, trickflow 195's, edelbrock single plane) so I have some learning to do.

 

good luck tuning that thing Stan. if you need a hand give me a shout. I'm finally getting mine about where it should be.

 

Will do, thanks for the offer Too bad you don't have a speed density

 

Start with the stock table and work from there to create the expanded version.
Your just making more work for yourself otherwise.

The error is in the XDF.
Change the Address to "9A0"
The actual running table does not look like that picture, just how it is being viwed by the editor is the problem.

I'll need to double check all that stuff in the upper area again.
Thought I had it covered...

 

hah! SD is for nerds, long live the crappy thirdgen MAF!!! LOL

 

Hmm, I don't know how addresses work yet so that is something that I have to teach myself. If you update the file let me know and I'll download or if you could email that would be awesome...

 

Highlight the item.
Press ""F2"
Change the address box to "09A0"
Save.

Table will now look correct
I just checked the other items above that address and the XDF is ok for all of them.
Looks like I just missed that one.
Sorry.

 

such that the RPM is on axis facing the lower left? That's a much better view....

 

f you hold down the "CTRL" key while pressing the mouse you can rotate the graph any way you like.
Shift will allow you to move it too.

 

Never had crossed my mind to spin the map around....sure gives a good view of where things are looking funny. And when I clicked on a "spot", the cell that applied to where I'd clicked was highlighted when I went back to the table!
Thanks!

 

I gave the NVSRAM version of the 1026b a try. It would not connect up to TunerPro. The ALDL log function seems broken. It would not respond to the BIN2ECM.exe program either. The 1026a version (non-NVSRAM) connected fine. Both were using a SST 27SF512 chip with the bin installed at offset 0x8000 (chip read back & verified). Is there anything special to using the NVSRAM version? I read through the docs a few times and didn't see anything needing to be done that is special to the NVSRAM version.

I am going to play with the NVSRAM version and see if I can figure it out.

 

The "b" version was the whole reason for my update. I tested with that version when I made the change and didn't notice anything but the launch mode retard not working. I was using ScannerPro for the most part. Not sure if I also used TP or DM to confirm it.
I'm out of town this week but will get right on that when I get back.

 

Everything checks out with the file.
Programs all connect and communicate.
I believe your trouble is with the loader.

You should be using the "rtp4-tool.tcl" file for Windows.
Its an interface for working with the board.
You will need this for Windows98SE to run the TCL file.
"ActiveTcl8.4.13.0.261555-win32-ix86-threaded.exe"
20MB so it will take some time to DL.

That is the version I use and have no problems.
I didn't try the original DOS programs to see if they still worked.
John

 

I did the classic newbie error and didn't install the NVSRAM properly on the ECM pins. After fixing that the 41026B code worked great. I used the TCL/TK tool and all the functions worked. I tried the DOS bin2ecm.exe program and it said the ECM didn't respond. This could be because I was using TunerPro for ALDL logging and it has memory leaks. If I run TP ALDL logging for a while and then try to run the TCL/TK tool........the drop down dialog box for the bin to upload will not appear. TunerPro will hog all the memory and make MS-Excel and MS-Word not work properly. Sometimes it will give a fatal error and freeze the computer. I think it does MEMALLOCs and doesn't test to see if the return pointer was good and I think it probably ALLOCs big arrays.
Anyway, the 41026B works great. Thank you.

 

The included definitions require several other edits to be made,

XDF Edits:
Coolant table row lables are incorrectly not shown as negative.
The only ones I found are:

$03AF Crank PW vs coolant
$04F6 Loop Closed Param, o2 R/L Offset Vs. Coolant Temp

To correct the labels so the graph can be used to edit:
Select the item,
Press F2 to open the XDF editor
Goto the "rows" tab
select each value and enter the correct negative value. (look at the value before you type the - so you remember what it should be)

ADS edit:
MAP Kpa value needs the 10.354 offset to be added.
(X * 0.392156) + 10.354 should be the conversion

If you save the ADS as a different file name you will get a "mismatch" error in TP until you update the XDF Header info.
Edit the XDF header information (CTRL +F2) and on the association tab, select the ADS file you are using.
Save XDF and message will be gone.

Damn Cavs just lost and are out.
There goes our hopes of getting a Championship in this town once again.

 

So I take it I am not the only one that saw the MAP KPA value skewed compared to the $8D definition file and figured out the offset wasn't there.

 

I can't fix it without knowing about it. (been over a year now)
Feedback is really important to finding errors that slip through the cracks or functionality improvements that are desired.

Good, Bad, or Ugly, Please post your results/findings.

 

FYI,
XDF edit needed:

U6 Channel Read (S_V4 Only)
Address 544D is incorrect for the both versions.
Should be 5453 to select channel 3 or 4 on U6

Description of function effected by the error:
Info Only,
You do not need to do this unless you are attempting to use Ch 3, Pin E10
Default setting is Channel 04.
Pin B3 on 730 (U6 Ch 4) Reads in counts only.
Read value is stored at address 0x01B9
Change any word in the ALDL to display the counts and scale externally.
Best output to ALDL word # 10.
(Was A/D TPS Counts 0x0094 by default)
Change at location 88DF in XDF using 16 bit size, 4 digit viewing to 01B9

Made selectable so Pin B3 or E10 pin can be used.
Make selection at Address $5453 (D453 in std hex editor)
U6 Channel 04 = B3
U6 Channel 05 = E10
*** May require hardware changes to remove pull up circuit on the input ***

 

doing a northstar coil pack setup and using S_AUJP_V4. accoring to this diy paper i need to set the max spark advance and the min spark advance to different values to allow for the 70* referance angle of the crank trigger wheel.
http://www.diy-efi.org/twiki/bin/view/Gmecm/DISdist

looking thru my xdf i only see the max definded. does anyone know where or how i would figure out where the min value address is at and i'll try my hand at adding the constant to my xdf?

 

Where do you get the rtp4-tool.tcl ?
The link doesn't work anymore?

Thanks,
Dave

 

IIRC it is posted at Moates site, not sure if it's the latest.
I'll see if I had another link to it somewhere.
MonteCarSlow may have it posted somewhere else too.

 

are you working on Launch mode, will it ever work.
Thanks for all your hard work.

 

I keep asking myself that too.
I'm figuring in the springtime once my 406 is back in I'll be tinkering again.
Must be something small that I missed that is killing it.
The definitions and docs still need to be updated and posted so you won't have to make the corrections listed.

 

Hey Guys,
Any place to go grab a fixed definitions XDF file without having to make the changes by hand? Moved to a new system after an HDD crash and hate having to relearn this all over again.
Thanks!
j

 

Any news on this yet?

 

Actually I am making progress,
Motor finally back in for the third time (F'n oil pans!)
Have about 5 hours on it so far. Tune sucks bad with too much spark and lots of fuel but it moved and showed some promise.
Was updating my definition files to have datatracing on as many items as possible and playing with the catergories,and histograms again.

Thx to LakeEffect for some good info to get me motorvated too.
Time to get to it and stop messing around
Winter is coming soon!