Page 3 of 3 FirstFirst 1 2 3
Results 21 to 28 of 28

Thread: KM C1085 / Fiery Rip Communications

  1. #21
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    Still all good with Fiery. No problems at all. Its is running the best it has ever run. 1,000 page file with sequential numbers in it just runs perfectly. These were set up as unique collate as well. Looks like the problem is finally fixed for us.

  2. #22
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    Well we've had a good run with Fiery up until today. We had a Fiery Crash imposing a 48 page program. I did notice on the Restart the startup was very very slow. I have deleted all the Service Log entries and have the print files in the print queue down to a minimum so I will have to wait probably until next year to see the problem comes back like it did before. The current program job has just about finished and will nearly be the last job this year.

  3. #23
    Join Date
    May 2015
    Location
    Atlanta, GA
    Posts
    123

    Default

    Hi Baldbug, did you submit the crash report that occured while Imposing? Did you add an email address or comment?

    Thanks and happy holidays,
    Mark

  4. #24
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    There is no Crash Report, and there never has been.

    The Crash is recorded into a USB stick for KM C1085 Crashes but not for Fiery Crashes.

    The Fiery just freezes or fails to respond.

    We still have Communication Errors between the KM C1085 and Fiery Server. This can take up to 10 minutes for communications to be re-established between the 2 devices.

    The Fiery restart is very slow with outlines of the boxes first appearing and then the jobs that are in Fiery.

    I have not started the Digital Press today as we are waiting for the Techie to come in and do some adjustments that need to be done in the KM C1085 only.

  5. #25
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    FIERY CRASH
    11,112 clics into a 30K clic run and Fiery decides to CRASH.

    No Error Messages on Fiery or C1085 just a loss of communication between the 2 devices.

    C1085 just sits and is warming up and then sits and it warms up again, but the Fiery is responsive to reboot only.

    Heaps disk space available. About just over 100 entries in Job Log.

    Up and running again after 2 restart attempts to try and get the Fiery to communicate with the C1085 again.

  6. #26
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    FIERY CRASH AGAIN:
    Started work early this morning to get the job done.
    C1085 was left in Standby Mode
    Fiery lost communication with C1085 when it was in Standby Mode
    Restart both devices
    Fiery restart very slow with spinning blue cursor
    Up and running after 10 min restart.

  7. #27
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    FIERY CRASH
    Another 12,192 clics done and then suddenly a Fiery miscommunication which gives no error on either device, so we restart both devices.
    10 minutes to get back to printing again.

  8. #28
    Join Date
    May 2009
    Location
    Minneapolis, MN
    Posts
    729

    Default

    Have just read this thread all the way back to August of last year.

    First off, EFI is not hearing of version 2.1 IC-308's having this issue in field, so I suspect this ongoing issue is only with system there.
    Intermittent issues like this one can sometimes be very difficult to diagnose

    I can offer some suggestions for you and your KM dealer tech to try, below.

    1.) This looks to be a Fiery to engine interface issue, so you need to make sure all components involved in that have been addressed in troubleshooting:
    - has Fiery to engine cabling been replaced?
    - has engine interface card in Fiery been replaced?
    - has VI card in engine been replaced?
    - has interface/processing card inside engine been replaced?
    - has engine firmware been updated to current version?

    2.) Is System software version on Fiery at v2.1, and has Fiery System Updates been run so that all Fiery patches listed there been installed?
    Current patches and correct install order:
    FIT101087873
    FIT101206715
    FIT101304140 (Composite)
    FIT101370308
    SP1_FIT101585435
    FIT101654523
    SP2_FIT101834647

    3.) Have all Microsoft Windows 7 critical and important updates been installed?

    4.) Has the Command WorkStation (CWS) that you are using the latest? If you prefer CWS5, you would want CWS5.8.0.116 (or newer). If you prefer CWS6, then you would want CWS6.3.0.152 SP1

    5.) That Fiery shipped with 4GB RAM. Given that you have observed some slowness, I would recommend bringing total installed RAM up to 8GB, or 16GB.
    Obtain the memory upgrade from:
    https://www.efi.com/products/fiery-s...rted-printers/

    Make sure "Fiery Server Name" is IC-308 when looking at memory selection (not IC-310)

    6.) Make sure no 3rd party, non-Fiery, applications are running on the Fiery itself. Sometimes those apps can interfere with optimum performance on Fiery server.

Page 3 of 3 FirstFirst 1 2 3

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts