Rice Lake TransAct 5.0 - Installation & Operation Manual User Manual

Page 297

Advertising
background image

286

ATS-2 / PDC Options (Auto Return to Unattended)

Check this box to automatically return to unattended mode after an attended transaction
has been processed.

ATS-2 / PDC Options (Update Tare)

This is a key sequence that when entered by the truck driver in response to any prompt
will update the truck tare weight and cancel the transaction in process. This only works if
the truck is allowed to update its tare weight in unattended mode.

ATS-2 / PDC Options (Cancel)

This is a key sequence that when entered by the truck driver in response to any prompt
will restart the transaction by prompting the driver reswipe or reenter his badge id.

ATS-2 / PDC Options (No Response)

This is a key sequence that designates no response to a prompt.

ATS-2 / PDC Options (Dir Change Preamble)

It may be necessary to process transactions in unattended mode where the material
direction is not the default direction (incoming or outgoing). If the truck weighs in and
weighs out the direction is determined from the two weights. However, if stored tare
weights are used, this is no longer possible. You can set a key sequence that when entered
in front of the material code will set the material direction to the opposite of the default
direction.

This is typically used for returned materials. For example, if this value is 888 and the
driver is returning washed sand (material code 100), he would enter 888100 in response
to the material code prompt.

ATS-2 / PDC Options (Drive Off Code)

Enter the material code that will be attached to transactions that are recorded in the
database when a truck drives across the scale without stopping or fails to complete the
responses to all the unattended prompts. You can add a special material type called
"Drive Off" for this purpose. A transaction is only generated if the truck's badge id has
been verified before the drive off.

ATS-2 / PDC Options (Log Terminal Messages)

When this box is checked, all unattended communications with the data terminal are
recorded in a file called error.log and placed in the application's Log folder. Buttons are
provided to view and clear this log.

Advertising