Quantcast
Channel: Main Sequence Software - Latest topics
Viewing all 8550 articles
Browse latest View live

Question on meridian flip logic

$
0
0

@chasmiller46 wrote:

I recently decided to try a night of imaging where I had two targets in a sequence file. The first target was acquired east of the meridian and the sequence performed an automated meridian flip with camera rotation properly and the target finished about 2AM. The scope was pointing to the north west at the end. The second target required the scope to point back to the east of the meridian and the scope did a "reverse" meridian flip, acquired the target (with camera rotation) and began tracking. However, immediately, the guiding began a "run away" so I stopped the sequence; performed a new calibration of PHD2 and resumed the imaging run without further problems.

Being 2AM, I did not take the time to trouble shoot the guiding issue but thinking about it later, it seems like PHD2 did not recognize that a reverse meridian flip had occurred and did not flip the calibration data.

I know that during the first meridian flip, SGP told PHD2 to reverse its calibration but I am thinking that when the second target was acquired, SGP may have not told PHD2 to reverse its calibration again.

PHD2 is connected to both the rotator and the mount but the option in PHD2 to flip the calibration data is unchecked since SGP is telling PHD2 to flip.

I did not bring any of the log files home with me but it seems like SGP did not tell PHD2 about the second meridian flip.

Charlie

Posts: 1

Participants: 1

Read full topic


Guider Never Reports "Settled"

$
0
0

@cgsathome wrote:

Hi guys,

Last night, I had a problem where the guider never settled and acquisition never started.

I have an STT-8300 with internal guider and use the SGP API to guide using PHD2. I have been using, with good success, settling settings of <0.5 pixels, option to "settle for" ticked and 6 seconds selected... I often use 4 second guide exposures.

Before last night my settling appeared to worked like this:

1) PHD would report distance away from being centered after each guiding frame (I often use 0.5 pixels)... this distance generally gets smaller with each report as it heads toward the threshold.
2) Once the threshold was reached, a countdown would start in the message bar reflecting how long the distance was below the threshold... I assume this is an SGP timer
3) If the countdown completed, the message bar showed a message "waiting for guider to report it has settled"
4) image acquisition would start

Last night:
1) same as above
2) Upon reaching threshold, nothing happened. Distances less than the threshold were continuously reported, but no countdown started and acquisition never started

I believe that I saw this behavior in all the versions listed below.

Unfortunately, my logs are something of a mishmash as I tried different combinations... I started off with 2.5.2.4. When I had a problem with that, I tried to upgrade to 2.5.2.5. Still no joy. Then I went back to 2.5.2.3 which I had successfully used on a number of nights. I was surprised to see that didn't work either.

Ultimately, in my late night delirium, I got a sequence to run. Unfortunately, I cannot identify what combination of reinstalls, reboots, power cycles and version changes enabled success, but the successful versions were SGP2.5.2.5 and PHD2.6.2. I also turned off the "settle time" tick box and typed "0" into the seconds field.

I suppose this might be peculiar to my setup, but since it seems like some of the recent betas were related to the SGP API, I wanted to report this in case it is helpful. I was also hoping someone might be able to take a look at the logs and see if they could help me figure what is going on.

Rather than include all the logs I have attached two, the last run that would not settle (which was 2.5.2.3) and the log from the successful run which was 2.5.2.5. If I can help further, I am happy to do that. I can also provide PHD2 logs, if helpful, but it seems like PHD is happily sending distances through all this, and maybe never gets asked to do anything else?

Best regards, and thanks!
Craig

Version info:

OS: Win 10 Pro Anniversary Update

SGP: 2.5.2.3, 2.5.2.4, 2.5.2.5

PHD 2.6.2, 2.6.2dev4

Last Run with no Settling

https://www.dropbox.com/s/dvmsh0h9o5pefnl/sg_logfile_20161024003111.txt?dl=0

Successful run

https://www.dropbox.com/s/dvmsh0h9o5pefnl/sg_logfile_20161024003111.txt?dl=0

Posts: 6

Participants: 3

Read full topic

Failed flip - need help disgnosing

$
0
0

@spokeshave wrote:

Two nights in a row now, my meridian flip has failed. I'm not sure I understand why. Seems like the mount flipped properly but I think it looks like PHD2 has trouble with the guide camera after the flip. Can someone take a look at the logs to help me diagnose? Any help is appreciated.

SGP log file:

