Printer timing out...

[Bart]

-- I'm having a consistent timeout error during printing larger files.

I'm running Sign Lab 8.0 Print and Cut, Sign Lab's VPM, Mimaki JV3 connected by 10' firewire, thur XP Pro SP3.

I receive a timeout error (code 23) consistently at 80% maximum (sometimes less)... of a 4'run!
Seems at 35" to 36" of a 48" print. The printer stops mid pass, travels
home, pumps up then codes out.
Yet using the same file, changing scale only, runs clean at 24"and 36".
I've changed my "port settings" to never sleep in Windows, with no change in result.
Dumped and completely reloaded all Cad Link software, including hardware profiles for Mimaki and Graphtec cutter. again no change...
Sent 2"x 4'simple boxed outline as a test thru, printed complete.
Seems to be file size issue, but no idea on what will remedy my dilemma.
Anyone out there ever dance this dance??

[JasonFF]

I've dealt with an incredibly wide range of problems on my Xerox 8160 + WFC Rip, your symptoms included.

There's a couple things I'd check out in an effort to fix it. Firstly, I've had this type of error when my hard drive filled up. Hey, don't mock me, the thing is a massive 15 GB. If your HD has under 1 GB free, it might be causing the problem and space should be freed up regardless.

If that's not the problem, then I would like to know if you have printed anything else 4 feet long at full printer width. depending on the file, my printer will crash out because the in-printer memory gets over filled with large documents, even though your computer should only be sending portions of the print to the printer at one time, sometimes Windows 2000 / XP don't execute very well. If your spool settings have changed since you last printed that large, that could be why. If the driver is set to spool, try changing it to not spool, and visaversa.

I hope one if these things helps you out.

[gig0]

I think Jasons comment about the spool settings might be a factor.

I've seen Epson 7800's choke the same exact way with large files when a front end EFI RIP has the 'Print while ripping' (I can't think of the exact phrase, atm) option turned on. The solution was to let the whole file dump into the queue before it starts printing. It sounds a lot like your problem.

[Bart]

First of all thanks for taking the time for me.

As far as the hard drive, using 32GB on a 931GB system.
Printing 4' @printer width as well as cutting the file in half literally. (original was running print 2up) Resulted in the same error same place... Rewriting the file from scratch even, results in no change .

I've got the printer settings in windows "print directly to printer". That gets it sent to the VPM without spooling. After the rip... Hittin print will get it fed from the VPM to the printer in 10% bites, per the bar graph. Often the Rip still acts as if it's working even after the printer errors.

[Bart]

Installing another new Fire Wire board seems to have me going again.
It took a tip given by Mike at Grimco... Installing a 1394 pci card with a "TI" chip set allowed my JV3 to process the entire file. Thanks for all your efforts.

Bart~

[JasonFF]

Installing another new Fire Wire board seems to have me going again.
It took a tip given by Mike at Grimco... Installing a 1394 pci card with a "TI" chip set allowed my JV3 to process the entire file. Thanks for all your efforts.

Bart~

That's great to know Bart. I'll have to check out what the TI chip adds. I wonder if that same file would work if connected by ethernet or by USB. Thanks for posting back with the solution. Long live PrintPlanet.