iPR_C1_Upgrade to _v64.06

[Stanman]

I upgraded My iPR_C1 to v64.06 and I am wondering if using SST v3.35E was ok or should
I have used SST v4.04Eq.
Any input on this would be appreciated.

[SCREWTAPE]

I upgraded My iPR_C1 to v64.06 and I am wondering if using SST v3.35E was ok or should
I have used SST v4.04Eq.
Any input on this would be appreciated.

You should use the latest v4.22. You can also use v4.04 or v4.11.
If you don't have any issues after upgrading then I wouldn't worry.

[Stanman]

You should use the latest v4.22. You can also use v4.04 or v4.11.
If you don't have any issues after upgrading then I wouldn't worry.

I have issues but then I had them before upgrading but in your opinion
should I try again with v4.04?

[SCREWTAPE]

I have issues but then I had them before upgrading but in your opinion
should I try again with v4.04?

What kind of issues did you have before?

[Stanman]

Thanks for your interest in my C1 problems.
Well I used SST v4.04 today and re-installed v64.06 but it did not change anything.
The issues i have been having is when I try to print from Q1 server I get an error message
E000747-8000.
The communication between Fiery and C1 is fine and file does try to print etc.
I tried re-seating all the cards, the boot-rom and the memory and still no good.
I was told I should try to connect a laptop directly to C1 through crossover and see if it will print.
If it did print would this really tell me anything?
If it can be connected that way how would I go about it?
Would I use the IP address 10.255.255.1 and set up a port or what?

[Oze]

You may need to load a print driver but basically put the laptop within range of the C1 then ping it...if the connection's ok add the C1 as a printer and load the driver if necessary on a new TCP/IP port.

[Stanman]

You may need to load a print driver but basically put the laptop within range of the C1 then ping it...if the connection's ok add the C1 as a printer and load the driver if necessary on a new TCP/IP port.

Do you know what I would set the interface value (0-5) in order to print directly from pc?
I know 3 is supposed to be the setting for Q1 server.

[SCREWTAPE]

Thanks for your interest in my C1 problems.
Well I used SST v4.04 today and re-installed v64.06 but it did not change anything.
The issues i have been having is when I try to print from Q1 server I get an error message
E000747-8000.
The communication between Fiery and C1 is fine and file does try to print etc.
I tried re-seating all the cards, the boot-rom and the memory and still no good.
I was told I should try to connect a laptop directly to C1 through crossover and see if it will print.
If it did print would this really tell me anything?
If it can be connected that way how would I go about it?
Would I use the IP address 10.255.255.1 and set up a port or what?

It won't print if you try connecting to the machine, you must have a printer kit installed. If you have a fiery connected that means that there is optional hardware already installed into the machine for that fiery. If you want to connect to the fiery directly, yes a crossover cable would be needed. You can use static iP or you can use DHCP which will automatically choose a IP address for the Q1. A standard tcp/ip port would need to be created in order to install a print driver.

E000747-8000, is this constant or intermit.
Is this your initial problem. This is image data transfer error.
Are you certified on this machine?
There some things you can try,
if this is your main issue.

[Stanman]

It won't print if you try connecting to the machine, you must have a printer kit installed. If you have a fiery connected that means that there is optional hardware already installed into the machine for that fiery. If you want to connect to the fiery directly, yes a crossover cable would be needed. You can use static iP or you can use DHCP which will automatically choose a IP address for the Q1. A standard tcp/ip port would need to be created in order to install a print driver.

E000747-8000, is this constant or intermit.
Is this your initial problem. This is image data transfer error.
Are you certified on this machine?
There some things you can try,
if this is your main issue.

I have a computer with command workstation that I can send a file to fiery but it is no different results than sending a test file from fiery. A tech friend just suggested trying to print without the fiery but I am gathering from what you say that it cannot print from any other source with it's installed hardware. Yes the C1 came set up for the fiery.
The fiery is connected with crossover and test files do get processed by the C1 then it comes up with the error every time. E000747-8000, is constant.
The fiery has been restored from the original disks, and works fine,
like you say it is an image transfer error.
I am not certified on C1, I am wondering if I need remove the interface card that connects
to fiery and get someone to try it in another machine or is there some other way you could suggest to check if it's functioning correctly?

[SCREWTAPE]

I have a computer with command workstation that I can send a file to fiery but it is no different results than sending a test file from fiery. A tech friend just suggested trying to print without the fiery but I am gathering from what you say that it cannot print from any other source with it's installed hardware. Yes the C1 came set up for the fiery.
The fiery is connected with crossover and test files do get processed by the C1 then it comes up with the error every time. E000747-8000, is constant.
The fiery has been restored from the original disks, and works fine,
like you say it is an image transfer error.
I am not certified on C1, I am wondering if I need remove the interface card that connects
to fiery and get someone to try it in another machine or is there some other way you could suggest to check if it's functioning correctly?

You can try to clear MNcon.
But please use precaution. There has been some cases where clearing MNcon resolved certain issue with E747-8000

MNcon operation method.
1) Select this item and press the OK key.
2) Turn OFF/ON the main power.
- The RAM data is cleared after the main power switch is turned OFF/ON.
- When this mode is executed, all the data in the SRAM board is initialized.
The file control information for a hard disk is also initialized, and image data in the hard disk cannot be read. Before you execute this mode, be sure to inform a user that all images in the box are going to be initialized and receive prior approval from him/her.
1) Print out the service mode data by COPIER > FUNCTION > MISC-P > P-PRINT.
2) Select this item and press the OK key. The machine is automatically activated and displays a message indicating "please turn on the main power again".
3) Turn OFF/ON the main power.

