VeriFone e265, User And Best Practices Manual

Page: 75 / 78

E
355/
E
265 U
SER AND
B
EST
P
RACTICES
G
UIDE
75
C
HAPTER
9
Control and Barcode Applications
This chapter discusses control and barcode applications and their supported
commands and responses.
Control
Application
Control application is the first application that runs on Mobile PINpad architecture
and it is set as the value of
*GO
configuration parameter.
For supported commands and their format and response, see e355/e265
PAYware Mobile Reader Control Application Commands Programmers Guide ,
VPN - DOC087-078-EN.
Barcode
Application
Barcode application is launched by control application and it is set as the value of
*VXAPPx
configuration parameter.
For more information on supported commands and their format and response, see
e315/e355 Barcode Application Programmers Guide, VPN - DOC087-070-EN .
Pipe Interface
Verison V01.15.01 and later of the control and barcode applications support pipe
interface. These are OS pipes that allow user applications (specified by
*VXAPPx
)
to send commands to control and barcode applications and get responses. The
command and response formats on these pipes are the same as regular control
and barcode application commands. One major difference is that command length
is limited to 500 bytes.
Pipe Names
Control application opens the pipe using name
P:CONTROL
, use this name for
establishing bi-directional communications with control application. Similarly,
barcode application opens the pipe using name
P:BARCODE
.
Once the pipe is open and connected with control/barcode application, the
sending and receiving are with standard
write()
and
read()
APIs. Currently,
both control and barcode applications do not support
close()
API, they expect
pipes to be left opened until the next re-boot.