ARCHITECTURE
Mobile PINpad Architecture
18 E355/E265 USER AND BEST PRACTICES GUIDE
PMR-MUX2 protocol uses commands to open, send, and close the
communications ports. For full details on the PMR-MUX2 protocol, refer to section
PMR-MUX2.
Device Ports
Applications running on e355 open the virtual COM device ports COM1A,
COM1B, COM1C, COM1D, and COM1E. These applications respond to the data
sent to these ports.
Table 7 shows the application names that open specific device ports.
XPI application uses COM1C port for supporting Zontalk downloads in addition to
its COM1A port for communicating with smart devices. The last COM1E port is
available for debug message output. There are no applications using this port.
Open and Close Events of Communication Ports
The e355 sends a Connect event to its application when application on the smart
device opens the port for communication. The e355 sends a Disconnect event
to its application when application on smart device closes the communication port.
If the e355 application has not opened the device port, but application on smart
device tries to open it, then e355 responds with an error code.
Applications on e355 can use API get_port_status() for detecting open and
close status of communication port in the smart device application.
Device Port APIs
Following are the APIs used by the device ports.
<0xFF5A><o5><CRC> COM1D
<0xFF5A><o6><CRC> COM1E
Table 6 Android/Windows Protocol Strings (continued)
Protocol Strings on
Android/Windows
Virtual COM Ports on e355
Table 7 Applications vs. Device Ports
Virtual COM Port on e355 Application Owner
COM1A mADK/XPI application
COM1B Barcode application
COM1C Zontalk downloads
COM1D Control application
COM1E Debug message output
To Next Page
Loading...
Need help?
General
