TimC

Hi Jeff, I have just done this and it works well carrying across all of your Autoslew and Sequence settings and data. On my Win Xp machine I found this folder: C:\Documents and Settings\All Users\Application Data\ASA and just copied and pasted it across to the new Win 7 64 bit machine to here C:\ProgramData\ASA I had to make the C:\ProgramData Folder viewable as it is at the start a "Hidden" folder. I then installed Autoslew ( a recent beta version) and Sequence. I had to find my latest profiles in the new ASA for Autoslew and Sequencee and load them when I opened Autoslew and Sequence, but everything seems to be there OK. I hope that helps!! Good luck! Regards, Tim

This is absolutely fantastic news indeed....Awesome!! Thanks for letting us know that help is on it's way. I hope you can keep the momentum up with this, and deliver by the end of year. Thanks very much. Regards, Tim

Thanks Lukas. So that is all I have to do! Regards, Tim

Hi, After getting continual runtime errors with the astronomy software on an XP PC, I have decided trying a PC upgrade to see if I can get a more stable platform. I am getting a WIn 64bit PC with a bit more memory and starting with a clean install state. What do I have to do, to transfer all of my current settings/pointing file/all current crucual Autoslew data for the mount, to the mew Operating system PC?? What files need to be copied across to the new PC?? Thanks and regards, Tim

Hi, I have the Premium , the DDM85XL with the bent pier. ASA have confirmed that with my many balancing attempts that the balance is way off.....therefore operator error fortunately seems to be the issue....I will work hard again on the balancing! Regards, Tim

Thanks Lukas, I have a Philipp Keller 20 inch Classical Cassegrain ( very similar, but I believe heavier than the ASA version) which is a very heavy scope. Attached is a FLI PL16803 plus FLI filterwheel and a MegaMOAG off axis guider with a ST402 autoguider....quite a heavy payload, I'm afraid. Regards, Tim

Hi, Thanks very much. Yes, I do see position errors - taken from recent logs...... 04:49:14.625: Interface SlewToTargetAsynch 04:49:14.625: Interface setting TargetRightAscension to 16.11 True 04:49:14.640: Interface setting TargetDeclination to -44.08 True 04:49:14.640: Interface SlewToTargetAsynch 04:49:14.859: Interface SetPark with Az=179.6 Alt=28.0 04:49:15.062: Interface Park 04:49:15.062: Starting Slew to RA 16.12h DE -79.08d EPOCH 0000 04:49:28.734: Telescope Interface sets Tracking to False 04:53:28.796: Raising fatal Error RA Axis: Position Error 01:42:21.140: Starting Slew to RA 11.42h DE -23.26d EPOCH 0000 01:42:32.156: Raising Warning DE Axis: Position Error Position Error during slewing autocorrected by ClServo Position Error correction failed 01:42:38.093: Raising Warning DE Axis: Position Error Position Error correction failed 01:42:46.062: Raising Warning DE Axis: Position Error Position Error correction failed 01:42:57.187: Raising Fatal Error DE Axis: Position Error Position Error correction failed 01:42:21.312: Axis 1 slewing to 14.01 01:42:21.375: Axis 2 slewing to 23.51 01:42:22.250: Axis 2 Pos:+004.01° Curr:+02.3A PosErr:+08.54arcsec 01:42:22.921: Axis 1 Pos:+014.06° Curr:+01.0A PosErr:+02.85arcsec 01:42:28.406: Axis 2 Pos:+017.92° Curr:+02.1A PosErr:+10.25arcsec 01:42:29.078: Axis 1 Pos:+014.01° Curr:+00.9A PosErr:-00.96arcsec 01:42:30.500: Axis 2 Error: Position Error 01:42:30.859: Axis 2 trying to autocorrect error and slewing again to 23.51 01:42:31.953: Axis 2 autocorrect slewing error failed 01:42:32.203: Axis 2 Error: Position Error 01:42:32.234: Axis 2 Error: Velocity Limit Exceeded 01:42:32.250: Axis 22 Tracking errors within 60 seconds, giving up 01:42:33.234: Axis 2 Error: Velocity Limit Exceeded 01:42:34.328: Axis 2 Error: Velocity Limit Exceeded 01:42:34.375: Axis 2 Pos:-004.23° Curr:+00.0A PosErr:+02.49arcsec 01:42:34.656: Axis 2 Error Cleared 01:42:34.671: Axis 2 turned off Motor 01:42:34.718: Axis 2 turned on Motor 01:42:35.343: Axis 1 Pos:+014.02° Curr:+00.1A PosErr:-00.54arcsec 01:42:35.390: Axis 2 Error: Position Error 01:42:35.406: Axis 2 Error: Velocity Limit Exceeded 01:42:35.437: Axis 2 trying to autocorrect tracking error 01:42:37.937: Axis 2 Error: Position Error 01:42:37.968: Axis 2 Error: Velocity Limit Exceeded 01:42:37.984: Axis 22 Tracking errors within 60 seconds, giving up 01:42:38.984: Axis 2 Error: Velocity Limit Exceeded 01:42:40.093: Axis 2 Pos:-029.28° Curr:+00.0A PosErr:+00.00arcsec 01:42:40.593: Axis 2 Error Cleared 01:42:40.593: Axis 2 turned off Motor 01:42:40.781: Axis 2 turned on Motor 01:42:41.125: Axis 1 Pos:+014.03° Curr:+00.2A PosErr:-01.79arcsec 01:42:43.296: Axis 2 Error: Position Error 01:42:43.328: Axis 2 trying to autocorrect tracking error 01:42:45.859: Axis 2 Error: Position Error 01:42:45.890: Axis 2 Error: Velocity Limit Exceeded 01:42:45.906: Axis 22 Tracking errors within 60 seconds, giving up 01:42:45.937: Axis 2 Pos:-024.28° Curr:+00.0A PosErr:+02.57arcsec 01:42:46.953: Axis 1 Pos:+014.04° Curr:+00.4A PosErr:-00.32arcsec 01:42:48.562: Axis 2 Error Cleared 01:42:48.562: Axis 2 turned off Motor 01:42:48.625: Axis 2 turned on Motor 01:42:52.328: Axis 2 Pos:-028.48° Curr:+03.2A PosErr:-04.02arcsec 01:42:53.406: Axis 1 Pos:+014.06° Curr:+00.2A PosErr:-00.18arcsec 01:42:53.437: Axis 2 Error: Position Error 01:42:53.453: Axis 2 trying to autocorrect tracking error 01:42:57.031: Axis 2 Error: Position Error 01:42:57.062: Axis 2 Error: Velocity Limit Exceeded 01:42:57.078: Axis 22 Tracking errors within 60 seconds, giving up With a fixed setup in a remote location with unattended robotic operation all night long, I hope there will be a way to balance and tune the system so that these don't occur at all. I just hope there is only operator insufficiency involved and not a problem with the mount itself. Mark, this is a worry to me....."I always set up with the Balance Tool, but it doesn't always guarantee trouble free running over long periods.".... ASA are going to remote in again to see if the tuning can be improved. I will work harder on the balance issue...but...I have an asymmetric camera filter wheel off axis guider combination with a camera rotator that rotates this whole assembly all over the place to get a guide star at focal length 4.7m. I can look at attaching a counter weight to the assembly, but it will be hard to assess the balance of the counterweight against the imaging devices. Regards, Tim

