Home
Downloads
Reviews
Register
Screens
Support
FAQ
Connecting
Get Started
E-mail
History

ScopeDriver

AquilaDigital
Partnership
Main Page

Search


ScopeDriver
Home
Reviews
Screens
Connecting
Downloads
Store
History
Support

ScopeDriver ©2001–2009 Stephen E. Hutson, All Rights Reserved

Technical Support — The ScopeDriver FAQ

The ScopeDriver FAQ (Frequently Asked Questions)

All of the information in the FAQ is on this page, to facilitate searching with your web browser. Click a topic below to jump to that topic’s position on this page.

Back to Support Main
Back to the Main Page

Contents

Installing and Connecting to a Telescope

Using ScopeDriver with Your Telescope



Back to Contents
Top of Page

When opening the installer, I get the message “ScopeDriver appears to be running from a compressed archive,” and it won’t let me proceed.

ScopeDriver brings up that message on Windows if it detects that it is being launched from the “Temporary Directory” or “Temp” directory. This usually happens when Windows shows you the contents of the .zip file, but hasn't decompressed them. In this case, you should right-click on ScopeDriver’s .zip archive and do an “Extract All” to the desktop or any other non-temporary directory.

If that’s not the issue, try creating a new directory named anything you want, then make a new subfolder inside that directory, and place the Installer and Installer Data files inside there. ScopeDriver only checks the names of the Installer’s parent folder and its enclosing folder to produce that error, so that should fix it.

This error should not occur on a Macintosh computer.

Back to Contents
Top of Page

I am receiving a message about Duplicate ScopeDriver Folders.

ScopeDriver has been designed so that you may easily move its installation between a laptop and a desktop computer, since it contains all of the data you have added inside the “ScopeDriver Data Folder.”

If you have more than one copy of ScopeDriver on your computer, both copies of ScopeDriver will have their own independent ScopeDriver Data Folders — one ScopeDriver Data Folder alongside one copy of ScopeDriver, and the other ScopeDriver folder alongside the other copy of ScopeDriver.

The solution is to place both copies of ScopeDriver in the same folder, so that both may share the same ScopeDriver Data Folder. You may need to rename one of them so that they may both coexist in the same folder.

When ScopeDriver detects duplicate ScopeDriver installations, the window displays recommendations based on the amount of customized data in each of your ScopeDriver Data Folders (comets and asteroids, User Objects, Sites, etc.) — and recommends which ScopeDriver installation you should keep.

Back to Contents
Top of Page

How do I connect my computer to my telescope?

We have created a support page which deals exclusively with this question. Click here to open that page.

Back to Contents
Top of Page

I try to click on a window’s controls in Mac OS 10.5.2, but nothing happens.

This seems to be a bug in Mac OS X 10.5.2, since it affects many application programs. We have created ScopeDriver 3.1.1 to fix this issue, and it is available at our downloads page. Windows users do not need this update.

You have encountered this bug — and should download the update — if you have experienced the following issue: The symptom of this problem is that a sheet window slides down normally inside its parent window, but you are unable to click on any of the sheet window’s controls. Keyboard shortcuts and commands continue to work normally.The situation only manifests itself if a sliding sheet window opens while a floating window is already on the screen. The two should be able to coexist peacefully, but for some reason this isn't happening in Mac OS X 10.5.2.

There are several floating windows in ScopeDriver for Mac OS X:

If a sheet window opens — and one of the above windows is open — you will be unable to click on the sheet window’s controls under Mac OS 10.5.2 until you download the update.

The update adds the following behavior to ScopeDriver for Mac OS X: Before a problematic sliding window opens, ScopeDriver temporarily closes all floating windows. ScopeDriver again shows the floating windows when the problematic sheet window closes.


Back to Contents
Top of Page

Some of my User Data (comets, sites, objects, etc.) is missing.

This is usually the result of having more than one ScopeDriver Folder. It is discussed at length above.

Back to Contents
Top of Page



I receive a message about multiple instances running.

ScopeDriver only allows one copy of itself to be running at any one time. This is because, on Windows, double-clicking an Observing List will normally open a new instance of ScopeDriver on Windows.

If you need to run more than one instance of ScopeDriver at the same time, hold down the ALT key while opening each instance of ScopeDriver. Note that both copies will share the same preferences file.

Back to Contents
Top of Page



ScopeDriver crashes or unexpectedly quits.

This may occur if ScopeDriver’s preference file becomes damaged, especially if the problem occurs at program launch. Open the Startup Preferences window as follows:

This will display the Startup Preferences window. Click to select the option Reset all preferences, then click the Save/Quit button and try launching ScopeDriver again.

Note that this procedure will cause ScopeDriver to use all default preferences for window positions and program settings.

