Commander4j - Recent changes [en-gb]

Label Function Syntax

Dgarratt — Wed, 24 Jun 2026 12:37:56 GMT

Updated by push_wiki.py

@@ Line 8: / Line 8: @@
   <*SSCC*>  <*QUANTITY*>  <*DESCRIPTION*>
 ===DATE_CREATED===
@@ Line 39: / Line 45: @@
 ===IIF===
-  <IIF,param1,param2,param3,param4>
+  <IIF(param1,param2,param3,param4)>
   IF param1 = param2 then
@@ Line 83: / Line 89: @@
   <PALLET_WEIGHT_BARCODE(KG,3)>
 ===PALLET_WEIGHT_TEXT===
 ===PRODDATE===
 ===RIGHT===
@@ Line 95: / Line 132: @@
 ===SUBSTRING===
 ===SUBTR_LPAD===
 ===TIMESTAMP===
 ===TRIM===
 ===UPPERCASE===
@@ Line 103: / Line 171: @@
 ===USERNAME===
 ===VERSION===

ModbusServer

Dgarratt — Mon, 22 Jun 2026 14:23:09 GMT

Updated by push_wiki.py

← Older revision		Revision as of 16:23, 22 June 2026
Line 159:		Line 159:

	* [[ModbusClient]] — the client-side companion tool		* [[ModbusClient]] — the client-side companion tool
	* [[AutoLab4j]] — ~~an automatic labeller that~~ uses the same Modbus stack to ~~watch production-line signals~~		* [[AutoLab4j]] — uses the same Modbus stack to monitor a coil and trigger a labeller on a change of state
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

ModbusClient

Dgarratt — Mon, 22 Jun 2026 14:23:08 GMT

Updated by push_wiki.py

← Older revision		Revision as of 16:23, 22 June 2026
Line 143:		Line 143:

	* [[ModbusServer]] — the server-side companion tool		* [[ModbusServer]] — the server-side companion tool
	* [[AutoLab4j]] — ~~an automatic labeller that~~ uses the same Modbus stack to ~~watch production-line signals~~		* [[AutoLab4j]] — uses the same Modbus stack to monitor a coil and trigger a labeller on a change of state
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

ModbusBridge

Dgarratt — Mon, 22 Jun 2026 14:23:07 GMT

Updated by push_wiki.py

← Older revision		Revision as of 16:23, 22 June 2026
Line 131:		Line 131:
	* [[ModbusClient]] — the interactive desktop Modbus client; the Bridge reuses its Modbus engine		* [[ModbusClient]] — the interactive desktop Modbus client; the Bridge reuses its Modbus engine
	* [[ModbusServer]] — the server-side companion tool, useful as a bench target for the Bridge		* [[ModbusServer]] — the server-side companion tool, useful as a bench target for the Bridge
	* [[AutoLab4j]] — ~~an automatic labeller that~~ uses the same Modbus stack to ~~watch production-line signals~~		* [[AutoLab4j]] — uses the same Modbus stack to monitor a coil and trigger a labeller on a change of state
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

ModbusServer

Dgarratt — Mon, 22 Jun 2026 14:22:36 GMT

Updated by push_wiki.py

← Older revision		Revision as of 16:22, 22 June 2026
Line 87:		Line 87:

	The '''Start / Stop''' button (the toggle at the top of the right-hand toolbar) binds and unbinds the server. The bind address, port and unit ID can only be changed while the server is stopped. The server can be stopped and started again without restarting the application, and '''all register values are kept across a stop/start''' — they are only lost when you exit the application.		The '''Start / Stop''' button (the toggle at the top of the right-hand toolbar) binds and unbinds the server. The bind address, port and unit ID can only be changed while the server is stopped. The server can be stopped and started again without restarting the application, and '''all register values are kept across a stop/start''' — they are only lost when you exit the application.

	~~[[File:ModbusServer1.png\|600px]]~~

	=== Register Table ===		=== Register Table ===
Line 161:		Line 159:

	* [[ModbusClient]] — the client-side companion tool		* [[ModbusClient]] — the client-side companion tool
	* [[AutoLab4j]] — uses the same Modbus stack to ~~read laboratory instruments~~		* [[AutoLab4j]] — an automatic labeller that uses the same Modbus stack to watch production-line signals
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

ModbusClient

Dgarratt — Mon, 22 Jun 2026 14:22:35 GMT

Updated by push_wiki.py

← Older revision		Revision as of 16:22, 22 June 2026
Line 77:		Line 77:

	The '''Connect / Disconnect''' button (the toggle at the top of the right-hand toolbar) opens and closes the connection. The host, port and unit ID can only be changed while disconnected. Once connected, the client polls the server roughly four times a second and the grid updates live.		The '''Connect / Disconnect''' button (the toggle at the top of the right-hand toolbar) opens and closes the connection. The host, port and unit ID can only be changed while disconnected. Once connected, the client polls the server roughly four times a second and the grid updates live.

	~~[[File:ModbusClient1.png\|600px]]~~

	=== Register Table ===		=== Register Table ===
Line 145:		Line 143:

	* [[ModbusServer]] — the server-side companion tool		* [[ModbusServer]] — the server-side companion tool
	* [[AutoLab4j]] — uses the same Modbus stack to ~~read Modbus printing triggers~~		* [[AutoLab4j]] — an automatic labeller that uses the same Modbus stack to watch production-line signals
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

ModbusBridge

Dgarratt — Mon, 22 Jun 2026 14:22:34 GMT

Updated by push_wiki.py

← Older revision		Revision as of 16:22, 22 June 2026
Line 131:		Line 131:
	* [[ModbusClient]] — the interactive desktop Modbus client; the Bridge reuses its Modbus engine		* [[ModbusClient]] — the interactive desktop Modbus client; the Bridge reuses its Modbus engine
	* [[ModbusServer]] — the server-side companion tool, useful as a bench target for the Bridge		* [[ModbusServer]] — the server-side companion tool, useful as a bench target for the Bridge
	* [[AutoLab4j]] — uses the same Modbus stack to ~~read laboratory instruments~~		* [[AutoLab4j]] — an automatic labeller that uses the same Modbus stack to watch production-line signals
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

Template:Menu Applications

Dgarratt — Mon, 22 Jun 2026 14:18:50 GMT

Applications

← Older revision		Revision as of 16:18, 22 June 2026
Line 25:		Line 25:
	====[[Middleware4j]]====		====[[Middleware4j]]====
	\|-		\|-
			\|\|[[file:Modbus_256x256.png\|link=[[ModbusBridge]]\|100px]]
			====[[ModbusBridge]]====
			\|
	\|\|[[file:Modbus_256x256.png\|link=[[ModbusClient]]\|100px]]		\|\|[[file:Modbus_256x256.png\|link=[[ModbusClient]]\|100px]]
	====[[ModbusClient]]====		====[[ModbusClient]]====
