So I have been reading up on things all day trying to catch back up on what is the latest and greatest (haven't touched my PROM stuff in about 2 years... went to Iraq for a year). I hear that the Super AUJP version 4 has a lot of fixes in it... Is it done and available? I looked at Moates' site and it doesn't appear to be there so I am guessing it is still being tested and tweaked. Can somebody verify this? Also, has TunerCat offered an updated definition file to work with the extended VE maps from Super AUJP version 3? I used to use TunerCat but I am at work and don't know which version of the definition file it is/was.... I have a 383 Miniram'd engine with a T56 and the .bin in the 730 ECM right now is based off the initial Super AUJP I believe which probably needs to be upgraded... TIA

I think alot of us are waiting, but it's alot of
work and checking everything to make sure
it is working

Oh I understand it is a lot of work... I have just been out of the loop for so long and it is hard to figure out what is what by doing searches and reading old posts and replies...

Anyone know how this is going and what it will consist of

I don't believe Tunercat ever had definition support the S_AUJP series changes. I could be wrong (it's happened before!).

It does exist and is good working code. That much is for sure.
Listing all the things we've done to it and the docs for using it (Instructions for using with CCP and EGR, XDF,ADS, ADX, etc) is the slow part now.
I am listing the changed items (XDF,ADS) so you can edit them into your definition files if desired.
That way TC does not need to support the changes. It's a DIY thing.
I do not believe we will release complete definition files just because of naming conventions causing diufficulties with supporting it. (Unsupported files will probably be available though)
I'm basically holding up the works (and have been for a while)

A quick list of changes:
Selectable sensor WB
Extended VE tables (Rbob & Z69 versions)
PW limiter corrected
Extended PE table & selectable use
VSS retard table (Launch ) selectable use
8K RPM
Knock light (selectable Knock, PE, AE TPS,AE MAP light)
MT/AT selection
Shift light (generic operation currently)
Lock BLM in PE selectable now
Idle spark table selectable now
ALDL status of AE map, AE TPS, PE actions, Calculated VE, others
F11, B3, E10 reads added to code and ALDL options
Open loop Idle selection/setting if desired
And more...

Now if I can just get the files completed and stop playing with it...

It's not too far off, Keep prodding or it will take longer

Indeed... Good point! Boy was I spinning my wheels for a while (and not the ones on the car)...lol. I have not used the TDF editor before and I don't know if I really want to either... Maybe now is the time to jump to a different editor.

Wow... And those are all changed/improved upon since the version 3 S_AUJP?

Can you elaborate on what the VSS retard table is for? I am confused on that one...

Forgive my ignorance please, I read a LOT on this board but am still as confused as the first day I started reading (shortly after the DIY board started). I have read about the S_AUJP but I dont know if I know the answer but does it work with an auto or manual car? or only auto, and does that mean the MT/AT selection on V4 will allow for either?

V4 is currently being used in Auto and Manual cars.
Some additional tweaks to the IAC parameters may be needed for MT use to better match AXXC operation. Tester(s) reported good results

The VSS retard will allow for some timing to be pulled out if the TPS% is greater than "X" at 0 to 60 MPH. Might give some traction to cars of higher power off the start.
I don't have a good enough launch to test this but should work .
Last minute addition and will need some feedback on that feature.

V4 is a huge step above V3 from everything i have read about it.
im really looking forward to playing with it.

JP, stay off the MCSS boards,.. J/K,.. on second thought, no, im not, get to work

