When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I can run S_AUJP and have wide band data logging. If I copy and paste my original bin into S_AUJP the wide band input does not work. Runs good enough on S_AUJP however once in closed loop and warmed up it idles erratically when not moving. If I am slowly moving at idle it is fine it is once I am completely stopped it starts this and will eventually stop running I have to slightly open the throttle to keep it running.
Below are some options in Tuner Pro that do not match the OriginalTune bin parameters in regards to a search of Tuner Pro for idle. Anyone have an idea on what to change first, or anything else to look at? Maybe this OriginalTune has a band-aid to remedy this. It idles great on this OriginalTune and when transferred copied over to S_AUJP bin.
This is a mild 350 with stock tpi intake with manual transmission and 7730 ECM.
Also I did get a MAT High error code 25 and live data shows it was at 302 degrees at one point and coolant was just under 180 degrees and it was maybe 50 degrees outside, also appears this code was disabled in Original Tune bin.
One is titled lameidle and toward the end at about 25 minutes the MAT jumps to 304 then you can see this erratic idle. Then lameidle2 the MAT jumps to almost 300 degrees at 8 minutes in.
I decided to watch the log with the Original Tune from the same day I ran so I could idle at stop lights and the MAT never goes above 142, but with S_AUJP goes over 300!
I'm seeing symptoms of the issue, but not necessarily the cause. For example, the spark timing starts going a little bananas after the MAT sensor jumps to 302. I also see the RPM bouncing around as well... it seems to die a couple of times and either recover on it's own, or get re-started by you.
I'm not sure why the MAT sensor would do that only on S_AUJP though. I just don't know what in the code would influence what is reported by the MAT sensor.
Have you tried to make all your S_AUJP idle parameters the same as your previous bin?
I have not yet done this, I went through every parameter and copied original tune to each one and then lost WB. I will try to go through this but idle is fine until this MAT temperature spike then it starts acting up. I stopped and burned another chip so it was more drive-able this same day and no MAT spike, I attached it here.
This is odd I also notice it appears to happen when the coolant temperature is above 175. I'll have to poke around and see what else I can see to change. Also the Innovate was acting up again so these readings were high and low during these logs I found these ALDL Word# what are these?
these log files are with what bin? S_AUJP? Or your original?
I have no idea what those two parameters are... I'm pretty code illiterate when it comes to that kind of stuff. Maybe RBob or someone else more knowledgable can chime in...
The last one is with original base bin or non S_AUJP just showing that this issue does not come up.
Is there anyway the WB input is getting into the MAT reference signal? I thought about this then checked the pin-out and these are close to each other pins F14 and F16.
I'll try running with original tune and wide band and see if I can duplicate this. It just seems far fetched that a bin would cause this.
You must verify the "range" of items copied from your original bin to the S_AUJP.
Be sure you have the latest version also.
Best to load your S_AUJP bin into tunerpro.
Then set your original bin as the "compare" bin.
Use the difference tool and copy the differences one by one up to the stock addressing only.
Items that are custom for S_AUJP are in the upper addresses of the bin (898E and above)
Those you must set manually as they did not exist in your stock bin.
Give that a shot and things should improve.
HTH,
Jp
Thank you JP I will try this I did try but not exactly to the address mentioned so will give it another shot and try to test when the salt is mostly off the roads here in MN
You may have solved your problem by now, but maybe this will help; and already solved, maybe it will help someone else. The attached information is extracted from the READ ME file include with S_AUJP v5. It explains how to easily copy a good Calibration to S_AUJP v5. HTH.
I have not even tried yet as it is in winter storage. I do remember reading this but reading it again I see: DO THIS FIRST:
See “Transfer Your Calibration and Update to V5” for how to easily move your existing Calibration to the new v5 BIN. This applies to current v4 users and pre-v4 users (AUJP2 and earlier) not yet using v4.
Does this mean it needs to be a AUJP to start with?
You may have solved your problem by now, but maybe this will help; and if already solved, maybe it will help someone else. The attached information is extracted from the READ ME file include with S_AUJP v5. It explains how to easily copy a good $8D Calibration to S_AUJP v5. HTH.
Post modified to insert $8D for completeness per JP's post.
10-28-2018, 10:26 PM
