Dgarratt: Updated by push_wiki.py

2026-04-01T10:26:16Z

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category:LabelServer4j]]
+This page describes the end-to-end operational workflow of LabelServer4j — from an operator assigning a process order in Commander4j through to a label being printed on the production line.
-The easiest way to work with the LabelServer application is to drive it from the Commander4j desktop software. In the screen below you will see the Pallet Labelling screen. The operator selects the order and then uses the "Assign to Labeller" button. They can then choose the production line which the order data is sent to. This data is exported via the Commander4j Interfaces in CSV format. The LabelServer program reads this data and sends it to the labellers which are defined in the configuration.
+Each configured labeller runs in its own background thread. All labellers poll and execute simultaneously. A site with six printers runs six independent threads, each managing its own TCP connection and input directory.
-More information on label printing can be found in the Commander4j wiki in the [[Production Declaration]] and [[Pallet Label]] pages. The data exported from the Commander4j is written to the folder defined within the [[Production Lines & Labellers]] screen.
+See also: [[Overview LabelServer4j]], [[LabelServer4j Configuration]], [[LabelServer4j Dataset CSV]], [[LabelServer4j Folder Structure]], [[Production Lines & Labellers]]
-[[file:AutoLab_Operation1.png|link=|800px]]
+[[Category:LabelServer4j]]

Dgarratt at 18:50, 31 August 2024

2024-08-31T18:50:20Z

← Older revision		Revision as of 20:50, 31 August 2024
Line 1:		Line 1:
	Category:LabelServer4j		[[Category:LabelServer4j]]

	The easiest way to work with the LabelServer application is to drive it from the Commander4j desktop software. In the screen below you will see the Pallet Labelling screen. The operator selects the order and then uses the "Assign to Labeller" button. They can then choose the production line which the order data is sent to. This data is exported via the Commander4j Interfaces in CSV format. The LabelServer program reads this data and sends it to the labellers which are defined in the configuration.		The easiest way to work with the LabelServer application is to drive it from the Commander4j desktop software. In the screen below you will see the Pallet Labelling screen. The operator selects the order and then uses the "Assign to Labeller" button. They can then choose the production line which the order data is sent to. This data is exported via the Commander4j Interfaces in CSV format. The LabelServer program reads this data and sends it to the labellers which are defined in the configuration.

2024-08-31T18:49:55Z

← Older revision		Revision as of 20:49, 31 August 2024
Line 1:		Line 1:
	Category:LabelServer4j		Category:LabelServer4j

			The easiest way to work with the LabelServer application is to drive it from the Commander4j desktop software. In the screen below you will see the Pallet Labelling screen. The operator selects the order and then uses the "Assign to Labeller" button. They can then choose the production line which the order data is sent to. This data is exported via the Commander4j Interfaces in CSV format. The LabelServer program reads this data and sends it to the labellers which are defined in the configuration.

			More information on label printing can be found in the Commander4j wiki in the [[Production Declaration]] and [[Pallet Label]] pages. The data exported from the Commander4j is written to the folder defined within the [[Production Lines & Labellers]] screen.

			[[file:AutoLab_Operation1.png\|link=\|800px]]

2024-08-31T11:10:08Z

Created page with "Category:LabelServer4j"

New page

Category:LabelServer4j