Line 33:		Line 36:
	\|\|[[file:SFTGet4j_256x256.png\|link=[[SFTPGet]]\|100px]]		\|\|[[file:SFTGet4j_256x256.png\|link=[[SFTPGet]]\|100px]]
	====[[SFTPGet]]====		====[[SFTPGet]]====
	\|		\|-
	\|\|[[file:SFTPSend4j_256x256.png\|link=[[SFTPSend]]\|100px]]		\|\|[[file:SFTPSend4j_256x256.png\|link=[[SFTPSend]]\|100px]]
	====[[SFTPSend]]====		====[[SFTPSend]]====
	\|-		\|
	\|\|[[file:sftpTransfer_256x256.png\|link=[[SFTPTransfer]]\|100px]]		\|\|[[file:sftpTransfer_256x256.png\|link=[[SFTPTransfer]]\|100px]]
	====[[SFTPTransfer]]====		====[[SFTPTransfer]]====
Line 45:		Line 48:
	\|\|[[file:TreeDoc_256x256.png\|link=[[TreeDoc]]\|100px]]		\|\|[[file:TreeDoc_256x256.png\|link=[[TreeDoc]]\|100px]]
	====[[TreeDoc]]====		====[[TreeDoc]]====
	\|		\|-
	\|\|[[file:XMLViewer_256x256.png\|link=[[XMLViewer]]\|100px]]		\|\|[[file:XMLViewer_256x256.png\|link=[[XMLViewer]]\|100px]]
	====[[XMLViewer]]====		====[[XMLViewer]]====
	\|-		\|
	\|\|[[file:ZPLRenderer_256x256.png\|link=[[ZPLRenderer]]\|100px]]		\|\|[[file:ZPLRenderer_256x256.png\|link=[[ZPLRenderer]]\|100px]]
	====[[ZPLRenderer]]====		====[[ZPLRenderer]]====
	\|
	~~\|\|[[file:Modbus_256x256.png\|link=[[ModbusBridge]]\|100px]]~~
	~~====[[ModbusBridge]]====~~
	\|}		\|}

ModbusBridge

Dgarratt — Mon, 22 Jun 2026 14:00:59 GMT

Updated by push_wiki.py

Show changes

ModbusBridge

Dgarratt — Mon, 22 Jun 2026 13:44:23 GMT

Created blank page

New page

Template:Menu Applications

Dgarratt — Mon, 22 Jun 2026 13:43:47 GMT

Applications

← Older revision		Revision as of 15:43, 22 June 2026
Line 51:		Line 51:
	\|\|[[file:ZPLRenderer_256x256.png\|link=[[ZPLRenderer]]\|100px]]		\|\|[[file:ZPLRenderer_256x256.png\|link=[[ZPLRenderer]]\|100px]]
	====[[ZPLRenderer]]====		====[[ZPLRenderer]]====
			\|
			\|\|[[file:Modbus_256x256.png\|link=[[ModbusBridge]]\|100px]]
			====[[ModbusBridge]]====
	\|}		\|}

File:ModbusServer1.png

Dgarratt — Sat, 20 Jun 2026 16:04:08 GMT

Dgarratt uploaded File:ModbusServer1.png

New page

ModbusServer

Dgarratt — Sat, 20 Jun 2026 16:03:52 GMT

Connection Bar

← Older revision		Revision as of 18:03, 20 June 2026
Line 87:		Line 87:

	The '''Start / Stop''' button (the toggle at the top of the right-hand toolbar) binds and unbinds the server. The bind address, port and unit ID can only be changed while the server is stopped. The server can be stopped and started again without restarting the application, and '''all register values are kept across a stop/start''' — they are only lost when you exit the application.		The '''Start / Stop''' button (the toggle at the top of the right-hand toolbar) binds and unbinds the server. The bind address, port and unit ID can only be changed while the server is stopped. The server can be stopped and started again without restarting the application, and '''all register values are kept across a stop/start''' — they are only lost when you exit the application.

			[[File:ModbusServer1.png\|600px]]

	=== Register Table ===		=== Register Table ===

ModbusClient

Dgarratt — Sat, 20 Jun 2026 16:03:12 GMT

Connection Bar

← Older revision		Revision as of 18:03, 20 June 2026
(One intermediate revision by the same user not shown)
Line 60:		Line 60:

	The window has three parts: a '''connection bar''' across the top, the '''register table''' in the centre with a vertical button toolbar down the right-hand side, and an '''activity log''' along the bottom.		The window has three parts: a '''connection bar''' across the top, the '''register table''' in the centre with a vertical button toolbar down the right-hand side, and an '''activity log''' along the bottom.

	~~[[File:ModbusClient1.png\|600px]]~~

	=== Connection Bar ===		=== Connection Bar ===
Line 79:		Line 77:

	The '''Connect / Disconnect''' button (the toggle at the top of the right-hand toolbar) opens and closes the connection. The host, port and unit ID can only be changed while disconnected. Once connected, the client polls the server roughly four times a second and the grid updates live.		The '''Connect / Disconnect''' button (the toggle at the top of the right-hand toolbar) opens and closes the connection. The host, port and unit ID can only be changed while disconnected. Once connected, the client polls the server roughly four times a second and the grid updates live.

			[[File:ModbusClient1.png\|600px]]

	=== Register Table ===		=== Register Table ===

File:ModbusClient1.png

Dgarratt — Sat, 20 Jun 2026 16:00:19 GMT

Dgarratt uploaded File:ModbusClient1.png

New page

ModbusClient

Dgarratt — Sat, 20 Jun 2026 15:59:45 GMT

The Main Window

← Older revision		Revision as of 17:59, 20 June 2026
Line 60:		Line 60:

	The window has three parts: a '''connection bar''' across the top, the '''register table''' in the centre with a vertical button toolbar down the right-hand side, and an '''activity log''' along the bottom.		The window has three parts: a '''connection bar''' across the top, the '''register table''' in the centre with a vertical button toolbar down the right-hand side, and an '''activity log''' along the bottom.

			[[File:ModbusClient1.png\|600px]]

	=== Connection Bar ===		=== Connection Bar ===

File:JMenuTree3.png

Dgarratt — Sat, 20 Jun 2026 15:53:43 GMT

Dgarratt uploaded File:JMenuTree3.png

New page

Menu4j

Dgarratt — Sat, 20 Jun 2026 15:53:22 GMT

Settings

← Older revision		Revision as of 17:53, 20 June 2026
(2 intermediate revisions by the same user not shown)
Line 42:		Line 42:


	[[File:JMenuTree1.png\|~~400px~~]]		[[File:JMenuTree1.png\|600px]]

	=== Leaf Properties ===		=== Leaf Properties ===
Line 74:		Line 74:


	[[File:JMenuTree2.png\|~~400px~~]]		[[File:JMenuTree2.png\|600px]]

	== Executing Commands ==		== Executing Commands ==
