MarkS
-
Posts
557 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Posts posted by MarkS
-
-
I did not receive the handles with my ASA10 either.
I remove the cell just by grasping the metal mounting plate. The holes in the plate allow this - I have had no trouble.
Mark
-
Thomas,
I had a similar problem last December, which was still there after I had completely removed Sequence and its Program Data files, and built a new Data file from scratch....
Desperate, I had a look at the Windows permissions (Windows7) and found that somehow they were not set as they should have been. I still cannot explain how that happened, but I reset them in both Autoslew and Sequence Program Files AND Program Data files - and Presto!!!!! system all worked again!
So this may not be your problem, but to check with Windows 7 go to the Program Files>Autoslew>(Right Click)>Properties>Security. Check that all permissions are allowed for Administrators, SYSTEM, and Users. Do the same for Sequence and for both Program Data files.
I don't know about Windows10, but this may give you a lead....
Someone more knowledgeable than I may have some better ideas - anyway let us know what you find. And good luck!
Mark
-
Bill,
You don't need clear skies. Just run the mount on a target in The SkyX - for up to several hours if necessary. No need for camera etc....
Mark
-
Very difficult to advise based on your post.
I think the first thing is to examine the Clservo logs. If you are not logging this data you need to go to Control>Misc settings>Enable log file.
Examination of these files during and after a run will tell you what the tracking errors and motor currents are in very fine detail.
This information may help pinpoint the trouble.
Mark
-
Fabrice, my information on NGC2104 and 2020 came from ESO:
https://www.eso.org/public/australia/news/eso1335.
Mark
-
Thanks Fabrice.
That torus is somewhat unusual, and being placed so close to the strong Ha nebula adds to the interest.
Mark
-
Many thanks Artem
Mark
-
This interesting region in an arm of the Large Magellanic Cloud contains several contrasting objects. NGC 2020 is the large very turbulent Ha emission nebula, and beside it is a more unusual oxygen emission nebula lit by young blue stars. The smaller, also very turbulent, Ha cloud is NGC2040. There is a number of other interesting objects scattered through the image.
The data for this image was taken over three fairly difficult nights characterized by intermittent cloud, wind, and high humidity.
2 hours RGB, and 2 hours Ha make up the image. It is an LRGB combination using Ha and R data for the L channel. ASA10N, DDM60 unguided.
Mark
-
Another great image
I like the curtains parting to reveal the galaxy - which is beautifully detailed for such a small object.Mark
-
Max,
I'm having no trouble with 5240 and 211 on two different systems - one using DDM60 and the other DDM85A. MLPT works fine - meridian flip etc....
Mark
-
Fine collection.
If I had to pick a favourite it would be SH2-187 - superbly detailed!Mark
-
Load carrying capacities are 45, 65, and 100 kilogram for the Bsaic, Standard and Premium respectively.
Mark
-
In addition to the differing weight carrying capacity, the Basic DDM85 has a different PA alignment adjustment from the Standard DDM85. Rather than a direct azimuth adjustment, it uses a lateral rocking adjustment.
The DDM85 Premium runs on a 24V supply; the other two on 12V.
Mark
-
Mike,
Sequence 213 has been released, but the upgrade seems to relate only to Equatorial Fork mounts.
I haven't bothered to update to it.
Mark
-
Max,
Two issues come to mind:
1. Have you tried re-installing 209 - or 211? (211 works fine for me)
2. Have you tried unchecking the 'Use Readout Modes' box?
These steps may at least give you some idea of what the trouble might be....
Mark
-
Thomas, that's a REALLY deep image!
Great colour, and an interesting target - way too far North for me to see. Thanks for sharing.
Mark
-
John and Colin,
I have figured out what my problem was. Because I am running an f/8 scope, the Autofocus coarse and fine steps on the Atlas need to be around 24000 and 12000 respectively. This takes a long time, and Sequence would time out.
Of course, the answer was easy once I realised what 'Focuser Timeout' in the Current Location and Hardware screen actually does. (It is not very clearly described in the mouse-over). I never need to think about it when I'm using the ASA10N and AAF3, but with the f/8 system all that is necessary is to increase the Focuser Timeout to 100 seconds, and everything works fine. It takes time but it works!
Mark
-
I don't know if it's relevant or not, but I have always had the 'Don't use Readoutmodes' box ticked.
I guess it may depend on the camera, but I only use the slowest readout modes anyway. I suppose by ticking the box Sequence ignores Maxim readoutmode reading.
Mark
-
Very strange, Mike!
I can't really offer much help, except to say that I've never had this problem with any of the Sequence versions up to 2.1.1, which I'm currently using with Autoslew 5244.
All my narrow band subs are 600 sec+.
I've never been able to decipher these error messages. Since the problem has spontaneously emerged, could a cable have become dodgy?
Mark
-
Splendid colour rendition and great detail
Mark
-
For the Autoslew Manuals go to the Downloads Tab on the main website. Open Google Drive, then:
For Autoslew: Customer Downloads>Software>Autoslew>Manuals. There you will find the correct manual for your mount.
For Sequence: Customer Downloads>Software>Sequence>Sequence200. You will also find other useful information notes.
You should have MaximDL to manage the camera. I use it to do this, and MaximDL is in turn managed by Sequence.
Mark
-
The ASA website has Autoslew and Sequence Manual downloads available.
You need to download the correct Manuals - there are different instructions for mounts with absolute encoders or relative encoders.
The manuals give step by step instructions on setting up. It is important to follow the instructions very carefully, as ASA mounts behave differently from others.
If you are still having difficulty with operation of the mount, after following the instructions, ask for help from ASA support. The email address is on the ASA website.
Mark
-
Does anyone use Sequence Autofocus with an FLI Atlas focuser?
Sequence seems to 'think' that 1000 Atlas steps equals 1 mm of travel, whereas it actually takes 12500 steps for 1 mm.
I thought I could just live with that by simply scaling the Coarse and Fine steps and the Maximum Way allowance. However, during the move from 'middle' the system fails due to 'focuser time-out'.
Is there a way of allowing longer time for the focuser to move? (The Atlas is very slow!)
Anyone?
Mark
-
Brilliant image! This never gets above the horizon here, so it's great to see it .
Mark
GPS connection
in Software
Posted
Hi Luc,
The following may be irrelevant in your case, but for what it's worth:
I assume the Comport assignment in Autoslew matches the assignment in Device Manager, and that the GPS Comport is on (box in Autoslew Comports Window is ticked).
Trivial I know but worth checking.
I have had issues with the GPS plugged directly into my laptop. Using a relatively short (2m) heavily shielded USB connector cured the problem!!! Using a longer unshielded lead caused it to fail again....go figure! And the same happened with a second GPS.
Good luck,
Mark