Overview LabelServer4j: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
You should refer to the documentation on [[Production Lines & Labellers]] | You should refer to the documentation on [[Production Lines & Labellers]] | ||
[[file:ManualLabAutomated2.gif|link=|800px]] | |||
Latest revision as of 10:24, 1 September 2024
LabelServer is a module of Commander4j which is designed to send data provided by Commander4j to external Labellers via a script which is just plain text. The script can contain specific printer commands and or data in whatever combination is needed. Therefore the application can accomodate a variety of printer types.
It shares a lot with the AutoLab4j module but has some important differences as well.
Rather than replicate wiki pages across the multiple Commander4j modules - some of the links will take to the relevant wiki page of the referenced program.
AutoLab4j is designed to send data when requested via a Modbus signal and is intended to generate a unique SSCC on each request. This makes the AutoLab4j program more suitable for Pallet Label.
The LabelServer application will send data to a labeller when an operator has assigned an order to a production line within the Commander4j application. This is more suitable for Case Label where the data remains the same (no SSCC).
You should refer to the documentation on Production Lines & Labellers