Hi, I think I have been having a similar problem where the DDM85 works OK for 20 to 60 minutes then just freezes up randomly. I will send the logs to ASA to see if they can help diagnose the problem. ASA did check the tuning recently. It may be a balance issue, but it I have tried re-balancing many times. Regards, Tim

Thanks very much Michael and Gerhard !

Hi, I have a 500mm Keller Classical Cassegrain with a DDM85 premium. I had made a Sequence pointing file initially of about 35 points. I am now trying to refine the setup to improve tracking etc. I have tried to re-use sequence to create a larger pointing model, but I am having no success. Questions: 1. Should I run the new pointing file with the old one removed from Autoslew or can I run the new pointing run with my current model active in Autoslew?? 2. When I have the new Sequence data *.pox file can I just add it to my existing data and combine all the information for Autoslew to use? 3. What is making Sequence suddenly crash and close itself always after taking about 40 points?? This is very frustrating as I am hoping to increase my pointing data to around 400 points with a permanent setup after ensuring with the hysteresis function that everything is very tight with the scope setup otherwise. I have Autoslew connected to TSX via POTH and when this happens POTH is frozen and TSX reports loss of communications. The mount runs all night when Sequence is not being used (Connected to CCDAutoPilot5) . Many thanks for your help !! Regards, Tim

Hi, Thanks very much for the replies. I was mainly querying why the software was freezing up and not issuing any corrections to the mount via Maxim during autoguiding and then when I disconnect AutoSlew it tells me there are 85 ASCOM programs connected to it....no wonder it had frozen and been unable to cope with adjusting mount position when commanded to by Maxim. Perhaps it is an USB issue. By the way, I have previously run the hysteresis routine and have reduced the hysteresis error down to about 9 arcsec.by optimising the Keller classical cassegrain primary mirror's stability. Regards, Tim

