INFO: Using EESE with Smart Eye Pro Server 8.2 requires setting E-Prime as the Client Type [29874]

This article applies to:

E-Prime Extensions for Smart Eye 1.0

NOTE: EESE 1.0 is for E-Prime 2.0.

Detail

When you use E-Prime Extensions for Smart Eye with SE Pro Server version 8.2, you need to select the "E-Prime" Standard Format packet configuration preset option from SE Pro Server:

You can confirm this configuration is in place when you see "E-Prime" as the Client Type for your Destination Host in the SE Pro Server's Communication Settings window. Please see your copy of the Smart Eye Pro Manual for more information on configuring a Destination Host for use with E-Prime.

Immediately before you launch your EESE experiment, you should visually confirm active eye tracking in the SE software and press the Track button in SE Pro Server:

If this configuration is not in place when running an EESE experiment with SE Pro Server 8.2, you can expect to receive a failure to connect error, such as:

Depending on whether you use UDP (default) or TCP, the failure to connect error can instead be: "An error has occurred in the Smart Eye receive thread." Take the following troubleshooting steps if connectivity errors persist after you set E-Prime as the Client Type in SE Pro Server:

1. Use the ping command to troubleshoot the network connection itself, see INFO: Locate Your IP Address and Ping Another Computer [31363] (If you specify TCP in the SmartEye Device and SE Pro Server, on a two-machine setup).
2. Power cycle the SE Pro Server machine and the eye tracker.
3. Consider (temporarily) disabling any firewall or antivirus programs (INFO: Windows Firewall Permissions with E-Prime [26269]). Make sure to reenable them before going to any other website.

See Also:

RELEASE INFO: Which version of E-Prime should I use with E-Prime Extensions? [19376]