Printing problame with bizhub c500 pro with ip-901/s300

[Leonard]

It's really strange that happens, you should be doing some kind of maintenance or the machine to cause this bug, otherwise it is more likely that the failure is given by a software error, if during a printing process I leave this corrupt file problem on the Fiery.

I insist that if a communication error between the Fiery and the C500 would have an error code, the fiery color does not send information in independent channels, this communication is established THROUGH a printer language.

Finally leave a small image which you can copy the configuration, this would help prevent the Fiery print THROUGH ICC (Profiles) corrupt, you can also try different output profiles.

Dear friends, Dear jma676,

i tried to fillowing your intructions and off course it's better if this only software problame.
i sent the pic result to this forum.

[Leonard]

and this day, i tried to configures color profile on printing properties. but still had result like above pic, but still sama And i have question, on our fiery's lcd, there is version 1.1 and this fiery using version 1.1eu. so i want upgrade driver from v1.1eu to v2.0eu, so maybe if i upgrade it's one solution, how to upgrade?
yesterday i tried to download fiery profile color, but how to use it?

[Leonard]

when i tried to print i found magenta vertical lines, it's clear on above pic.tq

[Stirton.M]

the problem is likely hardware. Damaged or defective cable, VIF or controller card in the fiery itself.

[Stirton.M]

A TSB entry gives some support to the software theory...

the interface cable from the controller to the machine - check for any bent pins and reverse the cable if possible.
Open up the controller and reseat all boards and connectors.
Reload system code and all patches. The latest version firmware or system software is available via the Konica Minolta Download Selector. Access the
Selector from SSD Web Support (CS Expert Support) by clicking on 'Download MSDS, Drivers, Firmware and more'.
____________________________________
Solution ID TAUS0627178EN* Solution Usage 2
Description
Test pages and print jobs are missing yellow.
Solution
CAUSE: Failed video interface board.
SOLUTION: Replace the video interface board (p/n 45032964).
__________________________________________________ __

If I recall, you purchased this controller separately through Ebay. Was it specifically for a Konica Minolta C500, or was it for a third party remark like Ikon? The point here being is that there is proprietary interface requirements. I have a suspicion you may be dealing with something as simple as this, and of course, I wonder if there really was a problem with the fiery, which is why it was for sale on Ebay for so cheap.

Reinstalling system may correct the problem. Unfortunately I will not provide this code for you, even though I have access to it. Contact your nearest KM dealer/branch for support on that particular issue. You may be forced to have a service tech look regardless.

[jma676]

and this day, i tried to configures color profile on printing properties. but still had result like above pic, but still sama And i have question, on our fiery's lcd, there is version 1.1 and this fiery using version 1.1eu. so i want upgrade driver from v1.1eu to v2.0eu, so maybe if i upgrade it's one solution, how to upgrade?
yesterday i tried to download fiery profile color, but how to use it?

Version.

IP-901 S300 Sys ver6.1 - Fiery verV2.0
IP-901 S300 Sys ver5.5 - Fiery verV1.1

has received a good stack of data with this and should solve your problem, I hope.

[jma676]

A TSB entry gives some support to the software theory...

[I][B]the interface cable from the controller to the machine - check for any bent pins and reverse the cable if possible.

Another case that we do not give attention to the continuity of the thread, Stirton.M you really think this bug can cause the Cable? separately from what is in the Bulletin, let me know.

[HORSE]

I Still reckon it's the video interface board.

[RRodgers]

You can't go from version 1.1 to version 2 without the dongle from EFI. Don't try it, it won't work. So if it was a version 1.0 or 1.1 keep it that way.

[Stirton.M]

Another case that we do not give attention to the continuity of the thread, Stirton.M you really think this bug can cause the Cable? separately from what is in the Bulletin, let me know.

The part I highlighted in RED is a part of that specific entry in the TSB. It is not something I added, merely highlighted to bring attention to what I have seen personally with regard to damaged cables. Contrary to your belief, the cable does send separate channel data, otherwise, why have all those data lines. Seems to be a waste don't you think?

Similar issues have been seen by me on the VIF as well as the controller end (as Horse also contents). As the TSB also does mention possible incorrect settings of the controller. The attached sample to that TSB is almost virtually identical to the OP's issue.
ps-test.jpg

Further, the cable itself can still have problems and never generate a code event. Hence why I posted the excerpt from that TSB. Understand now?

[HORSE]

I was talking about the Video Interface board of the controller.

[Stirton.M]

I was talking about the Video Interface board of the controller.

Sorry, yes, there is a distinction to that piece of hardware too. I edited it to reflect that correction. It was all in the wording, which I should have seen.

I think I even mentioned that as well, a few posts back.

[jma676]

The attached sample to that TSB is almost virtually identical to the OP's issue.

JA JA! Would think that this is almost impossible, because the red should not be present, it is clear that the color red is Postscript, but can not be absent Magenta this is just the start, No red without Magenta, that's clear. I'm surprised that this sample.
(Same with the Cyan / without Cian no blue nor green)

Make a quick test leads to zero the maximum density of magenta or cyan in color in ColorWise setup.

PS=If you pay attention you will understand that this sample shows a simulation profile /ISO Coated Copy 1/ is edited by someone who wanted to simulate this failure.)

[jma676]

OK, I understand what you say and what is explained by the TBS, thanks for replying, if you pay a little attention I said exactly what it is on TBS without having read it before your posting.

This type of failure it is good to analyze the operation of the communication between the Fiery and printer, and clear faults often occur without any kind of acknowledgment code in the system, but also I have the certainty that when a circuit or cable does not work, the system should not work.

Well we know that the information and theory of operation of equipment in the manual are limited.

I had a few months ago to repair a Bizhub Pro C6500 that had the code C-C101, actually I had to replace the PRCB and never acknowledge problems.
The odd thing is that apparently the team was running smoothly before but had joined the code C-C102.
(Of course no ICP was broken).

But then the Managers and policy changes, I'm old school my start was with analog equipment Ricoh remember that the system always bring a good explanation attached operation.

Today the field technician only needs to check and replace everything quickly Feature and what does not and we should not be reviewing a PRCB on the field.

[Chromatik]

wow