Also try and remove SDRAM from the Main Controller PCB.
2. Wipe the terminal of SDRAM with lint-free paper impregnated with alcohol, and then re-fit the SDRAM.
This is a part # just in case its the SDRAM WA7-3617 SD-RAM (DIMM)

Good luck.

[Penvy]

I feel your pain on this C1,

1st rule is NOT to add any other problems to this
C1 error.

These guys are correct,
Use the Q1 to print from
The Fiery controller log on should be automatic from the PC to the Q1
Remember ,this is what has to work anyway but you can ck the ip addy
at the log on.

Save all the print outs and door settings,
sometimes the install tech will leave the big printout
setup info with all of the service settings level 1 and 2
BE VERY CAREFUL NOT TO JUST START PLAYING WITH THESE SETTINGS

I cleared everything on mine when I did the "ALL" firmware upgrade
The USB stick is great but to do a complete upgrade,
the PC is the way to go.
I did the "all" to cover everything even the HDD.

Then I reset the "door settings"
One thing on the adj-x and Y for the scanner are backwards (on Mine)
and you get a black line across the front/side
just remember to look for that.

THe PCB's and subs are the last resort to replace and I
have found there would be other errors pointing to these.

My question is what happened just before this error came up.
Loss of power? unplugged? shutdown?
Jam?

P

[Stanman]

You can try to clear MNcon.
But please use precaution. There has been some cases where clearing MNcon resolved certain issue with E747-8000

MNcon operation method.
1) Select this item and press the OK key.
2) Turn OFF/ON the main power.
- The RAM data is cleared after the main power switch is turned OFF/ON.
- When this mode is executed, all the data in the SRAM board is initialized.
The file control information for a hard disk is also initialized, and image data in the hard disk cannot be read. Before you execute this mode, be sure to inform a user that all images in the box are going to be initialized and receive prior approval from him/her.
1) Print out the service mode data by COPIER > FUNCTION > MISC-P > P-PRINT.
2) Select this item and press the OK key. The machine is automatically activated and displays a message indicating "please turn on the main power again".
3) Turn OFF/ON the main power.

Also try and remove SDRAM from the Main Controller PCB.
2. Wipe the terminal of SDRAM with lint-free paper impregnated with alcohol, and then re-fit the SDRAM.
This is a part # just in case its the SDRAM WA7-3617 SD-RAM (DIMM)

Good luck.

I tried everything you suggested Screwtape.
I cleared MNcon, did the P-Print, removed and cleaned the SDRAM (2nd time), removed cleaned and re-seated boot ROM, I also removed and cleaned contacts on the interface board that connects to the video from Fiery.
Was there some information you wanted me to look at or tell you from the P-Print?
After I cleared the MNcon I noticed that it had changed the interface setting to "0".
Is that the default or do you just have to set it again?
It did not "see" the Fiery again until I set interface to "3", after that communication was ok and the same no matter what I set it to, (0-5).
Is it supposed to be set on "3" for Fiery, that is what I had been told?
Something I had not mentioned before is that no matter what I set the interface setting on when I send a test file from Fiery, details of the file always show "0" bytes file size.
I also ended up with an "Invalid or corrupt default key" message and had to correct that.

I feel your pain on this C1,

1st rule is NOT to add any other problems to this
C1 error.

These guys are correct,
Use the Q1 to print from
The Fiery controller log on should be automatic from the PC to the Q1
Remember ,this is what has to work anyway but you can ck the ip addy
at the log on.

Save all the print outs and door settings,
sometimes the install tech will leave the big printout
setup info with all of the service settings level 1 and 2
BE VERY CAREFUL NOT TO JUST START PLAYING WITH THESE SETTINGS

I cleared everything on mine when I did the "ALL" firmware upgrade
The USB stick is great but to do a complete upgrade,
the PC is the way to go.
I did the "all" to cover everything even the HDD.

Then I reset the "door settings"
One thing on the adj-x and Y for the scanner are backwards (on Mine)
and you get a black line across the front/side
just remember to look for that.

THe PCB's and subs are the last resort to replace and I
have found there would be other errors pointing to these.

My question is what happened just before this error came up.
Loss of power? unplugged? shutdown?
Jam?

P

What happened just before error came up was machine was shipped from California to Va.
It supposidly worked "fine" before it was shipped.

[SCREWTAPE]

I tried everything you suggested Screwtape.
I cleared MNcon, did the P-Print, removed and cleaned the SDRAM (2nd time), removed cleaned and re-seated boot ROM, I also removed and cleaned contacts on the interface board that connects to the video from Fiery.
Was there some information you wanted me to look at or tell you from the P-Print?
After I cleared the MNc I noticed that it had changed the interface setting to "0".
Is that the default or do you just have to set it again?
It did not "see" the Fiery again until I set interface to "3", after that communication was ok and the same no matter what I set it to, (0-5).
Is it supposed to be set on "3" for Fiery, that is what I had been told?
Something I had not mentioned before is that no matter what I set the interface setting on when I send a test file from Fiery, details of the file always show "0" bytes file size.
I also ended up with an "Invalid or corrupt default key" message and had to correct that.



What happened just before error came up was machine was shipped from California to Va.
It supposedly worked "fine" before it was shipped.

The fiery should be set to 3.
As i said take some precautions. You did well.
Are you still getting E747.

[Stanman]

The fiery should be set to 3.
As i said take some precautions. You did well.
Are you still getting E747.

Yes, E000747-8000, same as it ever was.
Does the file size "0" tell you anything?

[SCREWTAPE]

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?