https://www.dropbox.com/s/0yr03ncw9bcqxuo/sg_logfile_20161024185858.txt?dl=0

PHD log file:

https://www.dropbox.com/s/ufp41thcz8bhbdy/PHD2_DebugLog_2016-10-24_194254.txt?dl=0

Thanks.

Tim

Posts: 2

Participants: 1

Read full topic

AVX mount and NexRemote

$
0
0

@Debbie2317 wrote:

I was hoping someone could help me out connecting my AVX to SGP. My big question is whether to use NexRemote. The only way I can get it to connect is to attach the serial cable to the HC and then to the computer. If I try to use NexRemote, SGP won't connect to the mount. The com port box in the ascom driver settings window does not show an open com. If I close NexRemote it will allow me to select a com port. Am I missing something?

Posts: 6

Participants: 4

Read full topic

NGC 281 and NGC 891 near Paris

$
0
0

@Pulsar59 wrote:

Hello,

These two images with my reflector 250 f/4, Atik One and AZEQ6. All subs 300 s in bin 1x1.

NGC 281 : 3 hours Ha, 2,5 L, 3x30 min RGB.
NGC 891 : 4 hours L, 3x30 min RGB.

Posts: 3

Participants: 2

Read full topic

ZWO 224 camera fails to connect via ASCOM - need to reset camera device list

$
0
0

@johngwheeler wrote:

I have a ZWO 224MC which I'd like to use with SGP. I installed the ASCOM driver and this appears as an option in the camera drop-down list, and I can connect to it and set the camera gain etc.

However, I can't actually capture anything with the "frame & focus" tool or the main sequence. The camera works via SharpCap.

Any suggestions?

I did notice that two ASCOM entries appear in the drop-down. Could the ASCOM driver installation be corrupt?

Thanks,

John Wheeler

Posts: 2

Participants: 1

Read full topic

Dome geometry for Slaving - "off center" guide scope

$
0
0

@dnube wrote:

I'm reviewing my dome/mount geometry to verify and refine settings for slaving the dome opening to my mount/scope . Wondering about how I should handle the "GEM Offset" value considering that I have a guide scope that is mounted "off center" from the main OTA. Here is a (crude) drawing to illustrate:

If there was no guide scope, the GEM Offset would be "x". If the guide scope was mounted directly on top of the OTA, I would expect it to be a distance from Mount Pivot Point (MPP) to a point along the line between a and b (1/2 way between outer edge of guide scope and bottom edge of OTA). However, given the assymetrical nature of the guidescope, how should this be handled?

DaveNL

Posts: 2

Participants: 2

Read full topic

Autoguider (not) Settling with wrong parameters

$
0
0

@oguerrea wrote:

Hello,
I ran a session last night with my settling option for auto guider at 0.5 pixel for 2sec as below.

But my session failed with "Autoguider did not settled" and when looking at the log, I noticed:
[10/26/2016 11:13:24 PM] [DEBUG] [Sequence Thread] Waiting for Auto Guider distance to fall below 0.1
[10/26/2016 11:21:31 PM] [DEBUG] [Sequence Thread] Distance is below 0.1, starting timer...
[10/26/2016 11:21:34 PM] [DEBUG] [Sequence Thread] Distance stayed below 0.1 for 3 seconds, done settling...
Which short of a miracle given my setup...
But it worked only for one image, and the next time failed miserably:
[10/26/2016 11:41:47 PM] [DEBUG] [Sequence Thread] Auto guider failed to settle in the specified time limit, resuming the auto guider has failed...

Is there something I need to change/update so my settings (.5px for 2s) are properly taken into account?
Thanks,
Olivier

SGP log: sg_logfile_20161026230154.zip (53.4 KB)
PHD2 log: PHD2_GuideLog_2016-10-26_212055.zip (102.1 KB)

Posts: 5

Participants: 4

Read full topic


Auto stretch strange bahavior

$
0
0

@Pascal wrote:

Hello,
since the last beta release the auto stretch does not work properly with some of the frames I captured following the exposure time .... very strange. Auto stretch works with AF 2x2 or 2x2 and framing (1x1) with short exposure, (30sec) but not with 5min exposure (during sequence or manually using a right click). Re opening (file/open image) the 5min frames do not solve this problem. May be a bug
Thanks
Pascal
PS : I cannot upload the fit file
here is a single screenshot showing the result of a manual stretching ...

