Manroland PECOM Question

Started by johnny_jay, August 11, 2022, 11:42:08 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

johnny_jay

Hello,
We have a Manroland Lithoman, been running great for 5 or so years. One sticking point is the CIP Data we send to the press, the files are huge! When the techs were here installing the press, they were not much help but we got it figured out but the resolution of what we send is 1600 dpi, huge files. Our other presses all take 72 dpi data.

Anyone have any experience with this?

Thanks,

John
Kodak Prinergy and InSite
Preps
Epson P7000 driven by Fiery XF
Screen 16000N
Screen R36000ZX
3 web presses, 1 sheetfed press
G7 Expert

Joe

Are you sending via Prinergy? You can change the resolution in the PrintLink area of your output template.
Mac OS Sonoma 14.2.1 (c) | (retired)

The seven ages of man: spills, drills, thrills, bills, ills, pills and wills.

Joe

Now that I think about it when Manroland came out to setup our Rotoman press they had us send high resolution CIP files to the PECOM also. Maybe a requirement?
Mac OS Sonoma 14.2.1 (c) | (retired)

The seven ages of man: spills, drills, thrills, bills, ills, pills and wills.

johnny_jay

Yes, I can change it to anything in Prinergy. We even experimented on a job or two early on. When we set it up, the tech would just say that it would or would not work.

I got lucky when I posted a question on Print planet and there was a config file I needed and someone there sent me the text file that I had to do a slight modification.

Just seems 1600 is a bit overkill for cip, Pressroom is forced to clear out the cache quite often because of the size of these files.

Kodak Prinergy and InSite
Preps
Epson P7000 driven by Fiery XF
Screen 16000N
Screen R36000ZX
3 web presses, 1 sheetfed press
G7 Expert

Joe

Yeah there are samples of that config file somewhere in your prinergy server. Don't remember exactly where it was but I had to use it to get the correct naming convention right for our CIP files.

I really don't think that setting from your render section has any effect on the CIP files but I could be wrong. That is our one-bit tiff file resolution for plates. The CIP file resolution is in the PrintLink area where it says "Preview Resolution" and in your example that is set to "Very High" and for our Manroland Rotoman presses we used the "High" setting. The documentation for "Preview Resolution" shows:

QuotePreview Resolution
Defines the resolution for the plate preview that appears on the press console viewing station. Select one of the following resolutions in the list:

    • Low resolution is approximately 12.5 ppi, which gives good preview images.
    • Medium resolution is approximately 25 ppi, which gives a sharper preview image with more detail.
    • High resolution is approximately 50 ppi, which gives the sharpest available preview image with the most detail.
    • Very High resolution is up to 100 ppi, which gives the sharpest available preview image with the most detail, depending on the plate output resolution.
Note: Higher resolutions give better quality preview images, but they dramatically increase the preview image file size.

For the Manroland sheetfed press we used "High" also but for our KBA sheetfed and the rest of our web presses we use "Low".

And by we I mean where I used to work which I don't anymore. ;D
Mac OS Sonoma 14.2.1 (c) | (retired)

The seven ages of man: spills, drills, thrills, bills, ills, pills and wills.

johnny_jay

Thanks Joe!

We send 72 dpi to our 3 Komori presses, I will see if I can send a test or two and have pressroom look at it, or maybe just start sending them at 72 dpi and see what happens  ;)
Kodak Prinergy and InSite
Preps
Epson P7000 driven by Fiery XF
Screen 16000N
Screen R36000ZX
3 web presses, 1 sheetfed press
G7 Expert

Joe

Sorry for my confusion but...are you outputting the CIP files using its own process template? I ask because I don't think that resolution you are changing in the render section has any bearing on the CIP files. We output one-bit tiffs and CIP files from the same process template and that resolution setting in the render section was the resolution of our one-bit tiff plate files and had nothing to do with the CIP file resolution.
Mac OS Sonoma 14.2.1 (c) | (retired)

The seven ages of man: spills, drills, thrills, bills, ills, pills and wills.

scottrsimons

This may or may not help. We don't have a Manroland, but have KBA presses and Prinergy. We send our plate files separately from our CIP files. Our CIP files are rendered at 300 dpi with the preview set at 'Very High', where are plates are rendered at 2540 dpi 1-bit tiffs. And I believe the preview is just creating the basic thumbnail image for the pressman on their console for a visual of the job. But when they open the job on the console the 300 or in your case the 1600 image than shows. And our CIP files appear to be under 1mb in general.
"Your superior intellect is no match for our puny weapons!" - Homer J. Simpson

johnny_jay

