iPR_C1_Upgrade to _v64.06

[Stanman]

I know this might be stupid question.
Are you using the right PS driver for the Q1?
Did it come with user software?

Have you removed the fiery from the machine and if so, do you still get the E-code.

Does the file size "0" tell you anything?
No, It might be 0 because its not processing or going thru.

This only happen when you print, It does not happen on power up?

There are a couple of more things that can cause E747
1.sdram, As we know already.
2.memory (dimms)
3.main controller fault

Do you see a printer tab on the control panel.

How certain are you that this unit was working properly when it was shipped.

Last ?

Do you have a email address?

If I remove Fiery I do not get any error. I can print a file from control panel that does not go through Fiery, like the P-Print etc.
I had not mentioned the fact but I have a keyboard, monitor and mouse on Fiery so I can see what is going on.
The command workstation toolbar at the top of the screen turns red and says check network cable etc when I turn off the C1. The printer tab on C1 shows the printer and if I turn off Fiery it says "please wait". I am actually sending test files from Fiery directly.
If I use the control panel on C1 and send a file it is seen on the Fiery so I know that part is working but I feel like it is all in the file info not going through the video card/cable to C1.
You said sdram and then memory (dimms), I removed cleaned one dimm that was below hdd,
and the boot rom that was on the right side off hdd.
sdram? Is there more memory other than what I now about?
PM sent

[Penvy]

IF this mach was running before being shipped
usually the 1 cable I would look for is the short lan cable (marked)
from the Q1 to the C1
Also the input from the hub/PC to the Q1

Being able to print from the control panel is a big one,
That says the C1 itself should be OK
Sorry If I did not read that before somewhere in these posts that you stated that from the start!
Just dont want to go chasing other problems that are not there.

SO the point here is something changed after shipping.
that can be a problem if it was NOT prepared to do that!
But not usually in the PCB's unless this was shipped by stagecoach!

Just moving it from one part of the shop can be a problem.
Usually toner all over the place inside.

I am thinking that the correct cables have been switched/lost/broken


ALSO "who" can state the C1 was working before shipping.
Just my 3 cents....used to be 2 cents but costs went up!
P

[Stanman]

SO the point here is something changed after shipping.
that can be a problem if it was NOT prepared to do that!
But not usually in the PCB's unless this was shipped by stagecoach!

Just moving it from one part of the shop can be a problem.
Usually toner all over the place inside.

I am thinking that the correct cables have been switched/lost/broken


ALSO "who" can state the C1 was working before shipping.
Just my 3 cents....used to be 2 cents but costs went up!
P

It might as well have been "shipped by stagecoach", it had to come up a 1 mile long unfinished gravel, dirt, rd full of potholes up the side of a mountain.

[KenB]

I would imagine you've tried this already, but in case you haven't, power everything down, and remove the SCSI cable between the RIP and C1, and check very carefully for any bent pins. You may also want to reseat the interface cards (that the cable connects to) in both units.

If I'm not mistaken, the crossover cable carries the signals between the two, while the SCSI carries the data itself. It sounds like the two are communicating, but the print data isn't getting through.

Note: This is not a true SCSI cable, but rather a proprietary one. That means that if it's bad, you have to get one from Canon.

[Stanman]

I would imagine you've tried this already, but in case you haven't, power everything down, and remove the SCSI cable between the RIP and C1, and check very carefully for any bent pins. You may also want to reseat the interface cards (that the cable connects to) in both units.

If I'm not mistaken, the crossover cable carries the signals between the two, while the SCSI carries the data itself. It sounds like the two are communicating, but the print data isn't getting through.

Note: This is not a true SCSI cable, but rather a proprietary one. That means that if it's bad, you have to get one from Canon.

It is getting the file name etc and trying to print but it is not getting actual file.
This cable and the interface cards at both ends are in my mind were the problem lies.
I have reseated the card in C1 but not in the Q1, I have two of the cables but I have not thought to inspect them closely as you suggested.

[KenB]

It is getting the file name etc and trying to print but it is not getting actual file.
This cable and the interface cards at both ends are in my mind were the problem lies.
I have reseated the card in C1 but not in the Q1, I have two of the cables but I have not thought to inspect them closely as you suggested.

Are you able to print a config page from the Fiery to the C1?

Press F4 on the keyboard, and print a config page (or any of its buddies) from there.

If all that works, then the cabling and cards are OK.

[Stanman]

Are you able to print a config page from the Fiery to the C1?

Press F4 on the keyboard, and print a config page (or any of its buddies) from there.

If all that works, then the cabling and cards are OK.

No, it will not print anything from Fiery, it will send to C1, green light will keep flashing and it will say "waiting to print" and eventually come up with error code.