84Elky

v6-4 UPDATE 4/20/2020
This update includes new files with the changes below:

S_AUJP v6-4a.XDF

• V4 OPT 1 (0x98E), b7, Use Z69 EXTENDED PE Table to 8000 RPM
  Description corrected to say EXTENDED PE Table. Was previously EXTENDED VE Table.
• VE Upper Table EXTENDED (1600 to 6400 RPM)
  Description corrected to reference the bit ("0x98E b5") required for use of this table. Was previously "b7".

S_AUJP v6-4a.ADX

• Descriptions of Values "Channel 1, 2, and 3" were changed to advise that the use of Channels is not required if a sensor is connected directly to an ECM Pin.

There were no other changes.
Unzip the 2 files above to update to v6-4 or make the above changes to Revision #3 files. Should changes be made to Revision #3 files, it would be advisable to save the changed files as "v6-4a" to maintain proper Revision identification.


v6-3 UPDATE 4/4/2020
This update includes new files with the changes below:

S_AUJP v6-3c.XDF

• AE-TPS and AE-MAP:
  • Updated descriptions of each Calibration item to describe how changing them increases or decreases the respective AE.
• 0x53B=AE-TPS, AE-TPS PW (Unfactored Pump Shot)
  [Corrected above 4/12/2020 ] Was previously: 0x3C7=Crank PW Multiplier .vs. Ref Pulses 1-24:
  • Changed description for better explanation.
  • Changed Column Title from “Pulses” to “Pump Shot #’ to properly reflect what they represent.
• Changed several other descriptions for clarity.

S_AUJP v6-3b.ADX

• Error 42, EST Monitor Bitmask:
  • Changed Title to Error 42, EST Failure
  • Modified description to explain what this error reports.
• Error 24, VSS Failure Bitmask
  • Error was being improperly reported using 0x047 b7 instead of b4.
  • But rather than use 0x047 b4, changed to use 0x005 b7 to agree with error reporting for ALDL blink-out codes.
• Error 41, Cylinder Select Error Bitmask:
  • Changed reporting from 0x041 b0 to 0x006 b6 to agree with error reporting used for ALDL blink-out codes.

v6-Rev #1-S_AUJP ADX Items & XDF ALDL Reporting Scalars.xlsx

• This file was updated to reflect the Error Reporting Bitmask changes made in the ADX (see above).

There were no other changes.
Unzip the 3 files above to update to v6-3.


v6-2 UPDATE 1/17/2020
This update includes new files with the changes below:

• MUST READ ME FIRST (v6-2).docx: Modified Calibration Transfer Instructions. It is not possible to easily use TunerPro (TP) to accurately make Calibration transfers, and an all-at-once transfer is not possible. This is not a problem with TP. It has to do with the content of the XDF files. Older XDF files may not include items that need to be transferred, and the new S_AUJP XDF file contains items not in the older XDF files. Use of either XDF file can yield an "Item Not Defined" message even if the "Limit search to defined items" box is checked. This then requires the user to investigate each undefined item.
  Note that the preferred and recommended transfer method is to use a hex editor so the entire calibration can be transferred BIN-to-BIN at one time. If the free HxD editor is used as described in the S_AUJP MUST READ ME FIRST.docx file, the transfer can be completed in a couple of minutes and is guaranteed to be error free. This allows immediate use of S_AUJP just as if running under AUJP, except that the code is more efficient and more data is reported if using the supplied ADX file. New features can be added later when desired.
• S_AUJP v6-2a.XDF: Updated some table descriptions to properly reflect the use of Coolant or MAT as the lookup determinant. Functionally, nothing changed.

There were no other changes.
Unzip the 2 files above to update to v6-2.


v6-1 INITIAL RELEASE 12/21/2019
Version 6 of S_AUJP contains the features and changes below. The included "MUST READ ME FIRST.docx" file describes each item. This project would not have been possible without the contribution of:Additions:

• Easily transfer your AUJP or S_AUJP Calibration to Version 6 allowing immediate use
• TunerPro ADX and XDF files. Every item documented.
• Expanded WBo2 Support:
  • 2 independent controllers reporting AFR and Raw Counts from Sensor #1 and/or Sensor #2 directly to the ECM without need for external hardware channels
  • AFR Conversion Equations for all popular WB controllers with both linear and non-linear output
    (All equations also in TunerPro format for direct copying to ADX)
