When (not) to update firmware?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • skinnyb
    Trusted Tech

    250+ Posts
    • Jul 2008
    • 291

    #16
    Re: When (not) to update firmware?

    Unless firmware is documented to fix a particular problem, I don't touch it. Even if getting tech support involved (which I rarely do). If tech support asks if firmware is up to date the answer is always Yep!

    Comment

    • Exok
      Senior Tech

      500+ Posts
      • Jun 2011
      • 750

      #17
      Re: When (not) to update firmware?

      In my 20+ years of servicing Savin/Ricoh I've only felt the need to update software when the machine had a software corruption. In my experience, those problems were few and far between. I've had many machines go 10+ years on the original software without a need for an upgrade.

      Comment

      • M0scb
        Technician
        • Oct 2012
        • 32

        #18
        Re: When (not) to update firmware?

        I update firmware on most of my calls. In the last 10 years, I have only ever killed 2 machines, one was due to a faulty controller board. There are some firmware fixes that can prevent a subsequent issue generating another call. I find upgrading everything , not just engine and system seems to help. The only time I leave well alone is when custom firmware has been installed. It is just down to personal opinion.

        Comment

        • KenB
          Geek Extraordinaire

          2,500+ Posts
          • Dec 2007
          • 3944

          #19
          Re: When (not) to update firmware?

          It's bad medicine to "pick and choose" which updates to do, regardless of brand.

          A version of main controller will require a certain version of NIB, printer, etc...

          Not keeping all parts of the machine at the same "level" can be one reason why so many techs shy away from it, thinking they will break something. The truth is, if you don't do it all, you just very well may.

          I remember some years ago on Canon machines our configuration centers were flashing iR3570s and the like with main controller firmware, but little else. When the machines hit the customers' offices, the RUI (web page) would fail to open. After a few of these, it was easy to see the problem.

          The way I see it, engineers (I know, I already hear snickers) get paid big bucks to write this stuff. I would think (or at least hope) there is reason for it.
          “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

          Comment

          • Dumus
            Technician

            50+ Posts
            • Feb 2010
            • 79

            #20
            Re: When (not) to update firmware?

            What would our old proverb says:
            Feed the chickens and do not touch the buttons.
            Or, in translation, if and only if it is not you do make it to work.

            Comment

            • mikadonovan
              Senior Tech

              Site Contributor
              2,500+ Posts
              • May 2008
              • 2931

              #21
              Re: When (not) to update firmware?

              Originally posted by Dumus
              What would our old proverb says:
              Feed the chickens and do not touch the buttons.
              Or, in translation, if and only if it is not you do make it to work.
              I'm guessing with that philosiphy doing pm's is a total waste of time.
              NEVER ASSUME ANYTHING

              Comment

              • Cipher
                It's not easy being green

                1,000+ Posts
                • May 2006
                • 1309

                #22
                Re: When (not) to update firmware?

                It's fairly important to keep your machines up to date as a broad range of issues are being fixed via software these days.

                Some general tips.

                1. Read the readme files they may contain warnings / additional instructions.

                2. Read the readme files they may contain warnings / additional instructions.

                3. Don't update anything that displays a completely different firmware number from the older version.

                4. Always update all the modules.
                Some fixes are dependant on one or more modules being updated to the latest versions.
                I would recommend excluding Java updates though, best to leave those to the solution boys to sort out.

                5. On the older models (DSc) and smaller models (MP 161/171/201) the safest way to update is to do the system/copy first on it's own and to do network support on it's own.
                • Knowledge not shared, is eventually knowledge that becomes lost... like tears in the rain.

                Fully qualified technician for Ricoh - Canon - Sharp - HP - Brother

                Comment

                • Lagonda
                  Service Manager

                  Site Contributor
                  1,000+ Posts
                  • Aug 2008
                  • 1649

                  #23
                  Re: When (not) to update firmware?

                  I'm another one firmly in the "if it aint broke, dont fix it" camp. I've had too many dramas over the years where the update didn't go smoothly and you spent the rest of the day trying to coax the beast back to life. Also if you take the time to read the info sheet that is released with the frimware a lot of the changes are to fix very minor and trivial problems, ie a spelling mistake in Serbo-Croat.
                  At least 50% of IT is a solution looking for a problem.

                  Comment

                  • SargeNZ
                    Trusted Tech

                    250+ Posts
                    • May 2012
                    • 263

                    #24
                    Re: When (not) to update firmware?

                    I just bricked a Ricoh MP201 today after doing a firmware update. My own stupid fault too since it is well documented that there are two different machine versions out there, and different firmware is required to suit. So I spent 2 hours installing a temporary machine, since the BICU boards are on backorder!

                    Comment

                    Working...