Forum Replies Created
- Posts
For those of you following at home :-), the solution is below:
The i12+ & PCEye Mini, with TGIS installed, do not have a ‘Tobii Engine’ running. Therefore if you call tobii_engine_create, it fails. If Windows Control 2 is installed, ‘Tobii Engine’ comes along with it and it works.
It turns out there are two ways to enumerate Tobii devices through the SDK, one uses the engine (tobii_enumerate_devices) and one enumerates them directly (tobii_enumerate_local_device_urls). You need to detect if the tobii_engine is running or not and change which API call you make.
– Jay
Confirmed that if I install TobiiDynavox_WindowsControl_Bundle_2.0.12.4456 on the device, now the Stream Engine SDK will work on it. This software seems to add the equivalent of the Tobii 4c Gaming software package.
Is the solution simply to ask people to install the 4C Gaming software on top of their iSeries 12+ or PC Eye Mini devices?
Thane, we’re following the same path. To date we haven’t found a good answer. The approach we’re working on right now is to use the Gaze SDK for both the I series and the EyeX. However the results of the eye gaze data we’re receiving on the EyeX devices through the Gaze SDK is significantly inferior to what we received when using the EyeX SDK.
We did try running EyeX applications side by side with the PC Eye Go environment (also Gaze SDK based, sensor is very similar to the I series as I understand it). This worked somewhat, but we got reports back from our beta users that the quality of the eye gaze decreased in the PC Eye Go applications while an EyeX application was running. Once the EyeX application was exited, the quality would come back to ‘normal’. Our conclusion was that this wasn’t going to be a feasible path.
– jcb
From what I read above, if we install the EyeX Runtime on a PC Eye Go user’s computer, we may be leaving them in a state where their calibration becomes unreliable due to race conditions between the two engines. Tobii has not tested this scenario, so the outcome is uncertain.
Are you considering testing this scenario? This leaves us in a difficult situation.
– jcb
I’ll give it another shot with the latest installer.
Have you done a compatibility test pass on installing the EyeX on top of an existing PC Eye Go environment? We’re nervous that adding the EyeX runtime could disrupt the behavior of the PC Eye Go Accessibility suite and this could be very difficult for users constrained to just eye gaze.
Thanks for the help. Between this and another email I received, I got it working. In addition to this, I also had to install Bonjour for Windows (http://support.apple.com/kb/DL999) to enable Eye Tracker Browser to find the PC Eye Go.
I now have firmware v1.2.2 running. Now to get back to testing the Gaze SDK!
2014 is going to be an amazing year for Eye Trackers, I just know it!
And to start that off, bumping this thread about updated firmware for the PC Eye Go back into consciousness 🙂
– jcb
I am attempting to do the same. I have a PC Eye Go installed along with Gaze Interaction Software 2.6.2.7. The same system also has the EyeX SDK 1.0 installed on it and has had an EyeX attached.
When I visit Gaze Interaction Settings -> System Information, Eye tracker firmware version: remains blank and the Upgrade button remains disabled. The PC Eye Go is working with the Gaze Interaction Software and it show up in the Windows Device Manager under Network Adapters.
When I run:
fwupgrade –auto –info-only
I get back:
205 No eye tracker could be foundMy goal is to get the PC Eye Go working so I can write software that works with both it and the EyeX.
What should I do for next steps?