Home Forums Non-EyeX development other SDK for I-Series Running Communicator

This topic contains 1 reply, has 2 voices, and was last updated by Profile photo of Grant [Tobii] Grant [Tobii] 1 month ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #6506
    Profile photo of Kevin Braswell
    Kevin Braswell

    Team –

    I am developing a standlone .NET app for the I-Series device. At one point, I did a proof of concept app that ran using gaze SDK on the i-Series (Not using Windows Control). This was a successful test, however I did not run Communicator simultaneously.

    I need someone to confirm the following before we build our next release:

    1. Is Gaze SDK the correct sdk to leverage in this use case?

    2. Can our stand alone app use the global eye tracking settings/configuration (dwell/click -right-left eye – calibration, etc) if they have already been set?

    3. Will our standalone app running at the same time Communicator is running cause any potential issues or system resource conflicts?

    We are NOT using Windows control.

    Here is our environment:

    Windows 10 – Eye Series I-12
    Communicator 5
    Our App is a standalone .NET

    Please email me at kbraswell@smarthomesolutions.com or call @ (205) 868-9311 with any questions.


    Profile photo of Grant [Tobii]
    Grant [Tobii]

    Hi @kevinbrasswell, I am afraid the the Gaze SDK has been deprecated some time ago now and is no longer provided or supported by Tobii. Whilst we are intending on providing a replacement for the Gaze SDK in the future for the Tobii Tech range of eye trackers, it’s functionality will not necessarily be extended to assistive devices such as i-series.

    That being said, your case may merit special consideration so I have emailed you personally the contact you should speak to at Tobii Dynavox about this issue.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.