Known Issues - Wink Machine Integration Guide
Can’t Auto Reconnect After Token Expiry
Token has an expiry. Currently, while using https.force, WINKpms can’t automatically re-connect. Users would need to re-enter their login credentials. This might not be good especially when the machine interface is run in unattended mode. In this case, the machine integration process would stop and the user wouldn’t even know about it. Some development work is needed for this. ETA for this unknown as of right now. In the meantime as a workaround, when the machine interface is not working properly, it is recommended to attend the program to see if the user interaction is required.
Can’t Auto Reconnect On Connection Failure
Prior to https.force, whenever there was a connection failure, the WINKpms would automatically reconnect without the user interaction. However, with the https.force, user interaction is needed to click the retry button. This might not be good especially when the machine interface is run in unattended mode. In this case, the machine integration process would stop and the user wouldn’t even know about it. Some development work is needed for this. ETA for this unknown as of right now. In the meantime as a workaround, when the machine interface is not working properly, it is recommended to attend the program to see if the user interaction is required.
Can’t Auto Retry https send
Prior to https.force, whenever there was an error on https send call, the WINKpms would automatically reconnect without the user interaction. However, with the https.force, user interaction is needed to click the retry button. This might not be good especially when the machine interface is run in unattended mode. In this case, the machine integration process would stop and the user wouldn’t even know about it. Some development work is needed for this. ETA for this unknown as of right now. In the meantime as a workaround, when the machine interface is not working properly, it is recommended to attend the program to see if the user interaction is required.
WinkEcommClient processcall Unauthorized Error even after token is valid
Process call is used to send the data to the backend in order for them to be saved. An unauthorized error happens during the processcall even when the token is valid. More investigation is needed to know the exact cause of this issue. Some development work is needed for this. ETA for this unknown as of right now.
Can’t import/pull Lensmeter Addition
While exporting the lensmeter data to WINK, WINK is not getting the values from the addition field in the data file. As a result, the addition value is not imported/pulled in the EMR under lensmeter tile. Fix for this has already been made. This fix is released in hotfix version 5.00.60.13 or version 6.
Can’t import/pull prism in Lensmeter and Subjective Refraction tile
While trying to import the exported data in EMR, the prism values are missing in EMR under multiple tiles like lensmeter and subjective refraction. Fix for this has already been made. This fix is released in hotfix version 5.00.60.12 or version 6.
Can’t import/pull Addition2 for varifocal lenses
While exporting the lensmeter data to WINK, WINK is not getting the values from the second addition field in the data file. As a result, the second addition value is not imported/pulled in the EMR under lensmeter tile. Logic to store addition2 in the database is already in place. However, some work to add the addition2 field in the EMR tile is still remaining. ETA for this unknown as of right now.
Can’t import/pull Autorefractor data in EMR when data exported from RT5100 device
After exporting the data from RT5100 to WINK, the user can’t import autorefractor data in the EMR. Fix for this has already been made. This fix is released in hotfix version 5.00.60.12 or version 6.
Incorrect measurement values imported for RT5100 data
While importing/pulling the data which was exported from Nidek RT5100, some of the values are incorrect. Left side eye data is also assigned to the right side eye for both the subjective refraction and final prescription. Fix for this has already been made. This fix is released in hotfix version 5.00.60.12 or version 6.
Machine Interface crash due to unaided data in RT6100
When RT6100 sends unaided data, the machine interface crashes. The cause of this is a bug in the RT6100 driver’s unaided data section. Fix for this has already been made. This fix is released in hotfix version 5.00.60.12 or version 6. For the meantime as a workaround, it is recommended not to send unaided data from the RT6100 phoropter.
Missing Sphere, NearSphere, and NearSphere2 values while importing data into WINK
The reason for this is that there are typos in those tags in Nidek_V1.00. In this version, Xml has “Sphare” as one the tags instead of being “Sphere” and so on with NearSphere and NearSphere2. Wink is looking for very specific tags and those tags are not in the xml as there are typos. As a solution, In the LM device, the setting should be changed from Nidek_V1.0 to Nidek_V1.1 on page 13 of the settings. Innova is well aware of this bug.
Comments