Entry Points : TP3110 with Card Reader
  

TP3110 with Card Reader

TP Button/TP3110 ticket printer with swipe card reader.

Global Settings

 
Parameter
Description
Name
Name of the unit.
Description
Description of the unit.
Template name
Name of the unit type template
Template version
Version of the unit type template
Tickets on roll
Number of tickets on roll. Valid values between 1-3000. Default value is 2000.
 

Equipment Profile Level Settings

 
Parameter
Description
Name
Name of the unit.
Description
Description of the unit.
Type name
Name of the unit type.
Type description
Description of the unit type.
Unit id
Identification code of the unit.

Button 1-5

From the drop-down list of each Button, select the service that you want to be connected to that particular Button.
Date format on ticket
From the drop-down list, select the wanted date format. Available formats are:
YYYY-MM-DD; DD-MM-YY; MM-DD-YY; and Day Month Year.
Time format on ticket
From the drop-down list, select the wanted time format. Available formats are:
HH:MM; HH:MM am/pm; HH:MM:SS; and HH:MM:SS time zone (for example CEST).
Surface custom parameters
Which custom parameters should be available on the ticket.
The following parameters and strings to use in the Surface Editor application are available:
Waiting customers
Current waiting time
Branch name
Tickets left
Mark several of them by holding down Ctrl while clicking on them

Card Service

From the drop-down list, select which service should be connected to the swipe card reader.
Track to validate
From the drop-down list, select track 1, track 2 or track 3 to be used for validation.
Bank cards usually use track 2.
Start Validation
The first digit that should be used for card validation.
Validation data
The number that identifies a valid card.
Track 1-3 Mask
Enter the mask for the track that should be validated here.
The Card mask X settings specify the data to mask out on the three tracks of a card. These settings apply to all cards. An empty setting is the default setting and no data is masked out. List the bytes that should be set to 0 (=masked out).
Examples:
Card mask 1: 0-255 = set the complete track to all zeros.
Card mask 2: 0-1,6-255 = set all bytes to 0 except bytes 2-5.
Card mask 3: empty = no data is masked out.
Button delay
This is the minimum time that must elapse after a customer has pressed the button and until the next customer can get a ticket. Max: 60 seconds. Min: 0 seconds.
Tickets on roll
Number of tickets on roll.
Low ticket alarm
The number of tickets in the printer when the alarm is activated.
The ticket counter is restarted when the paper is fed into the printer mechanism.
Write card data in QAgent log (debug)
Note that this option may log confidential card data, use with caution!
Device Controller
From the drop-down list, select which Device Controller should be used.
 

Branch Level Settings

 
Parameter
Description
Default name
Default name of the unit.
Description
Description of the unit.
Unit Identifiers
The two columns of the table are:
Name - Name of the unit, by default the name of the unit plus a sequential number, for example WebReception 5 or WebServicePoint 2. Can be changed to anything, so long as the name is unique, within the branch.
Logic Id - An ID used in the connectors. The Logic Id continues with the next number in the sequence of the auto generated ID's within the unit type (e.g. Service Points, Entry Points, or Presentation Points). The number can be changed to anything, in the range of 1-9999, as long as it is unique within the Service Point, Entry Point, or Presentation Point.
Unit id
Identification code of the unit.
IP address
IP address of the ticket printer.

Button 1-5

The service that is connected to that particular Button.
Card Service
The service that is connected to the swipe card reader.
Start Validation
The first digit that is used for card validation.
Validation data
The number that identifies a valid card.
Device Controller
Name of Device Controller that is used.