84Elky

Revision 2 November 22, 2021
This v7 Revision 2 Release contains the following new and revised files. BIN FILES WERE NOT CHANGED.

New:
C4 Corvette CCM Commands.ADXNL
Revised:
MUST READ ME FIRST (With Rev 2 Nov, 2021).docxNL
S_AUJP v7 R2 NA.ADX
S_AUJP v7 R2 TURBO.ADXNL
S_AUJP v7 R2.XDFNLNL
Revision 1 October 15, 2021 (was previously 2016-apologies)
Documentation was updated to reflect an omitted description of a correction to the Shift Light logic. No other files were changed. Below is a summary:NL
Acknowledgement
This project would not have been possible without the much appreciated assistance of Mark_ZZ3 who provided valuable Turbo insight and performed extensive in-car 1 Bar Normally Aspirated (NA) and 2 Bar Turbo testing. Sincere thanks Mark for all your work, your willingness to perform unending tests and for your patience with the multiple Beta versions!

His Turbo project can be seen here:
https://www.thirdgen.org/forums/diy-...t-turbaro.html


About Turbo Version 7
BIN
In one BIN, S_AUJP Version 7 (v7) now provides 2 and 3 Bar Turbo support while continuing as before to support 1 Bar NA engines. The included documentation describes the two Scalars and the three Tables that allow quickly configuring for Turbo operation. No changes are required for NA users other than to transfer an existing Calibration to the v7 BIN as explained in Appendix A of the documentation.

XDF and ADX
The v7 files contain significant updates.
Turbo Users: Must use the provided v7 XDF file. A prior version ADX file can be used if the Turbo items in the provided Turbo ADX file are added.
Current S_AUJP Users: Can use v7 with prior S_AUJP XDF and ADX files for NA operation.

What v7 does

• Provides extensively-in-car-tested 1 Bar NA and 2/3 Bar Turbo support.
• Allows immediately running Boost by merely entering the MAP sensor Bar type (2 or 3), and updating or entering a few Turbo-related values.
• Automatically handles MAP conversion from 2/3 Bar to 1 bar equivalency for 1 Bar NA operation when not in Boost.
• Includes changes to Shift Light logic, Knock Bit On-Timer and XDF ALDL Reporting Scalar renumbering that were to be in Version 6 Update A, but which was not released.

What v7 does not do

• Wastegate control is not handed by the ECM. The wastegate must be controlled manually, or with a separate wastegate controller.

All feedback appreciated. Happy Boosting!
Elky

Mark_ZZ3

Thanks for the code! It makes for a great driving car ... all the best of NA mode, and then boost tuning when you need it. Great to see this in production for all to enjoy.

Mark.

icsamerica

OMG, I'm stunned! Thanks. Where do I send gifts?

ULTM8Z

We're extremely fortunate to have people stil this dedicated to these platforms... allows the rest of us to still enjoy these cars to their fullest potential.

Mark_ZZ3

Food for thought ... my 305 TPI with a Turbo runs 13's at the quarter mile drag ... all with S_AUJP. And you can drive it down to local malt shop without any issue ... just like a stock tune. Its quite impressive.

icsamerica

Anyone know what injector size the V7 Turbo features were developed with? I'm not able to get a decent idle unless I raise my fuel pressure sky high with 32lb injectors. With a 1 bar the car idles and drives perfect fine out of boost (open throttle body) With the 2 bar, AFR's are in the 20's and I get stalling / bucking. Something isn't right with my setup and I'm thinking the injectors are far off from where the V7 was developed.

Mark_ZZ3

I run mine with 38's. Boost table is a pretty linear increase over boost. The key is getting your VE correct in the 90-100 KPA as that is what the boost is based off. If you are lean in boost, then move the VE in the 90-100 columns up.

Get it running with a 1 BAR and your VE table correct. Then going to a 2 bar is just adding in boost.

For me ... when I ran 38s in place of 19's ... I started out with a VE table at 50% of the stock value. Then worked my way up to where it was happy. The inj constant I lowered a bit so I could get the VE where I wanted in and not getting too close to 90%.

Mark.

Orr89RocZ

iTrader: (20)

Nice!

i believe Vanilla Ice on this forum had already done a boosted $8D code but not sure if it was the extensive super code version lol

i had already sold my turbo tpi setup a year or so prior and never got to test it. This looks great tho, i will have to look into it more. I always went code $59 on 730 deals with good success.

84Elky