• Launch Control Spark Usage Time Control
• 4 and 6 Cylinder Multi Port Fuel Injected Engine support:
  • Distributor and Direct Ignition Systems (DIS) engines
  • Spark settings (Reference Angle, Maximum Advance, Maximum Retard)
• Support for ECM Pins B3, F11 and F12
• Engine-off Sensor Diagnostics

ADX Reporting

• Air Flow
• VE% Adjusted for Barometric Pressure
• Final PW After Compensations allowing true Injector Duty Cycle % Calculation
• Distance Traveled
• WBo2 AFR Differences:
  • Sensor #1 AFR .vs. Sensor #2 AFR
  • Sensor #1 AFR and #2 AFR .vs. Commanded AFR

Revisions:

• Default Setting for Bypassing TCC Coasting Unlock if NOT in DFCO
• INT Update Delay if Low TPS & MPH
• Launch Control TPS% Activation Threshold

Corrections:

• Lock/Don’t Lock BLM at 128 in PE
• Transmission Selection
• ALDL Reporting of TDC Spark Advance (SA-TDC)
• IAC Control
• Idle Spark Adjustment

In addition to the above, an Excel file lists items reported in the supplied ADX and the associated XDF ALDL Reporting Scalar associated with the items being reported.
Please post suggestions, corrections, etc.

Merry Christmas!
Elky

ULTM8Z

Damn you, Elky! Now I wont be able to resist pulling my ECM down to try it out!!

Seriously... cool stuff! Thanks for taking the initiative to do all of this!!

BWilcox

Hi Tom,

Thanks for your continued support of the GM 7730 ECU.

S_AUJP V6 is a really great software package.

Get some rest, then start thinking about V7.

It never ends,,,,,

Best Regards,

Bruce

Six_Shooter

iTrader: (2)

Neat...

I may have to update a V6 car I used V5 on...

ULTM8Z

Elky,

Found something curious...

The scalar "AIR FUEL Param, TPS Initialization Voltage" at 0x3E5... the description says

Initial TPS voltage at key-on or if engine not running. Becomes the threshold (L0099) against which TPS voltage is measured after being lag filtered.
Factory Default = 0.94 Volts

.94 volts? I thought it was .54 volts. Is this a typo?

RBob

iTrader: (1)

$8D (among others) auto-zero the TPS to the lowest seen voltage. It starts high so that it can be brought down to the lowest seen voltage, which is then used as 0% TPS.

The ECM checks for the lowest seen voltage on a regular basis.

RBob.

ULTM8Z

Ok, that makes sense. Thanks RBob.

84Elky

What RBob said + $8d uses 0.62 volts as the default for 0% TPS if the "lowest seen voltage" is less than 0.62v.

MikeT 88IROC350

i downloaded the -3c ZIP file, then opened up the new XDF, and did not see any changes to the crank PW multiplier vs pulses 1-24 table. Looks the same to me as my current XDF. Column was "ref pulse" and the description was the same.

QuickStyle

Extended VE tables to 6400 say to use flag 0x98E b7, but description says that is for VE tables to 8000. 0x98E b5 flag is for 6400. Are we supposed to be setting b5 for 6400 tables and the description is just wrong for the table?

84Elky

MikeT you are correct. My apologies. The hex address and title of the item changed was NOT 0x3C7=Crank PW Multiplier .vs. Ref Pulses 1-24. It was the table below that was changed:
0x53B=AE-TPS, AE-TPS PW (Unfactored Pump Shot)

The text in Post #1 above has been corrected. Thanks for reporting this.

84Elky

QuickStyle: Thanks for catching this. A bit of character and bit flips in the descriptions. No functionality affected but wording wrong and confusing as you noted. Will correct soon and post an update. For now, here's the correct verbiage:

0x98E b7
Title: V4 OPT 1 (0x98E), b7, Use Z69 EXTENDED PE Table to 8000 RPM
Description: This uses RPM/31.25 and Extended VE Table to 8000 RPM. Don't see benefit of using this until VE and Spark Tables are extended to 8000 RPM.
Description should say "Extended PE Table" and not "VE".

