Corpze
Beta Tester-
Posts
254 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Everything posted by Corpze
-
Thanks for the nice comments, however, i am having a bit trouble of getting the right color on the stars, as you can see, they are a bit blue-ish. How do you handle the color-levels? Before stretch? After combining? Regards, Daniel
-
First post here for me, would really like som input from you guys who have tons of experience. I have been using Pixinsight for a bit over a year and still learning. L and Ha 20x300s R,G,B 12x300s DDM85 Meade 102 APO (with a hint of bad collimation, ideal summer-project) - Subframeselector - Batch preprocessing - ABE, DBE when needed - Channel Combination - Masked MMT - Masked Deconvolution (Applied on both L, Ha and RGB) - HaLRGB combination - Permanent stretch - LRGB Combination - Curves /Daniel
-
How often do you have do a new PA/model?
Corpze replied to Corpze's question in ASA DDM85, 100, 200, 500
Thanks for your input Jay /Daniel -
Hi, i was just curious of how often you really have to do a new Polar Align due to the precession. Another question i have been wondering over is if you have to do a new model for the autumn/spring or if you are good to go with a good model throughout the whole year? /Daniel
-
Yes it is Working fine for me too, but only if i restart Sequence every night, otherwise, it won't park my scope ????
-
Aha, so it basically a Safety monitor, not a weather monitor... I guess ASA has a bit of debugging to do :-/
-
Hi, I am using a cloud and rain sensor (home built) that outputs Issafe or Isnotsafe through ASCOM. When I setup a new sequence, and press "Start @ time" in Sequence while the Safety Monitor reports "Not safe" - will Sequence wait until the conditions get "Safe" or will it abort? If it gets "Not safe" during a sequence, it will perform a "Close all" command right? But if it clears up say an hour after it has closed a sequence, will Sequence continue the sequence? (Probably not huh?) /Daniel
-
Haha, i have watched the video several times but never noticed that Thanks for the heads up
-
That should be very nice to get a comment from ASA, if it does calculates the "Superfit" from the drop-down menu or if you have to do a "manual" superfit from the "advanced" menu. (Auto slew .19) /Daniel
-
And another thing, do you calculate fourier AND superfit or is it enough to calculate superfit?
-
Wow Mark, that seems to be good numbers! are you getting this kind of accuracy every time you set up? i am impressed Have you tried Superfit? I am using a stationary setup so no PA for me I wrote down all the steps i did so i remember them next time i have to do a model (hopefully this model i did today will function to the autumn) Fresh restart of the computer Clear config Synch a star with Autoslew and planetarium Make an autopointfile - 25 degree min alt, 90 degree max alt, 10 degree grid in both RA and DE, pier side - both (in my case 110-ish stars) Load and calculate autopoint file Save the pointing file and "use now" Restart autoslew - Check that the new pointing file is in use! (Motors on, Homefind) Select and center a star with planetarium Synch with autoslew Set new home position This particular model gave me pinpoint accuracy when slewing, and with MLPT i have only tried 5min, but that was absolutely pin point stars. If anyone know how to calculate and apply the superfit, feel free to fill in And also, there is a setting in the autopoint - autogrid named "reference" on each East and West - what exactly does this function do? /Daniel
-
Hi, yes i have seen it, but would really like to double check if i am thinking right. Clear configuration before calculating and applying the new model? /Daniel
-
Hi, i am about to do a workflow with a video of how to do a superfit pointing model, but need some input. I have already a Working model with some stars, the pointing and tracking is good for 5-10 minutes. Last night, i did a 120 star autopoint file which i am about to use as a superfit. Is this the right workflow?; -open advanced pointing file -calculate and optimize polar, poiting, tracking etc. -Calculate and optimize superfit? -Apply new model - make a new homeposition Do i have to clear the old configuration at any point or do i apply the new one "on top"? /Daniel
-
Well, i have to admit that I am happy with my DDM85, but i would not recomend ASA to a person looking for a premium mount. If i knew what i know today, i would go for a 10 Micron :-/
-
Is there any documentation of the new Superfit function?
-
I am getting these "errors"? Myself, what is this? /Daniel
-
Thank you for the answer
-
Thanks for your input Thats no problem, just set your target, run @ time and it glises everything when finished
-
Hi, i was just wondering which park position "Sequence" is using when it is parking the scope and closes the session for the night? 1 or 2? /Daniel
-
Ok.... this feels like searching for a couple of needles in a haystack, but here goes... from the windows logbook; 2016-02-12 01:18:38 - System time synced to machine clock (this might have screwed both autoslew and sequence up) 2016-02-12 01:18:39 - Network link is disconnected (should not have caused anything serious fault?) 2016-02-12 01:18:40 - Energy save mode restored (According to this event log, the computer went to sleep 2016-02-11 22:17:29....... sigh) I will bang the head against the wall one more time.... it is a LOT of settings hidden in windows 10 that needs to be switched to the right mode for us night-active creatures So - energy mode - Check Windows update - Check Windows Maintenence - Set to be activated during daytime instead of 02:00 - check Anything more? /Daniel
-
Hi, i woke up this morning to a shut down computer with this error: any clues what might have happened? I also have a log from Cl servo log that sais readin32 error something. But why the pc shutdown? (I have recently installed win10, maybe something with the updates?) Regards, Daniel 23:12:34.895: Interface setting TargetRightAscension to 6,29 False 23:12:34.941: Interface setting TargetDeclination to 22,53 True 23:12:34.973: Interface ForceNextPierSide = pierEast 23:12:34.973: Interface SlewToTargetAsynch 23:12:34.988: Starting Slew to RA 06,29h DE 22,53d EPOCH 0000 23:17:36.506: To long sleep of main timer, was reset by controltimer 23:17:36.560: AliveProgresscount stopped at 100 01:18:38.499: To long sleep of main timer, was reset by controltimer 01:18:38.515: AliveProgresscount stopped at 101 01:18:39.572: To long sleep of main timer, was reset by controltimer 01:18:40.628: AliveProgresscount stopped at 102 01:18:41.290: Interface setting TargetRightAscension to 6,26 False 01:18:41.322: Interface setting TargetDeclination to 19,15 True 01:18:41.353: Interface ForceNextPierSide = pierEast 01:18:41.353: Interface SlewToTargetAsynch 01:18:41.368: Starting Slew to RA 06,26h DE 19,15d EPOCH 0000 01:18:41.728: To long sleep of main timer, was reset by controltimer 01:18:41.728: AliveProgresscount stopped at 103 01:18:42.740: To long sleep of main timer, was reset by controltimer 01:18:42.740: AliveProgresscount stopped at 104 01:18:43.740: To long sleep of main timer, was reset by controltimer 01:18:43.740: AliveProgresscount stopped at 105 01:18:44.740: To long sleep of main timer, was reset by controltimer 01:18:44.740: AliveProgresscount stopped at 106 01:18:45.763: To long sleep of main timer, was reset by controltimer 01:18:45.763: AliveProgresscount stopped at 107 01:18:46.763: To long sleep of main timer, was reset by controltimer 01:18:46.763: AliveProgresscount stopped at 108 01:18:47.763: To long sleep of main timer, was reset by controltimer 01:18:47.763: AliveProgresscount stopped at 109 01:18:48.763: To long sleep of main timer, was reset by controltimer 01:18:48.763: AliveProgresscount stopped at 110 01:18:49.767: To long sleep of main timer, was reset by controltimer 01:18:49.767: AliveProgresscount stopped at 111 01:18:50.770: To long sleep of main timer, was reset by controltimer 01:18:50.770: AliveProgresscount stopped at 112 01:18:51.779: To long sleep of main timer, was reset by controltimer 01:18:51.779: AliveProgresscount stopped at 113 01:18:52.783: To long sleep of main timer, was reset by controltimer 01:18:52.783: AliveProgresscount stopped at 114 01:18:53.783: To long sleep of main timer, was reset by controltimer 01:18:53.783: AliveProgresscount stopped at 115 01:18:54.783: To long sleep of main timer, was reset by controltimer 01:18:54.783: AliveProgresscount stopped at 116 01:18:55.237: Axis RA/AZ reported the following Problem: ReadInt32 error was solved OK with Cycleport 01:18:56.134: To long sleep of main timer, was reset by controltimer 01:18:56.134: AliveProgresscount stopped at 100 01:18:57.134: To long sleep of main timer, was reset by controltimer 01:18:57.134: AliveProgresscount stopped at 101 01:18:59.310: To long sleep of main timer, was reset by controltimer 01:18:59.310: AliveProgresscount stopped at 100 01:19:00.341: To long sleep of main timer, was reset by controltimer 01:19:00.341: AliveProgresscount stopped at 101 01:19:00.694: Axis RA/AZ reported the following Problem: Position Error Position Error during slewing autocorrected by ClServo Position Error correction failed 01:19:00.865: Raising fatal Error RA Axis: Position Error Position Error during slewing autocorrected by ClServo Position Error correction failed 01:19:09.585: Interface setting TargetRightAscension to 6,88 False 01:19:09.616: Interface setting TargetDeclination to 21,74 True 01:19:09.648: Interface ForceNextPierSide = pierEast 01:19:09.663: Interface SlewToTargetAsynch 01:19:17.438: Interface setting TargetRightAscension to 6,29 True 01:19:17.485: Interface setting TargetDeclination to 22,53 True 01:19:17.516: Interface ForceNextPierSide = pierEast 01:19:17.516: Interface SlewToTargetAsynch 01:19:25.330: Interface setting TargetRightAscension to 6,29 True 01:19:25.376: Interface setting TargetDeclination to 22,53 True 01:19:25.408: Interface ForceNextPierSide = pierEast 01:19:25.408: Interface SlewToTargetAsynch 03:29:29.499: To long sleep of main timer, was reset by controltimer 03:29:29.499: AliveProgresscount stopped at 100 03:29:30.555: To long sleep of main timer, was reset by controltimer 03:29:30.680: AliveProgresscount stopped at 101 03:29:32.456: To long sleep of main timer, was reset by controltimer 03:29:32.456: AliveProgresscount stopped at 102 03:29:33.456: To long sleep of main timer, was reset by controltimer 03:29:33.456: AliveProgresscount stopped at 103 03:29:34.457: To long sleep of main timer, was reset by controltimer 03:29:34.457: AliveProgresscount stopped at 104 03:29:35.457: To long sleep of main timer, was reset by controltimer 03:29:35.457: AliveProgresscount stopped at 105 03:29:36.457: To long sleep of main timer, was reset by controltimer 03:29:36.457: AliveProgresscount stopped at 106 03:29:37.457: To long sleep of main timer, was reset by controltimer 03:29:37.457: AliveProgresscount stopped at 107 03:29:38.457: To long sleep of main timer, was reset by controltimer 03:29:38.457: AliveProgresscount stopped at 108 03:29:39.457: To long sleep of main timer, was reset by controltimer 03:29:39.457: AliveProgresscount stopped at 109 03:29:40.457: To long sleep of main timer, was reset by controltimer 03:29:40.457: AliveProgresscount stopped at 110 03:29:41.473: To long sleep of main timer, was reset by controltimer 03:29:41.473: AliveProgresscount stopped at 111 03:29:42.483: To long sleep of main timer, was reset by controltimer 03:29:42.483: AliveProgresscount stopped at 112 03:29:43.483: To long sleep of main timer, was reset by controltimer 03:29:43.483: AliveProgresscount stopped at 113 03:29:44.489: To long sleep of main timer, was reset by controltimer 03:29:44.489: AliveProgresscount stopped at 114 03:29:45.489: To long sleep of main timer, was reset by controltimer 03:29:45.489: AliveProgresscount stopped at 115
-
that´s a close one, i am just installing all software on a new win10 computer, luckily, i saw this thread and got a heads up - Thanks Crister! Is there a way to shut these auto-updates off? It kinda feels like this is not the last time we will se this kind of related errors if win10 starts updating, restarting itself etc. /Daniel
-
Same for me, i have also noticed that sequence isn't shut down properly sometimes. When checking my active processes seq32.exe is still running even after i have shut i down - it does seems that autoslew/sequence might have a problem closing connections as gmalits sais. (autoslew 5.2.1.9, sequence 0.2.0.9) /Daniel
-
Yea, it is probably that way, but it would be nice to take a peak New tech is always fun to look at. /Daniel