due to the size upload limit

Posts: 1

Participants: 1

Read full topic

Complete Newb with issues, requesting assistance

$
0
0

@shawnhar wrote:

Hello, 1st of all let me say that last night was my 3rd full night with SGP and when I woke up this morning it had done a flip and continued to take subs, while I slept, so that's awesome!
What is also awesome is that SGP ran into lots of issues, but SGP was like, OK, fine, we will just start over, gotta love Recovery! So even with my newbness I still ended up with several usable hours long after I had gone to bed. WOOT!

Now, on to the issues, lol.
Log file here:
https://www.dropbox.com/s/8erarh7iae6tvou/sg_logfile_20161027084511.txt?dl=0

First, I seem to be having problems with PHD2 and SGP dithering and guiding, it seems the "pause guiding during AF" is not working, which causes PHD2 to loose the guide star, then that causes a cascade of failures resulting in a recovery sequence as PHD2 is still "running" but it's not guiding or paused. Hopefully this is just some setting I don't have right.

Second, the failover blind solve does not seem to be working, the log shows it send the pic to the server and it fails there as well. I have some issues with Platesolver2, most of the time it will solve in just a few seconds, other times it will not solve at all. I slewed to M33 last night and it would not solve, slewed away maybe 2 degrees, and it solved fine, slewed back to M33 and it still would not solve. Any tips on getting solving to work more consistently?

Third, I am seeing a few images that fail to download in the allotted time, I just realized this is set at "1", would "5" be a good setting? Is that in seconds?

EQ6 with EQMOD 1.29a
PHD2 v2.6.1dev11
QHY8 camera
Homebrew aurdiuno "Myfocuser" attached to stock focuser_10" SCT
(I know the autofocus has issues but I am still trying different settings)

Thanks!
- Shawn Harrison

Posts: 1

Participants: 1

Read full topic

AVX and control software

$
0
0

@Debbie2317 wrote:

I have an AVX mount which I can connect with SGP but then I can't use a control software because it says the com port is in use. I am connected through the HC. SGP and The control software uses the same com port. I first tried using Stellarium when I couldn't get that to work I purchased The Sky since others had success. Ur still having the same problem. Obviously I'm doing something wrong but I don't know where to start. Please help!
Debbie

Posts: 3

Participants: 2

Read full topic

FLI Camera Error: Error with FLIGetTemperature (Code: -5)

$
0
0

@Nicholas_Jones wrote:

I've go my hands on Finger Lake Instruments ML16200 and I'm trying to configure and test this camera along with a CFW2-7 filter wheel

I've installed the ASCOM drivers for FLI and SGP is connecting to the camera and filter wheel along with the focuser.

When starting a small test sequence of lights I get a dialog saying "Error attempting to capture image (see log for more information.)

I get the following errors in the log.

