Accuset 800 job time outs

[adam470]

Hi this is a continuation on a previous thread "help with accuset 800"
The rip I’m using is apogee s2v2 up6 on w2k
I am still getting job time outs with this message in the pilot imaging window

05/06/2010 10:31:15 AM - No on-line processor present
05/06/2010 10:31:15 AM - Connected to engine

05/06/2010 10:36:07 AM - Job ’’ (81) started
05/06/2010 10:36:07 AM - Job ’’ (81) ended

05/06/2010 11:32:34 AM - Job ’HTV-T-Back.ai’ (143) started
05/06/2010 11:32:34 AM - Page 1 : Plane ’Gray’ started
05/06/2010 11:32:35 AM - Page 1 : Plane ’Gray’ ended
05/06/2010 11:34:35 AM - Warning : a job timeout occurred
05/06/2010 11:34:35 AM - The engine seems to be in a pending busy state
05/06/2010 11:34:35 AM - Trying to reset the engine
05/06/2010 11:34:57 AM - Job ’HTV-T-Back.ai’ (143) ended

The accuset control panel has
Busy
rip active 0c //sometimes it will send through a few centimeters

Attached are two files from the rip job log which don’t seem to match the engine message
log.txt Log message.txt

The file was just plane black text converted to outlines and sent from ai cs4 to the named pipe

Sorry about the long post I hope I haven’t scared everyone off

Thanks

Adam

[spapa]

print a test from the control panel and see if accuset machine is in working condition
(offline, test, try test#0 for example,...)

[VladCanada]

Did you check F1 and F2 fuses at Accuset main board (IEC)?
Just pull them out.
One more Fuse (the same body) installed at APIS PAC board.
If all fuses are OK, the problem at that PAC board: one channel of data exchange RIP -imagesetter has broken, and that channel is responsible for Ready-Busy signal from Accuset.

[Ita]

My guess would be that you should check if your pac driver is in order. You can reinstall it and see if this solves your issue if not maybe you need a new apis pac connection. I use to support this aqcuipment and it happened sometimes.
Good luck with it and keep us posted

[adam470]

Hi Guys
I checked the fuses and they were good
I unplugged the cable plugged it back in made sure it was all tight
I sent a small file through the tcp/ip channel and it worked fine
I sent a different one through the pipe from the front end and it worked fine
shut it all down came back an hour later sent another file and it timed out
tried again with one of the first two and it timed out too

I think the driver is ok I did a reinstall between the two posts

Ita when you wrote apis connection did you mean I need a new apis pac board or something with the cable connectors

Thanks

Adam

[VladCanada]

Shut down Accuset and RIP PC or just imagesetter?

[TechDoc]

For any reason the engine can not respond to the RIP if it has finished a Scanline... Now the RIP waits for this message...until the RIP decides there is a timeout

Could be a problem with the PAC Board, maybe overheaten because the filters in your PC are clogged..
Can be APIS Cable (which goes from PAC to Imagesetter... APIS is dived in Video and Control_Signals.
The Status of the engine will be posted via Control_Signals (diferent wires inside of that cable)

[Ita]

Most of the times just reinstaling your apis driver is enough but maybe you need a new pac board. I would contact the guys that are giving you service on the accuset and its RIP.
Ita

[spapa]

If you have a technitian supporting your shop, maybe worth to try make a new cable.
The cable will connect this pci card

to the gray IDC40 connector (bottom right of next picture)


The cable that can be made for testing is a normal:

with the one end changed to connector matching the PCI card:

(hint: the above connector should be selected for flat cable so can be fitted in seconds on the cable I displayed above).

I have set two (of many) accuset machines working with such cables for many years now.
If the problem exists on the PCI card, there is a possibility to repair it.

[adam470]

Hi Guys

when I shut down I turned of the image setter and rip pc

today I tried to check the cable but couldn't do much so I plugged it all back in
sent a file it timed out so I jiggled the cable and held it straight out the back of the pc and the next file worked fine I'm going to try and get a new cable organised and see if that fixes it but in the mean time I'll try and eliminate other possibilities

dose anybody know if the driver here would be any different than the one on the install disk
AGFA PAC PCI bus APIS" drivers for w2k

Thanks

Adam