 |
Command:
PRINTER IMAGES
 |
Node: printer_images |
|
Mandatory: |
no |
|
max. Occurrence: |
unbounded |
|
Description: This tag is used as container for commands regarding printer images. This command is used to -> ask a UC3 to get the BMP file for a printer images from a FTP server -> ask a UC3 to put the BMP file for a printer images to a FTP server -> ask a UC3 to delete the BMP file for a printer image form it's local image folder To be sure that the UC3 devices really copied the image-files from the FTP server the logfiles form the UC3 or the logfile from the FTP server must be checked. The status from TransUC3 describes only if was possible to ask the UC3 scales to copy the image files.
|
|
Notes: This command is new since UC3 application version 1.2.0 Each UC3 saves the image files for the printer in the local subfolder ..\printer\... If in the customer.ini the parameter sDefaultCustomerPath=.. is not defined the files are copied to the default-folder
Speicherkarte\unicorn\images\printer\... If the parameter is defined for example with sDefaultCustomerPath=KCS_Demo_Image_Path the files are copied to the folder
Speicherkarte\unicorn\KCS_Demo_Image_Path\printer\...
|
|
 |
|
|
 |
Node: printer_image |
|
Mandatory: |
yes |
|
max. Occurrence: |
unbounded |
|
Supported modes: |
delete Delete the named item. read Read the named item. write Write the named item.
|
|
Description: This command is used for transfering, reading or deleting a printer image.
|
|
 |
|
|
|
 |
Tag: originator |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
max. 30 characters
|
|
Nillable: |
no |
|
Description: The originator who caused this software command.
Since this command is reserved for authorized Mettler-Toledo employees it has to be the email address of the originator, e.g.
nsp@mt.com which means that the network software platform caused this software command.
|
|
Notes: The originator is listed in the TRACE-Logfile.
|
|
 |
|
|
|
 |
Tag: last_change |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
Datatype: |
dateTime |
|
Range: |
- |
|
Nillable: |
yes |
|
Description: CCYY-MM-DDThh:mm:ss The format is as following: C = Century Y = Year M = Month D = Day T = Separator between date and time h = hour m = month s = second
|
|
 |
|
|
|
 |
Tag: source |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
max. 100 characters
|
|
Nillable: |
no |
|
Description: The name of a source file or an URL.
|
|
Notes: to read the command needs the complete folder from the FTP-server-ROOT (ask the UC3 to copy the file from the FTP server) example: ftp://192.168.155.23/_image_files/printer/ticket/ticket-header-logo.bmp to write the command needs the complete subfolders from the UC3 image folder (aks the scale to copy the file to a FTP server)
|
|
 |
|
|
|
 |
Tag: destination |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
max. 100 characters
|
|
Nillable: |
no |
|
Description: The name of a destination file or an URL.
|
|
Notes: to read the command needs the complete subfolders from the UC3 Image folder (ask the UC3 to copy the file from the FTP server) example: logo_0.bmp to write the command needs the complete existing folder from the FTP-server-ROOT (aks the scale to copy the file to a FTP server)
|
|
 |
|
|
|
 |
Tag: category |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
-
|
|
Nillable: |
no |
|
Description: Since the number of images on a device can be enormous they have to be assigned to different categories. The following categories are supported:
Name |
Description |
Application |
Images that are used by the application like the header and footer image for a ticket and the images for the labels. |
Article |
Article specific images, which are printed on a label or ticket. With the current UC3-applicaiton version 1.2.0 it's not possible
to use this images.
|
|
|
Notes:
ATTENTION: the category name is Key-Sensitive
|
|
 |
|
|