|
The only two positives I can think of are the implementation of AEMnet for using an AEM wideband over canbus, and the fix for crank to run taper not working properly in 1.5.2 R12. My car immediately jumping from cranking IAC Duty to my 850RPM IAC Duty % and sometimes dying after crank is getting pretty old.
I am considering upgrading for those two fixes from my current 1.4.0 firmware, are engine states really that bad? |
My tune is pretty much done. I think the older was simpler. The changes they keep making are bringing ES just about where things were before, but just spread out in different places.
My idle comes in and out when CLT hot when A/C is on because of how picky it is on decel settings. I can just put in the clutch and go into neutral, but why? Used to not have this issue. The changes to EGO seem unnecessary to me, and again, complicate things. As if the learning curve is not steep enough for new people already. I I'm noticing that EGO does not always work, and I suspect it is due to engine states seeing Accel or Decel. I don't care to chase it down. It will be some work to switch back, but not too much. Have to add some "I" to the Boost Control, because they have made it too sensitive. But, I have all my old tunes for those few items. Those are my thoughts. DNM |
The fix to the injection timing was pretty substantial for me, but you could fix it yourself and compile 1.4.
I actually like engine states, not more or less than the 1.4 treatment, but I haven't ever had any problems with it. I do remember there being something that really drove me to 1.5, and I can't for the life of me remember what it was.... SD logging is way better in 1.5, they added the pos/neg EGO authority table in 1.5 (awesome afaiac), idle VE?, did generic sensors get expanded?, egt? LTFT? I think the only thing that would would get me to go back would be the ability to modify the code. |
Originally Posted by Ted75zcar
(Post 1582800)
fix to the injection timing was pretty substantial for me, but you could fix it yourself and compile 1.4.
|
Originally Posted by DNMakinson
(Post 1582802)
Explain. I’m not aware of the problem or the solution @Ted75zcar .
|
Originally Posted by DNMakinson
(Post 1582792)
But are there useful items in 1.5.X that cause you to use the newer FW in spite of Engine States? Or do you tune Miatas with the newer only at the owner's request?
I can't recall anything that was fixed in 1.5 over 1.4, and I don't recall that I'm actually making use of any of the new features. EDIT from the MSExtra Release notes says, no features that have meaning to me: MS3 1.5 firmware Key changes and Gotchas - from 1.4.x and earlier ======================= 1. Engine states These must be configured for idle, overrun, idle VE, idle advance. 2. Dome control. Initial test implementation now replaced by implementation integrated with regular boost control. New table settings will be required. 3. Fan control. New settings for TPS and VSS shutoff. 4. A/C idleup. New settings for TPS, VSS and RPM shutoff. 5. Internally the handling of I/O pins has changed. 6. Nitrous progressive VSS and time based - **fuel adder handling changed** 7. Noise filter internal logic changed. DNM |
Correct me if I'm wrong, but can't you just set the accel thresholds sky high and pretty much have everything ignore them?
At least, that's what I've been doing because of the dumb taper bug. Accel and decel fuel still work, idle works, overrun works. Most starts I won't get a crazy decel or accel threshold well above the max settable value that kicks it off. |
Deezums, pretty much I have done that. Brings me back to “What do they bring to the table?”
Ted. I don’t have VVT. People with VVT should take note, however. 18, thanks. Looks like I have a tiny project. DNM |
I have switched to 1.5.2 RC12 recently:
New EGO PID algorithm requires retuning, works perfectly fine with P=25 I=9 D=3. Closed-loop idle crank-to-run taper wrong behaviour is finally fixed. |
| All times are GMT -4. The time now is 04:39 PM. |
© 2024 MH Sub I, LLC dba Internet Brands