INTERMEC Printing Resource Kit V4.00

  README.HTM

© 2004 - 2014 INTERMEC TECHNOLOGIES CORPORATION, ALL RIGHTS RESERVED

 

Contents

NEW FEATURES

VERSION HISTORY

REQUIREMENTS

KNOWN ISSUES

TIPS

UNDOCUMENTED FEATURES

REQUIREMENTS

 

NOTE:

An error can occur when you try to install Intermec software (such as IDL Resource Kits) using an invalid version of agent.exe. Agent.exe is part of Intermec's 3rd-party software update system called FLEXnet Connect – more commonly known as Intermec Update. Several Intermec Software components utilize FLEXnet Connect, such as SmartSystems, All IDL Resource Kits and Toolkits, DEX Toolkit and Verdex. This error may also occur if any 3rd party software utilizing version newer than v6 of FLEXnet Connect has been installed on your system.  .  If you encounter an error similar to: “"The file 'agent.exe.4747EFCD_A8CE_4016_80F6_BCAD9FE72' is not marked for installation." please contact Product Support or Developer Support.

 

Printing Resource Kit
VERSION 4.00 NEW FEATURES

1.    Removed most deprecated functionality. 
(If you need this deprecated functionality, such as the ActiveX control for the 700 series, or support for VS2005, please continue to use version 3.71)

2.    Added support for CV31.  (See Known Issues below.)

VERSION HISTORY

Ver #

Description

3.71

1.   Added support for PR2 and PR3 IrDA printers.

 

3.70

1.      Added support for CV61.

2.      Added support for PR2 and PR3 WiFi printers.

3.      Added new SOCKET transport type.  Allows more versatile and robust communications with WiFi, Bluetooth, and IrDA printers.

4.      Added additional parameter usage to Open, GetConfiguration, and GetStatus methods to make switching printers programmatically much easier when using the new SOCKET transport type.  (See Known Issues below.)

 

3.60

  1. Added support for new PR2 and PR3 Intermec Bluetooth printers.
  2. Added GetStatus function for retrieving current printer status from PR2 and PR3 printers.
  3. Added GetConfiguration function for retrieving current printer configuration from PR2 and PR3 printers.
  4. Added ability to get on the fly printer status while the printer communication channel is open from PR2 and PR3 printers.
  5. Added optional parameter to Newline function for advancing multiple new lines in one command.
  6. Added WriteLn functions to facilitate writing to the printer with an automatic Newline call at the end of the write.
  7. Added additional optional parameters to Open function to allow overriding the IP address and port when opening an IP connection.
  8. Added new example program, Example3 to demonstrate new features.
  9. Updated tutorial in User’s Guide.
  10. Updated the Java library to provide similar support described in number points 1 to 7 above.
  11. Updated the Java PrintReceiptSample to demonstrate new features such as querying the printer for the printer status and configuration.
  12. Added CV41 support.

 

3.52

1.      Intermec Update Install Patch

 

3.51

1.      Modified appearance of CF3.5 sample program to better fit additional screen resolutions.

2.      Fixed CompressOff to do nothing and return 0 if CompressOn is not supported on a printer.

3.      Fixed PB2 and PB3 graphics printing issue in the Java LinePrinter.bitmap method.

 

3.50

  1. Added new Compact Framework and Full Framework LinePrinter assemblies.

The LinePrinter assembly has been upgraded to Compact Framework 3.5 for use within Visual Studio 2008.
The LinePrinter assembly has been upgraded to the Full Framework 3.5 for use within Visual Studio 2008.

  1. LinePrinter assembly icons will now show up in the VS2008 toolbox.

The LinePrinter assemblies are now drag and drop compatible with Visual Studio 2008 and available in the Visual Studio 2008 toolbox.

  1. Added 2 new example programs for use with VS2008. 

The old Example1 C# example program has been given a new look and feel and updated for use with Visual Studio 2008.  Two new forms of the example project exist. One for Compact Framework version 3.5 and the other for the Full Framework version 3.5.

  1. Added support for the new 2” and 3” Intermec mobile printers.

New entries have been added in the ITC_CONFIG.xml sample configuration file for the new Intermec PB21 and PB22 2” mobile printers and the Intermec PB31 and PB32 3” mobile printers.

  1. Added PB2 and PB3 serial printer entries into sample ITC_CONFIG.xml file.

Added entries for those that may want to communicate serially with the PB2 or PB3 printers.

  1. On PB2 and PB3, turned off emphasized mode in Normal Font Sequence.