Line 129:		Line 129:
	\| System commands \|\| Whitelist of system commands (such as <code>open</code>) that do not require a file path to be validated		\| System commands \|\| Whitelist of system commands (such as <code>open</code>) that do not require a file path to be validated
	\|}		\|}


			[[File:JMenuTree3.png\|600px]]

	== Tree Navigation ==		== Tree Navigation ==

File:JMenuTree2.png

Dgarratt — Sat, 20 Jun 2026 15:50:36 GMT

Dgarratt uploaded File:JMenuTree2.png

New page

Menu4j

Dgarratt — Sat, 20 Jun 2026 15:50:10 GMT

Leaf Properties

← Older revision		Revision as of 17:50, 20 June 2026
(One intermediate revision by the same user not shown)
Line 40:		Line 40:
	* '''Delete''' — remove the selected node		* '''Delete''' — remove the selected node
	* '''Duplicate''' — copy the selected node		* '''Duplicate''' — copy the selected node


	[[File:JMenuTree1.png\|400px]]		[[File:JMenuTree1.png\|400px]]
Line 71:		Line 72:
	\| Icon \|\| An image file to display next to the item label		\| Icon \|\| An image file to display next to the item label
	\|}		\|}


			[[File:JMenuTree2.png\|400px]]

	== Executing Commands ==		== Executing Commands ==

File:JMenuTree1.png

Dgarratt — Sat, 20 Jun 2026 15:48:44 GMT

Dgarratt uploaded File:JMenuTree1.png

New page

Menu4j

Dgarratt — Sat, 20 Jun 2026 15:48:29 GMT

Adding and Editing Items

← Older revision		Revision as of 17:48, 20 June 2026
Line 40:		Line 40:
	* '''Delete''' — remove the selected node		* '''Delete''' — remove the selected node
	* '''Duplicate''' — copy the selected node		* '''Duplicate''' — copy the selected node

			[[File:JMenuTree1.png\|400px]]

	=== Leaf Properties ===		=== Leaf Properties ===

LogoClient

Dgarratt — Sat, 13 Jun 2026 19:43:05 GMT

Updated by push_wiki.py