Joe - Yes, the CIP files are their own output process. We do not output the CIP from the plate output because we have quite a few odd scenarios where there are upper plate changes, lower plate changes, single black plate changes and other odd outputs and the Manroland CIP data must be all 8 separations of a run.

We do it via RBA so we have a manual trigger RBA selected (based on paper) that does 3 things,  sends plate data to the plate setter, creates the CIP file and creates the tiff for PressProof.


Thanks Scott - that is similar to us as on our Komori Presses - the Manroland just needs 1600 dpi which seems extreme. I was mistaken earlier, I said 72 dpi for the Komori, but it is actually 600 dpi, still much less data.

Out Manroland plate size is roughly 46 x 75 inches to you can imagine a 1600 dpi file of that is quite large.

Our largest Komori plate is about 24 x 38 so even at 600 dpi it is much less data.
Kodak Prinergy and InSite
Preps
Epson P7000 driven by Fiery XF
Screen 16000N
Screen R36000ZX
3 web presses, 1 sheetfed press
G7 Expert

Joe

Quote from: scottrsimons on August 12, 2022, 06:09:12 AMThis may or may not help. We don't have a Manroland, but have KBA presses and Prinergy. We send our plate files separately from our CIP files. Our CIP files are rendered at 300 dpi with the preview set at 'Very High', where are plates are rendered at 2540 dpi 1-bit tiffs. And I believe the preview is just creating the basic thumbnail image for the pressman on their console for a visual of the job. But when they open the job on the console the 300 or in your case the 1600 image than shows. And our CIP files appear to be under 1mb in general.
If your actual CIP files were at 300 dpi they would be much larger than 1 MB. What kind of file is being sent to the location in your Device section of your output template? That is the file that will be 300 dpi.

Quote from: johnny_jay on August 12, 2022, 06:27:19 AMJoe - Yes, the CIP files are their own output process. We do not output the CIP from the plate output because we have quite a few odd scenarios where there are upper plate changes, lower plate changes, single black plate changes and other odd outputs and the Manroland CIP data must be all 8 separations of a run.


We do it via RBA so we have a manual trigger RBA selected (based on paper) that does 3 things,  sends plate data to the plate setter, creates the CIP file and creates the tiff for PressProof.

Ahhhh....so it is the tiff file for PressProof that is at 1600 dpi and not the CIP file as the render section does not have any bearing on CIP files. Our render section is at 2400 for the one-bit tifs and PrintLink set to "Low or High" depending on the press. That Preview Image is what the press console scans to set the ink keys and even the "Very High" setting is only at 100 dpi which is a lot higher than most need.

The setting for resolution in the render section only affects files going to the location listed in the "Device Section". The only setting that affects the resolution of the CIP files is the Preview Image of the PrintLink section.
Mac OS Sonoma 14.2.1 (c) | (retired)

The seven ages of man: spills, drills, thrills, bills, ills, pills and wills.

scottrsimons

Quote from: Joe on August 12, 2022, 07:07:26 AMIf your actual CIP files were at 300 dpi they would be much larger than 1 MB. What kind of file is being sent to the location in your Device section of your output template? That is the file that will be 300 dpi.
Joe, our system is sending 'generic press interface' ppf files, so I'm assuming that is why they are so small. And we are not using the 'Device' tab in out Process Template. And they are being sent to a CIPLinkX server.

Render.png PrintLink.png Device.png
"Your superior intellect is no match for our puny weapons!" - Homer J. Simpson

Joe

Quote from: scottrsimons on August 12, 2022, 07:20:08 AMJoe, our system is sending 'generic press interface' ppf files, so I'm assuming that is why they are so small. And we are not using the 'Device' tab in out Process Template. And they are being sent to a CIPLinkX server.

Try sending CIP files using the same PrintLink config but change the resolution in the render section. I think you will find it doesn't change the size of the ppf files in CIPLinkX (which is what we use for the KBA press too). We do output plate one-bit tiffs at the same time we output the CIP files and our render setting is 2400 dpi and that is what our plate files come out as. If that setting affected the CIP files they would be uncontrollably large and they are not. They are very small files as we have the setting on "Low" for our KBA press in the PrintLink settings.
Mac OS Sonoma 14.2.1 (c) | (retired)

The seven ages of man: spills, drills, thrills, bills, ills, pills and wills.

johnny_jay

Thanks everyone - I'll talk with the press room and try a test on a live job.
Kodak Prinergy and InSite
Preps
Epson P7000 driven by Fiery XF
Screen 16000N
Screen R36000ZX
3 web presses, 1 sheetfed press
G7 Expert