Configurations As Files; Compatibility Challenges - Printronix T2N series User Manual

Configurations as Files

The ability to save and restore configurations to and from a file allows users to create a
configuration once and then easily update multiple printers with that same configuration. A saved
configuration file can be loaded into the Configuration Utility and then downloaded into the printer
using the "Set" command.
CAUTION: The saved configuration file is in binary format and should not be opened or
modified outside of the Configuration Utility.
Save File: Saving Configurations as Files to the PC
The "Save File" button saves the current values in the Configuration Utility as a file (.dcf) to any
location on your PC running the utility. A "Save As" window opens to allow the user to choose the
location and file name.
Before saving the configuration to the PC, the following steps are recommended:
1. Configure the target printer as desired.
2. Perform a "Read" operation to verify the target printer configuration.
3. If complete, save the configuration by clicking the Save File button.
Note: The network configuration will not be included in the saved file since the IP address and
other parameters are unique for each printer.
Load File: Restoring Configurations from Files from the PC
The "Load File" button loads the Configuration Utility with the selected file on your PC (file
extension .dcf). The "Open" window displays allowing you to navigate the PC to select the
intended file. Once the file is selected, the configuration values are populated in the Configuration
Utility fields.
Note: The configuration values are not stored in the printer until the "Set" operation is performed.
Perform a Set operation in each of the Configuration Tabs.

Compatibility Challenges

The Configuration Utility is designed to be compatible with a specific firmware version level. Each
Configuration Utility release has a certain set of static configuration options. Similarly, a firmware
version can support a certain set of static configuration options. A compatibility problem occurs if
Configuration Utility capabilities do not match.
The version level format Vm.xxYY as described in Version Numbering (page 56) is common for
both firmware and the Configuration Utility. Version format "xx" represents configuration option
capabilities. Hence, firmware version V1.02C = V1.02B = V1.02F in terms of configuration
options. If more configuration options are added, the next version released would be V1.03A.
This same version scheme applies to the Configuration Utility. Using a common version scheme
makes it easy to determine where compatibility problems could exist. For example, if the firmware
was V1.03C and the Configuration Utility was V1.03F, they are compatible. Alternatively, if the
firmware is V1.03C and the Configuration Utility was V1.02P, the Configuration Utility has fewer
configuration option capabilities therefore creating a compatibility problem.
Consider the following compatibility scenarios:

Firmware versus Utility: T2N firmware version does not match the Configuration Utility

Saved Files versus Utility: T2N config files *.dcf does not match the Configuration Utility
66