DaveS

Many thanks Mark, and apologies for not replying sooner.

What happened to the software download centre? Went to look for a manual but had to go through a registration, then found that my DDM 85 camne up as not found. Annoyed and perplexed.

I was going to start my own thread on this as I had the same error last night, and I think on an earlier run, but clear nights have been few and far between so I'm not sure when it was. Cloudwatcher flagged up NOT SAFE and sequence looked like it had shut down but then tried to continue the exposures with the roof closed. Autoslew of course then threw up Position Errors. My exposure folder shows two bad subs of 15 mins each. 2021_11_21_16h43m.txt Autoslew Log 2021_11_21_16h44m.txt Sequence Log. The Autofocus wasn't involved in this error.

Hi Waldemar. Many, many thanks for the info. I'll be able to get on with it now. Dave.

This should be simple for those who know. I currently have the fans of my ODK12 connected to the auto dew controller output of my Pegasus APB, but this isn't ideal (Or anywhere near). What I would like to do is connect them to the three pin fan output on my DDM85, but do not know for sure the pinout or the type of connector. I *think* it's a Cannon locking DIN, but I not certain enough to order one, let alone wire it up. Can anyone give me any info please? TIA, Dave.

Currently I have Autoslew 5248 on both computers. The observatory computer has Sequence 2.1.1 The platform computer has Sequence 2.0.9. It did have 2.1.1, but I had a major crash requiring a clean install of Windows, and couldn't download 2.1.1 from the ASA downloads page. But I did have an old installation file of 2.0.9 Where can I get Sequence 2.1.3? I can only see 2.1.1 on the download page, and as I said, couldn't download it. Edit: The reason I couldn't download was the cookie settings in Chrome. Still can't find Sequence 2.1.3 though

Not really. I *still* get that pop-up. May try rolling back from the latest Autoslew to the one before. Only pops up when Sequence calls Autoslew, so it might be something in Sequence.

OK, gone back in to the remote PC, and redone the uninstall / reinstall with a restart in between. Checked the programData file and all the files are still there. Will check when we next get a clear sky.

Ah. Done the reinstall but didn't restart the computer. I did, though, back up the ASA ProgramData file just in case.

Thanks for the reply Waldemar, and sorry for not replying sooner. I've reinstalled the ASCOM platform, but I think I will have to reinstall the Autoslew as well, something I'm afraid of doing. Had too many borks to be confident. The pop-up doesn't occur when slewing from Cartes du Ciel, only on the first time Sequence calls for a slew from Autoslew.

Yep, yet another bork. I was running a sequence of two targets a couple of nights ago. All appeared to be going well until the sequence ended. Sequence closed down as it was supposed to, parking the mount and closing the roof. But then I saw Servo Errors popping up in Autoslew. The CCTV showed the telescope pointing into the roof, while Sequence was repeatedly trying to start a sequence by synching the 'scope. I ended up having to close the program to stop it. A check of the Log file the next morning showed that Sequence was trying to re-run the second of the targets. I've not had a chance to try a single target sequence since due to the weather, but wonder if this has happened to anyone else, and if so, how did you cure it?

Not yet, that might be the next step. Odd that it should have happened to both computers at the same time.

For the first time last night I got an ASOM pop-up asking me what type of mount I had. This occured when Sequence called for a move from Autoslew. I have looked in both Sequence and Autoslew for a setting that might have become unchecked but everything looked to be as it had been. I got this both on the DDM60 rig which had needed a software rebuild after a total crash, and on the DDM 85 which, as far as I know, has been OK. Has anyone else seen this lately? How can I prevent it from getting in the way again. After I tell ASCOM which type of mount I have it proceeds normally, but just pops up everytime a new call to Autoslew occurs at the start of a sequence. It doesn't occur during a sequence. I'm running ASCOM platform 6.5 SP1. Has there been a sneaky ASCOM update? Or has a Windows update borked it?

As far as I can tell it does use Park 1. Although I tried setting the OTA horizontal Autoslew didn't like it, firstly refusing to lay the OTA horizontal as it was below the limit, secondly I was getting position errors on startup. I've reset the OTA to the zenith for the time being.

Thanks Robert. 😄 Damn stupid emoji can't get rid of it What I typed was that I found a similar huge Sesto Senso log file on the C drive of the other remote PC, but was able to delete it as I had restarted the PC.