DC240/250: Fiery system 1.2 on RoHS devices?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • oxident
    Technician
    Site Contributor
    50+ Posts
    • Apr 2008
    • 74

    #1

    DC240/250: Fiery system 1.2 on RoHS devices?

    Hi!

    I've been trying to get the new Fiery system software 1.2 to work on my Bustled Fiery controller without any success...

    After the update (and after applying a dozen of available patches), the copier regularly shuts down with an error code ("please turn off the machine") or even worse, it prints faulty images within a running printjob.

    EFI told me that they aren't aware of any problems regarding version 1.2 on older revisions of the DC250. Xerox told me a technician has to come around to fix this. The technician replaced a few things, reloaded the system software and the problems reappeared.

    After that, Xerox is telling me that the system software 1.2 won't run on "Non-Non-RoHS" machines.

    But I can't believe that! I mean, what's the difference between a RoHS and a Non-RoHS Fiery? I'm sure that it can't be that difficult to simply replace the "failing" part...

    Has anyone any experiences with that system version?
  • XeroxTechBrazil
    Trusted Tech

    100+ Posts
    • Aug 2008
    • 199

    #2
    Software Level on 250

    What version of the IOT software are you running on the 250? There WERE issues with some of the earlier versions, one in particular was buggy.

    Comment

    • oxident
      Technician
      Site Contributor
      50+ Posts
      • Apr 2008
      • 74

      #3
      I'll take a look at this but the Xerox technician already updated the IOT software (and some other firmware parts like finisher and ADF) a few weeks ago ... without any positive effects besides that I'm now able to switch between single- and double-sided documents within a scan job

      Comment

      • XeroxTechBrazil
        Trusted Tech

        100+ Posts
        • Aug 2008
        • 199

        #4
        No, Not IOT Software

        No, you're right, the Xerox guy tech would have put in the latest or almost latest IOT software.
        You mentioned a fault code, what was it? And what exactly was the error message ?

        Comment

        • TechMate
          Trusted Tech

          250+ Posts
          • Mar 2008
          • 285

          #5
          Originally posted by oxident
          ... After that, Xerox is telling me that the system software 1.2 won't run on "Non-Non-RoHS" machines.

          But I can't believe that! I mean, what's the difference between a RoHS and a Non-RoHS Fiery? I'm sure that it can't be that difficult to simply replace the "failing" part...
          Restriction of Hazardous Substances Directive (RoHS) conformity are not present on earlier versions of bustled rips (i.e. v1.1 and below) and therefore, v1.2 is not a compatible system software for non-RoHS compliant rips (unfortunately)

          Comment

          • oxident
            Technician
            Site Contributor
            50+ Posts
            • Apr 2008
            • 74

            #6
            Originally posted by TechMate
            Restriction of Hazardous Substances Directive (RoHS) conformity are not present on earlier versions of bustled rips (i.e. v1.1 and below) and therefore, v1.2 is not a compatible system software for non-RoHS compliant rips (unfortunately)
            Well, okay, but what's the technical difference between RoHS and non-RoHS systems?

            Do the newer machines contain a different mainboard or video interface?

            Comment

            • copymachine
              Technician
              50+ Posts
              • May 2009
              • 53

              #7
              I shure that help you.
              Fiery Bustled Network Controller v1.2 Software Update.SERVICE BULLETINKey Notes:
              This software update brings EFI System 8e features to the DC240/250 Bustled Network Controller.
              The Fiery DFE s/w version v1.2 is customer and CSE installable.
              It provides SPAR fixes for DC240/250 product coded RoHS (AXA) and non-RoHS (WUP) controllers.
              No DFE h/w upgrades are required to support the s/w
              DC240/250 v1.2 release provides key security features:
              - IPv6
              - 802.1x
              - Authentication
              - IP filtering
              - IPSEC
              Installation of new drivers is required.
              This software is intended for customer installation. CSEs must not perform the upgrade unless there is a specific customer request.
              The upgrade is available without charge to the customer. If the customer requires update training or Analyst installation of the new drivers, these services are billable.

              Comment

              • oxident
                Technician
                Site Contributor
                50+ Posts
                • Apr 2008
                • 74

                #8
                Hi!

                Thanks for the interesting information! According to your post, it seems that V1.2 *is supported*

                I have a Fiery starting with WUP, so it's non-RoHS. But I'm not sure what "Prefix VGW" means in that case. My machine shows a "device configuration" VGY but I'm not sure if that's the "IOT print engine" mentioned in the document.

                Comment

                • oxident
                  Technician
                  Site Contributor
                  50+ Posts
                  • Apr 2008
                  • 74

                  #9
                  Just as a side note, my printer ROMs are as follows:

                  Controller 1.231.16
                  IOT 8.32.0
                  Finisher 17.15.0
                  IIT Rom 11.56.1
                  IIT Option Rom 12.3.2
                  ADF Rom 11.8.0
                  SJFI 3.0.3

                  Unfortunately, Xerox keeps telling me that the firmware isn't (and will never be) compatible with non-RoHS printers

                  Comment

                  • XeroxTechBrazil
                    Trusted Tech

                    100+ Posts
                    • Aug 2008
                    • 199

                    #10
                    Software Up To Date

                    Your software is up to date. I think the RoHs - non-RoHs has more to do with the build level of the IOT (or Fiery), rather than any inherent compatibility between a RoHs non-RoHs mix of equipment.

                    This is not an unusual situation for a popular machine that has had a long build life. At some point you have to forego the desireability of backward compatibility because the machine has changed so much.

                    The older IOT's are effectively "orphaned" because their early build levels are incompatible with newer features and add-ons. I am presently in the market for a 250 familiy box, this post came at a good time. I will have to do a little research to insure I don't buy something that has no future.

                    The confusion lies in the use of RoHs - non-RoHs to designate different build levels of the 250 family IOT, effectively suggesting that it is the presence or lack of "hazardous substances" that is driving the incompatibility.

                    Here's the info on your VGW prefix (attached).
                    Attached Files

                    Comment

                    • oxident
                      Technician
                      Site Contributor
                      50+ Posts
                      • Apr 2008
                      • 74

                      #11
                      Originally posted by XeroxTechBrazil
                      The older IOT's are effectively "orphaned" because their early build levels are incompatible with newer features and add-ons. I am presently in the market for a 250 familiy box, this post came at a good time. I will have to do a little research to insure I don't buy something that has no future.
                      Thanks for clarification. So I see that my VGY just means that I've got a VGW but for 220V ;-)

                      On the other hand, I've told my technician about the bulletin, copymachine posted (and the statement I've got directly from EFI Europe) but he refuses to accept that the 1.2 software is compatible with all DC240/250.

                      That's a pity because I can't use the features of the new 1.2 firmware...

                      From my current point of view I would really "re-think" buying an old revision of the DC250 with bustled Fiery. Maybe things are working better when using an EXP250 or a DocuSP but I haven't tested them.

                      Comment

                      • XeroxTechBrazil
                        Trusted Tech

                        100+ Posts
                        • Aug 2008
                        • 199

                        #12
                        DocuSP Users Please Post

                        It would b e nice if some users of the DocuSP server for the 250 would post their experiences, especially those who had previous experience with a Fiery or Creo, and feel competent to offer a knowledgeable comparison.

                        The DocuSp server seems to be catcfhing on, and it does have a lot of nice features.

                        The licensing objection seems to be less of an issue than it was in the past.

                        Comment

                        • oxident
                          Technician
                          Site Contributor
                          50+ Posts
                          • Apr 2008
                          • 74

                          #13
                          Currently, I've got another "statement", this time directly from EFI Europe, telling me that the 1.2 firmware is definitely compatible with Non-RoHS and RoHS devices as long, as the correct IOT firmware is installed.

                          Let's see how Xerox tries to fix this

                          Comment

                          • darkfocus

                            #14
                            DC250 1.2 software on a non ROHS controller

                            Change the HDD in the controller to a 80Gb IDE. We have done this upgrade several times in South Africa. I also replace the 256 MB RAM with a 1 GB DDR400 unit. Works fine.

                            Comment

                            • oxident
                              Technician
                              Site Contributor
                              50+ Posts
                              • Apr 2008
                              • 74

                              #15
                              Originally posted by darkfocus
                              Change the HDD in the controller to a 80Gb IDE. We have done this upgrade several times in South Africa. I also replace the 256 MB RAM with a 1 GB DDR400 unit. Works fine.
                              I've already expanded the 256MB RAM with another 512MB module, giving me 768MB but I'm quite unsure on how to upgrade the HDD.

                              Did you clone the harddrive's contents over to the new hdd? If yes, which partitions did you enlarge?

                              Comment

                              Working...