SCA Functional Specification

Configuring TCP Connection

• LAN Connection with Debug Cube - LAN (Ethernet) connection using the debug cube has the connectivity towards the Raptor side, hence the IP is not accessible by the Android OS. TCP interface for SCA application needs to be configured with device type as lan and device name as eth0 with this setup.
• LAN Connection with Non-debug Cube - LAN (Ethernet) connection using the debug cube has the connectivity towards the Android OS only. Android OS shares the IP with the Raptor through a separate IP over USB connection. TCP interface for SCA application needs to be configured with device type as preconfigured or lan and device name as usb0 for accessing IP connectivity with this setup. The device IP address will be displayed from Android Settings.
• WiFi Connection - WiFi will be accessible by Android OS only. Android OS shares the IP with the Raptor through a separate IP over USB connection. TCP interface for SCA application needs to be configured with device type as preconfigured or lan and device name as usb0 (IP over USB) for accessing IP connectivity with this setup. The device IP address will be displayed from Android Settings.

Configuring Connection Ports

When Android OS gets an IP connection request, only those requests with the following TCP port ranges are forwarded to the Raptor side. That means the applications, including SCA, those are running on Raptor will get the TCP connection requests and only if the listening ports ranges between:

• port 23 or 5100 to port 5599

Or

• port 12100 to port 39999

For SCA, the default primary port number is 5015 and secondary port number is 5016.
Using DEVICEPORT and DEVICESECONDPORT parameters, these default numbers need to be changed to the port numbers that come within the listening port ranges and accessible by the Raptor side. POS system makes the connection request with the changed primary or secondary port number.