Communication Protocols - VeriFone e355 User And Best Practices Manual

Communication Below are the communication protocols:
Protocols
iAP1
The iAP1 protocol is an Apple accessory protocol specified in MFi Accessory
Firmware Specification R46 for Apple 30-pin connector devices. This requires
Apple authentication coprocessor to validate e355 as valid Apple accessory
before being able to communicate with iOS device. Frame ID reading selects the
iAP1 protocol early on during the e355 power-up or restart. iAP1 is only supported
on USB interface and not supported on Bluetooth interface. Maximum message
size for read and write operations is 1024 bytes (1012 bytes payload), which is
same as iAP2 maximum message size.
iAP2
The iAP2 protocol is a complete replacement of iAP1 protocol and is not backward
compatible with iAP1. The iAP2 protocol is used specifically with the newer 8-pin
Lightning connector for iOS devices. The iAP2 protocol is specified in MFi
Accessory Interface Specification, which requires Apple authentication
coprocessor to validate e355 as valid Apple accessory before being able to
communicate with iOS device. The frame ID value selects the iAP2 protocol early
on during the e355 power-up initialization. The iAP2 protocol is also supported on
USB and Bluetooth interfaces. Maximum message size for read and write
operations is 1024 bytes (1012 bytes payload).
Example:
PMR-MUX2
Verifone developed a custom PMR-MUX2 protocol. Following are the key points
about this protocol:
•
•
•
Application Auto-Launch
This feature is supported in iAP2 driver version V01.05.04 and later.
*APP_LAUNCH_ID is used to specify a unique Application Bundle ID.
*APP_LAUNCH_ID=com.verifone.e355
Configuration variable *IOS_APP_ALERT is used to alert the user before
launching the application specified by *APP_LAUNCHID when an iAP2
accessory is connected. User alerts can be disabled for USB connection but
not for Bluetooth.
•
*IOS_APP_ALERT=1 will launch the application with no user alert.
•
*IOS_APP_ALERT=0 will launch the application with user alert.
Used over Bluetooth SPP and USB interfaces.
Protocol is message based and not stream based, increases the
communications integrity.
Message header contains virtual com channel number.
355/ 265 U B P
E E SER AND EST
A
RCHITECTURE
iap_get_keypad_state()
25
G
RACTICES UIDE