v7 was not developed with any particular injector in mind. But what happens when large injectors are installed to support boost is that idle becomes an issue (very rich). But interestingly, you're very lean not rich. Also, there should be no change in 1 Bar performance when a 2/3 Bar sensor is installed because the code accounts for the differences. So if you were idling OK before v7, there's something else causing the problem. And, wouldn't raising FP provide more fuel, but you are lean. Something not right for sure. Take a look at Post #5. It works and was extensively tested.
Also, take a look at the v7 docs where raising the threshold for Single Fire Mode is discussed. I believe Mark_ZZ3 raise his values to avoid Single Fire Mode at a low PW (see Larger Injector Considerations page 9). Can also reduce or zero low PW table values, but sounds like yours needs to be raised, or idle VE adjusted..

icsamerica

Thank you. I set the fuel cut at 2000 RPM and the car still revved way past that. At that point I knew something was really wrong and I soon figured it out. My Ostrich was not in the PROM socket. I forgot that I removed the Ostrich from the PROM and burned a chip right before my last track day. Very stupid mistake, but I blame Covid brain fog. That explains why it ran OK with 90lbs of fuel pressure. After I actually plugged in the Osterich into the PROM every think worked fine. The car idled fine but the afr's hit 16's as soon as I got into boost (2000 RPM) . I got some 60Lb injectors today from Southbay to replace my 32's that I hope to install tomorrow.

If anyone cares the car can be seen here... It's a AFR 195 headed 406 with a 212/218 cam with 1.7's, A Super Ram and Northstar DIS. The air cleaner is from a Bugatti Veyron but that car uses 2 of them. I could just keep up with a super charged LS1 corvette in the brick of a car that is my Jaguar. After this session the corvette driver confronted me in the paddock, I thought I was getting swung at (happened once before) ...a man of few words, he barked, open the hood. He was relieved when he saw a Chevy and his disposition changed quick.

icecold

this is awesome guys, i have been out of the third gen game for 15 years, but tonight i ordered up some new programming equipment and will be dusting the car off tomorrow and hopefully at least getting it started.

this is going to take me some baby steps to get back into the game as the last logging software i used was diacom and to erase chips it was a light. cant wait to get started it looks like you guys made a ton of headway since i put the car in the lift and pulled the battery.

thanks for all the hard work as i really like keeping the factory computer and running boost.

MikeT 88IROC350

I have been trying to modify this version 7 ADX, to connect up to my '90 C4, NA L98 engine, with no luck at all. I have set up the commands EXACTLY like my Corvette ADX has, which connects up less than 10 seconds.
This version, just flashes the gages and numbers, and the connect window flashes from blue to red, with errors. I am not sure what else to do. Would like to see if anyone else has some tips.
I would attach my 2 ADX files, but it's not accepted file type.

84Elky

Put them in a zip file and then they can be posted and I'll take a look.

MikeT 88IROC350

Ok, tried to zip 2 ADX files.......hope i did it right.

84Elky

Reviewing files. But need you to do something. Open your working ADX file in a text editor or word processor and post the format version of the ADX Editor. It will be on the first line in the file and look like this: <ADXFORMAT version="1.01">. DO NOT SAVE THE FILE. Just exit the editor.

MikeT 88IROC350

Here it is:, i copied a few lines from the text editor, of my working Corvette ADX stream.

<ADXFORMAT version="1.01">
<!-- Written 10/20/2021 09:02:22 -->
<ADXHEADER>
<guid>d32320b3-f112-4e87-9847-4faad0f964a6</guid>
<flags>0x10001</flags>
<objectcount>117</objectcount>
<userversion>$8D-1227730-V1.1</userversion>
<author>Mark Mansur Edit JeepsandGuns Edit CaptainKawasaki</author>
<desc>ADX modified by JeepsAndGuns of GearHead-EFI.com and IFSJA.org
Datalog dash changed, missing items added in, and some names and values changed to make this more user friendly. Connect Macro from James93LT1 and pasted in by CaptainKawasaki</desc>
<baud>8192</baud>
<DEFAULTS datasizeinbits="8" sigdigits="2" outputtype="3" baud="0" signed="0" lsbfirst="0" float="0" />
<connectcmd>Connect</connectcmd>
<monitorcmd>COMMAND0MAC</monitorcmd>
</ADXHEADER>

84Elky

Tks. Try the attached file and LMK. There are some things in the Corvette ADX that are different than the new file. I added/changed them in the attached.
If it works, I'll elaborate on what done.

MikeT 88IROC350

I got this modified ADX, and put it over to my datalogging laptop. I will test it out soon, thanks a million.
Working togethor, we know more!
Mike

MikeT 88IROC350

Victory!! I was able to connect up to my C4, with this modified V7 ADX. Took a few seconds, but thats kinda normal. Just ran car at idle in garage, for a few minutes. Seemed to stay connected. Have to wait for a nice day, to take a road test and log some data!
Cheers to Elky!

84Elky

Glad it's working. The only reason it does is because I had to edit the ADX file with a text editor which is a big no-no, but at the time did not know what to do to get the missing actions. Here's what everyone with a Corvette or a car with CCM, BCM or ABS needs to know.