0x9A0
Title: VE Upper Table EXTENDED (1600 to 6400 RPM)
Description: This is the Table to use if you have set the Flag bit 0x98E b7 to use Z69's extended VE Table. Otherwise use the Original Upper VE Table to 5600 RPM at 0x79A)
Description should say: 0x98E b5 and not "b7". It's b5 that controls the use of VE Tables.

Bottom line: b5 for VE Table selection, b7 for PE Table. Apologies for the confusion.
HTH, Elky

MikeT 88IROC350

No worries, just glad you updated your posted and made it right. I looked at that AE-TPS table myself, and will make the changes to my XDF as well.
Mike

Oliver667

Hey guys.

I discovered that there are adapters for our old ALDL ports that connect to an app via Bluetooth to display live information.

The app ("ALDLdroid") says that you need to have an ADX file that matches some table on your ECU. I am now trying to find such a file for my 1991 Firebird V6 3.1l automatic.

Are any of the 2 ADX files in the latest ZIP archive here good for that?

84Elky

I know nothing about ALDLdroid app, but an ADX is an ADX, No reason the 4a ADX won't work, but you have to be using S_AUJP so that is captures and reports the desired output.

Fred SS

iTrader: (3)

This is great. I planning on switching from MAF to Speed Density in the near future for my TPI conversion.

ULTM8Z

Elky,

I'm trying to do the transfer from my S_AUJP v5 over to the v6. Unfortunately, my hex-ignoramous-ness is making this extremely difficult...

I'm not understanding these hex addresses and how to find them...

I downloaded the hex editor recommended in the word document and am trying to follow the instructions. Any way to post a screeshot of what to grab and copy?

84Elky

Ok, I think we should change your TGO alias from ULTM8Z to HexMaster . Just kidding. It was not but a few years ago I couldn't spell "hex", and now I'm living in it..

Here ya go. Starting and ending highlights. In between not shown.

Start at 0x00E

End at 0xB5A

HTH, Elky

ULTM8Z

Thanks Elky. I will give this a shot.

space387

Is there a place to discuss possible features to attempt? I have an idea for use of an output that under normal circumstances is removed with S_AUJP.

SbFormula

Not that I know of.
You might want to PM @84Elky see what he says.
Cheers

84Elky

Yes, but PM is the place and you have not provided ability to receive PMs.
You can PM me but there has to be a way for me to reply.and discuss.

34blazer

Made the switch over the weekend to the version 6 from V4. It's been years since I tuned this car and seemed to forget that the z69 extended VE tables have 2 or 3 cells that must not be touched. 20,25, and 30kpa cells are to remain at 0,0, 6.64, respectively. Changing these will result in wild fuel delivery issues. Can't remember why, though.

RBob

iTrader: (1)

Sounds like the XDF is starting the table with the header for that table (BTDT).

RBob.

34blazer

Probably, but I don't know how to fix that if it is even possible. LOL

84Elky

34Blazer --
With all respect, there is not a problem with the S_AUJP Extended VE Table.

Addressing items in your post:

• Made the switch over the weekend to the version 6 from V4.

• It's been years since I tuned this car and seemed to forget that the z69 extended VE tables have 2 or 3 cells that must not be touched. 20,25, and 30kpa cells are to remain at 0,0, 6.64

I hope you find the issue, but it's NOT the Extended VE Table. Perhaps an incorrectly copied calibration from v4 to v6?

kPa (20-100, 5 kPa increment)===>
RPM (1000-3200, 200 RPM increment; 3200-6400, 400 RPM increment)
"
\/

34blazer

Elky, this was an issue in V4 years ago. JP addressed the issue back in 2010 when I first started using V4. It was fixed and an updated xdf provided, and I'm sure after 6 years I forgot which one had the incorrect addressing for the table. I just started with a fresh version 6 bin today and the z69 table is the only table that didn't have values were they were supposed to be. All good now. BTW, it was in the first few cells of the z69 table, which was in the 1600 rpm row. Forgive me for the spam, it's been a long time and I made the mistake of never noting my tuning changes.

355sbcTPI

Hi, It was mentioned that I might want to post to this thread...

