Hi,
I think we are talking about 2 different items here.
When operators talk about plate calibration , they usual refer to the linearization of the plate.
With plate linearization , I mean adjustments done on a workflow level to make sure that the requested dot % is also seen on the plate. In practive you expose a pattern with the complete range ( from 1 to 99 % ) , and you measure the result. This correction data is stored in the workflow, and you don´t need a HW engineer to help you with this. Users can create these curves themself.
When HW engineers talk about plate calibration, they usually refer to optical adjustments. Think about settings related to laser power, drum speed , focus , etc.... .
These settings are stored in a platedatabase , as mentiond in a previous reply.
This PlateDB sits inside the HW of the machine, and the information is copied towards the Operator Control Terminal ( OCT ) during boot.
Although not fully correct , I like to consider the OCT as a part of the engine. You can easily run the OCT software on a simple laptop sitting on top of the machine. You only need a serial cable to do so. But I have to admit , most people run it on the same platform as the workflow , and as such they think this is part of Apogee.
The workflow connects to the engine by the APIS cable.
Plate specific information is shared by using PlateID´s ( numbers ). And yes, Apogee gets this info from the engine.
So , to come back to the original question.
What if I something went wrong with the workflow ?
The plateDB , containing all hardware specific information , is still available in the engine. No problem.
Your OCT will find this data , as soon as it is connected.
Now Apogee needs to find the available plates ( or do they call it "media" ). I don´t think this happens automatically, so you probably need to click some buttons to do so.
After that , you must be able to output plates again.
As soon as plates come out , you should check the "linearization" and make new correction curves.
W3112