All provided demo files can be loaded into any ASCII editor, like Notepad or better Notepad++. However, as the file contains PCL5 Printer Commands, they CANNOT be printed from of a Windows application. They need to be sent directly to the printer or to a printer queue! The Admin Tab and Install Tab  both offer ways to test and reprint captured data streams.

A_SIMPLE_ELP_TEST.PCL This is usually the file for testing, If a  queue was successfully activated. If the printed document shows bar codes then everything is fine. 
Barcode_1D.pcl * Prints a huge list of bar code samples. Bar codes with ELP 
Barcode_2D.pcl * Prints an ELP Demo Page of all implemented 2D Barcodes
Barcode_Overview.pcl * Prints samples of bar codes and explains how they can be setup and configured
Barcode_Kyocera.pcl Prints some bar code samples in Kyocera Emulation, note, that emulation needs to be enabled!
ELPStatusPage.pcl Prints a ELP Demo Page and gives some information about error logging.
Invoice.pcl Prints en example of how invoices can be duplicate with watermarks etc.
LetterHead.pcl This Demo Page demonstrates how to print automatically forms, using ELP command in the data stream
PCL Macro Call.pcl This Demo Page demonstrates how ELP can replace a printer Flash Memory or hard disk for forms and/or font management, right away, without any changes to the PCL macro commands.

This example demonstrates how to print automatically forms, using an ELP_Command, which is triggered by some information found in the data stream.

chineseSimplified_Korean.pcl ¹ Demo page printing simplified Chinese characters in double byte mode.
chinese_traditional.pcl ¹ Demo page printing traditional Chinese characters in double byte mode.
SAP_Unicode.pcl ¹ A sample page with print samples in a lot of languages
Unicode_Internal_Fonts.pcl ¹ Print samples of  fonts build into the HP LaserJets in quite a number of languages. 

¹ Those files can be viewed and edited with Notepad++ 
$ Needs to have the ELP Unicode fonts installed, mainly used for SAP international printing

Hint: Capturing data streams for testing and reprinting can be done using the debug functions of W-ELP and is described in the chapter Need help? It is suggested for implementers to copy the captured files, or spool files out of the windows\system32\spooler\printers directory in the W-ELP directory for 2 reasons:

  • You have comparable print files, which just may help in the future if suddenly something does not work, and you can prove that the system was changed.
  • You can use this test function for fast reprinting without the need of an Admin or User.

In the Workpath folder (default: c:\ProgramData\Welp) several ini files can be found, they provide examples for:


Example how to print on every printed page the proper watermark / company letter head etc. depending upon page size and orientation. The forms must be generated and are not part of the demo.

Example.ini Configuration file for some provided examples.
Invoice.ini Configuration file for some provided examples.
Trigger.ini Configuration file for some provided examples.


Note: The original convert.ini file is located as a copy in the folder c:\ProgramData\Welp named convert.ori