Tuesday, August 18, 2020

Evscope Problems Outdoors

This is the dreaded and infamous "you are not connected" screen. Turning on the Evscope and checking the wifi connection did nothing to fix the problem.
Troubleshooting Begins
The Evscope was received on Monday afternoon and problems were noted that evening when taking the Evscope outdoors Monday night.

On Tuesday afternoon, the scope started to connect and it seemed it was working. However, Tuesday night led to problems again. At one point, it seemed to find Neptune with a lot of noise across the FOV, then immediately crashed and the image was lost forever. Thereafter, the telescope stopped booting, stopped connecting to the app, and was completely unstable and unusable. Both OPT and Unisteller were contacted on Tuesday. A telescope tech from OPT with Evscope experience immediately responded with email on Wednesday and we are setting up a time for an international phone connection for troubleshooting the telescope.

APP CONFUSION The app, during setup, it seemed to have this moment of confusion on the iPad (which does not have internet). First it asked to input the location manually and next it appeared to get location from "Location Services" and it asked for permission to share the location during app use. The latter is what transpired. Until a place in the menu is found to confirm the latitude and longitude, it won't be known if the values are correct. Later, the iPad app failed when the screens turned all white and the iPhone was used thereafter.
The telescope is extremely high tech and there's often no way of knowing what it's doing, calculating, or thinking during the required pauses of setup and/or operations. Without error reporting, other than a light color, the nonfunctional situation is clueless. The technical manual does not mention the points of boot time and other important operating aspects. Plus, there is no icon guide to the app. You need to ferret out the functions by trial and error and this is next to impossible when the app is locked up or not connected. Plus, when briefly connected, the actions are agonizingly slow, thus negating any surfing of functions. It's hoped there is a solution for this and there probably is.