The ITC_CONFIG.xml sample printer configuration file has been modified to not have emphasized mode on for the default font.  This change results in a more clear and readable font for the default text.

  1. Added Java classes to support printing

The Java class and method names are similar to the .NET API and work in similar fashion. It also uses the same XML format for the printer configuration file. The Java implementation relies on an open source library, kXML2, for parsing the XML configuration file. The license information is at the end of this document.

 

3.40

  1. Added support for PB2 and PB3 printers.

3.30

  1. Added Lib and Runtime directory paths for ITC_CE5.0 development platform.
  2. Added Lib and Runtime directory paths for WM6.0 development platform.

3.20

  1. Updated sample ITC_Config.XML files to include settings for PB50 and PW50 printers.

3.10

  1. Fixed problem keeping the component from automatically adding the DLL reference when the component is added to a project.
  2. Fixed DoubleWideOff method so that it now properly returns an error code if called outside of the Open and Close methods.
  3. Fixed Write(byte[]) method so that it now properly returns an error code if called outside of the Open and Close methods.
  4. Removed an unneeded missing file from the C# example for XP.
  5. Changed sample ITC_CONFIG.XML file for printer id’s BT20 and BT40 to PB20 and PB40 to align with product naming.
  6. Modified readme file for C# example 2, Simple Sample, to better explain program operation.
  7. Documentation correction to .NET LinePrinter default constructor.
  8. Add hooks to allow update manager to recognize new versions

3.00

  1. Separate IDL into individual Resource Kit installs.
  2. Update sample ITC_Config.xml printer configuration files.

1.03

  1. Visual Studio 2005 support.
  2. New Icons for VS Toolbars.

1.02

  1. Added support in LinePrinters for Compressed Graphics.
  2. Fix for STR and RTS Serial Printing in Printer Configuration File.

1.01

  1. Signed all DLL’s for WM5.0 Security.
  2. Fix ActiveX LinePrinter  load Failure on newly created projects.

1.00

  1. Initial Release of Toolkit.

 

KNOWN ISSUES

Currently on the CV31 Bluetooth support, you must use SPP protocol, (Port type “WPPORT”), or always specify a PIN to force pairing with every connection when making a RFCOMM socket connection, (Port type “SOCKET”).

 

Note that currently using the LinePrinter to open and authenticate, (supply a PIN number in Open, GetConfiguration, or GetStatus), on a CV61 with a PR2 or PR3 printer it will initiate automatic verification from the user before the authentication completes.  See best practice note under TIPS below.

 

The Intermec 3” printers, PB3, PB31, PB32, are incompatible with the old sample programs.  The old sample programs expect printer identifiers that end in either 40COL or 80COL.  The 3” printers have identifiers that end in 60COL.

 

If you wish to use the 3” printers with the old sample programs, you must do one of the following.

  1. Modify the printer configuration file ITC_CONFIG.xml to change the printer identifiers for the 3” printers to end in 40COL.  (PB3BlueTooth_60COL to PB3BlueTooth_40COL, etc.)
  2. Modify the sample program.  You could either modify the program to handle 60 column reports, or to default to 40 columns if the printer identifier does not end in 80COL.

 

The old sample programs are: “example XP”, “example1”,” example2”, “VB.NET”.  The new sample programs are “example1_CF3.5” and “example1_FF3.5”.

TIPS

Best practice for authenticating a device with a Bluetooth printer is to only do it once.  Avoid re-authenticating the printer with each Open.

 

PW50 will communicate via Bluetooth even if the mobile computer is cradled in the printer dock.  This is by design.

"PW50 Serial Printer" is used only when the printer is connected by a serial cable to the mobile computer.

 

UNDOCUMENTED FEATURES

 

REQUIREMENTS

 

1) You need these hardware components to use the Intermec Printing Resource Kit:

 

          Pentium PC, 400 MHz or higher

 

          128MB RAM

 

           50MB Hard drive space for installation

 

2) Windows 2000 (Service Pack 2 or later) or Windows XP (Home, Professional, or Server) operating system is recommended.

 

3) Visual Studio 2005 or later is required for developing .NET applications.

 

4) Microsoft eMbedded Visual C++ (EVC) version 4 with Service Pack 4, or Visual Studio 2005 or later, is required for building C/C++ applications for most devices.

 

5) ActiveSync 4.1 or later is needed to download the applications to the devices.

 

KXML LICENSE

Copyright (c) 2002-2007 Stefan Haustein, Oberhausen, Rhld., Germany
 
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
 

The  above copyright notice and this permission notice shall be included in

all copies or substantial portions of the Software.

 

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS

IN THE SOFTWARE.