M
X
800 SERIES PROGRAMMERS GUIDE 275
APPENDIX A
IPP MS and DUKPT Communications Packets
This appendix describes the required packet commands of the IPP for MS (Master
Session) or DUKPT operations supported by the M
x
800 series.
Advanced
Programming in
IPP
The differences between the Verix and Verix V IPP MS and DUKPT from the
M
x
800 series IPP (XMIPP8) are summarized in Table 22.
VVIPP supports IPP7 GISKE 3DES key features with one enhancement: All 10
master keys can be triple-length keys. IPP7 is limited to at most three triple-length
keys.
Minor Differences
by Packet
<SI>0103<SO> PROM Checksum
The value of the checksum does not match IPP7 because Verix V does not use
the same code.
<SI>0108<SO> IPP ROM Version Number
The return packet is
<SI>14IPP8 EMULvvv mm/yy<SO>{LRC}
where, vvv is the version number, mm is the release month, and yy is the release
year.
<SI>13n<SO> Select Baud Rate
Since there is no IPP UART, setting the baud rate does not affect anything.
However, the baud rate is stored in non-volatile memory so it can be returned in
diagnostics packets.
In platforms with an IPP chip, the application must determine the baud rate of the
IPP by sending a test packet at all possible baud rates until the IPP responds with
an ACK. In Verix-based Omni series terminals, there is no UART so baud rate
mismatch is not possible. Applications that try all possible baud rates receive an
ACK on the first test packet thus, speeding up applications slightly.
Table 22 Differences in M
x
800 series IPP
IPP IPP6 IPP7 VVIPP IPP8 VVIPP8 MXIPP8
Secure Message Mode No Yes No Yes No No
Spain SEMP/4B Yes Yes No Yes No No
Key tagging Yes No No No No No
DUKPT Engines 1 1 1 3 3 3
To Next Page
Loading...
Need help?
General
