printing pausing during large run?

[Shane Drew]

I had this happen today. Turned the machine off at the main switch, turned it back on so the network card could reset, and all was sweet.

Hope that helps

[Phil Halling]

Cheers Shane, seems to have worked.

Looks like we’re half a planet away from each other, but the problems are the same. A case of the grass isn’t always greener on the other side I suppose.

Phil

[Shane Drew]

pleased I could help phill.

are you running colorrip 2.2 by chance? My machine has only started doing this since I upgraded last week.

[Phil Halling]

No Shane, Troop – Wasatch V5.1.4

[Robert Lambie]

quote Phil Halling:

Any help appreciated as I am on tile 3 of 16, and it’s looking like a very long day 😥

its not anything other than you just said, these machines Waite till you have a big job then pounce with the smallest yet most annoying problems. :lol1: :lol1:

[David Rowland]

Phil, must give u a ring….

We get this on our older P4 rip PC, I am changing this over to a powerful Xeon Server which just eats up processing time. You might notice your PC’s harddrive is going overdrive, this will be your biggest clue. That means lack of memory available and its swapping to your harddrive.

In Shiraz, there is an option to Rip then Print, this works well as it RIPs the file before printing it, the PC struggles to keep up and causes 1-2 second breaks on very heavy bitmap graphics. The 1-2 second pauses on a JV3 forces it to pump the heads for a second and this chews up a tonne of ink.

Let me know if that helps Phil although I dont use your setup I suspect it is similar.

[Shane Drew]

Dave, my hard drive works no harder when my machine does this. And my file yesterday was a 1200 x 900 vector print. Hardly a big job. I’ve done bigger without a drama. I’ve got the roland guy coming out next week for a maintenance check, I’ll pick his brains.

[David Rowland]

i guess not shane… but that vector job is turning into 1200×900 multiband raster image which does create a large image, although it shouldnt be taxing enough to slow a computer.

The JV3 is connected via a Firewire interface for speed reasons, it can be connected to a parallel port but a lot reports on Mimaki groups suggest its too slow.

If you press Ctrl Alt Del and get Task Manager up, move over to preformance and you see CPU Usage, if this is high (100%) then the system is struggling to prepare the image to print, the PF Usage is half-way then it is swapping quite a bit to the harddrive, this usual is lack of memory in the PC or you are using the PC for other things and not using it as a dedicated print station.
Physical Memory will report something like 1048044 (1GB) or higher and you should have quite a large figure in the available bit. 1GB should be fine but if you getting performance hickups then memory will be the easy answer.

[Shane Drew]

quote Dave Rowland:

i guess not shane… but that vector job is turning into 1200×900 multiband raster image which does create a large image, although it shouldnt be taxing enough to slow a computer.

The JV3 is connected via a Firewire interface for speed reasons, it can be connected to a parallel port but a lot reports on Mimaki groups suggest its too slow.

If you press Ctrl Alt Del and get Task Manager up, move over to preformance and you see CPU Usage, if this is high (100%) then the system is struggling to prepare the image to print, the PF Usage is half-way then it is swapping quite a bit to the harddrive, this usual is lack of memory in the PC or you are using the PC for other things and not using it as a dedicated print station.
Physical Memory will report something like 1048044 (1GB) or higher and you should have quite a large figure in the available bit. 1GB should be fine but if you getting performance hickups then memory will be the easy answer.

interesting Dave. My roland running the parrallel route is very slow. Too slow to work efficiently. I’m not running firewire, just normal 100mps LAN cable.

[Peter Shaw]

I don’t think that this is a processor problem as Wasatch/Colorip/Troop print from a spooler. All the heavy processing has been completed by the RIP and all the spooler is doing is feeding out the data.

Peter

[Chris Wool]

quote :

In Shiraz, there is an option to Rip then Print, this works well as it RIPs the file before printing it,

also in colour rip which is the way i handel it then as the riped file is spooled printing i can rip the next file with no ill effects to the printer.

chris

[Shane Drew]

quote Chris Wool:

quote :

In Shiraz, there is an option to Rip then Print, this works well as it RIPs the file before printing it,

also in colour rip which is the way i handel it then as the riped file is spooled printing i can rip the next file with no ill effects to the printer.

chris

I queue them too Chris, makes life much easier

[Chris Wool]

shane have you got to grips with the hot folder option or like me left it alone

chris

[David Rowland]

the JV3 and Shiraz doesn’t actualy spool, it ssends bands the first 3-4 lines of data then sends it when ready, this way it doesn’t spend ages RIPing, it goes to work pretty quick, works like a Epson Stylus printer but with an advanced RIP. Mimaki put a firewire on as its faster then lan 100speed, a bit daft in my view.

[Shane Drew]

quote Chris Wool:

shane have you got to grips with the hot folder option or like me left it alone

chris

left it alone mate…. 😕

[Pauly]

I would stop the machine, clean the head and check the temprature of the plattern and the heads. We sometimes have this EXACT problem on our Seiko, its generally because the printer head is getting too dry and losing jets from the heater, i dont know why it does this, but if we clean it and turn off the heater. It will come good straight away. But in my experience, heat is the biggest killer here, it may be a temp sender telling the machine its too hot as a precaution and stalling at either end for a cool down???