← Older revision		Revision as of 21:43, 13 June 2026
Line 55:		Line 55:
	=== Connecting ===		=== Connecting ===

	In the connection bar you choose the connection '''Type''' (PL3 TCP or PL6 SFTP), enter the labeller's '''host / IP address''' and '''port''', and — for PL6 — a '''username and password'''. Pressing the connect button opens the link; a status indicator shows the connected host and port. ~~A real labeller is typically reached at its own network address (for~~ example ~~<code>192.168.1.100</code>);~~ the [[LogoRenderer]] emulator is reached at <code>127.0.0.1</code>.		In the connection bar you choose the connection '''Type''' (PL3 TCP or PL6 SFTP), enter the labeller's '''host / IP address''' and '''port''', and — for PL6 — a '''username and password'''. Pressing the connect button opens the link; a status indicator shows the connected host and port. For example, the [[LogoRenderer]] emulator running on the same PC is reached at <code>127.0.0.1</code>.

	Options in the connection area let you list the remote directory automatically on connect, send a periodic '''heartbeat''' to detect a dropped link, and set the socket read timeout.		Options in the connection area let you list the remote directory automatically on connect, send a periodic '''heartbeat''' to detect a dropped link, and set the socket read timeout.
Line 94:		Line 94:
	# '''Upload a layout''', '''send field data''', '''browse the emulated drives''' or '''poll the pallet log''' — and watch LogoRenderer render the result and log the traffic.		# '''Upload a layout''', '''send field data''', '''browse the emulated drives''' or '''poll the pallet log''' — and watch LogoRenderer render the result and log the traffic.

	In this arrangement LogoClient stands in for the driving software so you can develop and test against the renderer, while LogoRenderer stands in for the printer so you have something to talk to~~. LogoClient can equally be pointed at a real Logopak labeller when one is available~~.		In this arrangement LogoClient stands in for the driving software so you can develop and test against the renderer, while LogoRenderer stands in for the printer so you have something to talk to.

	== See Also ==		== See Also ==

LogoRenderer

Dgarratt — Sat, 13 Jun 2026 19:43:03 GMT

Updated by push_wiki.py

← Older revision		Revision as of 21:43, 13 June 2026
Line 112:		Line 112:
	# From LogoClient, '''upload a layout''', '''send field data''', '''browse the emulated drives''' or '''poll the pallet log''' — and watch LogoRenderer render the result and log the traffic.		# From LogoClient, '''upload a layout''', '''send field data''', '''browse the emulated drives''' or '''poll the pallet log''' — and watch LogoRenderer render the result and log the traffic.

	In this arrangement LogoRenderer stands in for the printer so you can develop and test a client, while LogoClient stands in for the driving software so you can drive the renderer~~. Either tool can equally be pointed at a real Logopak labeller when one is available~~.		In this arrangement LogoRenderer stands in for the printer so you can develop and test a client, while LogoClient stands in for the driving software so you can drive the renderer.

	== See Also ==		== See Also ==

LogoClient

Dgarratt — Sat, 13 Jun 2026 19:41:08 GMT

Updated by push_wiki.py

← Older revision		Revision as of 21:41, 13 June 2026
Line 99:		Line 99:

	* [[LogoRenderer]] — the companion tool that renders labels and emulates a Logopak printer		* [[LogoRenderer]] — the companion tool that renders labels and emulates a Logopak printer
	* [[Middleware4j]], [[LabelServer4j]], [[AutoLab4j]] — ~~production software that drives Logopak labellers~~		* [[Middleware4j]], [[LabelServer4j]], [[AutoLab4j]] — other Commander4j components in the labelling workflow
	* [[SocketTest]] — a raw TCP/IP testing utility		* [[SocketTest]] — a raw TCP/IP testing utility

	[[Category:Commander4j]]		[[Category:Commander4j]]

LogoRenderer

Dgarratt — Sat, 13 Jun 2026 19:41:07 GMT

Updated by push_wiki.py

← Older revision		Revision as of 21:41, 13 June 2026
Line 117:		Line 117:

	* [[LogoClient]] — the client-side companion tool that sends layouts and data to a labeller (real or emulated)		* [[LogoClient]] — the client-side companion tool that sends layouts and data to a labeller (real or emulated)
	* [[Middleware4j]], [[LabelServer4j]], [[AutoLab4j]] — ~~production software that drives Logopak labellers~~		* [[Middleware4j]], [[LabelServer4j]], [[AutoLab4j]] — other Commander4j components in the labelling workflow
	* [[ZPLRenderer]] — the equivalent preview tool for Zebra ZPL labels		* [[ZPLRenderer]] — the equivalent preview tool for Zebra ZPL labels

	[[Category:Commander4j]]		[[Category:Commander4j]]

LogoClient

Dgarratt — Sat, 13 Jun 2026 19:40:36 GMT

Updated by push_wiki.py

← Older revision		Revision as of 21:40, 13 June 2026
Line 31:		Line 31:
	== Source Code and Releases ==		== Source Code and Releases ==

	LogoClient is part of the open-source Commander4j suite and is distributed under the GNU General Public License.		LogoClient is part of the open-source Commander4j suite and is distributed under the GNU General Public License. The source code and release downloads are hosted on GitHub, and native install packages for every platform are listed on the Commander4j [[Downloads]] page.

			* '''Repository:''' [https://github.com/C4J/LogoClient https://github.com/C4J/LogoClient]
			* '''Releases (download media):''' [https://github.com/C4J/LogoClient/releases https://github.com/C4J/LogoClient/releases]
			* '''All Commander4j downloads:''' [[Downloads]]

	== Installation ==		== Installation ==

LogoRenderer

Dgarratt — Sat, 13 Jun 2026 19:40:34 GMT

Updated by push_wiki.py

← Older revision		Revision as of 21:40, 13 June 2026
Line 34:		Line 34:
	== Source Code and Releases ==		== Source Code and Releases ==

	LogoRenderer is part of the open-source Commander4j suite and is distributed under the GNU General Public License.		LogoRenderer is part of the open-source Commander4j suite and is distributed under the GNU General Public License. The source code and release downloads are hosted on GitHub, and native install packages for every platform are listed on the Commander4j [[Downloads]] page.

			* '''Repository:''' [https://github.com/C4J/LogoRenderer https://github.com/C4J/LogoRenderer]
			* '''Releases (download media):''' [https://github.com/C4J/LogoRenderer/releases https://github.com/C4J/LogoRenderer/releases]
			* '''All Commander4j downloads:''' [[Downloads]]

	== Installation ==		== Installation ==

LogoClient

Dgarratt — Sat, 13 Jun 2026 19:35:33 GMT

← Older revision		Revision as of 21:35, 13 June 2026
Line 7:		Line 7:
	== Purpose ==		== Purpose ==

	Software ~~such as [[Middleware4j]], [[LabelServer4j]] and [[AutoLab4j]]~~ drives ~~Logopak~~ labellers in production. When developing or supporting that software it is useful to be able to perform the same low-level operations by hand, and to see exactly what goes across the wire. LogoClient is that tool. It is useful when:		Software from Logopak DE drives labellers in production. When developing or supporting that software it is useful to be able to perform the same low-level operations by hand, and to see exactly what goes across the wire. LogoClient is that tool. It is useful when:

	* You need to '''send a layout or data file to a labeller''' and confirm it loads correctly.		* You need to '''send a layout or data file to a labeller''' and confirm it loads correctly.

Downloads

Dgarratt — Sat, 13 Jun 2026 19:34:01 GMT

← Older revision		Revision as of 21:34, 13 June 2026
(One intermediate revision by the same user not shown)
Line 8:		Line 8:
	\|-		\|-
	\| [https://github.com/C4J?tab=repositories All Projects] \|\| Overview of all Projects		\| [https://github.com/C4J?tab=repositories All Projects] \|\| Overview of all Projects
			\|-
			\| [https://github.com/C4J/Commander4j-AutoLab/releases AutoLab4j] \|\| Automatic Label Application triggered by MODBUS
	\|-		\|-
	\| [https://github.com/C4J/Commander4j/releases Commander4j] \|\| Commander4j Core Application		\| [https://github.com/C4J/Commander4j/releases Commander4j] \|\| Commander4j Core Application
	\|-		\|-
	\| [https://github.com/C4J/Commander4j-~~Middleware~~/releases ~~Middleware4j~~] \|\| ~~Middleware for message translation~~ to ~~external systems~~		\| [https://github.com/C4J/Commander4j-LabelServer/releases LabelServer4j] \|\| Service to send Label Data to Labellers
	\|-		\|-
	\| [https://github.com/C4J/~~Commander4j-AutoLab~~/releases ~~AutoLab4j~~] \|\| ~~Automatic Label Application triggered by MODBUS~~		\| [https://github.com/C4J/LaunchPad/releases LaunchPad] \|\| Menu system for Macos to replicate Launchpad
	\|-		\|-
	\| [https://github.com/C4J/~~Commander4j-LabelServer~~/releases ~~LabelServer4j~~] \|\| ~~Service to send Label Data to Labellers~~		\| [https://github.com/C4J/LogoClient/releases LogoClient] \|\| Client for communication with LogoRenderer
	\|-		\|-
	\| [https://github.com/C4J/~~sftpTransfer~~/releases ~~SFTP-Transfer~~] \|\| ~~SFTP Send~~ and ~~Receive Automatically~~.		\| [https://github.com/C4J/LogoRenderer/releases LogoRenderer] \|\| Interpret and view Logopak templates.
	\|-		\|-
	\| [https://github.com/C4J/~~sftpSend~~/releases ~~SFTP Send~~] \|\| ~~Utility to send files automatically via SFTP~~		\| [https://github.com/C4J/Menu4j/releases Menu4j] \|\| Java Menu (tree) for launching applications and scripts
	\|-		\|-
	\| [https://github.com/C4J/~~sftpGet~~/releases ~~SFTP Get~~] \|\| ~~Utility~~ to ~~collect files automatically via SFTP~~		\| [https://github.com/C4J/Commander4j-Middleware/releases Middleware4j] \|\| Middleware for message translation to external systems
	\|-		\|-
	\| [https://github.com/C4J/~~Menu4j~~/releases ~~Menu4j~~] \|\| ~~Java Menu (tree) for launching applications and scripts~~		\| [https://github.com/C4J/ModbusClient/releases Modbus Client] \|\| Modbus Client
	\|-		\|-
	\| [https://github.com/C4J/~~SocketTest~~/releases ~~SocketTest~~] \|\| ~~TCP/IP Client for device comms and debugging~~		\| [https://github.com/C4J/ModbusServer/releases Modbus Server] \|\| Modbus Server
	\|-		\|-
	\| [https://github.com/C4J/~~ZPL-Renderer~~/releases ~~ZPL-Renderer~~] \|\| ~~Emulates a Zebra ZPL labeller.~~		\| [https://github.com/C4J/sftpGet/releases SFTP Get] \|\| Utility to collect files automatically via SFTP
	\|-		\|-
	\| [https://github.com/C4J/~~XML-Viewer~~/releases ~~XML-Viewer~~] \|\| Utility ~~for viewing XML documents~~		\| [https://github.com/C4J/sftpSend/releases SFTP Send] \|\| Utility to send files automatically via SFTP
	\|-		\|-
	\| [https://github.com/C4J/~~ModbusServer~~/releases ~~Modbus Server~~] \|\| ~~Modbus Server~~		\| [https://github.com/C4J/sftpTransfer/releases SFTP-Transfer] \|\| SFTP Send and Receive Automatically.
	\|-		\|-
	\| [https://github.com/C4J/~~ModbusClient~~/releases ~~Modbus Client~~] \|\| ~~Modbus~~ Client		\| [https://github.com/C4J/SocketTest/releases SocketTest] \|\| TCP/IP Client for device comms and debugging
	\|-		\|-
	\| [https://github.com/C4J/TreeDoc/releases TreeDoc] \|\| Easy way to create a document for directory structure		\| [https://github.com/C4J/TreeDoc/releases TreeDoc] \|\| Easy way to create a document for directory structure
	\|-		\|-
	\| [https://github.com/C4J/~~LaunchPad~~/releases ~~LaunchPad~~] \|\| ~~Menu system~~ for ~~Macos to replicate Launchpad~~		\| [https://github.com/C4J/XML-Viewer/releases XML-Viewer] \|\| Utility for viewing XML documents
			\|-
			\| [https://github.com/C4J/ZPL-Renderer/releases ZPL-Renderer] \|\| Emulates a Zebra ZPL labeller.
	\|}		\|}

LogoRenderer

Dgarratt — Sat, 13 Jun 2026 19:28:23 GMT

← Older revision		Revision as of 21:28, 13 June 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	== Purpose ==		== Purpose ==

	A Logopak PowerLeap labeller normally lives on the factory floor and is driven over the network by software ~~such as [[Middleware4j]], [[LabelServer4j]] or [[AutoLab4j]]~~. When developing or supporting that software — or designing the label layouts themselves — it is often impractical to have a real labeller on the bench. LogoRenderer removes that dependency. It is useful when:		A Logopak PowerLeap labeller normally lives on the factory floor and is driven over the network by software provided by Logopak DE. When developing or supporting that software — or designing the label layouts themselves — it is often impractical to have a real labeller on the bench. LogoRenderer removes that dependency. It is useful when:

	* You need to '''see what a label layout will look like''' without printing it, by opening a <code>.llf</code>, <code>.lqf</code> or <code>.ldf</code> file and viewing a faithful preview.		* You need to '''see what a label layout will look like''' without printing it, by opening a <code>.llf</code>, <code>.lqf</code> or <code>.ldf</code> file and viewing a faithful preview.
Line 47:		Line 47:
	java -jar c4j_logorenderer.jar [file.llf]		java -jar c4j_logorenderer.jar [file.llf]

	Running the jar requires a recent Java runtime (Java 21 or later). If a layout file is supplied on the command line it is opened on start-up; otherwise the application starts with an empty canvas. Demo layouts and data files are provided in the <code>virtual_disk/c0/</code> folder.		Running the jar requires a recent Java runtime (Java 25 or later). If a layout file is supplied on the command line it is opened on start-up; otherwise the application starts with an empty canvas. Demo layouts and data files are provided in the <code>virtual_disk/c0/</code> folder.

	== The Main Window ==		== The Main Window ==

LogoClient

Dgarratt — Sat, 13 Jun 2026 19:23:13 GMT

Updated by push_wiki.py

New page

'''LogoClient''' (''c4j_logoclient'') is a standalone desktop application — and underlying client library — for communicating with [[Logopak]] PowerLeap label printers over the network. It connects to a labeller, transfers layout and data files to and from it, sends commands and field data, browses the printer's on-board storage and retrieves its logs. It exists so that the software-to-labeller conversation can be developed, exercised and diagnosed '''on an ordinary PC, in environments where no physical Logopak labeller is available''' to test against.

It is the client half of a pair: where a real labeller is not to hand, [[LogoRenderer]] can emulate one, and LogoClient talks to that emulator exactly as it would talk to real hardware. Together they let you exercise the whole label-printing workflow with no hardware at all.

''Disclaimer: LogoClient is an independent open-source tool and is '''not''' a Logopak product. It is not affiliated with, endorsed by, or supported by Logopak. Logopak, PowerLeap and related names are trademarks of their respective owners and are used solely to describe interoperability. The software is intended for local test and development use only — it must not be relied upon for production label printing.''

== Purpose ==

Software such as [[Middleware4j]], [[LabelServer4j]] and [[AutoLab4j]] drives Logopak labellers in production. When developing or supporting that software it is useful to be able to perform the same low-level operations by hand, and to see exactly what goes across the wire. LogoClient is that tool. It is useful when:

* You need to '''send a layout or data file to a labeller''' and confirm it loads correctly.
* You want to '''browse, upload, download or delete files''' on the printer's on-board drives.
* You are '''debugging the protocol''' and want a live, byte-level trace of everything sent and received.
* You need to '''send raw commands or field data''' to a labeller and read its replies.
* You want to '''poll a labeller's pallet log''' and capture one file per SSCC as labels are applied.
* You want to '''develop without a physical Logopak''' by pointing LogoClient at the [[LogoRenderer]] printer emulator instead of real hardware.

