There are various scanner setups required for batch Scanning. There is a section in the help file for each set of steps. Batch scanning is intended t be used in an environment where there is no RF network. In fact, the scanners for this function do not even need to support a wireless network. They are connected to the PC to upload and retrieve the required data. This function was devleoped for Windows Scanners only. In order to use Off line functionality with Android scanners, we have introduced Off Line functionality which is covered here. Off line scanning is a more complete solution and is recommended as the preferred option if at all possible.

 

This is not the same as Buffered Scanning. Buffered scanning uses a wireless network but has mechanisms to store data if the network is not available. The network is however required to start and stop jobs on the scanner.

 

There are core TransLution Setup options, there are requirements for the Scanner setup and then of course, there is the requirement to retrieve scanned data from the batch scanner. There are two ways to do this - either using the standard TransLution Client or, if the site is running EazyTouch, using the EazyTouch Batch Scanner Receive function.

 

Buffering - Overview

 

The release of TransLution 3.5 saw the release of what we have called buffering for scanner and touch screen users. This is a kind of batch scanning functionality in the sense that it supports scanning and a limited degree of validation while not connected to the server. This is not the same as Batch scanning which does not require any kind of wireless network. While this is a more complete solution than buffered scanning it is still limited to only being supported on Windows scanners. It is recommended that for all new implementations only Off Line scanning is implemented using Android scanners.

 

There are three types of scanning that support buffering:

  • Directed
  • Partially Directed
  • Undirected

 

There are specific setup requirements for each of these and they are described in the on line help sections below.

As a first step, we require new Function Area Types to be defined. For new implementations, these will already exist in the database but for upgrades, these will need to be added. Once this has been done we need to define the implementation specific Function Areas and their Scanner Prompt Sequences