Very cool... but I should be fine on the traction myself (11.5" MT ET Streets + LCA relocation brackets + adjustable torque arm with pinion angle set to -2*, etc. ). So hopefully I won't need to use that... But ya never know!

This might have already been covered, but is the WBO2 going to be there just to log something like an LC1's programmable analog output or will the WBO2 readings actually be used by the ECM for VE shaping and such? Also, and this one is probably an easy answer, but I didn't see it yet in my readings... But will the WBO2 selection cause the SES light to stay lit? I remember that one of the patches out there did that but I don't know if this one is that way...

THANKS!

WB is for indication/Logging only (for now)
This bin will NOT turn on the SES light unless you have an error
I did find why that happens in that other patch but forget what I found at the moment.

I'm really excited about the open loop in idle option, My motor is a nightmare to tune idle in closed loop.

Hi there,

Sorry I bring it back this thread.

Is there any estimated time for the release of the S_AUJP-v4?
Please don't take this as a push, but I like to know if I can plan my first engine start with this version. (Postponed to halve September)

If it is not viable than I will start with the v3.

I like the "Knock light" could find where to hock-up (pin number) I know that was explained before!

Thanks!
Cobra289

You said to keep prodding, so here we are

impatiently waiting

That patch used a memory location already in use. It was the TPS high/low bit that activated the SES.

Good job on the SAUJP_V4.

Prod felt
Keep them coming if progress is not seen.

I've had good luck with the v3 so far but I will jump on the prodding bandwagon too .

Although my original desire was to idle in open loop with my combo and I have actually gotten it to idle in closed loop fairly well at this point... Still some cool features in v4 that I would like to mess with though.

Speaking of... I haven't touched the car at all in nearly a month now! Eeesh... Been busy with other stuffs.

Thanks for all the hard work JP!

Well you said to keep prodding so heres a little jab

Just did some more of the detail documents early this week.
Its getting closer.
Added info on using extra inputs on the 730 as well now
Keep poking

Thanks for the update

I should have my 58 vette with 5.7 vortec w/miniram running soon. This will be a good start for it.
Thanks for all the work.
Ron

Patiently waiting.

Where can I find out about v3? Read up on it in these docs that seem to be mentioned? I'll do a search on here as I'm sure there is info on this site about previous versions, but hoping there is a specific site or page where all info is being held at, for ease of viewing, download, etc.

Thanks

I think you can get it off of Moate's site in the File Manager section.

No you are right. Any "implementation" of S_AUJP has been done strictly by individual users of TunerCat.

However, in the past, TunerCat has been agreeable to distributing "special TDFs" on past calibrations to valid owners of the regular calibration. So if anyone wants to work on developing a "TunerCat" version for the $8D, Tunercat will usually distribute it free of charge to any valid $8D TDF owner.

But, as TunerCat does own the original $8D and the S_AUJP version is still basically their $8D (with some modifications) - Tunercat wishes to reserve the right for distributing (or so this has been their policy in the past).

CAN'T WAIT for the v4 to arrive. I wish I would've gotten into tuning earlier so I could have helped beta. One thing I haven't seen and didn't know if its being considered but, 2 and/or 3 bar support? Is that going to be implemented ever or are we left to going $58,$59,$60 if we want that?

No boosted support in V4.
Only N/A for now anyway.

I (and others) do own & prefer Tunercat. All I need to know is the description and location of the various changes and the dimensions & increments of any tables that may be involved. I hope the objective is to have people use Version 4 of AUJP and not to force them to use other bin editing software.

The only factor that limit me to implementing any changes to TunerCat's TDF are my health which I must co-ordinate with other personal issues that also demand attention.

The docs I'm preparing are setup so any software can be used. No push to require a specific logging or editing package.
Addresses and conversion info to be provided.
Screen shots of TP will be included because thats what I have for the editing definitions.
TunerPro, ScannerPro and DataMaster will also be included for the Datalogging section.
I'm only including items specific to the V4 in the docs.

Can you post the documentation related to the earlier versions (or a link where it can be found)? Then I will add V1-3 now and contact TunerCat regarding make S_AUJP V1-3 available free of charge to all registered owners of $8D.

The only editing item is the extended VE table from Rbob's patch in V3.
This table has ben expanded even more in V4. Details on the table layout will be provided. Now I have to go and remember if both tables are supported.
I know they are both in the V4 but I don't remember documenting a selection bit for which to use.
More work

Is there any advantage to a "selection bit"? In other words, why would you want to use the smaller table when the bigger table handles it all? Sure, a person may not need the higher rpm values because their engine doesn't rev that high. But they just don't have to do anything with the upper values other than fill them with the values where they cease to operate anyway. I say, "Keep it Simple(r)".

Just backward compatibility to be able to directly import your existing cal values if you were already using the patch.
The new table is nicer so I guess the users can just make the conversion.
I belive 69Ghost made a conversion spreadsheet once upon a time.
I'll see about including it. Would be a nice adder to making the switch to the extended tables easier by filling in the extended cells based on the existing table.

We're getting close on the documentation, real close.

A couple of other questions I saw that may have not been answered (JP is real busy right now), but I'll list a couple of things I've been able to do while testing V4 in my manual tranny car:

Dual WB's (LC-1s in my case, one on each bank of the motor), with output from both going into the data logged stream

Fuel pressure now being logged in the data stream as well

Setting the in dash shift light to come on at any RPM desired, as well as controlling how long it stays lit

Knock sensor LED on dash so I know when the ECM is detecting knock. The light has also been tested to be able to display when in PE, when in MAP AE vs. TPS AE (but currently can only have one function displayed (knock or PE or MAP AE or TPS AE)

You can use a WB 0-1v output to replace the original NB O2 sensor if desired, but I have not done that one personally.

Manual tranny - I've been the main guinea pig for this part and have found NO problems. I had several with the standard S_AUJP (previous versions).

I'm also working to document the procedure to include ECM temperature control of both electric fans. Unfortunately that has been slowed down with my Acilles tendon surgery 2 weeks ago. I'm at least 3 weeks away from being able to get around much and definitely can't work a clutch while wearing this big clunky no-weight-bearing cast on my left leg....

Ooo, this is sounding really good.

Prod?

bump

Actually put a bunch of hours in it today.
Getting closer...

I did conclude that ONLY 1 extended VE table is supported. No need for both.
The higher resolution Z69' one is available.
The bit selects if you want to use it or the stock table.

The thing everyone will jump on is the doc on how to use new added inputs.
Will be cool....

Sounds a lot friendlier. Can't wait.
Thanks

V4 sounds sweet! I am patiently waiting. Good job guys!

Still working on this, haven't dropped the ball yet.
Bump for the new guy.

Pic of the upper VE table.

Is this only going to pupport up to 6400 RPM? If so what will the computer do for engines that run higher than that?

If you, all ready, run THAT engine with the standard eprom, than you don't have to worry.
The standard goes till 5600 rpm and these guys did add till 6400, it is almost 1000 rpm added, is that not enough?

Probably nothing will happens, the eprom will use the top row (6400 rpm) as basis for the calculations.
I suppose that you don't want to tune the VE above the 6400 rpm!!!!!

Regards,
Cobra289

The V4 adds 8K rpm ability to the P.E. table.
That takes care of that issue.

Thanks for clearing that up. I am already running 6000+ but I think I will go higher once I install the rev kit I have, thinking more like 7000 or so

bump