So the 4 low trans parameters do not work with a standard 12212156 OS, or only fail when you go to a COS?
Printable View
So the 4 low trans parameters do not work with a standard 12212156 OS, or only fail when you go to a COS?
Well theres no 4 low shift tables in any of the tunes that I have but it still works with the one Here are the tunes I have If anyone wants to look Ones a 2wd ones a 4wd Attachment 11063
Attachment 11064
Whipped, sorry but you are not being very clear. Are the 4 lo tables active when using the 12212156 OS?
The custom OS parameters appear to take over a section of the trans diagnostic part of the code (from what I can see) This may or may not be your issue.
I've only been partially helping with this problem for a while, but since I don't have a 4wd truck to test things on I can't do too much. but basically this is what's happening:
the problem exists on on 411PCM swapped 96-98 L31 based 4wd trucks...since these are L31 trucks, the base tune has to be from a Xvan, which of course never used 4wd, so in order to get the 4wd functionality, a hybrid tune was created by someone which used an S10 tune of some sort (others will have more info on that than I will). So the base tune that whipped posted up is what that is, it has full 4wd high and low functionallity, however when that tune is converted to a COS (02020003), it's 4low shifting functionality goes all haywire. so 12212156 OS 4low works, simple swap to 02020003 and its haywire.
several of us think that perhaps its a table that we don't have access to in the tune which is causing this problem, which is why we think a CAX might be needed. especially since the problem is centralized around the swapped PCM trucks. but no one is completely sure why the problem is happening.
since we know alot of people have the problem with 02020003, I wonder if anyone has tried it with any other COSs? perhaps its something with COS3 only? if you have a chance whipped, try COS5 or something, see if the issue is still there...
Ok thanks for your input im not the best at explaining things. Ill try a cos 5 and see what happens
When you upgrade from 12212156 to COS3 or COS5 are you doing this:
- full flash of COS3/5,
- cal only flash from 12212156,
- read back from PCM and save to file,
- edit file and fix any out-of-range cells (including A0012, A0013),
- look thru all tables for sane values and fix the insane ones,
- cal only flash.
Those are important, make sure that all the Axxxx tables and B3647 contain sane values.
OOR: make sure you get rid of the blue dogear corners.
That's what I did but I screwd up and used a file that the 4 didn't work on I gotta try agin
Thanks for the clear explanation Aloicious. Sounds like the custom parameters take over the part of the code necessary for the 4lo trigger.Quote:
Originally Posted by Aloicious
I dont think anything short of a rewrite of the COS will fix this.
Dont think a cax will fix it? Howard had talked to the guys at efilive about it and they dont wanna do anything to help they arent interested in doing anymore with the older pcm stuff
I wouldn't say that they are not interested in helping you, just that most of the time some of these one off requests can take days upon days (or quite possibly months) to come up with a fix, and it only benefits a handful of people. EFI Live is a business, and they are going to go where the money takes them, and that is keeping current on the newer stuff out there. Let's face it, if you ran a business and you had the choice to cater to 50-100 people who probably are not going to spend any more money with you other than your initial investment, or come up with a new product that will bring fresh/new customers to you and keep you in business, you would probably try to open up your customer base (at least I would). Most people do not realize the man hours coming up with a simple fix can take and it just isn't worth it in a business sense!!!Quote:
Originally Posted by Whipped383
Just my $.02, and please don't ask for change :)
Mike