-
Search Results
-
In reply to: MKS6000 Factory Update: Mount not homing
ullrichdittler
Hello Thomas,
Thank you very much for your answer.
The values RA: 3147 Dec:870 can be saved (via the button “Save o Bisque TCS”) and read out again after restarting the mount and the PC (“Get from Bisque TCS”): The saving of the data seems to work.
But homing the mount did not work: Only the RA axis moves when I start the home process and ends with one “peep”. The DEC axis does not move at all. The Sky shows: “not homed”
Can the behavior be caused by software settings?
Or would a remote access to the PC and to The Sky be helpful?Please let me know what information you still need to solve the problem.
Best regards,
Ullrich
—————-
For information, here are the parameters of the mount:
TheSky Version 10.5.0 Build 14036 (64 bit)
Date: Juni 30, 2026
Time: 18:59:15Motor firmware: 6.0.176
I/O firmware: 6.0.508
On-axis version, HA: 12, Dec: 12Bisque TCS Parameter HA Value Dec Value
——————————— ————- ————–
MKS_INDEX_ANGLE , 3140 , 870
MKS_UNIT_ID_ , 100 , 100
MKS_ACCELERATION , 600 , 600
MKS_HOME_VEL_HI , 1300000000 , 1300000000
MKS_HOME_VEL_MED , 150000000 , 150000000
MKS_HOME_VEL_LOW , 5900000 , 5900000
MKS_HOME_REQD , 1 , 1
MKS_HOME_JOYSTICK , 1 , 1
MKS_HOME_INDEX_OFFSET , 1995 , 35
MKS_CREEP_RATE , 0 , 0
MKS_GUIDE_RATE , -700959 , 700959
MKS_EMF_CONSTANT , 20 , 20
MKS_MAX_SPEED , 1926000000 , 1926000000
MKS_BASE_RATE , -44861734 , 0
MKS_MIN_POS_LIMIT , -5750000 , -8500000
MKS_MAX_POS_LIMIT , 1750000 , 2500000
MKS_PEC_RATIO , 8 , 8
MKS_HOME_DIR , 1 , 1
MKS_HOME_SENSE , 1 , 1
MKS_HOME_MODE , 2 , 2
MKS_HOME_IN_OUT_IN , 1 , 1
MKS_PEC_CUTOFF_SPEED , 0 , 0
MKS_MAX_VOLTAGE , 15 , 15
MKS_MAX_GAIN , 150 , 150
MKS_MAX_POS_ERROR , 2000 , 2000
MKS_JOY_CENTER , 1857 , 1860
MKS_MOTOR_FIELD_VOLTAGE , 8 , 8
MKS_POLE_COUNT , 4 , 4
MKS_ENCODER_COUNT , 4000 , 4000
MKS_COEFD , 3 , 3
MKS_MAX_INTEGRAL , 1280 , 1280
MKS_SMALL_STEP , 5 , 5
MKS_COEFF_I , 250 , 250
MKS_COEFF_P , 128 , 128
MKS_DERIV_MAX , 128 , 128
MKS_MOTOR_TORQUE_ADV , 200 , 200
MKS_ONAXIS_A1 , 0 , 0
MKS_ONAXIS_M1 , 0 , 0
MKS_ONAXIS_A2 , 67108864 , 67108864
MKS_ONAXIS_M2 , 6000000 , 6000000
MKS_ONAXIS_LP_COEF , 128 , 128
MKS_ONAXIS_MAX_POS_ERR , 10002 , 10002
MKS_ONAXIS_PEC_STEP_SMALL_P8 , 20 , 20
MKS_ONAXIS_PEC_STEP_BIG_P8 , 300 , 221
MKS_ONAXIS_PEC_DEADBAND_TICKS , 120 , 250
MKS_ONAXIS_PEC_SMALLSTEP_DEADBAND_TICKS, 4 , 20
MKS_ONAXIS_PEC_SMALLSTEP_PROPGAIN , 300 , 50
MKS_ONAXIS_PEC_SMALLSTEP_TRANS_SPEED, 1093504 , 2523470
MKS_ONAXIS_ENCODER_COUNT , 67108864 , 67108864
MKS_ONAXIS_ECCENTRIC_ANGLE_DEGS , 0 , 0
MKS_ONAXIS_ECCENTRIC_DIST_TICKS , 0 , 0
MKS_ONAXIS_DIRECT_ENC_POS , 0 , 0
MKS_ONAXIS_TICKS_TO_PLUS_LIMIT , 15741316 , 15741316
MKS_OTHER_MAX_CURRENT_MA , 950 , 950
MKS_OTHER_MOTOR_INDEX_POLARITY , 1 , 1
MKS_USER1_TICS360 , 12000000 , -12000000
MKS_USER1_dEXPECTED_HOME , 2.0000000 , 0.0000000
MKS_USER1_dHOME_SENSOR , 2.0000000 , 0.0000000
MKS_USER1_dBASE_RATE_PERC , 100.0000000 , 0.0000000
MKS_USER1_dCREEP_RATE_ASPS , 0.0000000 , 0.0000000
MKS_USER1_dGUIDE_RATE_FACT , 0.4999960 , 0.4999960
MKS_USER1_dMAX_SLEW_PERC , 90.0000000 , 90.0000000
MKS_USER1_NMOUNT_TYPE , 0
MKS_USER1_SYNC_VERSION , 10000
MKS_USER2_NVERSION , 0
MKS_USER2_FOCUS_AXIS , 1
MKS_OTHER_MOUNT_ID , Paramount MX
MKS_OTHER_DEBUG_OUTPUT , 0
MKS_OTHER_STARTUP_JS_RA , 0
MKS_OTHER_STARTUP_JS_DEC , 0
MKS_OTHER_STARTUP_JS_BUTTON , 0
MKS_OTHER_STARTUP_JS_GUIDER , 0
MKS_OTHER_SOUND_GUIDER , 0
MKS_OTHER_GP_IO_1 , 0
MKS_OTHER_GP_IO_2 , 0
MKS_OTHER_GP_IO_3 , 0
MKS_OTHER_GP_IO_4 , 0
MKS_OTHER_JOY_RATE_1 , 0
MKS_OTHER_JOY_RATE_2 , 0
MKS_OTHER_JOY_RATE_3 , 0
MKS_OTHER_JOY_RATE_4 , 0
MKS_INI_FOCMULT , 1
MKS_INI_FLIPHA , 0.0000000
MKS_INI_SPEEDPERC , 60
MKS_INI_SPEEDTHRESH , 5
MKS_INI_KERNEL_STATE , 0
MKS_INI_CALLLEVELLOGGING , 0
MKS_INI_PACKETLEVELLOGGING , 0
MKS_INI_FOCUSPULSESLOW , 60
MKS_INI_FOCUSPULSEFAST , 200
MKS_INI_HOMEAFTERCONNECT , 0
MKS_INI_SHOW_LIMITS , 0
MKS_INI_LOG_SLEWS , 0
MKS_INI_PPEC_HARMONICS , 2
MKS_INI_PPEC_RATIO1 , 1.0000000
MKS_INI_PPEC_RATIO2 , 8.0000000
MKS_INI_PPEC_RATIO3 , 1.0000000
MKS_INI_PPEC_SCALE , 1.0000000
MKS_INI_PPEC_TEETH , 375
MKS_INI_PPEC_PERIODS , 1
MKS_INI_PROHIBIT_TRACKING_BELOW_HZ, 1Lorenz
Hi Steve,
I’m using solely TheSky to control my PME II.
Last Sunday, I only sent the park command to the mount. After a few seconds in the parked position, the DEC axis moved to seemingly 0° declination, then there was a beep (same as when homing normally, but only one beep). After that, I sent a park command (not sure if I had to unpark first…), then the DEC axis moved north again until reaching the park position.
The only other ‘electric’ happening prior, was the closing movement of my telescope cap, but this device has been in service for ten years without ever causing any strange behaviour of the paramount. The cap reached the closed position approx. at the same time as the mount reached its park position.
I still don’t trust my DEC motor anymore (see previous posts). Mount seems to work (in general) after I fiddled a bit with the connection to the DEC extension cable…since then, the index angle measurements seem to be consistent…
Here are my parameters (no changes since the very odd occurrence homing DEC out of parked position).
TheSky Version 10.5.0 Build 14036 (64 bit)
Date: April 30, 2026
Time: 21:22:24Motor firmware: 6.0.176
I/O firmware: 6.0.508
On-axis version, HA: 12, Dec: 12Bisque TCS Parameter HA Value Dec Value
——————————— ————- ————–
MKS_INDEX_ANGLE , 197 , 201
MKS_UNIT_ID_ , 100 , 100
MKS_ACCELERATION , 500 , 500
MKS_HOME_VEL_HI , 1200000000 , 1200000000
MKS_HOME_VEL_MED , 120000000 , 120000000
MKS_HOME_VEL_LOW , 5900000 , 5900000
MKS_HOME_REQD , 1 , 1
MKS_HOME_JOYSTICK , 1 , 1
MKS_HOME_INDEX_OFFSET , 0 , 0
MKS_CREEP_RATE , 0 , 0
MKS_GUIDE_RATE , -1211252 , 998860
MKS_EMF_CONSTANT , 53 , 53
MKS_MAX_SPEED , 1260000000 , 1260000000
MKS_BASE_RATE , -77521077 , 0
MKS_MIN_POS_LIMIT , -9072000 , -10650000
MKS_MAX_POS_LIMIT , 2160000 , 3325000
MKS_PEC_RATIO , 9 , 9
MKS_HOME_DIR , 1 , 1
MKS_HOME_SENSE , 1 , 1
MKS_HOME_MODE , 2 , 2
MKS_HOME_IN_OUT_IN , 1 , 1
MKS_PEC_CUTOFF_SPEED , 0 , 0
MKS_MAX_VOLTAGE , 15 , 15
MKS_MAX_GAIN , 120 , 120
MKS_MAX_POS_ERROR , 2000 , 2000
MKS_JOY_CENTER , 1853 , 1860
MKS_MOTOR_FIELD_VOLTAGE , 8 , 8
MKS_POLE_COUNT , 8 , 8
MKS_ENCODER_COUNT , 4000 , 4000
MKS_COEFD , 8 , 8
MKS_MAX_INTEGRAL , 1280 , 1280
MKS_SMALL_STEP , 5 , 5
MKS_COEFF_I , 256 , 256
MKS_COEFF_P , 256 , 256
MKS_DERIV_MAX , 256 , 256
MKS_MOTOR_TORQUE_ADV , 200 , 200
MKS_ONAXIS_A1 , 0 , 0
MKS_ONAXIS_M1 , 0 , 0
MKS_ONAXIS_A2 , 67108864 , 67108864
MKS_ONAXIS_M2 , 6000000 , 6000000
MKS_ONAXIS_LP_COEF , 128 , 128
MKS_ONAXIS_MAX_POS_ERR , 10002 , 10002
MKS_ONAXIS_PEC_STEP_SMALL_P8 , 20 , 20
MKS_ONAXIS_PEC_STEP_BIG_P8 , 300 , 221
MKS_ONAXIS_PEC_DEADBAND_TICKS , 120 , 250
MKS_ONAXIS_PEC_SMALLSTEP_DEADBAND_TICKS, 4 , 20
MKS_ONAXIS_PEC_SMALLSTEP_PROPGAIN , 300 , 50
MKS_ONAXIS_PEC_SMALLSTEP_TRANS_SPEED, 1093504 , 2523470
MKS_ONAXIS_ENCODER_COUNT , 67108864 , 67108864
MKS_ONAXIS_ECCENTRIC_ANGLE_DEGS , 0 , 0
MKS_ONAXIS_ECCENTRIC_DIST_TICKS , 0 , 0
MKS_ONAXIS_DIRECT_ENC_POS , 0 , 0
MKS_ONAXIS_TICKS_TO_PLUS_LIMIT , 15741316 , 15741316
MKS_OTHER_MAX_CURRENT_MA , 950 , 950
MKS_OTHER_MOTOR_INDEX_POLARITY , 1 , 1
MKS_USER1_TICS360 , 20736000 , -17100000
MKS_USER1_dEXPECTED_HOME , 2.0000000 , 0.0000000
MKS_USER1_dHOME_SENSOR , 2.0000000 , 0.0000000
MKS_USER1_dBASE_RATE_PERC , 100.0000000 , 0.0000000
MKS_USER1_dCREEP_RATE_ASPS , 0.0000000 , 0.0000000
MKS_USER1_dGUIDE_RATE_FACT , 0.4999939 , 0.4999927
MKS_USER1_dMAX_SLEW_PERC , 70.0000000 , 70.0000000
MKS_USER1_NMOUNT_TYPE , 0
MKS_USER1_SYNC_VERSION , 10000
MKS_USER2_NVERSION , 0
MKS_USER2_FOCUS_AXIS , 1
MKS_OTHER_MOUNT_ID , Paramount ME II
MKS_OTHER_DEBUG_OUTPUT , 0
MKS_OTHER_STARTUP_JS_RA , 0
MKS_OTHER_STARTUP_JS_DEC , 0
MKS_OTHER_STARTUP_JS_BUTTON , 0
MKS_OTHER_STARTUP_JS_GUIDER , 0
MKS_OTHER_SOUND_GUIDER , 0
MKS_OTHER_GP_IO_1 , 0
MKS_OTHER_GP_IO_2 , 0
MKS_OTHER_GP_IO_3 , 0
MKS_OTHER_GP_IO_4 , 0
MKS_OTHER_JOY_RATE_1 , 266478
MKS_OTHER_JOY_RATE_2 , 2519435
MKS_OTHER_JOY_RATE_3 , 66135168
MKS_OTHER_JOY_RATE_4 , 1211266828
MKS_INI_FOCMULT , 1
MKS_INI_FLIPHA , -0.2411778
MKS_INI_SPEEDPERC , 60
MKS_INI_SPEEDTHRESH , 5
MKS_INI_KERNEL_STATE , 0
MKS_INI_CALLLEVELLOGGING , 0
MKS_INI_PACKETLEVELLOGGING , 0
MKS_INI_FOCUSPULSESLOW , 60
MKS_INI_FOCUSPULSEFAST , 200
MKS_INI_HOMEAFTERCONNECT , 0
MKS_INI_SHOW_LIMITS , 0
MKS_INI_LOG_SLEWS , 0
MKS_INI_PPEC_HARMONICS , 2
MKS_INI_PPEC_RATIO1 , 3.0000000
MKS_INI_PPEC_RATIO2 , 9.0000000
MKS_INI_PPEC_RATIO3 , 1.0000000
MKS_INI_PPEC_SCALE , 1.0000000
MKS_INI_PPEC_TEETH , 576
MKS_INI_PPEC_PERIODS , 1
MKS_INI_PROHIBIT_TRACKING_BELOW_HZ, 1-
This reply was modified 2 months, 3 weeks ago by
Lorenz.
dale didomenico
I recently upgraded my MKS-4000 to MKS-6000 Kit on my Classic ME. Now, I get very poor tracking in RA. In rechecking my mount I also, noticed very strange behavior when reading my ME motor index values which can be 1000 count off of reading.
The combinations I get are listed below on different readings following the SB ME instructions for reading the indexes.
RA DEC
509 1198 1st read
1507 1197 2nd read
1506 196 3d read
597 198 forth read
Based on these changes the numbers either have an extra 1000 added to the value or subtracted from the final value. Either way, the values should only change by 1 or 2 according to SB docs, so not sure what’s going on here. I do the measurements in balance mode only. I read the belts do not need to be removed for the ME classic anymore when reading motor indexes.
I have tried testing the mount with either combination above for the indexes, then proceed to do a Tpoint run, APA then new Tpoint run and still get poor tracking with RA star trail oscillation.
The dynamics of my mount configuration is below…
Running Daily Build 10.5.0 13960 Latest, Motor Firmware 6.0.174, IO Firmware 6.0.506
The google drive below has my latest Tpoint run, PE log for load and inspection, RAW PE data and sample Fit file with 60 sec image with the star movement in RA direction.
https://drive.google.com/drive/folders/1ZnuWbOYb7l9Ij7gv6s8Y2ZN5exFU7RIT?usp=sharing
https://drive.google.com/drive/folders/1ZnuWbOYb7l9Ij7gv6s8Y2ZN5exFU7RIT?usp=sharing
-
This topic was modified 11 months, 1 week ago by
dale didomenico.
In reply to: Strange TSX error after MKS6000 Upgrade
Gene3
APA CLS success!
Hey Tom- The build on my Series 6 MyT was 13936. I updated it to the latest (13954) and APA works perfectly. I did a 64 point Tpoint model which got me a Sky RMS of 8.0. I then did APA with CLS and in less than 10 minutes I had it dialed in as “excellent” in AZ and ALT. 6 minute subs at FL of 1000mm were perfect! I am going to check daily builds more often (8 yrs and 4 Paramounts and I never realized…) Thanks for your help – Gene
Topic: SBIG 11000m Autoguider cable
1671chrisw
I have the MKS 6000 successfully installed. Where do I connect the AO/Scope cable from my SBIG 11000m as the new instrument panel doesn’t have a guider port any more. Or don’t I need it if I use “direct guide”. Thank you
admin
AN SBIG CAMERA FIELD OF VIEW INDICATOR IS NOT LISTED IN THESKY6
ISSUE
I want to create a FOVI based on the SBIG ST-11000 CCD (or other) camera, but it is not listed in the Detector Database list on the View > Field of View Indicators, Detectors tab.
RESOLUTION
The specifications for the SBIG STL-11000 (and other newer model SBIG cameras) are included with TheSky6 version 6.0.0.23 and later. Click here to download TheSky6 Update.
Note: In order to preserve your modifications to the detector geometry list, the file that contains new detector information is not updated automatically.
To update this file, replace the file named Detector Geometry.txt in the TheSky6's My Documents folder with the newer, updated version of this same named file in TheSky6's Data folder. See below for details on how to do so.
-
From Windows Explorer, navigate to the TheSky6's Data/User/Field of View Indicators folder, by default, it is located in the folder:
“C:/Program Files/ Software Bisque/TheSky6/Data/User/Field of View Indicators”
-
Select the file named Detector Geometry.txt and then click Edit | Copy.
-
Navigate to the folder “My Documents/Software Bisque/TheSky6/Field of View Indicators” and then click Edit | Paste.
-
When prompted to replace the existing file, click Yes.
If you've made changes to your list of detectors, and just want to add the SBIG STL-11000 (or other model camera) to your list of detectors, then edit “Detector Geometry.txt” in the “My Documents” folder and add the “STL-11000 + ST-237…” information from the “Detector Geometry.txt” file in TheSky6's Data/User/Field of View Indicators folder.
APPLIES TO
TheSky6 Professional Edition, TheSky6 Serious Astronomer Edition version 6.0.0.21 and earlier.
KEYWORDS
SBKB
Last Reviewed:
Software Bisque Knowledge Base Article – 1145
THESKY DISCONNECTS FROM THE TELESCOPE WHEN A PARALLEL CAMERA DOWNLOADS
ISSUE
When downloading an image with a parallel SBIG camera, TheSky may automatically terminate the link to the telescope with the error 213 “Error, poor communication, link automatically terminated.”
RESOLUTION
Two possible solutions are:
1. Turn on High Priority Downloads in CCDSoft. From the camera control window go to the Setup tab and place a checkmark next to “High priority downloads.”
Or
2. Configure TheSky to not automatically disconnect the telescope upon poor communications.
A. Go to Start, Run and type “Regedit” and press OK.
B. Navigate to the HKEY_CURRENT_USER/Software/Software Bisque/TheSky/TELESCOPE for TheSky version 5 customers or HKEY_CURRENT_USER/Software/Software Bisque/TheSky6/TELESCOPE for TheSky6 customers.
C. Select, Edit, New, DWORD value, for the Name type “AutoTerminateErrCnt” and for the value put in something larger than 3 which is the default (like 1000).APPLIES TO
TheSky Version 5
TheSky Version 6
CCDSoft Version 5KEYWORDS
SBKB
Last Reviewed: 11/24/2004
Software Bisque Knowledge Base Article – 1098
WHAT FORMS OF PAYMENT DOES SOFTWARE BISQUE ACCEPT?
ISSUE
What forms of payment does Software Bisque accept?
RESOLUTION
Software Bisque accepts the following methods of payment:
Form of Payment Description Credit Cards The Software Bisque Store accepts the following major credit cards on the Software Bisque Store. - Visa
- MasterCard
- American Express
- Discover
The Software Bisque store does not accept PayPal (we apologize for the inconvenience).
Checks or Money Orders Software Bisque accepts personal checks, checks from schools or other institutions (checks must be drawn on a U.S. bank) or money orders in US currency.
Please make checks payable to: Software Bisque, Incorporated.
What does 'A Check Drawn on a US Bank' mean?
Wire Transfers Software Bisque can arrange a wire transfer as payment for orders exceeding $1000.00 and does not charge additional fees for this method of payment.
Note that wire transfers can be expensive for both parties, as banks typically apply significant processing fees to both you and Software Bisque. Please contact your local bank or financial institution for details about the charges you will incur when perfoming a wire transfer.
Software Bisque can provide account routing numbers on request.
Please email the Software Bisque Front Desk to get started.
Thank you.
Faxed Purchase Orders Faxed purchase orders on school or institution letterhead. Terms are net 15.
Orders can be placed with Software Bisque using the following methods:
Web Orders Visit the Software Bisque Store to place a secure order (credit card required). Phone Orders Call Software Bisque at 1-800-843-7599 or (303) 278-4478 and request a product or upgrade. Facsimile Order Fax the information below to Software Bisque at (303) 278-0045 Mail Order Software Bisque
912 12th St
Golden, CO 80401-1114 USAPlease provide the following information when placing orders:
-
The name and the version of the product you currently own (upgrades only)
-
Serial number of this product (for software upgrades only)
-
Product to which to purchase
-
Your First and Last Name
-
Street Address
-
City, State or Province, Postal Code or Zip Code
-
Country (if outside USA)
-
Daytime phone number
-
Credit card number and expiration date. (Never send your unsecured credit card information via e-mail!)
Notes:
-
A security deposit is required when ordering certain hardware products, such as Paramounts.
-
Software Bisque uses UPS (United Parcel Service) for all shipments, unless otherwise specified. If you require a different shipping service, please specify the company name and the required delivery type (overnight, second day, ground, Saturday delivery, etc.) when placing your order. Web customers should enter this information in the “Special Instructions” text box when placing your order.
APPLIES TO
All Software Bisque products.
KEYWORDS
SBKB, contact, address, shipping, cost, delivery, method
Software Bisque Knowledge Base Article – 1084
“NO COMPATIBLE PROGRAM WAS FOUND” MESSAGE WHEN INSTALLING THESKY POCKET EDITION
ISSUE
I receive an error message “No compatible program with device was found” when installing TheSky Pocket Edition.
RESOLUTION
1. Download and install the latest version from http://www.bisque.com/pedl.
2. If the behavior persists, try to manually install TheSky Pocket Edition to the device.To manually install TheSky Pocket Edition to the mobile device:
TheSky Pocket Edition installer copies several “.CAB” files to your desktop computer, in the “C:/Program Files/Software Bisque/TheSky Pocket Edition” folder.
TheSky Pocket Edition .CAB Files:
TheSky Pocket Edition.PPC300_2577.cab
TheSky Pocket Edition.PPC300_4000.cab
TheSky Pocket Edition.PPC300_10003.caba. Use ActiveSync to manually copy the file with the “2577” number (the numerical code for StrongARM processors).
b. On the mobile device, Tap this file name (using the Start | Programs | File Explorer) to begin the installation.TheSky Pocket Edition will be installed to your device.
APPLIES TO
TheSky Pocket Edition and TheSky Pocket Edition with Pocket TPoint.
KEYWORDS
SBKB
Software Bisque Knowledge Base Article – 223
PRE-4000 B.C. SOLAR SYSTEM POSITIONS INCORRECT
ISSUE
When using TheSky to display positions of Solar System objects (e.g. planets), or star positions (relative to horizon), results are incorrect for ancient (pre-4000 B.C.) dates.
RESOLUTION
Early versions of TheSky v4.00 for Windows had a date limit of 4000 B.C. to A.D. 10000. By the release of v4.00.105, the date entry limit had been extended backward to 4712 B.C., however the computational algorithms still had the 4000 B.C. limit.
Because of this inconsistency, setting the date and time (Data, Site Information, Date & Time) to a year less than -4000 always gives the result for January 1 of 4000 B.C. (thus, changing the date within this range will not alter the Sky Display). When performing a Time Skip across this limit, results prior to -4001 will be treated as the year -4001.
This problem was corrected, and the date limit further extended to 4713 B.C. in TheSky v4.00.200. The user should obtain this, or a later version.
APPLIES TO
Time Skip
KEYWORDS
SBKB
This article was formerly published under the identifier Q447KB in Software Bisque’s prior knowledge base.
Last Reviewed: 11/24/2004
Software Bisque Knowledge Base Article – 224
THESKY DOESN’T ACCEPT YEAR 4713 B.C.
ISSUE
TheSky doesn’t accept the year 4713 B.C. (-4713) in the Data, Site Information, Date and Time tab sheet. It rolls over from -4712 to 10000, even though source algorithms allow 4713 B.C.
RESOLUTION
Early versions of TheSky v4.00 for Windows had a date limit of 4000 B.C. to A.D. 10000. By the release of v4.00.105, the date entry limit had been extended backward to 4712 B.C., however the computational algorithms still had the 4000 B.C. limit.
Because of this inconsistency, setting the date and time (Data, Site Information, Date & Time) to a year less than -4000 always gives the result for January 1 of 4000 B.C. (thus, changing the date within this range will not alter the Sky Display). When performing a Time Skip across this limit, results prior to -4001 will be treated as the year -4001.
This problem was corrected, and the date limit further extended to 4713 B.C. in TheSky v4.00.200. The user should obtain this, or a later version.
APPLIES TO
Time Skip
KEYWORDS
SBKB
This article was formerly published under the identifier Q448KB in Software Bisque’s prior knowledge base.
Last Reviewed: 11/24/2004
Software Bisque Knowledge Base Article – 115
IMAGE BUTTON NOT ENABLED FOR SOME NGCS
ISSUE
With the NGC pictures (Ngcpic.sdb) active, the Object Identification dialog does not have an available Image button (camera), even though there is an associated image.
This affects all NGC objects with a catalog number less than 1000.
Examples: NGC5, NGC991.
RESOLUTION
TheSky does not correctly associate NGC aliases with preceding zeroes. This will be fixed in a future release, however there is an immediate solution:
1. Obtain a modified Ngcpic.txt and Ngcpic.sdb file from Software Bisque.
2. Place the new Ngcpic.txt and Ngcpic.sdb files in your …/TheSky/database folder.
3. If your CD-ROM is not drive letter E, then you will need to edit the Ngcpic.txt file and search-and-replace all occurrences of “E:” with the correct drive letter, including the colon.
4. Use TheSky’s Data, Sky Database Manager, Add/Remove Databases command to remove the current Ngcpic.sdb (if added), then add the new …/TheSky/database/Ngcpic.sdb database in its place.APPLIES TO
General
KEYWORDS
SBKB
This article was formerly published under the identifier Q240KB in Software Bisque’s prior knowledge base.
Last Reviewed: 11/24/2004
-
This reply was modified 2 months, 3 weeks ago by
Viewing 12 results - 1 through 12 (of 12 total)
Viewing 12 results - 1 through 12 (of 12 total)