We define our function core as a software that controls
all the processes and aggregates of a printing press.
The application runs as a background service
and is remotely controlled by the user interface.
It has an auxiliary user-interface that can be activated as required.
The so-called user interface is coupled to the function kernel via a TCP/IP connection
and communicates with it by a fixed plain text syntax.
It can therefore be created in any programming language,
with any development environment.
The software components basically communicate with each other via TCP/IP.
It does not matter whether the components are running on the same computer or not.
The print data usually provided by a so-called RIP software should be located
on the computer on which the printserver is executed.
The often used preview file can be located on one of the involved computers
in the access of the computer which executes the userinterface.
The so-called print servers are the most important component of our printing system.
They run in the background, process the print data and transmit it to the connected printhead modules.
Print servers involved in print data processing do not necessarily have to run on the same computer.
The motor server application is started and controlled by the function kernel.
It runs in the background and serves as a bridge to the used motor control.
Like all CLUSTERJET software components, the motor servers are also preconfigured
by a configuration file which is loaded when the application is started.
The configuration files can be created or adapted with an ordinary text editor.
The printhead controller hardware generates all the control signals required for the operation of a printhead
and outputs them together with the print data synchronized to an encoder signal.
The motor controllers implement control commands received from the controller
and set the connected motors in controlled motion.
In our case, the ink system controller consists of a small single-board computer
that runs software specifically designed for the application.
We usually use one of these small computers to control the vacuum level,
to refill ink if necessary and to control a cleaning station.
Of course, a PLC can also be used as an alternative.
Due to a very open structure, we can easily create interfaces for additionally required aggregates.
A printhead adapter routes the signals output by a printhead controller to the respective contacts of a printhead.
We define our function core as a software that controls
all the processes and aggregates of a printing press.
The application runs as a background service
and is remotely controlled by the user interface.
It has an auxiliary user-interface that can be activated as required.
The so-called user interface is coupled to the function kernel via a TCP/IP connection
and communicates with it by a fixed plain text syntax.
It can therefore be created in any programming language,
with any development environment.
The software components basically communicate with each other via TCP/IP.
It does not matter whether the components are running on the same computer or not.
The print data usually provided by a so-called RIP software should be located
on the computer on which the printserver is executed.
The often used preview file can be located on one of the involved computers
in the access of the computer which executes the userinterface.
The so-called print servers are the most important component of our printing system.
They run in the background, process the print data and transmit it to the connected printhead modules.
Print servers involved in print data processing do not necessarily have to run on the same computer.
The motor server application is started and controlled by the function kernel.
It runs in the background and serves as a bridge to the used motor control.
Like all CLUSTERJET software components, the motor servers are also preconfigured
by a configuration file which is loaded when the application is started.
The configuration files can be created or adapted with an ordinary text editor.
The printhead controller hardware generates all the control signals required for the operation of a printhead
and outputs them together with the print data synchronized to an encoder signal.
The motor controllers implement control commands received from the controller
and set the connected motors in controlled motion.
In our case, the ink system controller consists of a small single-board computer
that runs software specifically designed for the application.
We usually use one of these small computers to control the vacuum level,
to refill ink if necessary and to control a cleaning station.
Of course, a PLC can also be used as an alternative.
Due to a very open structure, we can easily create interfaces for additionally required aggregates.
A printhead adapter routes the signals output by a printhead controller to the respective contacts of a printhead.