Corpze Posted February 12, 2016 Report Share Posted February 12, 2016 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 Link to comment Share on other sites More sharing options...
robertp Posted February 12, 2016 Report Share Posted February 12, 2016 Hello David, did you check the windows event logs? Maybe you can find an indicator of a system shutdown or something. It's strange that you are missing 2 hours of logging information from 1:19 am to 3:19 am. Best regards, Robert Link to comment Share on other sites More sharing options...
Corpze Posted February 12, 2016 Author Report Share Posted February 12, 2016 Hi, i actually did and found some issued with the spp or something... Will check later, Windows 10 is kind of strange :-P I am on the phone right now but will check later. Link to comment Share on other sites More sharing options...
Waldemar Posted February 13, 2016 Report Share Posted February 13, 2016 Hi, i actually did and found some issued with the spp or something... Will check later, Windows 10 is kind of strange :-P I am on the phone right now but will check later. That definitely is an understatement! Link to comment Share on other sites More sharing options...
Corpze Posted February 13, 2016 Author Report Share Posted February 13, 2016 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 - CheckWindows update - CheckWindows Maintenence - Set to be activated during daytime instead of 02:00 - check Anything more? /Daniel Link to comment Share on other sites More sharing options...
Waldemar Posted February 13, 2016 Report Share Posted February 13, 2016 Be sure windows does not update third party software... It is infamous for that! I had to reinstall some software because it did that and I did not have the right licenses for the new software... B-(( Be sure AS is on the same timer as your comp. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now