FS-4020dn rebadged - F code errors (f579,f4f5,f259,f257,f264)

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • pez
    Technician
    • Jul 2015
    • 19
    #1

    FS-4020dn rebadged - F code errors (f579,f4f5,f259,f257,f264)

    Hello. Long time listener (first time caller), wondering if anyone has seen anything like the below:

    We've got 15 Olivetti rebadged FS-4020Dn printers that have been running on a network happily for a few years. As of April of this year, 5 of these printers have started exhibiting F code errors, displaying "Error. Power off." and an F code error.

    I've got one of these machines in front of me, and its on a firmware showing 2j0_3000.009.006 2012.07.31

    The Event Log from this particular machine shows the following:

    8 - 01.F259
    7 - 01.F259
    6 - 01.F4F5
    5 - 01.F579
    4 - 01.F579
    3 - 01.F579
    2 - 01.F579
    1 - 01.F579

    The first reported incidence of F579 came in April, around the time that we started receiving reports of F code errors on the other 4 printers (33% of the printer fleet).

    I am able to power this printer up, and it displays "Ready" on the screen. When I plug in an ethernet cable, within a couple of seconds the display changes to "Error. Power off. F259".

    I have another one of these printers next to me that showed a similar pattern of F code errors, which ended up with an F257 upon power up (whether it was on a network or not) and is now essentially dead.

    This second printer showed the following F code errors when I was last able to print an Event Log (before it started showing F257 errors). Again, these started back in April:

    8 - 01.F259
    7 - 01.F259
    6 - 01.F259
    5 - 01.F264
    4 - 01.F259
    3 - 01.F259
    2 - 01.F264
    1 - 01.F259

    I am told that they are all on the most current firmware, but we are enable to find reference to these F codes in the service manuals.

    We have no idea what happened back in April that could have caused these issues, but we're wondering if its something network based, perhaps some corrupt job that the machines have had an issue with/corrupting something.

    Has anyone seen anything like this before?

    Thanks in advance for any replies.
    Tags: None
    • blackcat4866
      Master Of The Obvious

      Site Contributor
      10,000+ Posts
      • Jul 2007
      • 22985
      #2
      Re: FS-4020dn rebadged - F code errors (f579,f4f5,f259,f257,f264)

      F579: An error is detected at the Job execution section.
      F4F5: An error is detected at the Job control section.
      F259: An error is detected at the Network management section.
      F257: An error is detected at the Network management section.
      F264: An error is detected at the System management section.

      Some sort of non-print data is hitting the IP addresses of your printers. I've seen software like PrintFleet, that checks each IP address on the network can cause print data errors. Especially since your printer boots up fine while off the network, then errors once on the network. The one check I didn't see on your list is, did you print directly from your laptop via a crossover cable, removing the network from the equation?

      It's really in the hands of the local IT now. Show them that you can print from your laptop while off the network. It will take some network sleuthing to figure out where the data is actually coming from and stop it. =^..^=
      If you'd like a serious answer to your request:
      1) demonstrate that you've read the manual
      2) demonstrate that you made some attempt to fix it.
      3) if you're going to ask about jams include the jam code.
      4) if you're going to ask about an error code include the error code.
      5) You are the person onsite. Only you can make observations.

      blackcat: Master Of The Obvious =^..^=

        Comment

        • pez
          Technician
          • Jul 2015
          • 19
          #3
          Re: FS-4020dn rebadged - F code errors (f579,f4f5,f259,f257,f264)

          Thanks for that. The codes are interesting.

          Unfortunately, we're getting the same behaviour when we use a cross over cable (to the printer that sits at "ready" following power up). I've wiresharked a laptop network connection to see if there's anything weird going on, but not seeing any traffic coming back from the printer, just the laptop trying to start communications with the printer.

          I've tried resetting it using a usb stick and printing a file called reset.capt that contains the following (is the prescribe OK here?):

          !R! EGRE;exit

          I am able to print an event log using the following code:

          !R! Elog;exit

          This machine is able to print via USB.

            Comment

            • blackcat4866
              Master Of The Obvious

              Site Contributor
              10,000+ Posts
              • Jul 2007
              • 22985
              #4
              Re: FS-4020dn rebadged - F code errors (f579,f4f5,f259,f257,f264)

              If you've already done an engine reset and attempted printing from laptop, you've narrowed it down considerably. The network interface is built into the main controller, so all network communication is happening on one board.

              I would attempt to load firmware. It's hard to say whether you'll have any success. If there is a Compact Flash port, you'll have a higher chance of success using the compact flash method. The CF card must be formatted on one of your functional FS-4020's. The firmware files are placed on the root of the drive. Caution: Be absolutely certain you have the right firmware. The tabletop printers will take whatever firmware you try to give it. If it's the wrong firmware, the printer will take that firmware and become a brick. Ask me why I know this.

              If the firmware doesn't help, replace the main controller, then immediately load the current firmware on first startup.

              The "Engineering Codes" are a pet peeve of mine. Apparently Kyocera thinks us techs are too stupid to use the information from these engineering codes to fix anything. For 5 years we couldn't get any information about them. I began to collect word-of-mouth data from other techs in the field, and put together an Excel database of this field experience. If you Google search "CFxxx Codes" you'll find the database, now in three languages. Since then Kyocera has released a bulletin with some information (since the cat was already out of the bag). I can summarize the entire bulletin in one paragraph:

              1) Reformat HDD U024 FULL; 2) Initialize backup memory U021; 3) Repl main PWB; 4) Repl HDD; 5) Retrieve USBLOG and contact SAD.

              =^..^=
              If you'd like a serious answer to your request:
              1) demonstrate that you've read the manual
              2) demonstrate that you made some attempt to fix it.
              3) if you're going to ask about jams include the jam code.
              4) if you're going to ask about an error code include the error code.
              5) You are the person onsite. Only you can make observations.

              blackcat: Master Of The Obvious =^..^=

                Comment

                • pez
                  Technician
                  • Jul 2015
                  • 19
                  #5
                  Re: FS-4020dn rebadged - F code errors (f579,f4f5,f259,f257,f264)

                  The printer that was sitting at Ready until we plugged it into a network (when it then showed f259), this morning goes straight to f257 upon boot up (regardless of whether its networked or not). Same behaviour as the other dead machine that we have (that also shows f257 on boot up). That is bizarre - yesterday it would at least sit at Ready when off a network and allow USB printing (and that was after we had flashed it with the latest available firmware several times).

                  Just had word that another printer has started displaying an f565 error this morning.

                  Papercut is carrying out print management activities on the network, and PrintMIB monitors meters for a remote billing/engineering solution. There are two Server 2008 servers running virtually supporting the network, one of which is handling the print server role.

                  We had a Kyocera based Olivetti 5500mfplus mfd at another location that came up with an F248 code error when they started using Windows 10 earlier this year - but we couldnt replicate it on demand so can't say if its anything more than coincidence.

                    Comment

                    Previous template Next
                    Working...