I just recently upgraded my '165 MAF series ecm to '730 MAP swap.
I have a 355 TPI with Vortec heads, SLP runners, Ford 30lb BB302 injectors, Comp Cam XR276HR-12
I am using the S_AUJP v6 for the first time so please be easy on me! I am also running Moates Ostrich 2.0 which is awesome by the way.
First start up was great actually...my motor idled pretty decent with some of the basic changes I made in the chip beforehand.
I've read through the instructions on WB O2 support but I think I am doing something wrong??? I can't get an AFR in Tunerpro RT.
I have a Zeitronix Zt-2 WB controller and I have hooked it up to pin F14 for sensor #1. I am also sending a simulated NBo2 signal to the ecm which is working properly.
I have selected my WB controller on the Flags "WB OPT 1, b7"
Am I supposed to enter a formula for the WB I have? Is there other Flags that I need to check in the Bin/Xdf?
When I run the Zeitronix Datalogger software by itself...It works.
Anyway, thanks for your time.

SbFormula

For my Autometer AFR #5776 (linear):
WB2-7 set to 0 for Pin F14
WB2-0 enable
Conversion: (X*0.0343137254901968)+10
Check your instruction for conversion. This is from Autometer manual:
The Auto Meter Wideband Air/Fuel gauge has a signal output for supplying information to a Data Logger or engine management system. The signal provided is a linear 0-4 volts output. 0 volts out equals 10.0 Air/Fuel Ratio, 4 volts out equals 17.0 Air/Fuel Ratio.

Check Appendix B-WBo2 AFR Conversion Equations in MUST READ ME FIRST.docx

Yours might be non-linear
Cheers

84Elky

355sbcTPI -- Sorry you're having issues. Because we don't know how the controller is connected, you need to read pages 7-10 of "MUST READ ME FIRST (v6-2a).docx". The zt-2 can provide both a linear and non-linear output. If using the non-linear, you'll need to enter the non-linear formula found at the top of page 29 into your ADX. If linear, use: (0.0392*X) + 9.6

Be sure read pages 7-10 for how to set up everything. If that doesn't work, or if it does, post back.

Here's the derivation of the linear equation if needed. Formula needs to reference Counts .vs. AFR and NOT Volts .vs. AFR:



Also, take a look at this for more info:
http://www.zeitronix.com/Products/zt...ndoutput.shtml

HTH, Elky

355sbcTPI

Hi guys! Thanks for your replies SbFormula, Elky, also Tuned Performance from another thread...

I have to say that I had no idea that my Zt-2 wide band controller could provide both linear and non-linear outputs.
Since I am simulating a NBo2 signal to the ecm my only option is to use the non-linear output that the Zt-2 provides.

I've been jumping around back and forth from the computer to the garage all day, reading and re-reading over again the "MUST READ ME FIRST (v6-2a).docx"
I think its working correctly. I put the AFR equation conversion "X / 10" in the ADX value "WBo2 AFR-Sensor #1"
I am a little confused about how to get Raw Counts though?
If I select WB OPT 2 (0x99B), b0 = 1=Get Sensor #1 Raw Counts. I then have to enter a different AFR equation conversion in the ADX value "WBo2 AFR-Sensor #1"
Looking at "Appendix B - WBo2 AFR Conversion Equations" it lists two non-linear equations for the Zt-2.