If using the Startup Preferences window to reset the preferences does not work — or if ScopeDriver crashes before it even can display the window, you may manually delete the two ScopeDriver preference files from the below locations:

If ScopeDriver fails to successfully start up, the program will present a “Crash Detected” dialog the next time it is launched. Clicking this dialog’s Startup Prefs button will automatically open the Startup Preferences window with the Reset all preferences option selected.

Back to Contents
Top of Page



ScopeDriver “freezes” as it opens, or when connecting to a telescope.

Historically, the most frequent cause of freezes or hangs has been conflicting third-party software (such as anti-virus programs that keep files open, fax or modem software that keep ports open, etc.). These and other incompatibilities can sometimes be isolated by restarting in Safe Boot Mode and running ScopeDriver or the ScopeDriver Installer from there. Windows users can restart in Safe Mode by holding down [F8] as you restart; Mac users can hold down the [SHIFT] key as the machine reboots.

If ScopeDriver installs and/or launches in Safe Boot Mode, this usually indicates a software conflict, since the conflicting software is being disabled when running in Safe Boot Mode.

If all works well in Safe Boot Mode, we usually find that ScopeDriver is freezing when it is building its serial ports list. The most common reasons are outlined below:

As ScopeDriver launches, it may also freeze if its preference files become damaged. You may reset the preferences as described in the section ScopeDriver crashes or unexpectedly quits, above.

Back to Contents
Top of Page



I have received an error message about a “busy” window

This is especially likely to occur on Mac OS X, where modal dialogs that are specific to a certain window (for example, the “Save changes?” dialog) are shown as “sheet windows” within their parent window.

Sheet windows do not halt program operation on Mac OS X; they instead simply prevent interaction with their parent window until the sheet window closes. Because of this, you may continue working in other ScopeDriver windows, even though a sheet dialog present in another window.

Sometimes, ScopeDriver may need to access a window that is currently displaying a Mac OS X sheet dialog. When this occurs, ScopeDriver presents an error message, brings the window and its sheet dialog to the front, and asks you to resolve the situation before trying again.

Back to Contents
Top of Page



I can’t quit the program in Windows.

ScopeDriver contains code to ensure that at least one menu-containing window is open at any given time. Sometimes, this feature can prevent ScopeDriver from properly quitting. Simply hold down the SHIFT key as you quit to override this function.

Back to Contents
Top of Page



Some of ScopeDriver’s time displays are incorrect, or incorrect UTC Times are populated for new Observing Log entries.

In order for ScopeDriver to correctly determine your GMT offset and sidereal time offset, it must first connect to a telescope. ScopeDriver then stores the last known GMT and sidereal time offsets for use when no telescope is connected.

If you enter Test Mode or create a new Observing Log entry — and have never connected to a telescope — ScopeDriver will be unable to determine these time values, and will usually substitute your local time instead. Once you connect to a telescope, ScopeDriver will save the instrument’s time settings for future commands, even those that require no connection.

To set the correct time before you ever connect to a telescope, first enter Test Mode by clicking the Test Mode button in the Connect window, then open the Time and Location window by selecting Time and Location... from the Telescope menu. In the Time and Location window, you may enter your longitude and latitude, then click the Sync. to Computer button to save your location and time offsets.

Back to Contents
Top of Page



ScopeDriver’s azimuth display isn’t working.

Some Autostar firmware releases contain a bug whereby some models will report their azimuth value in hexadecimal. Later firmware revisions correct this issue.

Some Gemini telescopes report the telescope’s current altitude, but not its azimuth. When connected to such a Gemini, the azimuth display simply reads “< unknown >.”

Back to Contents
Top of Page



I’m having trouble importing “elements” strings.

ScopeDriver is very particular about the format of elements strings that you import into an Observing List or from a text file. If any value is out of range or in the wrong order, ScopeDriver will refuse to load it, since it could cause problems later on.

The format of the element string is documented in the table “Orbital Element Format,” in the ScopeDriver User Guide.

To troubleshoot a problematic elements string, try the below procedure:

Back to Contents
Top of Page



The Connect window sometimes appears when I close a ScopeDriver window.

On both Macintosh and Windows, the Connect window appears when a connection is closed, and so may appear briefly even when the program is quitting.

ScopeDriver for Windows includes special code that helps ensure that at least one menu-containing window is open at all times. Otherwise, it would be possible to enter a state where no menu-containing windows are open, limiting program operation.

When the last window containing a menu closes, ScopeDriver detects this and opens the Connect window, so that you will be able to access the application’s menu system.

Back to Contents
Top of Page



I receive an error about communication failures, experience occasional disconnects, or my telescope behaves erratically.