[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] Waking from exposure time sleep period...
[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] Checking to see if the CCD has a temp...
[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] Saving the CCD temp...
[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] FLI Camera Error: Error with FLIGetTemperature (Code: -5)
[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] FLI Camera Error: Error with FLIGetCoolerPower (Code: -5)
[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] Entering super dangerous loop to await image completion...
[30/10/2016 9:34:20 PM] [DEBUG] [Sequence Thread] TEMP - Current Event16: 0
[30/10/2016 9:34:24 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetTemperature (Code: -5)
[30/10/2016 9:34:24 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetCoolerPower (Code: -5)
[30/10/2016 9:34:27 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetTemperature (Code: -5)
[30/10/2016 9:34:27 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetCoolerPower (Code: -5)
[30/10/2016 9:34:30 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetTemperature (Code: -5)
[30/10/2016 9:34:30 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetCoolerPower (Code: -5)
[30/10/2016 9:34:33 PM] [DEBUG] [Camera Thread] SGM_CAMERA_CAPTURE complete...
[30/10/2016 9:34:33 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetTemperature (Code: -5)
[30/10/2016 9:34:33 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetCoolerPower (Code: -5)
[30/10/2016 9:34:36 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetTemperature (Code: -5)
[30/10/2016 9:34:36 PM] [DEBUG] [CP Update Thread] FLI Camera Error: Error with FLIGetCoolerPower (Code: -5)

Posts: 1

Participants: 1

Read full topic

API for DSLR's

$
0
0

@helmbier wrote:

I installed SGPro 2.5.2.5 (trial licence). My mount is a 10Micron GM1000HPS. The camera I use is a Canon EOS 500D DSLR.
I wanted to do automated model making with the python app's of John Wainwright and Michael Würtenberger. No chance.
Both app's failed to control the DSLR because the SGPro API for DSLR isn't yet implemented or has some other problems. This I could read in the 10Micron forum.
My question is: Will a reliable API for DSLR's coming soon, let's say within the next half year, or is there no hope for.

Thanks
Helmar

Posts: 1

Participants: 1

Read full topic

Notifications rejected by cell carrier SMTP relay

$
0
0

@Astrobrat wrote:

First I would like to say what an awesome tool that you guys have created with SG Pro. Now I don't have to stay awake all night while my astro rig does the work of acquiring and photographing images.

I like the notifications system so I can periodically check the progress of the sequencing session. From time to time I will not get notifications but the test message works. I created a gmail account that sends the notification to tmomail as a SMTP so it shows up on my cell phone. Upon doing some research it looks like T- mobile's SMTP relay has added improved spam filtering this year. I have found several other complaints regarding T- mobile's rejection of their particular SMTP messaging applications.

Apparently some of the content of the status messages is being misconstrued as spam traffic (@#%& spammers) and "permantly rejected". I know that this is T'mobile's issue and I don't really expect them to change it.

I wonder if there is a way to format the status messages to stop resembling malicious hyperlinks or something similar. I do see the fits filenames processed in my text message stream to be hyperlinks...when you click them they land on T- mobile's web site with "content not found".

I know it's not MSS' s problem and most of the time notifications work. But I have to ask if there is a work- around for this little glitch.

Otherwise I couldn't be happier with the software...kudos for this sequencing concept!

Posts: 1

Participants: 1

Read full topic

NGC6960 - Witches Broom - Hubble Palette

$
0
0

@CarlightExpress wrote:

NGC6960 - Witches Broom by Simon Todd, on Flickr

http://stastrophotography.com/iVbtt

How Fitting for Halloween......My latest image - NGC6960 - Witches Broom in Hubble Palette Narrowband

Commonly referred to as the Witches Broom or the Western Veil of the larger Veil Nebula, this lies approximately 1470 Light years away.

In my opinion this is not an easy subject to image, and even more difficult to process, the image details are as follows:

15x600S in 7nm HA
15x600S in 7nm SII
15x600S in 7nm OIII
25 Darks
25 Flats

The HA was also used as a Luminance Layer

Equipment Used:
Imaging Scope: Sky-Watcher Quattro 8-CF 8" F4 Newtonian
Guide Scope: Celestron Telescopes C80ED Refractor
Mount: Sky-Watcher EQ8 Pro
Imaging Camera: Atik Cameras 383L+ Mono CCD Cooled to -20C
Guide Camera: Qhyccd QHY5L-II
Image Acquisition: Main Sequence Software Sequence Generator Pro
Guide Software: PHD2

Processing:
Pre-Processing: Maxim-DL for STacking, Darks and Flats Subtracting and Alignment of Colour Planes
Post Processing: Photoshop CS5, Noise Ninja

Enjoy
Simon

Posts: 1

Participants: 1

Read full topic


Ideal Exposition Time - More Explanation/Description

$
0
0

@RAPALA wrote:

Hello,

After few month utilization SGP Pro, I need understand and more information regarding the calculation of ideal exposure of a photograph.

I understand we need define the parameters in the Equipment Profile Mnager - Camera:

  • Readout Noise in e-.

  • Gain (Value and e-/ADU)

If our Camera have the gain defined by default (defined by the supplier) in the drive we need define Hight or Low and the Gain Value e-/ADU (Defined by the supplier).

But when we have camera, where SGP not suppot the value (Example QHY10 defined the gain in the driver ASCOM),

How SGP calculates the ideal exposure time? or where we need define more parameters to obtain the good "Ideal Exp. Time" ?

Many thanks for the comments or descriptions, will be very well received.

Regards,

Leandro

Posts: 4

Participants: 3

Read full topic

Change in set up config for Plate Solve

$
0
0

@tonyrodda wrote:

Hi,
I've been using SG Pro very successfully for long multiple photometry runs and PS2 worked every time (using the local ADM and UCAC3 Db).
Just changed from an Atik460 to an Orion G3 for my photometry set up and now PS2 won't work at all. Even for the same photometry fields.
I've set up a different (new) profile - all that's changed (materially) are field and pixel size.
Seems like I've missed something obvious in the config.
Any ideas before I generate a log and raise this formally?
Regards
Tony

Posts: 1

Participants: 1

Read full topic

2.5.2.5: Plate Solve broken please fix

$
0
0

@mads0100 wrote:

https://www.dropbox.com/s/yduh7z2jdp9ncdj/sg_logfile_20161031203346.txt?dl=0

I dunno why, but whatever you added to 'double check' my plate solving has broke SGP plate solving. I haven't figured out why I couldn't center over the past few nights. Well, when I try to plate solve using PS2 and it fails to blind failover, I get your error telling me my plate solve might be bad... but it's not. And this causes the sequence to fail.

Logs attached. Please turn that off!

Chris

Posts: 6

Participants: 4

Read full topic

Support for Nikon D500

Centering occasionally freezes with 2.5.1.17

$
0
0

@Kurious_George wrote:

Since upgrading to 2.5.1.17, centering often freezes during Step 3 and Step 4. Never seen that happen before. Using G11 with ASCOM v 1.0.56.0. Log below when freeze during Step 3 and Step 4 and then I abort after a minute or so. Text at bottom of window says "Image preview opened" when frozen.

STEP 3 FREEZE...

[11/1/2016 8:10:59 PM] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[11/1/2016 8:11:08 PM] [DEBUG] [Main Thread] Slewing to target...
[11/1/2016 8:11:08 PM] [DEBUG] [Telescope Thread] Slew telescope message received...
[11/1/2016 8:11:08 PM] [DEBUG] [Slew Monitor] Waiting for slew to complete...
[11/1/2016 8:11:08 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 1.91055555555556 (01h54m38.00s) Dec: 20.8075 (20°48'27.00")
[11/1/2016 8:11:08 PM] [DEBUG] [Telescope Thread] Telescope: Slew received J2000 coordinates, mount requires JNOW, converting...
[11/1/2016 8:11:08 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to JNOW RA: 1.92637053765131 Dec: 20.8898354598779
[11/1/2016 8:11:23 PM] [DEBUG] [Main Thread] Turning camera cooler on...
[11/1/2016 8:11:24 PM] [DEBUG] [Main Thread] Turning camera cooler on...
[11/1/2016 8:11:25 PM] [DEBUG] [TEC Thread] SGM_CHANGE_COOLER_TEMP message received...
[11/1/2016 8:11:25 PM] [DEBUG] [TEC Thread] TEC Change: Starting...
[11/1/2016 8:11:25 PM] [DEBUG] [TEC Thread] TEC Change: Changing temp from 15.80 to -10.00 in 300 seconds...
[11/1/2016 8:11:39 PM] [DEBUG] [Telescope Thread] Scope reports it is done with synchronous slew, verifying...
[11/1/2016 8:11:39 PM] [DEBUG] [Telescope Thread] Telescope: Slewing has completed
[11/1/2016 8:11:39 PM] [DEBUG] [Telescope Thread] Telescope: Settling for 5 seconds
[11/1/2016 8:11:44 PM] [DEBUG] [Telescope Thread] Telescope: Settling has completed
[11/1/2016 8:11:44 PM] [DEBUG] [Telescope Thread] Slew complete...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Center telescope message received...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Solving with Plate Solver Pinpoint...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Setting filter for auto center...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Setting filter position 1...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Filter position 1 is already set. Skipping...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Performing auto center step 1...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Skipping step 1...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Auto center reference frame solved successfully...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Performing auto center step 2...
[11/1/2016 8:11:49 PM] [DEBUG] [Telescope Thread] Created full file name: C:\Users\Astro\AppData\Local\SequenceGenerator\Temp\plate_solve_image-6.fit
[11/1/2016 8:11:49 PM] [DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE message received...
[11/1/2016 8:11:49 PM] [DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame...
[11/1/2016 8:11:49 PM] [DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame...
[11/1/2016 8:11:49 PM] [DEBUG] [Camera Thread] ASCOM (QSI) Camera: setting gain to LOW...
[11/1/2016 8:11:49 PM] [DEBUG] [Camera Thread] ASCOM (QSI) camera: setting normal speed readout...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] QSI expose and download: 24.7264142s
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] Created full file name: C:\Users\Astro\AppData\Local\SequenceGenerator\Temp\plate_solve_image-6.fit
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Locking bitmap for disk write...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Opening file stream...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Writing FITS headers...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Traversing and persisting bitmap data...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: FITS block fill...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Unlocking bitmap...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Closing file stream
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] Internal Interface: Set Preview...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] Display image preview using asynch task...
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] =========== Save file took 122 ms
[11/1/2016 8:12:14 PM] [DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE complete...
[11/1/2016 8:12:38 PM] [DEBUG] [Main Thread] Centering: User abort...
[11/1/2016 8:12:40 PM] [DEBUG] [Auto Center Closing Thread] Aborting auto center, waiting for centering routine to terminate...
[11/1/2016 8:12:40 PM] [DEBUG] [Telescope Thread] Aborting auto center...
[11/1/2016 8:12:40 PM] [DEBUG] [Telescope Thread] Auto center aborted, closing centering dialog...
[11/1/2016 8:12:40 PM] [DEBUG] [Auto Center Closing Thread] Centering routine has terminated...

STEP 4 FREEZE...

[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Opening fits file...
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Successfully opened fits file...
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Writing fits headers...
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Closing fits file
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Failed to sync the rotator to 267.5801 degrees, not connected!
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Performing auto center step 3 (scope)...
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Auto center slewing scope to match reference...
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 1.61753055555556 (01h37m03.11s) Dec: 15.7818888888889 (15°46'54.80")
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Telescope: Slew received J2000 coordinates, mount requires JNOW, converting...
[11/1/2016 8:30:31 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to JNOW RA: 1.6329035268679 Dec: 15.867621094988
[11/1/2016 8:30:40 PM] [DEBUG] [Telescope Thread] Scope reports it is done with synchronous slew, verifying...
[11/1/2016 8:30:40 PM] [DEBUG] [Telescope Thread] Telescope: Slewing has completed
[11/1/2016 8:30:40 PM] [DEBUG] [Telescope Thread] Telescope: Settling for 5 seconds
[11/1/2016 8:30:45 PM] [DEBUG] [Telescope Thread] Telescope: Settling has completed
[11/1/2016 8:30:45 PM] [DEBUG] [Telescope Thread] Auto center slew complete...
[11/1/2016 8:30:45 PM] [DEBUG] [Telescope Thread] Performing auto center step 4...
[11/1/2016 8:30:45 PM] [DEBUG] [Telescope Thread] Created full file name: C:\Users\Astro\AppData\Local\SequenceGenerator\Temp\plate_solve_image-11.fit
[11/1/2016 8:30:45 PM] [DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE message received...
[11/1/2016 8:30:45 PM] [DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame...
[11/1/2016 8:30:45 PM] [DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame...
[11/1/2016 8:30:46 PM] [DEBUG] [Camera Thread] ASCOM (QSI) Camera: setting gain to LOW...
[11/1/2016 8:30:46 PM] [DEBUG] [Camera Thread] ASCOM (QSI) camera: setting normal speed readout...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] QSI expose and download: 23.1363233s
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] Created full file name: C:\Users\Astro\AppData\Local\SequenceGenerator\Temp\plate_solve_image-11.fit
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Locking bitmap for disk write...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Opening file stream...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Writing FITS headers...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Traversing and persisting bitmap data...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: FITS block fill...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Unlocking bitmap...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SaveFileBmp16: Closing file stream
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] Internal Interface: Set Preview...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] Display image preview using asynch task...
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] =========== Save file took 104 ms
[11/1/2016 8:31:09 PM] [DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE complete...
[11/1/2016 8:31:18 PM] [DEBUG] [Main Thread] Centering: User abort...
[11/1/2016 8:31:19 PM] [DEBUG] [Auto Center Closing Thread] Aborting auto center, waiting for centering routine to terminate...
[11/1/2016 8:31:19 PM] [DEBUG] [Telescope Thread] Aborting auto center...
[11/1/2016 8:31:19 PM] [DEBUG] [Telescope Thread] Auto center aborted, closing centering dialog...
[11/1/2016 8:31:19 PM] [DEBUG] [Auto Center Closing Thread] Centering routine has terminated...
[11/1/2016 8:31:30 PM] [DEBUG] [Main Thread] PopulateDataModel: Transferring view to the data model...
[11/1/2016 8:31:30 PM] [DEBUG] [MF Update Thread] Performing serialize...

Posts: 1

Participants: 1

Read full topic

Viewing all 8550 articles
Browse latest View live