ARCHITECTURE
Mobile PINpad Architecture
E355/E265 USER AND BEST PRACTICES GUIDE 17
Virtual
Communication
Ports
By virtue of iAP1/iAP2/PMR-MUX2 protocols, the smart device and e355 can use
separate communications ports. The smart device uses a unique protocol string
for starting the communications with corresponding virtual communication port on
e355 side.
Figure 6 Virtual Communication Port Architecture
Protocol Strings
Table 5 presents the protocol strings for iOS devices with Lightning and 30-pin
connectors, and the associated virtual COM ports.
Apple iOS device with Lightning connector uses iAP2 protocol to communicate
with e355, and Apple iOS device with 30-pin connector uses iAP1 protocol to
communicate with e355. Both iAP1 and iAP2 protocols use the same protocol
strings on iOS device. For more information on communicating with accessory
using protocol strings, refer to External Accessory Framework on the Apple
developer website.
Table 6 shows protocol strings (commands) for Android/Windows devices and the
associated virtual COM ports.
Protocol string1
Smart Device
Protocol string2 ... Protocol string5
COM1A
e355
...
COM1B COM1E
Table 5 iOS Protocol Strings
Protocol Strings on iOS Virtual COM Ports on e355
com.verifone.pmr.xpi COM1A
com.verifone.pmr.barcode COM1B
com.verifone.pmr.zontalk COM1C
com.verifone.pmr.control COM1D
com.verifone.pmr.debug COM1E
Table 6 Android/Windows Protocol Strings
Protocol Strings on
Android/Windows
Virtual COM Ports on e355
<0xFF5A><o2><CRC> COM1A
<0xFF5A><o3><CRC> COM1B
<0xFF5A><o4><CRC> COM1C