iGen3

Start Up Maintainence?
How Often Should I Change All The Parts Inside The Print Press?
(If Someone Could Specify Seperately On Each Part How Many Weeks Even Days)
How often We Should Calibrate?
If We Use TRC What Should We Do After (Restart?)
The Print Quality Unfortuantly Recently Has Been Absaloutley Poor It Would Be Nice If Someone Could Give Us A Guideline That We Could Follow And We Can Address For Future Refrence.
(Please Do Not Say Buy An iGen4 )

 

Buy an iGen150

--
Mark

 

Go with the HFSI's and failure of each part. Some go to life and over, others fail earlier. There is no hard and fast rule as it all depends on enviroment, stock, job profiles etc
Calibrate once a day min (some don't even calibrate at all). If colour critical or a colour issue calibrate then
No need to restart after applying TRC
Print quality can be poor due to numerous factors already mentioned (env, stock, running a colour critical job straight after a low area coverage job without performing dev recovery is a no no - keep an eye on the toner ages). Are you doing your maintenance when needed and not over doing it -ie if it ain't broke don't fix it - I will assume the engineers are looking after the machine as I do know them

--
Mark

 

lol

 

Hi Mark

Recently We've Had Two New Operators To The Additionb Of The Team That Are Still Learning
Maintainence Wise When I Come Into My Shift I Do A MOB Calib, Dc0951 Then Te Auto Colour Calibration And If It's Still Bad A 614 Then Do The MOB Dc0951 Then The Auto Colour Which Seems To Be Effective.
What Do You Think ?
And Even Before That I Brush The Corotrons Down

 

Also What Do You Reccomend Running The Dev Ages Down To And Should I Make It A Daily Start of My Shift?
When Should I Do The Dev Recovery Do You Mean In Job Exerciser Or Just Dev Recovery In NVM By Running Them Down?
If In Job Exerciser How Many Sheets Should I Run Otherwise... I Know What You Mean

Also We Seem To Get Through A Lot Of 8_wires is that normal :/

 

My advise is to create a job file with the following

20% FPHT CMYK (4 sheets)
50% FPHT CMYK (4 sheets)
70% FPHT CMYK (4 sheets)

Run these at start of shift and see if the quality is OK. If it is - leave it. Bearing in mind this is an iGen3 it will not be 100% so some discretion is needed, also consider what the jobs are that you will be running. ie Getting the quality 100% for a low area black text job is not worth the effort. As I said don't fix what isn't broken. You can over do the maintenance to the effect that you can cause more probllems than you started with.
DC614 should only be run if all else is good and TBH not that often. This routine will correct any defects be it fuser, xport etc causing a PQ issue. If the fuser had bad gloss differential when run, the next time you change the roll you will get a defect show up as it is still running the corrupt profile that you created on the worn roll. If dc614 is failing Reset to last service profile as we will have run the routine when we had the engine in good nick

Set Toner ages to 50 and run 5 sheets in dc106 then reset back to what you had them set to (usually 80). The engine will cycle without printing sheets until the target of 50 is achieved. Your cleaner filters will fill up faster btw. Again not worth doing if the next job is a low area text based job

If wire MODs are failing early this usually means that the toner % is low in the tanks. The packer sensors may need to be calibrated again by us

--
Mark

 

I rarely change anything. Unless close or past due, and/or I am having issues. sometimes under, sometimes over. I dont calibrate anything unless I am having issues either. Or I am starting a high coverage job..

 

Agreed with Mark & peels "less is more". It's a lot of work to prevent all problems from happening. It's easier (and in many cases more efficient) to wait until they occur, then deal with them. That's not to say you shouldn't do preventative maintenance, but when you're new to the igen it's a lot to take in.

Perhaps make a log book where you can record the MACHINE PROBLEMS and ACTIONS TAKEN and WHAT YOU'VE LEARNED or something like that.
It will help you learn faster and keep things in perspective a bit better.

 

+1 on making a log book... wish I had done a better job of it...

however...as I was learning this thing, I would post issues here. i can search sometimes, and find my OWN problems when they resurface. Usually takes seeing an issue twice or three times , maybe, then it's burned into memory.