The following 2 lines are required in the ADX in order to control the above-listed modules:
<connectcmd>CONNECT</connectcmd>
<monitorcmd>COMMAND0MAC</monitorcmd>
The second line is in the S_AUJP ADX. It is inserted into the ADX when this Command is entered: Mode 1 ALDL Dump Request Macro. It's the first line that was missing in your ADX Mike, so it was added via a text editor. But I now know that was not necessary (knew it was not proper), thanks to Mark at TunerPro who noticed that the ADX Header Data item does not have the Connection Command selection specified as "Connect". When this is done, the <connectcmd>CONNECT</connectcmd> line is added to the ADX file. Mike, you need to change your ADX accordingly and the <connectcmd>CONNECT</connectcmd> line will remain, and your ADX will be forever correct:



There is another issue that may or may not affect proper operation. It has to do with the Repeat Count of the "Connect Macro". In that macro, Silence CCM and Silence ABS actions are executed 5 times, each followed by a 50ms pause. Below is the first of the 5 Connect Macro actions:
<ADXMACRO id="CONNECT" idhash="0xE7B186B1" title="Connect" repeatcount="10">
<NODE commandID="SILENCECCM-LT1" repeatcount="1" />
<NODE commandID="SILENCEABS-LT1" repeatcount="1" />
<NODE commandID="50MSPAUSE" repeatcount="1" />

In some Corvette ADX files, the "repeatcount" value for the Silence Actions shown above in blue is "1". In others it is "5". Again, Mark at TunerPro provided an answer as to how this value can be set =5. Thanks Mark!!!

The repeat value must be set for each Action in the Connect Command:



Still don't know if "1" or "5" is proper, but both seem to work.

Just glad it's now working, but do make the "Connect" change described above.

Elky

MikeT 88IROC350

Interesting, for sure. Not gonna quote all that you posted above, but I get it all. Excellent explanation. My C4 certainly has the CCM and ABS modules, and several others. Not sure about the BCM tho. I have counted 5 brain boxes for sure, may be more. Even tho my C4 is 31 years old, it has very complex systems installed. There is actually a "bus" or network that connects everything up. Not fun working on them for sure.

So you really think that "Connection Command" macro is what will fix my issue? I would bet on it as well. Gonna find out for sure, but certainly makes sense. Just cannot believe that i missed that one. I spent alotta time, getting all those commands and macros set up, going over them several times.

As far as the macro repeat count, for the 2 Silence commands, ya it was set to 5 in my working corvette ADX, missed that as well. It was set to 1 in your original ver7 of this ADX, for the silence commands. But, as you mentioned above, not sure with it set to 1 or 5, if it will make a difference.

Now, for sure, i can make these changes very easily.....but the modified ADX, that you posted a few days ago, works, and has these changes. Can I just use that ADX, for connecting to my C4?
Cheers again finding these little things!
Mike

84Elky

Yes you can use the ADX I sent. But for correctness, I would copy it to another ADX and then add the "Connect" command to the copy ADX Header. At that point the 2 files should be identical with copy being technically correct. If all OK, delete the file I sent and use the copy.

MikeT 88IROC350

I basically did that. Made the changes to my original working "NA" ADX, then saved it with a different name. I will keep the original "NA" ADX, for backup, then deleted your modified file that you sent. No need to have a bunch of extra files, just like to have a "working" file, and 1 backup, in case i mess something up. And yes, the backup NA file has the fix in it.
So, just now, went out and tried my newly saved working ADX, and it connected in about 10 seconds. All good. The weather looks good tomorrow, so hopefully I can take a drive and do a datalog.
Love this stuff!

MikeT 88IROC350

Elky, thanks for the updates. I downloaded the zip file, and saved all the new files accordingly. I will use the new XDF for sure, but no need for me to make a new ADX, with the C4 commands, since I already have a working version of S_AUJP v7 R2 NA.ADX. Don't need to re-invent the wheel!

I do just want to say one thing, about your 'C4 Corvette CCM Commands.ADX'. Maybe you should make a statement above, that says this is not complete working ADX, as it is a small file, which contains the commands/macros needed to connect to a C4 with the CCM feature. Now, you do make a statement in the header, that this is what the file is for, in order to add the commands over to a working ADX. Hopefully other tuning folks realize this....

Regardless, good job on updating your Word doc, App. A, for the process to get the C4 commands into an ADX file.
Mike

JP86SS

iTrader: (1)

Well I can state the NVSRAM version works good on the 1 bar setting.
Good enough to get me to try ""Launch Mode" again and I broke my stuff again.

Finally got 4th gear to work in the 700R4 (after 3 times rebuilding input drum, HD overrun hub is in now too), took it out and was feelin really good.

Looking to do a nice burnout for the first time this year, Jumped on it and ripped the hub off the water pump and right through the radiator with the fan!
It didn't surprise me, this has happened at least 4-5 times now.
Thinking it is the clutch fan getting thrown out of balance when I rev hard and fast from idle. Bought dual electric fans so no more of that!
Anyway will be looking at the fan 1 and 2 code while waiting for the snow to stop. (Is #2 fan on F8 ?)

Thanks for all the good work on the new version Elky

84Elky

Hey JP -- I thought a lot of HP was good. Maybe you need a high speed water pump . Just kidding and sorry for the disaster after the rebuild.

Yes, Fan2 = Pin F8.

JP86SS

iTrader: (1)

Just happy the trans is working.
I just wonder if using the clutch fan is detrimental to quick revs, but thats for another thread.
Have sometime now to get all my sensors logging right and restart tuning in the spring. Want to get boost someday and this version will get me closer to that goal. Glad it will make the transition when I do finally win the lottery 🤑
I have many ADX issues (EGT, NB simulated, Oil temp, WB gauge, etc) to figure out while getting the new fans operating. Will ping with questions for sure on Launch, and others.
Jp

ralmo94

What pinout would I use with a single barrel TBi and a 7727 s-ram, on a 4 cyl?

Do I need to jump pins for a single peak and hold injector?

Trying to get everything figured out for a project, any information is appreciated, can't wait to try out s_aujp, thank you for sharing all your hard work with the community.

84Elky

Pages 32-34 of the MUST READ ME FIRST document available for download in the link below provides the needed information:
https://www.thirdgen.org/forums/diy-...ml#post6437472

Mark_ZZ3

Sharing info ... depending on your distributor your spark reference angle is going to be base timing, or it will be 90 degrees. I ran a 2.4L iron duke single TBI setup and it needed 90 degrees for reference angle. Now with a 3.0L and a more traditional distributor, base timing reference works. All my stuff has been trial and error since there was no factory setup.

Mark.
'Turbaro!
'Rat10 with a 3.0L Mercruiser (I'm just the tuner on this, not the builder)

ralmo94

Awesome someone has ran it on an i4!
Document said it was untested.
I had since discovered a couple factory i4 pinouts. Just confirming for anyone else the factory pinouts do use the jumper wire for peak and hold.

Mark_ZZ3

Jumper wire for peak and hold? Maybe I missed that?

I used a resistor in line to simulate same load as port injector bank. It works ... maybe not the ideal design ... but I never followed the books.

ralmo94

The peak and hold injectors take. Lot of amps to snap open quickly,then once open to reduce load and heat on both the injectors and drivers, they ramp down amps to hold open the injector. It is reported that operating with resistors is not good long term, and hard on the driver, and potentially the injector. There is a pin called injector sense that is jumpered to another pin, that puts the driver in peak and hold mode, so current is sensed and correctly operated.

ralmo94

On a 7730 pins d5 and d7 are jumpered

ralmo94

7727 is connector j4 or D pins 4 & 8

mikelstudy_1

I basically did that. Made the changes to my original working "NA" ADX, then saved it with a different name. I will keep the original "NA" ADX, for backup, then deleted your modified file that you sent. No need to have a bunch of extra files, Speed Test just like to have a "working" file, and 1 backup, in case i mess something up. And yes, the backup NA file has the fix in it.

mikelstudy_1

all the best of NA mode, and then boost tuning when you need it. Great to see this in production for all to enjoy.

JP86SS

iTrader: (1)

Anyone seeing issues with the "display" bits that were added for AE-TPS, AE-MAP, or PE indications?
I'm running the NVSRAM version and the bits don't jive to what is going on. They are on/off randomly.
Trying to get a feel if it is just the "N" version issue or not.
TIA,
Jp

Finally all together again (Just in time for snow)
Damper has been cause of exploding water pumps!, Now running dual electric fans too.
Mini-starter on the 400 has now eaten 5 flexplates, back to AC Delco and rear brace and all is good.

MaxpowerTA

Hello, I've been trying to setup a Bin for a new project using the latest SAUJP V7 R2 zip package downloaded from this thread. Whenever I try to load the XDF in tunerpro RT I get an error saying "Failed to load XDF was created with newer version of the software" I tried it on 2 different computers and get the same error. I then tried it with the XDF from SAUJP V7 R1 and it loaded ok, is there much difference between the 2 revs?

ralmo94

Sounds to me like you need to download the current version of tuner pro?

84Elky

Bingo.

MaxpowerTA

Yup, the issue was my tuning laptop is an old XP based machine and tunerpro at some point recently stopped supporting XP. I was able to download the last XP supported version and am now able to use the rev1 XDF but not the rev2, I guess its time to step out of the stoneage.....