Hi, I have started to try and develop things further with the DDM 85. I am utilising CCDAutoPilot and trying to utilise longer exposures 10 to 20 min subs with the new mount. I am finding my tracking is not giving me round stars without autoguiding on the long exposures. This is probably (I guess) because I have to fix the mount balance better maybe or fix the cable drag that I still have to some degree at this stage, or perhaps I need a bigger and better pointing file.....Anyway with autoguiding using Maxim, the funny thing is that I get beautiful subs with great guiding for the first two or three subs in an automated run, then after that the mount seems to stop correcting and the guide errors go very high with no correction from the mount. Also, when I end the run and disconnect the software from each other Autoslew tells me there are now about 85 ASCOM programs connected to it ....Because of my situation in a remote site, I as yet cannot use MLPT for longer exposures as I need robotic automation to work through the whole night. I do understand Philipp is testing an automated multitarget night-long version of MLPT at the moment, however. Can anyone enlighten me about what I might be doing wrong with my attempts to autoguide with the DDM85 ?? Many thanks, Tim

Philipp, By the way, I checked out your website: www.chart32.de A 80cm scope in the mountains of Chile, with a very good team. Very impressive. Regards, Tim

Hi Philipp, Thanks again! It is good news if MLPT can be automated for remote use through the whole night. Thanks very much for writing all this good software! Regards, Tim

Hi Philipp, Thanks very much for the advice. I will see if using POTH is more stable. Regards, Tim

Thanks Dave, I have also found out the details of connecting 12V DC cabling to the FLI PL16803. It is in the FLI manual!! Regards, Tim

Thanks very much Josch. I see that you leave the mount switched on for prolonged perioids of time. I will de-power the mount to save electricity in betwwen session as we are on off-grid solar power only as no main power is present at our site. I think it will work out fine with doing a homefind and I am pleased there is no need to do any further synch's once the "Set ne homeposition" has been done once. Regards, Tim

Hi, This is all good information. Could I please ask Dave how he converted from the bare ends of the ASA cables to the power plugs for the cameras. I use the same cameras. Thanks, Tim

Hi All, Thanks for this discussion, it is very timely as I am in the process of setting up a DDM85 Premium for remote imaging with the observatory 3 hours drive away. I utilise CCDAutoPilot to do remote imaging all night. I also use The SkyX. How do I get CCDAutoPilot to automatically park the scope at the end of the nights imaging at the Park2 position, which is setup on my mount to be near the HomeFind position so that the mount will quickly and easily find the Homefind position again??? In the Southern Hemisphere, my mount needs the counterweight shaft to be pointing to the West and almost horizontal, with the scope pointing to the South at about 60 degrees elevation. How does CCDAutoPilot know to use the Park2 position (as opposed to the other available Park positions that can be set in AutoSlew?) for parking the mount. I tried setting a Park position using The SkyX's "set park position" command, but that seemed to make the mount go weird.....I find it OK to do a Homefind before each run being set and started in CCDAutoPilot, but as I do this usually before it gets dark, I don't find it convenient/easy to have to do a synch before commencing imaging. Is a synch required again and again with a permanent setup?? I would also highly value the ability to utilise MLPT on multiple targets automatically and remotely through the night using CCDAutoPilot. I hope Philipp Keller is working on automating the MLPT process, so that it can be called up as a routine at the start of a target light run within CCDAutoPilot. Many thanks, Tim

Thanks Gerhard!!

Hi, Does anyone know the answer to my question from a few days ago?? Please see my post of 19th May,..... thanks. Regards, Tim

Hi, I have just been reading the Sequence manual and I am wondering with the DDM85 PREMIUM mount using of course the bent pier, whether I should use the "Equatorial German" setting or the "Equatorial Fork" option as I see you state the DDM160 should use the Eq. Fork setting....?? Mount type For the DDM85 and DDM60 you should set this parameter to „Equatorial German“, for the DDM160 set the parameter to "Equatorial Fork". Please advise. Many thanks, Tim

Hi Gerald, Thanks very much. I am finding that I cannot connect to TheSkyX. I get an error 206 in TheSkyX and the mount does not connect. I am using the latest version of TheSkyX 10.2.0 (build 6409). I am using Win XP Pro SP3 and have .net 3.5 installed. I wonder if I should ask ASA to remote connect to the mount in the next day or so, as I will be out at the remote site over the next few days where the mount is....?? Best Regards, Tim

Hi, I have just received my ASA DDM85 Premium mount. It will carry a Keller 500mm Classical Cassegrain OTA. I have never used a bent pier before, so I am excited to see how well this system works for avoiding meridian flips. I see settings in Autoslew for setting limits: How far can you go through the meridian, minimum flip distance for east side slews......can you tell me what would be reasonable starting points for these settings?? I am in the Southern Hemishpere (Australia), so are there any settings to watch out for with respect to southern hemisphere operation? For instance, when the manual says point the OTA to the North to make a pointing map or such thing, I assume I should point South in these situations?? The mount is very impressive sitting on the amazing bent pier. I hope we set the base plate close enough to the correct orientation to the south pole, as the amount of azimuth adjustment available on the pier itself, seems quite small. I guess I will find out soon when I do my first polar alignment routine. Many thanks, Tim