EyeLink connection help

Support
1

Hi Chris,

I am setting up a new Mac Studio and am having trouble connecting to the EyeLink via MWorks. I have installed the EyeLink Developers Kit and followed these instructions to set up the Mac as the display computer. I believe the EyeLink host computer IP address is 100.1.1.3 (tested the ethernet connection with ping from the Mac terminal). I also checked “Open using Rosetta” for MWServer.

Here is the error message:

00:08:14: ERROR: Failed to create object.
Extended information:
reason: No factory for object type: iodevice/eyelink
location: eyelink.mwel: line 33, column 1
object_type: iodevice/eyelink
ref_id: idp105553151183999
component: eye_tracker
parser_context: mw_create

and code for the eyelink object:

eyelink eye_tracker (
tracker_ip = ‘100.1.1.3’
eye_lx = eye_lx
eye_ly = eye_ly
eye_rx = eye_rx
eye_ry = eye_ry
pupil_lx = pupil_lx
pupil_ly = pupil_ly
pupil_rx = pupil_rx
pupil_ry = pupil_ry
pupil_size_r = pupil_size_r
pupil_size_l = pupil_size_l
blink_r = blink_r
blink_l = blink_l
saccade_r = saccade_r
saccade_l = saccade_l
fixation_r = fixation_r
fixation_l = fixation_l
data_interval = 1ms
tracking_dist = 1024
// cal_target_x = cal_target_x // for eyelink-driven calibration
// cal_target_y = cal_target_y
// cal_target_visible = cal_target_visible
)

Are there any steps I’m missing? Any idea what might be the issue/what additional tests I can run?

Thanks,
Sol

2

Hi Sol,

FYI, the current version of the EyeLink Developers Kit supports both Intel and Apple Silicon processors, so there’s no need to run MWServer via Rosetta.

The error “No factory for object type” suggests the EyeLink plugin is failing to load. Can you quit MWServer and then re-launch it via Terminal using the following command?

MWORKS_WRITE_MESSAGES_TO_STDERR=1 /Applications/MWServer.app/Contents/MacOS/MWServer

The output in Terminal should contain a message starting with “WARNING: Plugin module (Eyelink) failed to load”. Please send me the full text of the message.

Thanks,
Chris

3

Oddly enough, unchecking “Open using Rosetta” and restarting MWServer in this way seems to have solved the issue!