Bah, my eye tracker turned up today, can’t use it with my 5k XR as the USB plug clashes with the 3d printed adapter for the vive DAS. Guess that’ll have to sit on a shelf until my 8KX turns up!
It seems that improvement is still needed… 
Not at all. I had that problem too. Use this adapter instead (only the top part):
If you got no printer surely someone close by can print you this. Takes 10 minutes to do since it is a very simple part.
5 Likes
I designed a new top strap adapter for the Vive DAS based on Drcube’s orignal design that works with the eye tracker which you can get the download link for at https://community.openmr.ai/t/pimax-8kx-with-eye-tracker-vive-das-original-front-cowling-vr-n-chill-and-usb-c-hub/29903?u=genesis
7 Likes
I received the files to update the eye tracker and my personal code but I can not extract UpdateFrimwareAssistant-Pimax.7z with it, Is there a generic password to extract the update files @rusi ?
Cheers,
Dennis
Got the eye tracker and installed the drivers via pitool but cant get the calibration to work at all. Green dots flash for a second and then nothing. Ive been trying all night with every configuration of pitool imaginable. It should not be this difficult to get this to work 
1 Like
There are two passwords.
- Compressed file password
- Password required for update
You have these two passwords in the mail you received.
(mail content)
Dear Customer,
①Connect Droolon Pi1 to the computer.
②Please use the attached Update tool to Update the firmware.（The unzip password is ####）
③Enter the upgrade code: @@@@@@@@
Please refer to the attached document for specific operation.
3 Likes
For those stuck at the initial recognition stage, I updated PiTool, then rebooted. It still didnt recognise the eye-tracker. I was able to get the download prompt by plugging the extra USB between the eye tracker and the port on the underside of the headset. It recognised it and then I was able to get the software.
As for anything else working. Nup, nothing… calibration hangs after the green dots disappear from the boxes, no red glow or anything from the leds on the tracker.
I’ve put a ticket in, will see what happens.
Another woeful product launch by Pimax…
[update]
They sent me a link to a video whoing how to install the eye-tacking module
[update2] when asked about which ports are required on 5k+
not both, only one USB-C port from top or bottom is OK
2 Likes
Thanks Rusi, they forgot the archive password in the initial email but now provided it.
1 Like
Received my eye tracking too, same issue where calibration do not work, the 2 green spot disappears. I too opened a ticket, waiting reply. May i ask how to check the ET firmware version? And which firmware version is the ones working?
From Droolon:
First, after plugging Droolon Pi1 into the computer, is there a camera named Droolon Pi1 in device Manager?
If a camera named Mobile VR is displayed in the device Manager, download and use the firmware update tool in the link below.
so, if you have a camera named Mobile VR in Dev mgr, you need to update the firmware.
I have the Droolon Pi1 Camera, and the firmware update doesnt run.
No news from Droolon about the calibration software or next steps to troubleshoot.
3 Likes
What is the password for the archive?
So people buy eye tracker from website and it literally does not work until you contact support to get personalized firmware AND there is no instruction at all that this was required.
So it is more like a developer prototype rather than a finished product.
Anyways, keep reporting on whether the eye tracking is worth it guys.
9 Likes
Yes and that’s what we call the Pimax experience. Even I am surprised of the lack of information or help coming from Pimax about this issue. The eye tracker could still turn out to be a great product we will just have to wait and see. Welcome to the Pimax experience 
8 Likes
Calibration still doesn’t work. I have since sent a support ticket to Pimax we will see how far that gets me.
same for me, fw was updated successfully and it now will be displayed as Droolon Pi1 in device manager and it will be recognised by Pitool but thats it, no lights no reaction during the calibration. If someone get it solved please post it.
The talk of passwords protecting the archive and installation sounds cumbersome, but also potentially heartening.
Must say I have been only too aware that the addition of eytracking and handtracking modules puts four cameras on your head, tracking you, your real environment, and how you respond to- and interact with the virtual environment.
I have been hoping to get to try the two out for a while, before the day comes when they are standard on every HMD, and I tape those cameras over, since at that point their imagery has come to go out to every Bezos, and every troll, and every identity thief, and every shady government, out there. 
Even with the camera feeds staying strictly on one’s machine, the resulting tracking data will have to go out, for a lot of online features, such as sharing your eye expression and pose with multiplayer friends, or telling an advanced 360 degree video server which part of the video to transmit at high quality for the moment. Any protection that limits who gets to receive such data would be welcome.
Of course… the Droolon password could of course be the very identifier by which you are snooped on.
1 Like
I have no ET but just wondering did you guys try that:
https://community.openmr.ai/t/eye-tracking-how/29987/12?u=teigue
https://community.openmr.ai/t/eye-tracking-how/29987/44?u=teigue
2 Likes
Yes I’ve spent hours trying every pitool configuration there is and moved my headset around in every position I could. Also reinstalled drivers and reinstalled pitool. The actual calibration software is locking up. When it starts you can see the “Unity” splash screen and that moves around when you move the headset around, but once the 2 green dots show up the entire program freezes.
I have no idea how some people have gotten it to work but it is NOT stable.
1 Like
Digging through the logs, looks like there is supposed to be a server of some sort on localhost, port 2001.
aSeeVRServer.log:
service addr: 127.0.0.1:2001
An error occurred while calling the ::bind function. local address: 127.0.0.1:2001 error: 10013
Service bind error: -7
aSeeVRClient.log
An error occurred while calling the ::connect function. remote address: 127.0.0.1:2001 error: 10061
connect server error: -6
2 socket err: 10038 -1 18446744073709551615
forward.log
forward addr: 127.0.0.1:5100
aSeeVR_connect_server: -1
So, the server is supposed to be started on port 2001, the forwarder looks like it then forwards something to the piServer on port 5100
Running TCPView from Sysinternals shows no server on port 2001, which matches the logs.
I’ve tried changing the server port from its config xml, and hooking it up with a change in forward’s config file but it appears that the calibration code is hard-wired to connect on port 2001 and doesnt work.
Anyone else getting similar logs?
5 Likes