Originally Posted by 1BADVAN
OK, thanks. Just for reference, which template did you build your cal with?
OK, thanks. Just for reference, which template did you build your cal with?
"T-SBEC_25_ATX_A577_Stock.v02"
I still didn't get a chance to try the fix I posted above. Anyone else? I'm going to try and do it tonight. 2 boys in baseball makes for a very busy week...
This Fix? I could but i don't know where i am looking for that? Also today the van almost did not start due to a weak battery. This was the first time that happened but probably the first time the van sat for 18 hrs without being started.
When i got to work i checked under the hood, and i heard and "electrical whine or hum" from the area where the SBEC is. I disconnected the power and reconnected it and it went away.
Yes, that fix. It's in the .asm file. You'll have to edit it with a text editor (notepad should work OK). Just do a find for "LE6DA" and remove the semicolon [;] in front of the line.
I think that 'hum' is related to the AIS motor. Though, I didn't have the hum on the van I tested last weekend.
i assume i do this and then re-compile?
Yep...
Ok i tried removing that semicolon and it was the same, the AIS motor clicked and there was an electrical Hum. IDK if it helps but the Phosphate 2.0 by Quantum (who says its based on your code) Does not cause the AIS clicking. IDK if there is a way to compare them easily or not. I will try to compile a different template and see what happens.
OK, thanks. I'll try it myself, too - still didn't get to it...
OK, fixed the AIS thing. I'm not really sure why this fixed it, but I had to move the AIS Bit pattern back to the stock location - in-line with the code. The T3 did NOT have this issue with relocating the AIS bit pattern, eventhough it has the exact same AIS control routine. Strange. Anyway, I'll post an update later. I want to take a quick look at the 2-step code tomorrow.
Sweet I will be waiting! Thanks for all the help!
06/06/11 - r2.8 now posted:
Fixed the AIS motor issue (running with the key-off).
Thanks! Works Great!
A quick question on boost control. I set the items under "boost Target lookup" to about 13, but all i could get was about 9 at first, then i put a restrictor in the line and it went to about 11. With the wastegate unhooked from any vac source it only goes to 16. My question is where to start? Do need to tighten up the wastegate can first, or try a smaller restrictor?
Also just to double check, i hook the vac lines up just like stock for my van right?
Should be setup just like the stock 2.5 T1 boost control. If the boost only goes to 16 with no vac lines hooked up, you probably need to tighten up the WGA. I had to try a couple of different restrictors to get mine to work at 18-20psi. I think I ended up with a 0.04".
v3 is released. Same as v2.8 except updated for compatibility with MP Tuner 2...
Question. When it is cool outside like 50 degreesthe A/F is perfect like 11.8 bit when warmer like 70 it goes to 10.9 how can i fix that so it is always the same.?
The easiest way is to add the charge temp sensor and put it in the tube between the I/C and the throttle body.
08/30/11 - r3.1 now posted:
For use only with MP Tuner 2
- Updated the naming of the Decel Fuel Shutoff valules and added to a new separate group.
- Updated the Staging Limiter code. Was not working due to the decel fuel shutoff code.
- Added code to fix the CCD Fuel Monitor value.
- Split MPVACD_AllowMapToTestGoodThisNearBaro into 2 value to correct MAP scaling.
- Updated Staging Limiter code to work when no switch is selected (on speed only).
- Setup AESLOP to scale inversley with MAP (only in MPT 2.0.0.9)
When I open the 2.5 High Torque cal I get errors right away. I'm just now starting to modify the cal from SDAC and noticed that there was a update to the Turbonator codebase for a few things so before I get to far into it I wanted to start with the newer code. Here's the errors I am getting.
Warning->Unknown table definition code at location 6465, code = Trace
Warning->Unknown table definition code at location 8038, code = Trace
any ideas? I tried the MP one to and get two errors also but at a different location.
Those errors don't mean anything. There were some 'extra' bytes that Chrysler had left behind in the cal area. I put them in to be complete (Iwasn't sure what they were for - and still don't know). But, MP Tuner doesn't like them. If you save the template, MP Tuner will take them out so the errors will be gone the next time you open it.
Your cal is based on the latest T-SBEC code, though maybe not for MPT2. I can't remember. The only difference between 2.x and 3.0 is the template being setup for MPT2.
Posting Permissions
Reply With Quote