Zeitronix Non-Linear (All)
AFR Conversion Equation (x=COUNTS)
-1.7215066416556963 + 1.1367611821793175x - 0.0422948541377416x2 + 0.0007981659725157204x3 - 0.00000786394929373063x4 + 3.860145708777e-8x5 - 7.394866832e-11x6
Zeitronix Non-Linear (All) TunerPro (Copy to ADX)
AFR Conversion Equation (X=COUNTS)
-1.7215066416556963 + (1.1367611821793175*X) - (0.0422948541377416*(POW(X;2)) + (0.0007981659725157204*(POW(X;3)) - (0.00000786394929373063*(POW(X;4)) + (.00000003860145708777*(POW(X;5)) - (.00000000007394866832*(POW(X;6))
)

I copied the bottom equation to the ADX...the one that say's "Copy to ADX" but TunerPro replies with "Missing )"
So I copied the top AFR equation and Tunerpro replies with "Equation Format Appears Valid"
After entering the top equation...it didn't work. I wasn't getting an AFR when the motor was running and monitoring my laptop.
I must be doing something wrong here but I am unsure how to get this to work?

Again, thanks for your time and I appreciate the insight!
355sbcTPI

84Elky

I realize it's complicated, but we'll get it working.

Does "think its working correctly" mean it's working as it should, or you're not sure? Given you are using X/10 conversion, you should have:
---0x99A b7 Set =Zeitronix Non-Linear
This will provide raw (unconverted) AFR which will be converted to AFR by the ADX when using the X/10 equation. By virtue of selecting a bit in 0x99A, an election is being made to use what the documentation refers to as an "internally-supported" controller to compute AFR.

With an internally-supported controller is used, Counts are used "internally" by the code to compute the raw AFR. So reporting of Counts is optional and for information only.

However, if you were NOT using an internally-supported controller (no bits in 0x99A are set), then Counts are automatically reported because they must be converted to AFR by the ADX using one of the equations in Appendix B.

Bottom line, when a controller is selected in 0x99A, a Conversion Equation is not required, which leads to the item below.

I don't believe there is any reference in the documentation to using WB OPT 2 for Option 1 (using an internally-supported controller). To report Counts:
XDF
- Select one of the 63 XDF ALDL Reporting Scalars and enter Address "0034" (maybe use "NV Ratio")
- Change the Scalar Title to something like: “Sensor #1 WB Raw Counts”

ADX
- Counts will be reported from ADX Value “WBo2 Counts Sensor #1”. In your version of the ADX file, the zero-based decimal Packet Offset number (currently 36), must be changed to one less than the 1-based number of the selected XDF ALDL Reporting Scalar. So this numbering requirement is not misinterpreted in the future, a soon to-be-released XDF file matches ALDL Reporting Scalar numbers with ADX Packet Offsets (both zero-based).
- The Conversion Equation should be: “X”

As indicated above, when using an internally-supported controller, an equation is not required. However, I appreciate your providing the feedback because two issues have been identified:
1)
The equation in the documentation is indeed incorrect with regard to parentheses. This was corrected in a to-be-released version. Apologies for not mentioning that in my previous post. To use a non-linear equation, remove the "(" before each "POW":
---Change "(POW" TO "POW".

As you discovered, the non-linear equations above each TunerPro equation cannot be used. They are provided to show the equation obtained from curve-fitting for those not using TunerPro.

2)
The "Missing )" message is a TunerPro mystery because once the above parentheses are removed per above, the equation is valid but still provides the message. But, despite the warning, if click OK the equation is accepted. I've reached out to Mark at TunerPro and hope to have an answer soon. For now this should not be an issue because you are not using the formula.

Follow up: It's believed the length of the formula is causing TPro to report "Missing )". It's on the list to be corrected. However, because the format of the equation is in fact correct, clicking OK will cause it to be accepted indicating it is not really missing a paren as we know. So the formula will work despite the warning. This can be proven by copying the formula to any ADX item and logging. Data will be reported according to the formula based on the value of "X".

HTH, Elky

355sbcTPI

Hi Elky...

When I had my Zt-2 running on my 165' maf ecm...I could never really tune properly. It took me a long time to figure out how to implement it into the $6E ADX...I don't think I had the formula right.
Now that I have switched over to the 730' ecm...I can see the AFR for my Zt-2 changing when I adjust the lower VE table while using the "X / 10" conversion equation. I only briefly adjusted the table at idle to see if it works.
I guess I was looking for a way to confirm that my Zt-2 is 100% working correctly in the S_AUJP code. More on my part to make sure I haven't missed anything.

Sorry, this is still new to me. I guess I was going for WB OPT 2 that I read in the "MUST READ ME FIRST (v6-2a).docx". That is why I was trying to enter the Zt-2 formula into the ADX.

This I was also trying to figure out...not sure what to do here? I don't even know how to select a Reporting Scalar?..lol I'll keep trying different things in TunerPro until I figure it out!
I wanted to make sure I posted back and I apologize for all the quotes.

Also, It's probably better for me to just stick with 0x99A b7 Set =Zeitronix Non-Linear flag because it's an internally-supported controller. I'm probably over complicating things for myself.
Thanks Elky.