placeholder
On this page you can find information about following topics:

How to use this documentation     go to the TOP

The representation of this documentation is arranged it in the following way:

header with the version information of this document.

    Navigation Tree
  • General Information
  • Supported Commands

    Description
  • Short Version - only NODE and TAG names
  • Long Version - NODE and TAG names with detailed information
  • Change history - Command changes during the documentation history
  • Examples - Example Requests and Replies for this command
  • at the top of the document is placed the information about the version of this documentation
  • on the left side is a navigation-tree / for more information click to the item Supported Commands
  • on the right side you get the Description about the selected topic or sub-topic of the navigation-tree / for more information click to the item Supported Commands

Hints how to use the navigation tree     go to the TOP

Warning To use the Navigation-Tree JavaScript must be enabled!
  • a mouse-click to the images or to the text behind them expands and closes all entries of this item
  • the symbol on the left side of the command list shows for which scale-type a command can be used

    this command can be used only for UC3 devices
    this command can be used only for ETICA devices
    this command can be used for UC3 and ETICA devices
    if the symbol background is green there have been new commands added with the latest docu version
    if the symbol background is orange there have been changes for this command with the latest docu version

  • a mouse-click to a command-name opens the "Short version" of the description for this command
  • for each command you can access the "Short Version", "Long Version", "Change history" and "Examples" by clicking the corresponding tree item

Hints how to use the buttons of the description-window     go to the TOP

In the header of the description window are three button to select
  • the "Short version", which shows in a compressed format only the NODE and TAG names to get a quick overview
  • the "Long version", which shows detailed information for each NODE and TAG.
  • the "Change history", which shows the whole change history for this command.
  • the "Example", which shows XML-requests for this command (the command which was sent to the UC3 devices)
    and the Reply (the response which was sent from the UC3 devices to this request).
Information The Example-Requests can be marked and copied to a new File (saved as a XML-File with UNICODE 16 Format - UTF16). This File can be sent to a UC3 Network with TransUC3.

General Information about the UC3 XML-Commands     go to the TOP

The commands described later are used for exchanging data between UC3 devices. All data sent to a scale or received from it are stored in the XML format.
This means that the rules and conventions which are assigned to that format have to be kept to,
e.g. the file has to be wellformed. Every 'opening' tag needs a 'closing' tag.
In the following it will be distinguished between nodes and elements.
A node is a special form of an element. It doesn't contain a value by itself but further subnodes.
An element on the other hand has a datatype and a value likewise.

The 'Long version' of a command contains detailed information about the nodes and elements.
For reasons of better understanding you can find some additional information at this place that helps you when setting up commands.
  • Mandatory
    If its value is set to yes this node or element is required for communication or for processing of the command at the target device.
    If its value is false than it is an optional element and must not to been sent.
    Elements that not have been sent to a target device are marked there. When reading data from the scale network this information is sent back without a content, e.g. <name/> or <name></name>.
  • max. Occurence
    The maximal occurence of this node/element within the command.
  • Supported modes
    The modes that are supported for this command.
  • Datatype
    The datatype the element is assigned.
    A description about the data type can be found when following the hyperlink assigned to the elements data type.
  • Range of values
    The range within a datatype that is supported by the scale.

Selection of a valid UC3 XML-File     go to the TOP

The following example describes the frame-items for a valid UC3 XML-File.

<? xml version=" 1.0" encoding=" UTF-16" ?>
<scaledata>
  Place here your XML command Requests.
</scaledata>

Annotation:
  • First, make up a reference to XML. The first line is responsible for that.
  • Besides it includes the version and the encoding. The attribute 'encoding' describes the character set with which the data of this file must be interpreted.
  • Encoding="UTF-16" tells that the international character set based on the ISO/IEC-10646-Norm (Unicode) with 16 Bit character width is used, i.e. 2 bytes in the file are corresponding to one character.
  • The initiating <xml>-tag for UC3 XML-Files has always the name 'scaledata'.
  • A relationship to the used XML-Schema is not necessary for the UC3 XML-Files, because ther is no automatic validation of the XML-File content against a proofed schema.
  • In the area "Place here your XML command Requests" must be written the XML-commands like described in this documentation.
  • To remove information that has been assigned to a tag before this tag must be sent without a value, e.g. <tare></tare> for deleting a tare value.
Information To create an new UC3 XML-File you can copy this skeleton into a new file and save it as xml file with unicode character set.

Deleting data of an element     go to the TOP

To delete all values of an element that have been set in former times this element must be sent without a value.

e.g. <price2 l="0"></price2>