As mentioned above, that firmware update for the eye-tracking module is ONLY if your module does not show up as Droolon Pi1 Camera
The main problem is now with the calibration software and combination of 2 services that run connecting with each other and the pi_service service.
I’ve emailed Droolon the log files, perhaps others should email them their log files as well.
do you know what the filepath of the log is?
calibration software log is in:
*install_dir* \aSeeVR_UserSDK\runtime\apps\aSeeVRUnityCalibration
runtime is in:
*install_dir* \aSeeVR_UserSDK\runtime
Forward is in:
*install_dir* \aSeeVR_UserSDK\forward
there is definitely stuff going on here.
from the forward log
'[2020-08-24 16:49:03.751]: forward addr: 127.0.0.1:5100
[2020-08-24 16:49:04.772]: aSeeVR_connect_server: 0
[2020-08-24 16:49:04.774]: got coefficient!!!
[2020-08-24 16:49:04.774]: coefficient callback arrived.
[2020-08-24 16:49:04.774]: read coefficient: 1
[2020-08-24 16:49:08.607]: Server aSeeVR_start Failed
’
from the aseevrclient file in in calibration
,[2020-08-23 12:17:42.136]: 2 socket err: 10038 -1 2836
[2020-08-23 12:17:42.136]: 2 socket err: 10038 -1 2836
[2020-08-23 12:17:42.136]: 2 socket err: 10038 -1 2836
[2020-08-23 12:17:42.136]: 2 socket err: 10038 -1 2836,
I’m currently in contact with the 7invensun support and they shared now a kind of a guide:
Also Pimax contacted me proactively and asked if everything is ok with the eye tracker and they are about to ship me “additional new base components of eye-tracking from the factory” whatever this means.
I will continue troubleshooting later in the evening and keep you posted.
But… does it work?
for me it currently doesn’t work, the tracker is displayed as Droolon Pi1 but I (my camera) see no IR LED activity, also the green dots during the calibration just disappear. I will check for other sw which might interfere like Rusi recommended and maybe try with another PC this evening. So far I tried the basic stuff, other usb cables, ports, various eye distances from the glass etc.
sigh …
Could somehow the firewall interfere? Maybe worth a try…
Does it mean that an app called ”forward” that starts at the same time as aSeeVR is making an error trying to establish a connection?
I wouldn’t open that port.
I gave the firewall permission to the following three executable files.
[forward.exe,Runtime.exe(aSeeVR),aSeeVRUnityCalibration.exe]
im somewhat reassured by the large number of people who have this issue. something will surely have to be done.
Question
No Fixed Foveated rendering option on my pitool 263, is this normal?
The eye tracking show Doolon Pi1 in device mangaer.
When I try to calibration , it show green dot and disappeared, so I can’t calibrate.
I check the aSeeVRClient.log and no any detail inside.
forward log
[2020-08-26 08:28:24.387]: forward addr: 127.0.0.1:5100
[2020-08-26 08:28:24.391]: aSeeVR_connect_server: 0
[2020-08-26 08:28:24.393]: got coefficient!!!
[2020-08-26 08:28:24.393]: coefficient callback arrived.
[2020-08-26 08:28:24.393]: read coefficient: 1
[2020-08-26 08:28:29.241]: Server aSeeVR_start OK
[2020-08-26 08:31:23.422]: call aSeeVR_disconnect_server
aSeeVrCalibration.log
none
What software which can be used for test?
Can I buy the silver plate if I need to change the headset?
The plate come with the tape, so I remove it because I see the paper for removing and now I can’t detatch it right now because the glue, I forgot about changing the headset and I place the wrong position around 0.5 mm, I can’t move the position right now.
So I need to know that how I can buy the new silver plate @PimaxQuorra
Make sure you email a copy of the log files to the droolon email address. Perhaps if enough of us do this they will realise that there is a problem with the runtime.
what would this email address be , how did you open a support ticket
7invensun support just ask me for this log file to check - different errors in this log
$installdir$\aSeeVR_UserSDK\runtime\devices\Pimax\config\armeabi\log\UserSDK.log
will wait for their reply.
Where to send the log file to check?
open a support ticket, they will forward your problem to 7invensun support via email
I can’t even get it to run enough to generate the USerSDK.log file 
I found the issue to be my 50ft usb 2.0 extension to my other room, when I moved the hmd near to the pc and plugged the usb in directly to pc (usb 2.0 port), the calibration started to work.
However, 1 massive problem is, when I wear the hmd normally, my eyes is pretty much next to the ET glass, very close - and it doesn’t detect my pupils. It only works, when I pulled the hmd maybe half inch to 1inch away from my eyes, it started to work. and having the screen way from you that far, massive lost of FOV… and I am already using the comfort kit cushion, is that considered thick size? i dunno.
Maybe my face-shape is the issue here.
