fairly fast, when I rev out the engine and shift gears. It's almost like SES is flickering when i hit the rpm for the shift light, in my dash. Anyone seen this before? I have my shift light set for 3000rpm and 2 seconds on, but the SES flickers fast, right around the same time. This is on my '90 Y-body L98 car. Running version 6 of S_AUJP.

I dont think there is any actual codes in the ECM. But I havent really checked for them. And of course the SES light does not stay on.

 

Sounds like a corrupt bin

 

i wondered this, as well. I have 2 chips, that i alternate, with updated bins, as I go. This issue just started recently.....I roll with the same bin, making small changes as I go. I erase the chip everytime, and verify with buffer.

 

Mike ---
Thanks for reporting this. It was corrected in S_AUJP v7 but unfortunately the details of the correction were not included in the release info or in the documentation. The MUST READ ME FIRST file has been updated and posted here: S_AUJP Version 7 - Now Supports Turbo (August, 2021) - Third Generation F-Body Message Boards

Here's a summary of the issue:

 

Interesting. Not sure what I am reporting, now, after doing some reading on topic. It appears that manual cars, with a shift light, should also light the SES, at the same time. Not sure I knew this....But with mine, using vers6 of S_AUJP, i do get the flickering of the SES at the time when shift light comes on. So maybe that is the issue, that has been corrected? I was getting close, to findind a fresh new bin, vers6, and starting over with my calibration....looks like now, i have a good reason to update to vers7!?!?

I am a little confused, on what was posted at the top of your link, for the version updates. Read this below:

Revision 1, October 15, 2016
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:
Beginning with the first version of S_AUJP (v4), the factory shift light provision applicable to manual transmission cars was removed because the fuel efficiency portions of that feature were deemed to not be applicable to a high performance application (1st to 4th shift, etc.). The removed factory provision was replaced with simpler logic providing shift indication at only a single calibration-specified RPM. This made the function available to both manual and automatic transmission cars. However, the logic was flawed because not all cars are factory-equipped with a shift light bulb in addition to the Check Engine Light (CEL) bulb. Under certain circumstances, a constant flickering of the CEL and possibly an installed Shift Light bulb was noticed.

This revision corrects that problem. The CEL now correctly indicates the Shift Point RPM in all cars. Cars with a factory shift light bulb (manual transmission cars), will find that the Shift Light bulb operates in concert with the CEL.

Also in this revision, the previous requirement to be in-gear for Shift Light operation was removed. Now the Shift Light operates in P/N to allow testing of the light-ON duration.
***** END REV 1 *****

That looks like an old update? Was it fixed back then? Or only fixed in version7? Now, as stated, factory default for shift light was well over 7000, so unless you change it in the PROM, you would never there was a problem. I'm pretty sure I set mine to 3000 long time ago, maybe never noticed the SES flickering, until the last year or so? Maybe just with version 6 S_AUJP? Took vette to track over a week ago, and i certainly noticed it then, as I was going above and below 3000 quite a bit! SES light was kinda going bonkers! as always, cool stuff!

 

Yes, must use v7 if you want a corrected Shift Light.


Below is what it should have said. Just going too fast making the update. So, it's not old but very recent. Tks for noticing and pointing it out:
Revision 1, October 15, 2021 (was previously 2016-apologies)

 

Just what I thought you would say......already downloaded v7, and I am reading the Word file. Its a lot to take in, but since I already run V6 of S_AUJP, it should go smooth.
Thanks for correcting your title of post......10 of 2021 not that long ago, but 2016, yes!

As far as your new version7, just a cupala quick questions....
I see you have 1 .XDF, and 2 ADXs....I will use the NA .ADX for sure, but what about the bins.....standard and NVSRAM.....what is the NVSRAM version?

Also, took a quick look at the scalars that needed to be updated....in version6, some of them are the same as your updates, assuming I will have to confirm them, once I make the update?

After getting the update complete and working, my next task will be trying to update the commands, in the new ver7 ADX, in order to connect up to my vette. I am really hoping, that it is just "connect" command, at the top of the list, that does the trick. Looks like 5x silence-silence-pause commands, in the 1 macro. stay tuned for that, might be a while!
Best,
Mike

 

NVSRAM loads the 32Kb of calibration and code into Non-Volatile RAM of the ECM instead of using a Prom. Forget it. Limited use.


Hate to belabor this, but you don't need to worry about any of this if you use a hex editor to transfer your calibration. Just copy a block of your calibration to v7 (addresses 0x00E through 0xB5A as described in Appendix A for transferring a v6 cal). By doing this, all you're doing is copying a block of hex numbers from your v6 to v7. After that, the v7 bin will run and operate EXACTLY as your v6. Then once it's running, you can review the changes made in v7 to see if you want to implement them. It's really that simple.
To summarize: In your case, transfer the cal and use your working ADX to start. Once it's running, update v7 ADX with the Commands so you'll can report things not in your current ADX.


There appear to be subtle differences in some of the other items, but they may be inconsequential. I believe if you implement the Connect command, all will be OK. If not, then careful review of the Actions in all the other Commands to make sure they are identical and implement any that are not.

 

I started working on this new connect macro, which has 3 commands that need to be created. Stay tuned for an update.
Mike

 

Bingo! This is why a hex editor should be used. No muss, no fuss. Done! Thanks for the testimony, for venturing out and for showing the world that hex doesn't bite .

Quote:

As far as the hex code stopping at B5A, it looks like there is more code in version7, down to address 105B, so that must be some new stuff.

What you see after 0xB5A are the default Turbo Calibration items. Things are designed so that anything new is added at the end of the Cal. That's why you can copy a specified block of the Cal and be 100% sure that all existing settings will be as before. There is "00" between end of Cal and beginning of code at 0x3000.

Quote:

Also, why do you start the copy at 0E? why not start at 00, as there are code values at the beginning. My version 6 bin was different than the new 7 bin. Regardless, burned a new chip today, and put it in my C4. I was able to rev it up enough, to see the shift light and SES light, come on in tandem. All good!

The bytes prior to 0x0E are:
00-01: BIN Version #, Release #
02-03: BIN Release Date (MM/YY)
04-05: BIN Version #, Development Sequence #
06-07=Checksum
08=Mask ID (8D, or AA if emulating)
09=# Cylinders (0=8 cyls; '7730 used for 4,6,8 cyls)
0A-0D=Reserved but with default 1,2,3,4 as further BIN identifier

HTH, Elky

 

Ya, using the hex editor was a no-brainer. I think i used it before, when i first started last year with vers6. This stuff doesnt scare me. I'm good with it, but i still ask questions. I see your responses to the post, with guy that started with a tach problem, going from V5 to V7.....you really helped him out alot, but he shoulda just used the hex editor!! TP can be a little tricky to navigate, its powerful for sure!

Thanks for the code byte definitions...i confirmed them in my bin. Just some basic setup stuff. I will drive my C4 to work tomorrow, and maybe datalog on tuesday. Fun stuff, just that I am sad to be parking my rides in a few weeks, for winter storage! But, I am determined to get the ver7 ADX datalogging with my C4!

 

Would be most helpful if you would post exactly the changes you make for inclusion in the documentation and to help others with 'vetttes.

 

Will do!! Just need a little time, to get it all working. Already been working on the commands......