Overview AutoLab4j: Difference between revisions
No edit summary |
No edit summary |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:AutoLab4j]] | |||
=Overview= | =Overview= | ||
| Line 9: | Line 10: | ||
AutoLab4j would typically be installed on a workstation next to the production line/labeller and as such you may have multiple copies running on a site. LabelServer handles mutiple printers from a central location but does not have any visual user interface. | AutoLab4j would typically be installed on a workstation next to the production line/labeller and as such you may have multiple copies running on a site. LabelServer handles mutiple printers from a central location but does not have any visual user interface. | ||
[[file:AutoLab4j_Animation.gif|800px]] | |||
[https://www.flaticon.com/free-icons/conveyor-belt Image from FlatIcon created by vectorsmarket15] | |||
[[file:AutoLab4j_3.png|800px]] | [[file:AutoLab4j_3.png|800px]] | ||
Latest revision as of 13:09, 2 September 2024
Overview
AutoLab4j is a program which has been developed to enable automatic label printing based on a trigger signal from a modbus device.
It was created to compliment the Commander4j application but in theory could be used with other systems.
This application is quite similar in role to the LabelServer program. The main difference is that AutoLab4j runs as a forground application with tray icon and has a visual component including a label preview, whereas the LabelServer program runs as a service and is normally run on a server.
AutoLab4j would typically be installed on a workstation next to the production line/labeller and as such you may have multiple copies running on a site. LabelServer handles mutiple printers from a central location but does not have any visual user interface.
Image from FlatIcon created by vectorsmarket15