== Supported Printers and Protocols ==

LogoClient supports both current Logopak controller generations:

{| class="wikitable"
|-
! Mode !! Hardware !! Transport
|-
| '''PL3 (TCP)''' || PowerLeap III || Direct TCP socket on the data ports (8000 / 8100 / 8200 / 8300). Carries the full LEAP, LAMA/LACE and LSP command set — layout activation, field data, firmware queries, file management, I/O monitoring and asynchronous reporting.
|-
| '''PL6 (SFTP)''' || PowerLeap 6 || File transfer over SFTP (port 22). PL6 is driven by exchanging files rather than TCP commands, so this mode is focused on uploading, downloading and listing files and reading the pallet log.
|}

== Source Code and Releases ==

LogoClient is part of the open-source Commander4j suite and is distributed under the GNU General Public License.

== Installation ==

Native install packages for '''Windows, macOS and Linux''' are available from the [[Downloads]] page and are the preferred installation method. Each installer bundles its own Java runtime, so '''no separate Java installation is required'''. Installing creates a native '''LogoClient''' launcher that can be started like any other desktop application.

=== Running from the jar ===

Alternatively the tool can be run directly as an ordinary Java (Swing) application:

java -jar c4j_logoclient.jar

Running the jar requires a recent Java runtime (Java 21 or later). The bundled JSch library is required only for PL6 (SFTP); PL3 (TCP) has no external dependencies.

== The Main Window ==

The window has a '''connection bar''' across the top, a central '''file-transfer and directory area''', a '''message pane''' for composing raw commands, and a pair of log panes along the bottom — an '''activity log''' and a '''wire trace'''. All transfer and command actions are disabled until a connection is open.

=== Connecting ===

