Dormakaba ALVARADO TAS12/IntraQ User manual

PUD4246R5-0
Alvarado Manufacturing Company, Inc.
12660 Colony Street, Chino, CA 91710
Telephone: [phone]
Fax: [phone]
[email protected]
www.alvaradomfg.com
TAS12/IntraQ Direct Connect
Advanced Conguration Guide
PUD4246R5-0 Version 4.0

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 2 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Contents
Preface. ...................................................................................................................................................................... 3
Document Overview................................................................................................................................................ 3
Support. .................................................................................................................................................................. 3
Changing Conguration from the Device. .................................................................................................................. 4
Navigate to the Device Conguration Screen. ........................................................................................................ 4
Device Conguration Options. ................................................................................................................................ 5
TAS.txt File. ................................................................................................................................................................ 6
Network................................................................................................................................................................... 6
JSON Interface Fields............................................................................................................................................. 7
General. .................................................................................................................................................................. 7
Other. ...................................................................................................................................................................... 9
Amanda.txt File......................................................................................................................................................... 10
Amanda GPIO....................................................................................................................................................... 10
RS232. .................................................................................................................................................................. 10
EDM. ......................................................................................................................................................................11
RFID-NFC.txt............................................................................................................................................................ 12
Messages.txt File. .................................................................................................................................................... 14
Screen Images. ........................................................................................................................................................ 15
Default Images...................................................................................................................................................... 15
Images and Response Codes............................................................................................................................... 17
Image File Naming Conventions........................................................................................................................... 17
Image File Guidelines. .......................................................................................................................................... 18
Sound Files. ............................................................................................................................................................. 19
Default Sound Files............................................................................................................................................... 19
Sound File Guidelines........................................................................................................................................... 19
Appendix 1 – Symbologies. ...................................................................................................................................... 20
Revision History........................................................................................................................................................ 21

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 3 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
This document is meant to provide users with detailed information about the various conguration options available
for Alvarado TAS12 and IntraQ Direct Connect devices. The document is current up to TAS12 DirectConnect
version 1.3.1.
For questions or comments about the information presented in this guide, contact Alvarado’s Entertainment Support
department. Support hours are Monday–Friday from 8:00 AM to 4:00 PM Pacic time.
Email: [email protected]
Phone: [phone]
Preface
Document Overview
Support
NOTE
Any instances where the TAS12 and IntraQ devices differ will be noted. Otherwise, you can
assume that conguration is the same for both devices. “TAS12” is the generic name for the
software application.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 4 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Changing Conguration from the Device
Navigate to the Device Conguration Screen
1. While on the idle screen, tap the screen three times within two seconds to go to the Login screen.
2. On the Login screen, enter a valid Login ID into the eld and press Enter to go to the Administrator Menu,
shown below. The default Login ID is 123. Your ticketing provider may also create different Login IDs for you
to use, so check with them if the default Login ID doesn’t work.
3. Press the Device Conguration button.
Most Direct Connect conguration options are in the conguration text les detailed in the following sections.
However, you can adjust some conguration options from the device itself.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 5 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Device Conguration Options
1. All the conguration options on this screen can also be congured int the tas.txt le. See the TAS.txt File
section below on page 6.
• Server Url: URL or URI of the validation server.
• Site Name: Identier that is sent to the validation server with each validation request that identies the
device’s location.
• Min Ticket Length: Minimum length a ticket’s barcode number must be for the device to attempt to
validate it. If a ticket’s barcode number is shorter than this value, the device will mark it invalid without
sending it.
• Max Ticket Length: Maximum length a ticket’s barcode number can be for the device to attempt to
validate it. If a ticket’s barcode number is longer than this value, the device will mark it invalid without
sending it.
• Online Mode: When this box is checked, the device attempts to communicate with the server when it
validates a ticket. If the box is unchecked, the device will not attempt to communicate with the server and
will follow ofine validation rules.
• Exit Mode: When this box is checked, the device scans tickets out of the facility. If using an Exit Mode
device with a turnstile, the turnstile GPIO settings must be set up for exit scanning as well. If the box is
unchecked, the device scans tickets into a facility.
• Ticket Validation: The Ticket Validation screen validates tickets when an operator scans or manually
enters a ticket number.
• Ticket Information in Manual Ticket Entry: Scanning tickets with the Ticket Validation screen displays
information about the tickets but does not validate them.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 6 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Network
TAS.txt File
Setting Name Default Description
SITE NAME= Text string identier that is sent to the validation server with each
validation request that identies the device’s location.
SERVER URI= http://192.168.0.100/ URI of the validation server.
ONLINE= True True: The device attempts to communicate with the server.
False: The device does not attempt to communicate with the server.
OFFLINE
VALIDATION=
True True: If the device loses connectivity to the server, it will use
simplied validation rules to validate tickets. The device can
upload ofine scans to the validation server after it reestablishes a
connection if that functionality is congured.
False: The device marks all tickets as invalid while it does not have a
connection to the validation server.
NETWORK
TIMEOUT=
8 The network timeout time, in seconds. If the device does not receive
a response from the server before this time, the device switches to
ofine mode.
Minimum value is 1.
SHRED ON MODE= False True: Once a ticket is validated at the device, it cannot be used
again. Use this setting with devices without turnstile arms.
False: Once a ticket is validated and there is a corresponding
turnstile arm rotation, it cannot be used again. Use this setting with
devices with turnstile arms.
LOCAL LOGIN= True True: The device does not download operator login information from
the server. Operator login information in the operators.txt le must be
manually congured and updated.
False: The device downloads operator login information from the
server.
EDIT VALIDATION
MASKS=
True True: Device operators can manually edit validation masks when the
device goes ofine.
False: Device operators cannot manually edit validation masks when
the device goes ofine.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 7 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
JSON Interface Fields
Setting Name Default Description
INTERFACE= 2 1: Uses SOAP XML interface
2: Uses JSON interface
AUTHENTICATION= Basic
YWRtaW4vYWx2YXJhZG8=
Basic authentication header used when sending
requests.
VALIDATE
ENDPOINT=
/validate Denes the endpoint for ValidateTicket requests.
INFO ENDPOINT= /info Denes the endpoint for GetTicketInfo requests.
FORCE ENDPOINT= /force Denes the endpoint for ForceValidation requests.
VOID ENDPOINT= /void Denes the endpoint for VoidValidation requests.
LOGIN ADMIN
ENDPOINT=
/login Denes the endpoint for LoginAdministration requests.
DEVICE SYNC
ENDPOINT=
/sync Denes the endpoint for SynchronizeDevice requests.
PING ENDPOINT= /ping Denes the endpoint for Ping requests.
General
Setting Name Default Description
LANDSCAPE MODE= False True: The application displays in landscape mode. Use
this with IntraQ units.
False: The application displays in portrait mode. Use
this with TAS12 units.
MIN LENGTH= 12 Minimum length a ticket’s barcode number must be for
the device to attempt to validate it. If a ticket’s barcode
number is shorter than this value, the device will mark it
invalid without sending it.
MAX LENGTH= 12 Maximum length a ticket’s barcode number must be for
the device to attempt to validate it. If a ticket’s barcode
number is longer than this value, the device will mark it
invalid without sending it.
GREEN= 20 Time in seconds that the green attendant LED remains
illuminated after a valid ticket scan. This is also the
time a patron has to move through the turnstile if
ACTIVATION TIME=0.
If SHRED ON MODE=False, the value dened in the
GLOBAL GREEN= eld in the TASData.txt le overrides
the value entered here.
RED= 3 Time in seconds that the red attendant LED remains
illuminated after a valid ticket scan.
If SHRED ON MODE=False, the value dened in the
GLOBAL RED= eld in the TASData.txt le overrides the
value entered here.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 8 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Setting Name Default Description
SCREEN TIMEOUT= 10 Time in seconds that the device will remain idle on
the Operator Menu or Operator Login screens before
it returns to the previous screen. The timeout applies
individually to each screen.
SCREEN REFRESH
DELAY=
5 Time in seconds that the device displays the result of the
most recent scan on the Ticket Validation or Delivery ID
Validation screens.
EXIT= False True: The device scans tickets out of the facility. If using
an Exit Mode device with a turnstile, the turnstile GPIO
settings must be set up for exit scanning as well.
False: The device scans tickets into the facility.
DEBUG MODE= False True: Adds a Close button to the Home screen which
closes the TAS12 application and returns to the desktop.
The device also records information about TCP service,
start, stop, and error states. This log le is located in the
Program Files\TAS\DeviceLog.txt le.
False: There is no Close button and the device does not
write to the DeviceLog.txt le.
SAME TICKET
DELAY=
2000 Time in milliseconds the device will wait before
processing a duplicate ticket. For example, a value of
2000 means that the device ignores a ticket’s barcode
for two seconds after it is scanned.
ACTIVATION TIME= 0 Sets the time in milliseconds that the activation signal
(output wires – ACC1) remain in a closed-contact
state. Set this value to 0 to use the value dened in the
GREEN= eld.
If there is a non-zero value in this eld, the contact
signal from the TAS12 unit will remain in the closed
state. If used with a turnstile, the turnstile does not re-
lock if a patron passes through the turnstile before the
conclusion of this time. This setting is meant for use with
non-Alvarado turnstiles and is typically set for 500 (0.5
seconds).
DISPLAY TYPE= 4 Vacuum Fluorescent Display (VFD) display port.
Possible port values:
• 0 – Noritake Itron VFD – Model CU20026SCPB-
T28A
• 2 – ASCII
• 4 – MatrixOrbital
PRINT RECEIPT= True True: When ENHANCED MODE is also set to true,
the device prints receipts when it scans a barcode
with one of the symbologies dened in the RECEIPT
SYMBOLOGY eld.
False: Scanned tickets validate, but do not print.
TRACK= 2 The device reads from this track number when a
magnetic scan media is presented.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 9 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Setting Name Default Description
LED TIME SLOW ON= 300 Time in milliseconds the LED remains on in Slow Flash
Mode.
LED TIME SLOW
OFF=
600 Time in milliseconds the LED remains off in Slow Flash
Mode.
LED TIME FAST ON= 200 Time in milliseconds the LED remains on in Fast Flash
Mode.
LED TIME FAST OFF= 200 Time in milliseconds the LED remains off in Fast Flash
Mode.
LED OFFLINE= 002 Denes LED status for when the device is in Ofine
Mode. See explanation in LED CODE0-9 elds for
details.
• First Digit – Green LED
• Second Digit – Yellow LED
• Third LED – Red LED
LED CODE0= 10 Denes LED status for when the device displays a valid
response. LED CODE0 corresponds with response
code “Good 0” (default valid ticket). LED CODE1-9
corresponds with response codes “Good 1” to “Good 9”.
The rst digit is green LED status and the second digit
is yellow LED status. Use one of the following values to
dene LED status.
• 0 – LED off
• 1 – LED on (solid)
• 2 – LED slow ash (as dened in the LED TIME
SLOW ON and LED TIME SLOW OFF elds)
• 3 – LED fast ash (as dened in the LED TIME
FAST ON and LED TIME FAST OFF elds)
LED CODE1= 11
LED CODE2= 12
LED CODE3= 22
LED CODE4= 22
LED CODE5= 22
LED CODE6= 22
LED CODE7= 22
LED CODE8= 22
LED CODE9= 22
Other
Setting Name Default Description
TICKET SCREEN
ACCESS BARCODE=
If the device scans a barcode with the number dened
in this eld, the device goes directly to the manual Ticket
Validation screen.
This is meant to allow device operators to manually
enter tickets (that have poorly printed barcodes, for
example) without being able to access other sensitive
conguration settings.
PARSE BARCODE= Denes a Regular Expression to pull certain data from
a ticket scan (1D or 2D). Contact Alvarado for additional
information/documentation.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 10 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Amanda GPIO
RS232
Amanda.txt File
Setting Name Default Description
ACTIVATION RELAY
OUTPUT=
219 The output port for the activation relay.
GREEN LED
OUTPUT=
83 The output port for the green attendant LED.
YELLOW LED
OUTPUT=
84 The output port for the yellow attendant LED.
FRONT RED LED
OUTPUT=
82 The output port for the red attendant LED.
BACK RED LED
OUTPUT=
9999 This is not currently used. Leave this set to 9999 (disabled).
ROTATION FORWARD
INPUT=
94 The input port for the forward passage feedback contact.
ROTATION BACK
INPUT=
90 The input port for the backward passage feedback contact.
FAN= 203 The port for the TAS12’s onboard fan.
FAN CONTROL
TEMP=
20 Sets the temperature at which the fan engages when TOGGLE
FAN STATE is set to “True”. Uses Celsius or Fahrenheit depending
on what is congured in the CELSIUS eld.
TOGGLE FAN STATE= False True: The fan will turn on when the temperature reaches the
setting dened in the FAN CONTROL TEMP eld.
False: The fan remains on as long as the TAS application is
running.
CELSIUS False True: The temperature is reported in Celsius on the About screen.
False: The temperature is reported in Fahrenheit on the About
screen.
Setting Name Default Description
SCANNER PORT= 2 RS232 port the scanner uses to connect to the device. The port
number can range from 1 to 4, depending on the scanner used.
SCANNER
BAUDRATE=
115200 Scanner RS232 port baud rate. Supported values are 9600,
19200, and 38400.
DISPLAY PORT= 0 RS232 port the VFD uses to connect to the device. Use 0 to
disable this setting.
DISPLAY BAUDRATE= 19200 VFD RS232 port baud rate. Supported values are 9600, 19200,
and 38400.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 11 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Setting Name Default Description
KEYBOARD PORT= 0 RS232 port used by keyboard in the range 1 – 4. To
disable keyboard set to 0. To enable keyboard, set value
to port not used by scanner.
When keyboard port is shared with front or background
display, it would use Display Port settings for baud rate,
data size and parity.
KEYBOARD
BAUDRATE=
19200 Keyboard RS232 port baud rate. Supported values:
9600, 19200 and 38400.
PRINTER PORT= 0 RS232 port the printer uses to connect to the device
when CARD ID MODE is set to True. Use 0 to disable
this setting.
PRINTER
BAUDRATE=
38400 Printer RS232 port baud rate. Set this 115200 for Zebra
KR403 printers.
EDM
Setting Name Default Description
EDM PORT= 0 UART port the device uses to communicate with
the motor controller board and a paired slave unit, if
applicable.
0: EDM functionality is disabled.
1: Enables communication through COM1, which
enables EDM mode.
EDM MAIN= True True: This TAS12 will operate as the main EDM. The
Main EDM communicates with the EDM controller.
False: This TAS12 will operate as the secondary EDM.
EDM BAUDRATE= 57600 Baud rate of the EDM port.
EDM INTERVAL= 100 Sets the time in milliseconds between status queries
between the main TAS12 and the EDM controller.
EDM DIRECTION= 1 This setting determines the rotation direction of the EDM
with respect to the TAS12 device.
0: Counterclockwise (right-hand exit unit or left-hand
entry unit)
1: Clockwise (left-hand exit unit or right-hand entry unit)
EDM MODE= 0 This setting determines the turnstile’s behavior for the
direction of the TAS12 being congured.
0: Controlled
1: Free pass
2: No passage (closed)
3: Barrier disabled (drop-arm lowered)
4: Emergency

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 12 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
RFID-NFC.txt
Setting Name Default Description
RFID= False True: Enables support for the RFID reader. The device
uses RFID scans as Delivery ID or ticket, depending on
the RFID IS TICKET eld.
False: Disables support for the RFID reader.
RFID READER= 2 Denes which RFID reader the device will attempt to
use. The following device selections are available.
1: ACR (If using an ACR reader, you must also dene
which one you’re using in the RFID NUMBER eld.)
2: Kiosk IV
3: EVO
RFID NUMBER= 1 Selects the RFID reader’s controller that it uses to scan
RFID media. This eld is only used if RFID READER is
set to 1.
0: Use with ACR1252 RFID readers.
1: Use with ACR122 readers.
RFID BLOCK= 0 Denes the block on the RFID card the device uses
to read data. This value can vary depending on the
manufacturer.
RFID IS TICKET= False True: The device uses RFID scans as ticket numbers.
False: The device uses RFID scans as Delivery ID
numbers
RFID READ UID= True True: The device reads the serial number (UID) of the
RFID chip. This is for devices that have not had custom
data written to them.
False: The device reads custom data from the RFID
chip.
RFID BUZZER= False True: The RFID reader beeps twice when it successfully
reads an RFID card.
False: The RFID reader does not beep when it reads
RFID cards.
RFID TYPE NAME= TAS12 attempts to read MiFare Ultralight RFID cards
that are encoded with a specic NFC NDEF format.
For example, entering pfasoft.com:card into this eld
would enable cards with that encoding to be read and
validated.
RFID CARD LENGTH= This is the length of the number on the RFID card that
will be validated when it is encoded in NDEF format.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 13 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Setting Name Default Description
RFID CODE
DELIMITER=
Denes a delimiter character used when reading
multiple blocks of data. The TAS12 device will read up to
the RFID CARD LENGTH or RFID CODE DELIMITER,
whichever comes rst.
PASSTHROUGH
MODE=
False True: The Kiosk IV RFID/NFC reader will only read
MIFARE media.
False: The Kiosk IV RFID/NFC reader will read MIFARE
and mobile NFC passes (Apple Wallet, Google Pay).
#MERCHANT-KEY 1= Merchant ID-Private Key pairs for decrypting mobile
NFC passes. Contact ticketing provider or Alvarado for
details.
If you are going to use a Merchant Key, remove the hash
symbol.
#MERCHANT-KEY 2=
#MERCHANT-KEY 3=
#MERCHANT-KEY 4=
#MERCHANT-KEY 5=
#MERCHANT-KEY 6=
#URL= Reserved

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 14 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Messages.txt File
The messages.txt le can be updated automatically by the server when the device rst comes online. The le
contains a list of messages that are displayed on the Ticket Validation screen depending on the response code
returned by the scan.
Messages are stored in the format “##Message”, where “##” is the response code that determines which message
is displayed, and “Message” is the text of the message. Alvarado includes a default messages.txt le in new
installations of TAS12 Direct Connect. The messages are displayed below to give an example of how you can set
up your own response messages.
Based on the table above, if a valid ticket returns a response code “0”, the message “Good Ticket” displays on the
Ticket Validation screen.
00Good Ticket
01Good 1
02Good 2
03Good 3
04Good 4
05Good 5
06Good 6
07Good 7
08Good 8
09Valid Bio
10Reentry
11Invalid Event
12Invalid Date
13Invalid Time
14Invalid Day
15Invalid Access
16Invalid Location
17Err 17
18Err 18
19Err 19
20Err 20
21Used In Event
22Used In Day
23Used In Hour
24Used All Days
25Used All Hours
26Used at 2nd Location
27No Entries Remaining
28Error 28
29Error 29
30Error 30
31Cancelled 1
32Cancelled 2
33Cancelled 3
34Cancelled 4
35Cancelled 5
36Cancelled 6
37Cancelled 7
38Cancelled 8
39Cancelled9
40Error 40
41Already In
42Already Out
43Exit without Enter
44Invalid Bio Score
45Invalid Family Pass
46Invalid Ticket Price
47Invalid User Code1
48Invalid User Code2
49Invalid User Code3
50Invalid Replacement Media
51Not Found
52Rescan
53EV Failure
54Invalid Ticket Checksum
55Error 55
56Err 56
57Err 57
58Err 58
59Other

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 15 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Screen Images
Default Images
The bitmap les identied and described below are included by default when TAS12 units ship from Alvarado.
Default IntraQ screens look the same, but are oriented in landscape mode.
The images shown in the tables below are for TAS12 devices. IntraQ devices have the same images and le
names, but different dimensions.
TAS12 Go.bmp IntraQ Go.bmp
Bitmap Image File Name Description Response Code
go.bmp Any valid entry scan that does not have a
specic bitmap.
0-10
stop.bmp Any invalid scan that does not have a specic
bitmap.
11-99

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 16 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Bitmap Image File Name Description Response Code
scan.bmp The default “idle” image when the device is
waiting for the patron to scan a barcode.
N/A
wait.bmp Displays when the device is launching the
TAS application or when it is processing
information.
If there are no bitmaps for printing available,
the device will use this image.
N/A
Print.bmp Image displays when the device is printing
tickets.
N/A

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 17 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Images and Response Codes
Each response code can have its own unique bitmap associated with it. When a ticket scan returns a response
code, the TAS12 displays the associated bitmap image on the screen.
For example, Alvarado uses response code 51 when a scanned ticket is not found in the database. When this
response code is returned, the device displays this bitmap:
When naming bitmap image les, use the following naming conventions:
• For valid response codes (0-10), bitmaps should be named go#.bmp. Replace the “#” with the
response code number.
• For invalid response codes (11-99), bitmaps should be named stop##.bmp. Replace the “#” with the
response code number.
• When replacing any of the default bitmaps, the new bitmap should have the same lename as the le
it is replacing.
Alvarado uses response code 16 for tickets that are scanned at the wrong location. When this response code is
returned, the device displays this bitmap:
stop51.bmp
stop16.bmp
Image File Naming Conventions

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 18 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Image File Guidelines
Observe the following guidelines when creating custom bitmaps:
• Bitmap les for TAS12 devices must have pixel dimensions 480 (W) x 640 (H). Bitmap les for IntraQ
devices must have pixel dimensions 640 (W) x 480 (H).
• Bitmap les must have the following attributes:
○Bit Depth: 8
○ File Size: Approx. 300 KB
○Resolution: 72 x 72 ppi
○Color Space: Indexed Color (256 Colors)
• All bitmap les are placed in the device’s FlashDisk\TAS folder.

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 19 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
The sound les described below are included by default when TAS12 units ship from Alvarado, unless alternative
sounds are provided by the customer. If a sound le has a name that includes a number, that sound plays for that
response code number.
Response codes indicate the reason GateLink10 determined a ticket was either valid or invalid.
The TAS12 device uses .wav les to play sounds. As with bitmaps, the device can play specic sounds for specic
response codes. The sound les can be customized if the guidelines presented below are followed.
• For valid response codes (0-10), sound les should be named go#.bmp. Replace the “#” with the response
code number.
• For invalid response codes (11-99), sound les should be named stop##.bmp. Replace the “#” with the
response code number.
• When replacing any of the default bitmaps, the new bitmap should have the same lename as the le it is
replacing.
• Has the same or similar size and bit rate as the existing .wav les.
Sound les are stored in the device’s FlashDisk\TAS directory.
Sound Files
Default Sound Files
Sound File Guidelines
File Name Description Response Code
Go.wav Default sound for a valid ticket. If no other specic sounds are
available, the device defaults to this sound.
All Valid
Printer.wav Sound indicates a communication error with the printer. N/A
Stop.wav Default sound for an invalid ticket. If no other specic sounds are
available, the device defaults to this sound.
All Invalid

TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
Page 20 For Assistance: [email protected] [phone] PUD4246R5-0
TAS12/IntraQ Direct Connect Advanced Conguration Guide 4.0
The table below shows the syntax for the RECEIPT SYMBOLOGY eld. For your convenience, the most commonly
used code characters have been provided.
TAS12 devices use the Honeywell 3320g barcode imager. A comprehensive chart of code characters for the
Honeywell 3310g imager can be found in Appendix A of the Vuquest 3320g User’s Guide (available on Honeywell’s
website).
Appendix 1 – Symbologies
Symbology AIM Code Character (3320g)
GS1 DataBar Family y
PDF417 r
MicroPDF417 R
Aztec, Aztec RUNE z
Data Matrix w
QR Code, MicroQR s
Maxicode x