dc 250 can not print configration report with built-in fiery controller

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • shawn_xia
    Junior Member
    • Jul 2011
    • 8

    #1

    dc 250 can not print configration report with built-in fiery controller

    copy function of this dc250 is good.but I can not print out configration report when I connect the built-in controller .the configration report always stuck in the memory. I reload the fiery software but the same.

    Is it possible the video card has problem?anything else?
  • bojans
    Service Manager

    Site Contributor
    1,000+ Posts
    • Feb 2008
    • 1313

    #2
    Re: dc 250 can not print configration report with built-in fiery controller

    Eureka tip:

    Ensure that the Scan crossover cable is free of damage and is properly connected between the "Scan" port on the bustled controller and the Ethernet port on the side of the copier.

    Comment

    • shawn Xia
      Xerox & Kinolta
      • Oct 2009
      • 25

      #3
      Re: dc 250 can not print configration report with built-in fiery controller

      thanks. I checked they are fine. I think if they are not connected properly,the icon of networking scan on the control panel will never appear.

      anything else?
      MSN:matchdg@hotmail.com
      Xerox & Konica Minolta Tech

      Comment

      • msoundpr
        Technician
        • Mar 2011
        • 15

        #4
        Re: dc 250 can not print configration report with built-in fiery controller

        Hi, check this,

        initializing the Sys-USER and then the Sys-SYSTEM via UI Diagnostics.
        Please note that NVM location 790-402 was always at a value of 5.

        At the end you will need to reload ESS sw. Are you connected to the network and can send job to be printed with your PC.



        Originally posted by shawn Xia
        thanks. I checked they are fine. I think if they are not connected properly,the icon of networking scan on the control panel will never appear.

        anything else?

        Comment

        Working...