How does everyone deal with firmware releases in their cars?

I ask because I'm a software engineer and know there are basically two methods for people:

1. Don't - It works stop touching it.
2. Bleeding edge - latest firmware always.

I've only just started my MegaSquirt journey on a @Reverant MS3 Basic with v1.4.0 firmware.
Watching some videos online I can see that v1.4.1 has idle specific tables and such.
Obviously the latest has the most bells and whistles but more code means more to break.
So wondering if people jump on the new ones or just tune and forget.

 

I would advise against, unless there is an official firmware release by Reverant which I am unaware of atm.
1.4.0 is good enough.

 

^ this is always a confusing thing with units from @Reverant. As I recall his MS2 stuff had to go back to him but the MS3 units use the “off the shelf” firmware. Maybe he can pop in and clarify.

 

His MS3 can use official firmware just fine. But unless you REALLY REALLY have a REAL problem to fix, I would not with 1.5 series of firmware due to the honestly braindead Engine States feature. AFAIK the only real improvement you could get would be in terms of EBC code.

 

Basic series ECUs always use stock firmware.

If the ECU works fine for you and you don't need additional (ie new) features, stick with the firmware provided. It's not a phone or a PC, you don't need to patch security vulnerabilities.

 

Thanks you all.
@Reverant The only reason I was asking was the tutorials at the top of this forum all use the v1.4.1 firmware.
Making the tutorials noticeably different for those on different firmwares (like me on v1.4.0).

Like having dedicated idle tables (literally as far as i have got).

 

I self-identify as type 2: bleeding edge (currently on 1.5.2 b4)

I have the Rev MS3 Basic.
Moved to 1.5.1 ages ago, and I am very happy with engine states; it makes a lot of sense to me now.

Engine states doesn't take much to understand; within 2 days I had idle engagement working perfectly.
It takes some of the complexity out of idle engagement, a number of fiddly parameters disappeared in the Closed-Loop idle settings. On 1.4 I had a intermittent low speed (2-5kph) throttle lift RPM drops that I couldn't completely fix - I think related to disable RPMdot, those went away with 1.5.1.
And it got even simpler when the fast accel/decel settings were removed.

The engine states tune tips explain what to look for in the logs to adjust the slow accel/decel values and once set, idle engagement becomes absolutely solid. Of course, YMMV.

Tony

 

As someone that has moved firmware did the frimware update have entries in the new cells already?
I only wish to go up to 1.4.1 so mine matches the video tutorials but it has some unique things which may not be populated so did the firmware propogate any infromation into these sorts of cells for you?

 

Yes, values are placed in the new fields which are typically sane values but they aren't necessarily good values for your application. Nothing will blow up but you may have minor issues.

For example: the engine state slow deceleration value was too low and caused idle engagement to oscillate in and out. It didn't break anything and only needed one log to determine what the value needed to be.

 

After reading about the difficulties of engine states with idle and the fact I'm a daily I will bump to 1.4.1 so i can do as the tutorials ask but no further.

 

Rev, does this apply to the Mini ecus too? I've got an NB MS3Mini running 1.4.0 which i'd like to bump to 1.4.1 for the revised closed-loop boost features.

 

Yes.

 

Anyone out there running the new 1.5.2 beta 4 have experience with the new change to "Type B" PID? How about this new "Add negative direction EGO authority table"?

Three Types of PID Equations

Do folks really get the PID settings to be completely stable and quick to resolve to the solution? I find I always get some ripple and overshoot otherwise it takes a lot longer to resolve.