In the connection bar you choose the connection '''Type''' (PL3 TCP or PL6 SFTP), enter the labeller's '''host / IP address''' and '''port''', and — for PL6 — a '''username and password'''. Pressing the connect button opens the link; a status indicator shows the connected host and port. A real labeller is typically reached at its own network address (for example <code>192.168.1.100</code>); the [[LogoRenderer]] emulator is reached at <code>127.0.0.1</code>.

Options in the connection area let you list the remote directory automatically on connect, send a periodic '''heartbeat''' to detect a dropped link, and set the socket read timeout.

=== Transferring and Managing Files ===

The central area lists the files on the printer for a chosen remote path and file mask, showing each file's name, size, modified time and type. From here you can:

* '''Upload''' a local file to the printer.
* '''Download''' one or more selected files to a chosen local folder.
* '''Delete''' selected files from the printer (with confirmation).
* '''Refresh''' the listing, and on PL6 navigate into sub-folders.

PL3 exposes the printer's storage areas (<code>/c0/</code>, <code>/c9/</code>, <code>/f0/</code>, <code>/r0/</code>) with file masks such as <code>*.llf</code> or <code>*.pcx</code>; PL6 exposes its SFTP folders.

=== Sending Commands and Field Data ===

In PL3 mode the message pane composes and transmits raw text to the labeller. Control characters can be entered as readable tokens such as <code><STX></code>, <code><ETX></code> and <code><CR></code>, and the end-of-line terminator appended on send is selectable. This is how layouts are activated, field data is sent, and LAMA/LSP queries are issued by hand. Replies appear in the activity log and the raw bytes in the wire trace.

=== Pallet Log Polling ===

LogoClient can poll the labeller's pallet log at a chosen interval and write the results to disk — one timestamped file per unique SSCC — into a chosen log folder. This reproduces, by hand, the "what was printed" feedback that production software collects, and works against both PL3 and PL6.

=== Activity Log and Wire Trace ===

Two panes record what happens. The '''activity log''' is a readable, timestamped narrative of connects, transfers, commands and errors. The '''wire trace''' shows the raw bytes in both directions — transmitted and received — with control characters rendered as tokens, which is invaluable when diagnosing exactly what a labeller sent or expected. Both panes can be saved to a text file or cleared.

== Configuration ==

The connection details and interface preferences are saved when you quit and restored on the next start, so the tool reopens ready to reconnect to the labeller you last used.

== Using LogoClient and LogoRenderer Together ==

The two tools form a complete bench setup for label development with no Logopak hardware:

# In '''[[LogoRenderer]]''', start the '''printer emulator''' on a port (default 8000).
# In '''LogoClient''', choose '''PL3 (TCP)''', set the host to <code>127.0.0.1</code> and the matching port, and connect.
# '''Upload a layout''', '''send field data''', '''browse the emulated drives''' or '''poll the pallet log''' — and watch LogoRenderer render the result and log the traffic.

In this arrangement LogoClient stands in for the driving software so you can develop and test against the renderer, while LogoRenderer stands in for the printer so you have something to talk to. LogoClient can equally be pointed at a real Logopak labeller when one is available.

== See Also ==

* [[LogoRenderer]] — the companion tool that renders labels and emulates a Logopak printer
* [[Middleware4j]], [[LabelServer4j]], [[AutoLab4j]] — production software that drives Logopak labellers
* [[SocketTest]] — a raw TCP/IP testing utility

[[Category:Commander4j]]

LogoRenderer

Dgarratt — Sat, 13 Jun 2026 19:23:10 GMT

Updated by push_wiki.py

New page

'''LogoRenderer''' (''c4j_logorenderer'') is a standalone desktop application that renders [[Logopak]] PowerLeap label layout files to a visual on-screen preview '''and''' can stand in for a physical label printer by emulating its TCP communication protocol. It exists so that label layouts and the software that drives them can be developed and tested '''on an ordinary PC, in environments where no physical Logopak labeller is available''' to test against.

It is the rendering and printer-emulation half of a pair: [[LogoClient]] is the client that sends layouts and data to a printer, and LogoRenderer can play the part of that printer. Together they let you exercise the whole label-printing workflow with no hardware at all.

''Disclaimer: LogoRenderer is an independent open-source tool and is '''not''' a Logopak product. It is not affiliated with, endorsed by, or supported by Logopak. Logopak, PowerLeap and related names are trademarks of their respective owners and are used solely to describe interoperability. The software is intended for local test and development use only — it must not be relied upon for production label printing.''

== Purpose ==

A Logopak PowerLeap labeller normally lives on the factory floor and is driven over the network by software such as [[Middleware4j]], [[LabelServer4j]] or [[AutoLab4j]]. When developing or supporting that software — or designing the label layouts themselves — it is often impractical to have a real labeller on the bench. LogoRenderer removes that dependency. It is useful when:

* You need to '''see what a label layout will look like''' without printing it, by opening a <code>.llf</code>, <code>.lqf</code> or <code>.ldf</code> file and viewing a faithful preview.
* You are '''writing or debugging software that talks to a labeller''' and need something on the network that answers the same protocol — without owning the hardware.
* You want to '''develop without a physical Logopak''' altogether: render layouts, emulate the printer, and feed it from [[LogoClient]] or your own client code.
* You need to '''check field data and operator prompts''' (LQF query fields) by typing values and watching the rendered label update.
* You are '''tuning fonts''' so the on-screen rendering matches a real printed label.

== Label and Data File Types ==

LogoRenderer understands the PowerLeap LEAP layout family:

{| class="wikitable"
|-
! Extension !! Description
|-
| <code>.llf</code> || Layout File — a complete label layout with all field data embedded. Opening one renders the label immediately.
|-
| <code>.lqf</code> || Query Layout File — a base layout containing <code>QUE</code> operator prompts for fields that are filled in at print time. Opening one also populates the '''QUE Input''' tab so values can be typed in.
|-
| <code>.ldf</code> || Data File — a data-only file that references a master layout. Opening one runs its <code>LOAD</code> and <code>FD</code> commands to load the referenced layout and populate its fields.
|}

Layouts may reference <code>.pcx</code> and <code>.bmp</code> images (logotypes) and a range of barcode types. A reference list of the wider Logopak file-type ecosystem is maintained alongside the project.

== Source Code and Releases ==

LogoRenderer is part of the open-source Commander4j suite and is distributed under the GNU General Public License.

== Installation ==

Native install packages for '''Windows, macOS and Linux''' are available from the [[Downloads]] page and are the preferred installation method. Each installer bundles its own Java runtime, so '''no separate Java installation is required'''. Installing creates a native '''LogoRenderer''' launcher that can be started like any other desktop application.

=== Running from the jar ===

Alternatively the tool can be run directly as an ordinary Java (Swing) application. It is built with Maven:

mvn package
java -jar c4j_logorenderer.jar [file.llf]

Running the jar requires a recent Java runtime (Java 21 or later). If a layout file is supplied on the command line it is opened on start-up; otherwise the application starts with an empty canvas. Demo layouts and data files are provided in the <code>virtual_disk/c0/</code> folder.

== The Main Window ==

The window is divided into a '''label preview canvas''' on the left and a '''tabbed working area''' on the right, with a menu bar and toolbars around them and a status bar along the bottom. The title bar shows the program name, version and the name of the open file.

The status bar reports the current file, the layout dimensions in printer dots and millimetres, the zoom level, and the number of fields in the layout.

=== Preview Canvas ===

The canvas shows the rendered label exactly as the layout describes it — text, scalable text, barcodes, graphic lines and boxes, and embedded logotype images. The rendering engine replicates the coordinate system and geometry of a PowerLeap III print head, including the upside-down (180°) print orientation. Clicking a rendered element highlights the source lines that produce it.

=== Source / QUE Input / Log Tabs ===

{| class="wikitable"
|-
! Tab !! Purpose
|-
| '''Source''' || Lists the raw layout commands, one per line, each with a checkbox and a plain-language description. Un-checking a line excludes it from the render, so individual elements can be toggled on and off. Selecting a line shows its properties for editing.
|-
| '''QUE Input''' || For LQF layouts, presents one input box per operator prompt. Type values and apply them to see the populated label. This mirrors what an operator would be asked for at the machine.
|-
| '''Log''' || A colour-coded activity log showing file loads, parser messages, and all traffic to and from the printer emulator.
|}

=== Viewing Controls ===

The '''File''' menu opens and reloads layout files and exports the rendered label as a PNG image. The '''View''' menu provides zoom (preset levels, zoom in/out, and fit-to-window) and a '''Rotate 180°''' toggle that flips the preview to match the printer's print orientation.

== Font Mapping ==

Because Logopak fonts are not present on a development PC, LogoRenderer maps each Logopak font name to a Java font for rendering. The '''Settings → Font Mappings''' dialog lists every mapping and lets you set the Java font family (or a bundled TrueType file), style, reference cell size and calibration factors so that the on-screen text closely matches a real printed label. The mappings are stored in <code>xml/config/fonts.xml</code>; fonts found in a layout but not yet mapped are added automatically with sensible defaults, ready to be fine-tuned.

== The Printer Emulator ==

This is the feature that makes hardware-free development possible. LogoRenderer can open a TCP server that emulates a Logopak PowerLeap III labeller, answering the same '''LEAP / LAMA''' protocol commands a real machine would.

=== Starting the emulator ===

The connection bar at the top of the window selects the '''IP address''' (default <code>127.0.0.1</code> for the local machine) and '''port''' (default '''8000''', the PowerLeap III primary data port; <code>8100</code>, <code>8200</code> and <code>8300</code> are also offered). Pressing '''Start Server''' begins listening; the Log tab shows when a client connects. Pressing the button again stops the server.

=== What it emulates ===

A connected client can do, against the emulator, the things it would do against a real labeller:

* '''Browse and transfer files''' on an emulated drive — the <code>virtual_disk/</code> folder provides the labeller's storage areas (<code>c0/</code>, <code>c9/</code>, <code>d0/</code>, <code>f0/</code>, <code>r0/</code>), so directory listings, downloads, uploads and deletes all behave realistically.
* '''Load a layout and send field data''' — when the client issues a <code>LOAD</code> command the emulator loads that layout into the preview, and as <code>FD</code> field-data commands arrive the on-screen label updates. The PC screen therefore shows what the real printer would be putting on a label.
* '''Retrieve logs''' — the emulator can serve pallet/label log files back to the client, so software that polls a labeller for "what was printed" can be tested end to end.

=== Pallet print simulation ===

When a loaded layout contains the pallet SSCC field, a '''Print Label''' control appears. Each press simulates a pallet print — two labels per pallet sharing one [https://en.wikipedia.org/wiki/Serial_Shipping_Container_Code SSCC] — increments the SSCC counter (persisted in <code>sscc.dat</code>), and queues a log entry that a client can later retrieve. This lets log-polling and pallet-tracking logic be exercised without a real production run.

== Using LogoRenderer and LogoClient Together ==

The two tools form a complete bench setup for label development with no Logopak hardware:

# In '''LogoRenderer''', start the '''printer emulator''' on a port (default 8000).
# In '''[[LogoClient]]''', connect in '''PL3 (TCP)''' mode to <code>127.0.0.1</code> on the same port.
# From LogoClient, '''upload a layout''', '''send field data''', '''browse the emulated drives''' or '''poll the pallet log''' — and watch LogoRenderer render the result and log the traffic.

In this arrangement LogoRenderer stands in for the printer so you can develop and test a client, while LogoClient stands in for the driving software so you can drive the renderer. Either tool can equally be pointed at a real Logopak labeller when one is available.

== See Also ==

* [[LogoClient]] — the client-side companion tool that sends layouts and data to a labeller (real or emulated)
* [[Middleware4j]], [[LabelServer4j]], [[AutoLab4j]] — production software that drives Logopak labellers
* [[ZPLRenderer]] — the equivalent preview tool for Zebra ZPL labels

[[Category:Commander4j]]

File:LogoRenderer 256x256.png

Dgarratt — Sat, 13 Jun 2026 12:36:10 GMT

Dgarratt uploaded File:LogoRenderer 256x256.png

New page

File:LogoClient 256x256.png

Dgarratt — Sat, 13 Jun 2026 12:35:42 GMT

Dgarratt uploaded File:LogoClient 256x256.png

New page

Template:Menu Applications

Dgarratt — Sat, 13 Jun 2026 12:35:26 GMT

Applications

← Older revision		Revision as of 14:35, 13 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	=Applications=		=Applications=

	{\| cellpadding="8" style="text-align:center"		{\| cellpadding="8" style="text-align:center"
			\|\|[[file:AutoLab4j_256x256.png\|link=[[AutoLab4j]]\|100px]]
			====[[AutoLab4j]]====
			\|
	\|\|[[File:Commander4j_256x256.png\|link=[[Commander4j]]\|100px]]		\|\|[[File:Commander4j_256x256.png\|link=[[Commander4j]]\|100px]]
	====[[Commander4j]]====		====[[Commander4j]]====
	\|
	~~\|\|[[file:Middleware4j_256x256.png\|link=[[Middleware4j]]\|100px]]~~
	~~====[[Middleware4j]]====~~
	\|
	~~\|\|[[file:AutoLab4j_256x256.png\|link=[[AutoLab4j]]\|100px]]~~
	~~====[[AutoLab4j]]====~~
	\|		\|
	\|\|[[file:LabelServer4j_256x256.png\|link=[[LabelServer4j]]\|100px]]		\|\|[[file:LabelServer4j_256x256.png\|link=[[LabelServer4j]]\|100px]]
	====[[LabelServer4j]]====		====[[LabelServer4j]]====
			\|
			\|\|[[file:LaunchPad_256x256.png\|link=[[LaunchPad]]\|100px]]
			====[[LaunchPad]]====
	\|-		\|-
			\|\|[[file:LogoClient_256x256.png\|link=[[LogoClient]]\|100px]]
			====[[LogoClient]]====
			\|
			\|\|[[file:LogoRenderer_256x256.png\|link=[[LogoRenderer]]\|100px]]
			====[[LogoRenderer]]====
			\|
	\|\|[[file:Menu4j_256x256.png\|link=[[Menu4j]]\|100px]]		\|\|[[file:Menu4j_256x256.png\|link=[[Menu4j]]\|100px]]
	====[[Menu4j]]====		====[[Menu4j]]====
	\|		\|
	\|\|[[file:~~sftpTransfer_256x256~~.png\|link=[[~~SFTPTransfer~~]]\|100px]]		\|\|[[file:Middleware4j_256x256.png\|link=[[Middleware4j]]\|100px]]
	====[[~~SFTPTransfer]]====~~		====[[Middleware4j]]====
	\|
	~~\|\|[[file:ZPLRenderer_256x256.png\|link=[[ZPLRenderer]]\|100px]]~~
	~~====[[ZPLRenderer]]====~~
	\|
	~~\|\|[[file:SocketTest_256x256.png\|link=[[SocketTest]]\|100px]]~~
	~~====[[SocketTest~~]]====
	\|-		\|-
	\|\|[[file:~~TreeDoc_256x256~~.png\|link=[[~~TreeDoc~~]]\|100px]]		\|\|[[file:Modbus_256x256.png\|link=[[ModbusClient]]\|100px]]
	====[[~~TreeDoc~~]]====		====[[ModbusClient]]====
	\|		\|
	\|\|[[file:~~LaunchPad_256x256~~.png\|link=[[~~LaunchPad~~]]\|100px]]		\|\|[[file:Modbus_256x256.png\|link=[[ModbusServer]]\|100px]]
	====[[~~LaunchPad~~]]====		====[[ModbusServer]]====
	\|		\|
	\|\|[[file:SFTGet4j_256x256.png\|link=[[SFTPGet]]\|100px]]		\|\|[[file:SFTGet4j_256x256.png\|link=[[SFTPGet]]\|100px]]
Line 38:		Line 37:
	====[[SFTPSend]]====		====[[SFTPSend]]====
	\|-		\|-
			\|\|[[file:sftpTransfer_256x256.png\|link=[[SFTPTransfer]]\|100px]]
			====[[SFTPTransfer]]====
			\|
			\|\|[[file:SocketTest_256x256.png\|link=[[SocketTest]]\|100px]]
			====[[SocketTest]]====
			\|
			\|\|[[file:TreeDoc_256x256.png\|link=[[TreeDoc]]\|100px]]
			====[[TreeDoc]]====
			\|
	\|\|[[file:XMLViewer_256x256.png\|link=[[XMLViewer]]\|100px]]		\|\|[[file:XMLViewer_256x256.png\|link=[[XMLViewer]]\|100px]]
	====[[XMLViewer]]====		====[[XMLViewer]]====
	\|		\|-
	\|\|[[file:~~Modbus_256x256~~.png\|link=[[~~ModbusServer~~]]\|100px]]		\|\|[[file:ZPLRenderer_256x256.png\|link=[[ZPLRenderer]]\|100px]]
	====[[~~ModbusServer]]====~~		====[[ZPLRenderer]]====
	\|
	~~\|\|[[file:Modbus_256x256.png\|link=[[ModbusClient]]\|100px]]~~
	~~====[[ModbusClient~~]]====
	\|}		\|}

Installation

Dgarratt — Wed, 10 Jun 2026 16:50:00 GMT

← Older revision		Revision as of 18:50, 10 June 2026
Line 50:		Line 50:
	== Install Java ==		== Install Java ==

	* Java 21 is needed if you are installing:		* Java 25 is needed if you are installing:
	** The desktop application on a Linux operating system.		** The desktop application on a Linux operating system.
	** The web components onto a server using Apache Tomcat.		** The web components onto a server using Apache Tomcat.

Web Applications Overview

Dgarratt — Wed, 10 Jun 2026 16:49:34 GMT

← Older revision		Revision as of 18:49, 10 June 2026
Line 64:		Line 64:

	* Apache Tomcat 11.x		* Apache Tomcat 11.x
	* Java 21		* Java 25
	* A configured and accessible Commander4j database (MySQL, MS SQL Server, or Oracle)		* A configured and accessible Commander4j database (MySQL, MS SQL Server, or Oracle)
	* A valid '''hosts.xml''' deployed with each WAR		* A valid '''hosts.xml''' deployed with each WAR

Menu4j

Dgarratt — Wed, 10 Jun 2026 16:49:12 GMT

← Older revision		Revision as of 18:49, 10 June 2026
Line 9:		Line 9:
	Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

	Alternatively, Menu4j can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:		Alternatively, Menu4j can be run directly from the distribution archive. It is a Java 25 desktop (Swing) application:

	java -jar JMenu.jar		java -jar JMenu.jar

XML Viewer

Dgarratt — Wed, 10 Jun 2026 16:48:56 GMT

← Older revision		Revision as of 18:48, 10 June 2026
Line 9:		Line 9:
	Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

	Alternatively, XML Viewer can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:		Alternatively, XML Viewer can be run directly from the distribution archive. It is a Java 25 desktop (Swing) application:

	java -jar xmlviewer.jar [optional path to XML file]		java -jar xmlviewer.jar [optional path to XML file]

TreeDoc

Dgarratt — Wed, 10 Jun 2026 16:48:39 GMT

← Older revision		Revision as of 18:48, 10 June 2026
Line 9:		Line 9:
	Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

	Alternatively, TreeDoc can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:		Alternatively, TreeDoc can be run directly from the distribution archive. It is a Java 25 desktop (Swing) application:

	java -jar Tree.jar		java -jar Tree.jar

Getting Started

Dgarratt — Wed, 10 Jun 2026 16:48:19 GMT

← Older revision		Revision as of 18:48, 10 June 2026
Line 7:		Line 7:
	* A supported operating system (Windows 10/11, macOS, or Linux)		* A supported operating system (Windows 10/11, macOS, or Linux)
	* A supported database (MySQL, MariaDB, MS SQL Server, or Oracle) installed and accessible		* A supported database (MySQL, MariaDB, MS SQL Server, or Oracle) installed and accessible
	* Java 21 (included in the Windows ~~installer~~; required separately on Linux)		* Java 25 (included in the Windows & Mac installers; required separately on Linux)

	For shop-floor scanner access you will also need Apache Tomcat 11.x. See [[Requirements]] for the full list.		For shop-floor scanner access you will also need Apache Tomcat 11.x. See [[Requirements]] for the full list.

Installation Middleware4j

Dgarratt — Wed, 10 Jun 2026 16:47:48 GMT

← Older revision		Revision as of 18:47, 10 June 2026
Line 7:		Line 7:
	* If using the SOCKET connector: network access to the target TCP/IP device		* If using the SOCKET connector: network access to the target TCP/IP device
	* Windows, Linux, or macOS		* Windows, Linux, or macOS
	* Java 21 — required only when running from the distribution archive; the native install package bundles its own Java runtime		* Java 25 — required only when running from the distribution archive; the native install package bundles its own Java runtime

	== Installation ==		== Installation ==