ScopeDriver is designed to allow “non-fatal” communication failures between your computer and telescope. A non-fatal failure is one that does not result in program instability or complete loss of telescope control.

Should ScopeDriver detect five or more non-fatal failures in a five-minute period, a dialog will appear, warning you about Excessive Communication Failures. If ScopeDriver cannot re-establish communication with your telescope in a reasonable period of time, the program will report that the connection with your telescope has been lost, and the Main Window will close.

First, make sure that you have selected the correct model of telescope in the Connect window.

You should also ensure that the checkbox labeled Increase Responsiveness in the Connect window is not selected. Uncheck Increase Responsiveness, cycle the power on your telescope and connect again.

If the above suggestions do not help, check to ensure that your serial connections are reliable. Check all cabling and adapter settings (including any driver software).

In addition to what is listed above, frequent communication failures could also indicate the following:

If your telescope still loses connection or behaves erratically, it is possible that your telescope is receiving commands too rapidly. Try slowing down the command rate by opening the Startup Preferences window as described above, and specifying a higher Command Buffer and/or Character Buffer value. Please note that increasing these values can slow down program operation, so use the lowest value that results in reliable operation.

Back to Contents
Top of Page



ScopeDriver doesn’t respond to the arrow keys on my keyboard, or some key presses are not recorded.

Some machines and computer models require that ScopeDriver more aggressively poll the keyboard. To do so, enable the Increase Keypress Responsiveness startup preference in the Startup Preferences window, opening the window as described above.

Back to Contents
Top of Page



I receive error messages when I try to perform an Internet update check.

Most often, such errors are the result of an inactive Internet connection. Try your web browser to see if you can connect to web pages. If so, then it is possible that your firewall or other software/hardware is interfering with the update and needs to be re-configured. ScopeDriver uses the http protocol to perform its update checks.

It is also possible that there is a problem with ScopeDriver’s update server. In this case, trying again later may allow successful update checks.

Back to Contents
Top of Page



I receive error messages when I open the program.

If you have ScopeDriver set to automatically check for updates at launch, and an Internet connection cannot be established, then ScopeDriver will present an error message. This message, however, will allow you to continue starting ScopeDriver.

There may also be a problem with one or more of the support files that ScopeDriver checks as it starts up. Try dragging ScopeDriver to the desktop and relaunching it. If the problem disappears, one of the support files may be too large or damaged. Be sure to return ScopeDriver to its original location after testing!

It is also possible that the file “ScopeDriver Preferences (3)” has become damaged. In Mac OS X, “ScopeDriver Preferences (3)” is located in the active User’s “Library” folder, in the “Preferences” folder. In Windows, it is in the Windows directory or the “Application Support” subdirectory of your user account.

Try the following:

The “ScopeDriver Preferences (3)” file must remain unlocked and in place while you use the program; otherwise, ScopeDriver will be unable to write preference information, and an error message will be generated.

Back to Contents
Top of Page



I receive error messages when I quit the program.

See the above discussion concerning the file “ScopeDriver Preferences (3).” Your startup disk must be writable (i.e., it cannot be a CD-R or other read-only medium). Otherwise, ScopeDriver will be unable to save preference information when you quit the program, and an error message will appear.

Back to Contents
Top of Page



I receive error messages while using the program.

If ScopeDriver reports an error while you are using the program, one of the following is likely to be true:

Make sure that ScopeDriver and its support files are installed on an unlocked disk, and that you have started your computer from an unlocked, writable startup disk.

If you believe you have found a bug in the program, let us know! ScopeDriver contains hundreds of thousands of lines of programming code, and it is unrealistic for us to expect that we have anticipated every possible situation. If the situation is repeatable, please outline the steps that are required to reproduce the problem.

Back to Contents
Top of Page



I’ve entered User Objects, but I can’t locate the new entries in the Find Object window.

Make sure the data you’re entering in the Find Object window is accurate. Also, be certain that you’re not using Begins With when you desire Contains.

You may also check to ensure that you have installed only one copy of ScopeDriver. Launching a different copy (in a different folder) will cause ScopeDriver to utilize different data files. This is described here.

Back to Contents
Top of Page



I receive an error message or unexpected behavior when I try to slew to a Land Object.

Objects referenced by altitude and azimuth are fully supported only on the LX200 Classic. If you are using a different telescope model, you may receive error messages.

Back to Contents
Top of Page



Portions of the Main Window appear blank.

This may occur with certain combinations of video drivers and software. Force the Main Window to redraw by clicking in a non-control area of the window while holding down the SHIFT and OPTION/ALT keys.

Back to Contents
Top of Page





Page updated Tuesday, December 16, 2008 7:10 PM